Financial reporting review often occurs through a sequence of files and emails. An entity sends a workbook, a group preparer marks comments, a disclosure owner edits a note, and the CFO receives a near-final PDF. The organisation may have many reviewers, but it is difficult to prove which data and version each person approved. A change after review can invalidate earlier sign-offs without anyone realising it.
A multi-level workflow links review to specific objects and versions. Entity preparers submit trial balances and schedules; entity reviewers approve the package; the group accepts it; disclosure owners approve assigned notes; consolidation journals receive maker-checker approval; group reviewers approve statements and notes; and the CFO certifies the final report snapshot. External auditors have read-only access and can raise queries without assuming management responsibility.
The purpose is not to add approval layers indiscriminately. It is to place the right review at the right point, prevent incompatible duties and ensure that changes trigger reperformance. This is particularly important for IFRS 18 and proposed Ind AS 118, where classification, main-business-activity, MPM and disaggregation decisions involve judgement that should not be approved only at document level.
The tenant administrator manages users, security and company setup but should not automatically gain financial approval authority. The group reporting administrator creates periods, releases packages and monitors the group process. Entity preparers and reviewers own local submissions.
Disclosure owners are assigned notes or policies, such as tax, pensions, financial instruments or revenue. Group preparers manage consolidation and the report pack. Group reviewers assess statements, notes and technical conclusions. The CFO or authorised executive gives final certification.
The external auditor role is read-only with query capability. The regulatory-content administrator manages standards and rules separately from client reporting data. These role boundaries reduce conflicts and support specialist ownership.
Permissions should operate at entity and section level. A local preparer sees only their entity. A tax owner may see tax schedules across entities but not unrelated payroll or legal data. Access changes should be logged and reviewed.
A review comment should attach to an import, mapping, account, journal, statement line, note, disclosure requirement, validation exception or report page. The review point records owner, priority, due date, description, evidence, status, resolution and reviewer closure.
This structure avoids vague email comments such as "please check note 17." The issue remains linked to the exact field and version. When the underlying object changes, the review point can be marked for reassessment.
Statuses may include open, assigned, response provided, under review, resolved and closed. Resolution is not complete until the reviewer accepts it. Reopening a closed issue should be logged.
Review dashboards should prioritise critical and material items. Low-risk suggestions should not obscure blocking issues. Owners and escalation dates make accountability visible.
Maker-checker approval should apply to material mapping changes, posted journals, applicability overrides, manual note totals, reopening locked submissions and final report approval. The preparer and approver must be different users for material items.
The reviewer should see the original and revised values, reason, supporting evidence and affected reports. A click-only approval without context is weak. The system can provide a comparison and drill-down before enabling approval.
Approval thresholds may depend on amount, risk or object type. A low-value presentation adjustment may need one reviewer, while a business-combination journal or MPM definition may need technical accounting and CFO approval.
Emergency overrides should be rare, role-restricted and fully logged. An administrator should not be able to bypass maker-checker invisibly.
Entity certification is a formal representation that the trial balance, mappings, schedules, intercompany data, disclosures and evidence are complete and accurate for the reporting package. The checklist should be specific enough to be meaningful.
The entity reviewer should confirm that material validation exceptions are resolved, local adjustments are approved, new accounts are mapped, related parties and intercompany balances are complete, and subsequent changes will be communicated. Certification should identify the package version.
Group acceptance is a separate decision. The group may reject or return a package for mapping, disclosure or intercompany issues. Once accepted and locked, reopening requires authorisation and impact analysis.
Certification history supports accountability but does not relieve the group of review. The group remains responsible for consolidated reporting and group-only conclusions.
Notes often require specialist knowledge. Assigning an owner ensures that responsibility is not diffused across the reporting team. The owner reviews entity inputs, group adjustments, narratives, applicability and reconciliation.
The disclosure owner should see related statement lines, requirements, validations, prior-year text and open issues. A note is approved only when structured facts, narrative and evidence are complete.
Changes to underlying balances should mark the note for reperformance. A previously approved note cannot remain green if its source facts changed materially. Dependency tracking is essential.
Policies should follow the same process. Carry-forward text is reviewed against current transactions and regulatory changes, and boilerplate is not automatically approved.
Profit-or-loss category assignments require preparer and reviewer. Material mixed accounts, group overrides and classification changes should receive technical accounting review. The main-business-activity assessment should be approved at entity and group level where conclusions differ.
The MPM register crosses finance and investor relations. The measure inventory, public communications, formula, comparable subtotal, reconciliation, tax and NCI effects and explanation should have defined owners. Final approval may involve the CFO because the disclosure represents management's view of performance.
Aggregation and disaggregation conclusions should be reviewed for materiality and communication, not only arithmetic. The system can flag "other" balances and combined items, but management approves the presentation.
Transition comparatives and cash-flow mappings also require review because reclassifications affect reported subtotals and trend information.
A controlled workflow recognises dependencies. If an entity replaces its trial balance, affected mappings, journals, notes, MPMs and reports are flagged. The system should not simply retain prior approvals.
The impact can be materiality-based. A small change may require only targeted review, while a material change reopens broader sections. The policy should define thresholds and mandatory dependencies.
Report comparison helps reviewers focus on changes since the last approved version. Differences can be classified as data, mapping, journal, rule, template or narrative changes. This reduces repetitive review while preserving control.
Final approval should be blocked when critical issues remain open, mandatory disclosures are incomplete, unapproved overrides exist or report references are broken.
Auditors benefit from read-only access to source lineage, evidence, approvals and report versions. They can raise queries against specific objects and monitor management responses. This reduces duplicate evidence requests and uncertain file exchange.
Management must retain responsibility. Auditors should not prepare mappings, post journals or approve management conclusions. Their queries and review status are separate from internal approvals.
Access should be time-bound and logged. Sensitive evidence may require additional restrictions. Exported audit packs can provide a controlled alternative where direct access is not appropriate.
For a single entity, Repositora uses a lightweight preparer, reviewer and administrator workflow. Comments, evidence, version history, locking and audit trail establish the foundation.
At group level, Repositora introduces entity, group, disclosure-owner, CFO, auditor and regulatory-content roles. Review points attach to all major objects, and maker-checker extends across mapping, journals, applicability, notes and final report.
The workflow should be configurable but not infinitely customisable. A clear standard model improves adoption and testing, with limited options for approval thresholds and specialist roles.
A subsidiary submits a package with a material new finance-income account. The entity reviewer approves the local balance, but the group mapping dashboard flags an inconsistent IFRS 18 category. The group returns the mapping for explanation.
Technical accounting concludes that the account is investing at the entity level but operating in a financing subsidiary's standalone view because of its main business activity. At group level, a controlled override is approved. The category change affects operating profit and the MPM reconciliation.
The disclosure owner updates the MPM note, the group reviewer approves the revised statements and notes, and the CFO approves the final snapshot. Each approval is tied to the version after the change; no earlier sign-off is misapplied.
Useful metrics include open review points by age and priority, average response time, reopen rate, approvals bypassed, changes after approval, packages accepted with warnings, manual overrides, and final report versions. Trends reveal bottlenecks and control weaknesses.
A governance forum should review recurring issues and approval thresholds. Too many late CFO issues may indicate insufficient earlier review. Excessive low-value approvals may create fatigue and encourage superficial sign-off.
Periodic access and segregation-of-duties reviews are necessary. The system should report users with conflicting roles, dormant accounts and emergency overrides.
Multi-level review is effective when responsibility follows the reporting object and every approval is tied to a version. Entity certification, specialist disclosure review, group approval and CFO sign-off form a chain of accountable representations.
For IFRS 18 and proposed Ind AS 118, the workflow gives technical judgements the governance they require. It ensures that classification, MPM and disaggregation decisions are reviewed where they arise, not discovered in the final PDF. The result is a close process that is both faster to navigate and stronger in assurance.
A controlled process begins with an explicit inventory of the data objects that drive transition comparatives and cash-flow redesign. For this subject, the core objects are as-reported fact, restated fact, transition adjustment, reclassification explanation, historical mapping, cash-flow concept, cash-flow mapping, indirect reconciliation item, rule-pack version, and validation result. Each should have a business definition, source, owner, effective period, version, status and relationship to the reporting output. That metadata is what allows the team to distinguish a valid change in policy or business activity from an unexplained movement in a spreadsheet.
Evidence should be captured as part of the workflow rather than attached after the reviewer asks for it. Each comparative reclassification should trace to the historical source fact and approved category decision. Each reconstructed historical amount should identify the method, limitation, preparer and reviewer. Each cash-flow line should retain its own mapping rationale and reconcile to balance-sheet and supplemental data. For transition comparatives and cash-flow redesign, the reviewer should be able to move from the reported result back through the decision, rule or mapping to the complete source population without changing systems or requesting an offline reconstruction.
A practical design workshop for transition comparatives and cash-flow redesign should use one completed reporting period and one difficult entity or disclosure population. Bring together group reporting, entity finance, accounting policy, tax, treasury, investor relations, internal audit, external-audit liaison and technology as relevant. Reconstruct the path from source file or manual schedule to the final statement, note and approval. Mark every copied value, mixed account, offline adjustment, unversioned judgment, repeated reviewer query and late document edit. The purpose is to identify where the statutory fact or conclusion leaves the controlled model.
Test the proposed design against prior-year restatement is performed by overwriting the signed comparative presentation and a transition reclassification changes reported cash flows even though there is no change in underlying cash. For each break, agree the accountable owner, preventive or detective control, source evidence, materiality or tolerance, reviewer, escalation route, affected reports and acceptance test. Assign standalone current and prior-year scenarios to the standalone foundation and introduce entity and group as-reported, restated and transition scenarios only after the underlying concepts and evidence are stable. The output should be a prioritised backlog with rule, data, workflow and report-design decisions-not a generic list of desired features.
Implementation quality often deteriorates through apparently convenient shortcuts. Challenge editing the signed prior-year report instead of scenario-versioning it. Treat as a warning sign building only a top-level transition table. Resist ignoring historical changes in business activity or group composition. Avoid assuming presentation reclassification changes cash-flow economics. Do not rely on using the report document as the cash-flow calculation engine. The recurring pattern is that data, judgment or approval is moved outside the controlled model to meet a deadline, and the workaround becomes the next period's starting point.
- Who is accountable when prior-year restatement is performed by overwriting the signed comparative presentation?
- Can the team demonstrate, for a complete population, that each comparative reclassification should trace to the historical source fact and approved category decision?
- What tolerance and escalation should govern historical accounts requiring reconstruction?
- Which owner maintains the definition and period version of as-reported fact?
- Which foundational capability must be stable before the group introduces entity and group as-reported, restated and transition scenarios?
What changes the outcome is the connection between source data, accountable work and the reporting conclusion. The standalone reporting foundation would place current- and prior-year scenarios and a manual transition bridge based on approved concepts in a controlled record. A connected group reporting layer would then bring together entity and group as-reported, restated and transition scenarios, together with a classification-driven comparative bridge and drill-down across entities, group adjustments and transition views. The result should be evaluated through reconciliation quality, exception ageing, reviewer effort, late changes and the ability to reproduce the final pack. Faster report generation is valuable only when the underlying judgment and source evidence remain visible.
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
