How to automate expense management in ERPNext

Key takeaways

• ERPNext is free, open source ERP for small and medium businesses, self-hosted or on Frappe Cloud.
• Employee claims live in the Frappe HR app's Expense Claim; company card charges arrive as bank transactions to be matched.
• Cost Center and Project are ERPNext's default accounting dimensions, and you can add more, such as Department.
• Vergo proposes account and dimensions from history, texts for receipts and records Journal Entries or Purchase Invoices through the REST API.

Where should you go next?

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

How do you automate expense management in ERPNext, step by step?

1. Issue an API key. Your ERPNext instance issues Vergo an API key against the Frappe REST API; Vergo then reads your chart of accounts and cost centers and records coded card spend as Journal Entries or Purchase Invoices, and out-of-pocket spend as Expense Claims.
2. Connect your existing cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
3. Collect 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. Code account and dimensions. For each line Vergo suggests the expense account, cost center and project, plus any custom dimension you use.
5. Record in ERPNext. Confirmed spend becomes a Journal Entry or Purchase Invoice, ready to reconcile against the bank transaction.

What does ERPNext need on each card transaction?

• Account: from your chart of accounts.
• Cost Center: a default accounting dimension.
• Project: the other default dimension, which also feeds project costing.
• Custom dimensions: such as Department, if you have added them.

Where does ERPNext stop and automation start?

ERPNext takes bank transactions from an integration, a statement import, Data Import or the API, and lets you match them to a Payment Entry or Journal Entry. Matching assumes the entry exists. For card spend, someone still creates it, picks the cost center and project, and finds the receipt. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought — the account, cost center and project — not just the vendor name on the header.

A practical example

A distributor running ERPNext on Frappe Cloud has two warehouses set up as cost centers. A warehouse manager buys pallet wrap and a forklift battery charger on one card. Vergo requests the receipt by text, suggests consumables on the north warehouse cost center for the wrap and equipment repairs on the south one for the charger, based on who usually buys what. The accountant approves, and a Journal Entry with both lines is recorded.

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. Because ERPNext lets you add dimensions, Vergo reads the ones your instance actually uses rather than assuming a fixed set. 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.