Skip to content
TAPR Docs

PEPPOL Overview

Overview

Section titled “Overview”

TaprNext is a PEPPOL access-point customer application: it registers legal entities, receives invoices, builds and validates outbound XML, and sends via AS4. Validation and format conversion use the phive microservice; transport uses the platform AS4 gateway.

Capabilities

Section titled “Capabilities”
DirectionWhat Tapr does
ReceiveAccept SBDH-wrapped invoices, validate, create Purchase Invoices (or forward in API storage mode), send MLR to the original sender
SendBuild UBL (or Factur-X path) from Sales Invoice fields, validate, send AS4, track MLR
LookupSMP lookup for participant document types
APIExternal systems can send/receive/validate without the UI

Receive paths

Section titled “Receive paths”
  1. Default / S3 storage — AP server stores the message; Tapr processes via webhook/job into a Purchase Invoice.
  2. API storage — Tapr receives XML on receive_peppol_message and forwards to your callback URL.

Invalid messages create a PEPPOL Rejected Message record instead of an invoice.

Send paths

Section titled “Send paths”
  1. Sales Invoice UI — Out Docs → Ready to Send → Send to Customer
  2. Direct API — send_peppol_invoice with raw XML or Factur-X PDF
  3. API create-and-send — higher-level send_invoice flow that creates a Sales Invoice from XML

Storage modes (inbound)

Section titled “Storage modes (inbound)”

Configured under Tapr Settings → Storage:

ModeBehavior
DefaultPlatform-managed storage for inbound PEPPOL files
S3Your bucket credentials for file storage
APIForward valid messages to your callback; minimal local file storage
Section titled “Related setup”
  1. Legal Entity Setup
  2. PEPPOL Registration
  3. PEPPOL API
  4. Storage Configuration
  5. MLR & Invoice Response
Section titled “Related topics”