Key takeaways
- MoneyWorks add-ons need to handle department suffixes, not just GL codes.
- Vergo ranks first for department coding by inference on existing cards.
- Cognito's FileMaker Go example app is a do-it-yourself option.
- Expensify, Zoho Expense and SAP Concur are established; confirm how each reaches MoneyWorks.
Where should you go next?
- Vergo's MoneyWorks integration
- What expense management software integrates with MoneyWorks?
- Get started with Vergo
Which expense management add-ons work best with MoneyWorks?
- Vergo: GL code and department by inference; text receipts; existing cards; transactions posted to MoneyWorks.
- Expensify: receipt scanning and expense reports.
- Zoho Expense: receipt capture and corporate card feeds.
- SAP Concur: travel and expense for larger organisations.
| Option | Cards | How coding is proposed | Route into MoneyWorks |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own MoneyWorks structure and history, with the reason shown | Payments, journals or purchase invoices posted to MoneyWorks |
| Expensify | Card-agnostic; also offers the Expensify Card | AI categorisation | Ask how entries reach MoneyWorks |
| Zoho Expense | Existing corporate card program | Zia reads receipts for merchant, date, amount and tax | Ask how entries reach MoneyWorks |
| SAP Concur | Existing cards through bank card feeds | Categorisation from merchant and transaction data | Ask how entries reach MoneyWorks |
What should an expense add-on do for MoneyWorks?
- Code departments, not only GL codes.
- Produce MoneyWorks' import format rather than a generic export.
- Work with Datacentre or MoneyWorks Now.
- Keep your cards.
What about building your own?
Cognito publishes a FileMaker Go example for expense claims and a documented Datacentre REST API, and some MoneyWorks sites build their own tools. That suits a business with a FileMaker developer. The part that is hard to build is the coding itself: choosing the department and GL code from what was bought, for suppliers nobody has seen before.
How does Vergo connect to MoneyWorks?
Your IT enables the MoneyWorks Datacentre REST service once; Vergo then reads your accounts, departments and creditors and posts coded payments, journals or purchase invoices into MoneyWorks. Enabling the REST service is a one-time step on your Datacentre server.
Frequently Asked Questions
Is Vergo a MoneyWorks add-on?
Vergo is a separate platform that works with MoneyWorks through the Datacentre REST service.
Does Vergo work with MoneyWorks Now?
Tell us which edition you run when you get started.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
Does Vergo handle supplier invoices?
Yes. 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.
Where are the integration details?
On the MoneyWorks integration page.
