opportunity / idea_filter — credible, but best treated as a narrow cleanup workbench for bookkeepers/accountants, not a replacement bookkeeping platform. The buyer, pain, MVP, willingness-to-pay hypothesis, and reachable distribution wedge all clear the bar.
Build a bookkeeper-facing workbench that ingests bank/QBO exports, detects combined deposits and likely constituent payments across Stripe/POS/checks/ACH/manual entries, and turns trial balance vs bank cleanup into a ranked exception queue plus client-question packet.
External bookkeepers, QuickBooks ProAdvisors, cleanup specialists, and small accounting firms inheriting messy SMB QuickBooks Online files. The sharpest first ICP is a practitioner handling 5–30 clients where one cleanup engagement can include 6–18 months of bank activity, card processor deposits, checks, EFT/ACH, petty cash/clearing accounts, and an accountant asking them to reconcile differences between the trial balance and bank activity.
The user language matters: the seed thread is not “automate all bookkeeping.” It is “QuickBooks trial balance v. bank,” a failed QBO year, an external bookkeeper/accountant dynamic, about 500 transactions per month, many deposits combined from Stripe and other credit-card processors, plus EFTs and checks. That is an archaeology problem, not a simple receipt/OCR problem.
Seed pain-language source. The fresh r/Bookkeeping thread asks for “Quickbooks Trial Balance v. Bank” breadcrumbs. The visible old.reddit text says the poster had “a fail of a year in QBO,” is being pushed by the accountant to find the issue, both are external to the client, the bank does about 500 transactions per month, and “many deposits are combined from Stripe and two other credit card processing platforms,” while other clients send EFTs and checks. It explicitly frames the problem as trial balance, bank, reconcile, and cleanup work after the fact.
QuickBooks support evidence. Intuit’s own support/community pages show this exact class of operation exists inside QBO but remains advice-heavy: a 2025 QuickBooks Community answer says a user can match a single batch deposit to multiple invoices in the Bank Transactions window; another QuickBooks Community result about merging/making deposits and reconciling a bank account with many transactions tells users to carefully match transfers and deposits and use journal entries if necessary. That confirms the accounting object model supports the workflow, but cleanup users still need procedure and judgment.
Accounting workflow evidence. QuickBooks’ own 2026 bookkeeping cleanup checklist includes “Clear undeposited funds” and says to ensure funds from every deposit in the account appear on the bank statement and vice versa, and to flag deposits that have not registered and where. Fit Small Business explains why Undeposited Funds exists: it lets multiple checks/cash payments be grouped into a single bank deposit so QuickBooks aligns with the combined deposits on the bank statement. This is exactly the reconciliation primitive that breaks when inherited files have deposits posted directly, split incorrectly, duplicated through feeds, or mixed with processor payouts.
Adjacent-platform evidence. Xero Central has dedicated help pages for creating and reconciling batch deposits/payments, including bank statement lines that correspond to batch deposits. This is not QBO-only; it is a cross-ledger accounting cleanup pattern.
Paid-market evidence. QuickBooks cleanup and reconciliation are sold services, not just free advice. Remote Books Online markets QuickBooks Cleanup, QuickBooks Reconciliation Services, catch-up bookkeeping, and fixed monthly bookkeeping. House of Bookkeepers advertises QuickBooks cleanup “from $360 one-time,” including full-year bank and credit-card reconciliation. Search results for Upwork show live cleanup/reconcile projects requiring QuickBooks and bank reconciliation skills. This supports willingness-to-pay, though for services more than software.
Supported terms to preserve in product/landing-page language:
Three forces make this wedge timely:
1. QBO bank feeds and processor integrations create partial automation debt. Clients often connect bank feeds, Stripe/POS apps, and card processors before they have a clean accounting workflow. The mess appears later as duplicate income, uncleared Undeposited Funds, journal-entry patches, and trial-balance gaps.
2. SMBs keep adding payment rails. A single client can combine Stripe, another card processor, ACH/EFT, checks, cash-clearing, USD accounts, and manual journal entries. Matching by date/amount alone degrades quickly.
3. Cleanup labor is expensive but still spreadsheet-driven. Bookkeepers sell cleanup/reconciliation because owners pay for tax readiness and lender/accountant confidence. A tool that saves 3–10 hours on one inherited client file can justify a small monthly or per-cleanup fee.
Build a local-first web app or lightweight SaaS with CSV/XLSX import before deep API integrations:
1. Inputs
2. Matching engine
3. Exception queue
4. Outputs
This avoids building a full accounting system. The wedge is evidence assembly and exception resolution for existing messy files.
1. Data access friction: QBO exports vary, users may not know which reports to pull, and bank CSV formats differ.
2. False confidence is dangerous: Bad matching suggestions can create accounting errors. The product must be a review queue, not auto-posting.
3. Edge-case explosion: Every client has weird processors, partial refunds, transfers, deposits spanning multiple days, multicurrency, and historical journal patches.
4. Services buying motion: Many bookkeepers may prefer billable hours unless the tool clearly improves margin or helps junior staff produce senior-quality packets.
5. Platform incumbents: Intuit could improve bank matching, but the inherited-file cleanup niche remains less attractive than forward bookkeeping automation.
The opportunity is credible, but the evidence base is stronger for “combined/batch deposit reconciliation is a real accounting workflow” than for “bookkeepers will buy a separate tool immediately.” The seed Reddit post is fresh and unusually specific, but it is one thread. Search/access limitations prevented full Reddit JSON, and some support pages are JS-heavy. The strongest validation gap is willingness-to-pay for software instead of services; early validation should test whether cleanup specialists will pay per packet, not just praise the idea. The MVP should avoid full QBO writeback until matching accuracy and liability boundaries are proven.
A focused cleanup workbench for bookkeepers handling messy QBO combined deposits looks like a practical SMB-admin pain with real paid labor behind it and a reachable niche channel.