Integrations
Connected where it counts.
Bokeping doesn’t collect integrations for the logo wall. It connects deeply to the few things your books depend on — your bank, your payments, and your history.
Bank Feeds · via Plaid
Your bank, connected once
Bokeping connects to thousands of US banks and card accounts through Plaid. The connection is read-only and encrypted — your credentials never touch Bokeping, and Bokeping can never move your money.
- Thousands of US banks and credit cards
- Read-only: view transactions, never move money
- Credentials stay with Plaid, encrypted end to end
- Disconnect any time without losing history
Online Payments
A pay button on every invoice
Let customers pay by card or bank transfer straight from the invoice. The payment posts itself, the invoice closes itself, and the receipt sends itself — you just watch the balance change.
- Card and bank payments on invoices
- Payments post to the books automatically
- Fees categorized, not mystery-subtracted
- Receipts sent without you touching anything
CSV & QBO Import
Moving in is a file drop
Bring customers, vendors, items, invoices, bills, and bank history from spreadsheets or QuickBooks. The importer maps your columns, flags what it’s unsure about, and reports every row it touched.
- CSV import for anything tabular
- QBO import for QuickBooks history
- Duplicates detected, not duplicated
- A full report of what landed where
Our approach
How we think about integrations
Most accounting tools measure integrations by the length of the logo wall. We measure them by what happens to your ledger. A connection that drops half-labeled transactions into your books creates work; one that arrives named, matched, and deduplicated removes it. So every integration we ship has to meet the same bar as a feature: the numbers it writes must trace to balanced entries, and the failure modes must be boring.
That’s why the list above is short and the depth is real. Bank feeds don’t just import — they match, learn, and reconcile. Payments don’t just process — they post, close the invoice, and file the fee. Import doesn’t just load rows — it reports every one it touched. When we add the next name to this page, it will work the same way.
All connections
What’s live, what’s next
We’d rather ship a short honest list than a long aspirational one. Planned means planned — not “someday.”
Plaid
LiveBank & card feeds
Stripe
LiveOnline invoice payments
CSV import
LiveSpreadsheet data, in bulk
QBO import
LiveQuickBooks history
Developer API
LiveYour books, programmable
Gusto
PlannedPayroll into the books
Avalara
PlannedAutomated tax rates
Zapier
PlannedEverything else
FAQs
Fair questions
No. There’s no per-integration fee: bank feeds come with Starter and up, CSV import is on every plan including the trial, and the developer API and its keys are available on every paid plan. When a customer pays an invoice online, the card processing fee belongs to the payment processor — Bokeping shows it plainly and books it as a fee, never buried in the total.
Use CSV import. Export transactions from your online banking, drop the file in, and they land in the same review flow with the same duplicate screening. Your books can’t tell the difference — the feed just saves you the export step.
Yes, and please do. The planned list — Gusto, Avalara, Zapier — is shaped by exactly these requests. Tell us what your business runs on and we’ll tell you honestly whether it’s coming, and roughly when.
Everything already in your books stays there. A connection is a pipe, not a warehouse — disconnecting stops new transactions from arriving, but your history, categorization, and reconciliations are untouched. Reconnect any time and the feed picks up where it left off.
Missing a connection you need?
Tell us what your business runs on — the planned list above is shaped by exactly these emails.
Ready to know your money?
We’re ready when you are. Free to start, up and running in minutes.