The ledger, proved monthly

A trial balance is the oldest control in accounting and most teams stopped looking at it. This one earns the look: May activity balancing at 15,326,992.08, labor rows the payroll module already proved, and every row one drill from its lines.

RuleProve the ledger every period: activity by account, debits equal credits to the cent, and the labor rows matching what payroll already reconciled.

Neverpresent a trial balance nobody can drill. A total that cannot reach its journal lines is a claim, not a proof.

Nothing here is clever; that is the point. The proof is boring arithmetic, run every month, drillable to lines.

◆ May 2026 activity, proveddebits equal credits at 15,326,992.08.

Account	Debits	Credits
1100 · Receivables	9,470,000.00
6000 · Wages	3,997,550.00
6010 · Employer taxes	305,812.58
6020 · Employer benefits	359,779.50
6100 · Travel	214,380.00
6200 · Software	389,210.00
6300 · Facilities	402,760.00
6400 · Depreciation	187,500.00
4000 · Revenue		9,470,000.00
2100 · Accrued payroll		4,663,142.08
2000 · Payables		1,006,350.00
1590 · Accumulated depreciation		187,500.00
May activity	15,326,992.08	15,326,992.08

The three labor debits are the same accounts the payroll module reconciles, the accrued payroll credit is its 4,663,142.08, and the payables credit is exactly the three operating expense rows it pays for. Every row drills to journal lines. Sample values are illustrative, never client data.

◆ Why activity, not just balancesmovement is where errors live.

A balance can be right by accident: two errors offsetting, a misposting hiding inside an opening balance. Activity for the period, debits against credits, is where a broken journal shows itself, which is why this proof runs on movement first and balances second.

◆ The owned answerthe proof as a standing query.

Summing landed journal lines by account and comparing the two columns is the entire report; it runs after every close and its history is kept. The tables are drawn on the GL star, and a month that fails the proof names its journals immediately.

Use case

Problem

The ledger is trusted on faith between audits: balances circulate without proof, and errors surface months later inside numbers already presented.

What we build

A monthly activity proof over the landed journal lines: debits equal credits to the cent, labor rows tied to the payroll module, every row drillable.

What you get

A ledger that proves itself every month, disagreements that name their journals the day they appear, and an audit that starts from evidence instead of extraction requests.

Can you prove last month’s ledger in one table?

We build the standing proof over landed lines, tied to payroll to the cent.

Talk to us

Terms on this page

GL: General ledger, the books this module lands and proves.
trial balance: Activity or balances by account with debits equal to credits.
activity view: Period movement, where broken journals show themselves.
drill: From any row to the journal lines beneath it.
offsetting errors: Two mistakes summing to a right-looking balance.
standing proof: The check that runs every period and keeps its history.