The Bank Feed Broke on Friday: A Case Study in Single Points of Failure
When the bank feed fails, you fly blind. We map out why single-pipe setups are dangerous and how to build a resilient manual backup for cash visibility.
“Connection Lost” is Not an Excuse
I refuse to tell a CEO “I don’t know how much money we have because the software is broken.”
That is an admission of incompetence. The software is a tool, not the master. If the hammer breaks, you use a rock. You do not stop building the house.
Yet, most SMB finance stacks are built on Single Points of Failure (SPOF).
- One Bank Account.
- One Bank Feed Aggregator.
- One Person who knows the password.
Last month, a major feed aggregator had an outage. For 4 days, thousands of companies saw zero transactions. They missed customer payments. They bounced direct debits because they thought they had funds they didn’t have.
The Leak: The “Set and Forget” Coma
We get lazy. Automation feels like magic, so we stop learning how the trick works. When the feed works, we sleep. When the feed breaks, we panic.
The leak here is Information Continuity. If you lose visibility for 48 hours during month-end close, you miss the deadline. You miss the reporting cycle. You look amateurish to investors.
Worse, you might make cash decisions based on stale data. “Oh, the dashboard says we have €50k.” No, the dashboard said you had €50k three days ago. Today, you might be overdrawn.
[TO EDITOR: Diagram of a pipe system. Pipe A is “Automated API” (Broken/Leaking). Pipe B is “Manual Bypass” (Valve closed). Caption: “Open the bypass valve when the main line fails.”]
The Plug: The Manual Override Protocol
We need resilience. Resilience costs nothing but discipline.
1. The “Plan B” Import Every Finance Manager must know how to manually import a bank statement.
- Step 1: Log into the bank directly.
- Step 2: Download the
.MT940or.CSVfile for the missing dates. - Step 3: Upload to Xero/QuickBooks/Exact.
- Step 4: Map the columns.
Test this today. If you don’t know how to map the columns, learn. Do not learn this while the house is on fire.
2. The Morning “Pulse Check” Do not trust the green light. Every morning at 09:00, check the “Last Synced” timestamp.
- < 24 hours: Green.
- > 24 hours: Yellow. Investigate.
- > 48 hours: Red. Activate manual import.
3. Redundant Banking Never keep 100% of your cash in one institution. If the bank’s entire interface goes down (it happens), you need a secondary account to fund payroll.
Summary
Technology fails. It is a question of “when,” not “if.”
Your job is to ensure that when the technology fails, the finance function continues. Meten is weten. Monitor the connection. Keep the manual import instructions on your desk.
FAQs
How often do bank feeds actually break?
More often than they admit. APIs change, tokens expire, aggregators (like Plaid/Yodlee) have outages. Expect 95% uptime, not 100%.
What is the backup plan?
The old school way. MT940 or CSV export from the bank, manually imported into the accounting tool. It is ugly, but it works.
Should we use multiple banks?
Yes. Always have a secondary operating account. If Bank A goes dark, Bank B can still pay the bills.