AAT Level 4 INAC study materials
AAT Level 4 INAC study resources

AAT Level 4 INAC common mistakes

AAT Level 4 INAC · Understand the traps and how to avoid them.

Mistake 1

When asked to identify control weaknesses in a described purchases or sales system, the candidate lists every control that is present and says it is 'adequate', rather than naming the specific missing or badly designed control (for example, the same person raising a purchase order and authorising payment).

Candidates read the scenario as a description to be summarised rather than as a system to be tested, and they default to reassuring language because nothing looks obviously fraudulent.

What to do instead

Practise converting each scenario sentence into a control assertion (authorisation, segregation of duties, custody, reconciliation, physical safeguard) and state explicitly which assertion is unmet and what the consequence is.

Mistake 2

Explaining the purpose of a control (e.g. 'a bank reconciliation ensures the bank balance is correct') instead of describing how the control is operated and what evidence it leaves (frequency, who performs it, independent review, retention of the reconciliation).

Exam questions asking 'describe the control' are answered as 'define the control', because candidates revise definitions rather than procedures.

What to do instead

For every named control, memorise a three-part answer: who does it, how often, and what document or record proves it was done.

Mistake 3

In a variance analysis question, calculating the variance correctly but then attributing the wrong sign or direction, so an adverse variance is described as favourable, or the price/rate variance is computed on actual quantity when the question's convention uses standard quantity.

Candidates rush the arithmetic and apply a memorised formula without checking which quantity basis the question implies, and they do not sanity-check direction against the narrative.

What to do instead

Always write the sign convention at the top of the answer (A = adverse, F = favourable) and finish every variance by stating in one sentence what the number means operationally before moving on.

Mistake 4

Reconciling budgeted profit to actual profit through variances but omitting or double-counting one line (typically fixed overhead expenditure or the sales volume margin variance), so the reconciliation does not tie to the actual profit given in the question.

Candidates build the statement from memory of a standard layout without using the actual profit figure as a balancing check.

What to do instead

Treat the given actual profit as a target: complete the reconciliation, then add or subtract the variances and confirm the total equals actual profit; if it does not, locate the missing line before writing the narrative.

Mistake 5

Calculating a single ratio (e.g. gross margin or receivables days) and concluding the company 'is profitable' or 'has good liquidity' without comparing it to a prior year, a sector benchmark, or another ratio that contradicts it.

Ratio questions are treated as calculation drills; candidates do not realise the marks sit in interpretation, and they lack a habit of cross-checking ratios against each other.

What to do instead

For every ratio computed, write one line of trend (versus prior year or benchmark) and one line of cause, and check each ratio against at least one related ratio (margin against turnover, receivables days against cash position).

Mistake 6

Preparing a statement of financial position or statement of cash flows that does not balance, and submitting it anyway with the difference left unexplained or forced into a suspense or 'other' line.

Under time pressure candidates abandon the check rather than tracing the error, and they are unfamiliar with using the movement in retained earnings and non-current assets as an independent proof.

What to do instead

Before writing the answer, compute profit for the year and the closing retained earnings independently, then reconcile non-current asset movements (opening + additions − depreciation/disposals = closing) to find the plug before drafting the statements.

Mistake 7

Ignoring the basis of assessment and the tax year boundaries in income tax and corporation tax computations, for example applying the current year's rates to profits of a different period or forgetting that a sole trader's profit is taxed in the year the accounting period ends.

Candidates learn rates and allowances but not the timeline that maps profits to tax years, and exam scenarios deliberately straddle year ends.

What to do instead

Draw a one-line timeline of accounting period end dates against tax years before computing anything, and label each figure with the tax year it belongs to.

Mistake 8

Producing a capital gains or capital allowances computation that mixes revenue and capital items, for example deducting repairs or renewals as capital expenditure, or claiming annual investment allowance on cars, without justifying the treatment.

Candidates apply the arithmetic of the allowance without revisiting the classification rules, and the scenario wording ('replacement', 'extension', 'repair') is designed to test exactly that distinction.

What to do instead

For each item, write a one-word classification (revenue/capital) and the reason before including it, and keep a short memorised list of the standard exclusions (cars from AIA, entertaining, depreciation, capital repayments).

Mistake 9

Answering a written-task question with bullet points copied from the scenario rather than applied explanation, so the response restates the facts given instead of using them to reach a judgement or recommendation.

Candidates manage time by writing short answers, and they have not practised the structure expected for the longer written tasks in the internal controls and reporting sections.

What to do instead

Use a fixed paragraph structure for written tasks: point, evidence from the scenario, consequence, recommendation; and allocate a set number of minutes per written task in practice mocks.

Mistake 10

Running out of time because the candidate attempts every question in order and spends too long on a single computational question, leaving written or discursive marks unattempted at the end.

Computational questions feel solvable and give immediate feedback, so candidates persist with them; written questions feel vaguer and are deferred until too late.

What to do instead

In mocks, set a per-question time budget, flag any question exceeding it and move on, and deliberately attempt the written tasks first or immediately after the first pass so those marks are secured.