How to automate expense management in Sage 200

Key takeaways

• Sage 200 treats a credit card as a Cash Book bank account, and card spend is entered as nominal payments against it.
• A nominal payment line carries the nominal code, cost centre and department, a VAT code and, in Professional, project detail.
• Bank feeds rules can set the nominal account and VAT code, but the rules page does not mention cost centre or department.
• Vergo proposes the full nominal analysis for each purchase and records bank payments through the Sage 200 API.

Where should you go next?

• Vergo's Sage 200 integration
• What expense management software integrates with Sage 200?
• Get started with Vergo

How do you automate expense management in Sage 200, step by step?

1. Connect Sage 200. Vergo connects through the Sage 200 API and reads your nominal codes and cost centres, whether Sage 200 runs on your servers or in the cloud.
2. Link your existing cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
3. Gather receipts by text. 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.
4. Confirm the analysis. Vergo proposes nominal code, cost centre, department and VAT code for every receipt line, with the reasoning.
5. Post the bank payment. The coded purchase is recorded as a bank payment on the card's Cash Book account, ready to reconcile against the statement.

What does Sage 200 need on each card purchase?

• Bank account: the credit card set up in the Cash Book.
• Nominal code, cost centre and department: the three parts of a Sage 200 nominal account.
• VAT code: so the VAT return picks up reclaimable input tax.
• Narrative and reference: so the line makes sense at audit.

Where do Sage 200's tools stop and automation start?

Bank feeds rules are useful for the regulars: the fuel supplier, the phone bill, the monthly software subscription. They match on the reference, amount or date and set the nominal account, VAT code and narrative. They cannot see what was on the receipt, so a builders' merchant charge that was half stock and half site consumables still gets split by hand, and the cost centre has to be chosen by someone who knows which branch spent it. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought — nominal code, cost centre, department and VAT together.

A practical example

A distribution business on Sage 200 has twelve cardholders across three depots. A depot manager buys pallet wrap and a team breakfast on one card. Vergo texts for the receipt, proposes the packaging nominal code with that depot's cost centre and standard-rated VAT for the wrap, and staff welfare with the same cost centre for the breakfast, pointing to earlier purchases coded that way. Finance confirms, and one bank payment with two lines lands in Sage 200.

How Vergo handles this

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. In Sage 200 that means the proposal covers the nominal code, cost centre, department and VAT code at once, because a right nominal code on the wrong cost centre still skews the management accounts. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. 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.