Group statutory reporting is often treated as the last mile of consolidation: once the numbers are consolidated, finance assumes that the financial statements and notes can be assembled quickly. In practice, the last mile is where many of the hardest control failures appear. Entity submissions arrive in different formats, mappings have changed without approval, note schedules do not reconcile to the consolidated trial balance, intercompany eliminations are visible in the statements but not in the notes, and narrative disclosures are updated outside the governed close process. The result may still look like a complete annual report, but the evidence supporting it is fragmented across spreadsheets, email chains and manually edited documents.
A controlled group statutory reporting operating model starts from a different premise. It treats the standalone and consolidated financial statements as governed outputs of a repeatable process, not as documents assembled after the accounting work has finished. Every reported amount should be traceable to an accepted entity submission, an approved adjustment or a controlled group-only input. Every disclosure should have an owner, an applicability conclusion, a source and a review status. Every final report should be reproducible from a stored data and rule snapshot. This is particularly important as IFRS 18 becomes effective for annual periods beginning on or after 1 January 2027 and Indian companies prepare for proposed Ind AS 118, because classification, subtotals, management-defined performance measures and disaggregation decisions need to be documented at both entity and group levels.
The operating-model objective is therefore broader than "faster consolidation." It is to create a finance-owned statutory reporting process that connects entity close, group aggregation, consolidation adjustments, disclosure preparation, technical accounting, review and document production. Repositora is designed around this proposition: controlled group statutory reporting and Ind AS 118 readiness without attempting to replicate the full scope of a heavy enterprise consolidation engine.
The consolidated trial balance is only one input to a statutory reporting pack. A complete set of group financial statements also requires accounting-policy narratives, basis-of-consolidation disclosures, subsidiary information, non-controlling-interest data, related-party schedules, debt maturity information, commitments, contingencies, segment information, tax reconciliations and numerous note roll-forwards. These inputs have different owners and different aggregation methods. Some are summed, some require eliminations, some are distinct lists, some are group-only conclusions and some are narratives that should not be aggregated at all.
Traditional close processes often blur these differences. The group team may request a large Excel reporting package and then manually determine which schedules can be added, which require elimination and which need a separate group conclusion. Because the method is embedded in individual spreadsheets rather than in a controlled data model, knowledge sits with a few experienced people. When an entity changes a schedule or a preparer leaves, the group team has to rediscover the logic. The risk is not only inefficiency. It is that the note presented to users does not reconcile to the statement line, does not reflect all entities or contains intra-group amounts that should have been removed.
The new presentation requirements intensify this challenge. IFRS 18 requires income and expenses to be classified into operating, investing, financing, income taxes and discontinued operations, with defined subtotals including operating profit and profit before financing and income taxes. The proposed Ind AS 118 follows the same broad architecture. A group cannot simply assume that the classification adopted by each subsidiary will automatically produce the correct consolidated presentation. A main-business-activity conclusion may differ between a standalone entity and the consolidated group. Accounts with similar names may contain different economic components. Management-defined performance measures may be communicated only at the parent or group level. These are group reporting judgements that need explicit ownership and review.
A practical target model has three connected layers. The first is the entity reporting layer. Each legal entity receives a controlled reporting package containing the trial-balance template, local-to-group mapping requirements, note schedules, related-party and intercompany forms, narrative questionnaires, Ind AS 118 classification questions, supporting-document requests and a certification checklist. The package is versioned and released by the group reporting administrator. Entity preparers work within a defined submission status flow, and entity reviewers approve the package before the group accepts it.
The second layer is the group processing layer. Accepted entity balances are aggregated, and approved consolidation or elimination journals are posted in separate layers. The calculation should remain transparent: final consolidated amount equals accepted entity amounts plus posted consolidation journals plus posted elimination journals. This deceptively simple formula is powerful because it preserves the components of the result. It allows finance and auditors to distinguish entity local balances, entity statutory adjustments, group aggregation, intercompany eliminations, other consolidation adjustments and the final consolidated balance.
The third layer is the statutory reporting layer. Statement lines and note fields are generated from controlled reporting concepts rather than from workbook cell references. Note schedules have defined aggregation methods and can receive note-level adjustments where a statement-level elimination is not sufficiently granular. Applicability rules determine which disclosures require completion. The report composer assembles the approved statements, policies, notes, corporate information, signatures and appended documents. The final pack is generated from a snapshot that records the data version, rule-pack version, template version and calculation-engine version.
These layers should be connected but not collapsed into one undifferentiated workflow. Entity preparers should not be able to alter group-only conclusions. Group preparers should not silently overwrite accepted entity data. Disclosure owners should be able to update their assigned notes without gaining access to unrelated entities or journals. External auditors should be able to review evidence and raise queries without posting entries. Clear role boundaries are an essential part of the operating model, not a secondary security configuration.
A controlled group reporting platform does not need to perform every consolidation calculation on day one. Three reporting modes allow organisations to adopt the model in proportion to their existing systems and complexity. Standalone mode extends the single-company process with roll-forward, improved disclosures, multi-level review, transition analysis and structured outputs. It is suitable for legal entities that prepare their own financial statements and for parent companies that need a controlled standalone pack alongside the group accounts.
Pre-consolidated mode is often the best starting point for group reporting. The customer continues to consolidate in Oracle HFM, another EPM platform, an ERP or a controlled spreadsheet process. It uploads the consolidated trial balance, a consolidation-adjustment report, entity or segment schedules and group disclosure data. Repositora then becomes the statutory reporting and disclosure workbench. This avoids replacing a functioning consolidation engine while still solving the difficult problems of note preparation, source lineage, applicability, review and document assembly.
Basic aggregation and manual consolidation mode is appropriate where the group does not have a dedicated consolidation system or where a smaller group wants a transparent workbench. Repositora imports entity-level trial balances, aggregates them and permits controlled manual journals for intercompany elimination, investment-versus-equity adjustments, goodwill, non-controlling interests, uniform accounting policies, reclassifications and note-only changes. The boundary must be explicit. Automated foreign-currency translation, ownership-change calculations, step acquisitions, complex NCI computations and equity-method calculations should remain outside the initial release. Manual approved inputs can be accepted, but the software should not imply that it is a full consolidation engine.
The operating model should assign ownership by object, not only by task. The entity finance team owns its trial balance, local schedules and certification. The group mapping owner controls group accounts and material mapping changes. Technical accounting owns rule interpretations and main-business-activity conclusions. Disclosure owners are responsible for designated notes and policies. The consolidation team owns group journals and intercompany resolutions. The group reporting team owns the report pack, while the CFO or authorised executive owns final certification.
This object-based ownership improves the close calendar. A conventional calendar may say "submit notes by day 10," but that does not show whether a note depends on an approved trial balance, intercompany resolution, tax schedule or board-approved forecast. A governed calendar links dependencies. The group cannot finalise trade receivable ageing until entity schedules are accepted and intra-group receivables are eliminated. The MPM note cannot be approved until the public-communication inventory, measure definition, reconciliation, tax effects and NCI effects are complete. The final report cannot be locked while critical validation exceptions or unresolved review points remain.
Statuses should be meaningful and enforceable. An entity package may progress from not opened to in progress, validation failed, submitted, under entity review, approved by entity, accepted by group and locked. Reopening an accepted package should require an authorised approver, a reason, a timestamp and identification of affected reports. This prevents late changes from bypassing the close governance and gives the group team a reliable basis for determining whether previously completed work must be reperformed.
The core control principle is that no final number or disclosure should exist only in the report document. Amounts should be stored as structured facts with entity, period, scenario, currency, reporting concept, source and adjustment layer. Narrative disclosures should use controlled variables for amounts, dates and company information, with manual overwrites clearly identified. Review comments should attach to the object that caused the issue, such as an import, mapping, journal, statement line, note, requirement or report page.
Source lineage should permit drill-down from a consolidated statement amount to the entities contributing to the line, the accounts within each entity, entity adjustments, consolidation and elimination journals, and finally the source import rows. This chain makes audit work more efficient because the evidence is organised around the reported result. It also improves internal review. A group reviewer can investigate a movement without asking the preparer to reconstruct the source workbook or explain which version was used.
Maker-checker controls should apply to material mapping changes, posted journals, applicability overrides, manual note totals, reopening locked submissions and final report approval. The control is not complete merely because two user names appear in an audit log. The reviewer should see the original value, revised value, reason, supporting evidence, period impact and affected reports. Approval should freeze the reviewed version, while any subsequent change creates a new version requiring renewed review.
At the standalone reporting level, Repositora establishes the controlled reporting foundation for a single company. It imports and validates a trial balance, maps accounts to canonical reporting concepts, records top-side adjustments, generates Schedule III Division II statements, prepares structured and narrative notes, performs tie-outs, supports preparer-reviewer sign-off and produces controlled outputs. This foundation matters because group reporting cannot be reliable if the entity-level logic is not structured.
For group and transition reporting, Repositora expands that foundation into a repeatable group process. It adds reporting groups and entities, prior-year roll-forward, entity submission packages, reusable import profiles, local-to-group and group-to-reporting mappings, pre-consolidated reporting, basic aggregation, manual consolidation journals, group note aggregation, Ind AS 118 transition workbenches, multi-level review, document composition and complete source lineage. The design preserves the same reporting concepts across standalone and consolidated packs, reducing duplication and allowing an entity to contribute to the group without rebuilding its statutory reporting logic.
The most important design choice is restraint. Repositora should complement rather than imitate enterprise platforms. It can accept outputs from HFM, Finalyzer, ERP systems or controlled Excel consolidations. Its differentiator is the compliance and disclosure layer: turning balances and approved adjustments into complete, traceable and reviewable Indian statutory financial statements while maintaining readiness for IFRS 18 and proposed Ind AS 118.
Consider an Indian manufacturing group with a parent and six subsidiaries. Two subsidiaries use SAP, three use different local ERPs and one maintains its ledger in a smaller accounting package. The group consolidates in an existing spreadsheet model. Historically, the annual report process begins after the spreadsheet consolidation is substantially complete. Each entity sends note schedules by email, and the parent team manually copies them into a master workbook. Intercompany balances are eliminated at statement level, but the receivable ageing note still includes some intra-group balances. The group's adjusted EBITDA measure is reconciled in an investor presentation but not governed through the statutory close.
Under the controlled operating model, the group creates a reporting period by rolling forward the prior approved pack. Entity profiles, mappings, note templates, policies and disclosure ownership are copied, while approvals, evidence and current balances are reset. Regulatory changes are presented for review. Each subsidiary receives a controlled package based on its import profile. Validation results are visible before submission, and entity reviewers certify the data. The group uploads the pre-consolidated trial balance and the adjustment report from its existing model, while entity note schedules are aggregated in Repositora.
The receivable note applies a "sum with eliminations" method, and the note-level elimination is linked to the related consolidation journal. The group performs the main-business-activity assessment and classifies profit-or-loss concepts for the proposed Ind AS 118 view. The MPM register captures adjusted EBITDA, the public communications in which it is used, its formula, the comparable specified subtotal, reconciliation items, tax effects and NCI effects. Review points are resolved in the platform, and the final PDF, Excel and DOCX outputs are generated from an immutable snapshot. The existing consolidation process remains in place, but statutory reporting becomes controlled and reproducible.
The first priority is to define the group reporting taxonomy and ownership model. Finance should identify the entities, reporting packs, reporting concepts, note schedules, aggregation methods, adjustment layers and approval roles. This work should be performed with experienced preparers and reviewers, not left solely to technology teams. The taxonomy must reflect how the group explains its financial position and performance, while remaining stable enough to support year-on-year roll-forward.
The second priority is to pilot the process with a manageable group perimeter. Five entities with different systems and reporting characteristics provide a useful test. The pilot should cover one complete cycle: package release, import, mapping, entity approval, group acceptance, aggregation, journals, note preparation, validation, review, report generation and snapshot reproduction. The output should be compared line by line with an independently prepared statutory pack and reviewed by an experienced chartered accountant.
The third priority is to measure control quality as well as speed. Useful indicators include percentage of entity packages accepted on time, material unmapped value, mapping changes after submission, number and age of intercompany differences, unposted journals at review cut-off, face-to-note exceptions, reopened packages, unresolved disclosure requirements and report versions generated after final approval. A faster close that produces more late changes is not a mature close.
A controlled group statutory reporting operating model creates a single, governed path from entity submissions to the final standalone and consolidated financial statements. It recognises that statutory reporting is not only a calculation problem. It is a coordination, judgement, disclosure, evidence and publication problem. By structuring each of those elements, finance can reduce dependence on personal spreadsheets, make review more effective and prepare for the presentation changes introduced by IFRS 18 and proposed in Ind AS 118.
The most credible transformation is incremental. Start with reliable entity data, controlled mappings, note aggregation, rule-pack versioning and source lineage. Use pre-consolidated reporting where an existing consolidation engine already works. Add a basic workbench only where it solves a real need. The result is not an HFM clone; it is a finance-owned statutory reporting system that makes every number and disclosure explainable.
Official materials checked on 25 June 2026: IFRS Foundation - IFRS 18; issued IFRS 18 text; IFRIC Update - March 2026; ICAI Accounting Standards Board.
This article is educational and does not replace applicable standards, final MCA notifications, professional advice or entity-specific judgment. Product capabilities should be verified against the approved release scope before publication.
Explore how Repositora can connect entity submissions, group reporting, statutory notes, source lineage and Ind AS 118 transition readiness across standalone, group and transition reporting. Visit repositora.com
