ASC 853
Active
Service Concession Arrangements
Addresses accounting for service concession arrangements where an operator provides public services on behalf of a grantor.
1
Conceptual Framework Linkage
Why the operator doesn't recognise the infrastructure as its own
In a SERVICE CONCESSION ARRANGEMENT, a private OPERATOR builds, upgrades, operates, and/or maintains PUBLIC infrastructure (e.g. a toll road, water treatment plant, or airport) on behalf of a public-sector GRANTOR – but because the GRANTOR retains control over the infrastructure and its residual interest, the operator does NOT recognise the infrastructure as its own PROPERTY, PLANT & EQUIPMENT. Instead, ASC 853 requires the operator to recognise either an INTANGIBLE ASSET or a RECEIVABLE, depending on the arrangement's payment structure.
A standard added specifically to converge with IFRIC 12
ASC 853 was added to the Codification SPECIFICALLY to align US GAAP with IFRIC 12 (Service Concession Arrangements) – making this, like ASC 606/IFRS 15 and ASC 820/IFRS 13, a genuinely CONVERGED area by deliberate design, rather than a coincidental similarity.
2
Scope – the Two Control Indicators
Both indicators generally must be present
IndicatorDescription
1The GRANTOR controls or regulates WHAT services the operator must provide with the infrastructure, TO WHOM it must provide them, and AT WHAT PRICE
2The GRANTOR controls – through ownership, beneficial entitlement, or otherwise – any SIGNIFICANT RESIDUAL INTEREST in the infrastructure at the END of the arrangement
3
Excluded Arrangements
Genuine leases and operator-retained residual interest fall outside scope
Arrangements are EXCLUDED from ASC 853 if they meet the definition of a LEASE (ASC 842 applies instead), or if the OPERATOR (rather than the grantor) retains a SUBSTANTIVE residual interest in the infrastructure at the arrangement's end – in that case, normal PP&E accounting under ASC 360 would generally apply instead.
4
The Intangible Asset Model
Used when the operator bears demand risk
Where the operator's right is to CHARGE USERS of the public service directly (e.g. toll road users pay tolls), and the AMOUNT of consideration is CONTINGENT on the extent that the public actually USES the service (genuine DEMAND RISK borne by the operator), the operator recognises an INTANGIBLE ASSET – representing its RIGHT to charge users – rather than a receivable, since the ultimate amount to be collected isn't a fixed or determinable sum.
5
The Receivable Model
Used when the grantor unconditionally guarantees payment
Where the GRANTOR (rather than users) UNCONDITIONALLY GUARANTEES to pay the operator specified, determinable amounts (regardless of usage – e.g. fixed "availability payments" for keeping infrastructure available and operational), the operator recognises a RECEIVABLE instead – since the amount to be received is contractually fixed or determinable and not contingent on usage.
6
Revenue Recognition During the Construction/Upgrade Phase
ASC 606 governs construction/upgrade services revenue
During the CONSTRUCTION or UPGRADE phase, the operator recognises REVENUE for those construction/upgrade SERVICES under the normal ASC 606 revenue recognition model (generally over time, as the performance obligation to build/upgrade infrastructure is satisfied), with a corresponding intangible asset or receivable built up as consideration for that construction activity.
7
Worked Example – the Intangible Asset Model (a Toll Road)
Demand risk borne by the operator
Example: Building and operating a toll road
An operator builds a toll road for a state government under a 30-year concession, earning revenue solely from tolls charged to drivers. The state controls toll pricing and retains ownership of the road at the concession's end.
The operator recognises an INTANGIBLE ASSET – its right to charge tolls – measured initially based on the fair value of the construction services provided, since the ultimate amount the operator will collect depends entirely on future traffic volumes (genuine demand risk), not a fixed guaranteed sum from the state.
8
Worked Example – the Receivable Model (Guaranteed Availability Payments)
A fixed, guaranteed payment stream
Example: Operating a water treatment facility under fixed availability payments
An operator builds and operates a water treatment facility for a municipality, receiving fixed annual "availability payments" from the municipality regardless of actual water volume treated, so long as the facility remains operational and meets contractual performance standards.
Since the municipality (grantor) UNCONDITIONALLY GUARANTEES fixed, determinable payments – NOT contingent on usage – the operator recognises a RECEIVABLE for the construction services provided, rather than an intangible asset, reflecting the ABSENCE of genuine demand risk in this arrangement.
9
Disclosure Requirements
What ASC 853 requires
Description of the arrangement, including its significant terms and the nature of rights/obligationsNature and extent of rights to use specified infrastructure, and obligations to provide/receive specified servicesChanges in the arrangement during the period
10
Critical Judgments & Estimates
Where judgement matters most
SIGNIFICANT JUDGEMENTS
Whether both control indicators are met, bringing the arrangement into ASC 853's scopeWhether the arrangement should follow the intangible asset model or the receivable model, or a combination of both
SIGNIFICANT ESTIMATES
Fair value of construction/upgrade services provided, forming the basis for initial intangible asset or receivable measurement
11
ASC 853 vs IFRIC 12 – a Genuinely Converged Standard
Comparison – ASC 853 vs IFRIC 12
FeatureUS GAAP (ASC 853)IFRS (IFRIC 12)
Scope control indicatorsGrantor controls services/pricing and residual interestSame two indicators – converged by deliberate design
Intangible asset model (demand risk)AvailableAvailable – converged
Financial asset/receivable model (guaranteed payment)AvailableAvailable – converged
ASC 853 was deliberately added to the Codification to mirror IFRIC 12 – this is one of the clearest examples of intentional, standard-level convergence anywhere in the library, alongside ASC 606/IFRS 15 and ASC 820/IFRS 13.
12
Statement Mapping
Where every ASC 853 event lands
EventStatement(s) affectedNotes
Construction/upgrade services revenueISRecognised under ASC 606, generally over time
Intangible asset modelBSRight to charge users recognised as an intangible asset
Receivable modelBSGuaranteed payment right recognised as a receivable
13
Related Topics
Cross-reference map
TopicConnection
ASC 606Governs revenue recognition for the construction/upgrade services provided under a concession arrangement
ASC 350Intangibles – governs subsequent amortisation of the intangible asset recognised under the intangible asset model
ASC 842Applies instead if the arrangement meets the definition of a lease, excluding it from ASC 853's scope
14
Quick-Reference Glossary
Grantor
The public-sector (or public-sector-like) entity that grants the operator the right to operate infrastructure under a service concession arrangement.
Operator
The private entity that builds, upgrades, operates, or maintains public infrastructure under a service concession arrangement.
Availability payment
A fixed payment made by the grantor to the operator for keeping infrastructure available and operational, regardless of actual usage.
Financial statement key
BS Balance sheet
IS Income statement
SE Statement of changes in equity
OCI Other comprehensive income
SCF Statement of cash flows