How does Vergo connect to Employment Hero Payroll UK?
Through an API key issued from your own payroll account — you switch access on once, Vergo does the rest. The UK developer guides are published at api.keypay.com.au, including the employee recurring expense reference under pay run inclusions.
What posts into the pay run?
Approved reimbursements post as expense requests, and standing items post as employee recurring expense inclusions on the pay run. Vergo works with the pay run create and finalise lifecycle so claims land in the period they belong to rather than whichever period someone happens to be looking at. Full CRUD on these records means a corrected claim can be corrected in payroll, not worked around with a second entry that cancels the first.
How does a claim get there?
An employee photographs the receipt when they spend, chooses the expense category and department or cost centre, and submits from their phone. The claim routes to their approver. Your policy — receipt thresholds, category limits, approval authority — runs at submission, so the payroll team is never the first person to discover a problem with a claim.
What does payroll see?
Per period, a reviewed list of approved claims, coded and receipted, ready to post as inclusions. What payroll no longer sees is a folder of photographs, a spreadsheet somebody maintains by hand, and a queue of employees asking when they will be paid back — each claim's state is visible to the person who submitted it.
Why does full CRUD matter?
Because claims change. A receipt is illegible and gets replaced, an amount was miskeyed, an employee left before the claim was paid. When the integration can update and delete inclusions rather than only create them, corrections stay inside payroll where they can be audited, instead of turning into a manual adjustment that nobody can explain six months later.
What about mileage and allowances?
Mileage is calculated from the journey at the rate you set. Standing allowances become recurring expense inclusions, configured once, so they stop consuming payroll attention every period while remaining visible and changeable.
What does finance get out of it?
Reimbursement spend coded to the department or cost centre that incurred it, in the period it happened, with each line traceable to a receipt and a named approver. That turns expense categories from a monthly total somebody assembles into a number that can be trended and questioned.
It also makes leavers survivable: the reasoning behind an approval stays on the claim, so a query after the approving manager has moved on is answered from the record.
How long does setup take?
Issue the API key from the payroll account, map your expense categories to the values your pay run expects, and mirror your approval hierarchy. Employees can submit from day one, and the first posted batch lands on your next pay run.
Does Vergo integrate with Employment Hero Payroll UK?
Yes. Approved reimbursements post as expense requests and pay run inclusions in your UK KeyPay payroll.
What records does Vergo create?
Employee expense requests, employee recurring expense inclusions on the pay run, and it works with pay run create and finalise so claims land in the right period.
Where do the API credentials come from?
From your own payroll account. You enable access once and Vergo configures and runs the rest.
Can a claim be corrected after posting?
Yes. The pay run inclusion records support update and delete, so corrections stay inside payroll rather than becoming untraceable manual adjustments.
