How do I find the regex that is failing?

The validator message echoes both the value and the pattern. Search the published XSD for the type name in the message (for example AgencyIDType, EndpointID); the xsd:pattern facet is the regex you must match.

Is cvc-pattern-valid auto-fixable?

Sometimes. Trimming whitespace, padding leading zeros, and uppercasing alpha characters are safe transformations that Invoice Navigator applies automatically. Substantive ID changes (wrong Leitweg-ID, wrong VAT number) are not auto-fixed because the consequences are tax or routing.

Why does my invoice fail in one validator but pass in another?

Stricter CIUS layers add country-specific patterns on top of EN 16931. A SIRET value that passes the generic Peppol BIS XSD will still fail Chorus Pro's stricter regex. Always run against the country CIUS your buyer uses.

Which fields most commonly fail cvc-pattern-valid in EN 16931?

BT-30 Seller legal registration identifier, BT-46/BT-47 Buyer identifier, BT-90 Bank assigned creditor reference, BT-12/BT-13 references when a country CIUS adds a pattern, and dates emitted as UN/CEFACT format 102 instead of 616.

Can I use a Schematron rule to catch this earlier?

No. xsd:pattern runs at the parser level, before Schematron. The structural failure short-circuits validation. Catch it earlier by validating against the XSD in your CI pipeline rather than waiting for the Access Point to reject.

Error codes · xsd

cvc-pattern-validIn your invoicing software

Value does not match the regex pattern declared in the schema

This is the rejection, word for word: „[cvc-pattern-valid] cvc-pattern-valid is an XSD facet-validation error raised when an element or attribute value fails the xsd:pattern regular expression declared on its simple type. The canonical message reads: "Value 'X' is not facet-valid with respect to pattern 'P' for type 'T'." In EN 16931 invoice payloads it usually fires on identifier fields (BT-30 Seller legal registration ID, BT-46 Buyer identifier, BT-90 Bank assigned creditor identifier), date fields with a stricter UN/CEFACT format pattern, and country-CIUS extensions like the Italian fattura tax-ID pattern.“

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

What we doRead the failing pattern and value out of the validator message; apply a deterministic transformation (trim, upper-case, pad, strip prefix) where one is safe, otherwise the caller must supply the corrected identifier.

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:EndpointID schemeID="0088">123 456 789 01</cbc:EndpointID>

After

<cbc:EndpointID schemeID="0088">1234567890123</cbc:EndpointID>

What the finding looks likeExample

FindingStructure invalid · cvc-pattern-valid

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check