What does the Vergo + isolved integration do?
- Capture employee reimbursement claims at the moment of spend, with the receipt attached from a phone
- Code each claim to the department it belongs to and route it through your own approval chain
- Code claims by AI inference from your accounting structure and history — no rule library to build
- Read receipts line by line, predicting the coding from what was actually bought rather than the vendor name
- Show why each coding was chosen, so approval is confirmation rather than re-coding
- Close the batch before the run opens and hand it to isolved as pay-import lines in the format it expects
- Keep every claim, receipt image and approval step on record in Vergo, so an audit request is a lookup
Reimbursements closed before the isolved run opens
Employees claim from their phone with the receipt attached, Vergo codes each claim to a department and routes it for approval, and the approved batch arrives as a pay-import file in the format isolved expects.
App information
Security and compliance
Encryption
Infrastructure
Access controls
Audits
Frequently asked questions
Does Vergo integrate with isolved?
Yes, for employee reimbursements. Access is enabled from inside your isolved account, and approved claims are delivered in the pay-import format isolved expects. Vergo does not write into your pay run.
Can Vergo run employee reimbursements for isolved payroll?
Yes. Claims are submitted with receipts, coded to a department or cost centre, approved through your chain, and batched into a reimbursement import for the next isolved pay run.
What does Vergo hand to isolved?
A structured reimbursement file: employee, amount, date and cost coding per line, in the import format isolved expects. Your payroll administrator imports it as part of the normal cycle.
What does setup require from us?
Enable API access from inside your isolved account. Vergo then configures coding, approval rules and pay-period batching. Because isolved is hosted, there is no install step.
Does isolved publish public API documentation?
The isolved REST reference sits behind a myisolved login, so its endpoints are not publicly verifiable. Vergo therefore commits to the pay-import path rather than naming endpoints it cannot confirm.
Discover more integrations
.png)
.png)
.png){kind=logo}
.png)
White-glove onboarding and customer support.
