Handle an entity report prepared to a different date

An entity file can arrive late while still covering the correct group date, or it can arrive on time with an earlier balance-sheet date. Record the financial period covered, extraction time, and submission status separately. Ask the entity accountant which transactions and adjustments are included. A recent file name does not prove that the underlying information reaches the group cutoff.

IFRS 10 governs preparation of consolidated statements for a parent and subsidiaries. Ask the group accountant to determine the permitted treatment of differing dates under the applicable framework. Do not assume that a familiar lag is acceptable or apply a generic maximum interval without confirming the relevant requirements and circumstances.

Identify what changed between the entity's reporting date and the group's date. Request transaction activity, significant contracts, unusual events, financing changes, and other facts the group accountant needs. The appropriate request depends on the approved consolidation approach. A bank movement report alone does not capture all accrual or noncash changes.

For a hypothetical group reporting at September 30, a subsidiary supplies a reviewed August 31 balance. A September activity bridge should identify the opening source, movements, adjustments, and closing result needed for the approved approach. If complete September information is unavailable, describe the limitation and obtain the group's accounting decision rather than representing August figures as September actuals.

Compare transactions between the entity and other group members during the intervening period. One side may include a service charge, settlement, or transfer that the earlier-dated submission excludes. Keep those items in a dated bilateral bridge. The elimination team should know which difference arises from the reporting date and which reflects an actual posting error.

Do not adjust only the intercompany balance while ignoring the related expense, income, asset, or cash consequence. Have the accounting reviewer assess the complete entry or reporting adjustment. A pair that agrees after a one-sided plug can leave the group statements inconsistent elsewhere. Retain the source transaction and the approved reporting-layer treatment.

State whether the gap information is a closed trial balance, an unreviewed extract, or a management estimate. Identify who prepared and reviewed it. Request the supporting schedules needed for material amounts, including noncash movements and judgments. A bridge with correct arithmetic can still rely on incomplete activity or unsupported estimates.

Keep the original entity submission and subsequent additions as separate versions. If the entity later supplies a final report for the relevant date, compare it with the group information already used. Ask the group accountant to assess differences and any effect on released reports. The earlier bridge should remain available to explain what was known at the time.

Agree future entity deadlines, required reporting dates, and minimum submission contents with the local and group teams. Identify statutory-calendar or system constraints that require a continuing approved approach. If the issue was simply late preparation, address the missing inputs or review capacity rather than institutionalizing a reporting lag without an accounting basis.

The final packet should identify the date mismatch, approved treatment, additional information, intercompany bridge, and remaining limitations. Give the statement assembler the exact source version used. The group can then explain how the entity contributes to the reported period without disguising an earlier-dated file as a completed current close.