Validation

NCS-EDI validates a message in several stages. The distinction matters: a syntax violation stops processing immediately, whereas a business violation leads to a clarification case – the message is retained and can run again after correction.

What is this for?

• Detect faulty messages before they turn into wrong documents.
• Distinguish blocking errors from mere warnings.
• Send the partner a meaningful acknowledgement.

How to set it up

1. Stage 1 – syntax: validated against the segment tables. A violation is an error, processing stops and the partner receives a CONTRL carrying the fault.
2. Stage 2 – code lists: qualifiers, currencies and country codes are checked. An error for mandatory entries, otherwise a warning.
3. Stage 3 – business rules: defined per document type. A violation leads to a clarification case (status CL).
4. Stage 4 – e-invoice: XRechnung and ZUGFeRD are validated against their rule artefacts; a violation prevents dispatch.