Use these concepts to connect accounting principles with calculations and professional decisions. Each example states its assumptions and resolves the problem. Work through the foundations before the applications, and match the material to a verified examination syllabus before treating it as an exam preparation plan.
Financial accounting and reporting foundations
1. Identify the applicable reporting framework
Resolve the reporting framework before applying recognition or measurement rules. Jurisdiction, entity characteristics and reporting purpose can affect applicability. FRS 100 addresses financial reporting requirements for UK and Republic of Ireland entities; its geographical scope does not establish United States requirements.
Worked example: A case states that a United States entity uses US GAAP. A reference discussing FRS 100 cannot establish its inventory treatment; analyze the case under its stated framework.
Mistake to avoid: Treating an authoritative standard from another jurisdiction as automatically applicable.
Reference: FRS 100 Application of Financial Reporting Requirements
2. Keep the accounting equation balanced
Assets equal liabilities plus equity. Analyze both sides of every transaction before deciding whether profit changes. Borrowing increases assets and liabilities, while an owner contribution increases assets and equity. Neither transaction creates revenue merely because cash increases.
Worked example: A business starts with $18,000 cash contributed by its owner and borrows $7,000. Assets are $25,000, liabilities are $7,000 and equity is $18,000.
Mistake to avoid: Recording loan proceeds as income and overstating profit.
Reference: FRS 100 Application of Financial Reporting Requirements
3. Translate transactions into balanced entries
Debits and credits describe entry directions, not favorable and unfavorable outcomes. Asset and expense increases ordinarily use debits; liability, equity and revenue increases ordinarily use credits. Every journal entry must have equal total debits and credits, including entries involving more than two accounts.
Worked example: Equipment costs $9,000, paid with $3,000 cash and $6,000 borrowing. Debit equipment $9,000; credit cash $3,000 and the loan liability $6,000.
Mistake to avoid: Assuming every credit means cash received.
Reference: FRS 100 Application of Financial Reporting Requirements
4. Separate accrual timing from cash timing
Accrual accounting records economic activity when recognition conditions are met, rather than simply when cash moves. An expense can arise before payment, and cash can arrive before revenue is earned. Identify what was delivered, consumed or owed during the reporting period.
Worked example: A business consumes $840 of electricity in December and pays in January. December records an $840 expense and payable; January's payment settles the payable.
Mistake to avoid: Moving the expense into January solely because that is when payment occurs.
Reference: FRS 100 Application of Financial Reporting Requirements
5. Adjust prepayments for benefits consumed
A prepayment initially represents a future benefit. As that benefit is consumed, transfer the appropriate amount from the asset to expense. Use the service period and reporting date, rather than spreading the payment mechanically across the calendar year.
Worked example: A $2,400 insurance payment covers twelve months beginning October 1. At December 31, three months have expired: expense is $600 and the remaining prepayment is $1,800.
Mistake to avoid: Expensing the entire payment immediately when most coverage remains unused.
Reference: FRS 100 Application of Financial Reporting Requirements
6. Understand what a trial balance cannot prove
A trial balance checks whether recorded debit balances equal recorded credit balances. Equality does not establish that transactions are complete, correctly classified or measured accurately. Missing transactions and equal errors on both sides can leave the trial balance balanced.
Worked example: A $450 cash repair is incorrectly debited to equipment and credited to cash. The trial balance still balances, but assets and profit are each overstated by $450.
Mistake to avoid: Treating balanced totals as evidence that the ledger contains no errors.
Reference: FRS 100 Application of Financial Reporting Requirements
7. Connect profit with changes in equity
Financial statements describe related aspects of the same business. Profit generally increases retained earnings, while distributions reduce it. Owner contributions are separate from profit. In a simplified case, reconcile opening equity, contributions, profit and distributions to understand the closing balance.
Worked example: Opening equity is $40,000, profit is $9,000, contributions are $3,000 and distributions are $4,000. Closing equity is $48,000.
Mistake to avoid: Including owner contributions in operating revenue to explain the equity increase.
Reference: FRS 100 Application of Financial Reporting Requirements
8. Distinguish customer advances from earned revenue
Receiving a customer payment does not by itself establish revenue. Analyze the promised goods or services and whether the relevant obligations have been satisfied. An advance ordinarily creates an obligation until performance supports revenue recognition under the applicable framework.
Worked example: A customer prepays $1,500 for five equal service visits. Assuming revenue is earned per completed visit, two completed visits produce $600 revenue and leave a $900 customer-advance liability.
Mistake to avoid: Recognizing the full advance as revenue while three visits remain owed.
Reference: FRS 100 Application of Financial Reporting Requirements
9. Compare inventory cost-flow assumptions
An inventory cost-flow assumption allocates available cost between goods sold and closing inventory. It need not describe the physical movement of every item. Calculate total units and costs before applying the stated method, and use only a method permitted by the relevant framework.
Worked example: Buy 10 units at $8 and 10 at $12; sell 12. FIFO assigns $104 to cost of sales and $96 to inventory. Periodic weighted average assigns $120 and $80.
Mistake to avoid: Using an average selling price instead of purchase cost to value inventory.
Reference: FRS 100 Application of Financial Reporting Requirements
10. Calculate depreciation as cost allocation
Depreciation allocates depreciable cost over an asset's estimated useful life; it does not directly measure changes in market value. Straight-line depreciation divides cost less estimated residual value by useful life. Timing and subsequent estimate changes require consistent treatment under the applicable framework.
Worked example: Equipment costs $14,000, has a $2,000 residual value and a four-year life. Full-year straight-line depreciation is $3,000, leaving $11,000 carrying amount after one year.
Mistake to avoid: Depreciating the residual value as though it will also be consumed.
Reference: FRS 100 Application of Financial Reporting Requirements
11. Separate receivables from expected collection losses
A receivable records an amount owed; a loss allowance reflects estimated amounts unlikely to be collected under the applicable framework. Gross receivables less the allowance produce the net reported amount. Compare the required ending allowance with its existing balance before calculating an adjustment.
Worked example: Receivables are $50,000 and the required allowance is $2,500. With an existing $900 credit allowance, the adjustment is $1,600; net receivables become $47,500.
Mistake to avoid: Charging the entire required allowance again without considering the existing balance.
Reference: FRS 100 Application of Financial Reporting Requirements
12. Reconcile bank and ledger balances
A bank reconciliation separates timing differences from items missing or incorrect in the books. Outstanding payments and deposits in transit ordinarily explain bank-side differences. Bank fees or unrecorded receipts ordinarily require book adjustments. Investigate unexplained differences rather than inserting a balancing amount.
Worked example: Bank balance $5,200 plus a $700 deposit in transit minus $900 outstanding payments equals $5,000. Book balance $5,030 less an unrecorded $30 bank fee also equals $5,000.
Mistake to avoid: Posting outstanding payments again when they are already recorded in the ledger.
Reference: FRS 100 Application of Financial Reporting Requirements
13. Reconcile profit to operating cash
For a simplified indirect reconciliation, add back noncash expenses and adjust operating working-capital movements. Increased receivables or inventory usually absorb cash; increased operating payables usually preserve cash. Remove items whose cash effects belong in other categories, following the relevant reporting framework.
Worked example: Profit is $12,000, depreciation $3,000, receivables increase $2,000 and operating payables increase $1,000. With no other adjustments, operating cash flow is $14,000.
Mistake to avoid: Adding an increase in receivables because reported revenue increased.
Reference: FRS 100 Application of Financial Reporting Requirements
14. Distinguish sector guidance from general standards
Sector guidance addresses specialized transactions or reporting needs alongside broader requirements. The FRC describes SORPs as sector-driven recommendations that supplement its standards and relevant requirements. Determine whether guidance applies to the entity before using it; specialized guidance is not automatically transferable across sectors or jurisdictions.
Worked example: A UK charity and a UK investment fund encounter different sector guidance. A charity-specific recommendation alone does not establish how the fund should report a transaction.
Mistake to avoid: Applying guidance because its title sounds relevant without checking its intended entities.
Reference: Statements of Recommended Practice (SORPs)
Management accounting and operating decisions
15. Distinguish product costs from period costs
Product costs attach to production and can remain in inventory until sale; period costs are charged to the period they relate to. The classification depends on the costing purpose and stated reporting rules. Trace the function of a cost rather than assuming every business expense belongs in inventory.
Worked example: Under a conventional manufacturing absorption model, $6,000 factory rent enters production overhead, while $2,000 head-office rent is a period expense.
Mistake to avoid: Including unrelated administrative costs in inventory merely to defer their expense.
Reference: FRS 100 Application of Financial Reporting Requirements
16. Model fixed, variable and mixed costs
Variable cost changes with activity, while fixed cost remains constant within a relevant range and time horizon. A mixed cost contains both components. Distinguish total cost behavior from cost per unit: fixed cost per unit falls when output increases within existing capacity.
Worked example: A delivery contract costs $400 monthly plus $3 per shipment. At 250 shipments, total cost is $1,150 and average cost is $4.60 per shipment.
Mistake to avoid: Treating the $4.60 average as a constant variable cost at every volume.
Reference: FRS 100 Application of Financial Reporting Requirements
17. Use contribution to calculate break-even
Contribution per unit equals selling price less variable cost. In a single-product model, fixed costs divided by unit contribution gives break-even units. This assumes stable prices, costs and capacity conditions; round upward when whole units are required to cover fixed costs.
Worked example: Price is $35, variable cost $21 and fixed cost $7,000. Contribution is $14 per unit, so break-even is 500 units. Selling 550 units produces $700 profit.
Mistake to avoid: Dividing fixed costs by selling price instead of contribution.
Reference: FRS 100 Application of Financial Reporting Requirements
18. Identify relevant costs for a special order
A relevant amount is a future cash flow that differs between alternatives. Exclude sunk costs and unavoidable allocations. Include incremental fixed costs and any lost contribution from displaced sales. A low price can still be beneficial when spare capacity exists and wider consequences are absent.
Worked example: With spare capacity, 300 extra units earn $18 each and cost $11 each incrementally. A $900 setup cost leaves an incremental benefit of $1,200.
Mistake to avoid: Rejecting the order solely because its price is below fully allocated unit cost.
Reference: FRS 100 Application of Financial Reporting Requirements
19. Allocate a scarce resource by contribution
When one resource limits output, prioritize contribution per unit of that resource, subject to demand limits and other conditions. Contribution per product unit can give the wrong ranking. Multiple interacting constraints may require a broader optimization approach rather than a simple ordering.
Worked example: Product A contributes $24 using three machine hours; B contributes $18 using one hour. B earns $18 per constrained hour versus A's $8, so allocate scarce hours to B first.
Mistake to avoid: Choosing A merely because its contribution per finished unit is higher.
Reference: FRS 100 Application of Financial Reporting Requirements
20. Compare making with buying incrementally
A make-or-buy decision compares avoidable production costs with purchase costs and other incremental effects. Include the value of alternative uses of released capacity. Unavoidable overhead does not become a saving simply because production stops. Quality, reliability and dependency also affect the decision.
Worked example: Making 1,000 parts costs $7,000 avoidable expense. Buying costs $8,000 but releases capacity earning $2,000 contribution. Buying improves the result by $1,000.
Mistake to avoid: Counting all allocated factory overhead as avoidable without checking what actually disappears.
Reference: FRS 100 Application of Financial Reporting Requirements
21. Explain absorption and variable costing differences
Absorption costing includes fixed manufacturing overhead in product cost; variable costing treats it as a period cost. Inventory changes can therefore create profit differences. In a simplified case with stable rates and no opening inventory, the difference reflects fixed overhead carried in closing inventory.
Worked example: Produce 1,000 units and sell 800. Fixed manufacturing overhead is $5 per unit. Absorption profit exceeds variable-costing profit by $1,000 because 200 units retain that overhead.
Mistake to avoid: Interpreting the higher absorption profit as evidence of additional cash generation.
Reference: FRS 100 Application of Financial Reporting Requirements
22. Assign overhead using meaningful activity drivers
Activity-based costing groups overhead by activity and allocates it using drivers connected to resource consumption. Different products may consume support activities differently even when production volume is similar. A useful driver explains cost behavior rather than merely being easy to count.
Worked example: A $12,000 setup cost pool supports 60 setups, giving $200 per setup. A product requiring nine setups receives $1,800 of setup cost.
Mistake to avoid: Allocating setup costs solely by units produced when setup frequency drives the work.
Reference: FRS 100 Application of Financial Reporting Requirements
23. Flex a budget to actual activity
A flexible budget recalculates expected cost for the actual activity level. It separates changes caused by volume from differences in spending or efficiency. Flex variable components using their drivers and retain fixed components within the relevant range; capacity changes may require a different model.
Worked example: Budgeted cost is $4,000 fixed plus $6 per unit. At 900 actual units, expected cost is $9,400. Actual cost of $9,700 is $300 unfavorable.
Mistake to avoid: Comparing actual cost with a budget for a different output level and calling the whole difference inefficiency.
Reference: FRS 100 Application of Financial Reporting Requirements
24. Separate material price and usage variances
A price variance measures paying a different rate; a usage variance measures consuming a different quantity for actual output. State the quantity basis and sign convention. Interpret the variances together because a cheaper material can require more consumption or increase waste.
Worked example: Actual use is 220 kg at $4.50; standard use is 200 kg at $5. Price variance is $110 favorable and usage variance $100 unfavorable, giving $10 favorable overall.
Mistake to avoid: Using planned-output quantities instead of the standard quantity for actual output.
Reference: FRS 100 Application of Financial Reporting Requirements
25. Build a cash budget from payment timing
A cash budget forecasts receipts and payments rather than accounting revenue and expense. Apply collection and payment timing to opening balances and forecast activity. Exclude noncash charges, and distinguish the predicted ending cash balance from any financing required to maintain a stated minimum.
Worked example: Opening cash is $2,000, receipts $8,500 and payments $11,200. Ending cash is negative $700; maintaining a $1,000 minimum requires $1,700 financing.
Mistake to avoid: Including depreciation as a payment or treating every credit sale as an immediate receipt.
Reference: FRS 100 Application of Financial Reporting Requirements
26. Compare return on investment with residual income
Return on investment divides a stated profit measure by invested capital. Residual income deducts a required capital charge from profit. An investment can reduce a division's average ROI while creating positive residual income, so evaluate whether performance measures encourage decisions consistent with the organization's objective.
Worked example: A division earns 20% ROI. A $50,000 project earns $8,000 annually, or 16%. With a 12% required return, its residual income is $2,000.
Mistake to avoid: Rejecting the project solely because its return is below the division's existing average.
Reference: FRS 100 Application of Financial Reporting Requirements
Tax reasoning and compliance foundations
27. Reconcile accounting profit to taxable profit
Accounting profit and taxable profit follow different rules. Start with the stated accounting amount and adjust only for differences established by the applicable tax rules or explicit case assumptions. An expense recorded in the accounts is not automatically deductible for tax purposes.
Worked example: Assume accounting profit is $40,000, a $2,000 expense is nondeductible and $3,000 additional tax depreciation is allowed. Taxable profit is $39,000.
Mistake to avoid: Using accounting profit as taxable profit without examining the stated adjustments.
Reference: FRS 100 Application of Financial Reporting Requirements
28. Distinguish a deduction from a tax credit
A deduction reduces the amount subject to tax; a credit reduces calculated tax, subject to its specific conditions. Their values therefore differ. Refundability, limitations and carryover treatment depend on applicable rules and should not be assumed from the word credit alone.
Worked example: Under a hypothetical flat 25% rate, a $1,000 deduction saves $250. A fully usable $1,000 credit reduces calculated tax by $1,000.
Mistake to avoid: Treating a deduction as a dollar-for-dollar reduction in tax.
Reference: FRS 100 Application of Financial Reporting Requirements
29. Distinguish marginal and average tax rates
A marginal rate applies to an additional amount of taxable income; an average rate divides total tax by a specified income measure. Under a progressive schedule, crossing a bracket boundary does not ordinarily cause the higher rate to apply retrospectively to all income.
Worked example: Assume 10% on the first $20,000 and 20% above it. Tax on $30,000 is $4,000, giving a 13.33% average rate and a 20% marginal rate.
Mistake to avoid: Applying 20% to the entire $30,000 in this hypothetical schedule.
Reference: FRS 100 Application of Financial Reporting Requirements
30. Use adjusted tax basis when analyzing a disposal
Tax basis measures an asset's cost or other amount under the relevant tax rules, adjusted for specified events. A simple disposal calculation compares proceeds with adjusted basis. That arithmetic does not itself determine the gain's character, applicable rate or any recognition exception.
Worked example: Assume an asset has $12,000 initial tax basis and $5,000 basis-reducing deductions. Selling it for $9,000 produces a $2,000 gain before other stipulated adjustments.
Mistake to avoid: Subtracting original cost while ignoring deductions that have reduced basis.
Reference: FRS 100 Application of Financial Reporting Requirements
31. Separate temporary differences from permanent differences
A temporary difference concerns amounts recognized for accounting and tax at different times and can create deferred tax consequences. A permanent difference does not reverse into a future taxable or deductible amount. Apply the governing framework's recognition and measurement conditions before recording deferred tax.
Worked example: Under stated assumptions, faster tax depreciation creates a reversing difference. An expense expressly declared permanently nondeductible creates no future deduction and therefore no deferred tax asset from that item.
Mistake to avoid: Recording deferred tax for every adjustment between accounting and taxable profit.
Reference: FRS 100 Application of Financial Reporting Requirements
32. Reconcile current tax expense, payments and payable
Current tax expense and cash tax payments need not match. Payments can settle opening liabilities or relate to the current period. In a simple payable reconciliation, add current tax accrued to the opening balance and subtract payments, while separately identifying refunds, prepayments and other adjustments.
Worked example: Opening tax payable is $3,000, current tax expense $8,000 and payments $9,500. With no other movements, closing tax payable is $1,500.
Mistake to avoid: Reporting $9,500 as the current tax expense merely because it was paid.
Reference: FRS 100 Application of Financial Reporting Requirements
33. Maintain a traceable tax reconciliation
A defensible tax computation connects each adjustment to the ledger, supporting records and the applicable rule or stated assumption. Reconciliation helps prevent duplicate deductions and omitted income. Documentation supports analysis but does not independently establish that an item qualifies for a tax treatment.
Worked example: A $6,400 expense account contains $5,900 supported transactions and a $500 duplicate posting. Correct the duplicate first; then assess the $5,900 under the relevant tax rules.
Mistake to avoid: Treating every documented payment as deductible without examining its purpose and treatment.
Reference: FRS 100 Application of Financial Reporting Requirements
34. Separate tax arithmetic from jurisdictional applicability
Determine the taxpayer, jurisdiction, tax type and relevant period before selecting rules. A calculation can be internally correct yet answer the wrong tax question. Filing obligations and territorial connections require the applicable current rules; customer location alone does not establish every obligation.
Worked example: A case supplies taxable profit of $50,000 and a hypothetical 18% rate. The calculation is $9,000, but it establishes no actual United States liability or filing requirement.
Mistake to avoid: Transferring a hypothetical rate or jurisdictional assumption into a real tax conclusion.
Reference: FRS 100 Application of Financial Reporting Requirements
Audit evidence and assurance judgments
35. Understand reasonable assurance
A financial statement audit seeks reasonable assurance concerning material misstatement, rather than certainty about every transaction. Estimates, sampling and concealed wrongdoing limit assurance. The conclusion addresses financial reporting under a stated framework; it does not guarantee future profitability or eliminate management's responsibility.
Worked example: A business later loses a major customer. That commercial setback alone does not establish that an earlier audit conclusion about its financial statements was incorrect.
Mistake to avoid: Interpreting an audit as insurance against business failure.
Reference: FRS 100 Application of Financial Reporting Requirements
36. Match assertions to the direction of testing
The testing direction should follow the risk. Moving from recorded items to supporting evidence can address existence or occurrence. Moving from independently identified source items into the records can address completeness. Each procedure also depends on the reliability and coverage of its starting population.
Worked example: To investigate omitted supplier liabilities, select subsequent supplier invoices and trace qualifying amounts into year-end payables rather than sampling only recorded payables.
Mistake to avoid: Using a list that excludes omitted items to test whether omissions exist.
Reference: FRS 100 Application of Financial Reporting Requirements
37. Connect assessed risk with the audit response
Audit risk reflects material misstatement risk and the possibility that procedures fail to detect it. Higher assessed risk generally calls for more persuasive evidence or stronger procedures. The risk model organizes professional judgment; numerical illustrations do not make its components objectively measurable probabilities.
Worked example: A sales system permits unauthorized manual entries. An appropriate response could examine access controls and test unusual entries directly, rather than relying only on stable total sales.
Mistake to avoid: Assuming a familiar process is low risk without considering how it can be overridden.
Reference: FRS 100 Application of Financial Reporting Requirements
38. Evaluate materiality by amount and nature
Materiality considers whether a misstatement could influence users' decisions, individually or with other misstatements. Amount is relevant, but circumstances and the nature of the item also matter. An arbitrary percentage does not replace judgment about disclosures, trends or important contractual conditions.
Worked example: A $2,000 misclassification moves a stated contractual ratio across its limit. Its effect may be significant despite being small relative to total assets.
Mistake to avoid: Dismissing an error solely because it falls below a numerical planning amount.
Reference: FRS 100 Application of Financial Reporting Requirements
39. Distinguish control testing from substantive testing
Control testing examines whether a control operated effectively. Substantive testing examines recorded amounts or disclosures directly. Understanding a process through a walkthrough is useful but does not by itself establish that the control operated consistently throughout the period.
Worked example: Inspecting approval evidence across purchase orders tests a control. Comparing a supplier invoice with the recorded payable directly tests an amount. These procedures answer different questions.
Mistake to avoid: Treating one successful walkthrough as proof of year-long control effectiveness.
Reference: FRS 100 Application of Financial Reporting Requirements
40. Assess evidence quality as well as quantity
Sufficiency concerns the quantity of audit evidence; appropriateness concerns relevance and reliability. Evidence must address the assertion being tested. Consider its source, how it was obtained and whether contradictory information remains unresolved. More evidence of the same weak kind may not solve a reliability problem.
Worked example: Twenty copies of an internally prepared balance listing do not provide twenty independent confirmations. Direct evidence from an appropriate external source may address a different reliability concern.
Mistake to avoid: Counting documents without considering what they establish.
Reference: FRS 100 Application of Financial Reporting Requirements
41. Limit sample conclusions to the tested population
Sampling conclusions depend on the population, selection method and testing objective. A sample can support broader conclusions only under a suitable design. Targeting unusual items is useful for investigation, but such selections do not automatically represent ordinary transactions or support statistical projection.
Worked example: Testing the ten largest invoices establishes findings about those invoices. It does not, by itself, estimate the error rate among thousands of smaller invoices.
Mistake to avoid: Calling a deliberately targeted selection representative merely because it contains many items.
Reference: FRS 100 Application of Financial Reporting Requirements
42. Build an independent analytical expectation
An analytical procedure compares recorded results with a credible expectation based on reliable information and a sufficiently predictable relationship. Establish an acceptable investigation difference for the procedure, then corroborate explanations. Repeating management's forecast without evaluating its inputs creates little independent evidence.
Worked example: Ten properties rented for twelve months at $800 imply $96,000 rent. Recorded rent of $88,000 leaves an $8,000 difference requiring investigation of vacancies, concessions or recording errors.
Mistake to avoid: Accepting 'seasonality' when the expectation already accounts for the full rental period.
Reference: FRS 100 Application of Financial Reporting Requirements
43. Evaluate estimates through methods and assumptions
An accounting estimate depends on methods, data and assumptions rather than a directly observable invoice amount. Evaluate whether they fit the measurement objective and consider contradictory evidence. Sensitivity analysis can reveal uncertainty; a later outcome alone does not prove the original estimate was unreasonable.
Worked example: A receivable-loss estimate assumes 2% defaults, but recent comparable customers show deterioration. Investigate the assumption and supporting data before concluding that the allowance is adequate.
Mistake to avoid: Accepting a familiar estimation percentage without checking whether current evidence supports it.
Reference: FRS 100 Application of Financial Reporting Requirements
44. Separate misstatement from inability to obtain evidence
An identified misstatement and an evidence limitation are different problems. Under conventional financial statement audit frameworks, opinion effects depend on materiality and pervasiveness. A pervasive material misstatement can support an adverse opinion; a pervasive material inability to obtain evidence can support a disclaimer.
Worked example: Confirmed pervasive overstatement differs from missing records that prevent assessment of possible pervasive errors. The first concerns known misstatement; the second concerns insufficient evidence.
Mistake to avoid: Selecting an opinion type without distinguishing known errors from unresolved uncertainty.
Reference: FRS 100 Application of Financial Reporting Requirements
Ethics, governance and information controls
45. Maintain integrity when presenting results
Integrity requires honest presentation and avoidance of information that is knowingly misleading. A technically correct subtotal can still mislead when its description conceals exclusions or uncertainty. Explain the measure, apply it consistently and preserve a traceable reconciliation to the underlying records.
Worked example: Management removes a $12,000 recurring service expense from 'normal profit.' Calling the expense recurring and showing the reconciliation prevents the adjustment from appearing to be an exceptional gain.
Mistake to avoid: Assuming a disclosed arithmetic adjustment makes its misleading label acceptable.
Reference: FRS 100 Application of Financial Reporting Requirements
46. Recognize threats to objective judgment
Objectivity concerns making judgments without inappropriate bias or influence. Personal incentives can distort estimates even without an explicit request to manipulate them. Identify the incentive, assess how it affects the decision and arrange appropriate review rather than assuming awareness alone removes the threat.
Worked example: A manager's bonus depends on profit, and that manager selects a low loss allowance. An independent review of assumptions addresses a concrete bias risk.
Mistake to avoid: Treating the manager's confidence as independent evidence supporting the estimate.
Reference: FRS 100 Application of Financial Reporting Requirements
47. Apply competence and due care to unfamiliar work
Competence involves having suitable knowledge and skills; due care involves applying them diligently. When an assignment exceeds current expertise, define the gap and obtain appropriate technical support or review. Learning a formula does not establish competence to interpret every surrounding contractual or reporting issue.
Worked example: An accountant can calculate a discount factor but has not analyzed a complex financing contract. Obtaining qualified technical review before final classification addresses the knowledge gap.
Mistake to avoid: Presenting a preliminary calculation as a settled professional conclusion.
Reference: FRS 100 Application of Financial Reporting Requirements
48. Protect confidential information appropriately
Confidential information should be accessed and disclosed only for an authorized purpose, subject to applicable obligations. Consider recipient, content and necessity before sharing. A legitimate request for analysis does not automatically justify distributing raw payroll or customer records.
Worked example: A department needs salary expense totals. Providing an authorized aggregate rather than individual salary records meets the analytical need while limiting disclosure.
Mistake to avoid: Sending a complete confidential dataset when a smaller authorized summary would suffice.
Reference: FRS 100 Application of Financial Reporting Requirements
49. Manage conflicts of interest explicitly
A conflict arises when competing interests can affect professional judgment or responsibilities. Identify the relationship and assess appropriate responses under applicable policies and standards. Disclosure can inform others, but some conflicts also require separate decision-makers, restrictions or withdrawal from the affected decision.
Worked example: An accountant's sibling owns a bidding supplier. Declaring the relationship and leaving the selection to an independent authorized team addresses more than merely mentioning the connection.
Mistake to avoid: Assuming disclosure alone resolves every conflict.
Reference: FRS 100 Application of Financial Reporting Requirements
50. Distinguish independence of mind and appearance
In assurance work, independence concerns both unbiased judgment and circumstances that a reasonable informed observer could view as compromising it. Personal confidence in one's fairness does not settle the assessment. Relevant professional requirements determine which relationships are prohibited or require other action.
Worked example: An assurance team member holds a direct investment in the client. Saying that the holding will not influence judgment does not remove the need to assess applicable independence requirements.
Mistake to avoid: Reducing independence to a private statement of good intentions.
Reference: FRS 100 Application of Financial Reporting Requirements
51. Separate authorization, custody and recording
Segregation of duties reduces the opportunity for one person to initiate, conceal and benefit from an improper transaction. Separate authorization, custody and recording where practical. In a small organization, independent review can compensate for some limitations but must be timely and meaningful.
Worked example: One employee prepares supplier payments; another approves them; an independent reviewer examines the bank reconciliation. This arrangement reduces the ability to conceal an unauthorized payment.
Mistake to avoid: Assigning a reviewer who merely signs documents without examining supporting evidence.
Reference: FRS 100 Application of Financial Reporting Requirements
52. Combine restricted access with traceable changes
Information controls should limit access to authorized needs and preserve evidence of important changes. Least-privilege access reduces exposure, while logs support investigation and accountability. Backups address recovery rather than authorization; these controls solve different problems and should not be treated as substitutes.
Worked example: A clerk may enter invoices but cannot alter supplier bank details. Logged changes to bank details receive independent review, creating both a restriction and an investigative record.
Mistake to avoid: Assuming a backup prevents unauthorized changes to live accounting records.
Reference: FRS 100 Application of Financial Reporting Requirements
Business strategy and financial management
53. Connect strategic objectives with operating measures
A useful performance measure follows a stated objective and a plausible relationship between actions and outcomes. Combine financial results with relevant operational indicators. A measure can encourage harmful behavior when it rewards volume while ignoring quality, costs or the customer outcome the strategy depends on.
Worked example: A repair business prioritizes reliable service. Tracking repeat repairs alongside jobs completed exposes a quality problem that a volume-only target could conceal.
Mistake to avoid: Calling an easily measured activity a strategic success measure without testing the connection.
Reference: FRS 100 Application of Financial Reporting Requirements
54. Interpret liquidity ratios with asset quality
The current ratio divides current assets by current liabilities. It summarizes balance-sheet coverage, not the timing or certainty of cash availability. Examine receivable collectibility, inventory usability and payment dates before concluding that a seemingly strong ratio means obligations can be met promptly.
Worked example: Current assets of $90,000 and liabilities of $45,000 give a ratio of 2.0. If $40,000 of inventory is obsolete, the ratio alone overstates practical liquidity.
Mistake to avoid: Treating every dollar of current assets as immediately spendable cash.
Reference: FRS 100 Application of Financial Reporting Requirements
55. Calculate the cash conversion cycle consistently
The cash conversion cycle adds inventory days and receivables days, then subtracts payables days. It approximates the interval financed through operating working capital. Use consistent periods, suitable averages and appropriate denominators. A shorter cycle can release cash but may also reflect unsustainable operating choices.
Worked example: Inventory days are 40, receivables days 30 and payables days 25. The cycle is 45 days; reducing receivables days to 24 reduces it to 39 days.
Mistake to avoid: Adding payables days when longer supplier credit normally shortens the financing interval.
Reference: FRS 100 Application of Financial Reporting Requirements
56. Discount cash flows to a common date
Money available at different dates is not directly comparable when a required return applies. Discount a future amount by the accumulation factor for its timing. Match the rate's period with the number of periods, and distinguish a promised future receipt from its present value.
Worked example: At an annual 10% discount rate, $1,210 received in two years has present value $1,000 because $1,210 divided by 1.10 squared equals $1,000.
Mistake to avoid: Subtracting 20% from the future receipt instead of applying compound discounting.
Reference: FRS 100 Application of Financial Reporting Requirements
57. Evaluate investment using incremental net present value
Net present value discounts incremental project cash flows and includes investment outflows at their actual dates. Exclude sunk expenditure and include relevant opportunity costs and working capital. A positive result indicates value creation under the assumptions, rather than certainty that forecasts will be achieved.
Worked example: Pay $10,000 now and receive $6,000 at each of the next two year-ends. At 10%, NPV is $413.22, so the project is favorable under these assumptions.
Mistake to avoid: Discounting accounting profit instead of the project's relevant cash flows.
Reference: FRS 100 Application of Financial Reporting Requirements
58. Recognize limits of internal rate of return
IRR is a discount rate that makes a project's NPV zero. It expresses a rate rather than total value created. Different project scales or timing can produce ranking conflicts, while unconventional cash-flow patterns can produce multiple IRRs. Evaluate mutually exclusive projects at the relevant required return.
Worked example: Paying $100 now for $120 in one year gives 20% IRR. Paying $1,000 for $1,150 gives 15%. At 10%, their NPVs are $9.09 and $45.45 respectively.
Mistake to avoid: Selecting the higher IRR automatically when choosing between mutually exclusive investments.
Reference: FRS 100 Application of Financial Reporting Requirements
59. Assess leverage through coverage and downside
Debt introduces fixed financing obligations that can amplify changes in earnings available to owners. Interest coverage provides one diagnostic, but does not establish cash availability or repayment capacity. Examine operating volatility, principal repayment dates and adverse scenarios alongside the chosen coverage measure.
Worked example: Operating profit of $30,000 and interest expense of $6,000 give five times coverage. If operating profit falls to $9,000, coverage falls to 1.5 times.
Mistake to avoid: Inferring low financing risk from one strong year's coverage while ignoring future principal payments.
Reference: FRS 100 Application of Financial Reporting Requirements
60. Distinguish sensitivity analysis from scenarios
Sensitivity analysis changes one assumption while holding others constant. Scenario analysis changes a coherent combination of assumptions. Both reveal how dependent a decision is on forecasts, but neither assigns probabilities automatically. Avoid combinations that are internally inconsistent with the business model.
Worked example: Reducing only sales volume tests volume sensitivity. Reducing volume and price while increasing collection delays creates a downturn scenario that tests several connected pressures.
Mistake to avoid: Treating the worst calculated scenario as a statistically established prediction.
Reference: FRS 100 Application of Financial Reporting Requirements
Sources
Reference context:
All study guides