Change record: Peppol BIS Billing 3.0 remains the base profile for network invoice exchange
The maintained OpenPeppol record defines invoice and credit-note terms, bindings, rules, code lists, and validation artefacts while leaving national tax and legal requirements to country implementations.
What changed
The maintained OpenPeppol record defines invoice and credit-note terms, bindings, rules, code lists, and validation artefacts while leaving national tax and legal requirements to country implementations.
This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.
Operating consequence
Buyers should require exact edition, syntax, country profile, participant identifiers, access-point role, validation, response, and archive evidence.
Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.
Capabilities to revisit
Structured E-Invoice Generation And Validation
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for structured e-invoice generation and validation.
Invoice Exchange Network And Recipient Discovery
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for invoice exchange network and recipient discovery.
Invoice Schema Format And Country-Profile Transformation
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for invoice schema format and country-profile transformation.
Tax Engine And E-Invoicing APIs
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for tax engine and e-invoicing APIs.
Audit Trail Document Archive And Evidence Export
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for audit trail document archive and evidence export.
Questions for operating teams
- Which exact population and effective date does the source establish?
- Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
- What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
- What test case would show whether the operational consequence has reached production?
- What record will close, defer, or supersede this review?
Evidence boundary
The source class is Official network technical specification. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.