SEPA XML schema error: “This element is not expected”
Last updated: 28 October 2026
A validator or your bank reports that an element is not expected, or shows cvc-complex-type.2.4.a. The file does not match the ISO 20022 schema of its own version, and the bank usually rejects it as a whole. Upload the file below to see which element is affected and what the schema expects in its place.
Check your file for schema errors
Choose fileChecking is free. Repair if needed: €14.95 excl. VAT per file.
Our server checks your file in memory only, never saves it to disk and deletes it after 30 minutes at the latest.
- Error
- Schema error (XSD)
- Where
- Any element, often BIC or BICFI
- Repair
- Automatic for version mix-ups, otherwise reported
What the error message looks like
Validators and banks give this message in English, whatever language your software uses. You meet it in your bank's portal when uploading, in the status file pain.002, or in the software that created the file. libxml2, used by many online validators, writes “This element is not expected”; Java validators (Xerces) write “cvc-complex-type.2.4.a: Invalid content was found starting with element …”. If a mandatory element is missing, the message reads “Missing child element(s)”.
XML schema validator (libxml2, for example xmllint and many online validators)
18: Element '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}BIC': This element is not expected. Expected is one of ( {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}BICFI, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}ClrSysMmbId, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}LEI, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}Nm, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}PstlAdr, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}Othr ).
23: Element '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}MndtId': This element is not expected. Expected is one of ( {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}AmdmntInd, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}AmdmntInfDtls, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}ElctrncSgntr, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}FrstColltnDt, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}FnlColltnDt, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}Frqcy, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}Rsn, {urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}TrckgDays ).
Java validators (Xerces)
cvc-complex-type.2.4.a: Invalid content was found starting with element 'BIC'. One of '{"urn:iso:std:iso:20022:tech:xsd:pain.008.001.08":BICFI, "urn:iso:std:iso:20022:tech:xsd:pain.008.001.08":ClrSysMmbId, "urn:iso:std:iso:20022:tech:xsd:pain.008.001.08":LEI, "urn:iso:std:iso:20022:tech:xsd:pain.008.001.08":Nm, "urn:iso:std:iso:20022:tech:xsd:pain.008.001.08":PstlAdr, "urn:iso:std:iso:20022:tech:xsd:pain.008.001.08":Othr}' is expected.
.NET validators
The element 'FinInstnId' in namespace 'urn:iso:std:iso:20022:tech:xsd:pain.008.001.08' has invalid child element 'BIC' in namespace 'urn:iso:std:iso:20022:tech:xsd:pain.008.001.08'. List of possible elements expected: 'BICFI, ClrSysMmbId, LEI, Nm, PstlAdr, Othr' in namespace 'urn:iso:std:iso:20022:tech:xsd:pain.008.001.08'.
Your bank (status report pain.002)
FF01InvalidFileFormatCH17ElementNotAdmittedCH21RequiredCompulsoryElementMissing
In the status report, banks put the reason in the Rsn/Cd field. Online banking often shows a translation of it. FF01 means the file format is invalid, CH17 that an element is not allowed there, and CH21 that a mandatory element is missing.
Our check
- Field <BIC> is in the wrong place or does not belong in this version. Expected: <BICFI>, <ClrSysMmbId>, <LEI>, <Nm>, <PstlAdr>, <Othr>.
- Field <MndtId> (mandate reference (MndtId)) is in the wrong place or does not belong in this version. Expected: <AmdmntInd>, <AmdmntInfDtls>, <ElctrncSgntr>, <FrstColltnDt>, <FnlColltnDt>, <Frqcy>.
- SeqTp (FRST/RCUR/OOFF/FNAL) is missing.
Cause
The XSD is the official ISO 20022 schema for one message version. It sets which elements may appear, in which order and under which name. An element in the wrong place, with a name from another version, or that does not exist, is “not expected”.
A common cause is a mix of versions: the namespace says pain.008.001.08, but the content still uses names from pain.008.001.02, such as <BIC> instead of <BICFI> or <BICOrBEI> instead of <AnyBIC>. In credit transfers in pain.001.001.09, <ReqdExctnDt> needs the sub-element <Dt>.
Other causes are the order, for example <MndtId> placed after <DtOfSgntr>, and a missing mandatory element such as the sequence type <SeqTp>.
How to fix it by hand
Most schema errors can be fixed in a text editor once you know which version the file claims to be.
- Open the file in a plain text editor, not a word processor.
- Read the namespace at the top, for example
urn:iso:std:iso:20022:tech:xsd:pain.008.001.08. The whole file must follow that version. - Rename the element on the reported line to the name of that version, in the opening and the closing tag, or move it to the position the message names.
- Save the file and validate it again before uploading it.
Before
<CdtrAgt>
<FinInstnId>
<BIC>ABNANL2A</BIC>
</FinInstnId>
</CdtrAgt>After
<CdtrAgt>
<FinInstnId>
<BICFI>ABNANL2A</BICFI>
</FinInstnId>
</CdtrAgt>In the example the creditor's bank is identified with <BIC>, the pain.008.001.02 name. In pain.008.001.08 the same value belongs in <BICFI>; the BIC itself stays the same.
How the tool repairs it
The check lists every schema error with its line number, the field name and the fields expected there, in the language of this page.
Names from another version are repaired automatically: BIC becomes BICFI, BICOrBEI becomes AnyBIC, and ReqdExctnDt gets its Dt. Files entirely in pain.008.001.02 or pain.001.001.03 are converted as a whole to pain.008.001.08 or pain.001.001.09; see SEPA XML versions. If SeqTp is missing, the tool asks you for the value (FRST, RCUR, OOFF or FNAL) and fills it in.
Every repaired file is validated against the XSD again before delivery. If it fails, you get no file and pay nothing, because the repair happens before payment. The check is free; a repair costs €14.95 excl. VAT per file.
What the repair writes in the change report:
- BIC field (BIC) renamed for this version (BICFI).
Other ordering errors, such as <MndtId> after <DtOfSgntr>, are reported but not repaired. Change the order in the software that creates the file, so the next export is right as well.
Related pages
- SEPA XML versions – how to tell pain.008.001.02 from pain.008.001.08.
- Invalid amount or IBAN format – when the element is right but its value is not.
- Field too long – the schema error about the length of a value.
- All SEPA file errors – overview of rejections on submission.
Frequently asked questions
What does cvc-complex-type.2.4.a mean?
It is the Java (Xerces) form of the same message: an element was found where the schema does not expect it. The message lists the elements allowed there.
My file says pain.008.001.08 but uses BIC. Is that wrong?
Yes. In pain.008.001.08 the element is <BICFI>; <BIC> belongs to pain.008.001.02. Rename it or let the repair do it.
Sources
- European Payments Council: SDD Core Customer-to-PSP Implementation Guidelines 2025 – fields, lengths and the SEPA character set for direct debit files
- European Payments Council: 2025 SDD Core Rulebook, version 1.1 – rules of the SEPA Core scheme, including the earliest collection date
- ISO 20022: External Code Sets – the list of reason codes such as AM10, FF01 and CH16 used in status reports