Richer data, no re-entry
Vendor names, memos, classes, projects, and COA mappings flow into Puzzle automatically. No re-categorizing, no blanks to fill.
Your money moves. Your books are already done.
Every transaction in Rho syncs to Puzzle automatically. Your books stay closed. You stay building. Banking and accounting, perfectly in sync. Always On.
What your books look like now
Every transaction type covered
Bill payments, reimbursements, treasury activity, internal transfers, refunds, and reversals. The full picture in one sync.
Set your rules once. They carry over.
Auto-categorization, enrichment, and sync rules carry over from Rho into Puzzle. No duplicate setup, no cleanup.
No more accounting busywork
Rho and Puzzle now connect directly. No Plaid in between, no stripped data, no gaps in your books.
Every transaction syncs with vendor names, memos, classes, and projects attached
Full coverage: banking, cards, bill pay, treasury, reimbursements, and refunds
Rho's accounting automations work natively with the direct integration
Accrual events post as journal entries, cash events post as transactions
Chart of accounts mappings carry over so nothing needs re-categorizing
Your books before and after the integration
Most startups connect their banking platform to their GL through Plaid. Rho connects directly to Puzzle, so your books actually match your money.
_
The direct integration
Every transaction syncs with full context. Vendor names, classes, journal entries, and COA mappings land in Puzzle automatically. You close the books because they're already done.
_
The Plaid workaround
Stripped metadata, missing transaction types, broken automations. You close the books by filling in what Plaid couldn't pass through.
FAQs
Puzzle Integration
Plaid strips out transaction metadata, limits which transaction types sync, and disables Rho's accounting automations. The direct integration fixes all three. You get full metadata (vendor names, memos, classes, projects, COA mappings), every transaction type (banking, cards, bill pay, treasury, reimbursements, refunds), and Rho's auto-categorization and sync rules working natively with Puzzle.
Everything. ACH, wires, internal and external transfers, card expenses, bill payments, reimbursements, treasury activity (interest, dividends, unrealized gains/losses, fees), and refunds and reversals. Accrual events like reimbursement creation post as journal entries. Cash events like disbursements post as transactions.
Mercury's integration is read-only. Brex covers cards and reimbursements but doesn't manage the full bill lifecycle. Ramp is a spend platform, not a bank, so you still need a separate banking integration for complete books. Rho covers banking, corporate cards, bill pay, treasury, and reimbursements in a single platform with a single integration. One connection, complete books.
We guide the transition so there are no duplicate transactions or disruptions. The onboarding process includes managing your existing Plaid connection and migrating you to the direct integration cleanly.
Early access is available now through the waitlist. Full availability rolls out in April 2026.
Puzzle doesn't currently support multi-entity natively. If you're consolidating across entities, Puzzle recommends using their "Join" feature. The Rho integration works within Puzzle's current entity structure.
We’re ready
when you are.
