How does Vergo connect to Dayforce UK?
Dayforce runs in the customer's own environment, and credentials are a web-services user created inside that instance. Your IT team enables web-services access once; Vergo does the rest. The RESTful Web Services developer guides are public on help.dayforce.com, which is what makes this a verifiable connection rather than a promise.
What syncs into Dayforce UK?
Approved reimbursements post as employee pay adjustments. Vergo reads Employees and the relevant HR details to match each claimant to the right record, resolves the pay group and pay code XRefCodes your configuration uses, and creates the adjustment via EmployeePayAdjustments. EmployeePaySummaries can be read back to confirm the adjustment landed in the intended cycle.
The practical effect is that a receipt photographed on a Tuesday can be an approved, coded pay adjustment sitting in the correct Dayforce pay group by Wednesday, without a payroll administrator typing anything.
How do employees submit expenses?
On their phone, at the point of spend. Photograph the receipt, choose the expense category and the department or cost centre, submit. The claim routes to the approver your structure defines. Policy rules run at submission — receipt thresholds, category limits, per-role approval authority — so problems surface with the employee, not with payroll a fortnight later.
What does payroll actually review?
A list, not a pile. Everything in it has already been approved by a named manager and coded to a real department, and each line links to its receipt image. Payroll's job becomes confirming the batch and the cycle it belongs to, then letting Vergo create the adjustments.
Claims approved after cut-off carry cleanly into the next cycle rather than being dropped or double-paid, and every claim's state is visible to the employee, which ends the majority of "where is my money" emails.
Why post reimbursements through payroll at all?
For UK employers running an enterprise HCM, paying reimbursements through the payroll cycle keeps one payment record per employee, one audit trail, and one place where the treatment of each category is defined. Paying expenses separately by bank transfer splits that record in two and makes year-end reconciliation the finance team's problem.
What does a controller get out of it?
Visibility before the money leaves. Because claims are coded at the point of spend and approved by the manager who owns the budget, out-of-pocket spend appears in the department it belongs to during the period it happened, not as a lump discovered after the cycle closes. Categories that drift — subsistence, travel, small equipment bought in a hurry — become visible as trends rather than as a surprise at year end.
The record also survives people leaving. When a manager moves on, the reasoning behind an approval does not walk out with them, because the approval, the coding and the receipt are held together on the claim itself.
What does setup involve?
Three things: a web-services user in your Dayforce instance, a mapping of your expense categories to the pay codes you want reimbursements to use, and your approval hierarchy mirrored in Vergo. Once those are set, the flow runs every cycle without further configuration.
Does Vergo integrate with Dayforce UK?
Yes. Vergo posts approved reimbursements into Dayforce as employee pay adjustments, using the documented RESTful Web Services in your own Dayforce instance.
What Dayforce objects does Vergo use?
Employees and employee HR details, EmployeePayAdjustments for the reimbursement itself, EmployeePaySummaries to confirm the cycle, and pay group and pay code XRefCodes for coding.
Who has to enable the connection?
Your IT or Dayforce administrator creates a web-services user in your instance once. Vergo handles configuration and mapping from there.
What happens to claims approved after cut-off?
They carry to the next cycle. Vergo tracks which cycle each adjustment belongs to so nothing is paid twice or silently dropped.
