CPA PEP Finance Elective common mistakes
CPA PEP Finance Elective · Understand the traps and how to avoid them.
Applying tax at the statutory rate when the exam gives a marginal or effective rate, or mixing pre-tax and after-tax cash flows in the same NPV schedule by discounting after-tax cash flows at a pre-tax rate.
Candidates memorize a single tax rate and stop reading the case facts; the habit of discounting operating cash flows at the WACC while leaving the tax shield on debt or the interest expense inside the flow is common, and time pressure discourages re-deriving the rate from the given data.
What to do instead
Before computing, write the rate chain explicitly: statutory rate, any rate change, and the resulting effective or marginal rate. Build a one-line table of 'pre-tax amount, tax effect, after-tax amount' for each line. Confirm the discount rate is after-tax for after-tax flows; if discounting unlevered flows at WACC, exclude interest from the flows and treat the tax shield in the discount rate or as a separate adjustment.
Selecting a project on IRR alone when the case involves mutually exclusive projects, scale differences, or multiple sign changes in the cash flows.
IRR is the first metric candidates learn and the easiest to compute with a calculator; the case data often presents both IRR and NPV, and candidates default to the higher IRR without checking whether the projects are mutually exclusive or whether NPV profiles cross.
What to do instead
State the decision rule explicitly: for mutually exclusive projects use NPV unless the case says otherwise. Compute the incremental cash flows (B minus A) and the incremental IRR, and check the crossover rate. Flag any project whose cash flow signs change more than once and note that IRR may be unreliable; report MIRR or NPV in that case.
Treating accounting profit or book value as the basis for a valuation or capital decision, instead of converting to free cash flow and market-based values.
Candidates carry over financial reporting habits and use net income, EBIT, or book equity directly in DCF and M&A questions; the case may present only IFRS statements, which invites using reported figures without adjustments for non-cash items, working capital, and capex.
What to do instead
Build a bridge from accounting numbers to cash flow every time: net income plus non-cash charges, minus working capital changes, minus capex, plus or minus financing items as appropriate. For valuation, state that terminal value uses a normalized free cash flow and a market-based discount rate, not book value. Show the adjustment line items rather than a single net figure.
Using the firm-wide WACC to evaluate a project or division with materially different business risk, or computing WACC with book-value weights and then presenting it as a market-weighted cost of capital.
The case gives one set of financial statements and candidates take the easy weights from the balance sheet; they also treat the WACC as a universal number rather than a risk-specific one, and do not notice when the case describes a new line of business or a different industry peer set.
What to do instead
Check whether the case provides a comparable company beta or industry data. If it does, relever the peer beta to the target capital structure and use market-value weights. If it does not, state the limitation and use a risk-adjusted rate with justification. Always label whether weights are book or market and explain why market weights are preferred for WACC.
Reporting a ratio, variance, or trend without a benchmark, and describing the number rather than explaining the business cause and consequence.
Candidates treat financial analysis as a computation exercise and stop after producing the ratio; they have not practiced the 'so what' step and are unsure which comparison (prior year, budget, peer) the case intends.
What to do instead
For every analytical point, use a three-part structure: the computed value, the comparison benchmark (prior period, budget, or peer), and the business explanation with a consequence for the decision at hand. If the case does not specify a benchmark, state the assumption. Cut any sentence that only restates a number without an interpretation.
Building a forecast without tying revenue, working capital, and capex to explicit drivers, then presenting a single point estimate with no sensitivity or scenario analysis.
Candidates default to a flat growth rate because it is fast, and they omit the balance sheet and cash flow links because the case emphasizes the income statement; scenario analysis feels like extra work when time is short.
What to do instead
State the driver for each forecast line (volume times price, days sales outstanding, capex as a percentage of revenue) and show the assumption table before the forecast. Include at least a base, upside, and downside scenario with the key variable flexed, and report the sensitivity of the decision metric (NPV or valuation) to that variable. Ensure the forecast balances: retained earnings roll forward and cash reconciles.
Ignoring hedging, interest rate, or foreign exchange exposure embedded in the case, or recommending a derivative without specifying notional, tenor, and the exposure it offsets.
Risk management questions are often buried in a paragraph of case facts rather than in a separate exhibit; candidates focus on the main transaction and treat the currency or rate exposure as background, and they are less comfortable with derivative mechanics.
What to do instead
Do a deliberate exposure scan: list each foreign currency, floating-rate debt, and commodity input, and quantify the exposure in dollars. Then map each exposure to a specific instrument with notional amount, tenor, and strike or rate, and state whether the hedge is a fair value or cash flow hedge and the accounting consequence. If the recommendation is not to hedge, justify that with the cost of hedging versus the risk tolerance stated in the case.
In an M&A or valuation question, computing a purchase price or synergy value without stating the financing mix, the control premium, and the allocation of synergy between buyer and seller.
Candidates jump to the DCF or multiples calculation and treat the offer price as given; they do not separate standalone value, synergies, and premium, and they overlook how the deal is funded, which changes EPS and leverage.
What to do instead
Lay out the value bridge explicitly: standalone target value, present value of synergies, control premium paid, and net value created for the acquirer. State the financing mix (cash, debt, shares) and compute the pro forma EPS and leverage impact. Show the maximum price the acquirer can pay before value is destroyed, and note the split of synergies between the parties.
Making a recommendation that conflicts with the facts in the case, or failing to identify the ethical or governance issue when a related-party transaction, pressure from management, or an accounting policy choice is described.
Candidates treat the case as a pure calculation and skip the qualitative facts; they also assume that a recommendation supported by the numbers is acceptable without checking independence, conflicts of interest, or the applicable CPA Code rules.
What to do instead
Before writing the recommendation, list the constraints and stakeholders from the case and check the recommendation against each. If a conflict, related-party deal, or pressure situation appears, identify the threat (self-interest, familiarity, intimidation), cite the relevant ethical principle or standard, and state the safeguard or course of action. The recommendation must be consistent with both the numbers and the professional obligations.
Presenting calculations without a clear conclusion, or writing a recommendation that does not answer the specific question asked (for example, recommending a hedge when the question asks whether to accept the project).
Candidates spend most of the time on computation and run out of time for the final answer; they also misread the required, which may ask for a recommendation to a named decision-maker with a specific decision criterion.
What to do instead
Read the required first and write a one-sentence answer before starting calculations. Structure the response as conclusion first, then supporting analysis, then assumptions and limitations. At the end, re-read the required and confirm the conclusion directly answers it and names the decision-maker and the decision criterion used.