Financial Statements

Where Financial Statements Get Lost

One organization’s audited annual statements live in the auditor’s PDF export from three years ago. Last quarter’s reviewed interim set is an attachment on an email thread. A consolidated set and a standalone set for the same entity and period sit in two different drawers, distinguished only by which spreadsheet someone remembers to check.

Lextree keeps one register instead: every prepared statement, its period, its scope, and — when independent assurance was involved — the auditor, the opinion, and the report date. Not a general ledger and not a filing tracker, but a record of the finished, approved artifact itself.

Still tracking that list in a spreadsheet? Grab our free financial statement register template and bring it into Lextree when you’re ready to stop reconstructing it from email.

One Record, Every Assurance Level

A single Financial Statement record covers audited, reviewed, compiled, and unaudited sets alike. Assurance level lives as a field on the record, not as a separate engagement you reconcile back to the statements it produced. When an auditor’s report is bound into the set, its date and opinion — unqualified, qualified, adverse, or disclaimer — sit on the same record as the numbers they cover.

Scope and Period, Named Clearly

Two sets often exist for the same entity and period: a standalone set alongside a consolidated or combined one. Scope is its own field, so “FY 2025 (consolidated)” and “FY 2025 (standalone)” stay distinct records instead of one ambiguous entry. Interim and annual periods work the same way, through the period label rather than a second axis to manage.

Why There’s No Built-In Approval Workflow

Some Lextree modules ship a seeded workflow because the underlying process looks the same everywhere. Closing and approving financial statements doesn’t — an audited company’s sign-off chain looks nothing like a small nonprofit’s. Rather than force one shape on every organization, Financial Statements ships with the same ad-hoc workflow tools every module has: build your own close-and-approve checklist once, and reuse it every period.

No Reminders, By Design

There’s no seeded due-date reminder here either, because there’s no single statutory clock to hang one on — statement-preparation cycles are the organization’s own choice. The actual filing of accounts at a registry, where one applies, is tracked separately as a periodic filing obligation. Add your own close-calendar reminder once your cadence is set, and it behaves like any other event in Lextree.

Where It Connects

A period’s statements are the evidence base for a Taxes provision, the financials a lender reviews under a Treasury covenant, the numbers a board approves under Governance, and — for a foundation — the figures behind a Grants 990-PF. Keeping the statement itself in Lextree means every one of those records can point back to the same finished artifact instead of a copy nobody’s sure is current.