One or more attachments are not properly encoded.

Check that all attachments are properly encoded and re-submit.

One or more attachments are corrupt.

Check that all attachments are not corrupt and re-submit.

One or more attachments are not in the accepted format.

Check that any attachments are in the accepted format. The accepted attachment formats are:

• DOC
• DOCX
• Office Open XML
• XLS
• XLSX
• PDF
• ODT
• ODS.

One or more attachments do not contain acceptable filenames.

Check that any attachment filenames:

• are unique
• do not exceed 255 characters
• do not contain invalid characters (<, >, :, ", /, \, |, ?, *).

One or more attachments contain embedded documents.

Check attachments and ensure embedded documents are not included in any attachments.

The embedded documents can be submitted as separate attachments in the lodgment.

The lodgment contains character sets that do not follow UTF-8 character encoding.

Check your lodgment and ensure it does not include any non UTF-8 characters.

The name/ABN/TFN of the Reporting entity do not match the details in our systems.

Check the details in the following fields:

• LCMSF8 (Reporting entity name)
• LCMSF7 (Reporting entity ABN)
• LCMSF65 (Reporting entity TFN).

The lodgment has been received from a subsidiary member of an income tax consolidated group or multiple entry consolidated group.

(Note: This error will not apply if an entity has been a standalone entity for part of the year.)

Check reporting entity details to ensure the lodgment is being made by the head entity of the income tax consolidated group or multiple entry consolidated group.

The reporting period start date and end date for the local file do not align with the reporting period of your income tax return.

Check the reporting period start date (LCMSF142) and end date (LCMSF143) align with your income tax reporting period.

Note: A 12-month reporting period is required to be used even if the local file covers a stub period. For example, a December balancer that joined an income tax consolidated group on 1 July 2019 should lodge the local file with the reporting period being 1 January 2019 to 31 December 2019.

An incorrect ABN/TFN has been provided for the entity that is lodging the master file on your behalf.

Check the details of the entity that is lodging the master file in the fields LCMSF19 and/or LCMSF20.

An incorrect ABN/TFN has been provided for the entity that is lodging the CbC report or CbC report notification on your behalf.

Check the details of the entity that is lodging the CbC report or CbC report notification in the fields LCMSF72 and/or LCMSF73.

An incorrect ABN/TFN has been provided for one or more entities that you are lodging the master file and/or CbC report Notification on behalf of.

Check the details in the fields:

• LCMSF77 and/or LCMSF78 (for master file)
• LCMSF115 and/or LCMSF116 (for the CbC report notification).

The name/ABN/TFN of the Reporting Entity do not match the details in our systems.

Check the Reporting Entity name and tax identification number (TIN) (for example, ABN or TFN) details.

File Contains Test Data for Production Environment.

Check that the lodgment does not contain any DocTypeIndic values in the range OECD11–OECD13.

Note: Further information is available in the CBC reporting status message XML schema: user guideExternal Link.

File Contains Production Data for Test Environment.

Check that the lodgment, intended to be received in a test environment, only contains DocTypeIndic values in the range of OECD11–OECD13.

Note: Further information is available in the CBC reporting status message XML schema: user guideExternal Link.

A DocRefID has been used for more than one record.

Check that each DocRefID is only used once in the lodgment.

The structure of one or more DocRefIDs is not in the correct format, as set out in the CBC reporting XML schema: user guideExternal Link.

Check the structure of all DocRefIDs are in the correct format, as set out in the CBC reporting XML schema: user guideExternal Link.

One or more CorrDocRefIDs refers to an unknown record.

Check that any CorrDocRefID values used in the lodgment have corresponding previously lodged DocRefID values.

The corrected record is no longer valid (invalidated or outdated by a previous correction message).

Check that the corrected DocRefID value is referencing the latest DocRefID for the data to be corrected.

A CorrDocRefID has been specified for one or more new elements.

If a message contains a new element, check that a CorrDocRefID has not been specified for the new element.

A CorrDocRefID has not been specified for one or more corrected elements.

If a message contains corrections, check that a CorrDocRefID has been specified for each correction.

A CorrMessageRefID has been used in the DocSpec_Type.

Check there is no CorrMessageRefID in the DocSpec_Type element. This data element is not used for CBC reporting.

A CorrMessageRefID has been used in the Message Header.

Check there is no CorrMessageRefID in the Message Header element. This data element is not used for CBC reporting.

The resend option (OECD0) has not been used for the Reporting Entity element.

If using the resend option (OCED0), check that this is only being used for the Reporting Entity element.

A deletion has been received for the Reporting Entity, however the deletion does not include all related CbCReports and AdditionalInfo.

If a lodgment contains a deletion for a Reporting Entity, check the deletion also includes all related CbCReports and AdditionalInfo.

The lodgment contains a mixture of new records (OECD1) and corrections (OECD2) and/or deletions (OECD3).

Check that new records (OECD1) and corrections or deletions (or both) (OECD2 or OECD3) are not contained in the same lodgment.

One or more DocRefIDs has been corrected or deleted twice in the same lodgment.

Check that a DocRefID has not been used more than once in the same lodgment.

An unknown DocRefID was specified for the resend option (OECD0).

If using the resend option (OCED0), check the details of the DocRefID and ensure that it is correct.

The DocRefID specified for the resend option (OECD0) is no longer valid (invalidated or outdated by a previous correction message).

If using the resend option (OCED0), check the details of the DocRefID and ensure that the latest, non-corrected DocRefID is used.

An incorrect name/ABN/TFN has been provided for one or more Australian constituent entities listed in your CbC report.

Check the name and tax identification number (TIN) details for the Australian constituent entities.

Note: Please provide a valid ABN or TFN with no space for the TIN.

Invalid MessageRefID format

Check MessageRefID format. Format will depend on the schema version being used.

MessageRefID has already been used

Check if the MessageRefID has already been used.

Channels: The ReceivingCountry code must be "AU"

OECD & CbC_EDH: The received message is not meant to be received by the indicated jurisdiction

For domestic lodgers: both the transmitting and receiving country fields in the message specification need to be AU.

For international lodgers: AU needs to be listed in the receiving country field value(s)

Invalid Message Type Indicator

Message Type Indicator must be CBC401 (new information) or CBC402 (corrections/deletions)

Invalid Doc Type Indics for given Message Type Indic

If Message Type Indicator is CBC401 the message can only contain Doc Type OECD0 (Resent Data) or OECD1 (New Data).

If Message Type Indicator is CBC402 (correction/deletion) the message can contain only Doc Types OECD0 (Resent Data), OECD2 (Corrected Data) or OECD3 (Deleted Data).