Scope financial statement note preparation with an accountant

Give the prospective accountant the entity or group, reporting periods, framework, intended recipients, and current statement drafts. Identify whether the assignment creates first-time notes, updates prior notes, or repairs an incomplete package. Ask which technical expertise is needed for the company's transactions and who will review significant judgments.

IAS 1 includes notes in a complete IFRS financial-statement set. The provider must determine the applicable disclosure requirements for the company's actual basis and effective standards. A proposal to copy last year's wording or another company's notes does not establish that the resulting package will cover the current facts.

List the company owners who can supply agreements, commitments, related-party information, legal matters, and other relevant facts. Agree who sends requests, tracks responses, and follows up on missing information. The note preparer may organize the process, but management and specialist advisers still need to provide the underlying facts within their roles.

Ask the provider to identify expected schedules before work starts. Maturity analyses, asset movements, equity changes, and significant estimates can require calculations that ordinary bookkeeping reports do not contain. State whether the provider will build those schedules, review company-prepared schedules, or rely on another professional's work. Each option changes the engagement's effort and dependencies.

The scope should distinguish collecting facts, calculating tables, drafting wording, assessing disclosure requirements, and checking final presentation. A capable editor can improve language without being responsible for technical accounting conclusions. Identify the qualified reviewer and the company approver for each significant area. Clarify whether legal review is needed for particular wording.

For a hypothetical lease note, the provider might draft from an approved lease schedule supplied by the company. If the lease schedule itself requires reconstruction or a new accounting conclusion, that additional work should be identified. Avoid assuming that preparing a disclosure table includes a complete technical review of every underlying contract unless the agreement says so.

Ask for a disclosure evidence index connecting material amounts and statements to their sources. Require a tie-out to the final face statements and comparative columns, plus a record of significant review decisions. The completed notes should be checked in the actual file intended for release, including references, units, and any tables imported from other applications.

Agree how the provider handles late ledger changes and subsequent-event information. Specify the source cutoff, included revision cycles, and notification process. If an external accountant or auditor issues a report with the statements, coordinate the timetable and review responsibilities with that professional. The note-preparation engagement should not imply assurance that it does not provide.

Review the completed notes, supporting schedules, evidence index, and unresolved-item register together. Ask the provider to identify assumptions, unavailable records, and decisions awaiting company approval. A polished document with an unanswered material question is not a fully completed accounting deliverable. Record any agreed limitation and who will resolve it before the intended use.

Retain editable files and an update guide suited to the next reporting cycle, subject to agreed ownership and licensing terms. Identify the recurring information owners and technical judgments that need reassessment. The project should leave the company able to explain the current notes and organize the next update without reconstructing the evidence from email threads.