Skip to main content

​
GreatBook workspaces

These workspaces are live in the GreatBook web application.

​
Start with the right record

GreatBook deliberately keeps these records distinct:

​
Transactions: the unified accounting-events list

Open Books → Ledger for the canonical Transactions list. The old /books/transactions address redirects here so saved links continue to work. The retired Journal list is also a compatibility entrance: ?tab=journal resolves to Transactions, and exact journal-entry links focus the owning event. Filter by event type, source, posting state, text, entity, account, date, reversal, source category or lineage status. The list intentionally includes posted events and events still waiting to post; Posted is the only status that means the GL changed. Open an event to drill into its stable event reference, source summary, intake or native/workpaper lineage, related obligations, posting provenance, complete journal entries and lines, reversals and integrity state. Follow the journal-entry link when you need the immutable write; follow a source or workpaper link when you need the record that explains it. If lineage is missing or legacy/unverified, the UI says so instead of inventing a source relationship. Intake is one origin for document events, not the origin of every accounting event. Native subledger records, approved workpapers, reversals and system writers can also be the authoritative source.

​
Books: native subledgers, not a second ledger

Books is a distinct workspace for the seven authoritative native subledger families:
  1. Settlement, rails, AP and AR
  2. Inventory and costing
  3. Payroll
  4. Loans and treasury
  5. VAT and statutory tax
  6. Adjustment notes
  7. Consolidation
The catalog describes 32 core tables and 41 broader structures; that is a coverage model, not 41 competing ledgers. Each family opens native registers, related records, accounting-event links, exact journal-entry links and its GL control-account tie-outs. Use a native register to answer what happened operationally, then traverse its accounting links to see what it caused in the book.

​
Source clocks and freshness

Family summaries, registers and tie-outs show freshness independently from read coverage. Each native structure uses its declared authoritative date or timestamp; a family reports the least-current established source clock so a recent row in one register cannot hide an old source in another. The current policy is 35 days: exactly 35 days is fresh, and only a greater age is stale. A source with no row or no established clock is inconclusive, and a failed clock read is error. Neither is relabelled stale. The UI preserves the source, as-of time, verification time and policy beside the conclusion.

​
Read states are part of the answer

Books does not turn a failing or incomplete read into an empty register. Wait through the loading skeleton, then read the state shown with the family, register and tie-out:
  • Complete — the requested read and its stated coverage completed.
  • Partial — some facts or verification are unavailable; counts and tie-outs retain their own coverage state.
  • Inconclusive — the system cannot establish the requested conclusion.
  • Error — the native read failed; retry instead of treating it as zero.
An empty register is meaningful only after a successful read says it is empty. Refresh keeps the last successful rows visible and labels them stale if the latest refresh fails. stale is a UI/projection freshness state, not a fifth Books backend read-state value.

​
Approval and Assurance evidence

Rows in payroll, loans and treasury, VAT and tax, adjustment notes, and consolidation show maker/checker evidence where a separate gate applies. GreatBook accepts only an exact durable journal_workpapers source key or exact Typewriter handoff/approval chain as evidence. The evidence keeps the maker identity and time, every checker identity, time and step, the approval time and the exact source or document link. Intake approval text, descriptions and descriptive source keys do not fill a missing trail. A native writer with no separate gate says not_applicable; a record that should have evidence but does not says unavailable and makes the register partial. Tie-outs show current Assurance findings, their evidence times and any attributable waiver decision. A waiver remains visibly a waiver and does not mark the control fixed. If findings cannot be read or the bounded family result is truncated, the Assurance block is error or partial rather than zero. Books never acknowledges, waives, resolves or writes a finding; those decisions remain in Audit.

​
Worked example: reconcile a Books family to the GL

  1. Open Books and choose the authoritative family, for example Settlement, rails, AP and AR.
  2. Read the family summary before choosing a register; it names the native structures and their coverage.
  3. Open the relevant register and verify its native amount, stable record identity and accounting-event links.
  4. Check every relevant source clock and any row-level approval evidence before treating the register as current and authorized.
  5. Open the family tie-out and compare the native total, GL control total, difference, tolerance, scope, verification time and Assurance findings/waivers.
  6. Follow the exact event and journal-entry references for any difference.
  7. Stop with the reported state: partial means required links or evidence are missing, inconclusive means the comparison cannot establish a conclusion, and error means no usable tie-out was read.

​
Accountant Accounting Desk

The Accountant workspace is a route workspace, not an agent chat. Use it to read the close position and its analytical layer:
  • Close — select a defined fiscal period and read its stored or live close report.
  • Analysis — see what journal lines belong to.
  • Allocations — see what each settlement settles, including a retained link from Matching.
  • Costing — see what each cost object absorbed.
  • Adjustments — see the entries a period needs.
Allocations, Costing and Adjustments are read surfaces: filters, fixed-point amounts, exact journal links and pagination make the facts inspectable. They distinguish loading, successful zero results, partial coverage, malformed/unreadable replies and refresh errors. Accountant Wave E adds carry-forward and year-end roll calculations, CIT handling and the adjustment-keyed release gate. A proposed adjustment still pauses at the Bookkeeper posting gate; a named, separate human must approve the exact stable adjustment source before a journal entry can establish that it posted. Wave D supplies the period-scoped close_gated audit family and monthly last_closed job, while Wave F adds depreciation-coverage proof for assets in service and still inside useful life. Those are separate from the screen’s read surfaces: the desk shows stored/live evidence, and the server-owned job/Close paths decide when a period-scoped control may run.

​
The staged workspace is a review surface, not another book

The merged MCP application can preserve a multi-turn checklist and proposed changes in a user/org/session-bound staged workspace. Propose, inspect, edit, omit/restore, validation, revert and confirmation change only temporary review authority. An exact confirmed commit may reach only the closed typed set: workflow resume, W3 Matching accept/reject/undo, Typewriter approve/submit, adjustment approve/reject, fiscal close/reopen and typed business reversal. Every selected item carries its typed target version and is re-read at commit. The receipt reports committed, skipped, failed or compensated items with canonical and audit references. There is no generic transaction, Books-row, journal, SQL or route action. The protected public MCP endpoint is current on registry 1.14.1, but provider behavior is unexercised.