Browse Auditing and Attestation (AUD)

AUD Pronouncements and Standards Update Reference for Exam Review

Use this AUD appendix to classify standards labels, update types, effective dates, and their audit consequences.

This appendix chapter helps you classify standards labels and update references during AUD review. Pronouncements can affect management’s accounting, the auditor’s procedures, attestation work, review or compilation services, report wording, or disclosure expectations. The exam task is usually not to recite the pronouncement number; it is to identify what changed and which responsibility follows.

Use this chapter when a question includes labels such as ASU, SAS, SSAE, SSARS, AU-C, AT-C, PCAOB AS, SOC, Topic 606, Topic 842, proposed standard, exposure draft, or effective date.

In This Chapter

Section Review role
B.1 Pronouncement Types Classifies ASUs, SASs, SSAEs, SSARS, PCAOB standards, and interpretive guidance by the work they affect.
B.2 Recent Pronouncements Applies major update themes to audit planning, evidence, reporting, effective-date discipline, and attestation context.

How to Use This Chapter

  • Use this appendix as a reference after the main reporting and standards chapters.
  • Classify the pronouncement before choosing a procedure or report.
  • Return here when you need to decode acronyms, place a new pronouncement in the right family, or decide whether an update changes management’s accounting, the auditor’s work, or only terminology.
  • Treat effective dates, entity type, and engagement type as controlling facts.

Pronouncement Effect Framework

If the update changes… AUD review effect
Accounting recognition, measurement, presentation, or disclosure Management applies the updated framework; the auditor tests the affected assertions and disclosures.
Audit responsibilities The auditor changes risk assessment, procedures, evidence evaluation, documentation, communication, or report wording.
Attestation requirements The practitioner identifies the subject matter, criteria, assurance level, and report form.
Review, compilation, or preparation requirements The CPA applies SSARS / AR-C logic rather than audit-opinion logic.
Public-company or PCAOB-covered requirements The auditor evaluates PCAOB standards, SEC/PCAOB independence context, and issuer reporting rules.
Implementation guidance or proposed language The candidate checks whether it is final, authoritative, and effective for the period in the fact pattern.

Update Discipline

When an AUD question references a new or revised standard, ask:

  1. Is the source accounting, auditing, attestation, reporting, or implementation guidance?
  2. Is the guidance final and effective for the period in the question?
  3. Is the entity a nonissuer, issuer, broker-dealer, government entity, employee benefit plan, or service organization?
  4. Does the update change management’s accounting, the auditor’s procedures, the assurance level, the auditor’s report, or only terminology?
  5. Which main AUD chapter should control the answer if the update reference is only background?

Pronouncement Classification Checkpoints

Checkpoint Exam use What to avoid
Source family Classify the label as accounting, auditing, attestation, review and compilation, PCAOB, implementation, or proposed guidance. Treating every acronym as if it changes audit procedures.
Effective status Check whether the guidance is final, proposed, effective, delayed, or only relevant to future periods. Applying a proposed or future rule as mandatory for the period under audit.
Entity and engagement type Identify nonissuer, issuer, government, employee benefit plan, service organization, audit, attestation, review, compilation, or preparation context. Mixing AU-C, PCAOB, AT-C, and SSARS logic in the same answer.
Responsibility affected Decide whether management, the auditor, the practitioner, the client, or the report user has the changed responsibility. Assuming an accounting update directly changes the auditor’s report wording.
Exam-control chapter Route the issue back to risk assessment, evidence, reporting, independence, attestation, or other main AUD content. Letting an update label distract from the underlying audit principle.

Common Traps

  • Treating an ASU as if it directly prescribes audit sampling or report wording.
  • Applying a proposed standard as mandatory before the fact pattern says it is effective.
  • Treating every SOC report as equally useful audit evidence.
  • Ignoring the difference between nonissuer AU-C requirements and PCAOB issuer-audit requirements.
  • Answering from an acronym alone without reading the entity type, period, and engagement objective.

In this section

Revised on Monday, June 15, 2026
A. Standards Ref
C. Report Examples