Categorizing bank transactions in QuickBooks Online without creating cleanup

The short answer: categorization in QuickBooks Online is the act of assigning an account from your chart of accounts to each bank transaction in For Review, then adding it. Done carelessly it is also the single largest source of cleanup work later, because every wrong category is a posted entry someone has to find and reclassify. The method below is built to keep the second job from existing: categorize deliberately, automate only what's unambiguous, and fix posted mistakes in bulk rather than one by one.

Where categorization happens

1. For Review (Transactions → Bank transactions) is the queue of transactions the bank feed — or a .qbo upload — has delivered but you haven't posted. Each row gets an account (the category), optionally a customer/vendor and a memo, then Add. Or Match, if the transaction already exists in the books as an invoice payment, a bill payment or a transfer.
2. Categorized / Reviewed is where added transactions land. You can undo from here if a category was wrong and you catch it quickly.
3. Reclassify transactions (in the accountant tools, and in some plans directly) is the bulk fix for posted transactions: filter by account, date and vendor, select many, move them to the right account or class in one action.

A method that doesn't create cleanup

• Match before you add. A customer payment that already has an invoice, a bill that was already entered, a transfer whose other side is in the books — adding these creates duplicates and overstates income or expense. Look for the match first.
• Sort by description, categorize by cluster. Identical payees group together; decide the account once and apply it to the group. This is also how you notice a vendor that sometimes belongs in two accounts.
• Use the real chart of accounts. Vague catch-alls ("Miscellaneous", "Ask my accountant") are deferred decisions. Use them only as an explicit to-do, and clear them before month-end.
• Transfers are not income or expense. Card payments from the checking account, moves to savings, owner contributions — categorize these as transfers or equity, never as revenue or cost. This is the most common error we see in migrated and backlogged books.
• Split what needs splitting. A single payment covering two accounts (loan principal and interest, a purchase with sales tax you track separately) gets split lines, not the biggest bucket.

Bank rules: automate the boring, not the ambiguous

Rules match on description, amount and bank account and pre-fill (or automatically add) the category. They are excellent for the fixed set of vendors that never change — rent, payroll provider, the subscriptions — and dangerous for anything variable. A rule that automatically adds every "AMAZON" charge to Office Supplies will quietly file equipment, inventory and personal purchases the same way for a year. The safe defaults:

• Rules for fixed vendors can auto-add; rules for everything else should only suggest.
• Include an amount condition where the amount is genuinely fixed — it catches vendor changes.
• Review the rules list quarterly. Stale rules outlive the vendor relationships they were built for.

Reclassifying: fixing what's already posted

When you find a category error in posted transactions, the question is how many siblings it has. One or two: open the transaction and change the account. Dozens: use Reclassify — filter to the wrong account and date range, tick the affected rows, pick the correct account, apply. Before you do, run a Profit & Loss for the period and save it, so you can show what moved. And note that changing categories in a period that's already been reconciled doesn't break the reconciliation — reconciliation checks bank amounts, not accounts — but it does change the financial statements for that period, which matters if returns were filed on them.

Backlogs: when the transactions arrive as statements, not a feed

The feed covers roughly 90 days. A catch-up client hands you a year of PDFs. Those transactions have to be imported before they can be categorized, and the import route decides how much work the categorization is. A CSV import gives you rows with no accounts; a .qbo import lands in For Review with stable IDs but still no accounts. Our converter can assign accounts from the client's own chart of accounts during conversion — it reads a QuickBooks or Xero chart export, categorizes each row with a confidence score, and shows you only the rows it wasn't sure about. Confirmed choices are remembered per client, so the second statement needs fewer decisions than the first. The rows then go in through the normal .qbo upload, categories attached, and your job in For Review becomes a review rather than a data-entry pass.

Check the result

After a categorization session, two reports tell you whether it went well: the P&L by month (a category that spikes in one month and vanishes the next is usually a vendor split across two accounts) and the balance in any catch-all account, which should be zero. Then reconcile the statement — a two-sided reconciliation is the proof that everything the bank saw made it into the books, whatever account it landed in.