How do the three levels differ in the decisions they address?

Operational work turns plans into near-term budgets, cost information, reports and commercial actions. Management work tests medium-term investments, organisational performance and reporting implications. Strategic work evaluates long-term choices, financing, enterprise risk and business value. The same business issue can appear at different levels: an inventory shortage might require an immediate production choice, a redesign of the supply process, or a strategic decision about supplier concentration.

How should I distinguish profit from cash when evaluating a decision?

Profit follows recognition and measurement rules; cash follows payment and collection dates. A credit sale can increase revenue and receivables before any cash arrives. Depreciation reduces accounting profit without a current-period cash payment. For an investment decision, estimate incremental cash flows at their expected dates and discount them; for financial reporting, apply the relevant recognition and measurement rules. Reconcile the two views before claiming that a profitable proposal is affordable.

What makes a case study recommendation sound?

A sound recommendation connects the business facts to a quantified consequence, identifies the assumption most likely to change the answer, and proposes an action within the simulated finance role. For example, a positive base-case net present value may support an investment, but a large loss under a plausible volume shortfall calls for a pilot, a contract commitment or a staged decision. The recommendation should also address reporting, people, controls and stakeholder effects when they materially affect the choice.

CGMA Professional Qualification Study Guide

Start with concept 1 Choose a topic

The CGMA Professional Qualification develops a finance professional’s work across three levels. At the Operational level, you turn data into short-term plans, reports and decisions. At the Management level, you assess investments, manage performance and explain what financial results mean for the business. At the Strategic level, you help leaders choose a direction, finance it and manage the risks that could prevent success. Each level brings together enterprise, performance and financial knowledge in a business case study. This guide follows that progression through concrete decisions: trace a cost to its cause, test an investment against its assumptions, distinguish a reporting adjustment from a cash effect, and recommend action that fits the role you are performing.

E1: Managing Finance in a Digital World

1. How finance helps create value

Finance creates value at several points in a decision. It enables action by producing dependable transaction records and making funds available. It shapes action by testing forecasts, comparing uses of scarce resources and challenging assumptions. It explains outcomes by reporting what happened and why, so managers can adjust. For longer opening hours, start with sales by hour, returns and staffing patterns; average daily sales can hide the hours that matter. Estimate incremental contribution after variable selling costs, then subtract extra wages and utilities. Compare that result with other uses of staff and cash. Once a trial begins, measure actual incremental profit and service effects against the forecast. The Operational level examination blueprint places these connected finance activities within E1.

Worked example: A retailer tests staying open two extra hours on Fridays. Finance checks whether the recorded evening transactions include returns, then forecasts £2,400 extra monthly sales less £1,200 variable costs and £700 staffing costs. The expected £500 monthly gain supports a limited trial. The store manager needs the staffing plan; the finance manager needs the £700 allocation. After four weeks, finance compares actual contribution and customer demand with the forecast before recommending wider use.

Watch the distinction: A sales increase alone does not prove that longer hours create value. Include the extra costs, check whether sales moved from earlier hours, and measure the outcome.

Reference: [1]

2. Digital processes and their controls

Follow a digital purchase from an authorised order through receipt, invoice capture, matching, approval and payment. Each stage answers a different question. Input validation checks that the supplier, quantities, prices and document fields are complete and plausible. Matching compares the invoice with the purchase order and, where applicable, evidence that goods or services arrived. Authorisation confirms that an appropriate person accepted the commitment or exception. A tolerance can speed routine processing, but it is a decision rule, not proof that an invoice is correct. Exceptions need an owner, a reason code and a recorded resolution; otherwise automation may simply accelerate errors. Keep payment release separate from changes to supplier bank details, and reconcile the payment file to approved invoices. This gives an audit trail from the original commitment to cash leaving the business.

Worked example: An invoice for £1,000 matches a purchase order for £900, while a hypothetical rule permits differences of up to £50. The £100 difference exceeds that rule by £50. The system should hold the invoice, show the mismatch and route it to a reviewer who checks the agreed price and receipt. Only a documented correction or authorised order change should allow payment; the £1,000 should not enter an approved payment run automatically.

Watch the distinction: A successful three-way match is not blanket permission to pay. Duplicate invoices, altered supplier bank details and invalid approval rights require separate checks.

Reference: [1]

3. Turning data into reliable information

Before analysing a trend, define exactly what each source counts. An order system may count gross sales, a returns system may record refunds later, and a finance ledger may use posting dates rather than sale dates. Clean duplicate identifiers and invalid dates, then reconcile totals through a documented bridge. Join records using stable transaction keys where possible; matching only on names or amounts risks false matches. Compare units, prices and periods after the definitions agree. A difference that disappears when returns are included is a definition issue; a difference that remains after reconciliation may be an error or a real change requiring investigation. Preserve the original extracts and record each adjustment so another person can reproduce the result. Reliable analysis depends as much on the meaning of the data as on arithmetic.

Worked example: The till feed shows 500 units sold; the reporting feed shows 480 net units because it also includes 20 returned units. Reconciliation is 500 gross units minus 20 returns equals 480 net units. At an assumed uniform net price of £40 per unit, net revenue is 480 × £40 = £19,200. Check whether refunds, discounts or tax alter that assumed price before treating £19,200 as ledger revenue.

Watch the distinction: Two different totals do not automatically mean one system is broken. First align the date range, unit definition and treatment of returns; then investigate any remaining gap.

Reference: [1]

4. Organising finance work

Organise finance work by the information and judgement it requires. High-volume, rule-based tasks such as standard invoice capture suit a shared service because consistent procedures and systems can reduce processing cost. Specialist teams handle matters requiring concentrated technical knowledge, such as complex reporting or tax analysis. A finance partner works near operational managers to understand local demand, customer terms and the consequences of a choice. Clear handoffs matter: the shared service should flag exceptions, the relevant specialist should advise on technical treatment, and the local partner should explain the business context. Decision rights must remain explicit even when work moves between teams. Monitor processing time, error rates and unresolved exceptions as well as cost, since a cheap process that delays decisions can damage value. See the related CIMA qualification guide for the wider pathway.

Worked example: A central team processes 8,000 routine invoices using approved orders and receipt records. It routes a disputed supplier price to the buyer and finance partner, while a technical specialist reviews any unusual accounting treatment. The local partner assesses a proposed customer payment term because it affects collection risk and sales strategy. The process owner tracks open exceptions so none disappear between teams.

Watch the distinction: Centralising every finance decision would remove useful local context. Centralise repeatable processing, but give business partners and specialists defined responsibility for unusual terms and judgements.

Reference: [1]

5. Influencing an operational decision

An insight influences a decision when the recipient can see the action, timing and result that matter to them. Start with the manager's controllable choice, then translate the financial estimate into operational terms. Separate a one-time setup cost from recurring savings and state whether the benefit is gross or net. Show the assumptions that could overturn the conclusion, such as whether reduced spoilage also reduces purchases or merely shifts stock. Recommend a practical trial or implementation date, assign an owner and specify a measure that can be observed frequently enough to correct course. A warehouse manager may respond to spoiled units and handling steps more readily than an annual profit figure alone. Finance should still reconcile the operational measure to purchase and disposal records so reported savings reflect real cash or margin effects.

Worked example: A warehouse can avoid an estimated £12,000 of spoilage each year by changing its stock rotation process at an annual cost of £3,000. Estimated net annual benefit is £12,000 − £3,000 = £9,000, assuming avoided spoilage reduces replacement purchases. Ask the manager to train staff this month and track spoiled units and disposal cost monthly. Review whether both fall before claiming the saving.

Watch the distinction: Quoting a £9,000 benefit without naming the warehouse action is weak advice. The manager needs an owner, start date and measure that tests whether the saving occurs.

Reference: [1]

P1: Management Accounting

6. Cost objects and cost behaviour

A cost object is the item you want to measure: a product, customer, order or department. Direct costs can be traced to that object without an arbitrary allocation; indirect costs need a reasonable allocation basis. Variable costs change with the relevant activity, while fixed costs stay constant in total within a stated activity range and period. These classifications answer different questions. A factory lease may be indirect to one product but direct to a factory department. A supervisor's salary may be direct to a product line yet fixed across a normal output range. Identify the cost object and activity driver before classifying anything. For a short-run decision, the change in total cost often matters more than an allocated cost per unit; for inventory valuation, the relevant reporting method may require an overhead allocation.

Worked example: For one product, material costs £6 per unit and a factory lease costs £2,000 per month. Material is direct to the product and variable with units. The shared lease is indirect to that product and fixed within the assumed capacity range. At 1,000 units, these costs total 1,000 × £6 + £2,000 = £8,000, or £8 per unit. At 500 units, the lease remains £2,000, though its per-unit allocation doubles.

Watch the distinction: A fixed cost is not always indirect, and a direct cost is not always variable. The cost object, time period and activity range determine the classification.

Reference: [1]

7. Absorption and marginal profit

Marginal costing charges fixed production overhead to the period. Absorption costing assigns it to units produced, so unsold units carry a share into closing inventory. If production exceeds sales, absorption profit is usually higher because some fixed overhead is deferred. If sales exceed production, overhead released from opening inventory can make absorption profit lower. Calculate a fixed overhead absorption rate using the stated production basis, then multiply it by the change in inventory units when rates are comparable. This reconciles the profit difference without recomputing every revenue and variable cost line. Watch for under- or over-absorbed overhead when actual spending or activity differs from the planned basis; that adjustment can also affect reported absorption profit. Neither method changes cash paid for the fixed overhead during the period.

Worked example: A factory produces 1,000 units, sells 800 and incurs £4,000 fixed production overhead. With no opening inventory and an actual-output allocation, overhead is £4 per unit. Absorption costing charges 800 × £4 = £3,200 against sales and carries 200 × £4 = £800 in closing inventory. Marginal costing charges all £4,000 now. With identical revenue and other costs, absorption profit is £800 higher.

Watch the distinction: The £800 profit difference is not extra cash or efficiency. It is fixed overhead held in closing inventory under absorption costing and expensed immediately under marginal costing.

Reference: [1]

8. Budgets and variance diagnosis

A static budget mixes spending control with the effect of producing a different volume. Flex it first: apply the planned input quantity per unit to actual output. Then split the material cost difference into price and usage. The price variance applies the difference between actual and standard price to actual quantity purchased or used, provided the quantity basis is stated. The usage variance values the difference between actual and allowed input at the standard price. Their sum reconciles actual material cost to the flexed standard cost when both use the same quantity basis. An adverse price variance can reflect supplier rates, mix or rushed purchasing; adverse usage may reflect waste, quality or production methods. Investigate causes before assigning responsibility, because cheaper material can itself increase usage.

Worked example: The standard is 2 kg per unit at £3 per kg. For 500 units, allowed input is 1,000 kg and flexed cost is £3,000. Actual use is 1,100 kg at £3.20, costing £3,520. Price variance is 1,100 × (£3.20 − £3) = £220 adverse. Usage variance is (1,100 − 1,000) × £3 = £300 adverse. Together they explain the £520 excess.

Watch the distinction: Using the original output budget to judge material use confuses volume with efficiency. Flex to 500 units first; also check the arithmetic, since the price variance here is £220, not £320.

Reference: [1]

9. Contribution and break-even

Contribution is selling price less variable cost per unit. Each unit sold contributes towards fixed costs, then profit. Divide fixed costs by unit contribution to find the sales volume where total contribution exactly covers fixed costs, assuming a stable price, variable cost and product mix over the relevant range. Margin of safety is planned sales less break-even sales; express it in units or as a percentage of planned sales. It shows how much demand can fall before the model predicts a loss. A price change alters contribution per unit, but volume may also respond, so recalculate break-even and test demand together. If capacity is limited, also compare contribution per scarce resource unit. The model is useful for a defined scenario, not a guarantee about actual sales or fixed costs.

Worked example: At £30 selling price and £18 variable cost, contribution is £12 per unit. With £60,000 fixed cost, break-even is £60,000 ÷ £12 = 5,000 units. Planned sales of 6,000 give a margin of safety of 1,000 units, or 1,000 ÷ 6,000 = 16.7%. If price falls to £28 with costs unchanged, contribution becomes £10 and break-even rises to 6,000 units.

Watch the distinction: A lower price does not automatically improve profit by raising sales. The extra units must compensate for lower contribution on every unit sold, subject to capacity and demand.

Reference: [1]

10. Short-term choices under uncertainty

For a short-term choice, include future cash flows that differ between alternatives. A cost already incurred is sunk; it cannot be changed by today's decision. Opportunity cost is the contribution sacrificed by using a scarce resource for one option instead of another. A decision tree lays out choices, uncertain outcomes, probabilities and cash consequences in time order. At a chance node, multiply each outcome by its probability and add the results; then subtract costs associated with the chosen branch. Expected value is an average over repeated comparable decisions, so a positive result may still hide an unacceptable downside for a cash-constrained business. Test probability estimates and the size of losses before recommending action. The CGMA practice questions can help you practise identifying which figures change with the decision.

Worked example: A promotion costs £4,000 now. It brings £9,000 incremental receipts with 60% probability or £1,000 with 40% probability. Expected receipts are 0.6 × £9,000 + 0.4 × £1,000 = £5,800; expected net value is £1,800. The downside outcome loses £3,000. An earlier £600 design fee is excluded if paid regardless of the choice, while the £4,000 is relevant because cancellation avoids it.

Watch the distinction: A past design fee should not be added just because it relates to the promotion. Include only cash flows the current choice changes, while still checking the downside outcome.

Reference: [1]

F1: Financial Reporting

11. Reporting rules and professional judgement

Financial reporting uses defined recognition principles so managers cannot choose revenue timing simply to meet a target. For a customer contract, identify what has been promised and whether control of the goods or service has passed. A signed order may establish a future obligation without satisfying it. Evidence can include delivery records, acceptance terms and the contract itself. If management proposes an unsupported entry, document the facts, the proposed treatment and the reason it conflicts with the evidence. Raise the issue through the finance review and governance channels appropriate to the organisation, keeping a clear record of the response. Professional judgement also requires checking unusual terms that could change when control transfers, rather than assuming every delivery arrangement is identical. The aim is a faithful period result that users can compare and trust.

Worked example: A manager asks finance to recognise £50,000 from an order signed on 30 December. Goods remain in the warehouse, delivery is due in January and the stated facts give no earlier transfer of control. Revenue recognised in December is therefore £0 for that order. Keep the order and delivery schedule, explain the timing to the manager and refer any proposed override to the reporting reviewer before closing the accounts.

Watch the distinction: A signed contract does not by itself mean revenue has been earned. Identify the performance obligation and evidence of satisfaction before deciding the reporting period.

Reference: [1]

12. Accruals and asset measurement

Accrual accounting records expenses in the period receiving the benefit, even when payment occurs earlier or later. A prepayment is an asset representing an unused future service. An accrual is a liability for a service already received but not yet billed or paid. A capital asset is a resource controlled for use over more than one reporting period; its cost is generally allocated through depreciation or amortisation rather than charged entirely when paid. Classification depends on what the payment buys, not its size alone. For a time-based contract, divide the total cost by the service months and allocate the months falling in the reporting period. Check the contract start date, cancellation rights and whether the benefit is genuinely available in future periods. Cash flow records payment once; profit may recognise the cost across several periods.

Worked example: A company pays £12,000 on 1 October for insurance covering the next 12 months and closes accounts on 31 December. Assuming equal monthly coverage, the charge is £12,000 ÷ 12 = £1,000 per month. October through December gives £3,000 expense; the remaining nine months give a £9,000 prepayment. Cash has already fallen by £12,000, while this period's profit falls by £3,000.

Watch the distinction: Charging the entire £12,000 when paid would understate current profit and omit the future coverage asset. Expense follows the period of benefit.

Reference: [1]

13. Reading the primary statements together

Profit, financial position and cash flow describe different aspects of the same activity. Profit includes revenue when earned and expenses when incurred, so it need not equal cash generated. The statement of financial position carries unpaid customer balances as receivables and unpaid supplier balances as payables. Starting from profit under the indirect cash flow method, add back non-cash expenses such as depreciation, subtract an increase in receivables and add an increase in payables, with the precise presentation depending on the statement and starting profit measure. A receivables increase means some recognised sales have not produced cash yet. Compare changes with sales and collection terms before calling them a problem. Check other working capital movements, tax and interest before treating a short reconciliation as a complete cash flow statement.

Worked example: Assume £30,000 profit after a £5,000 depreciation charge. Receivables increase by £8,000; there are no other working capital changes or relevant adjustments in this simplified example. Illustrative operating cash flow is £30,000 + £5,000 − £8,000 = £27,000. The £5,000 reduced profit without using cash now, while the £8,000 increase represents recognised sales not yet collected.

Watch the distinction: Profit of £30,000 does not mean £30,000 arrived in the bank. Depreciation and receivable movements change the bridge from accrual profit to cash.

Reference: [1]

14. Tax bases and timing differences

Current tax concerns taxable profit for the present period under applicable tax rules. Deferred tax addresses future tax consequences when an asset or liability has a different amount for accounting and tax purposes. For an asset, compare its carrying amount with its tax base: the amount deductible for tax when the asset's economic benefits are recovered. If the carrying amount exceeds the tax base, recovery generally creates a taxable temporary difference and a deferred tax liability, subject to the applicable recognition rules and exceptions. Multiply the difference by the tax rate expected to apply when it reverses, using a supplied hypothetical rate in practice calculations. Do not confuse a temporary difference with a permanent item that never reverses. Nor is deferred tax necessarily a bill payable immediately; its timing follows future recovery or settlement.

Worked example: An asset has an £80,000 carrying amount and a £60,000 tax base. Assuming recovery of the carrying amount creates taxable profit, the taxable temporary difference is £80,000 − £60,000 = £20,000. At a hypothetical applicable rate of 25%, the illustrative deferred tax liability is £20,000 × 25% = £5,000. Current tax still requires a separate taxable-profit calculation; the £5,000 is not automatically this year's cash payment.

Watch the distinction: Subtracting the tax base from the carrying amount does not calculate current tax. It identifies a temporary difference whose future tax effect may require deferred tax recognition.

Reference: [1]

15. The working capital cycle

The cash conversion cycle estimates how long cash is tied up between paying for operating inputs and collecting from customers. Add inventory days and receivable days, then subtract payable days. Inventory days represent stock holding; receivable days represent collection time; payable days represent supplier credit. Use consistent periods and appropriate average balances when calculating these ratios from accounts, since closing balances can distort a seasonal business. Shortening inventory or receivable days generally releases cash, while extending payable days delays cash outflow. Yet pushing customers, suppliers or stock levels too hard can harm sales, supply reliability or service. Diagnose the component that changed rather than treating the total as a single cause. A shorter cycle improves liquidity only if underlying activity and margins remain sound, and the days measures are comparable.

Worked example: Inventory is held for 50 days, customers pay after 40 days and suppliers are paid after 30 days. The cycle is 50 + 40 − 30 = 60 days. If receivable days fall to 35 while the other measures stay constant, it becomes 55 days, a five-day improvement. This suggests earlier collection and less cash tied up, assuming sales volume and credit quality are unchanged.

Watch the distinction: A shorter cycle is not automatically better. Delaying suppliers may risk supply, while cutting inventory too far can lose sales; examine the cause and trade-offs.

Reference: [1]

Operational Case Study

16. Turning a sales forecast into cash action

A short-term cash forecast begins with opening cash and places expected receipts and payments on the dates cash will actually move. Sales forecasts need conversion into collection dates; profit forecasts cannot substitute because credit sales, inventory purchases and loan payments have different timing. Separate confirmed flows from uncertain ones, and show the lowest cash point within the period, not only its closing balance. When a gap appears, verify the largest collections, payment due dates and any committed facilities before proposing action. An entry-level finance professional should present the calculation, assumptions and practical options to the finance manager and operational owners. Options might include following up overdue accounts, agreeing payment timing or arranging funding, with customer and supplier effects stated. Keep an updated forecast so actions are taken before a payment becomes due.

Worked example: As the finance officer, I forecast £10,000 opening cash plus £80,000 receipts less £95,000 payments, giving negative £5,000 closing cash. I would verify when the largest customer receipts clear and which supplier payments are contractually due before the shortfall date. I would send the finance manager a dated cash schedule and recommend an early funding discussion while collections are pursued, rather than waiting for the month-end balance.

Watch the distinction: A forecast sales increase cannot cover a payment due tomorrow if customers pay later. Use cash dates and identify the earliest shortfall, not just period totals.

Reference: [1]

17. A capacity-constrained customer order

When a resource is fully used, compare orders by contribution per unit of the scarce resource. Calculate incremental selling price less genuinely variable or avoidable costs, then divide by the bottleneck hours required. An order with positive unit contribution can still reduce total profit if it displaces work earning more per bottleneck hour. Calculate the contribution forgone from displaced work as an opportunity cost. Check whether unused hours exist at the required time, whether overtime or outsourcing is feasible, and whether quality or delivery commitments limit substitution. Customer relationships may justify a lower immediate return, but the strategic benefit needs evidence and a decision owner. In a case response, make the recommendation conditional on the capacity facts and state the price or contribution needed to avoid harming current profit.

Worked example: A proposed order contributes £18 per unit and uses three machine hours, giving £6 per hour. Existing orders earn £8 per machine hour and fill the available capacity. Each proposed unit would displace three hours worth £24, so accepting it reduces contribution by £24 − £18 = £6 per unit. I would decline or seek at least £6 more contribution per unit, unless verified spare capacity or a supported customer benefit changes the decision.

Watch the distinction: Positive £18 contribution does not make the order attractive when machines are full. The relevant comparison includes £24 of contribution displaced by each unit.

Reference: [1]

18. A suspicious performance dashboard

A dashboard percentage is a claim about defined source records, not a substitute for reconciling them. First identify its numerator, comparator period and whether it uses gross or net sales. Then trace source totals through uploads, adjustments and the ledger, checking transaction identifiers for duplication. Recompute the change only after the two periods use the same basis. If one feed includes a duplicate, isolate which period contains it; the direction of the correction matters. Record the original dashboard figure, corrected figure and reason for adjustment, then tell management what remains uncertain. An entry-level finance professional should avoid attributing growth to a campaign or operational improvement until the underlying sales movement is verified. Comparing customer counts, units and average selling price can then help explain genuine growth.

Worked example: Suppose prior sales were £200,000 and the current upload totals £244,000, including a duplicated £20,000 transaction. Corrected current sales are £244,000 − £20,000 = £224,000, so growth is (£224,000 − £200,000) ÷ £200,000 = 12%. The raw feed would falsely show 22%. I would match the duplicate's transaction ID to the ledger and confirm that the dashboard's £224,000 already excludes it before reporting 12%.

Watch the distinction: Do not subtract the duplicate twice or assume which period contains it. Reconcile raw and corrected totals for each period before accepting the dashboard's growth rate.

Reference: [1]

19. Responding to a spending variance

A spending variance becomes useful when it is connected to causes that managers can change. Compare actual cost with a budget flexed for the relevant activity, then separate one-off events from recurring patterns. Check invoices, work orders and equipment logs to determine whether the apparent cause is complete; a cost labelled exceptional may signal neglected maintenance. Assign each action to an owner with a date and a measure, such as callout count, downtime or cost per operating hour. A corrective plan should consider whether a repair costs less than repeated failures and whether it affects service or safety. Report the variance and the proposed action together, while updating the forecast for costs that will continue. Monitoring the recurring component prevents a temporary explanation from hiding a lasting problem.

Worked example: Actual maintenance is £18,000 against a £12,000 flexed budget, so the variance is £6,000 adverse. Work orders show a £4,000 one-off repair and £2,000 extra recurring callouts, exactly explaining the difference. I would ask the maintenance lead to diagnose the recurring fault and compare repair cost with expected future callouts. Track callout count and cost monthly; leave the one-off repair visible separately in the forecast.

Watch the distinction: Calling the entire £6,000 a one-off would hide the £2,000 recurring excess. Separate the causes and monitor the part that can continue.

Reference: [1]

20. Handling pressure to accelerate revenue

Pressure near a reporting deadline can turn a contract date into a misleading revenue date. For services, establish the promised service, when performance starts and how satisfaction is evidenced. Signing creates contractual rights and obligations, but on the stated facts it does not show that the customer received a service before year-end. An entry-level finance professional should retain the contract, schedule and proposed journal, record the factual reason for rejecting premature recognition, and refer the matter to the responsible reporting reviewer. If there are advance receipts, consider whether they represent a liability for future service rather than revenue. Explain the practical next step: confirm the service start date and recognise revenue as obligations are satisfied under the applicable terms. Escalation protects the accuracy of the close while allowing the commercial team to proceed with delivery.

Worked example: A £40,000 service contract is signed on 28 December, with work beginning in January. Assuming no service is delivered or separately satisfied by 31 December, current-period service revenue is £0, not £40,000. I would attach the contract and delivery schedule to the close file, decline the proposed revenue journal and ask the reporting reviewer to confirm treatment. Any advance cash receipt would be assessed as a contract liability on these facts.

Watch the distinction: Year-end signature is not evidence that £40,000 of service was provided. Use the performance schedule and completed work to determine revenue timing.

Reference: [1]

E2: Managing Performance

21. How a business model captures value

A business model explains who receives value, how the organisation delivers it, and how it earns enough to continue. Start with stakeholders: customers, suppliers, partners, employees and investors may want different outcomes. Then identify the value proposition for each important group. A platform might give buyers convenient choice while giving sellers access to demand. Delivery depends on activities, technology and rules that connect those groups. Its cost model shows what each interaction consumes; its revenue model shows who pays, how much and when. The difference funds overhead and any surplus shared with stakeholders. In an ecosystem, participation can matter as much as unit margin: buyers leave if sellers are scarce, and sellers leave if buyers are absent. The management level examination blueprint identifies business models and ecosystems within E2.

Worked example: A platform charges buyers £4 per completed transaction, pays the partner £2 and incurs £1 processing cost. Contribution is £4 − £2 − £1 = £1 per transaction, before fixed platform costs. At 10,000 transactions, that is £10,000. More registered buyers will not deliver that contribution if too few partners can fulfil orders; track completed transactions and partner availability together.

Watch the distinction: A positive contribution per transaction does not prove the model is profitable. Fixed platform costs still need covering, and weak partner participation may prevent the forecast transaction volume.

Reference: [2]

22. Leading performance through people

When performance falls, diagnose the constraint before choosing an intervention. A skill problem appears when people lack the knowledge or practice to complete a task accurately. A motivation problem is more plausible when capable people can perform it but have conflicting incentives, little feedback or no reason to prioritise it. A process problem arises when the workflow, handoffs or system makes timely work difficult even for trained staff. Compare error types, timing and teams, then speak with the people doing the work. A new system release followed by concentrated errors points toward changed screens, rules or handoffs; it does not by itself prove inadequate effort. Match the response to the cause: training and job aids for skill, clearer priorities for motivation, or workflow redesign for process. Measure both accuracy and elapsed time after the change.

Worked example: A fully staffed reporting team misses its deadline after a software release. Of 40 late reports, 28 contain the same new coding error. The manager tests the workflow, finds that the default code changed, corrects the setting and trains reviewers. If late reports fall from 40 to 8 and average preparation time falls from 3 hours to 2, the evidence supports the diagnosis, although other changes should be checked.

Watch the distinction: Treating every missed deadline as poor motivation invites pressure on staff while leaving the faulty workflow in place. Check whether errors began with a specific process change.

Reference: [2]

23. Designing useful performance measures

A useful performance measure connects an action to the outcome the organisation values. Cost per call captures efficiency, but used alone it may reward short calls that leave problems unresolved. Pair it with first-contact resolution, repeat contact, waiting time and customer outcome measures. Define each denominator and measurement period so changes can be interpreted. For example, repeat-call rate could mean customers who call again within seven days divided by customers with an initial call; it should not silently switch to a percentage of all calls. Compare the measures as a set and investigate trade-offs. A lower unit cost is valuable only if the extra demand it creates and any loss of service quality do not outweigh the saving. Use a consistent cohort and avoid treating correlation as proof that the target caused the behaviour.

Worked example: Assume each of 1,000 initial calls generates at most one repeat. At a 10% repeat rate, there are 1,100 calls costing 1,100 × £6 = £6,600. At 20% repeats, there are 1,200 calls costing 1,200 × £5 = £6,000. Cost falls £600, but 100 more customers need another call; assess first-contact resolution and customer impact before calling this an improvement.

Watch the distinction: Comparing £6 with £5 alone ignores the extra calls. A cheaper call can coincide with worse resolution, even when total measured call cost also falls.

Reference: [2]

24. Planning a project’s critical path

A project network begins with tasks, durations and dependencies. Work forward from the start to find each task's earliest start and finish: a task begins only after every predecessor finishes. At a merge, use the latest predecessor finish, because launch cannot proceed while any required branch remains incomplete. Then work backward from the project finish to find latest allowable dates. The difference between latest and earliest dates is float. A zero-float path is critical: delay on it delays completion unless time is recovered elsewhere. Tasks outside that path still need attention, since their float can be consumed and a new critical path can emerge. Check resource assumptions before relying on a network: two nominally parallel tasks may compete for the same specialist. The calculation gives the earliest feasible date under the stated durations and dependencies, not a promise of delivery.

Worked example: Design lasts two weeks. Testing then takes three weeks, while training takes one week in parallel; launch follows both. Testing finishes at week 2 + 3 = 5, and training at week 2 + 1 = 3, so launch can occur after five weeks. Testing has zero float; training has two weeks of float if resources and durations hold.

Watch the distinction: Adding every task duration gives six weeks and ignores parallel work. Equally, calling training harmless is unsafe: more than two weeks of delay would move the launch date.

Reference: [2]

25. Managing project change and benefits

A scope request should be judged against the approved business case, not by its attractive feature list. Identify incremental development and operating costs, incremental benefits, any benefit lost through delay, and risks introduced by the change. Put cash flows on a comparable basis, discounting them when their timing differs. Then check whether the feature alters dependencies, testing effort, customer adoption or the original benefits. The project sponsor should see the net change and the assumptions that drive it; a change with positive stand-alone benefits can still reduce project value. If it fails, consider a smaller release, a later phase or a different design. Protect the baseline by recording the decision, revised scope and owner. Benefits tracking after launch should compare realised outcomes with the revised case rather than treating delivery of the feature as proof of value.

Worked example: A proposed feature costs £30,000, brings £45,000 in discounted benefit and delays launch enough to lose £20,000 of discounted benefit. Its incremental value is £45,000 − £30,000 − £20,000 = negative £5,000. On these assumptions, decline or redesign it. A shorter build that preserves launch timing could change the result, but that needs a new estimate.

Watch the distinction: Approving the change because £45,000 exceeds its £30,000 build cost omits the delayed benefits. The correct comparison includes every incremental consequence of changing the approved plan.

Reference: [2]

P2: Advanced Management Accounting

26. Activity costs and customer profitability

Gross margin is a useful first layer of customer profitability, but it omits the activities needed to serve each customer. Activity-based costing traces support, order handling, delivery and returns through cost drivers such as call counts or deliveries. Choose drivers that explain resource use, then distinguish costs that would change with a customer decision from shared costs allocated for reporting. A customer with high sales can consume disproportionate service effort. Compare customer contribution after attributable activities, then investigate causes: frequent small orders, complex requirements or avoidable errors may be addressed through pricing, minimum order sizes or process changes. The Certified Management Accountant (CMA) study guide offers related management accounting study. A negative allocated customer profit is a diagnostic signal; dropping the customer improves total profit only if the forgone contribution is less than costs actually avoided.

Worked example: Customer A produces £50,000 sales and £15,000 gross margin, but uses 100 support calls at £80 each. Its profit after these calls is £15,000 − £8,000 = £7,000. Customer B produces only £30,000 sales, a £12,000 gross margin and 20 such calls, leaving £10,400. B contributes more after support despite lower sales; compare other attributable costs before deciding.

Watch the distinction: Ranking customers by revenue or gross margin alone hides service consumption. Conversely, an allocated loss does not establish that closing an account will save every allocated cost.

Reference: [2]

27. Target cost and product redesign

Target costing starts with a price the market will bear and subtracts the profit required per unit. The remainder is the allowable cost, which is compared with the current design estimate. This reverses cost-plus pricing: the design must fit a commercially viable price rather than assuming customers will accept whatever price covers current costs. Analyse the gap by component and by function. Value engineering seeks cheaper ways to deliver features customers value, while testing quality, reliability, warranty and life-cycle effects. A component saving that increases returns may fail economically even if the factory cost falls. Price changes require demand evidence: a higher margin per unit can reduce total profit if volume falls enough. Keep the target tied to a specified volume and product life, since required profit and cost structure may change as production scales.

Worked example: At a market price of £200 and required profit of £40 per unit, allowable cost is £160. Estimated cost is £175, leaving a £15 gap. One redesign saves £12 in components and £3 in assembly without changing performance, meeting the target. A £15 price rise also restores unit profit arithmetically, but demand research predicts fewer sales, so test total profit before choosing it.

Watch the distinction: Subtracting a 40% margin instead of the stated £40 profit changes the target incorrectly. Also, closing a factory-cost gap is insufficient if the redesign increases later service costs.

Reference: [2]

28. Capital investment with sensitivity

Net present value compares the present value of incremental future cash flows with the initial investment. Multiply each period's cash flow by its discount factor and subtract the initial outlay; use a cumulative factor only when equal cash flows occur at the same spacing across periods. Include cash consequences such as working capital and disposal proceeds when given, and exclude sunk spending. A positive NPV indicates value under the stated forecasts and discount rate. Sensitivity analysis then changes one uncertain input to show how fragile that conclusion is. The break-even annual cash flow equals initial cost divided by the cumulative factor, assuming identical annual flows and no other cash items. This is more useful than reporting a single forecast without its margin for error. Sensitivity is not a probability assessment: it shows the effect of an input change, not how likely that change is.

Worked example: Assume £100,000 paid now, followed by £45,000 each year for three years, and a hypothetical cumulative discount factor of 2.487. NPV is £45,000 × 2.487 − £100,000 = £11,915. If annual cash falls to £40,000, NPV is £99,480 − £100,000 = negative £520. Break-even annual cash is about £40,209, subject to factor rounding.

Watch the distinction: A positive base-case NPV is not a guarantee. Here a £5,000 fall in annual cash reverses the decision, so the demand assumption needs particular scrutiny.

Reference: [2]

29. Divisional returns and transfer prices

Return on investment divides divisional profit by invested assets. It helps compare performance, but a manager whose current ROI exceeds the required return may reject a profitable project that lowers the division's average. Residual income addresses that incentive by subtracting a capital charge from profit: project residual income is project profit less required return times project assets. It shows value above the minimum return, though comparisons across divisions of different size need care. Transfer pricing creates a related incentive problem when one division supplies another. With spare capacity, the supplying division's minimum acceptable price is its incremental cost, assuming no lost external sale; with full capacity, add the contribution forgone on displaced sales. The receiving division should not pay more than the cost of its best available alternative. A negotiable range exists only when these bounds overlap.

Worked example: A division earns £200,000 on £1 million assets, an ROI of 20%. A project earns £30,000 on £200,000, or 15%; combined ROI becomes £230,000/£1.2 million = 19.17%. At a hypothetical 10% capital charge, project residual income is £30,000 − £20,000 = £10,000, so it adds value. For an internal component costing £5 incrementally, with £2 lost contribution and an £8 outside alternative, £7 to £8 is a feasible transfer-price range.

Watch the distinction: Rejecting the project solely because it lowers average ROI sacrifices £10,000 of residual income. A transfer price should also reflect capacity and forgone sales, not just accounting cost.

Reference: [2]

30. Controls for operational risk

Operational controls should address a named failure route. A preventive control blocks an error or unauthorised act before it occurs; a detective control identifies one afterward so it can be corrected. In purchasing, separating vendor creation from payment approval reduces the chance that one person can create a false supplier and pay it. Independent verification of changed bank details addresses a different route: a real supplier's details may be replaced. A payment-to-approved-vendor reconciliation can detect transactions that escaped the first controls. Give each control an owner, evidence of operation and a review frequency suited to the risk. Assess residual exposure after considering system access, collusion, emergency overrides and whether reviewers actually investigate exceptions. A control that exists on paper but leaves the same person able to change access rights and clear alerts offers little protection.

Worked example: A buyer can create a vendor and approve a £12,000 payment to it. Separate the two permissions and have an independent employee confirm bank details using an established supplier contact. A finance reviewer then matches paid vendors to approved records and investigates changes. These steps reduce one-person fraud, but two employees acting together or an unchecked administrator override could still bypass them.

Watch the distinction: Adding a second signature to a payment is weak if the signer relies on the buyer's unverified vendor record. Address the record's creation and changes as well.

Reference: [2]

F2: Advanced Financial Reporting

31. Cost of capital for financing choices

Weighted average cost of capital combines investors' required returns using the market values of equity and debt as weights. Estimate the cost of equity and the current cost of borrowing, then apply a tax adjustment to debt interest only where the assumed tax benefit is usable. Divide each market value by total financing value and sum the weighted costs. The result can serve as a discount rate for projects with risk comparable to the firm's existing operations and financing assumptions. It is not automatically suitable for a much riskier project. Debt may initially lower the weighted cost because interest can produce a tax benefit, but more borrowing can increase default risk and the returns demanded by both lenders and shareholders. Check covenant headroom, cash flow resilience and financing flexibility alongside the arithmetic. The CIMA qualification guide places this calculation in the wider finance pathway.

Worked example: Suppose market-value equity is £6 million with a 12% required return and debt is £4 million costing 6% before a hypothetical 25% tax adjustment. The weights are 0.6 and 0.4. WACC is 0.6 × 12% + 0.4 × 6% × 0.75 = 7.2% + 1.8% = 9%. More debt could raise borrowing and equity costs, so 9% is not a permanent rate.

Watch the distinction: Using book-value weights when market values are available can misstate financing proportions. Applying the tax adjustment to equity, or assuming debt stays at 6% as leverage rises, also distorts WACC.

Reference: [2]

32. Revenue across performance obligations

The five-step revenue model asks you to identify the contract, identify distinct promises, determine the transaction price, allocate that price, and recognise revenue as each performance obligation is satisfied. A promise is distinct when the customer can benefit from it and it is separately identifiable in the contract. For a bundle discount, allocate the total price using relative standalone selling prices unless a specific allocation rule is justified by the facts. Equipment commonly transfers at a point in time when control passes, while a stand-ready support service is generally fulfilled over its service period. Contract signing and cash collection do not alone determine revenue timing. Confirm the actual promises, variable consideration and any conditions affecting control before posting. This framework also helps explain why a single invoice can produce revenue in different periods. Related reporting principles appear in the ACCA qualification guide.

Worked example: A customer pays £1,100 for equipment and one year of support. Standalone prices are £900 and £300, totalling £1,200. Allocate £1,100 × £900/£1,200 = £825 to equipment and £1,100 × £300/£1,200 = £275 to support. If equipment control transfers immediately and support is provided evenly, recognise £825 then and £275 over the year, subject to the contract facts.

Watch the distinction: Recognising all £1,100 when the equipment ships ignores the unsatisfied support promise. Allocating the £100 bundle discount entirely to support also needs justification.

Reference: [2]

33. Building group accounts

Group accounts present a parent and controlled subsidiaries as one economic entity. Control depends on power over relevant activities, exposure to variable returns and the ability to use that power to affect those returns; a shareholding percentage is evidence, not the whole test. At acquisition, compare consideration transferred plus the measured non-controlling interest with the fair value of identifiable net assets. The excess is goodwill under the assumed measurement basis. Subsequent consolidation combines assets, liabilities, income and expenses, then removes transactions and balances within the group because the group cannot owe itself money or earn revenue from itself. Review any unrealised profit left in inventory as well. Separate the share of profit and net assets attributable to outside shareholders. A correct acquisition calculation can still produce misleading group figures if internal sales or balances remain.

Worked example: A parent pays £700,000 for control. Assume the non-controlling interest is measured at fair value of £180,000 and identifiable net assets have acquisition-date fair value of £800,000. Goodwill is £700,000 + £180,000 − £800,000 = £80,000. If the parent records a £25,000 receivable from the subsidiary and the subsidiary a matching payable, eliminate both £25,000 balances on consolidation.

Watch the distinction: Adding the subsidiary's accounts without eliminations overstates group receivables and payables. Goodwill also cannot be computed from the parent's payment alone when the stated method includes non-controlling interest.

Reference: [2]

34. Connecting financial and sustainability reports

Financial statements measure recognised financial position and performance under accounting rules; sustainability information can describe resources, risks and effects that influence future value without appearing as current revenue or expense. Read a sustainability claim by checking its boundary, period, baseline and denominator. Absolute energy use answers how much energy was consumed. Energy intensity answers how much was used per unit of output; the two can move in opposite directions. A fall in total energy during lower production is not necessarily an efficiency gain. Ask whether measurement methods, site coverage and output mix stayed comparable. Connect the claim to financial implications carefully: higher energy intensity may suggest cost pressure, but prices and operating conditions also matter. Good reporting explains both the physical measure and the business context rather than treating a favourable percentage in isolation as proof of improved performance.

Worked example: A plant used 100 energy units to produce 100 output units last year. This year it uses 90 energy units, a 10% absolute reduction, but makes 80 output units, a 20% fall. Intensity rises from 100/100 = 1 to 90/80 = 1.125 energy units per output unit, a 12.5% increase. The claim of lower total use is true; an efficiency claim is unsupported.

Watch the distinction: Calling a 10% fall in energy use an efficiency improvement ignores production volume. Check intensity and whether the same sites, products and measurement methods are being compared.

Reference: [2]

35. Interpreting ratios in context

Ratios are clues about performance, liquidity and financing, not conclusions by themselves. Calculate them on consistent definitions, then explain the business mechanism behind the movement. Receivable days estimates how long sales remain unpaid: receivables divided by credit revenue, multiplied by days in the period. Closing receivables provide a quick indicator; average balances can be more representative where seasonality or rapid growth makes year-end unusual. Rising revenue with faster-rising receivables may mean slower collections, more generous terms, disputed invoices or a change in customer mix. Compare ageing, write-offs, cash receipts and contract terms before selecting a cause. Liquidity measures should also be read alongside payables, inventory and cash commitments. Accounting changes and acquisitions can move ratios without a comparable operating change, so reconcile the underlying amounts before recommending action.

Worked example: Assume all revenue is credit sales and each period is 365 days. Revenue rises from £1 million to £1.2 million; closing receivables rise from £100,000 to £180,000. Receivable days move from £100,000/£1 million × 365 = 36.5 days to £180,000/£1.2 million × 365 = 54.75 days. The 18.25-day increase suggests collection pressure, but check seasonality and the aged ledger.

Watch the distinction: Sales growth alone does not show stronger cash performance. Closing-balance receivable days can also be distorted by a year-end spike, so check average balances and ageing.

Reference: [2]

Management Case Study

36. Recommending a capital project

A finance manager's capital recommendation should join value, cash capacity and risk in one decision. Start with NPV under the base assumptions, then identify the driver that could turn value negative. Next map the maximum cash outflow and its timing against committed facilities, covenant headroom and other planned uses of cash. A positive NPV does not fund the early payments required to earn it. Propose a staged commitment when information will improve before the full spend becomes irreversible: define the evidence to be collected, who reviews it and a clear condition for the next release of funds. State the downside in monetary terms and how it affects liquidity. In a written management response, lead with a conditional recommendation, support it with the key numbers, and assign the immediate action. CGMA practice questions can help rehearse concise decisions.

Worked example: A project has £90,000 base-case NPV, but a plausible downside case has negative £60,000 NPV. It needs £200,000 peak cash before benefits arrive. Recommend proceeding only after £200,000 of usable funding is secured and an early demand test confirms the forecast. Authorise an initial stage, set the demand result required for the next stage, and report both NPV cases to decision makers.

Watch the distinction: Approving solely because base-case NPV is positive misses the £200,000 funding peak. Rejecting solely because a downside exists also ignores whether staging can limit exposure.

Reference: [2]

37. Fixing an unprofitable sales channel

A channel decision requires a bridge from reported profitability to profit that would change if the channel changed. Start with its contribution after variable sales costs, then subtract channel activities such as fulfilment and support using credible cost drivers. For closure, classify each cost as avoidable, retained or shifted to another channel. Also estimate whether customers will leave, migrate, or reduce purchases; their contribution cannot be assumed to disappear in full. Operational capacity, service quality, staff roles and contract commitments affect both the timing and size of savings. A channel showing a loss after allocated shared overhead may still support group profit if closure does not remove that overhead. The finance manager should recommend a test of customer behaviour and an implementation plan, with owners for service continuity and people impacts, before making an irreversible closure decision.

Worked example: A channel produces £120,000 annual contribution and uses £150,000 of genuinely avoidable fulfilment and support costs. If closing it removes both amounts and has no other effect, annual profit rises by £150,000 − £120,000 = £30,000. If £40,000 of customer contribution migrates to another channel without extra cost, the gain becomes £70,000. Validate migration, contracts and staff costs before closure.

Watch the distinction: A reported channel loss is not automatically a closure saving. Allocated overhead may remain, and customer migration or lost cross-sales can change the incremental result.

Reference: [2]

38. Explaining group performance

A group profit movement may mix operating improvement with changes in the group's perimeter and one-off transactions. Reconcile reported growth into the contribution from newly acquired businesses, disposal gains or losses, and a comparable movement from the businesses owned in both periods. Check that acquisition profit covers only the post-acquisition period included in consolidation. Also test whether changes in accounting policies, exchange rates or intra-group eliminations affect comparability. The remaining figure is a useful starting point for underlying growth, not a complete explanation of performance. Examine revenue, margin and recurring costs within that comparable business before attributing the change to operations. A concise management briefing should show the arithmetic, label one-off items, and state what information is still needed. That lets decision makers distinguish a stronger ongoing business from a higher reported total created by acquisition or disposal timing.

Worked example: Reported group profit is £40,000 higher than last year. Of that increase, £25,000 is post-acquisition profit from a new subsidiary and £10,000 is a one-off disposal gain. The remaining movement is £40,000 − £25,000 − £10,000 = £5,000. Describe £5,000 as growth from the comparable business only if consolidation, currency and accounting changes do not add further reconciling items.

Watch the distinction: Calling the full £40,000 increase organic growth attributes acquisition and disposal effects to continuing operations. Even the £5,000 remainder needs comparability checks before a firm conclusion.

Reference: [2]

39. Delivering change with stakeholders

Stakeholder planning asks who can influence a project and who will feel its effects. A power-interest map helps set the level of engagement, but it should be updated as decisions and concerns change. Frontline managers may have limited formal approval power yet strongly influence whether a new process is adopted. Investigate resistance as evidence: extra checking time may reflect a genuine control requirement, poor interface design or duplicate work. Observe a pilot, measure the burden and ask which checks prevent errors. Redesign redundant steps while preserving necessary control, then explain the benefit in terms relevant to the managers. Track realised financial savings alongside adoption, error rates and time spent. A project that meets its technology delivery date but creates an unmanageable weekly workload may fail to realise its forecast benefit.

Worked example: A system promises £100,000 annual savings, but ten frontline managers expect two extra checking hours each week. Assuming 50 working weeks, that is 10 × 2 × 50 = 1,000 hours annually. A pilot should measure actual hours and errors, then remove duplicate checks where safe. If adoption and net savings hold after redesign, expand the rollout; otherwise revise the case.

Watch the distinction: Labelling resistance as unwillingness to change misses a potentially material workload. Equally, removing every check to improve adoption could weaken the control the system was meant to provide.

Reference: [2]

40. Keeping an investment controlled

Investment control compares the latest forecast for total cost and benefit with the approved baseline, then makes the next decision using remaining cash flows. Calculate forecast cost at completion as spending to date plus expected remaining spend. Report the variance against approval and the change in expected benefits separately; their combined effect indicates how much the original value case has weakened, provided the benefit figures are on a comparable basis. Past expenditure is sunk for a stop-or-continue decision, although it remains essential for accountability. The manager should reforecast remaining cash flows, risks and funding needs before releasing more money. Set a decision gate with an owner, updated milestones and conditions for continuing. Investigate whether the cost overrun is a one-time estimate error, scope growth or a recurring delivery problem, since each calls for a different response.

Worked example: A project approved at £500,000 has spent £300,000 and now needs £260,000 more. Forecast total cost is £560,000, a £60,000 overrun. Expected benefits are also £80,000 below the approved case, so value has weakened by £140,000 before any timing effects. Pause new commitments for a revised cash-flow forecast; the next decision compares the £260,000 remaining spend with future benefits, treating £300,000 already spent as sunk.

Watch the distinction: The £300,000 spent should not force completion merely to avoid admitting a loss. It belongs in the variance report, while continuation depends on future costs, benefits and risks.

Reference: [2]

E3: Strategic Management

41. Choosing a strategy process

A planned strategy sets a destination, allocates resources and defines milestones before execution. It suits activities where obligations and demand are reasonably predictable, although assumptions still need review. An emergent strategy develops from observed results and unexpected opportunities; it is useful when customer behaviour or technology changes faster than a detailed plan can. Incrementalism makes small, connected changes that preserve learning and limit commitment. The choice also depends on organisational capability: experiments need reliable measures and authority to stop or expand them, while a deliberate plan needs coordination across functions. Separate the long-term objective from the route taken to reach it. A firm can protect its core through planned investment while testing new offers incrementally. Review each route against strategic goals, rather than treating every successful short-term trial as a new strategy.

Worked example: A firm operates a stable regulated service and enters a fast-changing digital market. It plans core staffing and system investment against service obligations. For digital sales, it funds a limited pilot, measures customer retention, contribution after acquisition costs and operational failures, and sets a review date. It scales only if repeat demand and unit economics remain sound beyond the initial promotion. A successful launch-week download count alone would not justify expansion.

Watch the distinction: A deliberate strategy does not require every action to be fixed for years. Its objectives and resource commitments can remain clear while evidence triggers planned revisions.

Reference: [3]

42. Reading the competitive ecosystem

Start with the ecosystem: customers, suppliers, substitutes, competitors and other stakeholders whose decisions affect value. A SWOT separates internal strengths and weaknesses from external opportunities and threats; a strong product is an internal strength, while a scarce input is an external threat. Porter’s Five Forces tests how industry structure may divide the value created. Supplier power rises when inputs are scarce and switching is difficult. Buyer power rises when customers can compare offers and leave cheaply. Mendelow’s power-interest matrix then helps decide which stakeholders need close engagement. Assess both market attractiveness and the firm's ability to capture returns: technical quality, distribution, bargaining position and defensible differentiation all matter. A growing market can still produce poor margins when powerful parties claim most of the surplus.

Worked example: A device maker has superior engineering, but one supplier owns a critical component and customers can switch brands easily. Supplier power is high because the maker has no immediate alternative; buyer power is high because customers have options. If the supplier raises prices, the maker cannot readily pass them on. It should test alternative components and distinctive service benefits before assuming product quality will protect its margin.

Watch the distinction: A SWOT opportunity is external; owning capable engineers is an internal strength. Neither proves that profits will follow when suppliers or buyers hold bargaining power.

Reference: [3]

43. Generating and screening strategic options

Generate options that change the means of competing, rather than variants of one forecast. Building a network develops direct control and capability but takes time. Buying an operator provides faster access but adds integration and valuation risk. Partnering uses another firm's capacity while reducing control and creating dependency. Screen each option through suitability, acceptability and feasibility. Suitability asks whether it addresses the strategic issue and external conditions. Acceptability tests expected returns, downside exposure and stakeholder reactions. Feasibility asks whether funding, people, systems and time are available. Apply a hard constraint first, then compare surviving options using consistent assumptions. If an attractive acquisition cannot be funded, it does not become feasible because its forecast return is high. A staged partnership might also create evidence for a later build or purchase.

Worked example: A company needs a service network within a year. Building costs £1.5 million but takes two years; buying costs £3 million; partnering costs £0.5 million and can begin in three months. With a £2 million funding limit, acquisition fails feasibility by £1 million. Building misses the stated timing need. Partnering is the feasible near-term option, provided contract terms and service quality satisfy customers and management's risk tolerance.

Watch the distinction: The highest projected return is not automatically the best option. An option that breaches a firm funding or timing constraint cannot deliver that return as proposed.

Reference: [3]

44. Making a strategic choice

Compare strategic options on a common basis: expected value, range of outcomes, cash demands, stakeholder effects and ability to execute. Expected value summarises probability-weighted outcomes, but hides severe losses and uncertain estimates. Examine scenarios that could cause the downside, whether the organisation can absorb them, and whether managers possess the capabilities needed to realise the upside. Consider who bears costs or gains, since customer, employee or partner responses can change the forecast itself. A useful recommendation names the preferred option, the conditions attached to it and the evidence that would reverse it. Distinguish a plausible downside from an expected loss: the former describes a scenario, while the latter requires probabilities. Avoid adding numbers with different meanings or treating a larger expected value as decisive when survival or delivery capacity is at stake.

Worked example: Option A has £5 million expected value and a plausible £4 million loss; B has £4 million expected value and a plausible £1 million loss. Suppose the board can absorb only a £2 million loss without cancelling essential operations. Recommend B on current evidence, assuming it fits the strategy and can be delivered. A could be reconsidered if staged investment, insurance or verified demand reduces its plausible loss within capacity.

Watch the distinction: Subtracting the full downside loss from expected value double counts risk. Expected value already weights modelled outcomes; examine the downside separately against capacity and confidence in the model.

Reference: [3]

45. Strategic control in a digital business

A digital strategy needs measures that follow the route from customer interest to durable cash flows. Registrations are an early volume signal, while activation, repeat use and retention reveal whether customers receive value. Contribution per active customer and cash generation are later financial outcomes. Define each measure consistently, including the observation period and denominator, so growth from a promotion does not conceal weaker engagement. Compare cohorts acquired at different times to separate a genuine improvement from an influx of low-intent users. Give managers control measures too, such as service reliability or complaint resolution, because poor delivery may explain weak conversion. A balanced CGMA practice questions exercise should ask what action follows a metric, not merely whether the number rose. Strategic control is a feedback loop: measure, diagnose, act and test whether the action improved value.

Worked example: Registrations rise from 10,000 to 20,000, while monthly active users stay at 4,000. Activation falls from 4,000 ÷ 10,000 = 40% to 4,000 ÷ 20,000 = 20%. The extra registrations have not increased active use. Check acquisition sources, onboarding completion and repeat activity before expanding advertising. Retain the same monthly definition of an active user so the comparison is valid.

Watch the distinction: Doubling registrations does not establish digital success. Without more active users or better economics, the larger total may reflect costly acquisition of people who never adopt the service.

Reference: [3]

P3: Risk Management

46. Risk appetite and response

Risk exposure combines the consequence of an event with its likelihood over a stated period. Expected loss equals probability multiplied by loss amount and helps compare responses, but an average can conceal a loss large enough to threaten survival. Risk appetite is the level and type of risk the organisation is willing to take; capacity is what it can withstand. TARA gives four responses: transfer through a contract or insurance, avoid the activity, reduce likelihood or impact, or accept the residual risk. Assess response cost, exclusions, implementation delay and what remains after the action. For a reduction measure, compare expected loss before and after, then subtract the control cost. Also test the worst credible scenario against capacity. A response may be economical on average yet inadequate if the remaining event could breach a critical financial or operational limit.

Worked example: Assume a one-year disruption has a 20% chance of a £2 million loss. Expected loss is £400,000. A £150,000 control lowers the assumed chance to 5% without changing severity, leaving £100,000 expected loss. The £300,000 reduction exceeds the cost by £150,000. Adopt it if the assumptions are credible, then test whether a £2 million event remains within risk capacity or needs further protection.

Watch the distinction: A positive expected saving does not make residual risk harmless. The control reduces the estimated frequency, while the full £2 million loss can still occur.

Reference: [3]

47. Interacting strategic risks

A risk register is useful for identifying exposures, but separate entries can miss interactions. Two events may share a cause, occur together more often than independence would imply, or amplify each other's impact. Map causal links before aggregating figures: a supplier interruption may force urgent purchases in another currency, while a simultaneous currency shock raises their cost. Scenario analysis asks what happens to cash, deadlines and customers if both events occur. Add any extra consequence created specifically by their combination, rather than simply adding standalone losses. If probabilities are available, joint likelihood needs evidence about dependence; multiplying separate probabilities assumes independence and can understate exposure. Assign an owner for the combined scenario and look for responses that break the link, such as alternative supply, inventory flexibility or a hedge matched to the contingent purchase.

Worked example: A supplier failure alone costs £1 million, and a currency shock alone costs £0.5 million. If both occur, a delayed launch adds £0.7 million. The joint scenario therefore costs £1 million + £0.5 million + £0.7 million = £2.2 million. Reporting only the two standalone risks would miss £0.7 million. Management should test whether alternative supply prevents the launch delay and how likely simultaneous events are.

Watch the distinction: Adding listed risk amounts is not always a complete joint scenario. Interactions can create additional losses, and separate probabilities cannot establish joint likelihood without a dependence assumption.

Reference: [3]

48. Internal control and assurance

Effective internal control joins five elements: the control environment, risk assessment, control activities, information and communication, and monitoring. The control environment concerns leadership conduct, accountability and willingness to challenge exceptions. Risk assessment identifies what could prevent objectives. Control activities include approvals, segregation and reconciliations. Information must reach the right people in usable form; monitoring tests whether controls operate and failures are corrected. Diagnose a failure by following the transaction and the exception trail. An approval limit is weak if senior staff can override it invisibly, even when ordinary transactions comply. Independent review of overrides gives the board evidence about frequency, reasons and outcomes. Assurance should consider both design and operation: a well-written control may be ignored, while an active control may still fail to address the real risk. Escalation must preserve a route outside the person who authorised the exception.

Worked example: Purchases above £50,000 require approval, but executives override the rule without recording reasons. The transaction rule exists, yet leadership behaviour weakens the control environment and absent exception reports weaken monitoring. Require logged overrides with supporting reasons, send a periodic independent report to the board committee, and investigate recurring patterns. Keep the ordinary approval control, while testing whether it operates for both routine and executive transactions.

Watch the distinction: More approval signatures alone will not fix an override problem. If senior staff can suppress or bypass the record, independent visibility and challenge are essential.

Reference: [3]

49. Cyber risk in the supply chain

Vendor cyber risk starts with what the supplier must access to deliver the service, which data are sensitive, and what damage a compromised or misused account could cause. Apply least privilege: grant only required systems, records and actions, for the required duration. Preventive measures include strong authentication, separate vendor accounts and approval of access changes. Detective measures include logs, alerts for unusual downloads and periodic access reviews. Assess evidence that the vendor manages its own staff, devices and incidents, then connect contract duties to technical oversight. Concentration matters too: a sole vendor's outage can interrupt payroll even without data theft. Specify who owns the relationship, who can remove access and how incidents will be communicated. The Strategic level examination blueprint places vendor and partner cyber risk within P3; the control choice still follows the actual access and exposure.

Worked example: A payroll vendor needs employee pay records but requests administrator access across the network. Give it a dedicated account limited to the payroll data and necessary functions, require strong authentication, and log access and exports. Test that payroll can run under those permissions. Review unusual downloads and remove access when the service ends. A signed contract helps assign duties but cannot itself reveal misuse.

Watch the distinction: A trusted vendor does not need unrestricted access. Contractual promises cannot replace access limits and monitoring, especially when its account could be compromised.

Reference: [3]

50. Responding to a cyber incident

Incident response proceeds through containment, evidence preservation, investigation, recovery and reporting, with overlap where speed matters. First stop continuing harm by disabling affected credentials or isolating systems. Preserve logs, timestamps and system images in a way investigators can use; indiscriminate wiping may destroy the evidence needed to identify scope and cause. Determine which accounts, data and services were affected and distinguish confirmed observations from estimates. Recovery should remove the entry route, restore trusted systems and verify normal operation before reconnecting them. Assign operational responders, technical investigators and decision makers clear responsibilities, including who updates the board and affected stakeholders. Reporting obligations depend on the applicable facts and jurisdiction, so record decisions and timing without assuming one universal deadline. After recovery, test whether control changes actually prevent recurrence and whether monitoring would detect a similar attempt earlier.

Worked example: At 02:00, monitoring flags unusual downloads from a compromised account. Disable the account and preserve authentication, access and download logs before changing affected systems. Investigators compare the downloaded records with authorised activity and test whether other accounts were used. Restore access only after credentials and the entry route are secured. The board update states the confirmed account and time, the estimated data scope, remaining uncertainty and the next decision point.

Watch the distinction: Restoring service immediately is not the whole response. If the entry route remains open or logs are lost, the attacker may return and the data impact may remain unknowable.

Reference: [3]

F3: Financial Strategy

51. Setting financial policy

Financial policy sets how much cash to retain, how much debt risk to carry and when to distribute surplus. Begin with organisational objectives and commitments, then forecast cash needs across ordinary operations, investment and adverse scenarios. Liquidity protects the ability to pay when obligations fall due; a profitable business can still fail a cash test. Dividend policy should therefore consider available cash after committed spending and a reasonable operating buffer, as well as future funding access. Gearing can support investment but creates fixed claims and may restrict choices when results weaken. Non-financial commitments, such as a promised plant upgrade or workforce obligations, also affect what cash is truly free. Compare policy choices consistently: a distribution benefits owners now, while retained cash may preserve strategic capacity. Explain the trade-off through dates and cash flows rather than treating the balance-sheet cash figure as entirely distributable.

Worked example: A company holds £8 million cash. It has committed £6 million to a plant upgrade and needs £1 million operating liquidity. On these assumptions, uncommitted cash is £8 million − £6 million − £1 million = £1 million. A proposed £3 million distribution exceeds that amount by £2 million. Recommend reducing or deferring it unless a credible funding plan covers the gap without undermining the upgrade or buffer.

Watch the distinction: Cash in the bank is not identical to surplus cash. Committed investment and operating liquidity have claims on it before a proposed distribution is assessed.

Reference: [3]

52. Choosing long-term funding

Long-term funding should match the project's cash pattern and the organisation's tolerance for fixed obligations. Debt preserves existing ownership but requires interest and repayment, often with conditions that limit flexibility. Equity has no contractual interest payment but dilutes ownership and may be expensive when issued under weak market conditions. Hybrid instruments combine features; their payment, conversion and control terms must be examined rather than inferred from the label. Compare the expected cash available for debt service with a downside case, and include principal repayments and existing commitments. A funding mix can be suitable even when no single source is ideal, provided it survives stress and leaves room for future investment. Also consider whether lenders or investors gain influence over strategic decisions. The lowest stated financing cost is insufficient if a bad year could force asset sales or breach financing terms.

Worked example: A £10 million project could use debt costing £0.7 million annual interest or equity with no fixed interest but ownership dilution. Forecast cash available for that interest is £0.9 million, leaving £0.2 million headroom. In the downside case it is £0.5 million, leaving a £0.2 million shortfall before any principal repayment. Full debt funding is fragile; test a mixed issue, delayed spending or more resilient project cash flows.

Watch the distinction: Equity is not free because it has no interest bill. New investors expect returns and existing owners give up a share of future value and control.

Reference: [3]

53. Managing currency and interest exposure

Transaction exposure comes from a known foreign-currency receipt or payment whose home-currency value can change before settlement. Translation exposure arises when foreign financial statements are converted for reporting. Economic exposure concerns longer-term effects of exchange rates on competitiveness and future cash flows. A forward contract matches a specified currency amount and date to lock the home-currency cash flow; it is most directly suited to transaction exposure. Compare the forward amount with possible spot outcomes, recognising that certainty also gives up favourable moves. Check that the underlying payment is sufficiently certain, because a cancelled transaction could leave a separate hedge position. Interest exposure similarly starts with the cash flow: a floating-rate borrower may seek fixed payments, while a fixed-rate borrower already has payment certainty. The hedge should match the actual timing, amount and nature of the exposure.

Worked example: A firm owes $1 million in three months and agrees a forward rate of £0.80 per dollar. It will pay £800,000. If settlement-date spot is £0.85, an unhedged payment would cost £850,000, so the forward saves £50,000 against that outcome. If spot is £0.75, unhedged cost would be £750,000 and the firm forgoes a £50,000 benefit. The forward's purpose is certainty, not a guaranteed gain.

Watch the distinction: A forward rate is not a forecast of the future spot rate. It fixes the payment for a matched transaction and may look better or worse after rates move.

Reference: [3]

54. Valuing a business from cash flows

A cash-flow valuation estimates what operations are worth from cash available to all providers of finance. Forecast free cash flow after operating needs, tax and reinvestment, then discount it at a rate consistent with the cash-flow risk and financing basis. A continuing value captures cash beyond the explicit forecast period; because it can dominate the result, state its growth and return assumptions clearly. A no-growth perpetuity with the first annual cash flow one year from now equals that cash flow divided by the required return. This gives enterprise value. Bridge to equity value by subtracting net debt and considering any other claims or non-operating assets consistently. Do not mix equity cash flows with an enterprise discount rate. Test whether the forecast can be funded and maintained, since a cash flow that depends on neglected capital spending will overstate value.

Worked example: Assume a business can sustain £5 million annual free cash flow to all capital providers forever, starting in one year, with no growth and a 10% required return. Enterprise value is £5 million ÷ 0.10 = £50 million. With £12 million net debt and no other adjustments, equity value is £50 million − £12 million = £38 million. These values change if cash flow, risk or reinvestment differs.

Watch the distinction: Enterprise value is not automatically the amount shareholders receive. Debt and other claims must be reconciled, and a perpetuity assumes the stated cash flow is sustainable.

Reference: [3]

55. Testing valuation assumptions

Different valuation methods answer the same question using different evidence. A discounted cash-flow model depends on forecasts of growth, margins, reinvestment, tax and the discount rate. A market multiple applies prices observed for comparable businesses to a consistent performance measure, often EBITDA. Reconcile the basis before comparing: an enterprise-value multiple produces enterprise value, and EBITDA must represent comparable operations and periods. A gap may reflect optimistic cash forecasts, an unusual comparable group, different risk or growth, or control and synergy assumptions. Trace the gap to drivers rather than averaging two outputs mechanically. Sensitivity analysis shows which assumptions could close it and how plausible those changes are. The ACCA qualification guide offers related financial reporting context, but a strategic valuation recommendation must also address financing, negotiation and execution risk.

Worked example: A cash-flow model values operations at £60 million. Comparable firms trade at eight times EBITDA, and the target has £6 million comparable EBITDA, giving 8 × £6 million = £48 million enterprise value. The £12 million gap is 25% of the multiple value. Review projected growth, required reinvestment and comparable risk before using £60 million in a bid; do not treat the difference as automatic synergy.

Watch the distinction: Two valuations should not be averaged simply because they differ. First check that both measure enterprise value and identify which assumptions cause the £12 million gap.

Reference: [3]

Strategic Case Study

56. Recommending a strategic direction

A senior finance manager should recommend a direction that the organisation can deliver, not simply the option with the largest modelled value. Establish how each option strengthens competitive position, identify the capabilities needed to earn its projected returns, and test who will build or supply them. Separate value already supported by evidence from value conditional on hiring, systems or partner performance. Assess investment timing, liquidity and the loss if implementation is delayed. A useful recommendation states the preferred route, the reason, conditions for approval and milestones that could change the choice. It should also identify who owns capability development and how the board will measure progress. If a higher-value option becomes feasible only after a capability milestone, preserve it as a future possibility without booking its benefits today.

Worked example: Direct expansion has an estimated £15 million value but requires a service team and market access the firm lacks. A partnership offers £11 million and an experienced delivery team. Recommend the partnership now, subject to enforceable service and data terms. Reopen direct expansion if the firm builds the team, demonstrates market access in a pilot and updates the valuation for development costs. The £4 million value difference alone does not resolve execution risk.

Watch the distinction: A larger forecast value is not a complete recommendation. If the required capability is absent, the forecast may describe a business the firm cannot yet operate.

Reference: [3]

57. Testing an ecosystem dependency

A platform can connect a business to customers while gaining power over fees, access rules and data. Map the dependency: what share of sales passes through the platform, which party controls customer relationships, and how quickly an alternative channel could work. Model fee changes as a reduction in contribution, then consider second-order effects such as lower demand if the firm raises prices. Bargaining power improves when the business can credibly move volume, distinguish its service or secure longer-term terms. A contingency channel must be tested, not merely named, because switching costs and customer habits can make it ineffective. A recommendation should combine contract protection, monitoring of concentration and investment in an alternative where the expected benefit supports it. This connects ecosystem analysis to cash flow and strategic resilience.

Worked example: A digital service expects £4 million annual contribution before a sole platform changes its terms. A £1.5 million fee increase lowers contribution to £4 million − £1.5 million = £2.5 million, a 37.5% decline. Negotiate notice and fee terms, while piloting a direct customer channel. Compare the pilot's acquisition costs and conversion with the fee exposure before claiming that it removes dependency.

Watch the distinction: Access to a large platform does not guarantee durable margins. A partner controlling customer access can capture more value when the business lacks a credible alternative.

Reference: [3]

58. Funding a strategic acquisition

An acquisition decision joins standalone value, buyer-specific synergies, purchase price and the cost of financing and integration. Estimate synergies only when their source, timing, owner and delivery cost are credible. Compare the resulting value to the seller's price on the same basis, then deduct transaction and integration costs to measure value created for the buyer. Test liquidity separately: even a positive-value purchase can create a funding crisis if payment and restructuring costs arrive before benefits. Debt adds fixed service requirements; equity may dilute existing owners. Assess downside cases in which synergies arrive late or fail. A bid ceiling should reflect those risks and the buyer's alternatives, not the seller's asking price. The recommendation should name the price or evidence needed for approval and preserve due diligence before funds are committed.

Worked example: A target is worth £30 million to the buyer, including evidenced synergies. The seller asks £34 million. Before transaction or integration costs, the buyer would pay £4 million more than estimated value, so the deal destroys £4 million on these assumptions. Recommend a price below £30 million after allowing for those costs, or seek new evidence that genuinely increases value. Also confirm funding and post-deal liquidity.

Watch the distinction: Expected synergies cannot be added again if the £30 million valuation already includes them. Double counting would hide the £4 million price gap.

Reference: [3]

59. Balancing strategic risk responses

Strategic risk responses should be assessed against both expected return and the organisation's ability to survive a severe event. Reduction changes the likelihood or impact, transfer shifts defined losses under a contract or insurance, and acceptance retains the exposure. A policy may leave exclusions, deductibles or delays, so check the remaining loss after transfer. For an operational asset, a flood can also interrupt service, affect employees and damage environmental or community commitments. Quantify these effects where evidence permits and describe uncertainties explicitly. Compare the cost of a redesign with the change in plausible loss, but do not subtract two scenario losses as though that difference were a guaranteed saving. Test whether residual loss fits risk capacity and whether the project still meets financial objectives after mitigation. Assign ownership for emergency plans, insurance terms and ongoing monitoring.

Worked example: A plant has £6 million expected value and a plausible £10 million uninsured flood loss. A £1 million redesign lowers that plausible loss to £2 million. If the redesign cost reduces project value pound for pound, revised expected value is £5 million before any probability-related benefit. The severe-loss reduction is £8 million, but its expected benefit needs event likelihood. Recommend the redesign if the remaining £2 million fits capacity, while checking insurance and continuity plans.

Watch the distinction: An £8 million reduction in a plausible loss is not automatically an £8 million increase in expected value. Probability and other consequences determine its financial expectation.

Reference: [3]

60. Maintaining a sound control environment

A sound control environment starts with leaders accepting the same scrutiny they expect elsewhere. In an acquisition, due diligence tests financial claims, legal commitments, technology, people and risks that could alter price or make integration impossible. Assign each open finding an owner, consequence, deadline and decision gate. Independent challenge should reach the board before approval, especially when deal sponsors face pressure to complete. An override may sometimes be proposed, but it must be visible, justified and authorised by someone able to assess the exposure; urgency itself does not remove the risk. Report unresolved issues alongside valuation and funding assumptions so directors can decide whether to pause, change terms or abandon the transaction. After a decision, monitor whether agreed protections and integration actions were completed. A missed deadline has a cost, but bypassing investigation can transfer a much larger unknown cost to the buyer.

Worked example: Leadership wants to sign an acquisition before month-end while customer-contract and cyber findings remain open. The senior finance manager advises the board to retain the due-diligence and approval gates, assigns legal and technology owners to quantify each issue, and requests a revised price and risk view. If findings cannot be resolved in time, negotiate an extension or conditional terms. The calendar date does not establish that the target's liabilities are acceptable.

Watch the distinction: Senior approval does not turn an unexamined risk into a controlled one. The board needs independent evidence about unresolved findings and a recorded decision on their consequences.

Reference: [3]

Official references and further reading

All study guides

Choose your exam version

CIMA E1

CIMA P1

CIMA F1

CIMA E2

CIMA P2

CIMA F2

CIMA E3

CIMA P3

CIMA F3

CIMA OCS

CIMA MCS

CIMA SCS

E1: Managing Finance in a Digital World

1. How finance helps create value

2. Digital processes and their controls

3. Turning data into reliable information

4. Organising finance work

5. Influencing an operational decision

P1: Management Accounting

6. Cost objects and cost behaviour

7. Absorption and marginal profit

8. Budgets and variance diagnosis

9. Contribution and break-even

10. Short-term choices under uncertainty

F1: Financial Reporting

11. Reporting rules and professional judgement

12. Accruals and asset measurement

13. Reading the primary statements together

14. Tax bases and timing differences

15. The working capital cycle

Operational Case Study

16. Turning a sales forecast into cash action

17. A capacity-constrained customer order

18. A suspicious performance dashboard

19. Responding to a spending variance

20. Handling pressure to accelerate revenue

E2: Managing Performance

21. How a business model captures value

22. Leading performance through people

23. Designing useful performance measures

24. Planning a project’s critical path

25. Managing project change and benefits

P2: Advanced Management Accounting

26. Activity costs and customer profitability

27. Target cost and product redesign

28. Capital investment with sensitivity

29. Divisional returns and transfer prices

30. Controls for operational risk

F2: Advanced Financial Reporting

31. Cost of capital for financing choices

32. Revenue across performance obligations

33. Building group accounts

34. Connecting financial and sustainability reports

35. Interpreting ratios in context

Management Case Study

36. Recommending a capital project

37. Fixing an unprofitable sales channel

38. Explaining group performance

39. Delivering change with stakeholders

40. Keeping an investment controlled

E3: Strategic Management

41. Choosing a strategy process

42. Reading the competitive ecosystem

43. Generating and screening strategic options

44. Making a strategic choice

45. Strategic control in a digital business

P3: Risk Management

46. Risk appetite and response

47. Interacting strategic risks

48. Internal control and assurance

49. Cyber risk in the supply chain

50. Responding to a cyber incident

F3: Financial Strategy

51. Setting financial policy

52. Choosing long-term funding

53. Managing currency and interest exposure

54. Valuing a business from cash flows

55. Testing valuation assumptions

Strategic Case Study