Bookkeeping · Tools & Practice · Brief · Working level
Bank-feed hygiene: feeds are suggestions, not bookkeeping
Bank feeds import data; they do not keep books. Treat every feed transaction as a suggestion pending review, keep categorization rules few and specific, and reconcile to the statement — the feed is not the statement.
Bank feeds are the best and most dangerous thing to happen to small-business bookkeeping. Best, because typing transactions from paper statements is over. Dangerous, because a feed looks like bookkeeping while being nothing of the kind: it is an unverified data stream that drops items, duplicates items, and guesses at categories. The entire discipline reduces to one sentence — the feed is a suggestion; the statement is the truth — and three habits that enforce it.
Rules discipline
Categorization rules automate the boring correctly — until they automate an error forever. Keep them on a leash:
- Write rules only for exact, recurring payees with a stable category: the landlord, the software subscription, the loan payment.
- Never key a rule on a fragment that could match strangers ("AMZN" matches half the internet's descriptors).
- Set rules to suggest, not silently post. You still click; you just click fast.
- Audit the rule list quarterly. Delete anything you cannot explain.
- For loan payments, remember no rule can split principal from interest correctly over time — post those deliberately, because the split changes every month.
| Account | Debit | Credit |
|---|---|---|
| Loan payable | 612 | |
| Interest expense | 238 | |
| Cash | 850 |
The feed shows an $850 withdrawal. The books need the split — and the split shifts monthly as the balance amortizes.
Duplicate risk
Duplicates are the feed's signature failure, and they arrive from predictable directions: a reconnected feed re-importing history; a manually entered invoice payment and its feed twin both posting; transfers between two connected accounts appearing once from each side. The symptoms are inflated income or doubled expenses that "look plausible."
The defenses: match feed items to existing ledger entries instead of adding blindly; post transfers as transfers (one entry moving money between two accounts, not two deposits); and after any feed reconnection, check the overlap window transaction by transaction before accepting anything.
The review habit
Feed hygiene is a cadence, not a cleanup:
- Weekly (or twice weekly at volume): open the feed queue, match or categorize every item, question anything unfamiliar. A short queue is reviewable; a 400-item January queue gets rubber-stamped.
- Monthly: reconcile every account to the bank's statement — the PDF or paper from the bank, not the feed's running balance. Ending balance must tie exactly. This is the same statement the owner independently eyeballs in the ten-minute owner check.
- Monthly: clear the exceptions. Uncleared checks, unmatched items, and "ask the client" transactions go on the question list in your monthly client note — not into a suspense account to die.
Why this is worth the twenty minutes
Everything downstream rests on it. The financials are only as true as the feed review; the year-end package in working with the tax accountant is only clean if the twelve reconciliations behind it are real; and the record-keeping standard in Publication 583 assumes your books actually reflect the bank activity. Feeds changed where the data comes from. They changed nothing about whose job it is to make the data true.
Frequently asked questions
- Why do books still need reconciling if bank feeds import everything?
- Because feeds drop transactions, duplicate them, and mislabel them. A feed is a data connection, not a statement — connections break silently, refresh windows miss items, and auto-matching pairs the wrong records. Reconciling to the bank's actual statement is the only proof the ledger is complete. A feed-fed ledger that has never been reconciled is unverified data entry.
- Should I use automatic categorization rules for bank transactions?
- Yes, but only narrow ones: exact payee, predictable amount, one category — rent, software subscriptions, loan payments. Avoid broad rules keyed on partial descriptions, and never let rules auto-add transactions without review. Every rule is a decision you stop looking at; keep the list short enough to audit in five minutes.