APRA APS 910 Financial Claims Scheme: the $250k deposit guarantee

What APS 910 is in one minute

Prudential Standard APS 910 *Financial Claims Scheme* is the APRA standard that requires locally-incorporated authorised deposit-taking institutions (ADIs) — banks, credit unions and building societies — to be operationally ready to pay depositors quickly if the Financial Claims Scheme (FCS) is ever activated. The FCS is the Australian Government's deposit guarantee: it protects deposits up to $250,000 per account holder, per ADI.

In practical terms, APS 910 is not about the guarantee itself (that sits in legislation). It is about *readiness*. It compels each covered ADI to maintain the systems, data and processes needed so that, on short notice, it can identify every account holder, calculate each one's protected balance, and generate the payment instructions APRA would use to reimburse depositors. If you are searching for "aps 910", you are almost certainly looking at this operational-readiness obligation rather than the guarantee mechanics.

The legislative basis: the Banking Act and the FCS

The Financial Claims Scheme is established under the Banking Act 1959, in the Division of Part II dealing with the financial claims scheme for account-holders with insolvent ADIs. The scheme can only operate once the Government formally declares that it applies to a particular ADI — typically where the institution has become insolvent and APRA is appointed to administer the payout.

APRA makes prudential standards, including APS 910, under its standard-making power in the Banking Act. The definition of a "protected account" — broadly, the deposit accounts that attract the guarantee — also sits in the Act. So the architecture is:

• The Banking Act creates the scheme, the guarantee and the declaration trigger.
• APS 910 imposes the day-to-day readiness obligations on ADIs so the scheme can actually be delivered when triggered.

APS 910 has been remade and refreshed over time; the version most readers will be working from is the standard that APRA finalised after a short consultation, taking effect in late 2023. Always confirm you are reading the current version on the APRA Prudential Handbook.

Who APS 910 applies to

APS 910 applies to locally-incorporated ADIs — Australian-incorporated banks, credit unions and building societies whose depositors are covered by the FCS. Foreign ADIs operating in Australia as branches are generally outside FCS coverage, because their depositors are not protected by the scheme; the readiness obligations follow the coverage.

If you operate a covered ADI, APS 910 is a live, continuous compliance obligation regardless of how remote insolvency feels. It is part of APRA's crisis-management framework, sitting alongside resolution and recovery planning. The point of the standard is that operational readiness cannot be built in a crisis — it has to be tested and maintained in calm conditions.

The FCS also extends to general insurance policyholders under a separate part of APRA's framework, but APS 910 is the standard for the deposit (ADI) side of the scheme.

The $250,000 deposit guarantee explained

The headline figure is the protection cap. Under the FCS:

• Eligible deposits are guaranteed up to $250,000 per account holder, per ADI.
• The cap applies to the sum of an account holder's protected deposits held under a single banking licence — so multiple accounts at the same institution are added together, not each guaranteed separately.
• For joint accounts, each account holder is generally entitled to the cap in their own right.
• An "account holder" can be an individual, a company, a trust, or a self-managed superannuation fund.

Covered products typically include transaction, savings and cheque accounts, term deposits, and offset accounts where the offset is a separate deposit account. Coverage detail can vary by product, so check the types of accounts covered page rather than assuming. A key consumer point: where a customer banks with brands operating under the same banking licence, those balances are combined for the cap — a common source of confusion when one banking group runs several brands.

Core obligations: Single Customer View and payout readiness

The substance of APS 910 is the requirement to build and maintain a Single Customer View (SCV) — the ability to consolidate, accurately and quickly, all of an account holder's protected balances so the $250,000 cap can be applied per person or entity.

Core operational obligations under the standard include the ability to:

• Uniquely identify each account holder and aggregate their accounts.
• Calculate the protected balance for each account holder, applying the FCS cap correctly.
• Generate payment instructions and reports in the format APRA requires, and transmit them to APRA, within the timeframes set by the standard.
• Maintain the data quality, systems and documentation needed to produce that information on demand.

The intent is speed and accuracy: if the scheme is declared, depositors should get timely access to their guaranteed funds, which means the ADI's data must already be clean, mapped and exportable. Treat the SCV not as a one-off project but as a data-governance discipline that has to survive every core-banking change, migration and acquisition.

Testing, audit and CEO attestation

APS 910 does not stop at building capability — it requires ADIs to prove it. The standard mandates:

• Regular testing of the FCS systems and the ability to produce SCV data and payment files.
• External audit / independent assurance over the relevant systems and data.
• CEO attestation to APRA regarding compliance and the integrity of the required systems and data.

This assurance layer is what gives APRA confidence that readiness is real rather than theoretical. Boards and senior management should ensure the testing cycle, audit scope and attestation wording are mapped to the current version of the standard, and that exceptions found during testing are remediated and tracked — not just noted.

Common pitfalls and what to do now

The recurring problems with APS 910 compliance are about data and aggregation, not the headline guarantee:

• Mis-aggregating account holders. Failing to combine all balances under one licence — or across multiple brands on one licence — produces wrong protected-balance figures.
• Stale SCV after change events. Core-banking migrations, product launches and acquisitions break the mapping that the SCV relies on. The SCV must be re-validated after every such event.
• Treating testing as a formality. Untested or partially tested payout files can fail under real timeframes. Test the full chain through to APRA-format output.
• Attestation gaps. CEO attestation should rest on documented evidence and current testing, not assurances given verbally.

What to do now if you operate a covered ADI:

1. Confirm you are working from the current APS 910 on the APRA Prudential Handbook.
2. Re-validate your Single Customer View logic against the per-account-holder, per-ADI cap, including multi-brand scenarios.
3. Run an end-to-end payout-file test and close any exceptions before the next attestation.
4. Confirm the external audit scope and CEO attestation language match the standard's current requirements.

For broader context on how this fits with deposit-taking regulation, see APRA's plain-language explainer on the Financial Claims Scheme and the wider financial services regulatory landscape. Always verify current figures, thresholds and timing directly with APRA before relying on them.