Expense management that works with Infor Lawson

Key takeaways

• Vergo reads your chart of accounts from Infor Lawson and codes every transaction by inference from your accounting structure and history.
• You keep the cards your business already holds — corporate cards, fuel cards, or personal cards used for reimbursement — with no re-issuing or banking change.
• Card spend, employee reimbursements and AP invoices run through one coding model and sync to Infor Lawson the same way.
• Transactions are ready to code the moment they happen, and once they clear, they sync into Infor Lawson coded and ready to post.

How does the Infor Lawson sync work?

Vergo reads your chart of accounts from Infor Lawson and codes every expense to the right account, department and class, so entries arrive in Infor Lawson coded and ready to post. 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. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Because Vergo infers coding from your own accounting structure and history, new vendors are coded on first sight without needing keyword lists or rule updates.

Do you have to change cards?

No. Vergo does not issue cards and never asks you to switch. It connects to the cards your business already holds — corporate cards, fuel cards, personal cards used for reimbursement — and connecting your existing cards involves no card applications, no re-issuing and no banking change. The platform is card-agnostic by design, so the payment rails you already use continue to work exactly as they do today. This means finance teams can layer expense management onto existing banking relationships without renegotiating terms, retraining staff on new card programs, or waiting for physical card distribution.

Who runs Infor Lawson?

Infor Lawson, from Infor, is run by large organisations in healthcare. If your finance team lives in it, the expense layer should adapt to it — not the other way round. Healthcare organisations typically run complex accounting structures with department hierarchies, grant tracking, and project-level reporting, and Infor Lawson is built to handle that complexity. An expense management system that reads those structures directly and codes to them by inference reduces the manual reconciliation work that comes from forcing a rigid external tool onto a flexible internal accounting model.

Do reimbursements and AP invoices work with Infor Lawson too?

Yes — the same coding model handles card spend, employee reimbursements and AP invoices, and all three sync to Infor Lawson the same way. Most tools treat these as separate products with separate coding setups; the same vendor coded two different ways is a reconciliation problem you inherit. When card transactions, reimbursement requests, and invoices all flow through one coding model trained on your accounting history, they land in Infor Lawson with consistent GL accounts, departments, and classes. Payment itself stays on the rails you already use — Vergo captures, codes, approves and syncs invoices, but the actual payment happens through your existing AP process.

How Vergo handles this

Vergo integrates with every ERP and accounting software, including Infor Lawson. It 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. 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.