How does Vergo connect to Employment Hero Payroll?
Directly, through the public API documented at api.keypay.com.au. This is the self-serve case: no partner application, no vendor gatekeeping, no IT project. That matters because most payroll integrations stall in a queue rather than in code.
What posts into the pay run?
Approved reimbursements post as employee expenses on the pay run, using POST /payrun/{id}/employee-expenses. Vergo also works with EmployeeExpenseRequests where the request record is the right home for a claim, and EmployeeRecurringExpenses for the standing monthly items — a phone allowance, a tool allowance — that otherwise get retyped every period. Webhook registrations let Vergo react to pay run events rather than poll blindly.
These are dedicated expense endpoints, not a generic adjustment field pressed into service, which is why reimbursements through Employment Hero Payroll land cleanly and stay legible on the payslip.
What happens before the post?
An employee photographs a receipt at the point of spend, picks the expense category and the department or cost centre, and submits. The claim routes to the approver your structure defines, with your policy enforced at submission. Only approved claims are eligible to post, and each one carries its receipt and its approver's name for as long as the record exists.
How do recurring expenses fit?
Standing reimbursements are set up once as recurring expenses and stop being a monthly task. Vergo keeps the recurring records aligned with what your policy says an employee is entitled to, so a change made in one place does not have to be remembered in another.
Why post through payroll rather than pay separately?
One payment record per employee, one audit trail, one place where each category's treatment is defined. Paying reimbursements by separate transfer creates a second stream that has to be reconciled at year end, usually by whoever is least able to argue their way out of it.
What does finance get?
Reimbursement spend coded by department or cost centre in the period it happened, with each line traceable to a receipt and an approver. Categories that grow quietly — travel, subsistence, small equipment — become trends you can see rather than a monthly total someone assembles by hand.
What happens to late claims?
They carry to the next pay run with their state intact rather than being dropped or entered twice. Employees can see where their own claims stand, which removes most of the traffic that otherwise lands on the payroll administrator in the days before pay day.
What does setup involve?
An API key, a mapping of your expense categories to the values your pay run uses, and your approval hierarchy mirrored in Vergo. Because the API is public and self-serve, the connection can be live the day you decide to do it — the pacing is your configuration, not a vendor's response time.
Does Vergo integrate with Employment Hero Payroll (KeyPay)?
Yes. Vergo connects to the public KeyPay API and posts approved reimbursements as employee expenses on the pay run.
Which expense endpoints does Vergo use?
EmployeeExpenseRequests, PayRunEmployeeExpenses including POST /payrun/{id}/employee-expenses, EmployeeRecurringExpenses, and webhook registrations for pay run events.
Does the vendor have to approve the integration?
No. The API is public and self-serve, so nothing is needed from Employment Hero or from your IT team beyond an API key.
Can standing allowances be automated?
Yes, through recurring expense records, so monthly allowances are not retyped every pay run.
