Why it matters
Payment and e-money institutions licensed by SAMA (or other regional regulators) are subject to minimum capital and safeguarding requirements that are not IFRS themselves but commonly require disclosure alongside the financial statements, and can affect going-concern and capital-management disclosures under IAS 1; a breach that is not flagged can leave readers unaware of a solvency or license-continuity risk that is often more urgent than routine IFRS matters.
Diagnostic questions
What specific minimum capital, liquid-asset, or safeguarding ratio applies under the entity's license category, and is compliance monitored intra-period, not just at year end? If a breach occurred or is anticipated, has the going-concern implication under IAS 1/IAS 10 been assessed, including post-year-end breaches? Does the regulatory capital base reconcile to IFRS equity, with reconciling items documented?
Recognition
1) Identify the specific minimum capital, liquid-asset, or safeguarding ratio(s) applicable under the entity's SAMA (or relevant regulator) license category. 2) Confirm compliance status at each reporting date and monitor intra-period, not just at year end. 3) If a breach occurred or is anticipated, assess whether it triggers a going-concern indicator under IAS 1/IAS 10 (including post-year-end breaches as a non-adjusting or adjusting event as appropriate). 4) Reconcile the regulatory capital base to IFRS equity where these differ (e.g., due to prudential deductions or filters), documenting each reconciling item. 5) Confirm the regulatory rules themselves do not override IFRS classification of any instrument (e.g., certain capital instruments may count as regulatory capital but still be a financial liability under IAS 32). 6) Update the analysis whenever SAMA rulebook changes are issued.
Measurement
Reconcile, where disclosed, the regulatory capital base to IFRS equity if the two differ due to prudential filters or deductions; measurement of the underlying assets and liabilities still follows IFRS regardless of the regulatory capital treatment; monitor the capital ratio using the same measurement basis the regulator requires, which may not be IFRS-consistent, and clearly label any regulatory-basis figures presented alongside IFRS figures.
Presentation & disclosure
Disclose: capital management objectives, policies and processes; whether externally imposed capital requirements were complied with throughout the period; the nature of any breach, its cause, and remedial actions taken; a reconciliation between regulatory capital and IFRS equity if materially different; and any going-concern implications of non-compliance.
Common mistakes
- Assuming regulatory capital treatment overrides IFRS classification (e.g., of certain instruments as equity)
- omitting capital-management disclosures because the requirement is '
- only regulatory'
- rather than an IFRS disclosure matter
- not flagging a capital shortfall as a possible going-concern indicator
- disclosing compliance as of year-end only without confirming there was no intra-period breach
- failing to update disclosures when the regulator'
- s minimum requirement itself changes.
Simple example
A SAMA-licensed e-money institution is required to maintain minimum capital of SAR 5,000,000; at year end its IFRS equity is SAR 5,300,000, comprising SAR 5,000,000 share capital and SAR 300,000 retained earnings. No journal entry is required for the regulatory capital assessment itself (it does not change IFRS recognition/measurement); management discloses the capital management policy in a note and confirms compliance with the regulatory minimum throughout the year, alongside a simple reconciliation table showing IFRS equity of SAR 5,300,000 versus the SAR 5,000,000 regulatory minimum, a SAR 300,000 buffer.
Professional judgment
Because this is driven by evolving local regulatory rulebooks rather than IFRS, entities should confirm current SAMA (or the relevant GCC regulator) requirements directly rather than relying on general accounting guidance; treatment of borderline instruments for capital purposes is often contentious. Grey areas include: whether subordinated shareholder loans or hybrid instruments count toward regulatory capital while remaining liabilities under IAS 32; how to treat a temporary, quickly-cured breach (e.g., resolved within days via a capital injection) for disclosure purposes; and the interaction between group-level capital adequacy and standalone entity requirements in multi-license group structures.
Source basis
Local Regulation · Regulatory Capital Disclosures (interacts with IFRS 7 / IAS 1)
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
- IFRS 15Principal vs agent in payment flows
- Professional JudgmentClient money segregation and balance sheet treatment
- IFRS 9Settlement receivables and float
- IAS 37Chargebacks and fraud loss provisions
- IFRS 9BNPL portfolio classification and expected credit losses
- IFRS 15Interchange and MDR revenue recognition
Educational and navigation content only. Not professional advice. Does not reproduce official IFRS/IAS text. Consult the authoritative standards and qualified professionals; professional judgment may still be required.
