Do employee reimbursements work with PayHero?
Yes. PayHero, the New Zealand payroll product from FlexiTime, publishes a public API, and Vergo connects to it directly — the connection is self-serve, so nothing is needed from the customer or from the vendor to get started.
What actually moves between Vergo and PayHero?
Vergo reads PayHero for the records it needs to code claims correctly — Get Employee, Get Pay Item, Get Pay Cycle and Get Expense — so submissions attach to real employees and real pay items instead of a stale list. Approved reimbursements then post into PayHero through Save Expense and Save Employee Pay, landing on the right pay cycle for the pay run. PayHero's developer portal documents the full operation set at developer.payhero.co.nz.
What does Vergo do before anything reaches PayHero?
Reimbursements are low-dollar and high-friction: a receipt in a glovebox, a mileage note on a phone, a spreadsheet that reaches payroll the day it is due. Vergo moves the loop onto the phone. The employee submits where the spend happened, photographs the receipt into the record, and codes it to the job or category your business uses. The approver sees the amount, the receipt and the coding together, so approving is a judgement rather than an investigation.
How does a team use this day to day?
Claims accumulate through the pay cycle instead of arriving in a rush at cut-off. Whoever runs payroll opens PayHero and finds approved reimbursements already sitting against the right employees and pay items, with the evidence retained in Vergo if anyone later asks what a payment was for. The pay run stops being the moment reimbursements get discovered.
What does setup involve?
Because PayHero's API is publicly documented and self-serve, connection is quick. The real work is mapping — agreeing which Vergo categories correspond to which PayHero pay items, and confirming employee records line up on both sides. That is one session with the person who runs payroll, then a validation batch of a handful of claims before anything runs at volume.
What does Vergo not do?
Vergo is not a payroll system. PayHero stays the system of record for pay calculation, PAYE, leave and payday filing. Vergo covers the spend that happens before payroll sees it — cards, invoices and reimbursement claims — and hands over approved, evidenced, coded records.
What should you confirm before committing?
Ask how many reimbursement claims your team processes per pay cycle, how many arrive after cut-off, and how often a claim is paid without a receipt on file. Vergo will run a sample of your own claims end to end into a PayHero test cycle before you commit, which answers the question faster than a feature comparison.
Does Vergo integrate with PayHero?
Yes. PayHero publishes a public API and Vergo connects to it directly under a self-serve model — nothing is needed from the customer or the vendor to establish the connection.
Do approved reimbursements reach PayHero automatically?
Yes. Approved claims post into PayHero through Save Expense and Save Employee Pay, against the correct employee and pay cycle.
What does Vergo read from PayHero?
Employee records, pay items, pay cycles and existing expenses, so claims are coded against records that actually exist in PayHero rather than a manually maintained list.
Does Vergo replace PayHero?
No. PayHero remains the payroll system of record. Vergo handles the reimbursement claim — capture, receipt, coding and approval — before it becomes a pay line.
