Preparing the CRS report
XML Schema
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've 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 format
AUReportingYearAUSendingCompanyINUniqueReference.
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 Tax Identification Number (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.
Nil reports
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.
You can also:
- 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.0This link will download a file.
Note: If you're generating a nil report from internal software, ensure you use CRS703 in the MessageTypeIndic field.
Testing
If you're 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.
CRS Small Reporter Tool
We've 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.0This link will download a file as previous versions are no longer accepted as of 1 January 2021.
Note: Ensure you have read the user guide before using the SRT.
Due date for the CRS report
Reports from Australian RFIs include data from January to December and are due annually, by 31 July in the following year.
Applying for an extension of time
If you're 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.
How to lodge
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 lodgments
CRS lodgments are checked for validity in 2 stages. Use the following steps to confirm the successful outcome of your CRS report.
Checking for a successful CRS lodgment
What is the outcome of your Validation Report?
- Unsuccessful – Correct the file and relodge.
- Successful – Await the receipt of a status message, then read on.
What is the result of your Status Message?
- Accepted – No further action is required.
- Rejected – Check the errors in the following table. Correct the errors and relodge.
Validation report
Once submitted, your lodgment will be checked to ensure the file meets the CRS specific requirements. You'll receive a Validation report which will indicate whether we have successfully or unsuccessfully received your lodgment.
If your lodgment is unsuccessful you'll need to address the errors detailed in the report and relodge. For further information onvalidation errors, see the CRS SpecificationsExternal Link.
If your lodgment is successful it means we have received your lodgment and it will progress to internal processing systems.
Status message
From September 2024, all lodgments that pass validation will generally receive a status message back to the point of lodgment, within 24 to 72 hours of lodgment.
A status message will have 2 possible status outcomes:
- Accepted – No further action is required.
- Rejected – You must correct the errors detailed and resubmit your file. Each error is defined by error code and your status will include a reference to the DocRefID that has triggered the error.
Note: A lodgment can be 'Accepted' with errors. In this case, no further action is required, however the errors detailed can be used to improve future reporting.
Labels of note in the status message include:
- OriginalMessageRefID – Reference to the original lodgment.
- Code – Error code.
- DocRefIDInError – DocrefID of the record containing the error.
- Status – Outcome of the lodgment
CRS status message errors
Your status message may contain error codes. If your lodgment has a 'Rejected' status you will be required to correct the errors and relodge your file. Not all error codes will result in a 'Rejected' status.
The following table contains a description of each status error code. Error codes denoted with (R) will result in a rejected lodgment outcome.
Error code | Description |
|---|---|
50009 (R) | Replace the MessageRefID field value with a unique value and relodge the file. |
60000 | The Account Number must follow the IBAN structured number format when the Account Number type = OECD601 – IBAN |
60001 | The Account Number must follow the ISIN structured number format when the Account Number type = OECD603 – ISIN. |
60002 | The account balance entered was less than zero. This amount must be greater than or equal to zero. |
60003 | The Account Balance must be zero if the account was indicated as closed in the account closed attribute. |
60005 | When the Account Holder is an Organisation and the 'Account Holder Type' is CRS102 or CRS103, the 'Controlling Person' must be omitted. |
60006 | When the Account Holder is an Organisation and the 'Account Holder Type' is CRS101, the 'Controlling Person' must be provided. |
60014 (R) | Date of birth must be in a valid range (for example, not before 1900 and not after the current year). Please correct and relodge the file. |
60015 | AccountReport should only be omitted if ReportingFI is being corrected or deleted, or if there is nil reporting. If the ReportingFI indicates new data (OECD1) or resent (OECD2), then AccountReport should be provided. |
60016 | When the Account Holder is an individual, the 'Controlling Person' must be omitted. |
80000 (R) | The DocRefID is already used for another record. Replace the DocRefID with a unique value and relodge. |
80002 (R) | CorrDocRefID is unknown. Replace with the successfully lodged DocRefID that requires correcting and relodge the file. |
80003 (R) | The CorrDocRefID is no longer valid as it has been invalidated or outdated by a previous correction message. You need to correct and relodge the file. |
80004 (R) | CorrDocRefID must not be used for new data records (OECD1). You need to correct and relodge the file. |
80009 (R) | The Reporting FI cannot be deleted without first deleting all related Account Reports. You need to correct and relodge the file. |
80012 (R) | A message must not contain data for 2 different Reporting Periods. You need to correct and relodge the file. |
80013 (R) | An unknown DocRefID was specified for the Resend option (OECD0). You need to correct and relodge the file. |
80014 (R) | The DocRefID specified for the Resend option (OECD0) is no longer valid as it has been invalidated or outdated by a previous correction message. You need to correct and relodge the file. |
9999 (R) | The ResCountryCode cannot be corrected. If this element must be changed, a deletion file (OECD3) must be lodged followed by a new data file (OECD1). |
For further information on error codes, see the OECD Status Message GuideThis link will download a file.
Enquiries after lodgment
A successful online lodgment may still result in follow up enquiries based on feedback from 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.
CRS news and information
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.
You can refer to the below links for further information:
- Common Reporting Standard for the automatic exchange of financial account information
- Automatic exchange of information guidance – CRS and FATCA
- 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