Cleaning Up Credit Card Feeds in QuickBooks Online (Without Doing It by Hand)

Every QuickBooks Online file with corporate cards on it has the same monthly ritual: open the banking screen, find a few hundred transactions in For review, and start clicking. This is a guide to shrinking that pile — first with the tools QuickBooks gives you, then by fixing the problem upstream.

What a card feed actually delivers

A bank feed is thinner than people expect. When you connect a bank or credit card, Intuit's documentation is explicit that transactions land in the For review tab and "won't affect your books until you match or categorize them."

What arrives is essentially a date, an amount, and a string of bank text. What doesn't arrive:

• The receipt. No feed carries one.
• The business purpose. "AMZN Mktp US*2K4LM" is not a memo.
• Class or location. The feed has no opinion about which job or entity the charge belongs to.
• Who spent it. A shared card number tells you nothing about the cardholder.

Every one of those gaps is filled by a human later. That's the work. Automating the categorization of a feed helps, but it never touches the other four columns — which is why teams who set up bank rules still find themselves in For review every month.

Tool 1: Bank rules, and where they stop

Bank rules are the strongest native lever, and they're more capable than most teams use. Per Intuit's bank rules documentation, you can create up to 2,000 rules, each with up to 5 conditions, matching on description, bank text, or amount using contains, doesn't contain, or is exactly. Rules can set transaction type, category, tags, and payee — and toggling auto-post means qualifying transactions are "automatically added" without manual review.

Used well, that clears the predictable tail: the same SaaS charge on the same day every month, the parking garage, the fuel stop.

Where rules stop is structural, not a limitation to work around. A rule keys off the text on the transaction. It can conclude "this merchant is usually software." It cannot conclude "this software charge belongs to the Denver office, on the Wilson job, and Priya approved it." Anything that varies by who spent it and why is out of reach, because none of that is in the string the bank sent.

So the practical rule about rules: automate the merchants that are always coded the same way, and don't try to encode judgment. A rule that's right 70% of the time is worse than no rule, because auto-post makes the 30% invisible until reconciliation.

Tool 2: Auto-matching, and why it misses

QuickBooks also tries to match feed transactions against records you've already entered. The matching documentation gives the exact window: QuickBooks suggests matches "for transactions with the same amount within a specific date range (90 days before to 20 days after the transaction date)."

Knowing those numbers explains most of the misses:

• A tip changed the amount. Match on exact amount fails on every restaurant charge that posts higher than the receipt.
• The record is older than 90 days. A deposit sitting since last quarter won't be suggested.
• It was already reconciled. Intuit's guidance is to exclude these, or you'll duplicate them.

None of that is a bug. It's the honest boundary of matching on amount and date, and it's why the entries that fall out are precisely the awkward ones you have to think about.

Tool 3: Class and location (check your plan first)

If you're tracking jobs, departments, or entities, class and location tracking are the QuickBooks equivalent of dimensions — and they're plan-gated: Plus and Advanced only, not Simple Start or Essentials. Turning them on costs nothing extra; you switch them on under Settings → Account and settings → Advanced → Categories.

Worth doing early. Retrofitting class onto nine months of posted transactions is a genuinely bad week.

The upstream fix

Here's the reframe that actually shrinks the pile: the feed is not where coding should happen. By the time a charge appears in For review, it's been stripped of everything except text and an amount, and you're reconstructing context from memory — which is why the work is slow and why it happens in a lump at month end.

Code it where the context still exists: at the card, close to the spend, while the person who swiped still remembers the dinner. Then QuickBooks receives transactions that are already categorized, already classed, already receipt-backed, and already approved — and For review becomes an exception queue instead of a to-do list.

Three things make that real, whatever tool you use:

1. Coding happens continuously, not monthly. Fifteen minutes on Friday beats an afternoon on the 3rd.
2. Receipts attach at the moment of spend — forwarded by email or captured on a phone — not chased in arrears.
3. Exceptions are surfaced, not searched for. Missing receipt, missing class, unusual amount: you want a queue, not a scroll.

Summit Spend does this by connecting the corporate cards you already have through Plaid — we don't issue cards — coding transactions against your chart of accounts, and exporting them to QuickBooks Online already complete. QuickBooks Online sync is included on our Starter plan at $10/user/month plus a $99/month platform fee ($500/year if you pay annually); AI auto-apply, automatic receipt matching, and multi-level approvals sit on Professional. If your card close is mostly a categorization chase, Starter is likely the plan you want, and you can request access to try it on your own cards.

But the principle stands with or without us: the cheapest way to clean up a credit card feed is to stop letting it arrive dirty.