Fixing Cross-Posted QuickBooks Online Bank Feeds
When a bank connection posts checking transactions into a credit card account in QBO, learn how to stop the corrupted feed, clean up the data, and rebuild accuracy.
When a bank connection goes rogue in QuickBooks Online, it can quickly corrupt your client’s books. A common failure mode occurs when a single financial institution connection begins cross-posting data—for example, routing checking account transactions into a credit card register. This renders the bank feed unreliable for both accounts. If you encounter this, you need a structured plan to stop the bleeding, clean up the data, and restore accuracy.
Disconnect the Corrupted Feed
The immediate priority is to prevent further damage. As soon as you realize the financial institution’s connection is routing transactions to the wrong registers, disconnect the bank feed for the affected accounts in QuickBooks Online.
Do not simply exclude the unwanted transactions, as the underlying connection will continue to pull flawed data on the next sync. Severing the connection halts the automated import and gives you time to assess the scope of the cross-posting without the situation compounding.
Isolate and Rebuild the Affected Period
Once the automated feed is disabled, establish a reliable baseline. Download the official PDF statements directly from the bank for both the checking and credit card accounts covering the entire affected period.
Because the automated feed is compromised, you will need to rebuild the entries manually. Have the client review the statements and tag every transaction with the correct category, class, and project information in a spreadsheet. Once the data is reviewed and finalized, you can manually enter the transactions or upload them into QuickBooks Online using a properly formatted CSV file.
Clean Up the QBO Registers
Before uploading the newly reviewed transactions, you must clear out the garbage data the broken feed left behind. Review both account registers to identify the incorrectly posted items.
You will need to delete the individual transactions that were routed to the wrong account. Deleting is generally preferable to excluding in this scenario, as exclusions remain in the hidden exclusion list and can cause confusion later. Once the incorrect entries are deleted and the registers are clean, you can safely import your reconciled spreadsheet data.
Evaluate the Root Cause
Before attempting to reconnect the accounts, consider the underlying stability of the connection. Cross-posting between accounts usually indicates a failure in the bank’s application programming interface (API) or a mapping error on the aggregator’s end.
If the financial institution cannot guarantee that the mapping issue is permanently resolved, reconnecting the feed will likely reintroduce the same problem. In cases where the bank’s infrastructure remains suspect, manually importing CSV statements moving forward, or guiding the client toward a different financial institution entirely, is the safest path forward.