Skip to main content

​
Two layers on the same documents

The usual way to divide finance work is by document: you do the bills, I do the payroll. GreatBook does not divide it that way, because that is not where the difficulty is. It divides by layer, on the same documents.
The rule, in one test.If the fix is “find the missing or mismatched document, or correct what it says”, it is the bookkeeping layer. If the fix is “decide what this belongs to, or what the period needs”, it is the accounting layer.

​
A supplier invoice, read twice

A supplier VAT invoice for fabric arrives. Two people look at the same piece of paper and ask completely different questions. Both people are looking at the same invoice. Neither one owns it.

​
The split is already in the database, on one row

This is not a metaphor about how work feels. A single journal entry line carries both halves, side by side: The sub-ledger tables split the same way, table by table, without being forced to: A payment is bookkeeping: it left the bank and it matches a bank line. Which bills it settles is accounting: that is an attribution decision about the very same payment.
The stocks case is the clearest illustration. Stock movement and its reconciliation are bookkeeping. Stock costing and valuation are accounting. One Close checksum straddles that line and is split in two for exactly this reason: NEG-STOCK-QTY is a movement error, NEG-STOCK-VALUE is a valuation error, and sending every valuation error to the movement worklist would waste the wrong person’s afternoon.
The layer map is a generated artifact covering 54 prototype tables, 18 operational flows and 146 document types, and the agents’ rulebooks, the product and this page all read the same file. Three surfaces cannot disagree about the division if there is only one copy of it.

​
Where each layer starts and stops

The captain’s own GL-flow diagram is usually read as a journey from left to right, with the bookkeeper owning the left part. Under the layered rule that reading is wrong. The left half is not the bookkeeper’s part of the trip; it is the bookkeeping layer of every hop, and the accounting layer runs above it the whole way. The bookkeeping layer finishes at hop 2. The accounting layer is present at hop 1, on the very first posting line, and is the only layer from hop 3 onward. Assurance runs across both: continuously on the left, close-gated on the right.
The obligation lifecycle is the same idea in miniature. Sign an office lease and a payable arises. Take a customer deposit and a refund obligation arises. Production completes and that refund obligation converts into a customer receivable. Money moves and the obligation disappears.Each of those transitions is bookkeeping. What the transition attributes to, and when it is recognised, is accounting.

​
The service ladder, and where GreatBook actually sits

Firms selling client accounting services usually describe their offering as a five-rung ladder. It is a useful shape, and it is worth being precise about what it is.
This five-rung ladder is the popular customer-facing framing of client accounting services, not a single canonical published framework.The AICPA and CPA.com CAS 2.0 Practice Maturity Model names three advisory tiers above a compliance foundation: CFO Finance, CFO Business Insights and Trusted Business Advisor, with CAS 1.0 as the cloud-based bookkeeping foundation.The five rungs below are the service ladder as clients hear it described. They are not an AICPA framework, and this page does not attribute them to one.
The assurance row is the point. Assurance is not a rung. It runs along the side of the ladder, auditing the bookkeeping layer on matching and the accounting layer on analysis, which is why it gets its own workspace rather than a tab inside somebody else’s.

​
What this means on screen

The rail names the workspaces, and the workspace names are the ones to use: An exception carries the layer that failed, and that tag is what routes it: a break in the matching layer goes to the bookkeeping lane in Audit → Actions, a break in the analytical layer goes to the accounting lane. Those are two different people’s afternoons, and the register says which. Notice what the diagram does not show: a second write path. Both layers propose into the same human posting gate and the same single writer. Adding an analytical layer added a lot of judgment and exactly zero new ways to reach the ledger.

​
What is honestly not built yet

Recorded here rather than left for someone to discover.
  • The dimension vocabulary is built, but analytical reads remain bounded. The dimensions owner records the catalog and explicit missing-column behavior.
  • close_gated is explicit-only. The 26 close-gated checksums run for a finished period from the monthly job or a question naming one of their controls, not from the routine full sweep.
  • Durable workflows stop at metadata. A guarded resume activates workflow-step metadata but does not yet execute a complete accounting operation.
  • Guarded actions remain narrow. The closed staged set reaches W3 Matching decisions, Typewriter approve/submit, adjustment decisions, fiscal close/reopen, typed business reversal and workflow resume; it still excludes generic writers, payments, intake/posting decisions and arbitrary routes.
  • Replay safety is exact, not key-only. A reused journal source key must carry the same immutable facts, and the paired native obligation uses stable source identity in the same transaction; conflicting facts refuse instead of duplicating or returning a misleading prior result.
  • Reserved future agent names are not shipped agents and do not change the two live workflow layers.