DOCSEARCHbyAlgolia
Submit Docs

Peppol BIS Invoice 3.0 Specification

repository·master·Indexed 41 days ago

https://github.com/openpeppol/peppol-bis-invoice-3

Technical requirements and guidelines for electronic invoice and credit note exchange based on the European Standard EN 16931. Includes specifications for UBL and UN/CEFACT XML Cross Industry Invoice (CII) D16B, Schematron validation rules, national transaction business rules, and detailed code list restrictions for elements such as Invoice Type Codes, VAT categories, and payment means.

Tokens
43.2K
Snippets
98
Records
209
Agent score
99%

What's inside Peppol BIS Invoice 3

  1. What is the Peppol BIS Invoice specification?

    master

    The Peppol Business Interoperability Specification (BIS) for invoices is a Core Invoice Usage Specification (CIUS) based on the European Standard EN16931. It provides the technical requirements and guidelines necessary to ensure interoperability for pan-European Public eProcurement.

    Developers and organizations use this specification to implement electronic billing processes, specifically for generating and exchanging invoice and credit note messages that are compliant with the European Standard.

  3. Understand the business process scope for Peppol BIS Invoice 3

    master

    The Peppol BIS Invoice 3 implementation guide covers electronic transactions for invoices and credit notes. The primary goal is to enable the creditor (issuer) to send structured data to the debtor (invoicee) regarding products, quantities, and prices.

    While procurement-related data is not mandated, the profile supports various ways of referencing the ordering process to enable automated processing. The implementation is designed to support the following business objectives:

    • Accounting: Provides document and line-level information required to book entries on both the debit and credit sides of company accounts.
    • Auditing: Provides data for identifying parties, products/services (description, value, quantity), settlement connections, and links to contracts or orders. For credit notes, it must identify the original invoice and the nature of the correction.
    • VAT Reporting: Supports the determination of VAT regimes and calculations, including elements required for national legal VAT requirements for both domestic and foreign buyers.
    • Payment: Identifies the means of settlement and clearly states the requested payment.
    • Verification: Provides information necessary for verifying and approving the invoice, such as links to preceding orders, contracts, buyer references, receipts, and the identification of the responsible person or department.

  4. Benefits of using Peppol BIS Invoice 3 specifications

    master

    The Peppol BIS Invoice 3 specification provides a standardized framework for electronic invoicing and credit notes. Implementing these specifications offers several strategic advantages for different types of organizations:

    For Procurement Agencies and Large Organizations

    • Automation of Invoicing: Provides a foundation for transitioning all invoices to electronic form. The specification's flexibility allows for gradual automation of invoice processing based on specific identifiers or references.
    • Process Streamlining: Enables significant savings by automating accounting, simplifying approval processes, ensuring timely payment scheduling, and automating auditing.
    • Operational Flexibility: Large companies can use these standardized documents for general operations while maintaining custom bi-lateral connections for specific large trading partners.
    • Process Restructuring: Serves as a basis for restructuring internal in-house invoicing processes.

    For SMEs and Trading Partners

    • Standardized Exchange: Allows Small and Medium Enterprises (SMEs) to offer trading partners the option of exchanging standardized documents in a uniform way.
    • Electronic Transition: Facilitates the movement of all invoices and credit notes into electronic form.

    For National and Regional Initiatives

    • Mandate Support: Can be mandated as the technical basis for national or regional eInvoicing initiatives.

  5. Understand the Schematron rule sources for PEPPOL BIS Billing 3.0

    master

    The Schematron files in this repository are used for validating PEPPOL BIS Billing 3.0 documents. The rules are categorized by their prefix:

    • PEPPOL prefix: Contains rules specifically defined by OpenPEPPOL.
    • CEN prefix: Contains rules provided by CEN TC434.

    The CEN rules are derived from version 1.3.14.1 of the TC434 validation artefacts.

  6. Understand the purpose and scope of Peppol BIS

    master

    The Peppol Business Interoperability Specification (BIS) provides the technical specifications required to implement Peppol business processes, specifically for electronic invoicing.

    Key characteristics:

    • Standard Compliance: It is a Core Invoice Usage Specification (CIUS) based on the European Standard EN16931. Documents compliant with this specification are compliant with EN16931.
    • Goal: To facilitate efficient electronic collaboration and interoperability in the billing process.
    • Scope: Provides detailed implementation guidelines for invoice and credit note transactions, ensuring interoperability between different systems.
    • Target Audience: Organizations looking to become Peppol-enabled (Contracting Authorities, Economic Operators, Service Providers) and their ICT suppliers (Architects, Developers, and Business Experts).

  7. Identify the target audience for Peppol BIS implementation

    master

    The Peppol BIS documentation is intended for organizations seeking to enable Peppol for electronic invoice exchange and their ICT suppliers.

    Key roles include:

    • Service Providers: Including Contracting Authorities (CA), Economic Operators (EO), and Software Developers.
    • Technical & Business Roles: ICT Architects, ICT Developers, and Business Experts.

  8. Identify unsupported business processes in Peppol BIS Invoice 3

    master

    The Peppol BIS Invoice 3 implementation (CIUS) explicitly excludes certain business processes defined in EN16931 Chapter 5.2. If your integration requires any of the following processes, it is currently out of scope for this specification:

    • P10 - Corrective invoicing: The distinction between a corrective invoice and a credit note was deemed unclear, so this process is excluded.
    • P11 - Partial and final invoicing: This process is excluded because partial and final invoices do not provide all the information mandated by this BIS.
    • P12 - Self billing: Due to the specific legal requirements (Directive 2006/112/EC Article 224) regarding prior agreements, acceptance procedures, and specific operational milestones, self-billing is not supported.

  9. Supported business process functions in Peppol BIS Invoice 3

    master

    The Peppol BIS Invoice 3 specification is designed to support specific internal business processes. When implementing or consuming invoices under this standard, ensure your system accounts for the following supported functions:

    • Accounting
    • Invoice verification (against contracts, purchase orders, and delivered goods/services)
    • VAT reporting
    • Auditing
    • Payment

    Note that while these functions are supported, the specification does not explicitly cover inventory management, delivery processes, customs clearance, marketing, or general reporting.

  10. What is the Peppol BIS and CIUS?

    master

    The Peppol Business Interoperability Specification (BIS) provides the technical requirements for implementing Peppol business processes, specifically ensuring interoperability for pan-European Public eProcurement.

    This specification is a Core Invoice Usage Specification (CIUS) based on the European Standard EN16931. Any instance documents (such as invoices or credit notes) that follow this CIUS are guaranteed to be compliant with the EN16931 standard. The primary goal is to standardize the use of invoice and credit note messages to facilitate electronic billing collaboration.

  12. Understand the Peppol BIS invoicing workflow

    master

    The invoicing process involves the electronic exchange of invoices and credit notes between a supplier and a customer. The standard workflow follows these steps:

    1. Issuance: The supplier issues and sends an invoice to the customer. This invoice typically refers to an order, a contract, or a frame agreement, and specifies goods or services via article numbers or descriptions.
    2. Reception & Processing: The customer receives the invoice and processes it through an invoice control system. This leads to one of three outcomes:
      • Approval: The invoice is fully approved, posted in the accounting system, and queued for payment.
      • Rejection: The invoice is completely rejected. The customer contacts the supplier to request a credit note.
      • Dispute: The customer disputes specific parts of the invoice. The customer contacts the supplier to request both a credit note (to nullify the original) and a new, corrected invoice.

    This workflow assumes that both the invoice and the credit note are exchanged electronically using the Peppol BIS standard.