PIPFA Foundation common mistakes
PIPFA Foundation · Understand the traps and how to avoid them.
In the corporate sector questions, treating IFRS and local statutory treatment as interchangeable-applying IFRS recognition or measurement rules to a scenario that asks for the treatment under the Companies Ordinance/statutory framework, or vice versa, without stating which framework is being applied.
Candidates study IFRS and corporate law as separate silos and then answer under whichever framework they revised last. Exam scenarios often deliberately mix a legal-form question (dividends, capital maintenance, distributable profits) with an accounting question, and the candidate defaults to the accounting rule.
What to do instead
Before answering any corporate-sector scenario, write one line at the top of your rough work: 'framework = IFRS' or 'framework = statute'. If the question mentions distributable profits, reduction of capital, or directors' duties, answer under the statutory/company-law framework; if it mentions recognition, measurement, or disclosure of a transaction, answer under IFRS. Practise by taking five past-style scenarios and labelling the framework before drafting any answer.
In corporate-sector numerical questions, computing profit or earnings per share without first determining the correct share capital structure and weighted-average number of shares, and ignoring bonus issues, rights issues, and the bonus element adjustment factor.
Candidates jump straight to the arithmetic because the numbers look familiar, and the time pressure rewards starting quickly. Rights and bonus issue adjustments are the step most often skipped because they feel like a technicality rather than the core of the answer.
What to do instead
Adopt a fixed three-step routine for every EPS or capital question: (1) list share movements with dates, (2) restate prior periods for bonus elements and compute the rights-issue adjustment factor, (3) only then compute the weighted average. Do three full worked examples of a rights issue with a bonus element before the exam and keep the adjustment-factor formula on your revision sheet.
In public sector questions, answering with private-sector financial reporting logic-for example, treating budget appropriations as revenue, or applying accrual commercial accounting to a cash-based appropriation question without flagging the basis of accounting.
Most candidates' prior accounting training is private-sector, and public financial management terminology (appropriations, votes, commitments, virements, excesses) is unfamiliar. Under time pressure the brain substitutes the familiar commercial treatment.
What to do instead
Build a one-page glossary of public financial management terms (appropriation, vote, commitment, virement, surplus/deficit, contingency fund) and, for each, write the private-sector concept it is often confused with. In every public-sector answer, state the basis of accounting (cash, modified cash, accrual) in your first sentence before applying any rule.
In public sector questions, confusing the roles of the legislature, the executive/accounting officer, and the auditor-general-for example, stating that the auditor-general authorises expenditure or that the accounting officer approves the audit report.
Candidates memorise institutions as a list of names rather than as a cycle of authorisation, execution, and oversight. The exam tests role boundaries, and a single role swap invalidates an otherwise well-written answer.
What to do instead
Draw the budget cycle as a loop with four labelled stages (authorisation by legislature, execution by accounting officer, reporting, external audit and parliamentary scrutiny) and place each institution on the loop. Before writing, check every actor you mention against that loop; if an actor appears in the wrong stage, correct it.
In PSTC written or oral tasks, producing a data dump-slides or answers that list every fact known about the topic-instead of structuring the communication around audience, purpose, and a single clear message.
Candidates equate demonstrating knowledge with maximum content, especially when the exam rewards technical accuracy elsewhere. Presentation tasks are marked on structure and audience fit, so more content lowers the mark.
What to do instead
Use a mandatory planning skeleton for every presentation answer: audience and their prior knowledge, one-sentence core message, three supporting points, and a closing call to action. Draft the one-sentence message first and delete any content that does not support it. Rehearse by summarising a technical topic to a non-technical audience in 60 seconds.
In PSTC, overloading slides with dense paragraphs and reading them verbatim, rather than using concise on-slide text with the detail delivered verbally.
Candidates write slides as a document because that is how they revise, and they fear forgetting detail. They then read the slide to avoid losing marks, which signals weak command of the material to the assessor.
What to do instead
Apply a hard rule: no more than six lines per slide, no more than six words per line, and no sentence you intend to read aloud. Put the detail in speaker notes. Practise delivering one slide with the slide hidden to prove you know the content without it.
In PSTC, ignoring non-verbal delivery and time management-running over the allotted time, failing to make eye contact, or answering a question with a fresh monologue instead of a direct response.
Candidates rehearse content only, never delivery, and under exam nerves they speed up or freeze. Time overruns and non-responsiveness are among the easiest marks to lose and the easiest to prevent.
What to do instead
Do at least three timed full run-throughs with a stopwatch, aiming to finish 10% under the limit. Prepare for questions by practising the 'answer, then explain' pattern: give a one-sentence direct answer first, then justify. Record one rehearsal and review it for pace, eye contact, and filler words.
In CCPT spreadsheet tasks, typing hard-coded values into formulas or overwriting source data instead of using cell references, named ranges, and absolute references where required.
Candidates test formulas on the actual worksheet and replace referenced cells with numbers to 'fix' an error, or build a formula that copies incorrectly because relative references were used where absolute references were needed.
What to do instead
Never replace a reference with a number; fix the reference. Before copying any formula, identify which rows and columns must stay fixed and apply the dollar signs deliberately. Keep a scratch sheet for testing and paste only the verified formula into the answer area.
In CCPT database and audit-software tasks (ACL or SAP-based exercises), writing the query or transaction step-by-step without first defining the population, the fields to extract, and the test objective, resulting in incomplete extractions or queries that return the wrong population.
Candidates treat the software task as a button-clicking exercise and start navigating menus immediately. Without a stated objective they cannot judge whether the output is complete or whether filters have excluded valid records.
What to do instead
For every software task, write three lines before touching the tool: objective in one sentence, population definition (which records are in and out), and fields required in the output. Then build the query, run it, and reconcile the record count against the population definition before finalising.
In CCPT SAP tasks, performing the requested transaction or report without recording the navigation path and the key data used, so the answer cannot be reproduced or verified and steps are missed under time pressure.
Candidates focus on reaching the end result and assume they will remember how they got there. In SAP-style environments, the path (menu route, transaction code, input fields) is part of the assessed competency, and memory fails under exam conditions.
What to do instead
Keep a running log as you work: transaction code or menu path, input values, and output obtained, written down at each step rather than reconstructed afterwards. Practise two or three common transactions until the path is automatic, and finish every task by re-walking the log to confirm each required step was performed.