Financial Statements module guide

What the Financial Statements Module Tracks

This Financial Statements module guide covers a single record type: the prepared statement set an organization holds for a given entity and period. The record carries the assurance facts — auditor, audit opinion, and report date — for audited or reviewed sets. The module tracks prepared financial statements, not their preparation. It doesn’t compute or generate numbers, so it doesn’t replace a general ledger or a filing tracker.

The Financial Statement Record

A Financial Statement record covers one statement set for an organization and period — annual, interim, consolidated, or standalone. When the set was audited or reviewed, the record also carries the assurance facts: the auditor, the audit opinion, and the report date. It belongs to its organization, and it has standard fields for Period and Auditor.

No Status or Timeline

Unlike most modules, a Financial Statement record has no status or timeline field, and this guide doesn’t describe one. A statement set is either on the record or it isn’t — there’s no in-progress lifecycle to move it through.

Fields on a Financial Statement

Every Financial Statement record starts with the same standard and custom fields. Your admin can rename, remove, or add to the custom set in Settings.

Standard Fields

• Period identifies the statement set’s reporting period.
• Auditor names the professional who produced the opinion, when one was engaged.

Custom Fields

• Scope distinguishes a standalone set from a consolidated or combined one for the same entity and period, so “FY 2025 (standalone)” and “FY 2025 (consolidated)” stay separate records.
• Assurance level records whether the set is audited, reviewed, compiled, or unaudited.
• Audit opinion records the result — unqualified, qualified, adverse, or disclaimer — when one was issued.
• Period end date, approved on, and auditor’s report date track the dates tied to the set.
• Notes holds anything the other fields don’t capture.

Adding a Financial Statement

Adding or editing a Financial Statement record requires Editor access to the module.

1. From the Financial Statements list, click New.
2. Choose the organization, set the period and scope, and save.
3. Open the record to attach the statement set, and — for an audited or reviewed period — set the assurance level, auditor, audit opinion, and report date.

Documents, Reminders, and Access

Attachments and Ad Hoc Reminders

The statement set attaches directly to its record. The auditor’s or reviewer’s report binds into the same file rather than tracking as a separate engagement. Because there’s no seeded due-date cadence, add your own event as a reminder to prepare or approve the next period’s statements. An ad hoc workflow can route a draft set through review and approval once your close-and-approve sequence is settled. No workflow template is seeded, since that sequence varies between audited and unaudited organizations.

Who Can Access This Module

Viewing Financial Statements requires access to the module; creating or editing a record requires Editor access. On Enterprise plans, access group scoping limits records to entities within your assigned access groups.