Errors and reprocessing

When something goes wrong, NCS-EDI discards nothing. The message is retained as the secured original, the findings are stored, and after correction the exchange can be reprocessed – with its history intact.

What is this for?

• Locate failed exchanges and identify the cause.
• Reprocess after correction without asking the partner to resend.
• Preserve the full history of an exchange.

How to set it up

1. Filter the journal for entries with status ER (error) or CL (clarification).
2. Open the entry and read the findings – they name the rule that was violated.
3. Fix the cause: a missing entry in the code lists, a wrong syntax profile on the partner or a business problem on the document.
4. Reprocess the exchange. It resumes from the secured original, not from the file in the error folder: the retry counter increases and a new journal entry points back to the old one.