Collect subsequent-event information through the reporting release

The accounting team needs a defined process for information arising after the balance-sheet date while statements are being prepared. Ask the responsible accountant which endpoint and requirements apply to the company and framework. Record the reporting date, intended approval or issuance date, and owners who must supply updates. A closed ledger does not end the information-gathering task.

IAS 10 defines IFRS events after the reporting period through authorization for issue and distinguishes evidence of existing conditions from new conditions. PCAOB AS 2801 addresses subsequent events in covered audits. Those contexts have specific requirements; do not assume that an internal management-pack deadline is the relevant endpoint for every professional report.

Give legal, operations, finance, and other relevant owners a focused request for significant developments since period-end. Examples may include major disputes, financing changes, asset damage, customer failures, commitments, or other events relevant to the business. Ask for dates, documents, and status. The accountant should determine the reporting treatment rather than asking nonaccountants to decide whether an event is adjusting.

Tailor the population to the company. A request sent only to the accounts-payable team will not capture every event known to the chief executive or legal owner. Record who responded and what period their response covered. A missing response remains a limitation to resolve, not an implied statement that nothing happened.

For each event, identify when the underlying condition arose, when the company learned of it, and when supporting documents became available. Retain the original date of the evidence. A later settlement can provide information about an earlier condition, while another event can arise wholly after period-end. The date of the final document alone does not answer the accounting question.

In a hypothetical review, a supplier dispute existed at December 31 and settled on February 10 while statements were still being prepared. Record the earlier dispute facts and the later agreement together. The accountant can then assess the required treatment. Do not classify the event solely as February activity because that is when the signed settlement arrived.

If release moves later, ask the accountant whether prior responses need updating and define the additional period to cover. Tell owners the new cutoff and request new facts rather than resending an ambiguous all-clear form. Preserve the earlier responses so the record shows how information developed over time.

Track every event through accounting assessment, proposed adjustment or disclosure, approval, and incorporation into the draft. Link it to the relevant statement version. A completed technical review does not prove that the note writer or journal preparer received the conclusion. Confirm the final document reflects the approved treatment before marking the event resolved.

Retain the request population, responses, event register, accounting conclusions, and release date with the final statements. Coordinate any auditor-specific requests directly with the auditor; management's internal process should support that work without representing itself as a completed audit procedure.

If significant information arrives after release, notify the responsible accountant or auditor promptly and preserve the facts. Do not silently replace the issued statements or assume the earlier process covers the new information. The professional should determine the next step under the applicable requirements, using the retained chronology to understand what was known before and after the report was issued.