All exam versions

ACCA PM Practice and Study Guide

60 concepts · 45 minute read

Apply costing, resource allocation, budgeting and performance analysis through twenty original practice items and sixty worked concepts. Eighteen items provide objective-test choices within their stems; two require constructed responses. Questions 1–5 and 10–14 form separate five-item cases, with necessary facts repeated. Coverage follows the September 2026–June 2027 ACCA Applied Skills PM syllabus current on 16 October 2026, without importing a future qualification redesign or APM content. This representative preview preserves the supplied learning allocation, not official domain weightings or a full mock structure. Citations establish syllabus relevance; technical explanations use established management accounting principles and explicit scenario assumptions.

What this guide covers

Free ACCA PM practice and 60 worked concepts for the September 2026–June 2027 Performance Management syllabus.

Management information systems and data analytics

1. TPS, MIS and EIS across the control hierarchy

A transaction processing system records routine events such as purchases, payroll and sales. A management information system aggregates those records into recurring reports for planning and management control. An executive information system provides selective strategic information, often combining internal trends with external indicators. Operational decisions usually need detailed, timely information; strategic decisions often require broader, less structured evidence. These are functional distinctions rather than rigid software boundaries. One platform may support several levels, so identify the decision, reporting frequency and required detail before selecting the most appropriate system.

Worked example: A factory records each material issue through its transaction system. Its monthly department report compares usage with standard allowances through MIS reporting. Directors then review capacity trends and competitor expansion through an executive dashboard before deciding whether to build another plant.

Common mistake: Assuming that senior users automatically require transaction-level detail overlooks the different aggregation, external information and decision horizons needed for strategic planning.

Official syllabus reference: [2]

2. ERP integration versus CRM customer insight

Enterprise resource planning integrates functions such as purchasing, inventory, production and finance around shared processes and data. Customer relationship management organises customer contacts, sales opportunities and service histories. ERP can reduce duplicate entry and reconcile operational events with accounting records; CRM can support retention, targeted offers and service analysis. Integration does not guarantee reliable information: inconsistent master data or poorly designed access rights can spread errors widely. Evaluate the business process and information requirement, then weigh implementation, migration, training and disruption costs against measurable benefits from integration or improved customer decisions.

Worked example: A distributor's ERP posts a goods receipt to inventory and updates purchasing records. Its CRM records the customer's unresolved complaint. Linking the systems lets the account manager distinguish a delayed shipment from a recurring service problem before offering compensation.

Common mistake: Treating ERP and CRM as mutually exclusive alternatives misses their different primary purposes and the potential benefit of controlled integration.

Official syllabus reference: [2]

3. Internet, intranet and wireless network choices

The internet supports communication across public networks, while an intranet provides organisation-restricted services using similar technologies. Wireless connectivity describes how devices connect, rather than whether information is public or private. These technologies can accelerate reporting and mobile data capture, but introduce access, availability and interception risks. Authentication, encryption, controlled permissions and resilient connections address different weaknesses. Choose controls according to the information and use case: an internal dashboard accessed over wireless still requires authorised users and protected transmission. Calling a network internal does not make every connected device or account trustworthy.

Worked example: Warehouse staff scan stock movements over a protected wireless network into an intranet application. Suppliers view selected order information through an authenticated internet portal. Separating permissions prevents supplier access to internal product margins while preserving useful real-time order visibility.

Common mistake: Equating wireless access with public access confuses the connection method with the permissions and architecture governing the information service.

Official syllabus reference: [2]

4. Information controls: validity, access and recoverability

Information controls should protect confidentiality, integrity and availability throughout collection, processing and distribution. Input checks can reject invalid codes or impossible quantities; reconciliations and audit trails help detect incomplete or altered processing. Role-based access and approval workflows restrict who can view or change sensitive information. Backups and tested restoration procedures support recoverability rather than preventing unauthorised disclosure. Segregation of duties reduces the opportunity for one person to introduce and conceal errors. Match each control to a specific risk, and distinguish preventive controls from detective checks rather than assuming a single control solves every information problem.

Worked example: A payroll clerk can enter approved hours but cannot change pay rates. A separate manager approves rate amendments, and a reconciliation compares payroll totals with authorised staff records. Tested backups allow recovery after system failure without replacing these approval controls.

Common mistake: Assuming a backup protects confidentiality confuses recovery after data loss with controls that prevent unauthorised viewing or alteration.

Official syllabus reference: [2]

5. Decision value and the cost of information

Useful management information is relevant to the decision, sufficiently accurate, timely, understandable and economical to obtain. Internal records can explain resource use and customer behaviour; external evidence can reveal market demand, competitors and economic conditions. Greater precision or frequency has value only when it can change a worthwhile decision. Collection, cleansing, integration, training and management attention all create costs. Evaluate incremental benefits against incremental information costs and consider reliability at source. A fast report with uncertain definitions may mislead, while a highly accurate report delivered after the decision may have little practical value.

Worked example: A retailer can buy daily competitor-price feeds for $20,000 annually, but changes prices only monthly. A cheaper monthly feed may support the same decisions. Daily data becomes worthwhile only if more frequent pricing actions generate sufficient additional benefit.

Common mistake: Assuming more data always improves decisions ignores acquisition costs, processing burdens and whether the additional information can alter an actionable choice.

Official syllabus reference: [2]

6. The five Vs and the data-to-wisdom pyramid

Big data is commonly characterised by volume, velocity, variety, veracity and value. These dimensions describe scale, arrival speed, different formats, reliability and useful benefit. The data-information-knowledge-wisdom pyramid explains a different progression: raw observations gain context, become interpretable relationships and ultimately support judgement about action. Large data volumes do not automatically produce knowledge, and a statistically strong pattern may lack operational value. Apply the five Vs to implementation challenges, then use the pyramid to explain how interpretation and organisational understanding convert recorded events into decisions.

Worked example: Thousands of temperature readings are data. A report showing repeated overheating after long production runs is information. Understanding the relationship with cooling capacity creates knowledge. Scheduling shorter runs after evaluating cost and delivery consequences applies judgement to choose an action.

Common mistake: Treating value as a synonym for volume overlooks that a small reliable dataset can support a better decision than a vast unreliable one.

Official syllabus reference: [2]

7. Four analytics methods and their decision outputs

Descriptive analytics summarises what happened; diagnostic analytics investigates why it happened. Predictive analytics estimates future outcomes, while prescriptive analytics recommends actions under objectives and constraints. Classification depends on the analytical output, not the software or whether historical data is used. A predictive model may feed a prescriptive optimisation model, but estimating demand alone does not choose production quantities. Diagnostic findings also require care because association may not establish causation. Identify the management question first, then determine which analytical method supplies the missing evidence or recommendation.

Worked example: A delivery dashboard reports late shipments descriptively. Further analysis links delays with a loading shift diagnostically. A model predicts next week's delays, and a scheduling optimiser recommends staffing changes. Each stage answers a different question despite using related operational records.

Common mistake: Calling every model using past observations descriptive ignores whether its output summarises history, forecasts events or recommends future actions.

Official syllabus reference: [2]

8. Data mining, visualisation and analytical reliability

Data mining searches large datasets for useful patterns such as customer groups, recurring associations or unusual transactions. Visualisation makes relationships and exceptions easier to inspect, but neither approach guarantees a valid interpretation. Missing records, biased samples, inconsistent definitions and changing operating conditions can distort results. Charts should disclose units, periods and denominators and use scales suited to the comparison. Test whether a discovered pattern persists in relevant data before acting on it. An attractive dashboard can communicate an error efficiently, so presentation quality must accompany data-quality and model checks.

Worked example: A retailer finds that premium customers appear to return fewer items. A chart separating online and store purchases reveals that premium customers mainly buy in stores, where returns are recorded differently. Correcting the records changes the apparent customer relationship.

Common mistake: Interpreting a visually strong correlation as proof of causation overlooks confounding variables, recording differences and the possibility of an unstable pattern.

Official syllabus reference: [2]

Specialist cost and management accounting techniques

9. ABC pools, cost drivers and unit costs

Activity-based costing groups overheads into activity pools and assigns each pool through a driver reflecting consumption of that activity. Calculate the rate as pool cost divided by total driver quantity, then multiply by each product's driver use. Sum assigned overheads and divide by product output for overhead per unit. Setup counts, purchase orders and inspections can explain costs that production volume alone misses. Driver choice requires a plausible causal relationship and dependable measurement. ABC reallocates costs; it does not itself eliminate overhead or establish that every assigned cost is avoidable.

Worked example: A purchasing pool costs $48,000 and processes 600 orders, giving $80 per order. A product requiring 45 orders receives $3,600 purchasing overhead. If it produces 900 units, this activity contributes $4 overhead per unit before other pools are added.

Common mistake: Dividing every activity pool by units produced defeats ABC's purpose when the activity is driven by batches, orders or product complexity.

Official syllabus reference: [2]

10. ABC versus volume-based overhead absorption

Traditional overhead absorption often uses one rate based on labour or machine hours. It works reasonably when products consume support activities in similar proportions to that volume measure. Where low-volume products require frequent setups or specialised support, a blanket rate may undercost them and overcost simpler high-volume products. ABC makes those differing activity demands visible. Compare revised product costs by tracing which pools move and why, rather than assuming ABC always increases cost accuracy enough to justify its expense. Complex driver systems also require maintenance and may create false precision if their underlying relationships are weak.

Worked example: Two products use equal machine hours, but the customised product requires twenty setups while the standard product requires two. A machine-hour rate assigns equal setup overhead. An ABC setup pool shifts more cost toward the customised product and changes the apparent margin comparison.

Common mistake: Assuming a higher ABC product cost means total company expenditure increased confuses a change in allocation with a change in resources consumed.

Official syllabus reference: [2]

11. Target cost from a sales margin

Target costing starts with a competitive market price and subtracts required profit to establish an allowable cost. If profit is a percentage of sales, target cost equals price multiplied by one minus that margin. A markup on cost requires a different calculation: divide selling price by one plus the markup. The target cost gap is estimated cost less allowable cost. In services, labour intensity, customer participation and variable service specifications can make consistent unit-cost estimates difficult. The allowable cost remains a planning objective, not evidence that the organisation can deliver the required quality at that amount.

Worked example: A service package sells for $240 and requires a 30% sales margin. Target cost is $168. An estimated cost of $180 creates a $12 gap. Dividing $240 by 1.30 would instead apply a cost markup and answer a different question.

Common mistake: Using a margin and a markup interchangeably changes the denominator of the profit percentage and produces an incorrect allowable cost.

Official syllabus reference: [2]

12. Value engineering to close a target cost gap

Value engineering examines product or service functions and seeks lower-cost ways to deliver benefits customers actually value. Design simplification, component standardisation, supplier collaboration and process redesign can close a target cost gap before costs become committed. Distinguish removing unnecessary cost from reducing required performance. A cheaper component may increase warranty, maintenance or disposal costs elsewhere in the life cycle. Evaluate savings across functions and stages, including service quality and sustainability consequences. Cost cutting that damages the market proposition can undermine the selling price from which the target was originally derived.

Worked example: A machine's custom casing costs $18 more than a standard casing. Testing shows the standard casing preserves safety, durability and customer-required dimensions. Adopting it closes part of the target gap without deleting a valued feature or transferring cost into later repairs.

Common mistake: Treating every reduction in specification as value engineering overlooks whether the removed function supports customer willingness to pay or required performance.

Official syllabus reference: [2]

13. Life-cycle profit and committed costs

Life-cycle costing accumulates costs from development through production, support and withdrawal rather than judging profitability from manufacturing cost alone. Include relevant design, launch, operating support and end-of-life obligations alongside expected lifetime revenue. Many costs become committed through early design decisions even though cash is spent later, which makes early analysis especially useful. Divide total life-cycle cost by lifetime units only when that average serves the decision. Life-cycle profitability depends on forecasts of volume, support demand and product longevity; an attractive production margin can coexist with an overall loss after development and closure costs.

Worked example: A product expects lifetime revenue of $2.4 million, production cost of $1.5 million, development of $500,000 and support and withdrawal costs of $300,000. Its manufacturing margin looks strong, but total life-cycle profit is only $100,000 before other stated costs.

Common mistake: Excluding pre-production design expenditure from life-cycle profitability confuses whether a cost is already sunk with whether the product was profitable overall.

Official syllabus reference: [2]

14. Theory of constraints and system throughput

The theory of constraints focuses improvement on the resource limiting the system's output. Identify the constraint, exploit its available capacity, subordinate other activities to its needs, elevate its capacity if worthwhile, and repeat when the constraint moves. Protecting a bottleneck from downtime or defective inputs can improve total output more than speeding up an unconstrained process. Producing excess work before the bottleneck may simply increase inventory. The relevant constraint may be production capacity or market demand. Reassess the whole system after improvement because the original limiting resource may cease to determine output.

Worked example: Assembly can process 100 units hourly, but testing handles only 70. Increasing assembly to 120 creates queues rather than more sales. Moving routine setup away from testing raises its usable capacity to 80, improving system output if demand and downstream capacity permit.

Common mistake: Maximising utilisation at every workstation can create excess inventory and local efficiency gains without increasing the output of the constrained system.

Official syllabus reference: [2]

15. Throughput accounting ratio and bottleneck economics

Under the usual short-run throughput assumption, throughput is sales revenue less direct material cost, while other factory costs are treated as operating expenses. Return per bottleneck hour is throughput per unit divided by bottleneck time. Cost per bottleneck hour is total factory operating cost divided by available bottleneck hours. Their ratio is the throughput accounting ratio. A ratio above one indicates that the stated throughput rate exceeds the allocated operating-cost rate, but does not independently prove long-term viability. Apply the scenario's cost assumptions and evaluate realistic sales demand, capacity use and changes in operating expense.

Worked example: A unit sells for $90, uses $30 material and takes half a bottleneck hour. Return is $120 per bottleneck hour. Factory cost of $80,000 across 1,000 available hours gives $80 per hour, producing a throughput accounting ratio of 1.5.

Common mistake: Subtracting all absorbed production costs when calculating throughput mixes conventional product costing with a model that treats those costs as period operating expenses.

Official syllabus reference: [2]

16. Throughput product ranking with sales ceilings

When one bottleneck limits production, rank products by throughput per unit of bottleneck resource, then allocate capacity in that order subject to demand. Throughput per unit alone can favour a product that consumes too much scarce time. After the highest-ranked product reaches its sales ceiling, use remaining capacity for the next product. Deduct unchanged operating expense from total throughput only when calculating profit. This simple ranking assumes a single effective constraint and divisible or suitably manageable quantities. Multiple binding constraints, compulsory bundles or indivisible large batches may require a different optimisation approach.

Worked example: Product M earns $80 throughput using two bottleneck hours; N earns $50 using one hour. With 100 hours and N demand of 60, make 60 N first, then 20 M. Total throughput is $4,600, respecting both demand and capacity.

Common mistake: Applying the highest hourly throughput to every available hour ignores that the corresponding product may not have enough demand to use all capacity.

Official syllabus reference: [2]

17. Input-output analysis and flow cost accounting

Input-output analysis reconciles physical inputs with saleable outputs, waste, emissions and inventory changes, helping identify material losses hidden in general overhead. Flow cost accounting follows material flows and can distinguish material, system and delivery or disposal costs associated with useful output and losses. The purchase value of wasted material is often larger than its disposal charge. Physical reconciliation requires consistent units and allowance for genuine transformations or inventory movements. These techniques connect environmental and financial performance without assuming that every apparent mass difference is avoidable waste or that every reduction automatically preserves product quality.

Worked example: A process uses 1,000 kg costing $6 per kilogram and produces 850 kg of product plus 150 kg of waste. Waste disposal costs $300. The material value lost is already $900, so focusing only on the disposal invoice understates the financial opportunity.

Common mistake: Counting disposal charges as the entire cost of waste excludes the purchased material and processing resources already consumed by discarded output.

Official syllabus reference: [2]

18. Environmental ABC and sustainability decision support

Environmental management accounting makes environmentally related resource use and costs visible for internal decisions. ABC can assign treatment, monitoring or disposal costs using drivers such as effluent volume, hazardous handling or waste batches instead of spreading them uniformly. Life-cycle analysis can expose costs shifted into use or withdrawal stages. Management accountants help establish reliable physical and monetary information, evaluate alternatives and explain trade-offs. Some environmental effects remain difficult to monetise or fall outside the organisation's accounts. Report those limitations explicitly rather than presenting an incomplete monetary total as a comprehensive measure of sustainability.

Worked example: Two products use equal machine hours, but one creates four times as much hazardous effluent. Allocating treatment costs through effluent volume reveals its greater environmental cost burden. Management can then compare process redesign with the existing product margin and customer requirements.

Common mistake: Assuming environmental costs are a separate fixed overhead category hides how particular materials, processes and products generate different resource and treatment demands.

Official syllabus reference: [2]

Decision-making techniques

19. Relevant material costs and alternative uses

A relevant cost is a future cash-flow difference caused by a decision. Historical purchase cost is sunk, but inventory can still have a relevant value through replacement or alternative use. Regularly used material normally carries replacement cost when consuming stock triggers replenishment. Surplus material without another use may carry foregone net disposal proceeds. If an alternative productive use exists, evaluate the benefit sacrificed rather than automatically using scrap value. Trace the actual consequence in the scenario and avoid combining replacement cost and disposal value when they represent alternative valuations of the same stock.

Worked example: A contract needs 300 kg of surplus material that could be sold for $3 per kilogram, with no replacement or other use. Its relevant stock cost is $900. If the material were regularly used and replaced at $7, the relevant amount would instead be $2,100.

Common mistake: Treating inventory as free because its purchase is sunk overlooks the future replacement spending or alternative benefit sacrificed by using it.

Official syllabus reference: [2]

20. Labour opportunity costs in make-or-buy decisions

Compare avoidable internal costs with the purchase price and other incremental outsourcing costs. Existing wages may be irrelevant when staff are paid regardless and have genuinely idle time. Overtime or replacement recruitment creates incremental cash cost. If production displaces profitable work, include the contribution sacrificed as an opportunity cost. Avoidable fixed costs belong in the comparison; arbitrary allocations of continuing fixed overhead do not. Financial savings must be considered alongside quality, supply reliability, confidentiality and loss of capability. The answer changes when capacity becomes scarce, even if the quoted supplier price and accounting unit cost remain unchanged.

Worked example: Making a component uses $14 material and two scarce labour hours. Each hour could earn $8 contribution on other work. Relevant make cost is $30 per component before any other incremental costs. A reliable supplier charging $27 may therefore be financially preferable.

Common mistake: Comparing a supplier quote with full absorbed unit cost can wrongly include unavoidable overhead while omitting contribution lost from scarce internal capacity.

Official syllabus reference: [2]

21. Shutdown and further-processing incremental tests

Short-term shutdown analysis compares contribution lost with fixed costs and other cash flows actually avoided. A product showing an allocated accounting loss can still contribute toward continuing common costs. For joint products, costs incurred before split-off are normally unchanged by a further-processing decision. Compare additional revenue after split-off with additional processing and selling costs. These applications share incremental logic but require different decision boundaries. Include closure, restart, customer and contractual effects where supplied. Do not extend a short-run result indefinitely when continuing costs or strategic capability become avoidable over a longer horizon.

Worked example: A joint product sells at split-off for $40,000 or after processing for $55,000. Additional processing costs $11,000, so processing adds $4,000. An allocated $18,000 share of joint production cost does not change that comparison because it is incurred under either alternative.

Common mistake: Requiring processed revenue to recover an allocated share of joint costs can reject profitable further processing because those costs do not change.

Official syllabus reference: [2]

22. Break-even, target profit and margin of safety

Contribution per unit is selling price less variable cost. Break-even units equal fixed costs divided by unit contribution; target-profit units add required profit to fixed costs before dividing. The contribution-to-sales ratio expresses contribution as a fraction of revenue and supports revenue-based calculations. Margin of safety is expected sales less break-even sales, expressed in units, money or as a percentage of expected sales. CVP assumes relevant-range cost behaviour, sufficiently stable prices and a consistent sales mix where applicable. Use charts to distinguish total revenue, total cost and profit rather than treating every intersection as a profit target.

Worked example: A product sells for $50 with $30 variable cost and $60,000 fixed costs. Break-even is 3,000 units. Expected sales of 4,000 give a 1,000-unit, or 25%, margin of safety. Earning $20,000 profit requires 4,000 units.

Common mistake: Dividing the safety margin by break-even sales instead of expected sales produces a different percentage from the standard margin-of-safety measure.

Official syllabus reference: [2]

23. Multiproduct CVP and the sales-mix boundary

Multiproduct CVP uses a constant sales mix to combine different contributions. For a unit mix, calculate weighted average contribution per unit or construct a composite sales bundle. For a revenue mix, use a revenue-weighted contribution-to-sales ratio instead. Divide fixed costs plus target profit by the appropriate combined measure, then restore the specified mix. Products with higher contribution alter break-even when their share changes. A multiproduct profit-volume chart may therefore depend on the order in which products are plotted. State the mix assumption and avoid combining unit weights with revenue-based ratios.

Worked example: A bundle contains three A units contributing $12 each and two B units contributing $8 each. Bundle contribution is $52. Fixed costs of $26,000 require 500 bundles to break even, meaning 1,500 A and 1,000 B if the mix holds.

Common mistake: Averaging two products' contribution-to-sales ratios without their revenue weights can misstate combined contribution even when the unit sales mix is known.

Official syllabus reference: [2]

24. Single limiting factors and outsourcing priority

With one scarce resource, rank products by contribution per unit of that resource, not by contribution per finished unit. Allocate capacity to the highest-ranked activity until its demand is satisfied, then continue down the ranking. In a make-or-buy problem, rank the saving from making internally per scarce-resource unit: purchase price less avoidable internal cost, divided by required resource. This identifies where internal capacity avoids the most external spending. Check minimum commitments and demand ceilings. The method assumes one effective constraint; multiple simultaneous constraints can make a simple ranking unreliable.

Worked example: Making part A saves $9 compared with buying and uses three scarce hours; part B saves $8 and uses two. A saves $3 per hour, while B saves $4. Use available internal capacity for B first, despite its smaller saving per part.

Common mistake: Ranking make-or-buy alternatives by internal contribution alone ignores that the decision benefit is the purchase cost avoided per scarce-resource unit.

Official syllabus reference: [2]

25. Linear programming and feasible corner points

Linear programming represents contribution or cost as an objective function subject to resource and demand constraints. Define decision variables, express all relationships in consistent units and include non-negativity restrictions. With two products, draw constraint boundaries and identify the feasible region; evaluate relevant corner points or solve intersecting binding constraints simultaneously. Under the linear model an optimum occurs at a feasible corner, though alternative optima are possible. Divisibility, constant coefficients and certainty are important assumptions. A mathematically attractive intersection is invalid if it violates another constraint or represents quantities the scenario does not permit.

Worked example: Maximise 20X + 15Y subject to X + Y ≤ 100 and 2X + Y ≤ 140. The boundaries intersect at X = 40 and Y = 60, earning $1,700. Compare this with other feasible corners before concluding that the intersection is optimal.

Common mistake: Solving two constraint equations establishes an intersection, but does not by itself show feasibility against every other limit or prove optimality.

Official syllabus reference: [2]

26. Shadow prices, slack and marginal resource value

Slack is unused availability in a less-than-or-equal resource constraint. A non-binding resource normally has zero shadow price in the current linear-programming solution because a small increase cannot improve the objective. A binding resource's shadow price measures the marginal improvement from one extra unit of availability, within the range where the relevant solution structure holds. It usually represents a premium above normal resource costs already included in contribution. Reoptimise or check the valid range for larger changes. Binding status alone does not guarantee a positive shadow price in every degenerate or redundant mathematical formulation.

Worked example: An optimal plan uses all machine time but leaves 20 labour hours unused. Additional labour has no immediate value if machines still prevent expansion. If an extra machine hour improves contribution by $14, paying a premium below $14 can be worthwhile within the applicable range.

Common mistake: Multiplying a shadow price by an unlimited resource increase ignores that another constraint may become binding and change the marginal benefit.

Official syllabus reference: [2]

27. Linear demand and price elasticity

A straight-line demand relationship can be written P = a − bQ, where a is the price-axis intercept and b measures the price reduction needed for an additional unit of demand. Derive the slope from two supplied price-quantity observations. Price elasticity measures percentage quantity change relative to percentage price change; use the base or midpoint convention specified in the problem and distinguish the signed coefficient from its magnitude. Elasticity varies along a straight demand line. Demand estimates describe an assumed relationship, not guaranteed sales, and can change with competitors, quality and market conditions.

Worked example: Demand is 1,000 units at $80 and 1,500 at $70. Price falls $10 for 500 extra units, so b is 0.02 and P = 100 − 0.02Q. Using the initial base, quantity rises 50% while price falls 12.5%, giving elasticity −4.

Common mistake: Assuming a constant slope means constant price elasticity overlooks that percentage changes depend on the starting price and quantity.

Official syllabus reference: [2]

28. Profit-maximising price through MR equals MC

For linear demand P = a − bQ, total revenue is aQ − bQ² and marginal revenue is a − 2bQ. Equate marginal revenue with marginal cost to identify a candidate profit-maximising quantity, then substitute quantity into demand to find price. Fixed costs affect resulting profit but not this interior quantity when they remain unchanged. Check capacity, non-negative demand, feasible prices and any discontinuous cost discounts. Where costs or prices change in steps, compare total profits across relevant feasible alternatives rather than relying on a single smooth marginal equation.

Worked example: Demand is P = 120 − 0.5Q and variable cost is $20 per unit. Marginal revenue is 120 − Q, so Q = 100 when MR equals MC. Price is $70. With $2,000 fixed cost, profit is $3,000 if capacity permits that output.

Common mistake: Using the demand equation itself as marginal revenue omits the revenue lost on existing units when price falls to sell additional output.

Official syllabus reference: [2]

29. Pricing strategies and incremental price decisions

Cost-plus pricing adds a specified markup to a defined cost base, while relevant-cost pricing focuses on incremental costs and opportunity costs for a particular decision. Skimming seeks high initial prices from willing early buyers; penetration uses a lower entry price to build demand. Complementary-product and product-line pricing consider related products, while discrimination charges different customer groups under suitable market conditions. Volume discounts require comparison of total incremental revenue and cost, including any discount applied to existing units. A strategy's label does not establish profitability: demand, capacity, competition and the precise cost base remain essential.

Worked example: A supplier offers a 5% discount if an order increases from 1,000 to 1,200 units. Calculate revenue on all 1,200 units at the discounted price, then compare with the original revenue and additional costs. Pricing only the extra 200 units misses discount leakage.

Common mistake: Applying a stated markup to a different cost base can produce an internally correct percentage calculation but the wrong quoted selling price.

Official syllabus reference: [2]

30. Maximax, maximin and minimax regret

When reliable probabilities are unavailable, payoff criteria express different attitudes toward uncertainty. Maximax selects the decision with the highest possible payoff. Maximin selects the decision with the best worst-case payoff. Minimax regret first calculates, for each state, the loss relative to that state's best available payoff, then chooses the decision with the smallest maximum regret. Regret is an opportunity loss, not necessarily a cash loss. These rules do not infer probabilities or establish a universally best attitude. Construct the payoff and regret tables consistently and identify which criterion the decision maker requests.

Worked example: Small expansion pays 20 or 40; large expansion pays −10 or 80. Maximax chooses large and maximin chooses small. Regrets are 0 and 40 for small, and 30 and 0 for large, so minimax regret chooses large with maximum regret of 30.

Common mistake: Calculating regret relative to the best outcome within each decision row ignores that regret compares alternatives under the same realised state.

Official syllabus reference: [2]

31. Expected values, information value and uncertainty tests

Expected value weights each outcome by its probability; decision trees apply that logic backwards, choosing the best available action at decision nodes. Perfect-information value is expected payoff with state-specific choices less the best uninformed expected payoff. Imperfect information requires updating probabilities and optimising after each signal before deducting research cost. Market research and focus groups can inform assumptions without eliminating uncertainty. Sensitivity analysis changes a variable to identify a switching point, while simulation generates a distribution from modelled uncertain inputs. Expected value is a weighted average, not a promised result or a measure of downside capacity.

Worked example: Without research, the best expected profit is $40,000. A survey permits signal-specific decisions worth $47,000 before its $3,000 fee. Information value is $7,000 and net benefit is $4,000. A simulation could additionally show how often the chosen policy produces a loss.

Common mistake: Subtracting research cost before comparing information quality can obscure the distinction between gross information value, its purchase price and the net decision benefit.

Official syllabus reference: [2]

Budgeting and control

32. Functional budgets, master budgets and flexing

Budgets translate strategic objectives into coordinated operational plans. Functional budgets for sales, production, purchasing and other activities feed the master budget, including financial statements and cash forecasts. A fixed budget relates to one planned activity level. A flexible budget describes cost and revenue behaviour across activity levels; a flexed budget applies those relationships to actual activity for comparison. Separate activity effects from spending performance by flexing variable items while preserving fixed amounts within the relevant range. Coordination matters because a sales plan unsupported by capacity, staffing or cash cannot form a feasible overall budget.

Worked example: A maintenance budget allows $10,000 fixed cost plus $3 per machine hour. At 4,000 actual hours, the flexed allowance is $22,000. Comparing actual spending with this amount is more informative than using the original allowance for 3,000 hours.

Common mistake: Increasing every budget line in proportion to output incorrectly treats fixed costs as variable and can conceal overspending.

Official syllabus reference: [2]

33. Incremental versus zero-based budgeting

Incremental budgeting adjusts an existing budget or actual baseline for expected changes. It is relatively economical but can preserve outdated activities and embedded inefficiency. Zero-based budgeting requires activities to be justified through decision packages, alternative service levels and prioritisation rather than assuming continuation. It can challenge discretionary spending but requires substantial information and management effort. Neither method removes the need to understand demand and obligations. Choose according to the stability, materiality and reviewability of activities; an organisation may use periodic zero-based reviews alongside incremental updates rather than applying one approach uniformly.

Worked example: A stable rental contract may be budgeted incrementally using the agreed increase. A marketing department with overlapping campaigns may benefit from decision packages showing each campaign's purpose, alternatives and expected benefit, allowing management to rank spending rather than simply add inflation.

Common mistake: Interpreting zero-based budgeting as an automatic spending cut ignores that justified activities may receive more resources than under an inherited baseline.

Official syllabus reference: [2]

34. Activity-based budgets from demand to resources

Activity-based budgeting works from planned outputs to required activities and then to resource capacity and cost. Identify the expected driver quantities, estimate the resources those activities require and consider whether capacity must change in steps. It reverses the allocation direction used in ABC: the focus is prospective resource planning rather than assigning historical overhead. Multiplying driver volumes by rates may estimate resource consumption, but cash spending need not change proportionately where resources are fixed or supplied in blocks. Explicitly identify unused capacity and distinguish resources required from resources actually acquired.

Worked example: A service centre expects 8,000 orders and one quality review per twenty orders, requiring 400 reviews. Each reviewer can complete 150 reviews annually. Planning therefore needs three reviewers, not 2.67 salaries, unless flexible staffing arrangements make fractional capacity genuinely available.

Common mistake: Assuming activity cost rates always predict cash expenditure overlooks spare capacity, indivisible staffing and step changes in acquired resources.

Official syllabus reference: [2]

35. Rolling forecasts, feed-forward control and beyond budgeting

Rolling budgets continually extend the planning horizon, while forecasts update expected outcomes. Feed-forward control compares predicted conditions with objectives and acts before a deviation fully occurs. Beyond budgeting challenges rigid annual target contracts through more adaptive planning, relative performance evaluation and decentralised responsibility. These approaches can improve responsiveness in volatile conditions but require reliable information, capable managers and clear accountability. Updating a forecast should not automatically rewrite an incentive target. Distinguish planning information, resource authorisation and performance evaluation so that honest forecasts remain useful rather than becoming negotiations to avoid adverse results.

Worked example: A forecast predicts a shortage three months ahead. Management secures alternative supply now, using feed-forward control. The rolling plan adds another month, while performance evaluation compares service reliability with relevant peers rather than treating the original annual forecast as an immutable contract.

Common mistake: Assuming beyond budgeting means abandoning financial planning overlooks its emphasis on adaptive coordination, relative targets and more responsive management processes.

Official syllabus reference: [2]

36. Participation, target difficulty and ethical budget design

Participative budgeting can improve local information and commitment, but managers may introduce slack by understating revenue or overstating necessary resources. Imposed targets can support strategic coordination yet ignore operational knowledge. Target difficulty affects motivation: an achievable challenge may encourage effort, while an apparently impossible target can prompt disengagement or manipulation. Assess controllability and cross-department dependencies rather than attributing every variance to the budget holder. Ethical and sustainability considerations include truthful estimates, transparent assumptions and avoiding targets that encourage hidden quality failures or cost transfers. Changes to budget systems also need training and credible management support.

Worked example: A purchasing manager inflates expected material prices to create a favourable future variance. Independent market evidence and open challenge can reduce this slack. A jointly agreed target should still allow genuine quality requirements and supplier risks rather than rewarding the lowest quoted price alone.

Common mistake: Assuming employee participation guarantees accurate budgets overlooks incentives to negotiate easier targets and the need for evidence-based challenge.

Official syllabus reference: [2]

37. High-low cost estimation and the relevant range

The high-low method estimates variable cost per activity unit from the cost difference between the highest and lowest activity observations, divided by their activity difference. Estimate fixed cost by subtracting variable cost at either selected activity level from its total cost. Select observations by activity, not by the highest and lowest costs. The method uses only two points and can be distorted by abnormal events or changed capacity. Apply the resulting equation within a comparable relevant range and consider whether inflation, seasonality or a step cost explains the observed difference instead of constant variable behaviour.

Worked example: At 2,000 hours, cost is $34,000; at 5,000 hours, it is $55,000. Variable cost is $21,000 divided by 3,000 hours, or $7 per hour. Fixed cost is $20,000, predicting $48,000 at 4,000 hours if the relationship remains valid.

Common mistake: Choosing the largest and smallest total costs rather than activity levels can select observations that do not represent the required high-low comparison.

Official syllabus reference: [2]

38. Regression, correlation and explanatory limits

Simple linear regression estimates a relationship such as total cost Y = a + bX using multiple observations. The slope estimates the change in Y associated with one unit of X; the intercept estimates Y when X is zero within the model. Correlation describes the strength and direction of linear association. The coefficient of determination describes the proportion of observed dependent-variable variation explained by the fitted model, not forecast certainty. Outliers, omitted variables, structural changes and extrapolation can undermine interpretation. A strong statistical relationship is useful evidence but does not establish that changing X causes the estimated change in Y.

Worked example: A fitted delivery-cost equation is $12,000 + $4 per parcel, with R² of 0.81. At 5,000 parcels the forecast is $32,000. The 0.81 describes explained sample variation; it does not mean the forecast is guaranteed to be 81% accurate.

Common mistake: Interpreting R² as the probability that a forecast is correct confuses model fit within observed data with the uncertainty of a future prediction.

Official syllabus reference: [2]

39. Time-series trends and seasonal adjustments

Time-series analysis separates recurring patterns from longer-term trend and irregular variation. Moving averages can smooth seasonal fluctuations, while seasonal factors express typical period effects. In an additive model, add a seasonal amount to the trend; in a multiplicative model, multiply trend by a seasonal index. Use the model and units specified by the problem. Forecasts assume relevant historical patterns persist, so structural changes, exceptional events and changing customer behaviour require judgement. A trend estimate is not a causal explanation, and short datasets may produce unstable seasonal factors even when the arithmetic is correct.

Worked example: A quarterly trend forecast is 2,000 units and the relevant multiplicative seasonal index is 1.15. Forecast demand is 2,300 units. If the model instead specified an additive seasonal uplift of 150 units, the forecast would be 2,150, using a different mechanism.

Common mistake: Adding a multiplicative seasonal index as though it were an absolute quantity mixes incompatible model definitions and gives an incorrect forecast.

Official syllabus reference: [2]

40. Cumulative-average learning curves and steady states

The cumulative-average learning model is Y = aX^b, where Y is average time per unit after X cumulative units, a is first-unit time and b equals log of the learning rate divided by log 2. Each doubling of cumulative output multiplies average time by the learning rate. Total time is X times cumulative average time; incremental batch time is the difference between cumulative totals. Learning may cease at a stated output level, after which use the scenario's steady-state assumption. The model suits repeated labour-intensive tasks more than unrelated work or processes dominated by fixed machine time.

Worked example: The first unit takes 100 hours and the learning rate is 80%. Average time for two units is 80 hours, so total time is 160 and the second unit takes 60. At four units, average time is 64 hours and total time is 256.

Common mistake: Treating cumulative average time as the time for the latest unit overstates later incremental hours and miscalculates batch labour requirements.

Official syllabus reference: [2]

41. Standard types and controllable performance evaluation

Standard costs specify expected resource quantities and prices for defined operating conditions. Ideal standards assume highly efficient conditions without normal losses; attainable standards allow realistic efficient losses and interruptions. Basic standards remain unchanged for long-term comparisons, while current standards reflect prevailing conditions. Select a standard suited to its purpose and explain behavioural consequences. Controllability requires examining whether a manager could influence the relevant cause over the evaluation period. A purchasing price variance may arise from an external market movement, but supplier choice and order timing may still contain operational responsibility. A variance identifies a question, not automatic blame.

Worked example: An attainable standard permits 1.05 kg input per finished unit because efficient production includes normal loss. Comparing actual usage with a one-kilogram ideal may produce recurring adverse variances even when the process is well controlled, weakening the standard's motivational usefulness.

Common mistake: Assigning every adverse variance to the named department ignores external influences, shared decisions and whether the selected standard represents achievable performance.

Official syllabus reference: [2]

42. Material usage split into mix and yield

Material usage variance can be separated into mix and yield effects using standard prices. Mix compares actual input quantities with the same total input redistributed into standard proportions. Yield compares actual total input with the standard input allowed for actual output, valued at the weighted standard input cost. Under consistent definitions, mix plus yield reconciles to total usage variance. A cheaper mix can create a favourable mix variance but worsen yield, quality or customer outcomes. Consider process controls, defect rates and physical losses alongside the financial variances before judging whether changing ingredients improved performance.

Worked example: A standard mix averages $5 per input kilogram and permits 900 kg input for actual output. Actual input is 950 kg. Yield is $250 adverse. If the actual composition costs $100 less than standard proportions, mix is $100 favourable and usage is $150 adverse.

Common mistake: Using actual purchase prices to value a material mix variance introduces price changes into an analysis intended to isolate input composition.

Official syllabus reference: [2]

43. Sales volume split into mix and quantity

Sales mix variance isolates changes in the proportions of products sold by comparing actual quantities with actual total sales redistributed into the budgeted mix. Sales quantity variance measures the effect of total unit volume changing while holding the budgeted mix constant. Value differences using standard contribution for a marginal-costing analysis, or the specified standard profit basis where appropriate. Mix and quantity should reconcile to sales volume variance. A favourable volume total can hide a shift toward lower-contribution products. This analysis assumes a meaningful unit aggregation and does not by itself explain price discounts, market changes or capacity effects.

Worked example: Budget mix is equal quantities of A and B, contributing $20 and $10. Actual total sales are 1,000 units: 400 A and 600 B. Compared with 500 each, the mix change loses $1,000 contribution even though total unit sales are unchanged.

Common mistake: Calling every increase in total units a favourable mix effect confuses the amount sold with the relative proportions of different products.

Official syllabus reference: [2]

44. Planning and operational price or labour variances

Planning variances compare an original standard with a justified revised standard; operational variances compare actual results with that revised benchmark. This can separate unrealistic planning assumptions or external changes from execution. For material price, use a consistent quantity basis so original-to-revised and revised-to-actual effects reconcile. Labour analysis may similarly distinguish changes in an appropriate time standard, including a revised learning assumption, from actual efficiency. Revisions require independent evidence and a clear policy. Updating a benchmark merely because actual performance was poor removes accountability and makes favourable operational results artificially easy to obtain.

Worked example: For 8,000 kg, the original price standard is $4, a justified revised market benchmark is $4.50 and actual price is $4.70. Planning price variance is $4,000 adverse; operational price variance is $1,600 adverse, reconciling to $5,600 against the original standard.

Common mistake: Revising standards to equal actual results eliminates operational variances without demonstrating that the original assumptions were genuinely invalid.

Official syllabus reference: [2]

45. Market size, market share and variance investigation

A market-size variance values the sales change expected from actual market volume at the budgeted share. A market-share variance compares actual sales with that revised constant-share benchmark. Using standard contribution separates these volume effects from selling-price changes. The split helps distinguish market opportunity from competitive performance, but market-share outcomes may still reflect deliberate pricing, product shortages or quality choices. Reconcile both effects to the overall sales-volume variance, then investigate material causes and linked indicators. Positive sales growth alone is insufficient evidence of strong execution when the market grew faster.

Worked example: Budget market demand is 50,000 units with 20% share. Actual market demand is 60,000, so the revised benchmark is 12,000 units. Actual sales of 11,000 exceed the original 10,000 but fall below the market-adjusted benchmark, separating favourable market growth from adverse share performance.

Common mistake: Judging sales managers solely against original sales volume can reward market expansion while concealing a deterioration in the organisation's competitive share.

Official syllabus reference: [2]

Performance measurement and control

46. Profitability decomposition: margin and asset turnover

Profitability analysis links operating margin with asset turnover to explain return on capital employed when consistent definitions are used. Operating margin compares operating profit with revenue; asset turnover compares revenue with capital employed. Their product equals operating profit divided by capital employed. A higher return may therefore reflect better margins, more efficient asset use or both. Compare periods and peers with attention to accounting policies, asset age, business models and exceptional items. A ratio change identifies a performance pattern, while explanations require evidence about prices, costs, volumes and investment rather than an unsupported causal story.

Worked example: A business earns $200,000 operating profit on $2 million revenue and $1 million capital employed. Margin is 10%, asset turnover is two and return is 20%. If turnover falls to 1.5 with margin unchanged, return falls to 15%.

Common mistake: Attributing a return improvement entirely to cost control ignores that asset disposals, sales growth or a smaller capital base can change the ratio.

Official syllabus reference: [2]

47. Liquidity, working-capital efficiency and gearing

Liquidity ratios assess short-term financial capacity, while working-capital measures examine how long resources remain tied up in inventory and receivables relative to supplier credit. The current ratio includes inventory; an acid-test measure normally excludes it. Inventory days, receivables days and payables days require appropriately matched balances and flow measures. Gearing indicates reliance on debt using the definition specified, and interest cover compares earnings with financing charges. Interpret these together and against operating conditions. More inventory can improve the current ratio while weakening cash conversion, and longer payables may preserve cash while damaging supplier relationships.

Worked example: Receivables of $300,000 against annual credit sales of $3.65 million imply approximately 30 receivables days using 365 days. A rise to 45 days may explain cash pressure despite reported sales growth, particularly if supplier payment terms remain unchanged.

Common mistake: Treating an improved current ratio as conclusive evidence of stronger cash management ignores slow-moving inventory and overdue receivables within current assets.

Official syllabus reference: [2]

48. Balanced scorecard and linked performance drivers

The balanced scorecard connects strategy with financial, customer, internal-process, and learning-and-growth perspectives. Financial measures describe economic outcomes, while other perspectives can expose drivers of future performance such as retention, first-pass quality and employee capability. Select measures because they fit the strategy, not merely to fill four boxes. Proposed cause-and-effect links are hypotheses requiring evidence, and too many indicators dilute attention. Combine leading and lagging measures with clear definitions and appropriate time horizons. A scorecard does not remove trade-offs: improving delivery speed, cost and quality may require deliberate resource choices.

Worked example: A service company tracks operating margin, customer renewal, first-contact resolution and staff certification. Management hypothesises that better capability improves resolution and then retention. Reviewing these relationships across periods tests whether training expenditure is producing the intended operational and financial benefits.

Common mistake: Assuming every non-financial measure is automatically a leading indicator overlooks that complaints or defects may record outcomes after the underlying failure.

Official syllabus reference: [2]

49. Short-termism, timing effects and financial manipulation

Short-termism arises when actions improve near-term reported results at the expense of longer-term objectives. Cutting maintenance or training may raise current profit while increasing future breakdowns or capability gaps. Financial manipulation can also involve timing, classification or estimates that alter apparent performance without equivalent economic improvement. Analyse incentives, recognition timing and non-financial consequences rather than assuming all favourable profit movements reflect genuine progress. Match rewards to controllable outcomes over appropriate horizons and use corroborating measures. Distinguish a valid cost saving from deferred expenditure or shifted consequences using evidence about service quality, asset condition and future commitments.

Worked example: A manager delays necessary maintenance until the following quarter, increasing current profit by $25,000. Machine downtime then rises. A quarterly profit-only bonus may reward the delay, whereas maintenance compliance and rolling reliability measures reveal the deterioration before annual financial results fully capture it.

Common mistake: Labelling every reduction in discretionary expenditure short-termism ignores whether the activity was ineffective and whether the saving preserves future operating capability.

Official syllabus reference: [2]

50. ROI and residual income for investment centres

Return on investment divides an appropriately defined profit by the corresponding investment base. Residual income deducts a capital charge, calculated as required return multiplied by investment, from that profit. ROI supports relative comparison but may discourage projects returning less than a division's current ROI despite exceeding the organisation's required return. Residual income exposes the incremental surplus above the capital charge, but absolute amounts favour larger divisions. Use consistent controllable profit and investment definitions, accounting periods and asset valuations. Neither measure independently resolves differences in risk, asset age or investment timing.

Worked example: A division earns 24% ROI, while a proposed $500,000 project earns $90,000 annually, or 18%. With a 12% required return, the project adds $30,000 residual income. Accepting it lowers divisional ROI while improving the surplus over the group's capital charge.

Common mistake: Using the division's current ROI as the residual-income capital charge replaces the stated required return and can recreate the same investment bias.

Official syllabus reference: [2]

51. Transfer-price ranges and group opportunity cost

A supplying division's minimum transfer price is incremental transfer cost plus opportunity cost. With spare capacity, opportunity cost may be zero; when transfers displace external sales, include the contribution sacrificed after avoiding external-only costs. The receiving division's maximum reflects its relevant alternative, often the adjusted external purchase price or incremental benefit from the input. A mutually acceptable range exists when the minimum does not exceed that maximum. Internal transfer revenue cancels within group profit, so the group decision depends on external cash flows and opportunity costs rather than the chosen accounting price alone.

Worked example: A supplier has $22 variable manufacturing cost and no displaced sales. The buyer can obtain an equivalent component externally for $31 including delivery. A price between $22 and $31 can support both divisions' acceptance, while group savings are $9 per transferred unit.

Common mistake: Treating the transfer price as an additional group cost double-counts an internal charge that is offset by another division's internal revenue.

Official syllabus reference: [2]

52. Transfer-pricing objectives and multinational tensions

A transfer-pricing system should support sound group decisions, meaningful divisional performance evaluation and appropriate managerial autonomy. Market, cost-based and negotiated approaches can serve these aims differently. Actual-cost transfer prices may pass supplier inefficiency to the buyer, while standard-cost prices can preserve responsibility for cost variances. Multinational arrangements also face exchange-rate exposure, different market conditions, customs and tax considerations, and applicable local requirements. These create constraints rather than permission to choose any price that improves reported group results. Evaluate the supplied facts without inventing tax rates, legal rules or a universally acceptable pricing basis.

Worked example: A supplying division's actual production cost rises because of avoidable waste. An actual-cost-plus transfer passes that increase to the receiving division. A standard-cost basis leaves the waste variance with the supplier, although both divisions still need a price that supports sensible sourcing decisions.

Common mistake: Assuming a single transfer-price method simultaneously optimises autonomy, motivation, performance comparison and multinational compliance overlooks conflicts among those objectives.

Official syllabus reference: [2]

53. Economy, efficiency and effectiveness in value for money

Economy concerns acquiring appropriate-quality inputs at suitable cost. Efficiency relates resources consumed to outputs delivered. Effectiveness concerns achievement of intended objectives or outcomes. A low purchase price is not economical if quality becomes inadequate, and a low cost per service does not establish that the service achieves its purpose. Analyse the input-output-outcome chain using measures consistent with the organisation's objectives. Value for money requires balancing these dimensions rather than maximising one in isolation. Outcomes may also reflect external conditions, so favourable changes should not automatically be attributed entirely to management action.

Worked example: A library buys books at lower prices, issues more loans per staff hour and improves access to required study materials. These respectively inform economy, efficiency and effectiveness. Cheap books that users do not need could improve a purchasing measure while weakening the service's objective.

Common mistake: Using total expenditure alone to judge value for money overlooks differences in service volume, quality, outcomes and the resources required by users.

Official syllabus reference: [2]

54. Multiple objectives and equity in not-for-profit services

Public-sector and not-for-profit organisations often pursue several objectives that cannot be reduced to profit. Access, service quality, outcomes and distribution across user groups may conflict with throughput or unit-cost targets. Specify the intended beneficiaries and distinguish total output from coverage of need. Disaggregated measures can expose deterioration hidden by improving averages, but comparisons require appropriate population and case-mix information. Financial sustainability still matters because services consume resources. Evaluate trade-offs explicitly rather than assuming higher volume means greater mission achievement or that equal spending per user always represents equitable provision.

Worked example: A support charity increases total appointments by 20%, but rural appointments fall while rural unmet need rises. Aggregate productivity improves, yet geographic access may worsen. Reporting appointments relative to eligible population by area would better connect delivery with the charity's access objective.

Common mistake: Treating equal service counts across districts as automatically equitable ignores differences in population size, barriers to access and intensity of need.

Official syllabus reference: [2]

55. Benchmarking and fair external comparisons

Benchmarking compares performance or processes with relevant peers, internal units or recognised strong performers to identify improvement opportunities. Comparability requires consistent definitions, periods, service scope and quality. Differences in scale, case complexity, geography or asset age may explain apparent gaps without excusing controllable inefficiency. Process benchmarking can reveal how results are achieved rather than merely rank outcomes. Use adjusted comparisons and investigate practices before adopting them. A peer's lower cost may reflect excluded activities or weaker service, while a genuinely better process may be transferable only after local constraints are considered.

Worked example: Two councils report refuse-collection costs per household. One includes recycling and serves remote properties; the other excludes recycling and serves a compact urban area. Separating service components and route characteristics creates a more meaningful comparison than ranking the unadjusted headline figures.

Common mistake: Assuming the lowest benchmark cost identifies the best operator overlooks differences in included services, quality and operating conditions.

Official syllabus reference: [2]

56. Absolute and intensity sustainability indicators

Sustainability performance can be expressed as absolute resource use or impact and as intensity per unit of output, revenue or service. Intensity helps compare operational efficiency, while absolute measures show total burden. Both may move in different directions when activity grows. Define reporting boundaries, units, denominators and periods consistently, and distinguish measured quantities from estimated impacts. Link environmental indicators with cost, quality and stakeholder objectives without assuming a single ratio captures sustainability. Improvements in one stage may shift burdens to suppliers, product use or disposal, requiring a broader interpretation.

Worked example: Energy use rises from 100,000 to 110,000 kWh while output rises from 10,000 to 12,500 units. Energy intensity falls from 10 to 8.8 kWh per unit, but total consumption rises 10%. Report both rather than describing the result simply as lower energy use.

Common mistake: Presenting a lower impact per unit as proof of lower total impact ignores changes in production volume and the reporting boundary.

Official syllabus reference: [2]

Employability and technology skills

57. Spreadsheet references, formulas and independent checks

Spreadsheet competence combines correct accounting logic with reliable cell references. Relative references move when copied; absolute references fix both row and column, while mixed references fix one dimension. Separate input assumptions, calculations and outputs so that changes can be traced. Check formulas against a simple independent calculation and test whether signs, units and cost behaviour are sensible. A syntactically valid formula may still answer the wrong requirement. Use available spreadsheet functions where useful, but avoid unnecessary complexity that obscures the calculation or makes errors difficult to identify.

Worked example: Cell B2 contains a standard rate and C5 contains activity. The formula =$B$2*C5 fixes the rate while allowing the activity row to change when copied downward. Checking one result manually confirms both the reference behaviour and the accounting relationship.

Common mistake: Adding absolute references to every cell can prevent intended copying behaviour and does not correct a formula built on the wrong accounting logic.

Official syllabus reference: [2]

58. Digital exhibit extraction and response navigation

Working with digital information requires matching each requirement to the relevant exhibit and transferring the correct value, period and unit. Maintain a clear distinction between budget, revised benchmark and actual data, particularly when several tables use similar labels. Navigate between exhibits and response areas deliberately, preserving working labels so calculations remain understandable after amendment. Reconcile totals and check whether figures are expressed in units, thousands or percentages. Efficient access means retrieving relevant information accurately, not copying every available number. The resulting response should remain self-contained enough for another reader to follow the calculation trail.

Worked example: An exhibit reports revenue in $000 while a separate note quotes a $25 unit selling price. Converting $750,000 revenue before dividing gives 30,000 units. Recording the source period and unit beside the working prevents an apparently plausible but thousand-fold quantity error.

Common mistake: Copying a displayed number without its unit and period can silently mix thousands with dollars or original budgets with revised benchmarks.

Official syllabus reference: [2]

59. Decision reports that connect calculations to action

A professional response states the decision or finding, supports it with relevant calculations and explains the operational implication. Use descriptive working labels and consistent monetary or physical units so that the reasoning can be checked. Discursive analysis should interpret scenario evidence rather than repeat definitions or merely describe numerical movements. Distinguish established results, assumptions and missing information, then make a recommendation proportionate to that evidence. Word-processing structure should make separate requirements easy to locate without excessive formatting. A technically correct table needs accompanying interpretation when the task asks for evaluation or advice.

Worked example: Instead of writing only that margin fell by two percentage points, explain that revenue grew but production costs grew faster, identify the supplied material-price increase as relevant evidence, and recommend investigating purchasing and usage separately before attributing responsibility to production.

Common mistake: Repeating every calculated ratio in prose adds length without demonstrating why the movement matters or what management should do next.

Official syllabus reference: [2]

60. Tables and charts that preserve meaning

Choose a presentation format that matches the analytical relationship. Tables support exact comparisons and reconciliations; line charts show changes over ordered time; bars compare categories; scatter plots explore relationships between numeric variables. Label units, periods, series and denominators clearly, and use consistent scales for comparable data. Distinguish percentages from percentage-point changes. Avoid visual choices that exaggerate small differences or conceal relevant variation, and retain essential numerical workings where the reader needs an auditable result. Effective presentation reduces interpretation effort while preserving uncertainty, scope and the meaning of the underlying measures.

Worked example: Customer retention rises from 80% to 84%. A labelled table shows a four-percentage-point rise and a 5% relative increase. A chart with an unexplained truncated axis could exaggerate the movement, so presentation should disclose the scale and use the appropriate description.

Common mistake: Calling a rise from 80% to 84% a four-percent increase confuses percentage points with the relative percentage change.

Official syllabus reference: [2]

Official syllabus sources

  1. ACCA Qualification structure and requirements | ACCA Global
  2. Performance Management - syllabus and study guide September 2026 to June 2027 (PDF, 839KB)
All study guides