Showing posts with label events after reporting date. Show all posts
Showing posts with label events after reporting date. Show all posts

Thursday, June 16, 2016

Audit Method: Subsequent Events

Subsequent Events as defined in ISA 560 are Events occurring between the date of the financial statements and the date of the auditor’s report, and facts that become known to the auditor after the date of the auditor’s report.”

The objectives of the auditor for considering subsequent events are:

(a) To obtain sufficient appropriate audit evidence about whether events occurring between the date of the financial statements and the date of the auditor’s report that require adjustment of, or disclosure in, the financial statements are appropriately reflected in those financial statements in accordance with the applicable financial reporting framework; and
(b) To respond appropriately to facts that become known to the auditor after the date of the auditor’s report, that, had they been known to the auditor at that date, may have caused the auditor to amend the auditor’s report.

Perform audit procedures designed to obtain sufficient appropriate audit evidence that all events up to the date of the audit report that may require adjustment of, or disclosure in, the financial statements have been identified

·   Consider changes in the areas which may affect the financial statements and other information in the annual report such as banking arrangements, currency and interest rates, key markets, key products, customers or vendors, key management or employees, government regulation or policy and the ratio of orders to sales and cash receipts and the position of the order book.

·   Consider other significant knowledge gained, for example press comment, internal audit reports, changes in client trading patterns, changes in laws or regulations, currency devaluations, major fires or catastrophes, or technology failures (e.g. computer operations failures) and security incidents.

·   Evaluate procedures management has established to ensure that subsequent events are identified.

·   Inquire of management and, where appropriate, those charged with governance as to whether any subsequent events have occurred which might affect the financial statements.

·   Review the results of the review of minutes of meetings of the entity’s owners, management and those charged with governance, including audit, executive and other Board committees since the balance sheet date.

·   Consider reviewing invoices from lawyers received after the year-end to determine whether any litigation, claims or assessments exist that were not previously identified in our analysis of legal expenses and other procedures.

·   Review the latest available interim financial statements and, as considered necessary and appropriate, budgets, cash flow forecasts and other related management reports. Consider whether they reveal any adverse trends or significant movements in balance sheet headings compared to the audited financial statements. Consider whether the management information is reliable.

Practice
Where a material subsequent event has been identified, determine whether it is reflected in the financial statements in accordance with the applicable financial reporting framework by adequate disclosure and, where appropriate, adjustment of the account balances and transactions affected. Consider also its effect on the audit report.

Tuesday, October 11, 2011

Audit Procedures: Subsequent Events


The subject of subsequent events is always relevant both for accounting students and professionals. The risk is quite high due to broad definition of “adjusting event” category in IAS 10:
     “An event after the reporting period that provides further evidence of conditions that existed at the end of the reporting period, including an event that indicates that the going concern assumption in relation to the whole or part of the enterprise is not appropriate.
The assessor of ACCA F8 paper, Steve Collings, wrote good article on this issue and I am going to highlight some moments and give examples in this post

Going Concern – No Conditions
Insolvent?
Going Concern issue!
As could be noticed from definition IFRS requires that some conditions should preexist for event to be adjusting. For the purpose of provision accruals IAS 37 specifies those conditions:
  • Reliable estimation of obligation;
  •  Obligation (conditions) whether constructive or legal existed at year end;
  • Transfers of money are expected with regards to this event.

For example, the CEO of well-known oil company gave a promise to clean any mess caused by his company on the 31st of December. The oil spill happened on 5th of January and as a result all expenditures required to clean the oil should be undertaken by company no matter if there is any special legislation.
Quite another situation with going concern issue. No special conditions required to acknowledge that company is not going concern anymore. The roots of this in concept of IFRS which assumes that observation of standards gives true and fair results only if company is going concern.

Examples
In my practice I had some issues related with subsequent events. For example, warehouse full of food (inventory) was burned. The issue was that it happened someday around the year end, it happened near the Siberian forest so it was difficult to access the warehouse. Finally, after thorough investigation it was found out that it happened after the year end, the matter was material so I had to disclose this issue in the notes to inventory section.
The other issue was as follows. My client has signed the management representation letter where he confirmed that he had disclosed all information, including environmental matters. Meanwhile, after a week the representation letter was signed but before the audit report signature it got known that local authorities started the investigation regarding recent air pollution committed by company. Eventually, the pollution had immaterial implications, but there are several lessons to be learned from that. First, the management representation letter should be signed the date closest to audit report, but bear in mind that this could become an issue incase of multilocation audit. It requires additional coordination efforts to make management of subsidiary sign the representation letter the date nearest to the date of audit report. Second, the procedures requiring review of outside information (newspapers, journals, databases) about the client should not be ignored, to be done thoroughly and client should be questioned in case of material issues. Third, even if the news/management answers evidently show that conditions did not exist at the year end, there is still necessity to check reason of pollution (in my example), whether there was a concealment with management involvement.
Timeline
I provide you with timeline of dates relevant for auditor in detection of events affecting audit procedures and actions to be undertaken in accordance with ISA 560.