How to automate expense management in 24SevenOffice

Key takeaways

• 24SevenOffice has become Finago; the accounting product is Finago Office and payroll is Finago Payday, serving Norway, Sweden and Finland.
• Travel and expenses are registered through the Economy app, with OCR pre-fill, approval and payout through payroll.
• Each expense carries a project and department, and dimensions can be made mandatory.
• Vergo proposes account and dimensions for company card spend, texts for receipts and posts through the REST API.

Where should you go next?

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

How do you automate expense management in 24SevenOffice, step by step?

1. Connect 24SevenOffice. Vergo connects directly through the documented 24SevenOffice REST API, reads your accounts and dimensions, and posts coded card spend as transactions. It is self-serve.
2. Connect company 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. Propose account, project and department. Vergo suggests the posting account, VAT and dimensions for each line, with the reason.
5. Post. Confirmed spend lands in the ledger, while employee travel claims can keep flowing through Finago Payday.

What does 24SevenOffice need on each card transaction?

• Account: the posting account for the expense type.
• VAT code: set per expense type in the travel and expense setup.
• Project and department: which can be mandatory dimensions.
• Receipt: for audit.

Where does 24SevenOffice stop and automation start?

The travel and expense flow is built around the employee: register a trip or outlay in the app, let OCR fill in the details, send it for approval, and it reaches payroll. That fits per diem and mileage well. A company card purchase is different, because nobody is owed money, yet it still needs a project, a department and a receipt. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought, not just the vendor name on the header.

A practical example

A Norwegian engineering consultancy on 24SevenOffice gives company cards to project leaders. One pays for ferry tickets and site safety equipment on a client project. Vergo texts for the receipts, proposes travel with the client project and the Bergen department for the ferry, and small equipment with the same project for the safety kit. The finance manager confirms, and both post with dimensions set.

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. For 24SevenOffice that means the projects and departments your ledger already uses. 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.