Source Reddit post: https://www.reddit.com/r/Bookkeeping/comments/1ul067j/qbo_connections_past_month_disconnected_across_12/
Source Reddit freshness evidence: 2 hours ago
Build a lightweight bank-feed connection health monitor and reconnect/status queue for bookkeeping practices and small accounting firms managing many QuickBooks Online client files, so recurring disconnected feeds become tracked work with client-ready explanations instead of surprise reconciliation chaos.
opportunity / idea_filter. This is a credible bookkeeping-operations wedge, especially as a service-assisted tool for firms with many QBO files. The distinct choke point is not categorization drift, combined deposit matching, fixed-asset cleanup, or generic cleanup. It is recurring connection health before bank transactions even arrive: disconnected bank feeds, reconnect loops, transaction-download gaps, client blame, and close/reconciliation delays.
Primary buyer: bookkeeping practices, small CAS/accounting firms, QBO ProAdvisors, and fractional controller teams managing multiple QuickBooks Online client companies.
Best early adopter:
User language to keep: bank feeds, disconnected, reconnect, transactions not pulling, weekly, clients looking at me, QBO connections, Chase, BOA, TD Bank, Error 350, bank transactions not downloading, manual upload, close delay, reconciliation delay.
The fresh Reddit seed is unusually direct. A bookkeeper says multiple client QBO bank feeds across Chase, BOA, and TD Bank have been disconnecting weekly across 12+ accounts for the past month. The key commercial signal is not just annoyance with Intuit. It is the operating burden: clients are looking to the bookkeeper for answers, and the bookkeeper has no satisfying explanation beyond QBO instability. One reply says they avoid bank feeds, enter their own activity, and reconcile monthly, which is a blunt substitute that trades automation for manual control.
Non-Reddit validators show this is not an isolated vocabulary problem:
1. Intuit has active support material for Chase-specific connection failures. Its Chase article says customers may receive login/authentication errors and that, due to Chase security guidelines, a Chase Online Banking ID can link Chase accounts to only one QBO company at a time unless the Chase Account Owner adds an authorized user for each QuickBooks company. That matters for bookkeeping firms because the friction is per client file and per bank credential, not just one business owner clicking reconnect once.
2. Intuit’s Open Banking reconfirmation article says bank feed consent may need to be reconfirmed every 90 days, with a Manage connections flow, past consents view, and reconfirm steps. Even though this specific article is UK/Open Banking, it validates the broader pattern: bank connections can expire or require recurring consent management, and QBO’s own support path is a manual reconnect workflow.
3. Intuit’s bank connection error documentation lists many reasons feeds break or stop downloading: bank website prompts, password changes, bank maintenance, bank server issues, inactive accounts, account name/detail changes, duplicate accounts, bank accounts moved to different servers, closed accounts, and the need to refresh, reconnect, disconnect/reconnect, manually update, or manually upload transactions. This supports the hypothesis that “why is this disconnected?” is an exception-triage workflow, not a single root-cause bug.
4. Intuit Community threads show recurring variants of the same pain: “Need to reconnect bank accounts every day,” “My bank accounts keep getting disconnected after every synchronization. I work with TD Bank,” “QuickBooks Online keeps disconnecting JP Morgan Chase bank accounts - Error 350,” “Bank Transactions not Downloading,” and “Reconnecting Bank Feed to already established accounts.” Search snippets and accessible pages show the same terms bookkeepers use: reconnect, disconnected, TD Bank, JP Morgan Chase, Error 350, bank transactions not downloading, and manual upload as a workaround.
5. Accounting workflow competitors validate budget and workflow adjacency. Financial Cents sells accounting practice management and month-end close workflows, says firms can ditch spreadsheets, QuickBooks, emails, and follow-ups during close, connect a client’s QBO file, ask clients transaction questions, and push corrections into QBO. Its pricing page shows solo, team, and scale plans with QBO integration, client tasks, portal, workflow, email integration, and plans around $49 to $69/user/month annually. Double says it connects to QuickBooks to help accounting firms manage clients and workflows, includes “AI Bank Feeds,” close pages, client portal/app, inbox, integrated review tools, and a $200/month annual commitment plus add-ons. Jetpack Workflow sells recurring workflow/project management for accounting firms and bookkeepers. These are substitutes, but they also prove firms pay for workflow control around QBO client work.
6. Month-end close positioning confirms the cost center. Financial Cents’ month-end close page says firms are juggling spreadsheets, QuickBooks, emails, and follow-ups, and that centralized transaction review and client communication make close repeatable and predictable. Feed disconnection sits one step before transaction review: if transactions are not pulling, the close checklist is blocked and the bookkeeper has to chase the client, the bank, or Intuit.
This wedge is timely because several forces compound:
A weekend-buildable first version should avoid promising magic API access or automatic repair. Start as a firm-facing triage desk and client communication layer.
Core objects:
1. Client-file registry: client name, QBO company, bank name, account nickname, last known feed state, responsible staff member, client owner/contact, MFA/authorization owner, monthly close due date, and normal transaction cadence.
2. Feed-health checklist/import: CSV/manual import from QBO banking pages or staff check-ins. Status values: connected, disconnected, needs reconfirmation, transactions not pulling, bank error, client action needed, manual upload needed, resolved.
3. Reconnect queue: grouped by client, bank, severity, close date, and “who must act.” For example: staff can refresh; client must approve bank prompt; Chase account owner must add authorized user; bank outage wait 24-48 hours; manual CSV upload needed.
4. Evidence log: timestamped screenshots/notes, QBO error text, bank, account, last successful pull, missing date range, support link used, and client communication history.
5. Client status templates: short, plain-English messages that say what is broken, who must reconnect, what transactions may be missing, and whether close/reconciliation will be delayed.
6. Close-impact dashboard: “8 feeds disconnected, 3 client actions pending, 2 accounts not pulling transactions since June 12, 5 clients at risk for delayed close.”
7. Post-resolution checklist: confirm transaction gap, avoid duplicate downloads, manually upload missing transactions if needed, document last successful refresh, then release to reconciliation.
V1 should work without privileged automation:
The first paid version can be sold as “bank-feed reconnect triage for bookkeeping firms” plus concierge setup: load the client registry, create templates, run a daily/weekly feed-health sweep, and produce a client-facing status queue.
Start where the pain language already appears:
A good validation test: offer a $300 to $1,000 one-time setup for a firm with 20+ QBO clients, including registry, templates, and two weeks of feed-health triage. If firms will not pay for that, the SaaS subscription is premature.
Substitutes today:
Whitespace: a narrow, bookkeeper-owned “connection health and client reconnect queue” that sits before reconciliation, documents evidence, and creates client-ready explanations. It should integrate with practice management tools later rather than pretend to replace them.
1. Build a simple Notion/Airtable/Retool-style prototype with client registry, feed status, reconnect owner, last successful transaction date, close risk, and canned client messages.
2. Offer it manually to 5 bookkeeping firms with 20+ QBO clients.
3. Ask for access to anonymized weekly counts: disconnected feeds, client authorization requests, missing transaction ranges, close delays, and manual upload events.
4. Price the initial service as setup plus per-client/month or per-firm/month. Test $300-$1,000 setup and $99-$299/month for ongoing triage/templates before building deep automation.
5. Only after repeated use, explore QBO/browser-assisted status capture. Do not start with bank credential automation.
The evidence is strong that QBO bank-feed reconnect problems exist and that accounting firms pay for QBO-connected workflow tools. The weaker part is direct proof that firms will buy a standalone connection-health product rather than use Financial Cents, Double, Jetpack Workflow, spreadsheets, or simply wait for Intuit/banks to resolve issues. The Reddit thread is vivid but small, with only a couple comments at capture time. Intuit docs validate failure modes, but support docs do not quantify frequency or labor cost.
The biggest unknown is API feasibility. If QBO does not expose enough bank-feed status, the product is more of an operating checklist and client-communication layer than a true monitor. That can still be monetizable as a concierge/service wedge, but the landing page should avoid overclaiming automatic detection. The fastest next step is not code; it is selling a feed-health triage sprint to firms already complaining about Chase/BOA/TD reconnect loops.
REDDIT_RESPONSE_DRAFT_START
That sounds exactly like the annoying middle ground where the bank feed is “automatic” until it isn’t, then the client expects you to explain Chase/BOA/TD and QBO auth weirdness like you control it. I’d start keeping a tiny reconnect log per client: bank, last successful pull date, error text, who has to act, whether transactions are missing, and what you told the client. It gives you something better than “QBO is being QBO” when close gets delayed.
For the ones that keep dropping, I’d also check whether the bank login is tied to multiple QBO files or if the client needs to approve/reconfirm consent on their side. I’ve been helping firms turn this kind of recurring QBO mess into a simple client status/reconnect queue so it doesn’t live in random emails every week.
REDDIT_RESPONSE_DRAFT_END
Real recurring bookkeeping-ops pain with a practical workflow wedge, but QBO integration visibility and incumbent absorption risk keep it from being an obvious BUILD.