From 1 January 2021, CRS reports must be created using the V2.0 CRS XML Schema and V3.0 of the guidance material.
The changes to V2.0 of the CRS XML Schema are:
- There is a mandatory schema version attribute.
- The message type indicator is a validation element and is mandatory.
- The minimum length of all string elements is one character
- for a validation element, a value must always be provided.
- for an optional element, if there is no value, the element should be omitted.
- The length of some string elements is limited – refer to the user guide.
- The use of fractions of seconds is allowed in the timestamp element.
- Controlling person information is not to be provided when the account holder is an Individual.
- The ISO code country list has been updated.
The CRS XML Schema and associated user guides are available on the OECD websiteExternal Link.
Additional requirements for CRS XML files
For compatibility with our systems, we have introduced some additional requirements for CRS XML files.
MessageRefID and DocRefID elements
In order to pass validation, all XML Schema files must contain MessageRefID and DocRefID elements with the following format:
The components of the above format are:
- Sending Country Code – must be, AU
- Reporting Year (the year in which the data relates) – for example, 2017 for a report period ending 2017-12-31
- Receiving Country Code – must be, AU
- Sending Company IN – (in order of preference), ABN, GIIN or TFN
- A unique string of characters the reporter can use to make the file unique – for example, UniqueReference.
The MessageRefID and DocRefID must be unique in space and time.
The Sending Company IN and Reporting FI elements must be identical in the report.
One CRS report per reporting entity
The lodgment of CRS reports will be limited to one reporting entity per report. The report should contain all the entity's reportable accounts.
Reporting details for trusts
If the reporting financial institution (RFI) is a trust the ReportingFI element must contain the details of the trust including the trust name, address and TIN (TFN or ABN) as opposed to the trustee. This ensures that the record of lodgment is correctly recorded against the trust.
Previous updates to CRS reporting requirements
For information on past CRS reporting updates see CRS for reporters and digital service providersExternal Link.
There is no requirement for RFIs to lodge a nil CRS report. However, lodging a nil report will help us monitor CRS compliance and may reduce the need for queries.
- Create and lodge a nil report as per the CRS XML schema user guideExternal Link.
- Generate a nil report using our Small Reporter Tool version 2.0 This link will download a file
Note: If you are generating a nil report from internal software ensure you use CRS703 in the MessageTypeIndic field.
If you are producing a CRS XML file in-house you can lodge a test file via Online services for agents or Online services for business. Ensure you select the lodgment type as a test and a validation report will be produced for your review.
We have a test environment available for digital service providers to test their software. The test environment can be accessed via the test facilityExternal Link. Developers will need to register with the Digital Partnership Office (DPO) to gain access to the test environment.
If you encounter any issues with registration or the test environment:
- email ATOBulkDataTransfer@ato.gov.au
- phone us on (02) 6216 4004.
We have developed a CRS Small Reporter Tool (SRT) to allow small RFIs with less than 50 reportable accounts to download and complete an Excel spreadsheet.
The spreadsheet will convert the information into the required XML Schema format.
This can then be lodged through Online services for agents or Online services for business. A nil report can also be generated if the RFI has no reportable accounts.
Ensure you download CRS SRT version 2.0 as previous versions are no longer accepted as of 1 January 2021.
Note: Ensure you have read the user guide before using the SRT.
Reports from Australian RFIs include data from January to December and are due annually, by 31 July in the following year.
If you are unable to lodge your CRS report by 31 July, you can request an extension of time using the mail option in Online services for agents or Online services for business. To apply select:
- a new message
- the topic Lodge report
- the subject Common Reporting Standard (CRS) extension of time.
The message should include:
- the ABN, TFN or GIIN of the RFI
- the name of the RFI
- your name and daytime phone number
- the reasons for the request to extend time to lodge
- the date by which you will be able to lodge the CRS report.
You can lodge your CRS report online through any of the following:
- Online services for agents
- Online services for business
- CRS enabled business or accounting software.
Log in to Online services for business
Validation of CRS reports is a three step process. A successful online lodgment may still result in follow up enquiries.
Following lodgment, further validation checks on CRS reports will be conducted in our data hub and by our international partner jurisdictions.
We will attempt to bundle together enquiries from all our international partners, however, some may still occur on an ad hoc basis.
We advise reporters not to archive CRS lodgment data for at least 12 months from the lodgment due date.
You can subscribe to our digital service providers news services to receive the latest CRS information through newsletters, alerts and emails.
If you have any further questions about the CRS, contact the CRS project team.
- Common Reporting Standard for the automatic exchange of financial account information
- Automatic exchange of information guidance – CRS and FATCA
- OECD's Automatic Exchange PortalExternal Link
- The OECD's Standard for Automatic Exchange of Financial Account Information in Tax MattersExternal Link
- The OECD's CRS Implementation HandbookExternal Link
- Australian domestic reporting system (PDF, 340KB)This link will download a file
- Common Reporting Standard (CRS)External Link on our Software developers website