Armenia Auditor Qualification Exam common mistakes
Armenia Auditor Qualification Exam · Understand the traps and how to avoid them.
Calculating materiality once at planning as a single percentage of revenue and then using that same figure unchanged for every opinion and every account balance, instead of setting performance materiality at a lower level and revising it when new information emerges.
Candidates memorise 'materiality = 0.5–1% of revenue' from summary notes and never practise the two-step process (overall materiality, then performance materiality as a fraction of it), nor the requirement to revise materiality as the audit progresses.
What to do instead
Practise a full materiality workpaper: choose the benchmark and justify it, compute overall materiality, compute performance materiality at a documented percentage, set a clearly trivial threshold, and write the revision trigger. Do three cases with different benchmarks (profit before tax, total assets, revenue) and defend each choice.
Describing audit procedures as 'obtain an understanding' or 'review the ledger' without stating the assertion tested, the population, the sample selection method, and what would count as a deviation.
Exam answers are often written from general audit vocabulary rather than from the ISA 315/330/500 logic of risk, assertion, procedure, evidence. Candidates do not realise that markers award points for the specificity of the procedure, not its name.
What to do instead
For every procedure you write, force the sentence pattern: 'For the [assertion] of [account], select [population] using [method], inspect [document], and treat [condition] as an exception.' Drill ten account balances through this template until it is automatic.
Treating the risk assessment as a narrative description of the client's business and stopping there, without linking each identified risk to a specific assertion and to a planned response (test of controls or substantive procedure).
Candidates conflate 'understanding the entity' with 'assessing risk of material misstatement'. They list business risks (competition, key customer loss) but never translate them into financial statement risk at the assertion level, which is what ISA 315 requires.
What to do instead
Build a three-column table for each case: identified risk, affected account and assertion, planned response. Practise converting business risks into financial statement risks explicitly, and note which risks are significant risks requiring substantive procedures regardless of controls.
Concluding that a control is effective because the client says it operates, or because one walkthrough showed it working, without testing operating effectiveness over a sample of the period and without considering the risk of management override.
Walkthroughs and inquiries feel like testing to candidates, and the distinction between understanding the control (ISA 315) and testing its operating effectiveness (ISA 330) is a classic weak point. Management override is also routinely forgotten.
What to do instead
For each key control, state separately: how you obtained understanding, how you tested operating effectiveness (sample size, period covered, selection method), and always add a mandatory substantive response to the risk of management override of controls, including journal entry testing.
Confusing the auditor's responsibilities with management's when answering questions on fraud, going concern, or subsequent events, and writing that the auditor 'must guarantee' or 'must detect all fraud'.
The exam tests the boundary between management responsibility and auditor responsibility, and candidates overstate the auditor's duty because they study procedures without studying the underlying responsibility framework (ISA 240, ISA 570, ISA 560).
What to do instead
Write out a one-page comparison for fraud, going concern, laws and regulations, and subsequent events: what management must do, what the auditor must do, and what the auditor reports. Use it to redraft any answer that contains the words 'guarantee', 'certify' or 'detect all'.
Answering Armenian tax questions with the headline rate only, ignoring the base, the timing of recognition, the treatment of VAT input credit, and the interaction with accounting profit for corporate income tax.
Candidates revise rates as isolated facts and never practise a full computation from a transaction through to the tax return line, so they miss adjustments, non-deductible items, and timing differences.
What to do instead
Work end-to-end cases: from a journal entry to taxable profit, listing every adjustment with its legal basis. Do the same for VAT (output, input, creditability, timing) and for payroll withholding. Always state the article or rule you are applying.
Applying IFRS recognition and measurement mechanically to a scenario without checking the specific standard's scope and decision tree, for example recognising revenue at the moment of invoicing rather than applying the five-step model, or classifying a lease without applying the right-of-use logic.
Candidates recall standard titles and headline principles but not the decision sequence, so they jump to a plausible answer that ignores a condition in the standard.
What to do instead
For the high-frequency standards (IFRS 15, 16, 9, IAS 36, IAS 37, IAS 19, IFRS 9 impairment), memorise the decision steps as a numbered checklist and apply the checklist out loud to three scenarios per standard before the exam.
Mixing up the roles and outputs of the quality control system, the engagement quality review, and the external regulatory inspection, and attributing independence threats to the wrong party.
The three layers (firm-level ISQM 1, engagement-level ISQM 2, regulator oversight) are studied as lists rather than as a system, so candidates cannot say who does what, when, and with what consequence.
What to do instead
Draw a one-page map with three columns: firm, engagement, regulator. For each, list the requirement, the person responsible, the documentation, and the consequence of failure. Then answer independence questions by naming the specific threat, the safeguard, and whether the safeguard is at firm or engagement level.
Ignoring the Armenian legal and regulatory layer when answering audit, ethics, or liability questions, treating the exam as pure ISA/IFRS and omitting licensing, oversight, disciplinary, and civil liability rules.
Candidates prepare from international materials and assume the local framework mirrors it. They also skip the Civil Code and Law on Audit Activity because the volume feels unmanageable.
What to do instead
Build a separate one-page summary of the Armenian audit law: who licenses, who oversees, registration requirements, continuing education, grounds for disciplinary action, and liability. Cross-reference each item to the corresponding ISA or ISQM requirement so the two layers reinforce each other.
Writing essay answers as unstructured prose that restates the question, without stating a conclusion first, then the reasoning, then the practical consequence.
Candidates run out of time and write stream-of-consciousness, so markers cannot find the assessed points even when the underlying knowledge is present.
What to do instead
Adopt a fixed answer skeleton for every discussion question: conclusion, basis (standard or law), application to the facts, consequence or recommendation. Time-box to the mark allocation and practise ten past-style scenarios under exam timing until the skeleton is automatic.