Plaid integration
Connect your bank accounts through Plaid. Bunny imports deposits nightly, suggests the matching open invoice, and turns your approval into a posted payment — cash application without the bank statement.
What the integration does
Nightly deposit import
Connect one or more bank accounts and Bunny imports deposits every night — no CSV downloads from the bank portal.
Automatic invoice matching
Each deposit is matched against open invoices and Bunny suggests the most likely one, with the amount and customer already lined up.
You approve, Bunny posts
Approving a suggestion creates the manual payment against the invoice, so AR and the customer's balance update immediately.
Choose your start date
Set a synchronisation start date so you import the history you want and nothing older.
Card payments reconcile themselves. Bank transfers do not — and in B2B SaaS the bank transfers are the invoices that matter, because that is how enterprise customers pay a six-figure annual commitment.
The usual process is somebody downloading a statement, opening the AR ageing report, and matching amounts by eye. It is slow, it is done weekly rather than daily, and it means the ageing report is always a little bit wrong.
The Plaid integration removes the manual part without removing the control. Deposits arrive in Bunny each night, each one paired with the open invoice it most likely settles. You approve; the payment posts.
Why the approval step stays
Automatic matching is right most of the time and wrong in exactly the cases you would want to catch — a partial payment, a customer settling three invoices with one wire, a deposit that is not a customer payment at all. Suggesting rather than posting keeps those in front of a person.
Frequently asked questions
Which payments does this cover?
Does Bunny post payments automatically?
How often does it sync?
Can we connect more than one bank account?
Keep the stack you have
Bunny sits between your CRM, your tax engine, your payment processor and your ledger — so quoting, subscriptions, usage and invoicing share one system of record without anyone migrating off the tools they already use.