Ask an SMB owner what runs their books and the answer is QuickBooks Online. Ask whether AI is involved and the answer is also yes: a coding agent on uncategorized transactions, a variance flagger on the P&L, a draft journal entry sitting in a queue. The pattern is everywhere. The gap is the same one we see across every accounting stack. The agent's reasoning evaporates the moment the entry posts. Why did it code that $4,800 charge to Software Subscriptions instead of Professional Fees? The audit trail says "modified by API user." That is not bookkeeping. That is a black box with a check mark.
Dock fixes the persistence side without touching what QBO already does well.
Architecture: QBO is the ledger, Dock is the deliberation
QBO stays source of truth for the chart of accounts, journal entries, and transactions. Dock holds agent OUTPUT: coding recommendations, variance flags, partial reconciliations, draft adjusting entries. Each row in Dock carries a qbo_journal_entry_id or qbo_transaction_id pointer back to the ledger. Agents read fresh from the QBO API every time they reason, so they never act on stale balances. Dock's consent gate fires the actual journal entry into QBO only after a human approves. Data path loops through Dock. The books never leave QBO.
Worked workflow: month-end close with a coding agent and variance flagger
It is the third business day of the month. Bookkeeper opens the close workspace.
The coding agent has spent the night reading uncategorized expenses from QBO. Sixty-two transactions, each one a row in Dock with a recommended account, a confidence score, and a one-line rationale citing vendor history and memo text. Forty-eight are above 0.95 confidence and pre-grouped for bulk approval. Fourteen sit below threshold with notes like "vendor new this period, similar memo to Q1 consulting accruals." Bookkeeper approves the high-confidence batch, reviews the rest manually. Each approval fires the journal entry to QBO with the agent attribution preserved in Dock.
Beside it, a variance agent has compared this month's P&L against the trailing three-month average. It flagged seven line items: marketing spend up 31 percent, COGS up 4 percent on flat revenue, a new utilities sub-account with no prior balance. Each flag is a Dock row with a draft note explaining the deviation and a suggested adjusting entry where it found timing differences. The controller reviews, accepts four, rejects three with comments. The rejections become training context the agent reads next month.
Five-step data flow
- Agent reads transactions, accounts, and prior-period balances from QBO API.
- Agent writes a coding recommendation or variance flag as a Dock row, attributed to its identity.
- Human reviewer reads the rationale in Dock, approves or rejects.
- Dock fires the approved journal entry to QBO via authenticated API call.
- Dock retains the full reasoning trail. QBO retains the posted entry with a Dock link in the memo.
Why QBO is the right ledger to wrap
SMB scale: Intuit's Global Business Solutions segment, anchored by QuickBooks, generated $3.0 billion in Q3 FY2025 revenue, up 18 percent year over year. The accountant workflow is mature. Tax season handoff to a CPA is standard. The IRS audit trail QBO produces is accepted documentation. Replacing QBO would be a non-starter for every SMB on it. Wrapping it with attributed agent output is the only realistic path. Same pattern we use for Xero shops.
If you want the broader picture on how Dock handles month-end across stacks, start with Dock for accounting and AI for bookkeeping and month-end close. Finance ops sits one layer up in Dock for finance.
CTA
Run your next QBO close inside Dock. The books stay where they are. The reasoning finally has a home.
FAQ
Does this overlap with QBO's built-in automation and Intuit Assist? QBO's automation suggests. Dock persists the suggestion, the rationale, and the human decision in one attributable row. They compose. Intuit Assist still runs inside QBO. Dock holds the work product of agents you build or bring.
What about multi-entity ops?
One Dock workspace per QBO company file. Cross-entity views aggregate by qbo_realm_id. Eliminations stay in QBO at consolidation time. Dock surfaces the inter-company variances before they post.
How does this handle the accountant handoff? Your CPA gets read-only access to the Dock workspace alongside their existing QBO Accountant access. They see every agent recommendation, every human override, every variance the close team caught. Year-end review takes hours not days.
Will the IRS accept this audit trail? The posted journal entries live in QBO with the same audit log they always had. Dock adds a parallel record of WHO recommended WHAT and WHY. That is supplementary documentation, not a replacement. Auditors love it.
Citations: