Working the Bank Feed: How to Categorize Transactions Without Drowning in Them

The feed is only as good as the review

Connecting your bank account to your books is the single biggest time-saver in modern bookkeeping. Instead of typing transactions off a PDF statement, every charge, deposit, and transfer flows in on its own. But a bank feed doesn't do your books for you — it delivers raw transactions that still have to be categorized, matched, or ignored before they mean anything. The owners who get value from the feed are the ones who work the queue; the ones who let it pile up end up with hundreds of uncategorized lines and a reconciliation that won't tie. This guide is about doing it right. (General education, not accounting advice.)

What "categorizing" a transaction actually means

When a transaction lands from the feed, you're deciding one thing: what account does this belong to in my books? A coffee-shop charge is an expense — but to which category? A deposit might be a customer paying an invoice, a refund, an owner contribution, or a transfer from savings. Categorizing means assigning each line to the right account in your chart of accounts so it shows up correctly on your profit & loss and balance sheet.

The reason this matters beyond tidiness: a miscategorized transaction is a wrong number on a report you'll later use to price work, file taxes, or judge whether the month was profitable. Dump everything into "Miscellaneous" and your expense categorization is worthless. Tag a customer payment as income a second time when the invoice already recorded it, and you've double-counted revenue.

Match versus convert: the decision behind every line

Most bank-feed transactions fall into one of two buckets, and knowing which is which is the core skill:

• Match — the transaction is already in your books, and the feed is just confirming it cleared. A customer pays a one-thousand-dollar invoice; you already recorded the invoice and maybe even the payment, so the bank deposit should be matched to that existing record, not entered again. Matching is how you avoid double-counting. The feed line and the book entry are two views of the same event.
• Convert — the transaction is new to your books. You bought supplies on the debit card and never recorded it anywhere; the feed is the first time this expense appears. Here you convert the line into a categorized expense (or income), creating the book entry from the bank data in one step.

The discipline is simple: before you categorize anything, ask "is this already in my books?" If yes, match it. If no, convert it. Getting that fork right is what keeps your feed-driven books honest — it's the same logic behind why your books don't match the bank when undeposited funds aren't handled.

A third option: ignore

Not every line is a business transaction. An owner transfer between two linked business accounts shows up twice — once as money leaving one account, once as money arriving in the other — and recording both as expense and income would be nonsense. A reimbursed personal charge you've already handled elsewhere, or a duplicate from a re-sync, also doesn't belong. For these, the right move is to ignore the line so it drops out of the review queue without polluting your P&L. Ignore is not "delete and hope" — it's an explicit decision that this line needs no book entry, and a good system keeps a record that you made it.

The habit that keeps the queue at zero

The single biggest lever isn't which category you pick — it's how often you look. A bank feed reviewed every Friday is a ten-minute task: a dozen or two fresh lines, each an easy match or convert. The same feed left for a month is a reconstruction project where you're squinting at a charge from three weeks ago trying to remember what it was for.

Pick a cadence — weekly is ideal, never longer than monthly — and work the queue to zero each time. When you do, month-end close stops being a scramble: the transactions are already categorized, the accounts already reconcile, and "closing the month" is a review rather than a rebuild. This is the same frequency discipline that turns a fifteen-day close into a five-day one.

Fitting it into reconciliation

Categorizing the feed and reconciling the account are two halves of the same loop. Categorization gets each transaction into the right account; reconciliation proves that what your books say about the account ties, to the penny, to what the bank says. Work the feed regularly and reconciliation becomes a formality — there's nothing left to chase because every line already has a home.

Hosting Books connects each bank and card through Plaid and brings new or changed transactions in automatically, then drops every one into a review queue with three states — unreviewed, reconciled, and ignored. For each line you can match it to an existing expense or invoice with amount-and-date suggestions, or convert it to a categorized expense in one step, and the dashboard nudges you when items are waiting — so "work the unreviewed list to zero" stays a quick weekly habit instead of a month-end emergency.

This article is general educational information about accounting concepts and is not accounting advice for your specific situation.