Expense management that works with IRIS

Key takeaways

• Vergo reads your chart of accounts from IRIS and codes every transaction to the right account, department and class using AI inference instead of rules.
• You keep your existing corporate cards, fuel cards and personal cards — no new card applications or banking changes required.
• Card spend, employee reimbursements and AP invoices flow through one coding model and sync to IRIS with consistent account assignments.
• Transactions are ready to code the moment they happen, and sync into IRIS once they clear.

Does Vergo work with IRIS?

Yes. Vergo connects directly to IRIS and syncs coded transactions into your accounting system. It reads your chart of accounts, including custom departments and classes, and applies those dimensions to every card transaction, reimbursement and invoice. Each entry arrives in IRIS coded to the correct account, department and class, ready to post without additional handling. The system uses inference rather than pattern-matching rules, so coding adapts to your IRIS structure as it exists today, with no configuration layer to build or maintain between the two systems.

Do we need to change credit cards?

No. Vergo does not issue cards and works with the cards your business already holds. This includes corporate credit cards, fuel cards and personal cards employees use for reimbursable purchases. Connecting your existing cards involves no card applications, no re-issuing and no banking change. The platform reads transaction data from those cards and applies coding, then syncs the results into IRIS. Because Vergo is card-agnostic, you control your banking relationships and card programs independently of your expense management layer, and any card that generates a transaction feed can participate in the same coding and reconciliation workflow.

What does AI-native expense management mean for IRIS users?

Traditional rules engines match keywords or vendor names to accounts; when a transaction does not match a rule, someone codes it manually. 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. This matters in IRIS because the system often uses multiple dimensions — account, department, class — and inference handles all dimensions at once, learning from past assignments rather than requiring explicit mapping for each vendor and each dimension combination.

A practical example

A construction firm running IRIS tracks costs by GL account, department and job class. An employee buys safety equipment from a new vendor the system has never seen. A rules engine would leave the transaction unassigned or route it to a catch-all account, requiring manual review and coding across three dimensions. Vergo infers the correct account from the transaction description, assigns the department based on the cardholder, and applies the job class from recent similar purchases, then shows the reviewer why each dimension was chosen. The reviewer confirms all three in one step, and the coded entry syncs to IRIS ready to post.

Do reimbursements and invoices sync to IRIS the same way?

Yes. The same coding model handles card spend, employee reimbursements and AP invoices, and all three sync to IRIS with the same account, department and class structure. Most tools treat these as separate products with separate coding setups; the same vendor coded two different ways creates a reconciliation problem. Vergo codes all three transaction types through one inference model, so a plumbing supply vendor receives the same account and class assignment whether the purchase arrives as a card charge, a reimbursement claim or an invoice. Payment itself stays on the rails you already use — Vergo captures, codes and syncs invoices, but does not replace your existing payment process.

Who runs IRIS?

IRIS is run by small and mid-sized businesses across industries, often in sectors like construction, nonprofits and professional services where job costing and fund accounting matter. These organizations need expense management that adapts to the chart of accounts and dimensions already configured in IRIS, not a system that requires rebuilding accounting structure to fit a vendor's template. Vergo reads from your existing IRIS structure and writes back to it without requiring parallel configuration or manual reconciliation between the two systems.

How Vergo handles this

Vergo integrates with every ERP and accounting software, including IRIS. 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. 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. 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. Connecting your existing cards involves no card applications, no re-issuing and no banking change. Approval workflows are optional and fit how you already control spend: route by GL account or by amount — or skip approval flows entirely and let policy flags catch only what breaks a rule. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.