Back to Home
Business Operations
Learning your books from the bank feed is why your numbers are wrong
Cloud ledgers put entering and matching on the same screen, so self-taught owners double-enter without knowing it. Five checks that tell you whether anyone is actually reconciling.
13Labs Team25 July 20268 min read
bookkeepingbank reconciliationcloud accountingprocess designowner-operators
Contents
What does it mean to run your books from the bank feed, and why is it a problem?
Working from the bank feed means you categorise money as it lands and treat that screen as the record. It is not. The feed is a copy of your bank statement waiting to be matched against a ledger you are supposed to have built separately. Skip the ledger and you get duplicate invoices, duplicate bills and a reconciliation that balances over rubbish data.
Why are cloud ledgers harder to learn than the old desktop ones?
Desktop accounting software forced the two mental models apart. You entered invoices and bills into the ledger in one place. Then, separately, you imported or keyed a bank statement and ticked things off against what you had already entered. The sequence taught you the double-entry logic whether you wanted to learn it or not. Cloud ledgers fused both into one screen. The feed shows a transaction, offers a category, offers to create an invoice, offers to match. All four actions live on the same row. Nothing about the interface tells you that create and match are opposite operations, or that doing both to the same real-world payment records it twice. That fusion is the whole problem. The interface is easier to operate and harder to understand. A self-taught owner can be productive on day one and structurally wrong by month three, with no error message in between. A bookkeeper on r/Bookkeeping described the exact failure: “someone learns QBO starting from the bank feed, gets comfortable categorising everything that way, and then months later discovers their books are a mess because they were double-entering without realising it. Invoices created AND categorised from the feed. Bills entered AND posted from the feed. The bank rec technically balanced but the underlying data was chaos.” Note the last sentence. The reconciliation balanced. Balancing is not evidence of correctness. It only proves that the total you told the software matches the total the bank told the software.
How do I tell if anyone is actually reconciling my books?
Five checks. Ten minutes. You do not need to know debits from credits to run them, and you should run them yourself rather than asking whoever does the work. One, the date of the last completed reconciliation, found on the bank reconciliation summary report. Bad looks like anything more than one full month behind today. Two, the unreconciled or uncleared balance on that same report. Bad looks like a large figure, or one that includes items older than 90 days. Three, aged payables compared against supplier statements. Bad looks like bills you know you paid still sitting open. Four, duplicate revenue, found by sorting sales by customer and amount. Bad looks like two identical amounts on the same day from the same customer. Five, suspense and uncategorised accounts on the profit and loss. Bad looks like any meaningful balance sitting there at month end. Checks one and two catch the common failure. Marking a transaction reviewed in the feed is not reconciling. It clears the item off the screen. The period is only reconciled when someone runs the reconciliation for a date range, agrees the closing balance to the bank statement, and finishes it. Another post on r/Bookkeeping shows what the gap looks like from outside: “Well I log into their qb and the last bank rec was done in February. It is now November. Their bookkeeper has been marking everything as reviewed but definitely not reconciling anything. There's 17.3k in uncleared transactions and some of them are dating back to last year.” That is nine months of activity that nobody has agreed to a bank statement. Every management report drawn off it was fiction.
Why does the mess only surface at year end?
Because nothing in the daily workflow complains. Duplicate bills do not throw an error. An uncleared transaction from last year does not block you from processing today's. Your profit and loss still renders. It just renders the wrong number. Year end is the first point where someone outside the business has to sign off on the balance sheet, and the balance sheet is where duplication shows up. Two entries for one invoice inflate both revenue and receivables. A bill entered from the feed and again from the supplier's copy inflates both expense and payables. The bank balance still ties, so nobody looked. The owner's reaction in that same r/Bookkeeping thread is worth sitting with: “When I (super super politely) mentioned this to the owner she said that its 'fine' and taht their bookkeeper will clean it up before year end lol.” Cleanup at year end costs more than doing it right monthly, because the person cleaning it up is reconstructing decisions from memory that nobody wrote down. More to the point, you spent the year making decisions on numbers that were wrong. That cost does not appear on any invoice.
Do auto-coding suggestions actually save time?
Sometimes. Not always, and the honest answer depends on how varied your spending is at a given supplier. Auto-coding works on merchant name and amount patterns. Where a supplier means exactly one thing to your business every time, the suggestion is right and accepting it is fast. Where a supplier means several things, the suggestion is a coin flip you now have to check. Two posts on r/Bookkeeping make the point better than a vendor comparison would: “Edit: the bank feed suggestions are garbage though and the “AI” it tries to implement has me recategorizing 80% of the items” and “We do not like quick books because it was auto reconciling our transactions and making mistakes; for example, it would log all home depot purchases as materials when we end up buying lots of tools there.” The hardware store example is the general case. Materials are a cost of sale. Tools are often an asset or a different expense line. One merchant, two treatments, no way for a pattern-matcher to know which without the receipt. Trades businesses, cafes and anyone buying from general suppliers hit this constantly. The test to apply is simple. For a given supplier, if you accept the suggestion without opening the receipt, are you right? If yes, rule it. If no, the suggestion is costing you more to review than it would cost to code from the source document in the first place. Reviewing a wrong answer is slower than producing a right one, because you have to reconstruct the right answer anyway and then undo the wrong one. This is not an argument against rules. It is an argument for rules that are narrow. A rule for your landlord, your phone provider and your insurer will be right forever. A blanket rule for a hardware chain will be wrong most weeks.
What is the fix that does not mean hiring someone?
Change the order of operations, then keep it. Enter bills and invoices from the source document, not from the feed. The supplier's invoice is the record. The bank line is evidence that you paid it. Enter first, match second. Use the feed only to match. If a feed item has no existing entry to match to, that is a signal something did not get entered, not an invitation to create it there. Reconcile on a fixed date each month, to a statement, and finish the reconciliation properly so the report shows a completed date. Keep suspense accounts empty, because anything you could not code is a question for someone, not a resting place. That is a process, not a piece of software. Which is the wider point. Most of what people call an accounting problem is a sequencing problem, and sequencing problems do not get fixed by switching products. They get fixed by one person in the business understanding why the order matters and owning the monthly rhythm. That is the same skill taught in buildAutomation: map the process, find the step where the data actually gets created, and put the control there rather than downstream.
Frequently asked questions
**Is marking a transaction as reviewed the same as reconciling it?**
No. Reviewing accepts a category and clears the item from the feed screen. Reconciling agrees a full period of transactions to a closing balance on a bank statement and locks it. You can review every transaction for a year and never reconcile a single month.
**How often should a small business reconcile?**
Monthly, on a fixed date, against the statement for that month. Weekly is fine if cashflow is tight. The failure mode is not frequency, it is never finishing a period, which leaves old uncleared items accumulating where nobody reviews them.
**How do I know if I have double-entered invoices?**
Run a sales report by customer sorted by amount and look for identical amounts on the same or adjacent dates. Then check aged receivables for invoices you know were paid. Duplicates from the feed usually show as an open invoice sitting next to a matched payment.
**Should I turn off bank rules and auto-coding entirely?**
No. Keep rules for suppliers that always mean one thing, such as rent, insurance and telecommunications. Remove rules for general suppliers where you buy several categories of thing. The test is whether you can accept the suggestion without opening the receipt.
**My bank reconciliation balances. Are my books right?**
Not necessarily. Balancing proves your recorded bank movements match the bank's. It says nothing about whether an invoice was recorded twice, whether a cost went to the right account, or whether a payable is real. Balance sheet review is the check that catches those.
**Does switching accounting software fix this?**
Rarely. The duplication comes from the order in which entries are made, and that order follows you across products. Fix the sequence first. If you still want to switch afterwards, you will migrate clean data instead of carrying the mess across.
Sources
Quotes are reproduced verbatim from public posts on r/Bookkeeping and attributed to the subreddit, not to individuals. On learning from the feed and double-entering: https://www.reddit.com/r/Bookkeeping/comments/1r4xj78/hot_take_quickbooks_online_is_legitimately_harder/ On reviewed-but-not-reconciled and the year-end cleanup response: https://www.reddit.com/r/Bookkeeping/comments/1osz1bq/how_do_i_politely_tell_my_client_their_bookkeeper/ On auto-coding miscategorising a hardware supplier: https://www.reddit.com/r/Bookkeeping/comments/1tiyqum/downloading_qbo_data_advice_needed/ These are individual accounts from a bookkeeping community, not survey data, and the discussions are not specific to Australia. Treat them as a recurring complaint pattern rather than a measured frequency.
Fix the process, then keep it in-house
buildAutomation trains two or three of your own people to map the process, find where the data really gets created, and build the checks that keep it clean. No agency retainer. Tell us what your admin looks like and we will scope it with you.
Talk to us about buildAutomation