Validation and correction

Automatic validation of e-invoices against country-specific rules, and correction of common errors, before documents enter the network.

Schedule a meeting

API documentation

how it works
Validation before sending: no rejections afterwards

An e-invoice that never reaches the network costs time and trust. The eConnect PSB validates each document automatically before it enters the network. That covers XSD schemas (structure) and business rules (content rules per standard and per country).

Validation uses two layers: the document is checked against the latest artefacts and, where relevant, against the previous version the network still accepts. You see immediately whether a document can be sent and whether an upgrade is required.

Validation messages are available in Dutch and English via the X-EConnect-Language header.

Structure validation (XSD)

Check of the XML structure: are all mandatory fields present and correctly formatted?

Business rules

Check of content rules: do calculations match, are identifier codes valid and are field combinations logical?

Country-specific rules

Extra validation rules per country and standard, such as NLCIUS, XRechnung or BIS Billing V3.

validation layers
Two validation layers, one result

Each document passes two independent validation steps before sending.

standalone validator
Standalone Validate API and free online tool

Besides automatic validation on send, eConnect offers a standalone Validate API. With POST /api/v1/generic/validate you validate an XML document without storing or sending it. There is no charge and no webhooks are triggered.

The document format is recognised automatically from the XML content. You do not have to state whether it is NLCIUS, BIS Billing V3 or another format.

The validator is also available as a free online tool on econnect.eu/en/validator, without an account, for developers and implementation partners.

Go to the free validator

customer-specific rules
Customer-specific and sector rules

Standard validation rules cover the generic requirements of Peppol and the national standards. For organisations with extra requirements (sector rules, internal accounting checks or customer-specific controls) the Validate API supports custom rule sets.

The parameter ?optionId={id} activates a predefined set of validation rules. Available options can be listed via GET /api/v1/generic/validate/options. You then validate against the standard and against the specific requirements of your sector or customer.

Automatic format detection

The Validate API recognises the document format automatically on every validation call.

Free online validator

Test documents directly in the online validator on econnect.eu. No account required.

NL and EN error messages

Validation messages are available in Dutch and English.

Technical characteristics
Frequently asked questions about validation and correction
What exactly is validated?

The PSB validates each document on two levels: the XSD structure (are all fields present and correctly built?) and the business rules (do calculations match, do identifier codes come from the right code lists and are field combinations logically sound?). On top of that come country-specific rules, such as the extra NLCIUS requirements for Dutch invoicing to government.

When is an invoice stopped?

An invoice is stopped when validation returns an error: a structure problem or a breach of a business rule. Warnings are reported but do not block sending. You receive a detailed assertion list with, for each finding, the flag (error, warning, success), the rule name and a description.

Can I validate documents without sending them?

Yes. Via the standalone Validate API (POST /api/v1/generic/validate) you validate XML documents without storage or sending. There is no charge. The free online validator at econnect.eu/en/validator does the same without an API integration, which is useful while testing an implementation.

How does the dual validation layer work?

The document is checked against the latest validation artefacts and, where relevant, against the previous version the network still accepts. If the document fails the latest version but passes the previous one, both results are returned. You can see immediately whether sending is still possible and whether an upgrade is needed.

Can I set customer-specific validation rules?

Yes. The parameter ?optionId={id} on the Validate API call activates a predefined rule set for customer-specific requirements or sector standards. Available options can be listed via GET /api/v1/generic/validate/options. This extension is available in the PSB platform and by arrangement with eConnect.

Want to prevent invoice errors structurally?

Schedule a meeting

Ask Cora a question