Common Audit Findings in Consolidated Financial Statements
Every audit cycle surfaces a familiar set of issues in consolidated financial statements. Despite years of experience, finance teams at large groups repeatedly encounter findings that could have been avoided with stronger processes and better infrastructure. Understanding the most common audit findings in consolidated statements is the first step toward preventing them from recurring quarter after quarter.
The challenge is structural. Groups with 15, 30, or 80 subsidiaries across multiple jurisdictions are managing different accounting systems, different fiscal calendars, different currencies, and different local GAAP requirements. Each of these variables introduces a point of failure that auditors will flag. For regulated enterprises reporting under IndAS, IFRS, or both, the margin for error is narrow, and the consequences of findings can extend well beyond the audit report itself.
What follows is a detailed look at six of the most frequently recurring audit findings in consolidated financial statements, along with a practical framework for preventing each of them proactively.
1. Incomplete Intercompany Eliminations
This is, without exaggeration, the single most common audit finding across Indian groups. Incomplete or incorrect intercompany eliminations account for a disproportionate share of restatement risk in consolidated statements. The reasons are well known: decentralized data entry, inconsistent nomenclature across subsidiaries, timing mismatches in revenue and expense recognition, and manual reconciliation processes that cannot scale with the complexity of the group.
Consider a manufacturing conglomerate with 25 subsidiaries, where raw materials, finished goods, and management fees flow between entities in India, Southeast Asia, and Europe. Each subsidiary records its side of the transaction in its own Chart of Accounts, often with different account codes and sometimes in different reporting periods. When the consolidation team at the holding company tries to match and eliminate these transactions, gaps appear. Intercompany receivables do not match intercompany payables. Revenue recorded by one entity does not match the cost recorded by the counterparty.
Auditors flag these discrepancies because they directly affect the accuracy of consolidated revenue, consolidated profit, and the balance sheet. Under IndAS 110, all intra-group balances, transactions, income, and expenses must be eliminated in full. Partial elimination, or elimination of only balance sheet items while missing P&L entries, is a finding that can cascade into material misstatement.
For a deeper examination of where these errors originate and how they compound, see our detailed analysis of common errors in intercompany elimination.
Why This Persists
The root cause is almost always process-related rather than knowledge-related. Finance teams understand the requirement. What they lack is a mechanism to ensure that both sides of every intercompany transaction are captured, reconciled, and confirmed before consolidation begins. When this reconciliation happens over email and spreadsheets, with 20 or more entities involved, something will slip through. Every time.
eMerge addresses this through a workflow-based intercompany elimination module where Company A enters figures for Company B, and Company B verifies them within the system. Eliminations happen in both the foreign currency and the base currency, and the dashboard tracks which entity pairs have completed their reconciliation and which are still pending. This kind of visibility is what prevents findings from reaching the auditor’s desk.
2. NCI Miscalculations
Non-Controlling Interest (NCI) computation errors are the second most common category of audit findings in consolidated financial statements. The calculation itself is conceptually straightforward: NCI represents the share of net assets and profit or loss attributable to minority shareholders. In practice, the computation becomes complex the moment you have multi-layered holding structures, step acquisitions, changes in ownership without loss of control, and subsidiaries that themselves hold stakes in other subsidiaries.
IndAS 110 requires that NCI be presented in the consolidated balance sheet within equity, separately from the equity of the owners of the parent. Profit or loss and each component of other comprehensive income must be attributed to owners of the parent and to NCI. Errors in this attribution flow directly into the equity section of the consolidated balance sheet and into consolidated earnings.
Where the Errors Originate
The most frequent NCI-related findings involve three specific situations. First, holding percentages that are not updated after a stake change during the period, leading to the wrong share being allocated. Second, NCI computed on post-acquisition profits only while ignoring fair value adjustments at the date of acquisition. Third, indirect holdings through intermediate subsidiaries where the effective holding percentage differs from the direct holding percentage, and the consolidation team applies the wrong figure.
We have documented these and other common pitfalls in detail in our post on NCI computation errors and common pitfalls.
In eMerge, NCI calculation is driven by user-definable formulas embedded in the report structure, linked to the holding percentage defined in the hierarchy manager. When a holding percentage changes, the NCI formula automatically reflects the change across all relevant reports. This eliminates the category of errors that arise from manual percentage lookups and manual formula adjustments in spreadsheets.
3. Foreign Currency Translation Reserve (FCTR) Errors
For any Indian group with overseas subsidiaries, FCTR is a persistent source of audit findings. The requirement under IndAS 21 is clear: assets and liabilities of foreign operations are translated at the closing rate, income and expenses at the average rate for the period (or transaction date rates in certain cases), and the resulting exchange difference is recognized in Other Comprehensive Income and accumulated in a separate component of equity as the Foreign Currency Translation Reserve.
The challenge lies in execution. A group with subsidiaries in the US, UK, Thailand, and Brazil is managing four different exchange rate pairs, each with closing rates and average rates that must be applied consistently. Historical rates must be maintained for equity items and goodwill arising on acquisition of foreign operations. When a foreign subsidiary is disposed of, the cumulative FCTR related to that subsidiary must be reclassified from equity to profit or loss.
Common FCTR-Related Findings
Auditors typically flag three types of FCTR errors. The following table summarizes them:
| Finding Type | Description | IndAS Reference |
|---|---|---|
| Incorrect rate application | Using average rate for balance sheet items or closing rate for P&L items | IndAS 21, Para 39 |
| FCTR reconciliation failure | Opening FCTR + movement during the period does not reconcile to closing FCTR | IndAS 21, Para 41 |
| Disposal reclassification missed | Cumulative FCTR not reclassified to P&L upon disposal of foreign operation | IndAS 21, Para 48 |
Each of these findings is avoidable with proper infrastructure. eMerge maintains a foreign exchange rate master with support for multiple rate types (closing, average, historical). Currency translation is automated based on the rate type assigned to each account group, and the system calculates FCTR automatically, providing a full reconciliation trail. This means the consolidation team can verify FCTR movements before the auditor ever asks.
4. Missing or Incomplete Disclosures
Disclosure findings are particularly frustrating because they often do not reflect errors in the numbers themselves. The financial data may be correctly consolidated, and the statements may balance perfectly, yet auditors will raise findings if the required disclosures under IndAS 112 (Disclosure of Interests in Other Entities), IndAS 24 (Related Party Disclosures), or IndAS 108 (Operating Segments) are missing or incomplete.
The disclosure requirements for consolidated financial statements are substantially more extensive than those for standalone statements. IndAS 112 alone requires disclosure of significant judgments and assumptions made in determining the nature of interests in other entities, information about interests in subsidiaries including the composition of the group, details about NCI, and restrictions on the parent’s ability to access or use assets. Many finance teams treat disclosures as an afterthought, assembling them manually after the consolidation process is complete. This approach is unreliable because the information required for disclosures often sits in different parts of the consolidation process and must be pulled together deliberately.
The Disclosure Gap in Practice
Consider a group that acquires a new subsidiary during the quarter. The consolidation team correctly includes the subsidiary’s financials from the date of acquisition. The NCI is correctly computed. The goodwill is correctly recognized. Yet the auditor flags a finding because the notes to accounts do not include the consideration transferred, the acquisition-date fair value of each major class of assets acquired and liabilities assumed, or the revenue and profit of the subsidiary since the acquisition date, all of which are required under IndAS 103.
eMerge’s Noteify module is specifically designed to address this gap. It allows finance teams to create notes to accounts with columnar and textual content, with numbers directly linked to the consolidation reports. Placeholders dynamically pull prior period comparatives, and different note templates can be created for different entities or different reporting requirements. The result is a complete financial package, with consolidated and standalone balance sheets along with full notes, that can be exported to Excel as a ready-to-audit document.
5. Unsupported or Undocumented Adjustments
Every consolidation involves adjustments that do not originate from any individual subsidiary’s trial balance. Goodwill impairment, fair value adjustments on acquisition, elimination of unrealized profit on inventory, reclassification of investments from cost to equity method: these are all entries passed at the holding company level during consolidation. When these entries lack adequate documentation, supporting calculations, or approval trails, auditors will flag them as unsupported adjustments.
This finding is particularly damaging because it raises questions about the integrity of the entire consolidation process. If the auditor cannot trace a consolidation journal entry back to its supporting logic, they cannot form an opinion on whether the entry is appropriate. Under SA 230 (Audit Documentation) and SA 500 (Audit Evidence), the auditor is required to obtain sufficient appropriate audit evidence. If the finance team cannot provide it, the finding is inevitable.
The Traceability Requirement
The issue is compounded in organizations where consolidation is done in spreadsheets. Manual entries in Excel have no inherent audit trail. There is no record of who made the entry, when it was made, whether it was approved, or what the supporting calculation was. Even if the entry is correct, the absence of a trail is itself a finding.
In eMerge, consolidation entries are passed in a journal voucher format at the holding company level, and every entry carries a complete audit trail: who created it, when, who approved it, and what narrative was provided. Audit reports can be generated that show every adjustment, its classification, and its trail. This level of traceability is what auditors look for, and it is what prevents “unsupported adjustment” from appearing in the audit findings report.
6. Inconsistent Application of Accounting Policies Across Entities
IndAS 110, Para 19 requires that consolidated financial statements be prepared using uniform accounting policies for like transactions and other events in similar circumstances. When subsidiaries within a group apply different accounting policies, whether for depreciation methods, revenue recognition thresholds, or inventory valuation, the consolidation team must make adjustments to align them with the group’s accounting policies before consolidation.
Auditors frequently find that these alignment adjustments are either missing or inconsistently applied. A subsidiary in one jurisdiction may be depreciating assets on a straight-line basis while the group policy is written-down value. If the consolidation team does not pass a regrouping entry to align the subsidiary’s figures to the group policy, the consolidated statements will reflect mixed accounting policies, which is a direct violation of IndAS 110.
For a broader perspective on where IndAS-specific consolidation errors occur, including policy inconsistencies, refer to our discussion of common IndAS consolidation mistakes.
How to Prevent Common Audit Findings in Consolidated Statements Proactively
Preventing audit findings requires moving from a reactive approach, where the team fixes what the auditor finds, to a proactive approach, where the consolidation infrastructure itself prevents errors from occurring. This shift depends on three structural changes.
Centralized Consolidation Infrastructure with Distributed Execution
The consolidation process must allow subsidiaries to upload their data, map their trial balances, and confirm intercompany transactions from their locations, while the holding company’s finance team maintains centralized control over the hierarchy, the common chart of accounts, elimination rules, and consolidation entries. This distributed model is essential for groups operating across time zones, and it is exactly how eMerge is designed to operate: web-based, collaborative, with role-based access that ensures each user sees and does only what they are authorized to do.
Locking Mechanisms That Enforce Process Discipline
One of the most common causes of audit findings is data changes made after consolidation has begun. A subsidiary uploads a revised trial balance after eliminations have already been computed, and suddenly the numbers do not tie. eMerge’s corporate lock feature allows the administrator to freeze all entity data before consolidation begins. Any subsequent changes require administrator authorization, ensuring that the consolidated numbers are based on a stable and verified data set.
Built-In Audit Trails and Drill-Down Capability
Every figure in the consolidated financial statements should be traceable back to its source. This means drill-down capability from the consolidated balance sheet to the entity-level trial balance, and from there to the general ledger. It means every journal entry, every elimination, every consolidation adjustment carries a record of who made it and when. When audit teams can access this level of detail within the system, findings related to unsupported adjustments and unexplained variances disappear.
A Proactive Prevention Framework
The following table summarizes each finding category and the corresponding preventive measure:
| Common Audit Finding | Root Cause | Preventive Measure |
|---|---|---|
| Incomplete eliminations | Manual reconciliation, decentralized data | Workflow-based intercompany reconciliation with entity-level confirmation |
| NCI miscalculations | Outdated holding percentages, manual formulas | Hierarchy-linked automated NCI computation with formula-driven reports |
| FCTR errors | Incorrect rate application, no reconciliation trail | Rate master with type-based assignment and automatic FCTR reconciliation |
| Missing disclosures | Disclosures treated as afterthought, assembled manually | Integrated notes-to-accounts module linked to consolidation data |
| Unsupported adjustments | No audit trail for consolidation entries | Journal voucher format with full audit trail and approval workflow |
| Inconsistent accounting policies | No mechanism to enforce uniform policies | Common report format with regrouping entries at entity level |
Conclusion
Audit findings in consolidated financial statements are rarely the result of incompetence. They are the result of process gaps, infrastructure limitations, and the sheer complexity of managing financial data across dozens of entities with different systems, currencies, and reporting requirements. The six findings discussed here, incomplete eliminations, NCI miscalculations, FCTR errors, missing disclosures, unsupported adjustments, and policy inconsistencies, are predictable. And because they are predictable, they are preventable.
Finance teams that invest in consolidation infrastructure designed specifically for this purpose find that audit cycles become shorter, findings become fewer, and the team’s time shifts from firefighting to analysis. eMerge has been enabling this shift for large Indian and multinational groups for years, with implementations that go live in six to eight weeks and match published reports to the last penny.
If your organization is dealing with recurring audit findings in its consolidated statements, a structured walkthrough of your consolidation process can reveal exactly where the gaps are. Schedule a discussion with the eMerge team to understand how your specific consolidation challenges can be addressed systematically.
