Every behind-on-the-books story starts the same way: a busy quarter, then two, then a tax deadline or a loan application that suddenly needs real financial statements, and a QuickBooks file with eight months of uncategorized transactions staring back at you.
The standard fixes are to hire it out (cleanup services typically charge $500 to $1,500 for a few months behind, and $2,000 to $13,000 for multi-year rescues, taking one to eight weeks) or to lose a string of weekends to it yourself. This guide covers the third option that exists now: an AI agent does the reading, matching, and data entry inside your own QuickBooks file, and you make the judgment calls it escalates. Same books at the end, a fraction of the cost, and your evenings mostly intact.
Cleanup vs. Catch-Up: Know Which One You Need
The terms get used interchangeably, but they're different jobs:
- Catch-up fills the gap: months where transactions were never recorded or categorized at all.
- Cleanup fixes what's wrong: miscategorized expenses, duplicate entries, unreconciled accounts, AR that was collected but never applied, AP that was paid but still shows open.
Most neglected files need both, in that order for the existing months: fix the errors first so the catch-up work lands on a sound foundation. Intuit's own cleanup checklist is a solid map of the territory; what follows is how the same steps run when an AI agent is doing the labor.
Before You Start
Two-step setup if you haven't already: create a DeepLedger account, connect your QuickBooks Online company through Intuit's official OAuth flow, then connect Claude, ChatGPT, or another AI client to the DeepLedger server. First month free, which conveniently is cleanup month.
Then gather what you have: bank and credit card statements covering the gap (or better, connect the live bank feed and import CSV or Excel exports for the older months), plus whatever receipts and invoices exist. Don't wait for a complete document pile; missing paper gets flagged, not guessed at.
Step 1: Get a Diagnosis, Not a Vibe
Start by asking the agent for the damage report:
"Review the state of this company's books through last month. How many uncategorized transactions per month? Which accounts haven't been reconciled, since when? Anything odd in AR and AP aging? Duplicate vendors or accounts? Give it to me month by month."
The agent reads the reports and transaction history and comes back with the actual shape of the problem: which months are merely unrecorded versus actively wrong, where balances stopped matching the bank, which vendors exist three times with three spellings. Ten minutes in, you know whether you're doing a catch-up, a cleanup, or the usual both, and you have a work plan ordered month by month.
Step 2: Feed It the Missing Months
Connect the bank feed for current data, and import statements (CSV or Excel) for the months before the connection. Upload the receipts and invoices you collected to the documents page so the agent can read them and attach them to the transactions they support.
Everything the agent records from here carries a recorded marker, so a transaction that comes in twice (once from an import, once from the feed) can't be booked twice. Duplicate detection is built into the recording tools, not left to model memory.
Step 3: Categorize in Passes, Oldest Month First
Now the actual work:
"Work January: categorize what you can defend from QuickBooks history and my policies, record the clear items, and escalate anything you're not sure about with your reasoning."
The agent checks each transaction against your existing history (how was this vendor coded before?), records the clear items with a written rationale, and turns the ambiguous ones into tasks: proposed category, confidence, evidence, reasoning. You work the task list in the portal: approve in bulk, correct the wrong ones, reject the noise.
Here's what makes the pass structure matter: every correction is written to the agent's memory as policy. January might escalate forty items. By April, the vendors you corrected in January are coded by rule, not by guess, and the escalation list shrinks accordingly. The cleanup literally accelerates as it goes, which is precisely the property a months-long backlog needs.
Step 4: Fix the Structural Mess
With transactions landing correctly, aim the agent at the file itself:
- Master data: standardize the three spellings of the same vendor on one name, deactivate the duplicates, and fix the miscategorized accounts.
- Reclassifications: wrong-account history gets corrected with journal entries the agent drafts and explains, and you approve before anything posts; debits must equal credits or the server rejects the entry outright.
- True duplicates: voided, not deleted. No tool on the server can delete a posted transaction, so the audit trail survives your cleanup, which is the standard any reviewer will hold it to.
Step 5: Reconcile and Prove It, Month by Month
Categorized isn't done; reconciled is done. Run the close for each caught-up month:
"Run the month-end close for January."
The agent works the same six-step close procedure every time (reconciliation checks, AP and AR review, accruals, depreciation, statement review, trial balance) and scores the month against a 16-point checklist. Results land in the Close Sheet: the financial statements themselves with the agent's findings pinned to the exact lines they affect, exceptions flagged, proposed adjusting entries waiting for your approval. You sign each month when it deserves signing. That signature trail, month by month, is what turns "I think we're caught up" into statements a lender or tax preparer will accept.
Step 6: Don't Need This Guide Again
The same loop that dug you out keeps you out: the agent works the bank feed as transactions arrive, escalates the genuinely new situations, and the close becomes a monthly ten-minute review instead of a quarterly archaeology dig. The memory it built during your cleanup (every policy, every correction) is the head start on every future month. If you'd rather not even prompt it, the hosted always-on agent runs the sweep on a schedule with the same review gates.
What AI Honestly Can't Do in a Cleanup
Worth saying plainly, because cleanup is exactly where overclaiming hurts:
- It can't conjure missing documents. It will flag the transactions that need support so you can chase the paper, but a missing invoice is still missing.
- It shouldn't make tax judgment calls, and doesn't. Prior-year adjustments that touch filed returns, entity questions, aggressive-vs-defensible categorization: these get escalated with the evidence organized, and a professional should review them. The agent's job is making that conversation shorter, not replacing it.
- It won't paper over a broken bank feed. If statements and the ledger genuinely can't tie out, the close checks fail loudly rather than pass politely. A cleanup that ends in a signed close means the checks passed, not that everything was waved through.
If what you actually want is to never see any of this, including the review, an outsourced service is the honest alternative; just go in knowing whose system your books will live in.
DeepLedger puts a supervised AI agent inside your own QuickBooks Online: it reads the backlog, records what it can defend, escalates what it can't, and ends every caught-up month with a close you sign. The first month is free, no credit card required.
Start your cleanup at deepledger.ai or read how the whole system works.