Australian CRS Reporting: ATO Specification v1.1 to Schema v3.0

Section 396-105 in Schedule 1 to the Taxation Administration Act 1953 gives every Australian reporting financial institution that maintained a reportable account during a calendar year until the first 31 July after that year to give the Commissioner of Taxation its Common Reporting Standard statement. The XML file carrying that statement is checked against the Australian Taxation Office’s CRS 2021 specification, a versioned technical package on the ATO’s Software Developers site whose published releases include v1.1 through v1.4. Australian CRS reporting is now heading into its first schema change since the move to v2.0 in 2021: the ATO has told reporting financial institutions that version 3.0 of the OECD CRS XML Schema takes effect on 1 January 2027, and has asked them not to lodge CRS reports between 15 December 2026 and 15 January 2027 while it updates its systems.

Four layers decide what an Australian CRS file must contain and how it is checked: the statute in Subdivision 396-C, the OECD schema and its user guide, the ATO’s own validation rules, and the ATO’s lodgment instructions. They move on separate clocks. The ATO’s schema switch on 1 January 2027 is an administrative change to the file format. Treasury’s October 2026 exposure draft, which would bring the OECD’s 2023 amendments to the CRS into Australian law for the 2027 calendar year, is a legislative change that has not yet been passed.

Related reading: how Germany’s BZSt is moving its CRS filers to schema v3.0

Australian CRS reporting dates for 2026 to 2028

Date What happens Status and source
31 July each year CRS statement for the previous calendar year (1 January to 31 December) due to the Commissioner In force: TAA 1953 Sch 1 s 396-105(6); ATO CRS reporting page
2 October 2026 Reported ATO email circular concerning CRS XML Schema v3.0; the original 2 October 2026 communication was not independently available for verification As reported by KPMG (23 October 2026); see the ATO guidance updated 6 October 2026
15 December 2026 to 15 January 2027 ATO asks reporting financial institutions not to submit CRS reports while it updates its systems (a request, not a stated channel closure) ATO guidance, as reported by KPMG
1 January 2027 CRS XML Schema v3.0 takes effect for ATO lodgments ATO guidance, as reported by KPMG and Allens
1 January 2027 Possible effective date of the amended CRS, to be confirmed Treasury consultation only; commencement subject to confirmation against the exposure draft and final legislation; not law
31 July 2027 First CRS reports in schema v3.0 due, ordinarily for calendar year 2026; transitional “not reported” codes permitted ATO guidance, as reported by KPMG and Allens
31 July 2028 First statement for the 2027 calendar year, if the amended CRS applies from that year and the s 396-105(6) deadline is retained (conditional calculation) Follows from s 396-105(6); Australian application provisions to be confirmed

Where the obligation sits: Subdivision 396-C of the TAA

The Tax Laws Amendment (Implementation of the Common Reporting Standard) Act 2016 received royal assent on 18 March 2016 and inserted Subdivision 396-C into Schedule 1 to the Taxation Administration Act 1953 (TAA). The ATO records that the CRS legislation came into effect on 1 July 2017 and that Australia’s first exchange of information took place in 2018. The compilation of the TAA dated 1 October 2026 lists nine sections in Subdivision 396-C, from 396-100 to 396-136, covering statements, the meaning of CRS, domestic choices, application, record keeping, anti-avoidance, false self-certifications and the Commissioner’s annual report.

Section 396-105(1) sets three conditions, each tested against a calendar year. At some point in the year the entity is a Reporting Financial Institution within the meaning of the CRS (or has been told by a section 396-130(5) notice to act as one); at that time it is resident in Australia or is a branch located in Australia; and at some point during the year it maintains either a Reportable Account within the meaning of the CRS or an account that a notice under section 396-130 requires it to treat as a Reportable Account. When all three are met, the entity gives the Commissioner a statement with the information the CRS requires about each such account. Reportability is decided by applying the CRS due diligence procedures (s 396-105(3)), the statement is in the approved form (s 396-105(4)), and it is due no later than the first 31 July after the end of the calendar year (s 396-105(6)). The ATO describes the approved form as the CRS XML Schema format.

Section 396-110 then defines the CRS by reference to Part II.B of the OECD Standard for Automatic Exchange of Financial Account Information in Tax Matters, approved on 15 July 2014, applied consistently with the OECD Commentary. That is why most CRS definitions an Australian reporting team works with are OECD text, and why the ATO’s specification is only one of the four layers.

Australia also adopted what the OECD calls the wider approach. In the CRS text, a Reportable Jurisdiction is one with which an exchange agreement is in place and which appears on a published list. Section 396-120(3) instead treats every jurisdiction other than Australia as a Reportable Jurisdiction. The ATO’s FATCA guidance draws the operational consequence: US account holders must be reported in both the FATCA report and the CRS report.

Australian reporting financial institutions submit a separate FATCA XML report to the ATO, which forwards the information to the US IRS. Although the Australian FATCA reporting format uses IRS Form 8966-related XML standards, Australian institutions follow the ATO’s lodgment procedures rather than directly filing through the US IRS channel. The applicable US account holders must also be included in the Australian CRS report under Australia’s wider approach.

Who reports, which accounts and which data items all come from the statute and the CRS it incorporates. A new release of the ATO specification changes the checks a file has to pass on the way in.

Which institutions lodge, and the settings Australia chose

The CRS recognises four kinds of Financial Institution: Custodial Institutions, Depository Institutions, Investment Entities and Specified Insurance Companies. The categories carry their own tests. A Custodial Institution, for example, holds financial assets for the account of others as a substantial portion of its business, which the CRS measures as gross income from holding financial assets and related services equal to or above 20% of total gross income over the shorter of the prior three-year period or the entity’s life. A Financial Institution that is a Non-Reporting Financial Institution, under the CRS or section 396-115, has no statement to give.

Section 396-115 fills the gaps the CRS leaves to domestic law. Section 396-115 identifies specified government entities, international organisations, central banks and qualifying retirement funds listed in Annex II of the Australia-US FATCA agreement as Non-Reporting Financial Institutions, subject to the statutory conditions and exceptions.

Australian law expressly excludes self-managed superannuation funds and small superannuation funds from the domestic Non-Reporting Financial Institution category in section 396-115(1)(a). Their accounts are instead addressed separately as Excluded Accounts under section 396-115(3)(aa) and (ab). Other qualifying Annex II accounts and categories prescribed by legislative instrument may also be Excluded Accounts. Where the CRS lets a jurisdiction give institutions an election, section 396-115(4) assumes the Australian entity may make it.

Three Australian settings change the reporting answer in edge cases:

  • Pre-existing accounts are measured against 30 June 2017 (s 396-120(6)), and a New Account is any financial account that is not a Preexisting Account (s 396-120(7)). The first reporting period ran from 1 July to 31 December 2017.
  • An entity may choose to treat all dollar amounts in the CRS as Australian dollars (s 396-120(8)); without that choice, the amounts are US dollars.
  • A statement is only required for a year in which the institution maintains a Reportable Account. The ATO says there is no requirement to lodge a nil CRS report, though lodging one helps it monitor compliance and may reduce queries.

Trusts need care. Under the CRS, a trust can be a Non-Reporting Financial Institution to the extent its trustee is a Reporting Financial Institution and reports everything required for all the trust’s Reportable Accounts. Where the trust itself is the Reporting Financial Institution, the ATO requires the ReportingFI element to carry the trust’s name, address and tax identifier (TFN or ABN) and gives its reason: that is what records the lodgment against the trust itself.

What the ATO CRS 2021 specification package contains

The ATO’s CRS overview page sends digital service providers to the Common Reporting Standard page on its Software Developers site for “the CRS XML schema and technical updates”, and its lodgment page refers reporters to the CRS specifications for the meaning of validation errors. The 2021 specification belongs to the ATO service named CRS.0002 2021, and the Software Developers site lists releases of it including v1.1, v1.2, v1.3 and v1.4.

The ATO’s package content note for its 2027 CRS service describes how these packages work. Its audience is software developers building the CRS service on the ATO’s Bulk Data Exchange platform. All the message artefacts that make up the CRS suite sit in one zip file, and the package is “versioned up each time artefacts are added or updated”. Depending on the service, a package can include message structure tables, contract schemas and samples, rule implementation code (C# or Schematron) and a validation rules workbook. For CRS, the note lists the OECD CRS XML Schema and user guide as an external artefact available from the OECD website, bundles the schema files, and adds the ATO’s own contribution: validation rules numbered VR.ATO.CRS.000xxx.

Read that way, the operative parts of the specification for a reporting financial institution are the validation rules workbook and the package contents note that says which rules changed. A file mapped only to the OECD user guide can be schema-valid and still fail ATO-specific checks, because those checks live in the ATO workbook and on its lodgment page.

Version numbers count releases of the ATO package, and the schema generation is tracked separately, by service. The draft package for the next service, CRS.0003 2027, describes its rules as new rules added “in addition to the existing CRSv2.0 validation rules”. That places every release of the 2021 specification, v1.1 to v1.4, on schema v2.0, and the “2021” in the service name is read here as the year the ATO began requiring schema v2.0 (1 January 2021). A team that last mapped its checks against v1.1 is several releases behind on the same service, and the move to schema v3.0 happens through a different service altogether.

Building the file: ATO rules on top of schema v2.0

From 1 January 2021 the ATO has required CRS reports to be created with version 2.0 of the CRS XML Schema and version 3.0 of the OECD user guide. The ATO lists the changes v2.0 brought: a mandatory schema version attribute; a mandatory message type indicator; a one-character minimum for all string elements (validation elements always need a value, and an empty optional element is omitted); length limits on some strings; fractions of seconds allowed in the timestamp; no controlling person information when the account holder is an individual; and an updated ISO country list.

The ATO then adds its own requirements for compatibility with its systems. The rules below come from the July 2024 version of the ATO’s CRS reporting page; the ATO updated that page again on 6 October 2026 for schema v3.0, so the current version is the one to check for any change.

Topic ATO requirement
MessageRefID and DocRefID Format AU + reporting year + AU + Sending Company IN + unique reference; unique in space and time
Reporting year in the ID The year the data relates to, for example 2017 for a period ending 31 December 2017
Sending Company IN ABN, GIIN or TFN, in that order of preference; Sending Company IN and Reporting FI elements must be identical in the report
Entities per file One reporting entity per report, containing all of that entity’s reportable accounts
Trust as Reporting FI The trust’s own name, address and TFN or ABN, in place of the trustee’s
Nil report (optional) Built to the CRS XML schema or generated by the Small Reporter Tool; MessageTypeIndic CRS703 when produced from internal software

Corrections follow the OECD design. Each record carries a DocTypeIndic: OECD1 for new data, OECD2 for corrected data, OECD3 for deletion, and OECD0 for resent data, which is only used to resend the Reporting FI element when a correction targets an account report alone. The OECD user guide says a message should contain either new records or corrections and deletions, but not a mixture. A CorrDocRefID always points at the latest DocRefID sent for that record, so a second correction to the same account report references the DocRefID of the first correction.

Validation report, status message and the codes that reject a file

The ATO checks CRS lodgments in two stages. The validation report comes first and says whether the ATO successfully received the lodgment against its CRS-specific requirements. An unsuccessful report means the file is corrected and relodged. A successful one means the file has moved into the ATO’s internal processing, and the reporter then waits for a status message. Since September 2024, lodgments that pass validation generally receive that status message at the point of lodgment within 24 to 72 hours.

The status message carries one of two outcomes, Accepted or Rejected, with labels for the OriginalMessageRefID, each error Code and the DocRefIDInError. The ATO marks the codes that force rejection with an (R). The others can still appear in an Accepted status message.

Code Trigger, per the ATO table Outcome
50009 MessageRefID is not unique Rejected
60014 Date of birth outside a valid range, for example before 1900 or after the current year Rejected
80000 DocRefID already used for another record Rejected
80002 / 80003 CorrDocRefID unknown, or already invalidated by a previous correction Rejected
80004 CorrDocRefID used on a new data record (OECD1) Rejected
80009 Reporting FI deleted before all its account reports are deleted Rejected
80012 One message holds data for two reporting periods Rejected
60002 / 60003 Negative account balance; non-zero balance on an account flagged as closed Error in an Accepted message
60005 / 60006 / 60016 Controlling Person present or missing against the account holder type, or present for an individual Error in an Accepted message

The ATO states that a lodgment can be Accepted with errors. No further action is required for that lodgment, and the ATO suggests using the listed errors to improve future reporting. Acceptance also leaves the file open to questions. The ATO warns that a successful lodgment may still lead to follow-up enquiries driven by feedback from partner jurisdictions, which it tries to bundle, and advises reporters not to archive CRS lodgment data for at least 12 months from the lodgment due date.

Lodging, testing and asking for more time

A CRS report can be lodged through Online services for agents, Online services for business, or CRS-enabled business or accounting software. A team producing its XML in-house can lodge a test file through either online service by selecting the test lodgment type, and receives a validation report to review. Digital service providers use a separate test environment, which needs registration with the ATO’s Digital Partnership Office.

Small reporters have another route. The ATO’s CRS Small Reporter Tool lets a reporting financial institution with fewer than 50 reportable accounts complete an Excel spreadsheet that converts the data to the required XML, which is then lodged through the online services. It can also generate a nil report. The July 2024 version of the ATO’s CRS reporting page requires version 2.0 of the tool, earlier versions having stopped being accepted from 1 January 2021.

An extension of time is requested through the mail function in Online services for agents or Online services for business, under the topic Lodge report and the subject Common Reporting Standard (CRS) extension of time. The request names the institution’s ABN, TFN or GIIN, the institution, a contact and daytime phone number, the reasons, and the date by which the report will be lodged.

A FATCA extension does not carry over to CRS. When the ATO moved the 2020 FATCA reporting deadline to 31 August 2021 to give reporters time to obtain missing US TINs, it stated that the extension did not apply to CRS reports.

Two record clocks also run in parallel. The 12-month archive advice above is about keeping lodgment data at hand for enquiries. The statutory duty in section 396-125 is longer: written records that correctly record the procedures by which the institution determines whether it maintains a Reportable Account and what information its statement must contain, kept in English or in a form readily convertible to English, for five years after the statement is given, or, where no statement was required, until 31 July in the sixth year after the end of the year.

Due diligence and the ATO’s AEOI review

Every reportability decision in the file traces back to the CRS due diligence procedures, and the Act attaches a penalty to one part of them. Section 288-85 makes a Reporting Financial Institution liable to an administrative penalty of one penalty unit if it is required to obtain a self-certification when applying the CRS due diligence procedures and fails to obtain it by the time the statement for that account is due (or would be due, if the account were reportable). Section 396-135 separately applies the penalty regime to false or misleading self-certifications.

The anti-avoidance rule in section 396-130 runs the other way. Under section 396-130, the Commissioner may require an institution to treat an account as reportable where the Commissioner reasonably believes that a relevant transaction or arrangement was undertaken by the Reporting Financial Institution, the Account Holder, an intermediary of either, or another entity for the purpose, or dominant purpose, of preventing the account from being a Reportable Account. A notice under section 396-130(5) can also require a Financial Institution to act as a Reporting Financial Institution.

Two ATO recommendations sit on top of the statute. It asks reporting financial institutions to use the European Commission’s TIN online check module to verify the structure of foreign TINs issued by most European countries, and to consider the OECD’s analysis of residence and citizenship by investment schemes when a customer’s stated tax residence may rest on one of them.

The ATO’s CRS and FATCA self-review guide shows how it tests all this. An AEOI review looks for objective evidence across three core elements: AEOI governance, due diligence obligations and reporting systems. The ATO rates a framework as operating as required, operating in part (requires improvement), or not operating as required or not in place. Where a review finds no major deficiencies, the ATO intends to start the next one periodically, at least once every four years, and expects reporters in the intervening period to monitor their framework and act on major reporting errors through remediation plans, amended reports or both.

The output also has a public life. Section 396-136 requires the Commissioner to report to the Minister by 31 December of the following year on Reportable Accounts maintained by Australian institutions, for each reportable jurisdiction with six or more accounts, and the report is tabled in Parliament.

Schema v3.0 and the ATO CRS.0003 2027 package

The ATO has since released newer draft packages for the CRS.0003 2027 service. The current published draft is specification v0.3, issued in October 2026, following v0.1 in August and v0.2 in September. The ATO’s package contents note for v0.1 (13 August 2026) describes the draft release for the external vendor test environment: it supports version 3.0 of the OECD CRS XML Schema and identifies ten new validation rules in addition to the existing v2.0 rules: VR.ATO.CRS.000319 to VR.ATO.CRS.000326, VR.ATO.CRS.000329 and VR.ATO.CRS.000330. The v0.1 note gives no production date for these ten rules; 1 January 2027 is the date the ATO’s schema v3.0 guidance, as reported by KPMG and Allens, sets for schema v3.0 to take effect for ATO lodgments.

Reporting teams should build and test against the latest v0.3 package rather than treating the original v0.1 workbook as the operative draft. Any additional rules affecting the DDProcedure element must be verified against the current package and subsequent ATO publications before being incorporated into production controls.

The timing has since firmed up. KPMG reports that an ATO circular, dated 2 October 2026 in that report, set 1 January 2027 as the date schema v3.0 becomes effective, set the lodgment pause shown in the dates table, and pointed to the external vendor test environment and updated specifications on the Software Developers CRS page.

The ATO identifies 31 July 2027 as the statutory due date for the 2026 CRS reporting year. That date falls on a Saturday. Under Schedule 1, section 388-52 of the Taxation Administration Act 1953, an approved form due on a non-business day may be lodged on the next business day. Because Monday 2 August 2027 is a public holiday throughout the Northern Territory, the resulting permitted lodgment date is Tuesday 3 August 2027. This is a statutory next-business-day conclusion, rather than a separately announced ATO extension.

Allens, citing the ATO’s CRS reporting page as updated on 6 October 2026, adds that for reports due by 31 July 2027 reporting financial institutions may report the new data elements, use transitional “not reported” codes, or combine the two.

The “not reported” values come from the OECD schema itself. OECD CRS XML Schema v3.0 provides transitional values CRS900 for Account Holder self-certification status, CRS1000 for Controlling Person self-certification status, CRS1100 for Account Type, CRS1200 for Pre-existing Account or New Account, and CRS800 for Controlling Person type. For the 2026 reporting-year file lodged under schema v3.0, the ATO requires the new mandatory data elements either to be populated or to carry the applicable transitional codes. The ATO also instructs reporters not to use Account Number Type OECD606 (Specified Electronic Money Product) at this stage. Where the actual Account Type is supplied rather than CRS1100, additional ATO validations require consistency between Account Type, Account Number Type, Equity Interest Type and Payment Type.

The schema annotates each of the transitional values as a transitional measure for interoperability with the previous version, “particularly in respect of corrections”. Poland’s national schema shows the same elements arriving through a domestic form, as covered in our CRS-1(4) schema article.

The legal timing matters here. The 31 July 2027 file normally carries 2026 data, collected under the CRS as Australian law currently defines it, while the v3.0 schema has room for data points that current Australian law does not yet require. The ATO’s permission to use the transitional “not reported” codes for that file fits this timing, and the DDProcedure rules the August note held back pending legislation point the same way.

Treasury’s exposure draft: amended CRS rules from the 2027 calendar year

On 15 October 2026 Treasury opened consultation on “Crypto asset tax transparency: draft legislation”, closing on 28 October 2026. The exposure draft, Treasury Laws Amendment Bill 2026: Tax Information Reporting, delivers a 2025-26 Mid-Year Economic and Fiscal Outlook measure. It would create a framework for the OECD Crypto-Asset Reporting Framework in a new Subdivision 396-D, introduce a domestic crypto reporting regime, and amend Subdivision 396-C. It is a draft. Nothing below applies until Parliament passes the bill.

Treasury confirms that its October 2026 exposure draft proposes to update Australia’s implementation of the CRS. The following points describe changes contained in the OECD’s amended CRS and their proposed relevance to Australian reporting. The precise Australian legislative provisions, exceptions, commencement arrangements and reporting application dates remain subject to confirmation against the draft legislation and any subsequently enacted instruments.

  • The OECD’s 2023 publication contains amendments to the CRS Rules and Commentary. Treasury’s October 2026 consultation proposes to update Australia’s CRS implementation, but the precise legislative incorporation provision and commencement arrangements remain subject to confirmation against the exposure draft and final legislation. The existing Australian annual lodgment deadline is established by section 396-105(6).
  • Scope would widen to Specified Electronic Money Products and central bank digital currencies, through broader Depository Institution and Depository Account definitions, and to financial assets that reference Relevant Crypto-Assets, such as crypto derivatives. The proposed amended CRS includes an exclusion for qualifying low-value electronic money products. The precise threshold, averaging methodology and Australian application conditions need to be checked against Treasury’s draft legislation and explanatory materials before being incorporated into reporting controls.
  • Reporting financial institutions would report whether a valid self-certification was obtained, whether the account is pre-existing or new, the account type, whether the account is jointly held and the number of joint holders, and the role in which a person is a Controlling Person or Equity Interest Holder.
  • Holders resident in more than one jurisdiction would generally have every jurisdiction of residence reported, without reliance on treaty tie-breaker rules.
  • Scholarship plans would cease to be Excluded Accounts, following the 2024 OECD peer review assessment that they do not meet the excluded-account conditions.
  • An optional Non-Reporting Financial Institution category would cover Investment Entities that are genuine non-profit organisations.

The self-certification penalty would also widen. The one-penalty-unit penalty in section 288-85 would cover failures to obtain a self-certification, to validate it (including confirming its reasonableness), or to act on a change in circumstances that makes a self-certification or other information incorrect or unreliable, within the time the CRS requires; the specific remediation period depends on the amended CRS due diligence requirements and their final application in Australian law. The exposure draft proposes to extend the self-certification penalty to additional due diligence failures. The precise commencement and application provisions must be confirmed against the draft legislative text and any subsequently enacted Act before they are used to establish compliance deadlines.

If the amended CRS applies from the 2027 calendar year and the existing statutory annual deadline is retained, the first statement for that period would ordinarily be due by 31 July 2028 under section 396-105(6). This remains a conditional calculation pending confirmation of the Australian commencement and application provisions. The CARF side runs in parallel, with proposed commencement in 2027 and first international exchanges in 2028, as distinct from the parallel domestic crypto reporting regime for which the government envisages first reports to the ATO in 2028, and is covered in our CARF crypto tax reporting guide. Whether, and from when, the amended CRS applies in Australia is the open question.

Frequently Asked Questions

Our only foreign-resident customer closed their account in March. Is there anything to report for that year?

The trigger in section 396-105(1)(c) is maintaining a Reportable Account at any time in the calendar year, so an account closed part-way through the year can still put the institution in scope for that year. The schema carries an account-closed attribute, and the ATO’s status-message rules expect an account flagged as closed to show a zero balance (error 60003). Whether a particular closed account is reportable still turns on the due diligence outcome for that account.

Can several funds with the same trustee go in one XML file?

Each file covers one reporting entity. The ATO limits each CRS report to a single reporting entity, and where the Reporting Financial Institution is a trust, the ReportingFI element carries that trust’s name, address and TFN or ABN. Each trust that is itself a Reporting Financial Institution therefore needs its own file, even where one trustee prepares all of them.

A lodged record shows the wrong country of residence. Can it be fixed with an OECD2 correction?

The ATO’s status-message table says the ResCountryCode cannot be corrected. Where that element must change, the record is deleted with an OECD3 file and then lodged again as new data with OECD1. A correction file that tries to change it directly returns a rejection code.

We need to correct a 2025 report after 1 January 2027. Which schema applies?

From 1 January 2027, the ATO will reject CRS submissions using XML Schema v2.0. Its published hard-cutover rule does not specify an exception for corrections relating to earlier reporting years. A correction to a 2025 report submitted after that date must therefore use schema v3.0. The OECD user guide for schema v3.0 (version 4.0, October 2024) sets out the correction procedures and the transitional “not reported” values intended to support interoperability with earlier submissions, but the ATO’s express permission to use transitional codes is framed around reports due by 31 July 2027. Before lodging a correction relating to an earlier year, confirm the ATO’s applicable transitional-code treatment and validate the file against the current CRS.0003 specification.

Does the Australian-dollar election under section 396-120(8) change what we report?

The election changes the currency in which the CRS’s dollar amounts are read, so the thresholds in the due diligence procedures are applied in Australian dollars instead of US dollars. Section 396-120(8) frames it as a choice to treat all dollar amounts in the CRS as Australian dollars, wording that points to applying the choice across the board once made.

We obtained an extension for our FATCA report. Do we need a separate one for CRS?

Yes. CRS extensions are requested through the CRS-specific subject in the online services mail function. The ATO’s 2021 FATCA extension, which moved 2020-year FATCA reports to 31 August 2021, expressly did not apply to CRS reports, and the ATO’s CRS reporting page sets out its own extension route.

Key Takeaways

  • The v0.1 package contents note for CRS.0003 2027 keeps the existing v2.0 validation rules and adds ten more, so a schema v3.0 build inherits the current ATO rule set and extends it; the later v0.3 workbook can add or change rules, so test against the latest draft in the external vendor test environment and re-read its rule list before fixing controls.
  • For the file due 31 July 2027, record a field-by-field decision on each v3.0 element that has a transitional “not reported” value (the Account Holder and Controlling Person self-certification flags, Controlling Person type, account type and DDProcedure): populate it, or report that value.
  • Set retention for the written records of how the institution identifies Reportable Accounts and determines the statement information to five years after the statement is given (s 396-125); the 12-month ATO advice only covers keeping lodgment data at hand for partner-jurisdiction enquiries.
  • A missed self-certification costs one penalty unit under section 288-85 today; the exposure draft would extend that penalty to validation and change-in-circumstances follow-up, subject to the applicable amended CRS deadlines and Australian transitional provisions.
  • Prepare AEOI review evidence across governance, due diligence and reporting systems; with no major deficiencies, the ATO intends the next review at least once every four years.
  • Subject to Australian enactment and commencement, the OECD’s amended CRS would broaden reporting coverage for specified electronic money products, central bank digital currencies and crypto-linked financial products. The proposed domestic treatment of scholarship plans must also be confirmed before account classifications and due diligence controls are changed.

Sources and References

Before the ATO’s requested CRS submission pause on 15 December 2026

The ATO has requested that reporting financial institutions refrain from submitting CRS files between 15 December 2026 and 15 January 2027 while it deploys system updates. Its published wording is a request not to submit, rather than confirmation that the lodgment channel will be technically unavailable throughout that period. Separately, schema v2.0 files will be rejected from the hard cutover on 1 January 2027. The artefact to have ready well before the 31 July 2027 due date is a schema v3.0 file for the 2026 calendar year that has passed the draft CRS.0003 2027 rules in the external vendor test environment, with any DDProcedure rules tracked against the current package and the progress of the Treasury bill.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts