ACCA AA: Why Your Audit Procedures Keep Losing Marks

Audit Procedures questions are among the most consistently answered — and consistently under-scored — areas of the ACCA Audit and Assurance (AA) exam. Candidates frequently understand the underlying audit concept perfectly well, but write it down in a form that earns only partial credit, because a vague action verb isn't the same thing as a specific, evidenced audit procedure. This is a technique problem more than a knowledge problem, and it's fixable once the pattern is visible.

What examiner feedback actually says

ACCA's own examiner's reports for AA repeatedly call out the same weakness: procedures written as generic instructions rather than specific actions. A statement like "increase professional scepticism" reads as a reasonable audit response in principle, but on its own it doesn't describe an actual procedure an auditor would perform — there's no action, no evidence source, and no way to verify it was actually carried out. Reports have been explicit that this kind of statement earns only partial credit (around half a mark), not the full mark available for a properly constructed procedure. The same applies to instructions like "review disclosures" without specifying what in the disclosures is being checked against what criteria.

The pattern behind these examples is consistent: examiners are marking for specificity, not for the right general idea. A candidate who understands exactly which audit risk they're responding to can still lose most of the marks available if the procedure itself is written too loosely to be assessed as a real action.

What a mark-scoring procedure actually contains

A well-constructed audit procedure generally needs three things: an action verb describing what the auditor does (inspect, recalculate, agree, confirm, observe), a specific source of evidence (a named document, system, or third party), and a clear link to what the procedure is testing for. "Inspect a sample of goods received notes for the period around the year end and agree to the corresponding purchase invoices and inventory records to confirm correct cut-off" does all three things explicitly. "Test cut-off" does none of them, even though both statements reflect the same underlying audit thinking.

This distinction matters most under exam time pressure, when it's tempting to write down the audit objective (what you're trying to achieve) rather than the audit procedure (the specific action that achieves it). Objectives and risks are useful for planning which procedures to write, but they aren't themselves markable procedures.

A second common gap: confusing tests of controls with substantive procedures

AA scripts also frequently blur the distinction between tests of controls (checking that a control is operating as designed) and substantive procedures (checking that the financial statement figures themselves are materially correct). A candidate asked for substantive procedures over revenue who writes "inspect evidence that the sales invoice was authorised by a manager" has described a test of control, not a substantive procedure — useful audit evidence in a different context, but not responsive to what the question actually asked for. ISA 330 (the auditor's responses to assessed risks) frames these as distinct categories of response for a reason: they test different things and are performed for different purposes, and exam questions are specific about which one they want.

How to practise this specifically

The most effective fix is deliberately over-specifying procedures during practice, then trimming only what's genuinely redundant — rather than starting vague and hoping the marker infers the detail. For every procedure drafted in practice, checking it against three questions helps: what document or system am I inspecting; what am I comparing it to; and what audit risk or assertion does this address? If any of those three can't be answered from the sentence as written, the procedure isn't specific enough yet.

This exam-technique gap is distinct from the underlying audit knowledge covered in a general introduction to what audit procedures are and how auditors test financial statements — that groundwork explains the concepts, while AA exam success depends specifically on how precisely those concepts get written down under exam conditions.

Frequently asked questions

Why does "increase professional scepticism" not score full marks in AA?

Because it describes a mindset rather than a specific, verifiable audit action — examiner feedback has repeatedly flagged this type of generic statement as earning only partial credit, since it doesn't specify what evidence is being examined or how.

What's the difference between a test of control and a substantive procedure?

A test of control checks whether a control is operating as designed (for example, that invoices require managerial authorisation); a substantive procedure checks whether the financial statement figures themselves are materially correct. AA questions specify which type is being asked for, and answering with the wrong type loses marks even if the procedure itself is well written.

What three elements should a scoring audit procedure include?

A specific action verb, a named source of evidence, and a clear link to what's being tested — all three need to be explicit in the sentence, not implied.

The gap between knowing audit theory and scoring well in AA is almost entirely about precision in how procedures are written — candidates who build the habit of naming the document, the comparison, and the risk in every procedure consistently outperform those who understand the same concepts but write them down as general intentions. Learnsignal's ACCA AA course covers this exam technique alongside the full syllabus.