Key takeaways
- Premier has field expense submission, so an add-on must earn its place on job-level coding for cards.
- Vergo ranks first because it reads jobs and cost items and posts back to Premier.
- Expensify, SAP Concur and Emburse are general tools that usually do not know your job structure.
- Test any option on a receipt split across two lots.
Where should you go next?
- Vergo's Jonas Premier integration
- What expense management software integrates with Jonas Premier?
- Get started with Vergo
Which expense management add-ons work best with Jonas Premier?
- Vergo: job, level and cost item suggested; receipts by text; existing cards; GL journals and AP invoices posted through the API.
- Premier field expenses: native submission with receipts and approvals.
- Expensify: expense reports for office and sales staff.
- SAP Concur: for large contractors with corporate travel programs.
- Emburse: for firms keeping an existing card issuer.
| Option | Cards | How coding is proposed | Route into Jonas Premier |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own Jonas Premier structure and history, with the reason shown | GL journals and AP invoices with documents, posted through the API |
| Expensify | Card-agnostic; also offers the Expensify Card | AI categorisation | Ask how entries reach Jonas Premier |
| SAP Concur | Existing cards through bank card feeds | Categorisation from merchant and transaction data | Ask how entries reach Jonas Premier |
| Emburse | Existing Amex, Mastercard or Visa programs, or Emburse Cards | AI categorisation | Ask how entries reach Jonas Premier |
What should an add-on do for Premier?
- Read the job tree, down to phase, building or lot.
- Use Premier cost items, not a generic category list.
- Post back to Premier with the receipt.
Why job structure decides it
Premier's value is real-time job cost. A card purchase coded to an account but not a lot is invisible to the project manager until someone fixes it. Vergo proposes the lot and cost item before the cost posts. 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.
How does Vergo connect to Premier?
Vergo connects through the published Jonas Premier API, reads your jobs, accounts and cost items, and posts coded card spend as GL journals, or as AP invoices with the receipt added as a document. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into Premier.
Frequently Asked Questions
Is Vergo a Premier module?
No. Vergo sits outside Premier and uses its published API.
Can Vergo work alongside Premier field expenses?
Yes. Some teams keep Premier submission for reimbursements and use Vergo for cards.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
Does Vergo handle subcontractor and 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 details?
On the Jonas Premier integration page.
