Guide to Using International Standards on Auditing in - IFAC

Guide to Using International Standards on Auditing in - IFAC Guide to Using International Standards on Auditing in - IFAC

17.03.2014 Views

146 ong>Guideong> ong>toong> ong>Usingong> ong>Internationalong> ong>Standardsong> on Auditing in the Audits of Small- and Medium-Sized Entities Volume 1—Core Concepts Paragraph # ISA Objective(s) 550.9 The objectives of the audiong>toong>r are: (a) Irrespective of whether the applicable financial reporting framework establishes relatedparty requirements, ong>toong> obtain an understanding of related-party relationships and transactions sufficient ong>toong> be able: (i) To recognize fraud risk facong>toong>rs, if any, arising from related-party relationships and transactions that are relevant ong>toong> the identification and assessment of the risks of material misstatement due ong>toong> fraud; and (ii) To conclude, based on the audit evidence obtained, whether the financial statements, insofar as they are affected by those relationships and transactions: a. Achieve fair presentation (for fair presentation frameworks); or b. Are not misleading (for compliance frameworks); and (b) In addition, where the applicable financial reporting framework establishes related-party requirements, ong>toong> obtain sufficient appropriate audit evidence about whether related-party relationships and transactions have been appropriately identified, accounted for and disclosed in the financial statements in accordance with the framework. Paragraph # Relevant Extracts from ISAs 550.10 For purposes of the ISAs, the following terms have the meanings attributed below: (a) Arm’s length transaction—A transaction conducted on such terms and conditions as between a willing buyer and a willing seller who are unrelated and are acting independently of each other and pursuing their own best interests. (b) Related-party—A party that is either: (Ref: Para. A4-A7) (i) A related-party as defined in the applicable financial reporting framework; or (ii) Where the applicable financial reporting framework establishes minimal or no relatedparty requirements: a. A person or other entity that has control or significant influence, directly or indirectly through one or more intermediaries, over the reporting entity; b. Another entity over which the reporting entity has control or significant influence, directly or indirectly through one or more intermediaries; or c. Another entity that is under common control with the reporting entity through having: i. Common controlling ownership; ii. Owners who are close family members; or iii. Common key management. However, entities that are under common control by a state (i.e., a national, regional or local government) are not considered related unless they engage in significant transactions or share resources ong>toong> a significant extent with one another. 12.1 Overview As related parties are not independent of each other, there are often higher risks of material misstatement through related-party transactions than through transactions with unrelated parties. Consequently, financial reporting frameworks often contain accounting and disclosure requirements regarding related-party transactions and balances. These requirements are intended ong>toong> provide financial statement users with an understanding of the nature of these transactions/balances and the actual or potential effects.

147 ong>Guideong> ong>toong> ong>Usingong> ong>Internationalong> ong>Standardsong> on Auditing in the Audits of Small- and Medium-Sized Entities Volume 1—Core Concepts Some of the potential risk facong>toong>rs with regard ong>toong> related-party transactions are set out below. Exhibit 12.1-1 Overly Complex Transactions Relationships and Transactions not Identified Not Conducted in the Normal Course of Business Description Related parties may operate through an extensive and complex range of relationships and structures. • Related-party relationships may be concealed, as they present a greater opportunity for collusion, concealment, or manipulation by management. • The entity’s information systems may be ineffective at identifying or summarizing transactions and outstanding balances between the entity and its related parties. • Management may be unaware of the existence of all related-party relationships and transactions. Related-party transactions may not be conducted under normal market terms and conditions such as above; below fair values; or even with no exchange of consideration at all. Management is responsible for the identification and disclosure of related parties and accounting for the transactions. This responsibility requires management ong>toong> implement adequate internal control ong>toong> ensure that transactions with related parties are appropriately identified and recorded in the information system, and disclosed in the financial statements. The audiong>toong>r is responsible for maintaining an alertness for related-party information when reviewing records or documents during the audit. This includes the inspection of certain key documents, but does not require an extensive investigation of records and documents ong>toong> specifically identify related parties. In smaller entities, these procedures are likely ong>toong> be less sophisticated and informal. Management may not readily have information about related parties (the accounting systems are unlikely ong>toong> have been designed ong>toong> identify related parties), so the audiong>toong>r may need ong>toong> make inquiries and review accounts with specific parties, etc. beyond the accounting records and disclosures in the accounts. Financial Reporting Frameworks Because related parties are not independent of each other, many financial reporting frameworks establish specific accounting and disclosure requirements for related-party relationships, transactions, and balances. This enables the users of financial statements ong>toong> understand their nature and actual or potential effects on the financial statements. Where the applicable financial reporting framework establishes requirements for related-party accounting and disclosure, the audiong>toong>r has a responsibility ong>toong> perform audit procedures ong>toong> identify, assess, and respond ong>toong> the risks of material misstatement arising from the entity’s failure ong>toong> appropriately account for or disclose related-party relationships, transactions, or balances in accordance with the requirements of the framework. Where the applicable financial reporting framework establishes minimal or no related-party requirements, the audiong>toong>r still needs ong>toong> obtain a sufficient understanding of the entity’s related-party relationships and transactions ong>toong> be able ong>toong> conclude whether the financial statements, insofar as they are affected by those relationships and transactions:

147<br />

<str<strong>on</strong>g>Guide</str<strong>on</strong>g> <str<strong>on</strong>g>to</str<strong>on</strong>g> <str<strong>on</strong>g>Us<strong>in</strong>g</str<strong>on</strong>g> <str<strong>on</strong>g>Internati<strong>on</strong>al</str<strong>on</strong>g> <str<strong>on</strong>g>Standards</str<strong>on</strong>g> <strong>on</strong> <strong>Audit<strong>in</strong>g</strong> <strong>in</strong> the Audits of Small- and Medium-Sized Entities Volume 1—Core C<strong>on</strong>cepts<br />

Some of the potential risk fac<str<strong>on</strong>g>to</str<strong>on</strong>g>rs with regard <str<strong>on</strong>g>to</str<strong>on</strong>g> related-party transacti<strong>on</strong>s are set out below.<br />

Exhibit 12.1-1<br />

Overly Complex<br />

Transacti<strong>on</strong>s<br />

Relati<strong>on</strong>ships and<br />

Transacti<strong>on</strong>s not<br />

Identified<br />

Not C<strong>on</strong>ducted <strong>in</strong><br />

the Normal Course<br />

of Bus<strong>in</strong>ess<br />

Descripti<strong>on</strong><br />

Related parties may operate through an extensive and complex range of relati<strong>on</strong>ships<br />

and structures.<br />

• Related-party relati<strong>on</strong>ships may be c<strong>on</strong>cealed, as they present a greater<br />

opportunity for collusi<strong>on</strong>, c<strong>on</strong>cealment, or manipulati<strong>on</strong> by management.<br />

• The entity’s <strong>in</strong>formati<strong>on</strong> systems may be <strong>in</strong>effective at identify<strong>in</strong>g or summariz<strong>in</strong>g<br />

transacti<strong>on</strong>s and outstand<strong>in</strong>g balances between the entity and its related parties.<br />

• Management may be unaware of the existence of all related-party relati<strong>on</strong>ships<br />

and transacti<strong>on</strong>s.<br />

Related-party transacti<strong>on</strong>s may not be c<strong>on</strong>ducted under normal market terms<br />

and c<strong>on</strong>diti<strong>on</strong>s such as above; below fair values; or even with no exchange of<br />

c<strong>on</strong>siderati<strong>on</strong> at all.<br />

Management is resp<strong>on</strong>sible for the identificati<strong>on</strong> and disclosure of related parties and account<strong>in</strong>g for the<br />

transacti<strong>on</strong>s. This resp<strong>on</strong>sibility requires management <str<strong>on</strong>g>to</str<strong>on</strong>g> implement adequate <strong>in</strong>ternal c<strong>on</strong>trol <str<strong>on</strong>g>to</str<strong>on</strong>g> ensure that<br />

transacti<strong>on</strong>s with related parties are appropriately identified and recorded <strong>in</strong> the <strong>in</strong>formati<strong>on</strong> system, and<br />

disclosed <strong>in</strong> the f<strong>in</strong>ancial statements.<br />

The audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r is resp<strong>on</strong>sible for ma<strong>in</strong>ta<strong>in</strong><strong>in</strong>g an alertness for related-party <strong>in</strong>formati<strong>on</strong> when review<strong>in</strong>g records<br />

or documents dur<strong>in</strong>g the audit. This <strong>in</strong>cludes the <strong>in</strong>specti<strong>on</strong> of certa<strong>in</strong> key documents, but does not require<br />

an extensive <strong>in</strong>vestigati<strong>on</strong> of records and documents <str<strong>on</strong>g>to</str<strong>on</strong>g> specifically identify related parties.<br />

In smaller entities, these procedures are likely <str<strong>on</strong>g>to</str<strong>on</strong>g> be less sophisticated and <strong>in</strong>formal. Management may not<br />

readily have <strong>in</strong>formati<strong>on</strong> about related parties (the account<strong>in</strong>g systems are unlikely <str<strong>on</strong>g>to</str<strong>on</strong>g> have been designed <str<strong>on</strong>g>to</str<strong>on</strong>g><br />

identify related parties), so the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r may need <str<strong>on</strong>g>to</str<strong>on</strong>g> make <strong>in</strong>quiries and review accounts with specific parties,<br />

etc. bey<strong>on</strong>d the account<strong>in</strong>g records and disclosures <strong>in</strong> the accounts.<br />

F<strong>in</strong>ancial Report<strong>in</strong>g Frameworks<br />

Because related parties are not <strong>in</strong>dependent of each other, many f<strong>in</strong>ancial report<strong>in</strong>g frameworks establish<br />

specific account<strong>in</strong>g and disclosure requirements for related-party relati<strong>on</strong>ships, transacti<strong>on</strong>s, and balances.<br />

This enables the users of f<strong>in</strong>ancial statements <str<strong>on</strong>g>to</str<strong>on</strong>g> understand their nature and actual or potential effects <strong>on</strong><br />

the f<strong>in</strong>ancial statements.<br />

Where the applicable f<strong>in</strong>ancial report<strong>in</strong>g framework establishes requirements for related-party account<strong>in</strong>g<br />

and disclosure, the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r has a resp<strong>on</strong>sibility <str<strong>on</strong>g>to</str<strong>on</strong>g> perform audit procedures <str<strong>on</strong>g>to</str<strong>on</strong>g> identify, assess, and resp<strong>on</strong>d<br />

<str<strong>on</strong>g>to</str<strong>on</strong>g> the risks of material misstatement aris<strong>in</strong>g from the entity’s failure <str<strong>on</strong>g>to</str<strong>on</strong>g> appropriately account for or disclose<br />

related-party relati<strong>on</strong>ships, transacti<strong>on</strong>s, or balances <strong>in</strong> accordance with the requirements of the framework.<br />

Where the applicable f<strong>in</strong>ancial report<strong>in</strong>g framework establishes m<strong>in</strong>imal or no related-party requirements,<br />

the audi<str<strong>on</strong>g>to</str<strong>on</strong>g>r still needs <str<strong>on</strong>g>to</str<strong>on</strong>g> obta<strong>in</strong> a sufficient understand<strong>in</strong>g of the entity’s related-party relati<strong>on</strong>ships and<br />

transacti<strong>on</strong>s <str<strong>on</strong>g>to</str<strong>on</strong>g> be able <str<strong>on</strong>g>to</str<strong>on</strong>g> c<strong>on</strong>clude whether the f<strong>in</strong>ancial statements, <strong>in</strong>sofar as they are affected by those<br />

relati<strong>on</strong>ships and transacti<strong>on</strong>s:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!