A broken QuickBooks Online file is an accounting problem.
But after years of cleanup work, I became increasingly convinced that many firms are dealing with a second problem at the same time.
The engagement itself is fragmented.
The accounting story gets split across tools.
The reviewer investigates the file in QuickBooks Online. Notes may live in a spreadsheet. Client explanations arrive through email. Documents sit somewhere else. Scope is written into a proposal. Tasks move into a project-management system. The CPA receives a different set of files later.
None of those tools are necessarily bad.
The problem is that the accounting context connecting them often depends on the person doing the work.
The reviewer becomes the integration layer.
That means the professional has to remember why a question was asked, which finding it related to, what evidence was considered, whether the client answer changed the conclusion, what made it into scope, and what still needs attention.
When one person carries the entire engagement, that may be manageable for a while.
It becomes much harder when the work pauses, the engagement lasts months, another team member gets involved, the client asks what is happening, or the file eventually moves to another professional.
Fixing the books does not automatically preserve the reasoning.
A clean ending balance does not tell the next reviewer how you got there.
A corrected transaction does not explain what evidence supported the correction.
A completed task does not tell someone whether the issue was fully resolved or simply handled as far as the available information allowed.
That reasoning matters, especially when the work is reviewed later.
This is why BrokenBooks starts with structured review.
The review is where the accounting story begins to take shape.
What did we check? What did we find? What evidence supports it? What is still unknown? What did the client tell us? What did the professional determine? What work might need to happen next?
BrokenBooks is being built around preserving those distinctions so the engagement does not have to be mentally reconstructed every time it moves forward.
Cleanup is one use case. The underlying problem is broader.
The same need exists when a firm is reviewing a file before taking on a client, checking work before tax preparation, performing an internal quality review, or conducting deeper due diligence.
The file may be simple or complicated. The client may be in construction, retail, manufacturing, professional services, or another industry entirely.
The common problem is that professional review creates valuable context, and most accounting workflows do a poor job preserving it.
That is the problem BrokenBooks is trying to solve.
Related: See how BrokenBooks approaches the review and engagement workflow.
