Every total is just its lines

Ask why a total moved and the answer is always journal lines. The delivered drill searches since launch and errors at scale, so practitioners cap it at six months. The owned model lands the lines once, and the question stops having a ceiling.

RuleDrill from any total to its journal lines with the worktags attached, over a stated date range. The line grain is where every reconciliation ends.

Neverpoint a since-launch report at the journal line source. Past a few million lines the delivered report errors out, and practitioners cap ranges at six months.

The ledger is only ever the sum of its journal lines. Keep the lines and every total explains itself.

◆ One journal, workedthe May payroll accrual, balanced to the cent.

JRN 2026-05 payroll accrual	Debit	Credit
6000 · Wages	3,997,550.00
6010 · Employer taxes	305,812.58
6020 · Employer benefits	359,779.50
2100 · Accrued payroll		4,663,142.08
Journal total	4,663,142.08	4,663,142.08

The credit is the same 4,663,142.08 the payroll module reconciles from the other side. One event, one balanced journal, and a drill that ends at lines a person can read. That is the whole promise of keeping the line grain. Sample values are illustrative, never client data.

◆ Where the delivered drill stopsscale, and the six-month habit.

The delivered journal line sources search since the launch of the tenant, and university reporting teams document the failure: past a few million records the report errors, and the working guidance is to span no more than six months per run. Practitioner-observed, and exactly the wall the delivered-versus-owned page predicts at history scale.

Export ceilings stack on top: the same report-service caps the extraction pattern documents apply here, which is why the owned model lands lines continuously instead of re-querying history.

◆ The owned answerlines landed once, drills without ceilings.

The owned fact lands every journal line with its worktags as it posts, so history depth is a storage decision instead of a report timeout. The star behind it is on the GL model page; the drill becomes a filter, and the six-month habit retires.

Use case

Problem

Journal drills hit since-launch scale walls and export ceilings, so teams cap ranges at six months and history questions go unanswered.

What we build

A journal-line fact landed continuously with worktags attached, on the same conformed keys as the payroll module, drillable at any depth.

What you get

Reconciliations that end at readable lines, history questions answered from storage instead of timeouts, and one grain shared with every other module.

Can you drill three years of journals?

We land the line grain once, and the ceilings stop being your problem.

Talk to us

Terms on this page

GL: General ledger, the books this module lands and proves.
journal line: One debit or credit with its account and worktags; the grain.
balanced journal: Debits equal credits, per journal, always.
since-launch search: The delivered source scanning all history per run; the scale wall.
six-month habit: The practitioner workaround of capping report ranges.
line grain: Keeping every line, forever; the owned model’s choice.