What does cvc-datatype-valid.1.2.1 mean?

An XML Schema error: a value does not match the lexical format of its declared simple type. The message tells you the bad value (X) and the expected datatype (Y), such as xs:decimal or xs:date.

Why is 1.234,56 rejected as a decimal?

xs:decimal requires a dot decimal separator and forbids thousands grouping. 1.234,56 uses a comma decimal and a period thousands separator, neither accepted. The valid form is 1234.56.

What date format does the invoice schema require?

Date elements are xs:date and require ISO 8601 YYYY-MM-DD (e.g. 2026-12-31). Formats like 31/12/2026 or 12.31.2026 fail. dateTime values additionally need a time and usually a timezone.

Can Invoice Navigator auto-fix cvc-datatype-valid.1.2.1?

Yes for unambiguous cases (confidence 0.70): we normalise decimal separators, strip grouping and currency symbols, and convert clearly-ordered dates to ISO 8601. We ask for confirmation when a date is genuinely ambiguous (e.g. 03/04/2026) since guessing could change the invoice meaning.

Error codes · xsd

cvc-datatype-valid.1.2.1In your invoicing software

Value does not match the required XML datatype format

This is the rejection, word for word: „[cvc-datatype-valid.1.2.1] cvc-datatype-valid.1.2.1 is an XML Schema (XSD) validation error meaning a value does not satisfy the lexical rules of its declared simple type. The message reads "'X' is not a valid value for 'Y'." In e-invoicing this usually means a number, date, or boolean is formatted in a locale or style the schema does not allow — a comma decimal separator, a DD/MM/YYYY date, or 'Yes'/'No' for a boolean.“

The XSD defines exact lexical formats and the value breaks one. Common triggers: xs:decimal with a comma or thousands separators instead of plain dot-decimal; xs:date in DD/MM/YYYY or DD.MM.YYYY instead of YYYY-MM-DD; xs:dateTime missing time or timezone; xs:boolean as Yes/No instead of true/false/1/0; trailing currency symbols or whitespace in a numeric element; or grouping separators leaked by a locale-aware number formatter.

What to have readyNothing. The file has to be re-exported from your invoicing software; we check it again afterwards.

What we doFor xs:decimal: strip thousands separators, convert comma decimals to dots, remove currency symbols and whitespace (1.234,56 becomes 1234.56). For xs:date: convert to ISO 8601 YYYY-MM-DD (31/12/2026 becomes 2026-12-31), disambiguating DD/MM vs MM/DD from the source locale. For xs:boolean: map to true/false or 1/0. Apply the same normalisation at the source by formatting with the invariant culture, then re-validate.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

<cbc:IssueDate>31/12/2026</cbc:IssueDate><cac:LegalMonetaryTotal><cbc:LineExtensionAmount currencyID="EUR">1.234,56</cbc:LineExtensionAmount><cbc:PayableAmount currencyID="EUR">1.469,13</cbc:PayableAmount></cac:LegalMonetaryTotal>

After

<cbc:IssueDate>2026-12-31</cbc:IssueDate><cac:LegalMonetaryTotal><cbc:LineExtensionAmount currencyID="EUR">1234.56</cbc:LineExtensionAmount><cbc:PayableAmount currencyID="EUR">1469.13</cbc:PayableAmount></cac:LegalMonetaryTotal>

What the finding looks likeExample

FindingStructure invalid · cvc-datatype-valid.1.2.1

Location__from_error_message__

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check

Often appears together with

cvc-complex-type.2.4.aInvoice XML structure does not match the required schema cvc-complex-type.4Required attribute is missing from an invoice element