# Australia moves CRS reporting to schema 3.0 from 1 January 2027, with transitional codes

> The ATO moves CRS reporting to schema 3.0 on 1 January 2027, asks RFIs not to lodge from 15 December to 15 January, and allows transitional codes.

Source: https://taxdo.com/resources/blog/post/australia-crs-schema-3-0-cutover

Last updated: 2026-11-08

**From 1 January 2027 the ATO will accept CRS files in schema 3.0 only, with transitional “not reported” codes allowed in reports due by 31 July 2027.**

The Australian Taxation Office (ATO) will reject CRS files on schema version 2.0 from 1 January 2027, under a hard cutover announced on 17 August 2026\. Version 0.3 of its draft CRS 2027 specification was published on 22 October 2026\. The ATO has asked Reporting Financial Institutions (RFIs) not to submit files from 15 December 2026 to 15 January 2027.

## 01 · What changed

In its [software developers notice](https://softwaredevelopers.ato.gov.au/CRS) of 17 August 2026, the ATO said that from 1 January 2027 files submitted using Version 2.0 “will be rejected”. The OECD’s [Amended Common Reporting Standard XML Schema user guide](https://www.oecd.org/en/publications/2024/10/amended-common-reporting-standard-xml-schema%5F27960161.html) documents schema 3.0.

The [version 0.3 package](https://softwaredevelopers.ato.gov.au/CRSspecification) adds a rule that each DocRefID in the payload must be unique and updates the rule limiting each lodgment to one CrsBody element. The ATO’s [CRS reporting page](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/third-party-reporting/crs-reporting) (last updated 6 October 2026) sets out the transitional codes.

## 02 · Key dates

| **Date**                            | **What happens**                                                                                  | **Source**                     |
| ----------------------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------ |
| 17 August 2026                      | Cutover announced; schema 3.0 testing available in the External Vendor Testing Environment (EVTE) | ATO Software Developers notice |
| 15 December 2026 to 15 January 2027 | RFIs asked not to submit CRS files                                                                | ATO CRS reporting page         |
| 1 January 2027                      | Schema 3.0 takes effect; Version 2.0 files rejected                                               | ATO Software Developers notice |
| 31 July 2027                        | Annual due date; transitional codes allowed in reports due by then                                | ATO CRS reporting page         |

The window is a request: RFIs “are also requested not to submit files” while system updates are deployed. The ATO does not say what happens to a file lodged in that window.

## 03 · Who is affected

The cutover applies to every RFI lodging CRS reports; the ATO says RFIs include banks and other deposit-taking institutions, custodial institutions, investment entities and specified insurance companies. A trust that is an RFI still reports its own details, including its [TFN or ABN](https://taxdo.com/resources/global-tax-id-validation-guide/australia), not the trustee’s.

## 04 · What it means in practice

The ATO says the new data elements are mandatory: an RFI must either report the data or use the transitional codes. For reports due by 31 July 2027 the codes are CRS900 (Account Holder self-certification status), CRS800 (Controlling Person type), CRS1000 (Controlling Person self-certification status), CRS1100 (account type) and CRS1200 (Pre-existing Account or New Account), each meaning “not reported”. The OECD user guide describes each as available “as a transitional measure, in order to facilitate interoperability with the previous version of the schema”, notably for corrections.

The ATO says RFIs should not use the new Account Number Type code OECD606 (Specified Electronic Money Product), which has no transitional code. Not using CRS1100 activates additional ATO validation rules on consistency between Account Type, Account Number Type, Equity Interest Type and Payment Type. The August notice adds rules on schema versioning and mandatory contact information; neither these nor schema 3.0 apply to production files before 1 January 2027.

The ATO’s pages state no exception for corrections to periods reported on Version 2.0, nor whether transitional codes may be used in them. The v0.3 package lists further rules for DDProcedure, the Pre-existing or New Account field, as “\[d\]ependent on legislation review and release”.

## 05 · What to do now

**1.** Plan any remaining Version 2.0 lodgment, including corrections, around the 15 December to 15 January window and the 1 January 2027 cutover.

**2.** Developers and in-house XML producers: test against the v0.3 package in the EVTE, after registering with the ATO’s Digital Partnership Office.

**3.** For reports due by 31 July 2027, decide for each new data element whether to report it or use its transitional code, and leave out OECD606.

## 06 · The wider picture

Treasury’s [exposure draft](https://storage.googleapis.com/files-au-treasury/treasury/p/prj3fc33897695d43bf731d0/page/fil3fc4348d8b5d68289257f%5Fc2026%5F813391%5Fed.pdf), on which [consultation](https://consult.treasury.gov.au/c2026-813391) closed on 28 October 2026, would incorporate the amendments in the OECD’s 2023 update to the Common Reporting Standard, with 1 January 2027 as the effective date of the amended CRS. Its amendments to Subdivision 396-C would apply to the 2027 calendar year and later. From the later of 1 January 2027 and commencement, the one-penalty-unit penalty for failing to obtain a self-certification would also cover failing to validate one or to act on a change in circumstances. The draft would provide a framework to introduce the OECD’s Crypto-Asset Reporting Framework, which our [CARF guide](https://taxdo.com/resources/blog/post/carf-crs2-crypto-tax-transparency-guide) sets out.

Our [CRS 2.0 guide](https://taxdo.com/resources/blog/post/crs-2-0-compliance-guide-banks) covers the amended standard and the [self-certification guide](https://taxdo.com/resources/blog/post/crs-2-0-dac8-mandatory-self-certification-guide) the self-certification data it requires. New Zealand’s Inland Revenue is also [moving CRS filing to schema 3.0](https://taxdo.com/resources/blog/post/new-zealand-crs-schema-3-0-cutover).

## How TaxDo helps

Our [regulatory compliance engine](https://taxdo.com/services/regulatory-compliance) collects and checks the self-certification, [validates TINs against official sources](https://taxdo.com/services/tax-identity/tin-lookup) and resolves indicia, so new accounts carry the new data elements at onboarding. It produces [CRS XML](https://taxdo.com/services/regulatory-compliance/crs) validated against the OECD schema 3.0, ready for your institution to test and lodge, while the reporting obligation stays with your institution. See [CRS compliance](https://taxdo.com/services/regulatory-compliance/crs).

## Frequently asked questions

### Is Australia in the CRS?

Yes. Australia's CRS obligations sit in Subdivision 396-C of Schedule 1 to the Taxation Administration Act 1953.

### What needs to be reported under CRS?

Treasury's [explanatory materials](https://storage.googleapis.com/files-au-treasury/treasury/p/prj3fc33897695d43bf731d0/page/fil3fc49a2fe901e8722181a%5Fc2026%5F813391%5Fem.pdf) say that, under Australia's draft law, Reporting Financial Institutions (RFIs) would report for the 2027 and later calendar years, beyond the existing account data, whether a valid self-certification was obtained, whether the account is pre-existing or new, the account type, whether it is jointly held and by how many holders, and the role of each Controlling Person or Equity Interest Holder.

## References

- [Australian Taxation Office, Common Reporting Standard reporting](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/third-party-reporting/crs-reporting): last updated 6 October 2026
- [ATO Software Developers, Common Reporting Standard](https://softwaredevelopers.ato.gov.au/CRS): notice of 17 August 2026
- [ATO Software Developers, Common Reporting Standard (CRS) 2027 specification v0.3](https://softwaredevelopers.ato.gov.au/CRSspecification): published 22 October 2026
- [The Treasury, Crypto asset tax transparency: draft legislation](https://consult.treasury.gov.au/c2026-813391): consultation 15 to 28 October 2026
- [The Treasury, Exposure draft explanatory materials, Treasury Laws Amendment Bill 2026: Tax Information Reporting](https://storage.googleapis.com/files-au-treasury/treasury/p/prj3fc33897695d43bf731d0/page/fil3fc49a2fe901e8722181a%5Fc2026%5F813391%5Fem.pdf): October 2026
- [OECD, Amended Common Reporting Standard XML Schema: User Guide for Tax Administrations](https://www.oecd.org/en/publications/2024/10/amended-common-reporting-standard-xml-schema%5F27960161.html): October 2024
_This article reports ATO guidance and Treasury's exposure draft, which is not law, as at 6 November 2026, and is not tax or legal advice. Confirm obligations under Subdivision 396-C of Schedule 1 to the Taxation Administration Act 1953 with the ATO or a registered tax agent._ 

![TaxDo](https://taxdo.com/icons/icon-192.png) 

TaxDo Team Tax & Regulatory Advisory Team [LinkedIn](https://www.linkedin.com/company/taxdo-global/) [Facebook](https://www.facebook.com/profile.php?id=61567185422669) [X](https://x.com/TaxDoGlobal)