One of the ideas I cared about very early in BrokenBooks was deceptively simple:
Unknown is a valid review state.
That probably sounds obvious. In practice, accounting workflows often push people toward a completed answer even when the available evidence does not support one.
A blank answer and an unknown answer are not the same thing.
A blank can mean nobody reviewed the issue.
Unknown can mean the reviewer investigated it, identified the limitation, and knows exactly what information is missing.
Those are very different states.
Professional review does not always produce immediate certainty.
You may see a balance that does not make sense but need historical support before you can explain it.
You may have a client explanation but still need documentation before you can determine the accounting treatment.
You may know that an issue exists without yet knowing how many periods it affects.
Forcing a conclusion at that point does not make the review more complete. It makes the documentation less honest.
Uncertainty should create a next step.
The useful question is not simply, “Do we know the answer?”
It is, “What would we need in order to know?”
That might be a client clarification, a bank statement, payroll support, a prior-year tax return, a loan agreement, an inventory report, or additional investigation inside QuickBooks Online.
Once that next step is visible, uncertainty becomes manageable instead of disappearing into notes or memory.
This matters for review quality.
If another professional revisits the file later, they should be able to distinguish between:
- an issue that was reviewed and supported,
- an issue that was reviewed and found to be incorrect,
- an issue that still requires information, and
- an area that has not yet been reviewed.
That distinction becomes even more important when work moves between team members or from bookkeeping into tax, due diligence, or another professional review.
Software should not pretend to know what the professional does not know.
BrokenBooks is being built to structure the review, not manufacture certainty.
The system can preserve the evidence, the questions, and the current state of the review. The bookkeeper or accountant decides what the evidence supports.
Sometimes that conclusion is clear.
Sometimes the correct professional answer is: we do not know yet.
That answer deserves a real place in the workflow.
