PEPPOL Send & Receive FAQ

Overview

Common PEPPOL issues and where to look. Track tags: User, Implementor, Integrator.

Send fails from Out Docs (User)

Symptoms: Send Failed, or Ready to Send with sending errors.

Check:

1. Legal Entity PEPPOL registration is approved.
2. Receiver ID is valid (SMP lookup).
3. Required addresses, VAT, tax codes present.
4. Charges mapped; credit notes have preceding invoice refs.
5. Buyer Reference filled. Invoice Manager requires it when you save edits; invoices from New Invoice, Upload, AR Email, ERP fetch, SFTP or API can arrive without it.
6. On exports outside the EU, tax codes are not the domestic S (look for the cross-border banner on Line Items).
7. Document format is the one you meant to send. An empty format sends Peppol BIS Billing 3.0 UBL when the receiver accepts it.
8. French CTC only: coded notes are on Notes and Business Process Code is set. On BIS 3.0, Business Process Code is empty, and there is at most one note unless both parties are German.
9. XRechnung only: Payment IBAN and seller contact name, phone, and email are filled (Buyer Reference is the Leitweg-ID).
10. Peppol Sender ID points at an Approved registration of the legal entity.

Sending errors name the field to fix where the PEPPOL rule can be mapped to one.

See Reviewing & Sending Sales Invoices.

MLR shows rejected (User / Implementor)

1. Open the sales invoice MLR status and reason.
2. Confirm the customer can receive the document type you sent.
3. Correct and resend only if appropriate.

See MLR & Invoice Response.

Invoice never arrives (inbound) (Implementor)

1. Confirm PEPPOL registration and participant ID shared with vendors.
2. Check storage mode (Default / S3 / API) and credentials.
3. Look at PEPPOL Rejected Messages for validation failures.
4. Check inbound logs / Error Log for processing exceptions.
5. Inbound PEPPOL is not blocked by the message quota — a full quota is not the cause.
6. Check Tapr Settings → Other → Peppol Network — a live site must be on Production.

API send returns validation error (Integrator)

1. Validate XML with validate_xml before send.
2. Ensure doc_type_id and process_id are set for raw XML sends.
3. Factur-X PDF path must send a real PDF body (%PDF magic bytes).

See REST API Reference.

Quota / metering blocked (Implementor)

Plans limit messages and API calls. When exceeded, outbound sends, non-PEPPOL intake (upload, email, SFTP, cloud folders) and metered APIs refuse new work (inbound PEPPOL keeps arriving) until the period resets or you upgrade. Check Tapr Settings → Subscription.

Related topics

• PEPPOL Overview
• Connection Issues FAQ
• Error Reference