Validations
This page explains how Sovos validates your documents, including the possible outcomes and the three validation layers applied before passing them to the PEPPOL Access Point.
Validation outcomes
- Inadmissibility
Inadmissibility occurs when the platform can't process the message because of a technical problem, for example, a corrupted file, invalid encoding, or unrecognized format. Sovos stops processing the document.
Correct the technical problem, for example, fix the file encoding or format, and resubmit.- Rejection
Rejection occurs when the document fails a functional or semantic rule, for example, a missing mandatory field, a data inconsistency, a duplicate invoice ID, or a schema violation. Sovos rejects the document.
Read the error detail, fix the specific fields, and resubmit with a newSenderDocumentId.
Validation layers
When you send an invoice, Sovos validates it in three steps:
- Step 1 - Technical validation
- Sovos checks the document schema, structure, and encoding against PINT, Universal Business Language (UBL), and XML standards.
- Step 2 - Shared PINT rules validation
- Sovos applies rules common to all PINT-compliant invoices. If your invoice fails any of these rules, Sovos rejects it as non-compliant.
- Step 3 - UAE-specific PINT rules (AE PINT)
- Sovos applies UAE-specific PINT rules for invoices exchanged between UAE PEPPOL participants. If the buyer is outside the UAE, only the shared PINT rules from Step 2 apply.
For the full schematron rule sets for all PINT-AE document types, see the United Arab Emirates electronic document specifications - Version 1.0.3.