Vergo connects to the Push Operations API to read employee records and match reimbursement claims. Write endpoints are not confirmed in the public documentation, so Vergo prepares approved reimbursements in the import format the pay run expects rather than writing into the payroll ledger.

Yes. Vergo captures claims with receipts, runs approvals against your location and cost centre structure, and produces approved reimbursement entries for the Push Operations pay period.

Vergo reads Employees to match claims to people, and generates reimbursement entries — employee, amount, date, description, and cost coding — in the import format Push Operations expects. Vergo does not write into the payroll ledger.

Your IT issues the token once, and Vergo handles the connection from there. Your side is confirming employees, location and cost centre structure, and the target pay period — typically a single working session.

Push Operations pays reimbursements through the pay run. Receipt capture, approval routing, and the documentation behind each claim sit outside it — that is Vergo's part.