Double-entry, drillable, and honest

Every other statement is a summary; the general ledger is the record. Date, account, document, details, debit, credit — every entry in order, for any period, with running access to the document that caused it. When a figure looks wrong anywhere else in the books, this is where you find out why.

Long periods page honestly: the screen tells you when it is showing the first 500 lines and that totals are not the whole period — never a silently truncated number.

A ledger line here is never orphaned arithmetic: it references the sale, purchase, payment, transfer or settlement that wrote it, and the document opens from the line. The investigation path is always the same — start from the account that looks wrong, read its entries, open the document, done.

Journals balance individually, not just in total. One that does not is a posting bug worth reporting, not correcting by hand — and the screen's integrity checks are built to surface exactly that.

Documents post themselves: 'auto: sell', 'auto: purchase' — the Journal shows 139 entries for a trading month with debits equal to credits, none of them typed by a bookkeeper. Manual journals exist for the genuinely manual cases and are labelled as such, permission-gated, with reversing support.

The books are current at the moment of sale, not at the end of a data-entry backlog.

When a document is corrected, its old journal lines do not vanish — they move to the audit trail with when, by whom, and why they went. The ledger stays clean for reading while history stays complete for auditing: both audiences get what they need.

That is what 'edits with a trail' means in practice, and it is why accountants relax here.