Expense management that works with Elite 3E

Key takeaways

• Vergo reads clients and matters from Elite 3E, codes expenses to the correct client and matter, and pushes coded entries back so nothing arrives as an uncoded lump at month end.
• You do not need to change cards — Vergo connects to the corporate cards, fuel cards and personal cards your business already holds.
• Card spend, employee reimbursements and AP invoices all run through the same coding model and sync to Elite 3E the same way.
• Transactions are ready to code the moment they happen, not after they clear.

How the Elite 3E sync works

Vergo reads your clients and matters from Elite 3E, codes every expense to the right client and matter, and pushes coded entries back into the system. This means expenses arrive already coded, not as an uncoded lump at month end that someone must allocate by hand. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into Elite 3E. The structure that matters here is clients and matters: every transaction gets mapped to the right place in your existing project hierarchy without manual intervention at the point of reconciliation.

Do you have to change cards?

No. Vergo does not issue cards and never asks you to switch. It connects to the cards your business already holds — corporate cards, fuel cards, personal cards used for reimbursement — and connecting your existing cards involves no card applications, no re-issuing and no banking change. This matters for firms that have negotiated terms with existing card providers or that have employees already enrolled in a particular programme. The connection layer is card-agnostic: Vergo reads transaction feeds from whatever issuer you use, codes the expenses, and syncs the coded results to Elite 3E. The card itself stays exactly where it is.

Who runs Elite 3E?

Elite 3E, from Thomson Reuters, is run by large organisations in legal services. Law firms and corporate legal departments use it to manage time, billing and matter accounting at scale. Vergo reads the client and matter structure these firms already maintain, codes transactions to that structure without requiring a parallel rules library, and syncs coded entries back so the general ledger and matter ledger stay consistent. The expense system becomes a feed into Elite 3E, not a separate reconciliation exercise.

Do reimbursements and AP invoices work with Elite 3E too?

Yes. The same coding model handles card spend, employee reimbursements and AP invoices, and all three sync to Elite 3E the same way. Most tools treat these as separate products with separate coding setups; when the same vendor is coded two different ways, you inherit a reconciliation problem. Vergo captures, codes and syncs invoices to Elite 3E — payment itself stays on the rails you already use, whether that is check runs, ACH batches or another method. Reimbursements work the same way: an employee submits an expense, Vergo codes it to the right client and matter, and the coded transaction syncs once approved.

A practical example

A partner flies to meet a client, pays for the flight on a corporate card, submits a taxi receipt for reimbursement, and approves an expert-witness invoice for the same matter. In a traditional system, each of those might be coded separately — the card transaction in one tool, the reimbursement in another, the invoice in a third — and reconciled by hand at month end. In Vergo, all three are coded to the same client and matter by the same inference model, reviewed in the same queue, and synced to Elite 3E as separate line items already tied to the correct billing code. The finance team sees one reconciliation, not three.

How Vergo handles this

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. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into Elite 3E. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. 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. Connecting your existing cards involves no card applications, no re-issuing and no banking change.