Key takeaways
- Certinia already has PSA expense reports, so an add-on should earn its place on company card spend.
- Vergo ranks first for GLA, dimension and project coding by inference on existing cards.
- SAP Concur, Expensify and Emburse are established; confirm how each reaches Certinia's ledger.
- Check dimension support first: Certinia analyses expense lines by up to four dimensions.
Where should you go next?
- Vergo's Certinia integration
- What expense management software integrates with Certinia?
- Get started with Vergo
Which expense management add-ons work best with Certinia?
- Vergo: GLA, Dimensions 1–4 and project by inference; text receipts; existing cards; cash entries and purchase invoices through the API.
- Certinia PSA expense reports: native claims per resource and project.
- SAP Concur: an enterprise T&E suite many large consultancies standardise on.
- Expensify: scans receipts into reports without a card change.
- Emburse: keeps an existing Amex, Mastercard or Visa program in place.
| Option | Cards | How coding is proposed | Route into Certinia |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own Certinia structure and history, with the reason shown | Cash entries and purchase invoices through the public API |
| SAP Concur | Existing cards through bank card feeds | Categorisation from merchant and transaction data | Ask how entries reach Certinia |
| Expensify | Card-agnostic; also offers the Expensify Card | AI categorisation | Ask how entries reach Certinia |
| Emburse | Existing Amex, Mastercard or Visa programs, or Emburse Cards | AI categorisation | Ask how entries reach Certinia |
What should an add-on do for Certinia?
- Code all four dimensions, not only the GLA.
- Know the project for client-billable spend.
- Record in Financial Management without a CSV step.
- Leave PSA intact for consultants who claim there.
Why card spend, not reports?
PSA handles out-of-pocket claims tied to an assignment. The remaining work is company card spend: subscriptions, travel booked centrally, client purchases. That is where statement coding eats finance time, and where Vergo proposes each value with the reason shown. 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 Certinia?
Vergo connects through Certinia's public API, reads your general ledger accounts and dimensions, and records coded card spend as cash entries or purchase invoices, with reimbursements as purchase invoices to the employee as vendor. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into Certinia.
Frequently Asked Questions
Is Vergo a Salesforce AppExchange app?
No. It runs outside your Salesforce org and connects through Certinia's public API.
Can Vergo run alongside PSA expense reports?
Yes. Many services firms keep PSA for consultant 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 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 Certinia integration page.
