Your bank feed is not a nice-to-have integration. It's the whole job. Every transaction starts here. The charge lands in your feed first. Everything after that (categorized reports, a clean P&L, a close that actually closes) depends on what happens to it next.
Most people treat the feed like plumbing. It's not. Bank feed bookkeeping is the queue you work every day. How well you clear it decides whether your books are current or three weeks behind.
What is a bank feed?
A bank feed is the automatic import of bank and card transactions into your ledger for categorization and matching. Your bank connects to your accounting software. Transactions flow in daily. Each one needs a category, and when it pairs with an invoice or bill, a match. The feed itself isn't the work. Clearing it is.
- The feed is the job, not a step in it - every transaction you'll ever categorize enters through here first.
- Three states, one goal - uncategorized, categorized/for review, and matched and reconciled; a transaction isn't done until it hits the third.
- Automation gets you most of the way - roughly 85% of transactions categorize correctly on first import, and QBO's own feed rules clear about half of what lands.
- The rest is real work - clicking categorize 500 times a day is what happens when nobody triages the exceptions early.
- Feeds break in predictable ways - stale connections, duplicate imports, and lump-sum deposits are the three repeat offenders.
- A broken feed compounds - a week of unattended feed items becomes a month of unreliable financials fast.
Uncategorized. The transaction just landed. Your software has a guess (based on the payee, the amount, or history), but nothing's confirmed. This is the inbox — and the longer it sits, the harder it is to remember what a $340 charge from three weeks ago actually was.
Categorized, for review. Someone, or a rule, assigned an account. It's not wrong exactly. But it hasn't been checked against source documents or matched to anything else in the books. A rule can categorize fast and still categorize wrong. This state exists as a checkpoint, not a finish line.
Matched and reconciled. The transaction is tied to its source: an invoice, a bill, or a bank statement line. The numbers agree. This is the only state where the transaction stops needing anyone's attention.
Skip the middle state enough times and you get books that look done but aren't. "Categorized" and "correct" quietly stop meaning the same thing.
Categorizes the routine. Flags what needs you.
See Growthy on a sample book. Read-only bank access.
Get startedStale connections. Banks rotate credentials and change login rules often. A lapsed connection stops pulling new transactions quietly. No alarm goes off.
Duplicate imports. A manual CSV import layered on top of a live feed connection double-counts the same transactions. Finding and voiding the duplicates takes longer than importing correctly the first time would have.
Lump-sum deposits. Stripe and Square batch dozens of sales into one deposit. The feed shows one number. The ledger needs several. Matching that single line to the right invoices is where feeds stop being easy.
None of these are exotic failures. They're the three things that happen to almost every set of books eventually. That's why bank feed reconciliation is worth learning on purpose, not discovering by accident.
The uncategorized state above isn't neutral either. Leave enough uncategorized expenses sitting in the feed and your P&L understates real spend for as long as they sit there.
A bank feed that imports transactions but never gets worked isn't automation. It's a pile. The value only shows up when uncategorized becomes categorized becomes matched, every day, before the pile gets big enough to dread opening.
Transaction categorization built around the exceptions, not the easy 85%, keeps that pile from forming. Get started with Growthy and clear your feed before it clears you.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice.
