Expense management that works with Agresso

Key takeaways

• Vergo integrates with Unit4 (formerly Agresso) and syncs projects and phases from your ERP structure.
• You keep your existing cards — corporate, fuel, or personal — with no card applications or banking changes required.
• AI inference codes transactions to the correct project and phase on first sight, with no rule library to maintain.
• Card spend, employee reimbursements and AP invoices all flow through the same coding model and sync to Unit4.

How does the Unit4 integration work?

Vergo reads your projects and phases from Unit4, codes every expense to the appropriate project and phase, and pushes coded entries back to your ERP. Transactions become available to code the moment they occur, before they clear, so coding happens in real time rather than accumulating as a month-end task. Once transactions clear, the coded entries sync into Unit4 automatically. This structure ensures that nothing arrives in your ERP as an uncoded lump requiring manual intervention, and your project accounting reflects spend as it happens rather than days or weeks later.

Can we keep our existing cards?

Yes. Vergo does not issue cards and never requires you to switch providers. It connects to the cards your business already holds — corporate cards, fuel cards, and personal cards used for reimbursement. Connecting your existing cards involves no card applications, no re-issuing and no banking change. This card-agnostic approach means finance teams can adopt expense management without negotiating new banking relationships, re-training employees on new card programs, or managing a transition period where old and new card programs run in parallel. The expense management layer adapts to your existing payment infrastructure rather than forcing infrastructure changes.

What does AI-native expense management mean for project accounting?

Traditional rules engines match transactions against keyword lists and text patterns; when a transaction fails to match, someone codes it manually. AI inference works differently: it proposes coding based on your own accounting structure and transaction history, including projects and phases, with no rule library to build and no keyword lists to maintain. New vendors are coded on first sight because the model understands context from similar past transactions. Every proposed coding includes an explanation of why it was chosen, so a reviewer can confirm the logic in seconds rather than re-code from scratch. For project-driven organizations, this means the system learns which vendors, amounts and descriptions typically map to which projects and phases, then applies that understanding automatically.

A practical example

A mid-market professional services firm runs three concurrent client projects in Unit4, each with multiple phases for discovery, delivery and closeout. An architect buys software licenses for the discovery phase of Project A; the transaction appears in Vergo before it clears. The AI proposes Project A and the discovery phase, explaining that this vendor and amount match prior discovery-phase purchases. The project lead confirms in seconds. Two days later, the same architect files a cab receipt for travel to Project B's site; Vergo codes it to Project B's delivery phase based on the timing, location metadata and the employee's recent project assignments. Both entries sync to Unit4 with full project and phase coding intact.

Do reimbursements and AP invoices sync to Unit4 as well?

Yes. The same coding model handles card spend, employee reimbursements and AP invoices, and all three sync to Unit4 the same way. Most tools treat these as separate products with separate coding logic, which creates reconciliation problems when the same vendor is coded differently depending on payment method. A single coding model eliminates that inconsistency. For AP invoices specifically, Vergo captures, codes and approves the invoice, then syncs the coded entry to Unit4 while payment itself stays on the rails you already use — your existing banking and payment workflows remain unchanged.

Who uses Unit4?

Unit4 is deployed by mid-market companies across industries, with particular concentration in professional services and the public sector. It was formerly known as Agresso, and many finance teams still use that name internally. Organizations that have built their financial operations around Unit4's project and phase structure need an expense management layer that adapts to that structure rather than imposing a different chart of accounts or forcing manual mapping at month end. The expense system should read the ERP's structure and code to it natively, preserving the project-centric workflow that Unit4 enables.

How Vergo handles this

Vergo integrates with every ERP and accounting software, including Unit4. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use. Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into your accounting or ERP software. Connecting your existing cards involves no card applications, no re-issuing and no banking change.

Related questions