University of Sydney · FACULTY OF ACCOUNTING

ACCT6007 Chap.2 Reporting, Subsequent Events and Assertions

- one subject, every graph, every model, every mark
6 Chapters4-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 2 of 7 · ACCT6007

Reporting, Subsequent Events and Assertions

This chapter connects the financial-reporting timeline to the auditor's changing responsibilities and treats assertions as testable management claims. Subsequent events are classified by the condition that existed at reporting date, not simply by discovery date.

Assertion work focuses on direction: recorded items are tested outward for existence or occurrence, while source evidence is traced inward when completeness is at risk. An adjusting event supplies later evidence about a year-end condition and can change recognised amounts. A genuinely new later condition is non-adjusting, though material disclosure may still be required.

Before the audit report date, the auditor actively performs procedures such as enquiry, reading minutes and reviewing later interim information. Responsibility changes after signing and again after issue, so a good answer locates the fact on the timeline before stating action. Assertions prevent vague procedures.

Occurrence and existence test whether recorded items are real; completeness tests what may be missing; cut-off tests the period; valuation tests the amount; rights and obligations test the entity's relationship to a balance; and presentation considers classification and disclosure. A named starting population and direction reveal what a proposed procedure can actually prove.

Presentation and disclosure remain relevant even when recognition and measurement are correct. A debt balance may be genuine and accurate but classified in a way that distorts liquidity; a material later event may be absent from the notes even when year-end numbers require no adjustment. Procedure language should identify the source, selection, date range, attribute and purpose.

When later facts emerge, consider governance minutes, legal developments and financing evidence. The chapter combines timing and assertions: locate the condition, identify the statement effect, choose the claim at risk and design evidence that can expose the suspected error.

In this chapter

What this chapter covers

  • 01

    True and fair view

  • 02

    Reporting and audit dates

  • 03

    Adjusting subsequent events

  • 04

    Non-adjusting disclosure

  • 05

    Transaction assertions

  • 06

    Balance assertions

Worked example · free

Classify a later customer failure

Q [4 marks]. The step weighting is an AskSia study allocation, not a University marking scheme. A customer fails after year end. Explain when the receivable estimate should be adjusted.
The line moves from reporting date to audit report and issue; notice that the auditor’s active search and later response change across those responsibility dateThe line moves from reporting date to audit report and issue; notice that the auditor’s active search and later response change across those responsibility dates.Reporting dateAudit reportIssue to usersLater discovery
The line moves from reporting date to audit report and issue; notice that the auditor’s active search and later response change across those responsibility dates.
  • 1Identify the customer's condition at reporting date.
  • 1Decide whether later failure confirms an existing impairment condition.
  • 1Adjust measurement if existing; otherwise consider material non-adjusting disclosure.
  • 1Evaluate evidence, materiality and the auditor's responsibility date.
Adjustment is appropriate when later failure confirms financial difficulty already present at year end. A genuinely new later condition is non-adjusting, though material disclosure may be needed.
Sia tip — Do not let the discovery date replace the date when the underlying condition existed.
Glossary

Key terms

Adjusting event
Later evidence about a condition existing at reporting date.
Non-adjusting event
A later event arising from a new post-reporting-date condition.
Occurrence assertion
The claim that recorded transactions actually occurred.
Completeness assertion
The claim that all items requiring recognition were recorded.
Cut-off assertion
The claim that transactions were recorded in the correct period.
Valuation assertion
The claim that balances are recorded at appropriate amounts.
FAQ

Reporting, Subsequent Events and Assertions FAQ

How do adjusting events differ from non-adjusting events?

An adjusting event provides more evidence about a condition existing at reporting date, so recognised amounts may change. A non-adjusting event arises from a later condition and normally affects disclosure rather than the year-end measurement.

Why does audit-procedure direction matter?

Direction determines the error a procedure can find. Starting with recorded items and vouching outward helps test whether entries are real. Starting with source evidence and tracing inward can reveal items omitted from the accounting records.

Can one account have several assertions at risk?

Yes. Receivables may be fictitious, incomplete, wrongly valued or presented poorly. The scenario decides the primary assertion. State the possible misstatement and direction before choosing the label, then design a procedure for that precise risk.

Study strategy

Exam move

Build two cards for each assertion: one overstatement or understatement example and one directional procedure. Place reporting date, audit report date and issue date on a timeline, then classify fresh events by the underlying condition date. For every answer, add the accounting effect and the auditor's action rather than stopping at a label.

Use supplier invoices, receiving reports, dispatch records, bank evidence and contracts as starting populations and say which omissions or fictitious entries each direction could reveal. Pair existence with completeness and occurrence with completeness so that the contrast becomes automatic. Then pair valuation with rights and obligations to avoid treating physical presence as sufficient ownership evidence.

For subsequent events, write the condition at year end, the later evidence, the accounting treatment, materiality and the relevant responsibility date in separate lines. Challenge any answer that begins “after year end means non-adjusting.” During timed practice, turn a generic procedure such as check invoices into a sentence naming the selected population, supporting document, date range and assertion.

Finish by asking whether the same evidence supports the note disclosure as well as the recognised balance. This routine makes assertion choice defensible rather than intuitive. Mix balance, transaction and disclosure examples so the same label is not attached automatically to one account.

In the final check, ask whether the selected evidence starts inside or outside the accounting records and whether that direction matches the suspected omission or overstatement. Also check the period boundary and whether disclosure needs separate evidence from the recorded amount. State the condition date before choosing adjustment, disclosure, or further procedures.

Working through Reporting, Subsequent Events and Assertions in ACCT6007? Sia is AskSia’s AI Accounting tutor — ask any ACCT6007 Reporting, Subsequent Events and Assertions question and get a clear, step-by-step explanation grounded in how ACCT6007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 196 of your University of Sydney subjects - and 1,000+ Bibles across every Australian university.
Sia - your ACCT6007 tutor, unlimited, worked the way the exam marks it
The full 4-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works