PIPFA Intermediate common mistakes
PIPFA Intermediate · Understand the traps and how to avoid them.
Answering public-sector questions with private-sector terminology, for example treating a government grant as revenue recognised immediately rather than applying IPSAS 23 rules on non-exchange transactions and conditions.
Most candidates study the corporate syllabus first and revise public-sector topics last, so they default to IFRS 15 or IAS 20 logic under exam pressure instead of IPSAS 23 and the IPSASB conceptual framework.
What to do instead
Build a one-page comparison table contrasting IFRS and IPSAS treatment of grants, non-exchange revenue, heritage assets, and service concession arrangements, and practise classifying ten grant scenarios as exchange or non-exchange before attempting full questions.
Failing to apply the modified accrual or accrual basis distinction when preparing public-sector financial statements, mixing cash-based budget figures into accrual-based statements without reconciliation.
Candidates are trained on corporate financial statements where the accrual basis is assumed, and they overlook that public-sector reporting often requires a budget-to-actual reconciliation under IPSAS 24.
What to do instead
Practise a reconciliation statement from budget basis to accrual basis using a simple government department scenario, and memorise the disclosure requirements of IPSAS 24 for budget comparison.
Calculating deferred tax on temporary differences without correctly identifying the tax base of assets and liabilities, particularly for provisions, development costs, and revalued assets.
Candidates memorise the deferred tax formula but skip the step of computing the tax base for each balance sheet item, so they misclassify deductible and taxable temporary differences.
What to do instead
Work through IAS 12 examples item by item, writing the carrying amount and tax base for each line before computing the difference, and practise revaluation and provision scenarios where the tax base equals zero.
Applying the wrong consolidation method, using proportionate consolidation or equity accounting where IFRS 10 requires full consolidation, or misjudging control when voting rights are less than 50 per cent.
Candidates rely on the percentage of ownership as the sole indicator of control and do not assess potential voting rights, contractual arrangements, or de facto control.
What to do instead
Revise the IFRS 10 control model as three elements (power, exposure to variable returns, ability to use power to affect returns) and apply it to at least five scenarios with holdings between 30 and 60 per cent.
Producing numerical answers without workings, or with workings that cannot be followed, so method marks are lost even when the final figure is close.
Time pressure leads candidates to jump to the final number, and many do not realise that examiners award marks for each correct step in a computation.
What to do instead
Adopt a fixed layout for every calculation question: state the standard applied, show each line of the computation with a label, then present the final figure. Rehearse this layout under timed conditions until it becomes automatic.
Quoting a standard by number but describing the wrong recognition or measurement principle, for example citing IFRS 15 for a lease or IFRS 16 for revenue from contracts with customers.
Candidates learn standard numbers by rote close to the exam and confuse the newer standards (IFRS 15, 16, 17) because they were introduced in quick succession.
What to do instead
Create a one-line summary card for each standard listing its scope, recognition principle, and measurement basis, and test yourself by matching ten short scenarios to the correct standard without looking at the numbers.
Ignoring the requirement to discuss both financial and non-financial performance in public-sector answers, giving only ratio analysis or only narrative commentary.
Corporate syllabus training emphasises ratio analysis, so candidates transfer that habit to public-sector questions that require service delivery, efficiency, and value-for-money discussion.
What to do instead
Practise structuring public-sector performance answers around the three Es (economy, efficiency, effectiveness), adding at least two service delivery indicators alongside any financial ratios.
Misapplying ethical and independence requirements by treating a threat as automatically disqualifying rather than evaluating whether safeguards reduce it to an acceptable level.
Candidates memorise the five threat categories but not the conceptual framework's evaluate-and-address process, so they give a yes or no answer instead of a reasoned judgement.
What to do instead
Practise writing three-sentence ethical judgements: identify the threat, assess its significance, then state the safeguard or action. Apply this to at least eight short scenarios covering self-interest, self-review, and familiarity threats.
Leaving scenario-based questions unanswered or writing only a single sentence when the question asks to discuss, evaluate, or advise.
Candidates spend too long on computational questions and run out of time, then rush the discursive section, which carries a large share of the marks.
What to do instead
Allocate time in proportion to marks before starting, keep calculation answers to their budget, and practise writing discursive answers with a point, explanation, and application structure of three to four sentences per mark.
Confusing the roles of internal audit, external audit, and audit committees in public-sector entities, attributing financial statement opinion work to internal auditors or oversight of management to external auditors.
The governance and audit syllabus overlaps heavily between corporate and public sectors, and candidates learn the definitions without distinguishing accountability lines in publicly funded bodies.
What to do instead
Draw a responsibility map showing entity management, internal audit, external audit, the audit committee, and the legislature or Public Accounts Committee, and annotate each with its objective, reporting line, and output.