APRA APS 112 sets out how Australian authorised deposit-taking institutions (ADIs) must calculate their credit risk capital requirements under the Basel III standardised approach, as adapted for the Australian regulatory context. In practice, this means ADIs must assign risk weights to their on-balance-sheet and off-balance-sheet exposures, calculate risk-weighted assets (RWA), and hold sufficient capital to meet APRA’s minimum requirements. The sections below walk through what APS 112 demands, how it differs from the global Basel framework, where ADIs typically struggle, and how to build a practical readiness programme.
What does APRA APS 112 require Australian ADIs to calculate?
APS 112 requires Australian ADIs to calculate risk-weighted assets for credit risk exposures using the standardised approach. This means assigning prescribed risk weights to each exposure category, including residential mortgages, corporate lending, retail portfolios, and off-balance-sheet commitments, and then aggregating those RWA figures to determine the minimum capital an ADI must hold against credit risk.
More specifically, ADIs need to work through several interconnected calculations. First, they must classify every on-balance-sheet asset and off-balance-sheet item into the correct exposure class. Each class carries a risk weight, which may be fixed or dependent on external credit ratings, loan-to-value ratios, or other borrower characteristics. Second, ADIs apply credit conversion factors to off-balance-sheet exposures to convert them into credit equivalent amounts before risk-weighting is applied. Third, credit risk mitigation techniques, such as eligible collateral or guarantees, can reduce the effective exposure or risk weight, but only when they meet APRA’s eligibility criteria.
The resulting RWA figure feeds directly into the capital adequacy ratio. APRA requires ADIs to maintain a minimum Common Equity Tier 1 (CET1) ratio, a Tier 1 ratio, and a Total Capital ratio, all calculated as a percentage of total RWA. APS 112 is therefore not a standalone exercise. It sits at the heart of an ADI’s overall capital adequacy framework and directly influences how much capital the institution needs to hold at any given point in time.
How does APS 112 differ from the Basel III standardised approach?
APS 112 is built on the Basel III standardised approach but includes APRA-specific adjustments that are, in several areas, more conservative than the global Basel framework. The most significant difference is that APRA applies higher risk weights to certain residential mortgage exposures, particularly investor loans and interest-only mortgages, reflecting the characteristics of the Australian housing market.
There are several other areas where APS 112 diverges from the Basel Committee’s baseline:
- Residential mortgages: APRA uses its own loan-to-value ratio bands and risk weight schedule rather than the Basel standard table, and distinguishes between standard and non-standard loans with different treatment for each.
- Unrated corporate exposures: APRA’s treatment of unrated corporates can differ from the Basel default, requiring ADIs to apply judgement in classification rather than defaulting to a single prescribed weight.
- Sovereign and bank exposures: APRA retains specific requirements for exposures to the Australian government and the Reserve Bank of Australia, which interact with but are not identical to the Basel sovereign risk weight framework.
- Credit risk mitigation: APRA’s eligibility criteria for collateral and guarantees are closely aligned with Basel but include additional operational requirements that ADIs must satisfy before mitigation benefits can be recognised.
The practical implication is that ADIs cannot simply implement a generic Basel III credit risk engine and assume it meets APS 112. They need a system that can accommodate APRA’s specific risk weight schedules, exposure classifications, and mitigation rules as distinct configurations, not as minor tweaks to a global template.
What are the biggest compliance challenges ADIs face under APS 112?
The biggest compliance challenges under APS 112 are data quality and granularity, the complexity of mortgage risk weight calculations, and the operational burden of keeping the framework current as APRA issues updated guidance. Each of these can slow down reporting cycles and introduce calculation errors if systems are not purpose-built for the task.
Data quality and contract-level granularity
APS 112 requires risk weights to be applied at the individual exposure level. This means an ADI needs clean, complete, and correctly classified data for every loan, commitment, and off-balance-sheet item in its portfolio. In practice, data is often spread across multiple origination systems, product platforms, and legacy databases. Consolidating that data, validating it, and mapping it to the correct APS 112 exposure class is one of the most time-consuming parts of the compliance process. When data quality is poor, risk weights get applied incorrectly, and the resulting RWA figure cannot be trusted.
Mortgage portfolio complexity
Residential mortgages are typically the largest single asset class for Australian ADIs, and APS 112 applies a detailed risk weight schedule to them. LVR bands, loan purpose, repayment type, and whether a loan is classified as standard or non-standard all affect the risk weight. Managing these variables across a large mortgage book, and updating them as loan characteristics change over time, requires a system that can handle dynamic risk weight assignment at scale without manual intervention.
Keeping pace with regulatory updates
APRA regularly updates APS 112 and its associated guidance. Each update can require changes to risk weight tables, exposure classifications, or mitigation eligibility criteria. ADIs relying on hardcoded or IT-dependent systems face lengthy development cycles every time a change is needed. This creates a recurring compliance risk: the system may be accurate for the previous version of the standard but out of date by the time a regulatory update takes effect.
How can ADIs prepare their systems for APS 112 compliance?
ADIs can prepare their systems for APS 112 compliance by investing in three areas: a reliable data foundation, a flexible calculation engine, and a clear approach to regulatory reporting. Getting these three elements right means the compliance process becomes repeatable and auditable rather than a manual scramble at each reporting date.
On the data side, ADIs should prioritise building a centralised financial data repository that aggregates exposure data from all source systems, applies quality checks at the record level, and maintains a complete audit trail from source to calculation result. Principles aligned with BCBS 239, the Basel Committee’s standards for effective risk data aggregation, provide a useful reference point here. A system that surfaces data quality scores across millions of records and supports a structured correction workflow with approval steps gives risk teams confidence that the numbers feeding into RWA calculations are reliable.
On the calculation side, the system needs to support APRA’s specific risk weight schedules and exposure classifications as configurable parameters rather than hardcoded rules. This matters because when APRA updates APS 112, the change can be implemented through configuration rather than a development project. The ability to run what-if analyses and stress tests on the RWA output, without requiring IT involvement, also allows risk teams to understand the capital impact of portfolio changes or regulatory updates before they take effect.
On reporting, it is worth treating regulatory calculations and reporting as two distinct disciplines. The calculation engine should produce accurate, granular, auditable RWA results. Separately, a standard connector layer can format and deliver those results to whichever regulatory reporting vendor the ADI already uses or prefers. This separation gives ADIs flexibility to work with best-of-breed reporting tools rather than being locked into a single end-to-end solution that may not support all jurisdictions or reporting formats equally well.
When should ADIs start their APS 112 readiness programme?
ADIs should start their APS 112 readiness programme well before any regulatory deadline, ideally at least twelve months in advance. The data consolidation and system configuration work takes longer than most teams anticipate, and leaving insufficient time creates pressure that leads to shortcuts, which in turn create audit and accuracy risks.
In 2026, ADIs that have not yet fully implemented the updated APS 112 requirements should treat this as an immediate priority. APRA’s supervisory focus on capital adequacy and credit risk measurement has intensified, and the regulator expects ADIs to demonstrate not just compliant outputs but also a robust, auditable process behind those outputs.
A practical readiness programme typically moves through three phases. The first is a gap assessment: understanding where current data, systems, and processes fall short of what APS 112 requires. The second is remediation: addressing data quality issues, implementing or configuring the calculation engine, and establishing the reporting workflow. The third is validation and parallel running: testing the new system against known results, running it in parallel with existing processes, and building confidence in the output before going live.
Starting early also gives ADIs time to use the readiness programme as an opportunity rather than just a compliance exercise. A system capable of producing accurate, granular APS 112 results in near real time is also a system that can support capital planning, portfolio strategy, and internal risk management, not just regulatory submissions.
At ElysianNxt, our Basel.NXT module covers the full credit risk standardised approach, including APRA-specific risk weight configurations, credit risk mitigation, and output floor calculations, all within a platform that is configurable through the UI rather than through IT development. If you want to see how that maps to your APS 112 requirements, our team is happy to walk you through it. explore credit risk
Frequently Asked Questions
Can smaller or mid-tier ADIs use the same APS 112 compliance approach as the major banks?
Yes, but the scale and complexity of implementation will differ. Smaller ADIs typically have less portfolio diversity, which simplifies exposure classification, but they often have fewer internal resources to dedicate to data remediation and system configuration. The core requirements of APS 112 apply equally regardless of ADI size, so the framework and methodology remain the same — what changes is the scope of the data consolidation effort and the level of automation needed to sustain compliance efficiently over time.
What happens if an ADI misclassifies an exposure under APS 112?
Misclassification directly distorts the RWA calculation, which means the ADI may be holding either too little or too much capital against that exposure. Undercapitalisation is the more serious risk and can attract APRA supervisory action, including requirements to hold additional capital buffers or remediate the calculation process. Beyond the capital impact, misclassifications also undermine the audit trail, making it harder to demonstrate to APRA that the overall capital adequacy framework is reliable and well-controlled.
How should ADIs handle exposures that don't fit neatly into a single APS 112 exposure class?
APS 112 includes guidance on how to treat exposures that share characteristics across multiple classes, but ambiguous cases still require documented judgement calls. ADIs should establish a formal classification policy that sets out decision rules for edge cases, supported by a sign-off process involving risk and finance teams. Documenting the rationale for borderline classifications is important not just for internal governance but also for demonstrating to APRA that the ADI has applied a consistent and defensible methodology across its entire portfolio.
How do credit risk mitigation techniques like guarantees and collateral actually reduce RWA under APS 112?
Under APS 112, eligible collateral and guarantees reduce RWA either by lowering the effective exposure amount or by substituting a lower risk weight (for example, replacing the borrower's risk weight with the guarantor's). However, APRA's eligibility criteria are strict: collateral must meet legal certainty, valuation, and operational requirements, and guarantors must be recognised entities with an eligible credit rating or classification. ADIs should not assume that all collateral held commercially will qualify for mitigation treatment under APS 112 — a specific eligibility assessment is required for each instrument.
What is the role of external credit ratings in APS 112 risk weight calculations, and what if a borrower is unrated?
For certain exposure classes, such as corporate and bank counterparties, APS 112 allows ADIs to use external credit ratings from APRA-approved rating agencies to determine the applicable risk weight. When a borrower is unrated, ADIs must apply the prescribed unrated risk weight for that exposure class, which is often higher than the rated equivalent. This makes it important for ADIs to maintain accurate records of which counterparties hold eligible external ratings and to update those records promptly when ratings change, as a rating downgrade or withdrawal can materially increase RWA.
How often should ADIs review and update their APS 112 calculation parameters as APRA releases new guidance?
ADIs should monitor APRA's publications continuously and conduct a formal review of their APS 112 parameters every time APRA issues an updated prudential standard, practice guide, or information paper that touches on credit risk. In practice, this means designating a regulatory change owner within the risk or finance function who tracks APRA releases and triggers an impact assessment whenever relevant guidance is updated. Relying on periodic reviews alone — such as annual reviews — is insufficient given the pace at which APRA has been refining its capital framework in recent years.
What documentation should ADIs maintain to support an APRA review of their APS 112 calculations?
ADIs should maintain end-to-end documentation that covers data lineage from source systems through to the final RWA output, the classification methodology and decision rules applied to each exposure class, evidence that credit risk mitigation instruments meet APRA's eligibility criteria, and a record of any judgement calls made for non-standard exposures. Calculation logs that show how each risk weight was derived — including the input variables used — are particularly important, as APRA expects ADIs to be able to reconstruct and explain any individual calculation, not just present aggregate results.
Related Articles
- What is IRRBB and why does it matter for banks?
- What does the output floor mean for bank capital requirements?
- How does COREP reporting work for financial institutions?
- What is the role of macroeconomic variables in stress testing?
- How do you measure credit risk exposure?
This content was generated with the help of AI and it may contain mistakes
