Receive Peppol invoices Use case

Receive Peppol invoices: import structured documents, validate them and route them for review

Bring incoming Peppol invoices into the same controlled workflow as uploaded and API documents. Dynafis retains transport metadata, validates the structured invoice and routes exceptions to review.

When do I need this?

For companies and accounting teams that want automated receipt without losing validation, tenant separation, approval and evidence.

Benefits
  • Receive through a configured certified Peppol provider
  • Preserve sender, recipient, document type, message ID and timestamps
  • Validate invoice structure, totals, tax data and business references
  • Detect duplicates and apply idempotent processing
  • Route accepted documents and exceptions into the correct workspace
Typical workflow
  1. Configure the receiving capability and provider connection
  2. Receive and store the original document plus transport metadata
  3. Validate and classify the invoice
  4. Assign the result to review, approval, export or downstream integration
Trust note

Dynafis supports teams with AI, rules and validation. The guidance does not replace tax advice or a legally binding review.

FAQ
Do I need a Peppol provider to receive invoices?

Yes. Receiving on the Peppol network requires a registered capability through a certified service provider or Access Point.

Are received invoices posted automatically?

Not by default. Validation and review policy determine whether an invoice can continue automatically or requires a human decision.

How are duplicate deliveries handled?

Provider and message identifiers are used for idempotent processing so a repeated webhook or delivery does not silently create duplicate invoices.