Skip to content
TAPR Docs

PEPPOL Rejected Messages

Overview

Section titled “Overview”

When an inbound PEPPOL message fails validation, Tapr does not create a Purchase Invoice. Instead it stores a PEPPOL Rejected Message audit record (with envelope metadata, validation errors, and file attachment when storage allows).

When this happens

Section titled “When this happens”
  • SBDH unwrap / schema validation fails
  • PEPPOL business rules fail hard enough to reject before invoice creation
  • Payload is not a processable invoice (and not handled as MLR-only traffic)

Valid invoices continue through normal PEPPOL Receiving.

What to check

Section titled “What to check”
  1. Open the Rejected Message list in the desk (PEPPOL Rejected Message).
  2. Inspect validation errors JSON.
  3. Confirm sender/receiver IDs and document type.
  4. Ask the sender to retransmit a corrected message if appropriate.

Storage notes

Section titled “Storage notes”
  • Default / S3 modes — original file may be attached to the rejected record.
  • API mode — rejection is still logged; local S3 attachment may not apply.
Section titled “Related topics”