Validations
Sovos validates all documents before passing them to the PEPPOL Access Point.
Validation outcomes
- Inadmissibility
Inadmissibility occurs when the platform cannot process the message because of a technical problem, for example, a corrupted file, invalid encoding, or unrecognized format. The document is not processed further.
Correct the technical problem 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. The document is non-compliant and rejected.
Read the error detail, fix the specific fields, and resubmit with a newSenderDocumentId.
Validation layers
When you send and invoice, Sovos validates it in three steps:
- Step 1 - Technical validation
- Sovoschecks the document schema, structure, and encoding against PINT, Universal Business Language (UBL), and XML standards..
- Step 2 - Shared PINT rules validation
- Sovosapplies 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 PEPPOLparticipants. If the buyer is outside the UAE, only the shared PINT rules from Step 2 apply.
Check the full schematron rule sets in the United Arab Emirates electronic document specifications - Version 1.0.3 for PINT-AE Invoice, PINT-AE Credit Note, PINT-AE Self-billing Invoice, and PINT-AE Self-billing Credit Note.