IT spend is no longer a parade of perpetual licenses on the balance sheet. It is SaaS subscriptions, cloud commits, partner revenue shares, and the occasional patented tech embedded inside your authentication stack. IFRS — through the IFRIC March-2019 and April-2021 agenda decisions — has been very specific about how this gets recorded. Most IT and procurement teams still get it wrong, and Big-4 auditors are now writing PBC requests around exactly these arrangements. This piece walks the standards, simulates the journals, and shows where Indonesian PSAK still has a gap.
Why IT Ops, Dev and Sourcing now sit inside the IFRS conversation
Three forces collided. First, IFRS 15 collapsed revenue recognition into a single five-step model that finally caught up to multi-element software contracts. Second, IFRS 16 pulled most lease-like infrastructure arrangements onto the balance sheet. Third, the IFRS Interpretations Committee (IFRIC) issued two agenda decisions — March 2019 on cloud computing arrangements (CCAs), and April 2021 on configuration and customization (C&C) costs in a SaaS contract — that effectively rewrote the IT cost capitalization playbook. The combined effect: if your IT Ops or Dev team is buying software, signing a SaaS subscription, or sourcing through a partner, the journals you used to book under IAS 38 are probably wrong.
What Big-4 auditors test first
PwC and EY engagement teams now ask, before testing balances: 'Show me the policy that distinguishes a service contract from an intangible asset, applied per arrangement above materiality.' If you cannot produce that policy, every capitalized SaaS implementation cost on your books is an audit finding waiting to happen.
Three big questions PwC, EY, and a PCAOB / SOX committee will ask
Q1 — Service contract or intangible asset? Show the test, per contract.
Under the IFRIC March-2019 agenda decision, a customer in a SaaS arrangement obtains an intangible asset under IAS 38 only if (a) the customer has the contractual right to take possession of the software during the hosting period without significant penalty, and (b) it is feasible for the customer to either run the software on its own infrastructure or contract another party to host it. If both conditions fail, the arrangement is a service contract — there is no intangible asset, no capitalization, only an expense as the service is consumed. Auditors will ask you to walk this two-step test for every SaaS deal above materiality and produce the contract clause that drives the conclusion.
Common failure mode
Indonesian and SE-Asia listed entities frequently capitalize 'software – SaaS' on the asset side. Under IFRS, that account simply should not exist for arrangements that fail the IFRIC test. Restatement risk is real once a Group auditor consolidates.
Q2 — For every capitalized C&C cost, where is the control assertion?
The IFRIC April-2021 decision is more nuanced. Configuration (setting up flags) and customization (writing additional code) costs in a SaaS arrangement are generally expensed as the service is received. They can be capitalized only if they create a separate intangible asset that the customer controls — for instance, custom code that runs on the customer's own infrastructure, or that the customer can extract and reuse. Auditors expect a per-cost-line memo: control assertion, useful life justification, amortization start date, and the impairment trigger you will monitor (e.g. vendor end-of-life, contract termination, change in usage).
Q3 — Principal vs agent in partner and reseller arrangements.
The moment you involve a sourcing partner, reseller, or system integrator, IFRS 15.B34–B38 applies. Are you the principal (you control the good or service before transfer to the customer — gross presentation) or the agent (you arrange for another party to provide it — net presentation)? The three indicators — primary responsibility, inventory risk, and pricing discretion — must be evaluated and documented per arrangement. PCAOB inspections regularly cite gross-vs-net errors as material weaknesses; SOX 404 testing now treats the conclusion memo as a key control.
How IFRIC interprets each spend category
(a) SaaS subscriptions
Default treatment is expense over the service period (IFRS 15 from the vendor's side; an expense as the service is consumed from the customer's side). Prepayments sit in 'Prepaid expense' and unwind monthly. There is no intangible asset unless the IFRIC March-2019 control test is met — which, in commercial multi-tenant SaaS, almost never happens. The DSAK-IAI in Indonesia has not issued an equivalent buletin teknis, but PSAK 25 paragraf 12 instructs preparers to apply IFRIC pronouncements where PSAK is silent.
(b) Software licenses (perpetual vs term)
A perpetual on-prem license that the customer can run on its own infrastructure is an intangible asset under IAS 38 — capitalize at cost, amortize over useful life. A term license with no take-possession right is a service contract. The IFRS 15 distinction between 'right to use' (point-in-time) and 'right to access' (over time) lives on the vendor's books, but it informs how the customer thinks about the contract substance.
(c) Partnerships, sourcing & embedded patented tech
Imagine a fictional vendor 'Aegis Auth' partnering with a telco to deliver frictionless authentication on smartphones — a masked, simulated SIM-binding token-exchange protocol broadly inspired by network-based authentication standards. The telco pays Aegis a SaaS subscription, a one-off configuration fee, a perpetual patent license to embed Aegis's SDK, and an integration fee to a third-party system integrator. Each leg of that arrangement hits a different standard: IAS 38 for the patent license (capitalizable — identifiable, controlled, future economic benefit), IFRS 15 contract cost asset (IFRS 15.91–94) for the integration fee paid to obtain or fulfill the contract, and IAS 38 / IFRIC April-2021 for the configuration fee. Treat them separately or you understate amortization expense and overstate intangible assets.
The capitalize-vs-expense decision matrix
| Item | Standard | Treatment | Audit checklist |
|---|---|---|---|
| Perpetual on-prem license | IAS 38 | Capitalize (intangible) | Take-possession right; useful life ≤ 10y default |
| SaaS subscription fee | IFRIC Mar-2019 | Expense (service) | No control of software; prepayment unwinds monthly |
| SaaS configuration (flags, mapping) | IFRIC Apr-2021 | Expense over service period | No separable asset |
| SaaS customization — separable code on customer infra | IAS 38 | Capitalize | Customer controls IP; UL memo on file |
| Data migration | IAS 38.69 | Expense | Excluded from cost of intangible |
| Training & change management | IAS 38.69(d) | Expense | Excluded — mandatory |
| Cloud IaaS — dedicated server with substitution restriction | IFRS 16 | ROU asset | Substantive substitution test failed → lease |
| Patent acquired (e.g. embedded auth SDK) | IAS 38.25 | Capitalize at cost | Identifiable + control + future EB |
| Internal R&D — research phase | IAS 38.54 | Expense | Mandatory; no judgement |
| Internal R&D — development phase | IAS 38.57 | Capitalize if PIRATE met | Probable benefit, Intent, Resources, Ability, Technical feasibility, Expenditure measurable |
| Partner upfront fee paid (incremental, recoverable) | IFRS 15.91 | Contract cost asset | Amortize over expected benefit period |
| Revenue share to partner (variable) | IFRS 15.B34 | Reduce revenue OR expense | Principal vs agent memo |
| Cloud commit / reserved instance prepayment | IAS 38 / IFRS 16 | Prepaid asset (or ROU if lease) | Service vs lease assessment |
Useful-life heuristic
For embedded patent licenses tied to a SaaS subscription, cap useful life at the shorter of the legal patent life and the contract's non-cancellable term plus reasonably certain renewals. Auditors love seeing that explicit min() calculation in your memo.
Journal simulation — Aegis Auth × PT Nusantara (fictional)
Total contract value USD 1,200,000 over 36 months. Components: USD 600,000 SaaS subscription, USD 300,000 implementation (USD 90,000 separable customization, USD 210,000 non-distinct C&C), USD 200,000 perpetual patent license to embed the Aegis SDK, USD 100,000 partner integration fee paid to a system integrator. Useful lives: customization 36 months, patent 60 months, contract cost asset 36 months.
Dr Prepaid SaaS subscription 600,000
Dr Implementation expense (C&C, non-distinct) 210,000
Dr Intangible — Customization (separable) 90,000
Dr Intangible — Patent license 200,000
Dr Contract cost asset (partner fee) 100,000
Cr Cash / Accounts payable 1,200,000Dr Subscription expense 16,667
Cr Prepaid SaaS subscription 16,667
Dr Amortization expense (customization) 2,500 # 90,000 / 36
Cr Acc. amortization — customization 2,500
Dr Amortization expense (patent) 3,333 # 200,000 / 60
Cr Acc. amortization — patent 3,333
Dr Amortization expense (contract cost) 2,778 # 100,000 / 36
Cr Acc. amortization — contract cost 2,778What changes if you got it wrong
If the entity had naively capitalized the full USD 1.2M as 'Software', Year 1 expense would understate by roughly USD 90k and intangible assets would overstate by the same. Across a portfolio of contracts this becomes material — and is the single most common SaaS restatement we see in SE-Asia listed entities.
Excel-style amortization roll-forward
| Period | Subscription exp | Customization amort | Patent amort | Contract cost amort | Total P&L hit |
|---|---|---|---|---|---|
| Month 1 | 16,667 | 2,500 | 3,333 | 2,778 | 25,278 |
| Month 12 | 16,667 | 2,500 | 3,333 | 2,778 | 25,278 |
| Month 36 (end SaaS) | 16,667 | 2,500 | 3,333 | 2,778 | 25,278 |
| Month 37–60 | — | — | 3,333 | — | 3,333 |
| Lifetime total | 600,000 | 90,000 | 200,000 | 100,000 | 990,000 + 210,000 day-1 expense |
The Indonesia PSAK gap
PSAK 19 (Aset Takberwujud) is the textual equivalent of IAS 38, and PSAK 72 mirrors IFRS 15. But DSAK-IAI has not issued any Indonesian buletin teknis or interpretasi equivalent to the IFRIC March-2019 or April-2021 agenda decisions on SaaS. In practice this leaves three gaps:
- No vernacular guidance on the take-possession test, so 'Software – SaaS' line items remain on local TBs and only get re-classified at Group consolidation.
- No DSAK position on C&C costs; many KAP (local audit firms) still tolerate full capitalization of implementation fees, citing PSAK 19 paragraf 25.
- No interpretation of cloud-commit prepayments under PSAK 73 (the IFRS 16 equivalent), so substitution-right analyses are inconsistent across telco and banking issuers.
Practitioner workaround
Until DSAK acts, document a written accounting policy memo invoking PSAK 25 paragraf 12 — which permits applying recent IFRIC pronouncements in the absence of specific PSAK guidance — and reference IFRIC March-2019 / April-2021 directly. This single memo is what saves you in a Group audit.
How IASB theory frames the judgement
The Conceptual Framework (2018 revision) defines an asset as 'a present economic resource controlled by the entity as a result of past events'. Control is the load-bearing word. A SaaS arrangement gives you the right to receive a service; it does not give you control of the underlying software resource. This is why IFRIC concluded the way it did — not because of a mechanical rule, but because the Conceptual Framework forces the question 'what do you control?' If you cannot answer that with a contract clause, you do not have an asset. Lecture-hall version: capitalization is the consequence of control, not the cause of it.
How rules can vary
US GAAP (ASC 350-40) was updated in 2018 to allow capitalization of SaaS implementation costs broadly mirroring internal-use software — a deliberate divergence from the stricter IFRIC view. Dual-reporting groups must maintain two ledgers and reconcile in the IFRS-to-GAAP bridge.
Download — printable accounting crosswalk
IFRS for SaaS, Subscriptions & Partnerships — practitioner crosswalk
3-page PDF with the decision matrix, the Aegis Auth Dr/Cr simulation, the PSAK gap memo template, and the three Big-4 questions. Branded for blog.rudyprasetiya.com.
ifrs-saas-subscription-partnership-accounting.pdf · Download PDF →
Rudy Prasetiya
IT GRC, cybersecurity & audit practitioner. Writes about controls that actually hold.
