How does Vergo connect to Moorepay?
Through the Moorepay API portal at api.moorepay.co.uk, with credentials arranged from inside your own Moorepay account — you enable access once, then Vergo does the rest. Credential issuance is not documented publicly in the portal, so Vergo treats it as customer-arranged and handles the setup with your payroll contact rather than assuming a self-serve key.
What posts into Moorepay?
Approved reimbursements post as worker expenses through the Expense Module, which supports POST and PUT so a claim can be created and later corrected rather than reversed with a second entry. Vergo reads Workers to match each claimant to the right payroll record, and works alongside Process Payroll so expenses land in the run they were intended for.
How do employees claim?
On the phone, at the point of spend: photograph the receipt, pick the expense category and the department or cost centre, submit. The claim routes to the approver your structure defines. Policy runs at submission — receipt thresholds, category limits, who may approve what — so the payroll team is never the first to find a problem.
What changes for the payroll team?
The chasing stops. Instead of collecting claims by email, checking them against a policy from memory, waiting on managers and retyping totals, payroll reviews an approved list and lets Vergo post it. Every line carries its receipt and its approver's name, so a query months later is answered by a search.
Employees see the state of their own claims, which removes most of the traffic that lands on payroll in the week before pay day.
Why post through payroll instead of paying separately?
A separate expense payment run creates a second payment record per employee, a second reconciliation, and a second place where category treatment has to be decided. Posting through Moorepay keeps reimbursement inside the same record as pay, which is where an auditor expects to find it.
What about corrections and late claims?
Corrections use PUT on the existing expense record rather than a compensating entry, so what payroll holds matches what actually happened. Claims approved after the run has been processed carry to the next one with their state intact — not dropped, not paid twice.
What does finance see?
Reimbursement spend coded to the department or cost centre that incurred it, in the period it happened, each line traceable to a receipt and a named approver. Categories that grow quietly — travel, subsistence, small equipment — become trends rather than a monthly total someone assembles by hand.
It also makes turnover survivable: the reasoning behind an approval stays on the claim, so a query raised after the approving manager has left is answered from the record.
What does setup involve?
Enable API access on your Moorepay account, map your expense categories to the values your payroll uses, and mirror your approval hierarchy in Vergo. Employees can submit immediately, and the first posted batch reaches your next payroll run.
Does Vergo integrate with Moorepay?
Yes. Approved reimbursements post into Moorepay as worker expenses through the Expense Module, feeding the payroll run.
What Moorepay objects does Vergo use?
The Expense Module for POST and PUT of employee expenses, Workers to match claimants to payroll records, and Process Payroll for run timing.
How are credentials obtained?
From your own Moorepay account. Issuance is not documented publicly, so Vergo arranges it with your payroll contact as part of setup.
Can a posted expense be corrected?
Yes. The Expense Module supports PUT, so a claim is corrected in place instead of being reversed with a second entry.
