Key takeaways
- Puzzle expects receipts to come from a spend tool.
- Vergo is first when you keep your bank's cards.
- Brex and Ramp have Puzzle integrations that carry receipts and mapped fields.
- Puzzle lists Bill.com under expense management.
Where should you go next?
- Vergo's Puzzle integration
- What expense management software integrates with Puzzle?
- Get started with Vergo
Which expense management add-ons work best with Puzzle?
- Vergo: receipts by text on any card; category, class and department suggested; entries posted through the API.
- Brex: receipt references and custom fields travel into Puzzle, on Brex cards.
- Ramp: card transactions, reimbursements and bill pay flow into Puzzle, on Ramp cards.
- BILL: payables, listed by Puzzle under expense management.
| Option | Cards | How coding is proposed | Route into Puzzle |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own Puzzle structure and history, with the reason shown | Transactions and journal entries posted through the public API; reimbursement bills prepared for it |
| Brex | Brex Mastercard corporate cards | AI expense management built into the card | Puzzle lists a Brex integration |
| Ramp | Ramp Visa corporate card | Auto-coding trained on customer transaction patterns | Puzzle lists a Ramp integration |
| BILL | BILL's own corporate card | BILL AI auto-categorisation | Puzzle lists Bill.com under expense management |
What should a Puzzle add-on do?
- Deliver receipts with every charge.
- Code classes and departments if you use them.
- Reduce review items, not add a second inbox.
Keep your bank, or switch cards?
Startups often open a Brex or Ramp account early. Others keep cards at the bank that holds their venture debt or deposits. For them, a card-agnostic add-on gets receipts and coding without moving money. 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 Puzzle?
Vergo connects through Puzzle's public API, reads your financial accounts, and posts coded card spend as transactions or journal entries through Puzzle's API, with reimbursements posted as bills to the employee through the same API. Coding is proposed as the charge happens, ahead of the bank sync.
Frequently Asked Questions
Is Vergo on Puzzle's integration list?
Vergo connects through Puzzle's public API as its own service.
Can Vergo work with a fractional accountant?
Yes. Reviewers see each proposal and the reason, and confirm.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
Does Vergo handle bills?
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 Puzzle integration page.
