Key takeaways
- Maconomy already has expense sheets, so an add-on must earn its place on card spend and coding accuracy.
- Vergo ranks first for job, task and activity coding by inference on existing cards.
- SAP Concur, Emburse and Navan are travel and expense suites; Expensify focuses on reports.
- Ask each vendor whether entries arrive as Maconomy expense sheets or as something finance re-keys.
Where should you go next?
- Vergo's Deltek Maconomy integration
- What expense management software integrates with Deltek Maconomy?
- Get started with Vergo
Which expense management add-ons work best with Deltek Maconomy?
- Vergo: job, task and activity by inference, text receipts, existing cards, expense sheets with receipts through the Containers Web Service.
- Maconomy expense sheets: the native option for claims, mileage and approvals.
- SAP Concur: travel and expense suite for global firms.
- Emburse: travel and expense on existing card programs.
- Navan: travel booking with expense attached.
| Option | Cards | How coding is proposed | Route into Deltek Maconomy |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own Deltek Maconomy structure and history, with the reason shown | Expense sheets with receipts through the Containers Web Service |
| Maconomy expense sheets | Card spend entered by the employee | Employee selects job, task and activity | Native |
| SAP Concur | Existing cards through bank card feeds | Categorisation from merchant and transaction data | Ask how entries reach Deltek Maconomy |
| Emburse | Existing Amex, Mastercard or Visa programs, or Emburse Cards | AI categorisation | Ask how entries reach Deltek Maconomy |
| Navan | Navan cards, or existing cards through Navan Connect | Categorises by merchant type and employee role | Ask how entries reach Deltek Maconomy |
What should an expense add-on do for Maconomy?
- Code to job, task and activity, not just a GL account.
- Arrive as an expense sheet, so Maconomy's approvals and billing still apply.
- Keep receipts attached for client re-billing.
- Keep the firm's card program.
Should you use Maconomy expense sheets or an add-on?
If most spend is out-of-pocket and staff code reliably, Maconomy on its own may be enough. If firm cards carry the volume and project accountants re-code jobs every close, an add-on that proposes the coding pays back. 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. Once your IT enables API access, Vergo creates expense sheets with receipts attached through Maconomy's Containers Web Service, coded to job, task and activity.
Frequently Asked Questions
Is Vergo a Deltek product?
No. Vergo is a separate platform that connects to Maconomy through its Containers Web Service once IT enables access.
Can Vergo and Maconomy Touch run together?
Yes. Many firms keep Maconomy Touch for mileage and use Vergo for card spend.
Do we have to switch cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
Does Vergo handle vendor 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 details?
On the Deltek Maconomy integration page.
