Study guides / AUD: Auditing & Attestation / Audit evidence & data
Audit evidence & data
AUD: Auditing & Attestation · quick review
Audit evidence must be sufficient (quantity) and appropriate (relevant and reliable). Assertions tell you what each procedure proves. Data from the entity must be tested before you rely on it, including in data analytics.
The rules
- Reliability rises when evidence is from independent outside sources, obtained directly by the auditor, documentary, original, and produced under effective controls.
- Transaction assertions: occurrence, completeness, accuracy, cutoff, classification and presentation. Balance assertions: existence, rights and obligations, completeness, accuracy, valuation and allocation, classification and presentation.
- Direction of testing: vouching from the records to source documents tests occurrence or existence. Tracing from source documents to the records tests completeness.
- Procedures: inspection, observation, external confirmation, recalculation, reperformance, analytical procedures and inquiry. Inquiry alone is never sufficient.
- Information produced by the entity (reports and data extracts) must be tested for completeness and accuracy, for example by reconciling to the ledger and checking the extraction parameters.
Common traps
- Analyzing 100% of a population doesn't help if the extract is incomplete.
- Observation covers only the moment it happens. Someone may act differently when watched.
- Confirmations are strong evidence of existence but weak evidence of valuation, because a customer may confirm a balance it can't pay.
How it's tested
Match procedures to assertions, rank evidence reliability, and evaluate data analytics results. Document review simulations may involve analytics outputs.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson