Skip to content
Language: EN

CRS Rejected by Luxembourg ACD: Error Codes & Fixes

Published

You uploaded your CRS file to the Luxembourg tax administration (ACD) and got a status message back with a code you do not recognise: NACK, ERR, 98902, 50007. This guide explains what each status means, what the most common rejection codes point to, and what to change before you send the file again.

It applies to CRS files in the Luxembourg AEOI_LUX format. The new AEOI_LUX_V3.0 schema becomes mandatory on 1 January 2027, and the ACD runs a pre-validation platform so that you can test files all year long. For the schema changes themselves, see our comparison of CRS XML Schema v3.0 and v2.0.

Want to catch the file-level errors before you upload? Our free tool checks your XML against the ACD schemas and the file-name convention, in your browser.

Try the free CRS XML validator (Luxembourg, V3.0)


What happens after you upload a CRS file?

The ACD checks every file in two stages and sends a status message after each one, through the channel you used to submit it (FundSquare e-File or Cetrel SOFiE).

  1. Technical check. Can the ACD read and use the file? The answer is ACK or NACK.
  2. Business check. Does the content respect the OECD, EU and ACD rules? The answer is VAL, WAR or ERR.
StatusMeaningWhat you must do
ACKFile received and readable. Business validation starts.Nothing yet. Wait for the second status.
NACKFile received but unusable (format or structure problem).Fix the file and submit a new one.
VALAll checks passed. The data is stored and will be sent to the destination jurisdictions.Nothing.
WARAccepted, with warnings only.No correction is required. Take the warnings into account for future reports.
ERRAt least one blocking business error. The whole file is rejected and no data is stored.Send a new, compliant file.

A single bad record is enough to reject the entire file with ERR. This is why it pays to validate before you upload.

What to do when your file is rejected

  1. Read the status message. Each error gives a code, a description, the DocRefId of the record concerned (when the error is about a specific record) and the path of the faulty element.
  2. Fix the cause in the source data and regenerate the file.
  3. Keep the same type of message. A resubmission after a rejection is not a correction. Do not switch to CRS702 or OECD2 unless the rejected file was already a correction.
  4. Use a new AEOI_RefId and a new file name, otherwise the new file is rejected as well. We also recommend a new MessageRefId, which is what the OECD guidance asks for.
  5. Test it first on the ACD pre-validation platform (environment T), without real personal data, or with our free validator.

How to read the status message

The status message is an XML file in the AEOI_LUX_RETURN_V3.0 format. Its name repeats the name of your file, followed by the date of the ACD response, the word STATUS, LU and the result.

Inside, look at the ValidationErrors blocks. There is one per error:

ElementWhat it tells you
@severityERR (blocking) or WAR (warning).
CodeThe error code, as listed below.
DetailsThe description of the rule that failed.
DocRefIDInErrorThe record concerned. If it is absent, the error is about the whole file or the header.
FieldError / FieldErrorPathThe XPath of the faulty element, when the ACD could identify it.
DocumentLineThe line number in your XML file, when known.

The most common rejection codes and how to fix them

The tables below group the codes by the part of the file that causes them. Use them as a checklist. The codes come from the ACD technical circular ECHA n° 4 and the OECD CRS Status Message guide (version 3.0, applicable from 1 January 2027). The ACD may adjust its list for the AEOI_LUX_V3.0 schema, so always trust the description in your own status message first.

1. File name and file format

CodeCauseHow to fix it
98902The file name is already known to the ACD.Change the DateHeure part of the name (a new timestamp makes every name unique).
98900The message type in the file name is not CRS701, CRS702 or CRS703.Use one of the three values.
98905The fiscal year in the file name is earlier than 2016.Use a four-digit year of 2016 or later.
98901The environment letter does not match the platform: T file sent to production, or P file sent to test.Use P for production and T for pre-validation, and upload to the matching platform.
98909The RFI identifier in the file name differs from the RFI_Identifier element inside the file.Make both values identical (the 20-character Luxembourg technical identifier).
98915The file is not well-formed XML.Open it in an XML editor or validate it. Typical causes are an unclosed tag or a broken character. Save the file as UTF-8 without a byte order mark.
98914A special character is not replaced by its entity reference, or a whitespace character other than the plain space is used.Replace &, <, >, quotes and apostrophes by &amp;, &lt;, &gt;, &quot;, &apos;. Remove unusual spaces, often pasted from Word or a web page.
98916The file uses a UTF-8 character that the ACD does not accept.Replace it. The accepted subset is listed in the ACD FAQ.
98903The file is too large.The current ACD manual allows 250 MB before encryption and compression (the 2020 circular said 60 MB). If you are above the limit, split by CrsBody, never inside one, and contact the ACD first.
50007The file does not respect the XSD schema.Validate against AEOI_LUX_V3.0.xsd and fix every reported element. Most often a missing mandatory element, a wrong order, or a value outside an enumeration.

The expected pattern is CRS_<YYYYMMDDhhmmss>_<CRS701|702|703>_<year>_<B|C>_<depositor ID>_<RFI identifier>_<P|T>.xml, for example CRS_20170601120000_CRS701_2016_B_19801234567_01234567890M00000000_T.xml. The channel is B for FundSquare e-File and C for Cetrel SOFiE. The depositor ID has 11 or 13 digits.

2. Message header and identifiers

CodeCauseHow to fix it
50008The MessageRefId does not follow the required structure.Build it as country and year block, then block type and RFI identifier, then your own unique part (see below).
50009The MessageRefId was already used in a message validated by the ACD.Generate a new unique value for every file.
98201An identifier (AEOI_RefId, MessageRefId, DocRefId) is longer than 100 characters.Shorten the unique part. It can have 67 characters at most.
98105The MessageTypeIndic in the file differs from the message type in the file name.Align both.
98100 / 98101TransmittingCountry or ReceivingCountry is missing or is not LU.Set both to LU.
98108The ReportingPeriod is before 31 December 2016.Use 31 December of the reporting year.
98006The Timestamp format is wrong.Use YYYY-MM-DDThh:mm:ss, without milliseconds.
80007A CorrMessageRefId is present in the header.Remove it. It must never be used for CRS.
98312NameReportingFI in the Luxembourg header differs from the Name of the ReportingFI.Make the two names identical, character for character.
98908The RFI_Identifier is not the identification number followed by its extension.Concatenate the two values without any separator.

The identifiers share one structure. An 8-character block comes first: LU, the reporting year, and the destination country (LU for the message). It is followed by a 25-character block: the type (HL, HC, RF or AR), an underscore and the 20-character RFI identifier. Your own unique part closes it. Identifiers are case-sensitive and lowercase letters are not accepted.

3. Zero reports, new data and corrections

CodeCauseHow to fix it
98001A nil report (CRS703) contains an AccountReport.Keep a single ReportingFI and no account.
80009A nil report was sent while validated data for the same year was not cancelled. Also raised when a ReportingFI is deleted before all its accounts.Cancel all reported records first, then send the nil report.
80000 / 80001The DocRefId is already used, or its format is wrong.Generate a unique DocRefId per record, with the structure above.
80004A CorrDocRefId is given for new or resent data.Use CorrDocRefId only for corrections and deletions.
80005A correction or deletion has no CorrDocRefId.Point to the DocRefId of the record you correct.
80002 / 80003The CorrDocRefId is unknown to the ACD, or the record was already corrected.Point to the latest version validated by the ACD.
80010One message mixes new data with corrections or deletions.Send them in separate files.
80011The same record is corrected or deleted twice in one message.Keep one correction per record.
80012One message holds two reporting periods.One file per reporting year.
80013 / 80014A resend (OECD0) refers to an unknown DocRefId, or to one that is no longer valid.Resend only records validated and not corrected since.
80006 / 80008A CorrMessageRefId is present in a DocSpec, or OECD0 is used on an AccountReport.Remove it. Resend applies to the ReportingFI only.
98030The DocTypeIndic is a test value (OECD10 to OECD13).Use OECD0 to OECD3.
98026The DocRefId values of one CrsBody do not start with the same 8 characters.Keep one prefix per CrsBody.

A correction file always repeats the ReportingFI in addition to the corrected or deleted records, and gets its own MessageRefId. If you are not sure which message type to use, our page on the CRS reporting solution shows how Fund XP generates new, correction and nil files.

4. Content of the records

CodeRule that failed
60000 / 60001The account number must be a valid IBAN or ISIN when the account number type says so.
60002 / 60003The balance cannot be negative, and must be zero when the account is closed.
60004The name type is not valid for CRS (OECD201).
60005 / 60006Controlling persons must be omitted for reportable account holders (CRS102, CRS103) and provided for a passive NFE with reportable controlling persons (CRS101).
60016An individual account holder cannot have a controlling person.
60007The ReportingGroup is repeated. Only one is allowed.
60013The ReportingFI residence country is missing or is not LU.
60014A birth date is outside a valid range (before 1900 or after the current year).
60015The AccountReport is omitted although the ReportingFI carries new or resent data.
98301 / 98302The residence countries of the person do not include the destination jurisdiction written in the DocRefId.
98910The Nationality element is used. It is not part of CRS reporting.

Wrong or malformed tax identification numbers deserve a check of their own, because they cause many warnings. Our TIN structure and syntax validation page explains how Fund XP handles them.

A pre-flight checklist before every upload

  • The file is UTF-8 without a byte order mark and well-formed.
  • It validates against AEOI_LUX_V3.0.xsd.
  • The name follows the convention and its timestamp is new.
  • The RFI identifier is identical in the file name, in RFI_Identifier and in the identifiers.
  • AEOI_RefId, MessageRefId and every DocRefId are new, uppercase and shorter than 100 characters.
  • New data and corrections are in separate files, and each file covers a single reporting year.
  • The environment letter matches the platform.

The free CRS XML validator covers well-formedness, schema validity, the file-name pattern and the RFI identifier match. Rules that depend on what the ACD already holds, such as an existing DocRefId, can only be checked by the ACD, which is why a test on the pre-validation platform is worth the few minutes.

Frequently asked questions

What is the difference between NACK and ERR?

NACK comes from the technical check: the file is unusable because of its format or structure. ERR comes from the business check: the file was readable but contains at least one blocking rule violation. In both cases nothing is stored and you must send a new file.

Is a resubmission after a rejection a correction message?

No. A rejected file never reached the ACD database, so there is nothing to correct. Send the same type of message again (CRS701 for new data), with a new AEOI_RefId and a new file name.

Do I have to fix a WAR status?

No. The data is accepted and sent on. The ACD asks you to take the warnings into account in future reports.

Why is my file name rejected with 98902?

Because the ACD already holds a file with that exact name. Change the timestamp in the name. The same file with a new timestamp is accepted as far as the name is concerned.

Can I test a CRS file without sending real data?

Yes. The ACD provides a pre-validation platform throughout the year, and asks that no real personal data is sent there. You can also run the file through our free validator, which works in your browser and checks the XSD and the file name.

Does the same list of codes apply to FATCA?

The status message format is shared, but this article covers CRS only. Check the FATCA documentation of the ACD for FATCA files.


Need to file CRS in Luxembourg without chasing error codes? Fund XP checks your data field by field, validates the XML against the ACD schemas before you download it, and can file it with the ACD for you.

See the CRS reporting solution Talk to us

Sources: ACD user manual for CRS reporting, technical circular ECHA n° 4 of 10 August 2020, OECD CRS Status Message XML Schema User Guide version 3.0. This article is for information only and does not replace the official documents of the ACD.