Key takeaways
- Pennylane users range from freelancers to mid-sized companies, usually working closely with an accountant.
- Vergo ranks first where cards come from an existing bank.
- Pennylane's own cards and notes de frais are the native alternative if you are willing to move banking.
- SAP Concur, Navan, Expensify, Emburse and Zoho Expense fill other niches.
Where should you go next?
- Vergo's Pennylane integration
- What expense management software integrates with Pennylane?
- Get started with Vergo
How do the options rank for Pennylane users?
- Vergo: best overall on existing cards. Account and axes by inference, text receipts, justified entries.
- SAP Concur: for groups whose travel policy runs through Concur.
- Navan: for teams that book trips and file expenses in one place.
- Expensify: a simple report flow that accepts any card.
- Emburse: for companies tied to a particular card issuer.
- Zoho Expense: for companies already in the Zoho suite.
| Option | Cards | How coding is proposed | Route into Pennylane |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own Pennylane structure and history, with the reason shown | Transactions and journal entries with receipts, through the public API |
| SAP Concur | Existing cards through bank card feeds | Categorisation from merchant and transaction data | Ask how entries reach Pennylane |
| Navan | Navan cards, or existing cards through Navan Connect | Categorises by merchant type and employee role | Ask how entries reach Pennylane |
| Expensify | Card-agnostic; also offers the Expensify Card | AI categorisation | Ask how entries reach Pennylane |
| Emburse | Existing Amex, Mastercard or Visa programs, or Emburse Cards | AI categorisation | Ask how entries reach Pennylane |
| Zoho Expense | Existing corporate card program | Zia reads receipts for merchant, date, amount and tax | Ask how entries reach Pennylane |
What matters most for Pennylane users?
- Justificatifs on every transaction, for the accountant.
- Analytic reporting by project, region or team.
- Banking stability: not every company wants to move its cards.
Why does Vergo rank first for Pennylane?
Pennylane's model depends on every transaction being justified and categorised. 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. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Vergo connects through Pennylane's public API, reads your ledger accounts, and records coded card spend as transactions or journal entries with the receipt attached; reimbursements go in as supplier invoices to the employee.
Do you have to change cards?
No. Vergo does not issue cards; connecting your existing cards involves no card applications, no re-issuing and no banking change. Your bank connection to Pennylane is unchanged.
Frequently Asked Questions
Is Vergo only for construction companies?
No. Agencies, retailers and software companies use it; coding follows your Pennylane ledger accounts and axes.
How does Vergo compare with Pennylane's own cards?
Pennylane cards attach receipts to their own transactions. Vergo does the same, plus coding, for the cards you already hold elsewhere.
Does Vergo work outside France?
Vergo works wherever Pennylane does, through its public API.
How do we start?
Get started; Pennylane connects through its public API.
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.
