Use this guide alongside the IPSASB Certification Examination Free Practice Test to develop your understanding of public sector financial reporting. Start with the foundations, then work through statement presentation, revenue, assets, financial instruments and consolidation. Each example illustrates a durable accounting principle under stated assumptions. The references establish the IPSASB reporting context; consult the applicable standards for detailed requirements.
Public sector reporting foundations
1. Accountability and decision usefulness
Public sector financial reporting helps users assess how an entity manages resources and supports decisions about future resource allocation. Financial results need interpretation alongside public service responsibilities. A surplus alone does not establish effective service delivery, and a deficit alone does not establish poor management.
Worked example: A library reports a surplus of 40,000 while reducing opening hours. The surplus indicates a financial result; assessing accountability also requires understanding the reduction in services.
Mistake to avoid: Treating the largest surplus as automatic evidence of the best public service performance.
Source: About IPSASB | IPSASB
2. Accrual accounting versus cash accounting
Accrual accounting records economic effects when they occur, rather than only when cash moves. Identify when goods or services were received, when revenue arose and whether an obligation remains outstanding. Cash records remain important, but payment timing does not determine every expense or revenue period.
Worked example: A department receives December cleaning services costing 6,000 and pays in January. December records a 6,000 expense and payable; January payment settles the payable.
Mistake to avoid: Recording January expense solely because the supplier receives payment in January.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
3. Assets can provide service potential
A public sector resource can be useful because it delivers services, even if it generates no cash inflows. Asset analysis considers the resource, the entity's control and the resulting service potential or economic benefits. Lack of a selling price or admission charge does not automatically prevent asset recognition.
Worked example: A municipality controls a footbridge used without charge. Its ability to provide safe passage represents service potential, so zero toll revenue does not by itself exclude it from asset analysis.
Mistake to avoid: Recognizing only resources expected to produce commercial cash receipts.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
4. Present obligations versus future intentions
A liability concerns a present obligation arising from past events, rather than every planned future expenditure. Examine whether the entity already has an obligation to transfer resources and whether it can realistically avoid that transfer. An approved plan or budget is not automatically a recognized liability.
Worked example: An agency budgets 90,000 for equipment but has not ordered it or incurred another obligation. The budget alone creates no equipment payable; delivered equipment awaiting payment does.
Mistake to avoid: Recognizing all approved future spending as liabilities at the reporting date.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
5. The accounting equation
Assets equal liabilities plus net assets or equity. Net assets represent the residual after liabilities are deducted from assets, rather than a separate cash reserve. Use this relationship to check transaction effects and detect inconsistencies between balances. A balanced equation is necessary, but it does not prove correct classification.
Worked example: Assets of 720,000 less liabilities of 280,000 give net assets of 440,000. Borrowing another 50,000 increases cash and liabilities equally, leaving net assets unchanged.
Mistake to avoid: Treating a borrowing receipt as an increase in surplus or net assets.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
6. Revenue versus owner contributions
An inflow's accounting depends on its substance, including whether it represents revenue or a contribution from an owner acting in that capacity. Government involvement alone does not establish ownership treatment. Examine the transaction's documented rights and purpose before deciding whether the inflow belongs in financial performance or directly in net assets.
Worked example: Under the stated classification, a 200,000 owner capital contribution increases cash and contributed capital. A separate 15,000 service fee increases revenue when the service is earned.
Mistake to avoid: Classifying every transfer from a government as an owner contribution.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
7. Recognition versus disclosure
Recognition places an item and its measured amount in the financial statements. Disclosure explains relevant information, often in notes, and can address items not recognized. First evaluate the applicable recognition requirements, then determine the information users need. Mentioning an obligation in a note does not correct an omitted recognized liability.
Worked example: A confirmed supplier payable of 8,400 belongs in liabilities. Describing the unpaid invoice in a commitments note without recording it leaves liabilities understated by 8,400.
Mistake to avoid: Using a note as a substitute for recognition when recognition requirements are met.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
8. Measurement bases answer different questions
Historical cost and current measurement bases describe different aspects of a resource or obligation. Historical cost starts from transaction amounts; current measurements use conditions relevant to the measurement date. Identify the required basis before calculating a value. An available market estimate does not automatically replace a historical-cost carrying amount.
Worked example: Equipment cost 100,000 and has accumulated depreciation of 25,000. Under the stated cost basis, its carrying amount is 75,000, even if a dealer estimates resale proceeds of 82,000.
Mistake to avoid: Switching measurement bases simply because another value is easier to obtain.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
9. Faithful representation and useful estimates
Useful information should represent the economic phenomenon faithfully, with appropriate explanations of uncertainty. Estimates are not inherently unreliable: many accounting amounts cannot be observed directly. Use supportable assumptions, apply a suitable method and explain significant uncertainty. False precision can obscure the limits of an estimate rather than improve it.
Worked example: A receivable estimate uses documented collection experience and current debtor information. Explaining those assumptions makes the estimate more useful than presenting an unexplained exact-looking recovery amount.
Mistake to avoid: Assuming an estimated amount must be excluded merely because its outcome is uncertain.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
10. Materiality includes nature and context
Information can be material because of its size, nature or circumstances. Consider whether omitting, misstating or obscuring it could affect accountability assessments or decisions. Public sector users may care about sensitive transactions even when amounts are relatively small. There is no universal percentage that resolves every materiality judgment.
Worked example: A small payment to an entity connected with a senior decision maker may need attention because of its nature, despite being minor compared with the agency's total expenditure.
Mistake to avoid: Dismissing a sensitive transaction solely because it falls below a numerical screening amount.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
Financial statements and presentation
11. Statements explain different dimensions
Financial statements connect resources and obligations, financial performance, movements in net assets and cash flows. Each answers a different question. Read them together rather than treating any one statement as a complete assessment. Notes explain policies, uncertainties and details that condensed statement totals cannot communicate.
Worked example: An agency buys equipment for 30,000 cash. Its asset composition and cash flows change immediately, while financial performance generally reflects consumption through depreciation rather than the entire purchase payment.
Mistake to avoid: Expecting every cash payment to appear as an equal expense in financial performance.
Source: IPSASB | IPSASB
12. Financial position is a dated snapshot
A statement of financial position reports recognized assets, liabilities and net assets at a particular date. Balances must reflect rights, obligations and transactions existing at that date. Distinguish closing balances from activity during the year, and ensure the reporting boundary matches the entity described in the statements.
Worked example: A year-end payable is 12,000 after invoices of 70,000 and payments of 58,000, assuming no opening balance. Report 12,000 as the closing liability, not total annual purchases.
Mistake to avoid: Presenting the year's transaction total as though it were the closing balance.
Source: IPSASB | IPSASB
13. Surplus measures recognized performance
Surplus or deficit reflects recognized revenue less recognized expenses for a period. It differs from the cash movement because of accruals, prepayments, depreciation and financing transactions. Interpret it using the accounting policies and public service context. A surplus is not necessarily cash available for immediate spending.
Worked example: Revenue of 140,000 and expenses of 128,000 produce a surplus of 12,000. If 20,000 of that revenue remains receivable, the surplus cannot be equated with cash received.
Mistake to avoid: Calling the reported surplus the entity's available bank balance.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
14. Reconciling movements in net assets
Closing net assets reflect opening net assets plus the period's recognized movements. Separate surplus or deficit from owner transactions and other movements recorded directly in net assets under the applicable framework. This reconciliation explains why the change in net assets may differ from the reported financial result.
Worked example: Opening net assets are 300,000. A surplus of 24,000 and an owner contribution of 50,000 produce closing net assets of 374,000, assuming no other movements.
Mistake to avoid: Forcing every increase in net assets into revenue to make the reconciliation balance.
Source: IPSASB | IPSASB
15. Cash flows follow transaction substance
Operating, investing and financing categories distinguish different sources and uses of cash. Routine service activity differs from acquiring long-term assets or obtaining finance. Classify the cash transaction itself, and apply the relevant requirements consistently. Non-cash transactions cannot become cash flows merely because they affect assets or liabilities.
Worked example: A department pays 9,000 for routine supplies, 40,000 for equipment and receives 60,000 from borrowing. These illustrate operating outflow, investing outflow and financing inflow respectively.
Mistake to avoid: Including equipment obtained entirely on credit as a cash investing outflow.
Source: IPSASB | IPSASB
16. Reconciling surplus to operating cash
An indirect cash-flow reconciliation adjusts the starting financial result for non-cash items and relevant operating balance movements. Increasing receivables generally reduces cash relative to revenue; increasing operating payables generally increases cash relative to expenses. Separately address items whose cash effects belong in other categories.
Worked example: A simplified surplus of 25,000, depreciation of 7,000, receivables increase of 4,000 and operating payables increase of 3,000 give operating cash of 31,000.
Mistake to avoid: Adding an increase in receivables because it increases reported assets.
Source: IPSASB | IPSASB
17. Current and non-current classification
Classification distinguishes resources expected to be realized or consumed, and obligations expected to be settled, within the relevant operating cycle or other applicable classification period. Consider contractual terms and the entity's rights at the reporting date. The name of an account alone does not establish whether its balance is current.
Worked example: A loan described as long-term has a 14,000 installment due within the applicable current classification period. Separate that installment from the remaining balance when the presentation requirements call for it.
Mistake to avoid: Classifying an entire loan as non-current because its original term was several years.
Source: IPSASB | IPSASB
18. Gross presentation versus offsetting
Showing amounts separately preserves information about resources, obligations and activity. Offsetting is appropriate only when the applicable requirements permit or require it. Having the same counterparty is not sufficient by itself. Distinguish presenting related information together from reducing two recognized balances to one net figure.
Worked example: An agency has a 16,000 receivable and a separate 11,000 payable with one supplier. Without an applicable basis for offsetting, present both rather than only a 5,000 receivable.
Mistake to avoid: Netting every receivable and payable involving the same organization.
Source: IPSASB | IPSASB
19. Policies, estimates and errors differ
An accounting policy determines a recognition, measurement or presentation approach; an estimate uses judgment within that approach; an error results from a mistake or misuse of available information. Classify the change before selecting its accounting treatment. New evidence about an asset's life differs from correcting an incorrect original calculation.
Worked example: New inspection evidence shortens equipment's remaining useful life. That is an estimate change; discovering that last year's depreciation formula omitted a component is an error requiring separate analysis.
Mistake to avoid: Calling every correction an estimate change to avoid evaluating prior-period consequences.
Source: IPSASB | IPSASB
20. Budget and actual amounts need a common basis
A meaningful budget comparison aligns accounting basis, reporting period, classification and entity coverage. Differences can arise even when both sets of figures are correct. Reconcile those differences before interpreting a variance. Budget authority and recognized accrual expenses answer related but distinct questions.
Worked example: A cash-based equipment budget records a 48,000 purchase, while accrual expenses include 6,000 depreciation. The 42,000 difference reflects different bases and is not automatically an underspending variance.
Mistake to avoid: Comparing cash expenditure directly with accrual expense without identifying basis differences.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
Revenue, transfers and receivables
21. Exchange and non-exchange economics
An exchange involves receiving and giving approximately equal value directly between the parties. Taxes and many transfers have different economics because the payer does not receive equivalent value directly in return. This distinction helps analyze substance, but detailed revenue recognition must follow the applicable standard and the arrangement's terms.
Worked example: A resident pays 35 for a pool session, receiving a direct service. A general tax payment finances wider services without an equivalent direct exchange with that taxpayer.
Mistake to avoid: Assuming any transaction involving government is necessarily non-exchange.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
22. Service revenue and reporting cut-off
For a straightforward service arrangement, analyze how much service has actually been provided by the reporting date. An invoice date or collection date may differ from service delivery. Recognize revenue using the applicable requirements and a measure that faithfully represents performance rather than automatically using total contract cash.
Worked example: A training center delivers four of six equal sessions before year-end under a 12,000 agreement. Assuming revenue follows delivered sessions, recognized revenue is 8,000.
Mistake to avoid: Recognizing all contract revenue because the agreement was signed before year-end.
Source: IPSASB | IPSASB
23. Advance receipts can represent obligations
Receiving cash before providing an agreed service does not automatically create revenue. Determine whether the entity owes services, a refund or another transfer of resources. Under the stated recognition assumptions, an advance remains a liability until the relevant obligation is satisfied or otherwise appropriately resolved.
Worked example: A museum receives 3,600 for six equal workshops and delivers two. Assuming revenue follows delivery, recognize 1,200 revenue and retain 2,400 as an obligation for the remaining workshops.
Mistake to avoid: Using receipt of cash as the sole test for revenue recognition.
Source: IPSASB | IPSASB
24. Grant terms drive the accounting analysis
A grant's title does not determine when revenue arises. Read the arrangement to identify resources controlled, enforceable obligations, required activities and consequences of non-performance. The applicable revenue requirements determine the resulting treatment. Separate the receipt of funding from the assessment of obligations that funding may create.
Worked example: An agency receives 80,000 under an agreement requiring repayment for undelivered specified services. Its analysis must address that enforceable obligation; calling the payment a grant does not resolve recognition.
Mistake to avoid: Recognizing every grant immediately without examining the agreement's substantive terms.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
25. Purpose restrictions versus present obligations
A direction about how resources should be used differs from a present obligation that meets liability recognition requirements. Examine enforceability, required performance and the consequences of failing to comply. Restricted cash does not automatically equal deferred revenue, and unrestricted cash does not prove that no obligation exists.
Worked example: Funding described as supporting literacy needs further analysis. If no present obligation exists under the applicable requirements, that purpose label alone does not justify recording a liability.
Mistake to avoid: Creating deferred revenue solely because funding is designated for a particular purpose.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
26. Tax entitlement and collection are separate
Tax accounting requires identifying the relevant taxable event and entitlement under the applicable framework before evaluating recognition and measurement. Collection timing is a separate question. Once a valid receivable is recognized, uncertain recovery requires its own assessment rather than assuming the entire assessed amount will become cash.
Worked example: Assume recognized tax receivables total 200,000 and an appropriate recovery assessment supports an allowance of 12,000. Net receivables are 188,000; cash collection remains a later event.
Mistake to avoid: Treating every assessed amount as fully collectible without evaluating recoverability.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
27. Disputed assessments require separate analysis
An announced charge, fine or assessment is not necessarily an established receivable. Distinguish whether an entitlement exists from whether an existing entitlement is collectible. A dispute over the underlying entitlement can affect recognition or measurement differently from a debtor's inability to pay an otherwise valid amount.
Worked example: A 5,000 assessment remains subject to a dispute that determines whether anything is owed. The immediate question is the existence of an entitlement, rather than merely estimating default on 5,000.
Mistake to avoid: Treating every unresolved entitlement dispute as an ordinary collection problem.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
28. Resources received without cash payment
Donated resources can affect financial reporting despite involving no cash receipt. Identify what the entity controls and apply the relevant recognition and measurement requirements. Goods, facilities and volunteer services need separate analysis; the accounting for one category cannot automatically be applied to every kind of contribution.
Worked example: A health agency receives donated diagnostic equipment. Assess the controlled equipment under applicable asset and revenue requirements; the absence of payment does not by itself justify omitting the resource.
Mistake to avoid: Assuming all donations are unrecorded because they produce no bank transaction.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
29. Principal versus collection agent
An entity collecting money for another party must distinguish its own revenue from amounts held on that party's behalf. Analyze control, responsibilities and the arrangement's substance. Gross receipts can overstate activity when the collector is an agent. Any fee earned for collection is analyzed separately.
Worked example: An office collects 50,000 for another entity and earns a separate 2,000 collection fee. Under the stated agency arrangement, the 50,000 is payable to the principal and only 2,000 is fee revenue.
Mistake to avoid: Reporting all money passing through the bank account as the collector's revenue.
Source: IPSASB | IPSASB
30. Billing errors versus credit losses
A correction to an invalid or overstated charge differs from a loss on a valid receivable. Establish what the debtor genuinely owes before estimating collection. Otherwise, revenue corrections and credit losses become confused, obscuring both service income and debtor performance.
Worked example: A valid 9,000 bill was entered as 10,000. Correct the 1,000 overstatement first. If expected recovery of the valid amount is 8,700, the separate collection shortfall is 300.
Mistake to avoid: Using a credit-loss allowance to hide a billing error that should be corrected.
Source: IPSASB | IPSASB
Physical and intangible assets
31. Asset cost versus operating expenditure
For a straightforward purchased asset, distinguish costs needed to bring it to the location and condition required for intended use from costs of operating it afterward. Apply the relevant capitalization requirements rather than adding every related invoice. Routine training or subsequent operating losses do not become asset cost merely through association.
Worked example: Equipment costs 42,000, delivery 2,000 and necessary installation 3,000. Under the stated cost assumptions, capitalize 47,000; separately expense 1,500 of routine staff training.
Mistake to avoid: Capitalizing every cost incurred near the equipment's purchase date.
Source: IPSASB | IPSASB
32. Repairs versus qualifying improvements
Routine maintenance preserves an asset's existing operating condition, whereas a qualifying improvement or replacement may create additional service potential. Analyze what the expenditure achieves and apply recognition requirements. Large cost alone does not establish capitalization, and small cost alone does not establish expense treatment.
Worked example: A 4,000 routine service maintains a vehicle's existing condition and is expensed under the stated assumptions. A separately assessed qualifying replacement component is capitalized, with the replaced component considered for removal.
Mistake to avoid: Classifying expenditure solely by invoice size rather than its economic effect.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
33. Depreciating significant components
Significant parts of an asset can have different useful lives and consumption patterns. Component depreciation reflects those differences more faithfully than applying one life to the entire asset. Identify material components and avoid continuing to recognize the carrying amount of a component after it has been replaced.
Worked example: A building shell costs 600,000 with a 30-year life; its lift costs 90,000 with a 10-year life. With zero residual values, annual straight-line depreciation totals 29,000.
Mistake to avoid: Depreciating the lift over the shell's life despite its shorter expected service period.
Source: IPSASB | IPSASB
34. Availability for use determines depreciation timing
Depreciation reflects consumption of an asset's depreciable amount over its useful life. For a straightforward depreciable asset, assess when it reaches the location and condition necessary for intended operation. Purchasing, paying for and first using the asset can occur on different dates; those dates are not interchangeable.
Worked example: A 24,000 machine with a four-year life and no residual value is ready for use for the final three months of the year. Straight-line depreciation is 1,500.
Mistake to avoid: Delaying depreciation solely because management has not yet scheduled the first job.
Source: IPSASB | IPSASB
35. Revising useful life and residual value
Useful life and residual value are estimates based on expected use and recovery. New evidence can change future depreciation without proving the previous estimate was an error. For a straightforward prospective revision, allocate the remaining depreciable amount over the revised remaining life using the appropriate consumption pattern.
Worked example: An asset's carrying amount is 36,000, revised residual value is 6,000 and revised remaining life is five years. Future annual straight-line depreciation is 6,000.
Mistake to avoid: Recalculating depreciation from original cost while ignoring the current carrying amount.
Source: IPSASB | IPSASB
36. Identifiable intangibles versus general capability
An intangible asset requires more than an expectation of future benefit. Assess identifiability, control and the relevant recognition requirements. A resource may be identifiable through separability or contractual or other rights. General staff expertise, reputation or institutional capability does not automatically form a separately recognized intangible asset.
Worked example: A purchased software license provides identifiable rights requiring asset analysis. Employees' improved familiarity with the software is general capability and does not automatically create a second intangible asset.
Mistake to avoid: Capitalizing every organizational strength because it may improve future performance.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
37. Research differs from qualifying development
Exploration of possible solutions differs from development of an identified resource that meets the applicable capitalization requirements. Project approval or management optimism is insufficient by itself. Examine the evidence supporting feasibility, completion, use and reliable cost measurement before treating development expenditure as an asset.
Worked example: A team spends 18,000 investigating several possible software designs. Those exploratory costs do not become a development asset merely because a later, separately assessed project succeeds.
Mistake to avoid: Retrospectively capitalizing exploratory costs solely because the eventual project becomes useful.
Source: IPSASB | IPSASB
38. Amortizing finite-life intangible assets
For a recognized finite-life intangible asset, amortization allocates the depreciable amount over the useful life according to the expected consumption pattern. Assess availability for use and any limits imposed by the rights obtained. A physical absence does not prevent an asset from being consumed through time or use.
Worked example: A software right costs 27,000, is available throughout the year and has a three-year useful life with zero residual value. Under straight-line amortization, annual expense is 9,000.
Mistake to avoid: Leaving a finite-life intangible unchanged because it does not physically wear out.
Source: IPSASB | IPSASB
39. Impairment depends on the asset's purpose
Impairment addresses a loss in recoverable benefits or service potential beyond ordinary depreciation. Public sector analysis distinguishes cash-generating assets from assets held primarily to deliver services. Do not apply a commercial cash-flow test indiscriminately to free public services. Identify the relevant impairment framework before choosing the measurement method.
Worked example: Flood damage closes half a free community center. The assessment concerns the reduction in its service potential; zero admission revenue alone is not evidence that its carrying amount must be zero.
Mistake to avoid: Using lack of profit as the sole impairment indicator for a service-delivery asset.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
40. Disposal gains use carrying amount
On a straightforward asset disposal, compare net disposal proceeds with carrying amount to determine the gain or loss. Remove both the asset's recorded cost and related accumulated depreciation. Original purchase price is not the correct comparison once depreciation or other carrying-amount adjustments have occurred.
Worked example: Equipment cost 50,000 and accumulated depreciation is 38,000. Selling it for net proceeds of 15,000 produces a gain of 3,000 because carrying amount is 12,000.
Mistake to avoid: Reporting a 35,000 loss by comparing proceeds directly with original cost.
Source: IPSASB | IPSASB
Financial instruments and financial risk
41. Contractual financial assets and liabilities
Financial instrument analysis begins with contractual rights and obligations. A contractual right to receive cash differs from a right to receive goods or services. A contractual payment obligation differs from an obligation arising solely through other mechanisms. Do not classify every receivable or obligation without examining its source.
Worked example: A loan receivable gives a contractual right to cash and requires financial instrument analysis. A supplier prepayment for future stationery instead represents a right to receive goods.
Mistake to avoid: Calling every asset with a monetary carrying amount a financial asset.
Source: IPSASB | IPSASB
42. Debt and equity follow contractual substance
For an issuer, a contractual obligation to deliver cash generally points toward a financial liability, subject to the applicable classification requirements and exceptions. An instrument's name does not settle its classification. Review repayment terms, payment discretion and any separate components before accepting an equity description.
Worked example: An instrument called permanent capital nevertheless requires repayment of 100,000 on a fixed date. That mandatory cash obligation requires liability analysis despite the capital label.
Mistake to avoid: Accepting management's chosen instrument name instead of examining contractual obligations.
Source: IPSASB | IPSASB
43. Present value of a future payment
Present value translates a future cash amount into an amount at the measurement date using an appropriate discount rate. Match the rate period with the cash-flow timing. Coupon amounts and market discount rates serve different purposes. The calculation illustrates valuation mechanics, rather than determining which accounting measurement basis applies.
Worked example: A single 11,025 receipt due in two years has a present value of 10,000 at an annual 5% rate: 11,025 divided by 1.05 squared.
Mistake to avoid: Discounting two years of cash flows using only one year's discount factor.
Source: IPSASB | IPSASB
44. Effective interest and carrying amount
Under a straightforward effective-interest calculation, interest is the opening carrying amount multiplied by the effective rate. Compare that interest with cash received or paid to explain the carrying-amount movement. A discount can increase carrying amount over time even though the contractual coupon remains unchanged.
Worked example: A debt asset opens at 9,500 with a 6% effective rate and pays a 400 coupon. Interest is 570, so its closing carrying amount becomes 9,670 before other adjustments.
Mistake to avoid: Using the coupon as interest revenue while ignoring the discount's allocation.
Source: IPSASB | IPSASB
45. Interest rates and fixed-payment values
For fixed future payments, a higher discount rate reduces present value, while a lower rate increases it. This economic relationship explains interest-rate exposure, but the resulting accounting effect depends on the required measurement category. A market-value change does not automatically require the same adjustment for every instrument.
Worked example: A 1,100 payment in one year is worth 1,000 at 10%, but approximately 1,047.62 at 5%. The lower discount rate increases its present value.
Mistake to avoid: Assuming an increase in market interest rates increases the value of existing fixed payments.
Source: IPSASB | IPSASB
46. Probability-weighted collection shortfalls
Credit-risk analysis considers both the likelihood and size of collection shortfalls. A probability-weighted illustration helps explain the economics, but a required impairment calculation may also involve discounting, applicable horizons and forward-looking information. Expected loss is not identical to the most likely outcome or the worst possible outcome.
Worked example: For a simplified 10,000 exposure, assume 90% probability of full recovery and 10% probability of recovering only 4,000. The undiscounted probability-weighted shortfall is 600.
Mistake to avoid: Presenting this simplified multiplication as a complete standard-compliant impairment model.
Source: IPSASB | IPSASB
47. Credit, liquidity and market risks
Credit risk concerns counterparty non-performance; liquidity risk concerns difficulty meeting obligations; market risk concerns movements in prices or rates. The risks can interact but require different analysis. A valuable long-term asset does not necessarily provide the cash needed for a payment due tomorrow.
Worked example: An agency holds a collectible five-year loan but must repay borrowing next week. The immediate problem is liquidity, even if the loan's credit quality remains strong.
Mistake to avoid: Assuming sufficient total assets eliminate the risk of missing near-term payments.
Source: IPSASB | IPSASB
48. Fair value and observable market evidence
A market-based valuation uses evidence appropriate to the instrument and measurement date. Quoted prices for identical instruments differ in evidential strength from estimates based on similar instruments or models. Understand adjustments and assumptions before accepting an output. Management's intended holding period does not itself establish market value.
Worked example: Assume the applicable measurement requires an unadjusted active-market quote of 96 per unit. Holding 500 identical units gives a value of 48,000, subject to the stated measurement assumptions.
Mistake to avoid: Replacing relevant market evidence with the entity's desired future selling price.
Source: IPSASB | IPSASB
49. Forward contract payoff direction
A forward contract fixes a price for a future purchase or sale. Identify whether the entity must buy or sell before calculating its settlement payoff. A maturity payoff differs from a contract's value before maturity, when discounting and other valuation factors may matter. Economic hedging does not automatically establish hedge accounting.
Worked example: An agency agrees to buy 1,000 units at 20 each. At settlement, the market price is 23, giving a favorable economic difference of 3,000 before costs.
Mistake to avoid: Reversing the payoff sign by treating a purchase contract as a sale contract.
Source: IPSASB | IPSASB
50. Risk disclosures explain exposure
A carrying amount alone cannot explain an instrument's repayment timing, concentration or sensitivity to adverse conditions. Relevant disclosures connect amounts with contractual terms, risk management and significant assumptions. Distinguish gross exposure from the effect of collateral or other protection; protection may have limits or separate enforceability considerations.
Worked example: Two agencies each report borrowings of 500,000. One owes the amount next month and the other over several years, so the identical totals conceal very different liquidity exposures.
Mistake to avoid: Assuming equal carrying amounts imply equal financial risk.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
Controlled entities and public sector combinations
51. Control establishes the reporting boundary
Control analysis considers power over another entity, exposure or rights to variable benefits and the ability to use power to affect those benefits. Public sector benefits can include non-financial outcomes. Ownership percentage alone is insufficient, and funding alone does not automatically establish control.
Worked example: Assume an agency can direct another entity's relevant activities and use that power to affect service benefits it receives. Those facts support control analysis even without ordinary share ownership.
Mistake to avoid: Limiting control assessment to whether the investor owns a majority of shares.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
52. Substantive rights versus protective rights
Rights that enable direction of relevant activities differ from rights designed only to protect an interest. Assess whether decision rights are substantive and can be exercised when decisions matter. A veto over exceptional actions does not necessarily provide ongoing power over the activities that determine benefits.
Worked example: A funder may block disposal of donated property but cannot direct programs, staffing or budgets. That protective restriction alone does not establish that the funder controls the recipient.
Mistake to avoid: Treating every veto or safeguard as power over the recipient's relevant activities.
Source: IPSASB | IPSASB
53. Consolidation differs from aggregation
Consolidated statements present a controlling entity and its controlled entities as one economic entity. Adding balances is only an initial step: internal relationships and transactions must be eliminated. Aggregation without establishing the correct boundary can include unrelated entities or preserve amounts that do not represent dealings with outsiders.
Worked example: Two agencies receive funding from the same treasury. Shared funding does not by itself justify combining their statements; first identify the reporting entity and establish the relevant control relationships.
Mistake to avoid: Assuming common funding is sufficient to define a consolidated group.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
54. Align information before consolidation
Combining statements requires comparable information about similar transactions and relevant reporting periods. Identify policy differences, reporting-date differences and significant intervening events before making consolidation adjustments. Apparent inconsistencies can arise from different accounting methods rather than genuine differences in the entities' economic activity.
Worked example: A controlled entity expenses a qualifying asset purchase while the group's policy capitalizes it. Adjust the submitted figures to the appropriate group policy before adding and eliminating balances.
Mistake to avoid: Adding statements mechanically while leaving material accounting-policy differences unresolved.
Source: IPSASB | IPSASB
55. Eliminating reciprocal balances
A group cannot owe a receivable to itself. Eliminate matching internal receivables and payables after investigating differences. Timing issues, unrecorded transfers or errors may prevent immediate agreement. Elimination removes the internal relationship from group statements; it does not cancel the obligation in the entities' separate records.
Worked example: A department's 22,000 receivable matches its controlled entity's 22,000 payable. Eliminating both reduces consolidated assets and liabilities by 22,000, with no effect on net assets.
Mistake to avoid: Eliminating unequal internal balances without first finding the reason for the difference.
Source: IPSASB | IPSASB
56. Eliminating internal revenue and expense
Consolidated performance excludes revenue and corresponding expense arising solely from transactions within the group. Keep dealings with external parties intact. An internal recharge can be useful for separate-entity accountability, yet it does not represent revenue earned by the group from an outside customer.
Worked example: A central service unit charges a controlled agency 18,000 for support already consumed. Eliminate 18,000 internal revenue and 18,000 internal expense; the group surplus is unchanged.
Mistake to avoid: Eliminating the group's external support costs along with the internal recharge.
Source: IPSASB | IPSASB
57. Unrealized profit in internal inventory
Inventory remaining within a group should not include profit created solely by an internal sale. Determine the original group cost and the proportion still held before calculating the elimination. Markup on cost differs from profit margin on selling price, so identify which percentage the example provides.
Worked example: Goods costing 8,000 are sold internally for 10,000, and 40% remain unsold externally. Remove unrealized profit of 800, leaving that inventory at group cost of 3,200.
Mistake to avoid: Applying the markup percentage directly to internal selling price as though it were a margin.
Source: IPSASB | IPSASB
58. Internal asset transfers and excess depreciation
Selling a depreciable asset within a group does not create a disposal gain for the group. Restore the asset to the appropriate group carrying amount and adjust later depreciation for the internal price uplift. Consider the remaining useful life and transfer timing when calculating the additional adjustment.
Worked example: An asset carrying 30,000 is transferred internally for 42,000 with three years remaining. Eliminate the 12,000 gain and reverse 4,000 excess annual depreciation under straight-line assumptions.
Mistake to avoid: Eliminating the internal gain but leaving depreciation based on the inflated transfer price.
Source: IPSASB | IPSASB
59. Non-controlling interests remain within consolidation
Where ownership interests exist, a controlling entity generally consolidates the controlled entity's relevant balances in full rather than multiplying each balance by its ownership percentage. Separately identify interests attributable to other owners. Calculate allocations using adjusted results and the appropriate ownership period, rather than unadjusted annual totals.
Worked example: Assume a controlled entity's adjusted annual surplus is 40,000 and outside owners hold 25% throughout the year. Their share is 10,000; full consolidation still precedes that allocation.
Mistake to avoid: Consolidating only 75% of every asset and liability because the controlling owner holds 75%.
Source: IPSASB | IPSASB
60. Acquisitions versus amalgamations
Public sector combinations require assessing whether the transaction is an acquisition or an amalgamation under the applicable requirements. Control and economic substance matter; payment of consideration alone does not settle the classification. Establish the combination type before selecting its recognition and measurement approach rather than importing a commercial acquisition formula automatically.
Worked example: Assume analysis establishes that two service operations form an amalgamation. Select the applicable amalgamation approach; zero consideration alone is not a reason to apply an acquisition goodwill calculation.
Mistake to avoid: Treating every public sector restructuring as a purchase of a business.
Source: About IPSASB | IPSASB; IPSASB | IPSASB
Context sources
Source context checked:
All study guides