Keep one financial statement draft when several people edit

Give every circulated statement draft a version identifier and an underlying trial-balance version. Record who assembled it and when. A reviewer should be able to say which numbers and notes were assessed, even while another person continues editing. Shared editing can be useful, but a moving document makes a completed review ambiguous unless the reviewed state is retained.

Appoint one person to assemble the release candidate. Note writers and technical reviewers can own their sections, while the assembler controls incorporation into the full set. Decide how proposed edits enter that set. Avoid asking several people to return differently named copies with no process for identifying which changes were accepted.

Classify each comment by what it changes: a ledger amount, a statement mapping, a disclosure calculation, wording, or presentation. A number change may require a refreshed trial balance and new tie-outs. A wording change may require legal or technical review without changing the ledger. Routing them separately lets the right person assess the effect.

Use a comment register for unresolved decisions, including the section, proposed correction, owner, and affected draft. Keep the actual resolution beside the comment. Marking a comment closed because someone replied is insufficient if the accepted change never reached the assembled document. Inspect the resulting page or table before recording the item as incorporated.

Suppose an illustrative adjustment increases a liability by $7,500. The balance sheet changes, but a maturity table, expense line, cash-flow reconciliation, or explanatory note may also need attention. Ask the accounting reviewer to identify the affected outputs and give the assembler a complete change list. Do not expect the person editing the first table to discover every dependency.

PCAOB AS 1215 calls for documentation of significant findings and actions addressing them within covered audits. For internal statement preparation, a linked change record provides a practical way to retain the disposition of review points without treating the company's drafting file as an audit file.

When the team has incorporated the agreed changes, produce a fixed review candidate. Record its source balances and open matters, then ask the reviewers to work against that version. If a material change arrives during review, identify whether it requires a replacement candidate or a limited re-review of affected sections. Preserve the earlier candidate so comparisons remain possible.

Check the final exported document, including page references, tables, headings, and notes that cross a page boundary. A correct working file can produce an incomplete export or include an older linked object. The assembler should verify that the distributed file contains the accepted wording and amounts, rather than assuming the export inherited every edit.

Approvals should identify the release candidate or final document they cover. Retain the final file, unresolved matters accepted by the responsible decision-maker, and the recipient list where relevant. If an external accountant or auditor issues a report with the statements, coordinate that release with the professional responsible for the report.

Close the drafting register by resolving comments or transferring genuine continuing matters to a named owner. Keep the accepted changes and their rationale available for the next reporting cycle. That record allows the next preparer to carry forward an approved disclosure without reconstructing why one reviewer changed it and another rejected an earlier version.