`XSD-UNEXPECTED-ELEMENT`

InvoiceIn checks · validation rule

InvoiceIn checksError

The XML contains an element the schema does not allow at that position. Either the element name is wrong, it belongs to another profile/version (e.g. UBL 2.0 or ZUGFeRD EXTENDED), it is duplicated, or it is a custom extension. Remove or rename it.

Field: (XML element named in the message)
Rule set: InvoiceIn checks
Who has to fix it: The sender

This is a property of the file you received, so it cannot be corrected on your side without changing the document — ask the supplier to reissue it.

Worked example · FA(3)

FA(3) is a fixed sequence: when the mandatory P_15 is missing, the schema flags the next element as "not expected" — add P_15 before Adnotacje.

Fails this rule

<!-- Fa has no P_15 (total amount due): the schema reports the element that follows, Adnotacje, as unexpected -->

Passes

<P_15>2051</P_15>

Check your own invoice

Drop the file that failed. We parse it, run the official rule sets against it and list every finding with a fix — 20 invoices per day, no key, nothing stored.

Open the live demo

Same explanation over the API: GET /v1/rules/XSD-UNEXPECTED-ELEMENT?lang=en