Key takeaways
- Pennylane has expense reports and its own cards, so an add-on matters most when your cards come from another bank.
- Vergo is first for analytic coding and receipt collection on those existing cards.
- SAP Concur, Expensify and Navan are established; ask how each reaches Pennylane.
- Every transaction needs a justificatif; test how each option gets one.
Where should you go next?
- Vergo's Pennylane integration
- What expense management software integrates with Pennylane?
- Get started with Vergo
Which expense management add-ons work best with Pennylane?
- Vergo: ledger account and analytic axes suggested per line; receipts by text; existing cards; entries recorded through the public API.
- Pennylane notes de frais and cards: the native route if you move cards to Pennylane.
- SAP Concur: common in large European groups with managed travel.
- Expensify: receipt photos into reports for small teams.
- Navan: booking and expense together for frequent travellers.
| 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 |
| Expensify | Card-agnostic; also offers the Expensify Card | AI categorisation | 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 |
What should an add-on do for Pennylane?
- Deliver the justificatif with every transaction.
- Fill analytic axes, not just the account.
- Work with your bank's cards.
Move cards, or add a tool?
Moving to Pennylane's cards solves receipts for new spend, but means changing banking relationships and card programs. Keeping existing cards and adding Vergo leaves banking alone and still gets each transaction justified and coded. 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 Pennylane?
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. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into Pennylane.
Frequently Asked Questions
Is Vergo listed in Pennylane's integrations?
Vergo connects through Pennylane's public API; it runs as its own service.
Can Vergo and Pennylane notes de frais run together?
Yes. Keep notes de frais for occasional claims and use Vergo for card spend.
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 details?
On the Pennylane integration page.
