QuickBooks lied to me three times in one import

// build log · field notes · the "it did WHAT" edition

ErnieCard's loaded. Eighteen charges, one refund, no bank feed so I built the CSV by hand. Zero errors, son.

ErnieCheck my work, dude! Green checkmarks all the way down — I'm not complaining.

I counted.

It was worse than an error message. QuickBooks doesn't fail loud — it fails polite. Three times, one import.

Lie #1 — it flipped every charge into a payment

My spreadsheet had two money columns: charges and payments. That's how the statement looks.

QuickBooks only has one slot for money. Hand it two columns and it grabs one, ignores the other, and... never mentions it. All eighteen charges landed as payments. The card had an excellent month.

The fix is super dumb: one money column, charges negative. QuickBooks even tells you this — on the screen after you've mapped the columns.

You don't have to suck it and redo it by hand, either. Select everything, undo, exclude, re-import. Ten minutes. Back to fucking off.

The next day I remembered the rule backwards and argued with my own notes about it. Ed wouldn't budge, so we settled it with three rows on the smallest card. Notes were right. House rule: a disagreement about how a tool behaves gets settled by a test, not by who said it louder.

Lie #2 — it dropped a row and said nothing

One refund in the batch. Partial, so the charge column was blank. Whatever — it's a refund, not a charge.

QuickBooks looked at the blank and just... fucked off to do something else. No "1 row skipped." No yellow triangle. Seventeen rows went in, and that lying weasel told me eighteen went just fine.

I only found it because the total didn't tie. That's the whole detection system.

This is the scary one. A flipped sign you'll catch — the card looks weird, you go look. A vanished row is just... vanished. Nothing looks weird. Adios, Bart. The only way to catch it is to count what went in against what you handed it, every time, like a paranoid person.

Dude. Be a paranoid person.

Lie #3 — the reconcile screen pre-checked stuff that wasn't on the statement

QuickBooks thinks it's better than you. Open the reconcile screen and there's a bunch of shit already checked that's nowhere on the statement — anything dated before the statement end, including eight charges the card doesn't bill until next cycle. Looks like a real break. A couple thousand bucks of real break.

So first I unchecked everything like a savage and went down the statement line by line. Eleven transactions in, just before the eye twitch, my brain came online: "Just count, dipshit."

Sixty-three things checked, fifty-five lines on the statement. Eight extras. Added them up: the difference, to the penny.

Counts tell you where. Dollars only tell you whether.

What I do now

• One money column. Charges negative. No exceptions.
• Count what went in against what I handed it, before I look at a single dollar.
• Smallest card first, so the cheap test happens before the expensive mistake.
• Never trust a green checkmark I didn't earn.

AI can do some wicked cool shit with ones and zeros. But cleanup work isn't just numbers. It's human hacks earned through painful hours of red, itchy eyes — hacks that worked for years before robots started doing it faster, more efficiently, and spectacularly fucking wrong while telling you "just the tip" with a straight face.

No amount of ones and zeros will figure out why a Home Depot receipt is categorized as Legal Services. An LLM can't predict that Barbara in Accounts Payable doesn't give a shit, so she types three letters and picks whatever comes up first. Barbara will never be AI's problem. Some sad sack human has to deal with her.

If that's what job security means in 2026, send me all the Barbaras.

Got something that needs to be cleaned the fuck up? Don't know where to start? Maybe I can help. HMU.