Data health
0 posted journal entries checked.
Entries with no narration
0
An entry with no narration shows as a bare number and amount — hard to read, easy to misjudge.
Duplicate entry numbers
0
Two entries sharing one number usually means a numbering sequence broke somewhere.
Numbers that don't match date order
0
Sorting by number won't give chronological order. Fine to view by date instead — never renumber history to fix this.
Entries with fewer than two lines
0
A real double-entry line can never have just one side. This is structurally invalid, not just unusual.
Entries dated in the future
0
Usually a forward depreciation schedule accidentally left posted, or a parsing error from an import.
Ledger balance (debits vs credits, and orphaned records across all organizations) is checked separately — see the accounting dashboard for balance, and runfix-orphaned-journal-entries.tsby hand for the orphan check, which cannot run inside a normal page for the same reason tenant data can't leak between organizations.