No department or location P&L
The most common request by a distance. Usually solvable in place, because the data is often recoverable from classes and vendor patterns even where nobody set up dimensions properly.
By current system
QuickBooks Online is good software and most companies using it should keep using it. The failure mode we see is not staying too long — it is being sold a replacement before one is needed. Here is what can be fixed without leaving, and the three things that genuinely cannot.
184 consecutive days tied · variance $0.00
The situation
The most common request by a distance. Usually solvable in place, because the data is often recoverable from classes and vendor patterns even where nobody set up dimensions properly.
A workflow problem rather than a ledger problem. Bills can be read, coded, matched, and approved on top of QuickBooks, writing finished bills back into it.
Consolidation in a spreadsheet. Reporting-level consolidation is achievable in place; genuine intercompany elimination is not, and that distinction usually decides whether you move.
Often fixable with daily reconciliation and a structured checklist without touching the ledger at all — the constraint is usually waiting rather than volume.
For software and services companies this is the usual forcing event, and it is one of the three things QuickBooks cannot be made to do from outside.
QuickBooks has no real fixed-asset subledger, so the schedule lives outside it and does not tie. Also on the short list of genuine limits.
The integration is read-only and stays that way unless you enable write-back deliberately. Within about two weeks, on the QuickBooks file you already have:
If one of those is your binding constraint, the ledger has to change — and the shadow ledger means it does not have to be a leap.
Whether department reporting is fixable in place depends on whether the dimension was ever captured. Classes used consistently are recoverable. Payroll arriving as one lump journal with no department is not — no system can invent what was never recorded, and the fix is at the point of entry.
We will tell you which of the two you have during the assessment rather than in week three, and where we apply a defensible mapping we label those figures as derived rather than captured.
Questions
A read-only connection and about a week is enough to tell you whether it is a reporting problem or a ledger one.