How does Vergo connect to Deel?
API access is switched on from inside your own Deel account — you issue a token from the Deel app with the scopes required, and Vergo does the rest. Deel's developer documentation is public at developer.deel.com, and the reimbursement flow is written up as a supported use case at its reimburse-expenses guide.
What posts into Deel?
Approved reimbursements become adjustments. Vergo resolves the employee's contract, selects the adjustment category that matches your expense category mapping, and creates the record via POST /rest/adjustments so it lands in the Global Payroll cycle before cut-off. Adjustment categories and contracts are read to keep the mapping accurate as your workforce changes.
Deel's EOR expenses follow a different path from Global Payroll adjustments; Vergo treats them separately rather than assuming one route covers both.
How do employees claim?
From the phone, when the spend happens. A photograph of the receipt, an expense category, a department or cost centre, and submit. The claim routes to the approver defined by your structure, and your policy runs at submission — receipt thresholds, category limits, who may approve what. Employees see the state of every claim, so they stop asking payroll.
Why does the cycle cut-off matter?
An adjustment only reaches a payslip if it exists before the cycle closes. Vergo tracks each claim against the cycle it is destined for, posts approved ones ahead of cut-off, and rolls anything approved late into the next cycle with its state intact. That is the difference between an employee being reimbursed this month and being reimbursed after they have chased twice.
What does this replace?
Usually a spreadsheet and a shared inbox. Someone collects claims by email, checks them against a policy from memory, asks a manager for a yes, retypes the totals into an adjustment screen, and files the receipts somewhere. Every one of those steps is a place for a number to change or a receipt to vanish.
With Vergo the coding and approval happen where the knowledge is, and the posting happens through Deel's own documented interface, so the payroll record and the expense record are the same record.
What does finance see?
Reimbursement spend, coded by department or cost centre, in the period it was incurred rather than the period someone got round to processing it. That matters most for the categories that quietly grow — travel, subsistence, equipment bought under time pressure — because a monthly total that is always assembled by hand is a total nobody trends.
Because approval and coding sit on the claim with the receipt, a later question is answered from the record rather than from someone's memory of a decision made in a busy week.
What is involved in setup?
Issue an API token in the Deel app with the adjustment scope, map your expense categories to Deel adjustment categories, and mirror your approval hierarchy. Employees can submit immediately; the first posted batch lands on your next cycle.
Does Vergo integrate with Deel UK payroll?
Yes. Approved reimbursements post into Deel as payroll adjustments through the documented POST /rest/adjustments flow, in time for the Global Payroll cycle.
What Deel objects does Vergo use?
Adjustments, adjustment categories, and contracts — enough to place the right amount against the right employee and category in the right cycle.
Does this cover Deel EOR workers?
EOR expenses use a different path from Global Payroll adjustments. Vergo handles the two separately rather than treating them as one flow.
Who issues the API credentials?
You do, from inside your Deel account. Vergo configures the mapping and runs the posting once the token exists.
