For finance teams, software providers and accounting firms that need to create structured invoices from ERP, accounting, API or document data.
Create an e-invoice Conversion
Create an e-invoice: generate EN16931, Peppol, XRechnung or Factur-X from reviewed data
Create a structured e-invoice from one reviewed data set. Dynafis separates invoice content, document profile and delivery channel so that EN16931, Peppol, XRechnung and Factur-X are handled correctly rather than treated as interchangeable labels.
- One canonical model for EN16931, UBL, CII, Peppol BIS Billing, XRechnung and Factur-X
- Select the document profile according to recipient, country and process
- Validate mandatory fields, totals, taxes and references before export
- Human approval and version history for each generated invoice
- Keep download, API export and network delivery as controlled separate steps
- Identify the recipient, destination process and required profile
- Review invoice data and complete missing information
- Generate and validate the structured e-invoice
- Download, integrate or release it to the configured delivery channel
Trust note
Dynafis supports teams with AI, rules and validation. The guidance does not replace tax advice or a legally binding review.
FAQ
Is every PDF an e-invoice?
No. A structured e-invoice contains machine-readable invoice data in an accepted syntax or hybrid profile. A plain PDF alone is generally not structured.
Is Peppol an invoice format?
No. Peppol combines network rules and document profiles. The invoice itself commonly uses UBL and a Peppol BIS or national profile.
Which format should I create?
The format depends on recipient capability, jurisdiction and process. Dynafis keeps that choice separate from the underlying invoice data.