How to automate expense management in Tryton

Key takeaways

• Tryton is open-source business software with financial and analytic accounting, maintained by the Tryton Foundation.
• Bank and card statements are booked with the account_statement module, with CSV and OFX import.
• There is no official employee expense module; analytic accounts can be set on move and invoice lines.
• Vergo proposes account and analytic coding by inference and records account moves or supplier invoices through Tryton's RPC interface.

Where should you go next?

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

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

1. Issue an application key. Your administrator or hosting provider creates a user application key for Vergo. Vergo then reads your accounts, analytic accounts and parties.
2. Keep the cards you have. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
3. 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 coding. Vergo proposes the expense account and analytic accounts on each axis you use.
5. Record the move. Card spend is recorded as an account move against the card account; supplier bills as supplier invoices.

What does Tryton need on each card purchase?

• Account for the expense.
• Analytic accounts, one per axis your company reports on.
• Party: the supplier or card issuer.
• Date and amount matching the statement line.

Where does Tryton stop and automation start?

Tryton's statement module books what the bank says happened, and its reconcile wizard matches moves to statement lines. Its OCR modules read supplier invoices. Nothing in the standard modules collects a receipt from an employee or decides the analytic split of a card purchase. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought, then proposes account and analytic coding together.

A practical example

A research services company on Tryton tracks costs on two analytic axes: department and client project. A lab manager buys reagents for one client project and printer toner for the office on one card. After a quick text for the receipt, Vergo proposes the lab supplies account with the lab department and that client's project for the reagents, and office supplies with administration for the toner. The accountant confirms, and one account move with two lines is recorded; the statement import then reconciles against it.

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 Tryton, it proposes a value for every analytic axis you use, not just the first. 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.