Can valid UBL XML still be rejected by a Peppol Access Point?

Yes. XML syntax is only one layer. Business rules, Peppol-specific requirements, routing identifiers and receiver or national requirements may also be evaluated.

Does passing RejectFix guarantee Peppol acceptance?

No. RejectFix runs its implemented checks and is not an Access Point or the official OpenPeppol Schematron.

← Troubleshooting guides

Peppol validation error vs Access Point rejection

Short answer: a structurally valid XML document may still fail business rules, Peppol-specific rules, electronic-address routing or requirements applied by a country, platform or receiver.

The validation layers

XML syntax: Is the document well-formed XML?

UBL structure: Are elements, namespaces and data types used in the expected document structure?

EN 16931 business rules: Are mandatory business terms present and are calculations consistent?

Peppol BIS Billing rules: Does the document satisfy the Peppol usage specification, including electronic-address requirements?

Routing and receiver checks: Can the Access Point identify the participant and deliver the document for the expected process?

Why the rejection message matters

The exact code identifies which layer failed. A parsing error requires different action from a BR-CO total mismatch or a missing EndpointID. Always work from the newest rejection report rather than assuming that every rejection has the same cause.

Why one successful check is not a guarantee

Tools may implement different rule sets or releases. An Access Point may also apply network, receiver or jurisdiction-specific controls beyond the checks performed locally.

What to do next

Locate the exact rule in the current Peppol documentation, compare the related XML value with the source business record, regenerate the invoice, validate again and resubmit through the normal Access Point workflow.

Browse the error-code library →