Annual Audit Manual
COPYRIGHT NOTICE — This document is intended for internal use. It cannot be distributed to or reproduced by third parties without prior written permission from the Copyright Coordinator for the Office of the Auditor General of Canada. This includes email, fax, mail and hand delivery, or use of any other method of distribution or reproduction. CPA Canada Handbook sections and excerpts are reproduced herein for your non-commercial use with the permission of The Chartered Professional Accountants of Canada (“CPA Canada”). These may not be modified, copied or distributed in any form as this would infringe CPA Canada’s copyright. Reproduced, with permission, from the CPA Canada Handbook, The Chartered Professional Accountants of Canada, Toronto, Canada.
2351 Consideration in auditing the consolidation process
Apr-2018
In This Section
Work to Perform on the Consolidation Process
Consolidation section of the audit file
Component Financial Information
Procedures regarding Intercompany Balances and Transactions not eliminated on consolidation
Overview
This section discusses:
- The responsibility to design and perform audit procedures on the consolidation process
- Audit procedures to be performed with regards to the risk of material misstatement in the consolidation process
- Consolidation section of the audit file
CAS Requirement
In accordance with CAS 600.17, the group engagement team obtains an understanding of group-wide controls and the consolidation process, including the instructions issued by group management to components. In accordance with paragraph 25, the group engagement team, or component auditor at the request of the group engagement team, tests the operating effectiveness of group-wide controls if the nature, timing and extent of the work to be performed on the consolidation process are based on an expectation that group-wide controls are operating effectively, or if substantive procedures alone cannot provide sufficient appropriate audit evidence at the assertion level (CAS 600.32).
The group engagement team shall design and perform further audit procedures on the consolidation process to respond to the assessed risks of material misstatement of the group financial statements arising from the consolidation process. This shall include evaluating whether all components have been included in the group financial statements (CAS 600.33).
The group engagement team shall evaluate the appropriateness, completeness and accuracy of consolidation adjustments and reclassifications, and shall evaluate whether any fraud risk factors or indicators of possible management bias exist (CAS 600.34).
The group engagement team shall determine whether the financial information identified in the component auditor’s communication (see paragraph 41(c)) is the financial information that is incorporated in the group financial statements (CAS 600.36).
CAS Guidance
The consolidation process may require adjustments to amounts reported in the group financial statements that do not pass through the usual transaction processing systems, and may not be subject to the same internal controls to which other financial information is subject. The group engagement team’s evaluation of the appropriateness, completeness and accuracy of the adjustments may include (CAS 600.A56):
- evaluating whether significant adjustments appropriately reflect the events and transactions underlying them;
- determining whether significant adjustments have been correctly calculated, processed and authorized by group management and, where applicable, by component management;
- determining whether significant adjustments are properly supported and sufficiently documented; and
- checking the reconciliation and elimination of intra-group transactions and unrealized profits, and intra-group account balances.
OAG Guidance
When consolidation adjustments such as those discussed in CAS 600.A56 relate to a component, the group engagement team needs to consider communicating adjustments to component auditors as appropriate. Such adjustments may include, for example, adjustments made at group level to align accounting policies between components, journal entries that should have been pushed-down to the component, or adjustments suggested by the component auditor but booked only at the group level.
Testing of consolidation adjustments may sometimes be performed before the entity completed the preparation of its financial statements. In such circumstances, the group engagement team needs to review the final consolidation schedules for any significant differences from the consolidation schedules initially tested, as any such changes are journal entries made in the preparation of the financial statements, and therefore, according to CAS 330.20(b) (OAG Audit 9031) and CAS 240.33 (OAG Audit 5509) need to be audited. In doing so, we may use technological solutions to identify any differences between the two sets of consolidated schedules, we may obtain from management a complete list of all journal entries booked between the schedules we tested initially and the final schedules and agree them to the differences between the schedules, or any combination of the two.
OAG Guidance
The consolidation section of the audit file normally includes (unless included elsewhere in the audit file):
- Copies of the financial statements and audit reports of components where work was performed in connection with the group audit.
- Evidence of tie out of component audit reporting package with the financial statements.
- Documentation of our review of the component auditors’ communications.
- Notes of accounting policies and any major variations in policy between consolidated entities. This is best documented as carry-forward information.
- A copy of the consolidated financial statements and significant supporting working papers showing the aggregation of the financial statements of the parent and the components’ financial statements.
- Details of consolidation journal entries, including intercompany eliminations. Recurring consolidating journal entries may be documented as carry-forward information.
CAS Requirement
If the financial information of a component has not been prepared in accordance with the same accounting policies applied to the group financial statements, the group engagement team shall evaluate whether the financial information of that component has been appropriately adjusted for purposes of preparing and presenting the group financial statements (CAS 600.35).
If the group financial statements include the financial statements of a component with a financial reporting period-end that differs from that of the group, the group engagement team shall evaluate whether appropriate adjustments have been made to those financial statements in accordance with the applicable financial reporting framework (CAS 600.37).
OAG Guidance
CASs require us to perform substantive procedures for each material class of transactions, account balances and disclosure. Therefore, if there are material intercompany balances that are not eliminated on consolidation (either at the group or component level), we need to test them substantively in addition to any controls testing performed.
OAG Guidance
The guidance above outlines the procedures we would perform in relation to the consolidation process, including elimination of intercompany balances and transactions. However, in addition to work performed on the consolidation process, we also need to consider intercompany balances that are not eliminated on consolidation and therefore may not be covered by the procedures listed above.
For example, group entity financial statements may include significant receivables or payables from/to a component accounted for by the equity method, which would not eliminate upon consolidation. These balances and transactions need to be tested substantively by either the group engagement team or the component auditor on the group engagement team's behalf. Similarly, if a component auditor is engaged to perform an audit of the component's standalone financial statements, the component financial statements would ordinarily include intercompany balances and transactions, which need to be tested substantively (if material) by the component auditor for the purposes of the standalone component audit. This block provides guidance on procedures we would perform in relation to such non-eliminated intercompany balances and transactions in situations like those described above. Such procedures would be considered in addition to the work on consolidation performed as part of the group audit.
Group and component auditors need to consider if sufficient appropriate evidence has been obtained with regards to material intercompany balances and transactions not eliminated on consolidation. CASs require us to perform substantive procedures for each material class of transactions, account balance and disclosure (see CAS 330.18). Therefore, if there are material intercompany balances that are not eliminated on consolidation (recorded at either the group or component level), either the group engagement team or component auditors need to test them substantively in addition to any controls testing performed.
Procedures to be performed to obtain sufficient appropriate audit evidence regarding intercompany balances and transactions not eliminated on consolidation depend on materiality, results of the risk assessment, group and component controls over intercompany processes and other specific circumstances of the engagement. For example, more extensive substantive procedures would ordinarily be performed if there is a significant risk related to intercompany balances or transactions and the amounts of such balances and transactions significantly exceed the relevant materiality level. Group and component auditors use their professional judgment when developing the testing plan over intercompany balances and transactions and consider the relevant factors that may impact this judgment.
The engagement team needs to have an understanding of the purpose of significant intercompany transactions and consider if significant transactions outside the entity's normal course of business have occurred in order to plan to address the related risks, as appropriate (see OAG Audit 7533 for guidance on testing significant related party transactions outside the entity's normal course of business).
Controls Over Intercompany Processes
As part of developing evidence gathering activities regarding intercompany balances and transactions not eliminated on consolidation, engagement teams would consider results of evaluation of the controls over intercompany processes (both group-wide and component level controls, where appropriate), as results of controls evaluation would affect the nature, timing and extent of further procedures. When we plan to rely on controls over intercompany processes, our test plan would also need to include testing the operating effectiveness of such controls. For example, when intercompany balances and transactions are reconciled at the group entity level, the group engagement team may evaluate and test related group-wide controls to determine if they operate effectively and share the results of such testing with component auditors. When each component is responsible for recording and reconciling its own intercompany balances and transactions, evaluation and testing of corresponding controls (where we plan to rely on controls) would be performed by component auditors.
Recoverability of Intercompany Receivables Not Eliminated on Consolidation
Consider if non-eliminated intercompany receivables are recoverable, e.g., by inquiring of the component and group management and performing other procedures as appropriate. Sometimes the decision regarding settlement of intercompany balances is made by group management and therefore even if the counterparty component represents a financially viable entity, it may be necessary to obtain evidence regarding group management plans to determine if the receivables will be recovered.
Procedures Summary
The following table summarizes procedures that a component auditor may consider when developing a plan for obtaining evidence about material intercompany balances and transactions included in component financial statements (i.e., not eliminated on consolidation). The first column outlines various testing procedures and the second column indicates if such procedures are expected to be effective and efficient in specific circumstances of the engagement. For example, it illustrates that obtaining a schedule of intercompany balances directly from the group engagement team would normally only be appropriate when the group and component entities have the same period end. The component auditor applies professional judgment when deciding which substantive audit procedures included in the table below may need to be performed. The list of audit procedures is not exhaustive and therefore component auditors need to consider if other procedures may be more effective and efficient in the specific engagement circumstances.
Group Entity and Component Have the Same Period End |
Group Entity and Component Have Different Period Ends |
|
Obtain an understanding of the business rationale of the intercompany transactions and evaluate relevant controls |
Yes |
Yes |
Perform testing of the operating effectiveness of controls over the intercompany sub-process (if applicable) |
Yes |
Yes |
Obtain and review schedule of intercompany balances from the group engagement team (Note 1) |
Yes |
No |
Review a confirmation obtained by management from the management of the counterparty component and test reconciling items (Note 2) |
Yes |
Yes |
Send confirmation request to the counterparty component auditor (Note 3) |
Yes |
No |
Send confirmation request to the group management |
Yes |
Yes |
Send confirmation request to the counterparty component management (Note 4) |
Yes |
Yes |
Perform substantive testing of the intercompany balances and transactions |
Substantive testing of intercompany balances and transactions by tracing to supporting documents |
|
Review the formal agreements |
Where a formal agreement exists supporting a balance or transaction, obtain and review this in order to confirm that the balance or transaction(s) has been recorded in accordance with the formal agreement. |
|
Test foreign currency translation and recognized foreign exchange income (loss) |
Where applicable, agree the rates used for translation of the intercompany balances or transactions with external sources. Check that the recognition of foreign exchange income (loss) is in line with the requirements of the relevant financial reporting framework. |
|
Review intercompany suspense accounts |
Where applicable, review suspense accounts for entries related to intercompany balances and transactions and consider testing the recorded entries by tracing to supporting documents. |
|
Evaluate potential tax risks |
Consider if there are potential tax risks related to intercompany balances and transactions. For instance, lack of proper documentation supporting intercompany transactions (e.g., those that make up the balance at period end) may result in some tax exposure. Also, specific territory regulations may be in place regarding transfer pricing used between the entities within the group. Evaluate such potential tax exposure and develop response to the related risks, engaging tax specialists as appropriate. |
(Note 1) As explained in OAG Audit 2342, OAG Audit teams acting as group engagement teams need to consider communicating to OAG Audit teams acting as component auditors a schedule of intercompany balances (or otherwise facilitate access to such information) and procedures performed by the group engagement team over such balances and transactions. This communication will provide OAG Audit teams acting as component auditors with evidence over intercompany balances and transactions recorded in the group entity's financial statements and make the component auditor procedures performed for the group and component audit purposes (providing the group entity and components have the same period end) more effective and efficient. The schedule of intercompany balances would be agreed to the group entity's financial records by the group engagement team.
(Note 2) Where a schedule referred to above is not provided by the group engagement team, appropriate audit evidence for the component auditor may come in the form of testing an intercompany confirmation, obtained by the management of the component under audit from the management of the counterparty component with whom the balance is held or transaction(s) undertaken. As the inherent risk and significance of the balance under consideration increase, the extent of necessary evidence increases as well and the more likely it is that other procedures may need to be performed in addition to testing the intercompany confirmation.
This procedure would normally be effective only when management of both components is sufficiently independent from each other. In particular, management of the component providing the confirmation cannot be accountable for the balances recorded at the component requesting the confirmation (which may be the case when the accounting function is centralized in a shared service center). Otherwise there may be an increased risk of fraud and such procedures may be not effective. Consider if there is a potential risk of inadequate segregation of management duties before performing this procedure. Note that similar considerations would generally apply when the confirmation is obtained from the group management.
(Note 3) The component auditor may also seek confirmation of significant intercompany transactions or balances from the counterparty component auditors. This would normally be most effective in situations when the component from which the confirmation is sought has the same period end. Such confirmations are facilitated in a shared service center environment, where the component engagement team may well have access to the records of both of the entities that are parties to the intercompany balances. Consider the understanding of the counterparty component auditors, previous experience of working with them and other relevant factors when determining whether requesting a confirmation from the counterparty component auditor would be effective and efficient.
(Note 4) Note that if an intercompany balance not eliminated on consolidation represents a receivable, there is a rebuttable presumption that requesting external confirmations will be performed (unless specific criteria apply), in line with the accounts receivable confirmations policy in OAG Audit 7055. We may rebut the presumption to confirm when accounts receivable are irrelevant or immaterial, when the use of confirmations would be ineffective, or when based on our assessment of risk and assurance obtained from controls testing, the combined assessed level of inherent and control risk over applicable assertions is low. Refer to OAG Audit 7055 for further guidance. When a confirmation regarding the intercompany balances and transactions has been obtained using other procedures listed above (e.g., a confirmation was obtained from the group engagement team), requesting external confirmations from the component management may not be necessary. Also note that requesting a confirmation from the counterparty component management would normally be effective only when management of both components is sufficiently independent from each other (as explained in Note 2 above).