IPSAS 48
Active
Transfer Expenses
Establishes principles for transfer providers accounting for transfer expenses with and without binding arrangements, covering transfer right assets, transfer obligation liabilities, and variable consideration provisions. Effective 1 January 2026.
Active Standard
IPSAS 48 Transfer Expenses is the current, active standard issued by the IPSASB establishing financial reporting requirements for transfer providers providing goods, services, or other assets without receiving direct reciprocal consideration. Effective for periods beginning on or after 1 January 2026.
IPSAS 48 is the mirror-image companion standard to IPSAS 47 Revenue. Because IFRS does not contain an equivalent standard for the giving entity's perspective in non-exchange transfers and grants, the IPSASB developed IPSAS 48 independently, drawing concepts from Government Finance Statistics (GFS) and aligning its binding arrangement mechanisms symmetrically with IPSAS 47.
1
Objective, Scope & Partial-Scope Arrangements (paras. 1–5)
Objective – the mirror image of IPSAS 47
Establishes principles a TRANSFER PROVIDER applies to report useful information about the nature, amount, timing, and uncertainty of expenses and cash flows from transfer expense transactions – requiring the entity to determine the transaction TYPE, then apply the corresponding accounting.
Leases (IPSAS 43); contributions from/distributions to owners Service concession arrangements (IPSAS 32); employee benefits (IPSAS 39) Financial instruments, INCLUDING concessionary loans (IPSAS 41) Social benefits (IPSAS 42); insurance contracts; share-based payments; income taxes
Partial-scope binding arrangements (para. 5)
Where a binding arrangement is PARTLY within this Standard's scope and partly within another's: if the OTHER Standard specifies how to separate/measure its portion, apply THAT first, then apply IPSAS 48 to whatever remains. If the other Standard does NOT specify separation, apply IPSAS 48 to the ENTIRE arrangement instead.
2
Definitions (paras. 6–7)
The core vocabulary – inverted from IPSAS 47
Transfer expense
An expense from a transaction, other than taxes, where an entity provides a good, service, or other asset to another entity WITHOUT directly receiving anything in return.
Transfer provider / transfer recipient
The entity providing the good/service/asset / the entity receiving it, without a direct exchange either way.
Transfer consideration
The total amount of resources an entity expects to transfer.
The binding-arrangement pair – rights and obligations
Transfer right
An entity's enforceable right to have the transfer RECIPIENT satisfy its obligation as specified, or face the binding arrangement's consequences.
Transfer obligation
An entity's OWN obligation in a binding arrangement to transfer resources in a specified manner.
Stand-alone consideration
The amount an entity intends to compensate the transfer recipient for satisfying each of its obligations.
Binding arrangement, compliance obligation, taxes, and third-party beneficiary are IMPORTED directly from IPSAS 47 (para. 7) – this Standard doesn't redefine them.
3
Identifying the Transfer Expense Transaction (paras. 8–17)
The gateway: asset recognition drives the accounting
Accounting turns on whether the transfer RESULTS IN an asset. Where it does, that asset is derecognized as the entity's rights are extinguished. Where it doesn't, a transfer expense is recognized either when the entity LOSES CONTROL of the resources, or when it incurs an obligation and recognizes a liability for it (para. 8). Whether a BINDING ARRANGEMENT exists is itself an input into both tests.
The same enforceability test as IPSAS 47
WITHOUT a binding arrangement → apply paras. 18–20 (§4) WITH a binding arrangement → apply paras. 21–43 (§5–§11)
Enforceability requires legal or equivalent means to hold parties accountable – substance over form, written/oral/implied practice, all mirroring IPSAS 47's own binding-arrangement framework exactly (paras. 10–17).
4
Transfer Expenses Without Binding Arrangements (paras. 18–20)
Two paths – a provision, or simple derecognition
Constructive/legal obligation exists → recognize an IPSAS 19 PROVISION (which itself recognizes the expense); resources later transferred SETTLE it
No such obligation → recognize the expense when the entity CEASES TO CONTROL the resources – usually the transfer date
Measurement
Provision route → IPSAS 19 paras. 44–72 govern initial AND subsequent measurement Cease-to-control route → measure the expense at the transferred resources' CARRYING AMOUNT
5
With Binding Arrangements – Identifying Transfer Rights (para. 21)
The mirror image of IPSAS 47's compliance obligation
At inception, identify each DISTINCT transfer right = the entity's right to have the recipient satisfy a SEPARATE obligation – OR a series of rights with substantially the same characteristics/risks and the SAME satisfaction pattern
Where IPSAS 47 asks "what has the ENTITY promised to deliver?", IPSAS 48 asks "what has the RECIPIENT promised to satisfy, that the entity can enforce?" – the SAME binding arrangement, viewed from the opposite side.
6
Recognition – Transfer Right Assets & Transfer Obligation Liabilities (paras. 22–25)
Who performs FIRST determines the accounting
SequenceResult
ENTITY transfers resources FIRST, before the recipient performsDerecognize the transferred resources; recognize a TRANSFER RIGHT ASSET for the enforceable right to have the recipient later perform
RECIPIENT satisfies its obligations FIRST, before the entity transfersRecognize a TRANSFER OBLIGATION LIABILITY for the entity's own now-crystallized obligation to transfer resources
Expense recognition – two triggers (para. 24)
When (or as) a TRANSFER RIGHT ASSET is DERECOGNIZED – extinguished as the recipient satisfies the binding arrangement's terms When a TRANSFER OBLIGATION LIABILITY is RECOGNIZED
A transfer right is extinguished once the entity no longer has enforceable rights under the binding arrangement (para. 25) – mirroring precisely how IPSAS 47's compliance obligations are satisfied over time or at a point in time, but from the payer's perspective.
7
Derecognition Due to Non-Performance by the Transfer Recipient (paras. 26, 43)
Converting to a financial asset – where cash recovery is enforceable
If the recipient becomes UNABLE or UNWILLING to perform, AND the entity has an enforceable, UNCONDITIONAL right to cash/another financial asset instead → derecognize the transfer right asset, recognize a FINANCIAL ASSET, subsequently measured under IPSAS 41
Otherwise – an impairment question, not a derecognition one
Where the terms, legal system, or circumstances DON'T support that financial-asset conversion, the transfer right asset instead gets tested for IMPAIRMENT under IPSAS 21 (non-cash-generating) (para. 43) – since a transfer right asset, by its nature, doesn't generate cash returns the way IPSAS 26 assumes.
8
Modifications to a Binding Arrangement (paras. 27–29)
Separate arrangement – the two-condition test (para. 28)
Scope INCREASES – one or more ADDITIONAL transfer rights arise, from the recipient accepting new/increased obligations Transfer consideration INCREASES by an amount reflecting the VALUE of those additional rights, compensating the recipient for the added obligations
Mirrors IPSAS 47's own modification test (§7 of that Standard's poster) almost exactly, adapted for the payer's side.
Blended treatment – a cumulative catch-up
If NOT a separate arrangement, the entity RE-ESTIMATES total transfer consideration and its allocation between extinguished and unextinguished transfer rights as at the modification date. The DIFFERENCE between the newly-determined accumulated transfer expense and what was PREVIOUSLY recognized is recognized in surplus or deficit immediately, as at the modification date (para. 29).
9
Measurement – the Transfer Consideration (paras. 30–34)
Carrying amount, not fair value
Transfer consideration = total CARRYING AMOUNT of resources transferred (or obligated to transfer), including the effects of variable consideration
A deliberate contrast with IPSAS 47's fair-value-oriented transaction consideration – since the transfer provider is giving something it ALREADY holds at a known carrying amount, rather than receiving something new to be valued.
Initial measurement of each item
Transfer RIGHT ASSET (entity transfers first) → measured at the TOTAL carrying amount of resources ALREADY transferred (para. 31) Transfer EXPENSE on extinguishment → the transfer consideration amount ALLOCATED to that specific extinguished right (para. 32) Transfer OBLIGATION LIABILITY (recipient performs first) → the total carrying amount the entity is OBLIGATED to transfer (para. 33)
Assumes the recipient will perform under the EXISTING arrangement, with no cancellation/renewal/modification (para. 34) – the same "as-is" assumption IPSAS 47 makes for the transaction consideration.
10
Variable Consideration & Allocation to Transfer Rights (paras. 35–39)
Variable amounts – routed through IPSAS 19, not estimated directly here
Discounts, rebates, refunds, credits, price concessions, incentives, bonuses, penalties, or contingency on a future event – SAME variability sources as IPSAS 47 (para. 35). A genuinely different mechanic though: variable consideration in a transfer expense context typically creates a liability of UNCERTAIN TIMING/AMOUNT, meeting IPSAS 19's PROVISION definition (para. 36). Recognized/measured only when it's MORE LIKELY THAN NOT a present obligation exists, per IPSAS 19 paras. 44–72 (para. 37) – a HIGHER bar than IPSAS 47's own "highly probable no reversal" constraint.
Allocation – identified, or proportionate
Allocate to each distinct transfer right by its STAND-ALONE CONSIDERATION, adjusted for variable amounts
Variable consideration identifiable with SPECIFIC rights → allocate directly to those NOT identifiable with specific rights → allocate PROPORTIONATELY across all rights, by their share of the (non-variable) transfer consideration (para. 39)
11
Changes in the Transfer Consideration (paras. 40–42)
Two different causes, two different treatments
NOT from a modification (e.g. an uncertain event resolves) → allocate the change to transfer right assets/obligation liabilities on the SAME basis used at inception; amounts allocated to an ALREADY-EXTINGUISHED right go to surplus or deficit immediately, as an expense or a reduction of one (para. 41) FROM a modification → apply the §8 modification mechanics instead (para. 42)
12
Presentation & Disclosure Requirements (paras. 44–61)
Presentation, and the disclosure objective
Provisions from non-binding-arrangement obligations follow IPSAS 19's OWN presentation requirements (para. 44). Disclosure objective: enable users to understand nature, amount, timing, and uncertainty – covering (a) transfer expenses and related balances, (b) transfer arrangements, and (c) significant judgments on transfer right asset recognition (para. 50). IPSAS 1's materiality/aggregation guidance governs throughout (para. 51).
Key required items
Transfer expenses incorporated into the IPSAS 1 expense analysis, face or notes (para. 53) Qualitative/quantitative info on SIGNIFICANT transfers, with and without binding arrangements (para. 54) Where a transfer right asset converted to a FINANCIAL ASSET (§7) → IPSAS 30 financial asset disclosures apply (para. 55) Transfer OBLIGATION liabilities for cash → IPSAS 30 payables disclosures (amortized cost) (para. 56) Variable-consideration or non-binding-arrangement liabilities → IPSAS 19 provisions disclosures (paras. 57–58) PURPOSE, payment terms, resource nature, and risks/uncertainties for binding AND non-binding transfer arrangements – aggregable by similar nature (paras. 59–60)
13
Effective Date & Transition (paras. 62–64)
Twinned with IPSAS 47
Periods beginning on/after 1 January 2026 – earlier application requires SIMULTANEOUS adoption of IPSAS 47 (para. 62). One of the newest Standards in the entire Handbook, issued as IPSAS 47's direct companion.
Applied PROSPECTIVELY to transfers occurring on/after the date of initial application, OR Applied RETROSPECTIVELY under IPSAS 3 to each prior period presented
An entity CHOOSES between these two transition methods (para. 64) – a genuine option, unlike most Standards' single mandated transition path.
14
Relationship to GFS – No IAS/IFRS Equivalent
A genuinely public-sector-only Standard
IPSAS 48 has NO IFRS Standard equivalent – IAS 20 (government grants) addresses only the RECIPIENT's accounting, and IFRS has never developed a standard for the GIVING entity's side. This is a genuine gap the IPSASB filled independently, benchmarked instead against Government Finance Statistics (GFS) reporting guidelines.
TopicComparison
Definitional lineageIPSAS 48's "transfer expenses" definition is DRAWN from GFS's "transfers" concept, but reframed from the transfer PROVIDER's perspective
Classification driverIPSAS 48 is driven by BINDING ARRANGEMENT existence; GFS is driven primarily by whether the transfer is COMPULSORY or VOLUNTARY – the two frameworks CAN converge on the same outcome, but not always
Grant categorizationIPSAS 48 splits by binding-arrangement status (with/without, including capital transfers); GFS splits grants into CURRENT vs. CAPITAL, regardless of binding-arrangement status – different outcomes are possible
Timing of expense recognitionIPSAS 48: when the enforceable transfer RIGHT is extinguished. GFS: based on the TYPE of grant
15
Statement / Process Mapping
The master decision map
- Is there a BINDING ARRANGEMENT? No → §4 (provision, or cease-to-control expense). Yes → continue (§3)
- Identify each distinct TRANSFER RIGHT – the entity's enforceable right to have the recipient perform (§5)
- WHO performs first? Entity transfers first → TRANSFER RIGHT ASSET. Recipient performs first → TRANSFER OBLIGATION LIABILITY (§6)
- Recipient unable/unwilling to perform? → convert to a FINANCIAL ASSET if an enforceable unconditional cash right exists; otherwise test for IMPAIRMENT (§7)
- Measure the TRANSFER CONSIDERATION at carrying amount, including variable-consideration effects routed through IPSAS 19 (§9, §10)
- ALLOCATE consideration across transfer rights by stand-alone consideration, adjusted for variable amounts (§10)
- Recognize the expense as the transfer right asset is DERECOGNIZED or the transfer obligation liability is RECOGNIZED (§6)
Concept-to-statement mapping table
IPSAS 48 conceptStatement(s)Notes
Transfer right assetSOFPAt the carrying amount of resources already transferred
Transfer obligation liabilitySOFPAt the carrying amount the entity is obligated to transfer
Transfer expenseSOFPerfOn extinguishment of a transfer right, or liability recognition
Variable-consideration provisionSOFPPer IPSAS 19, only when more-likely-than-not
Converted financial asset (non-performance)SOFPSubsequently measured under IPSAS 41
Transfer arrangements, judgmentsNotesMandatory disclosures, paras. 53–61
16
Related Standards – Cross-Reference Map
How IPSAS 48 connects across the IPSAS body of literature
StandardNature of the connection
IPSAS 1Expense analysis, materiality, and aggregation disclosure principles (§12)
IPSAS 3Governs the retrospective transition option (§13)
IPSAS 19Governs non-binding-arrangement obligation provisions AND variable-consideration provisions – the central measurement engine throughout this Standard (§4, §10, §12)
IPSAS 21Impairment testing for a transfer right asset that isn't converted to a financial asset (§7)
IPSAS 30Disclosure requirements for converted financial assets and amortized-cost payables (§12)
IPSAS 41Subsequent measurement of a financial asset converted from a non-performing transfer right (§7)
IPSAS 47The direct mirror-image Standard – the recipient's own accounting for the SAME binding arrangements, with simultaneous adoption required (§1, §13)
17
Quick-Reference Glossary
Transfer expense
An expense from a transaction, other than taxes, where an entity provides a good, service, or other asset without directly receiving anything in return.
Transfer provider / recipient
The entity giving, and the entity receiving, in a transfer transaction.
Transfer right
An entity's enforceable right to have the transfer recipient satisfy its obligation, or face the binding arrangement's consequences.
Transfer obligation
An entity's own obligation in a binding arrangement to transfer resources in a specified manner.
Transfer consideration
The total amount of resources an entity expects to transfer.
Capital transfer (provider perspective)
An outflow from a binding arrangement specifying the recipient will acquire or construct a controlled non-financial asset.
Financial statement key
SOFP Statement of financial position
SOFPerf Statement of financial performance
Notes Notes to the financial statements