Bank connectivity is the highest-emotion module in small-business accounting. When it works, nobody talks about it. When it breaks — missing transactions, duplicated lines, stale balances — it erodes trust in the entire ledger. The fix is not blind faith in a provider; it is two paths to the same truth: a live feed when economical, and a boring CSV import when the feed lies.
Why feeds fail in the wild
- Institutional maintenance windows and MFA churn break aggregation unexpectedly.
- Pending vs posted timing creates “ghost” balances if users reconcile too early.
- Corporate cards and sub-accounts look like separate universes unless mapping is disciplined.
CSV as operational backbone
A CSV import path is not retrograde — it is operational insurance. Your rules engine (vendor → expense category, memo patterns, splits) should run identically whether the row arrived from a feed or a download. That symmetry is what lets you close on a bad connectivity week without heroic manual entry.
How Privbooks prices this honestly
Privbooks keeps CSV import on the free tier and places live Plaid on paid tiers where per-connection vendor costs are real. The product goal is simple: never trap you on a single brittle pipe.