# Invoice & Creditnote

# Introduction

Invoice is a document sent by a supplier to a customer claiming payment for goods or services supplied under conditions agreed by the seller and the buyer.

The seller may invoice for one or more transactions referring to goods and services related to one or more order, delivery instruction, call off, etc.

An invoice may contain references to payment terms, transport details and additional information for customs or statistical purposes in the case of cross-border transaction.

Credit note is a document issued to indicate a return of funds in the event of an invoice error, incorrect or damaged products/services, purchase cancellation or otherwise specified circumstance.

---

# Recommended formats

Below is a list of invoice and credit note formats recommended by us.

# Pagero Universal Format Billing 2.0

Pagero Universal Format is developed and maintained by Pagero Group. PUF is based upon Universal Business Language Version 2.1 (UBL 2.1).

To align with new regulations and the business needs that comes with the growing use of electronic invoices throughout the world, the core idea of PUF is to enable its users to provide enough data to meet the requirements in these markets.

To be able to provide the broadest support possible, PUF has been designed with the following core basis in mind:

• European standard EN 16931-1:2017 - EN 16931-1:2017 complies with the European Directive on electronic invoicing for public authorities (EN 2014/55 / ​​EU). It has been prepared by the Technical Committee TC434 at CEN by the European Commission.
• PEPPOL BIS Billing 3.0 (OpenPEPPOL´s CIUS (Core Invoice Usage Specification) with EN16931 as the underlying specification)
• Other CIUS´s based on the regulations of EN 16931-1:2017
• Extensions based on the regulations of EN 16931-1:2017
• Country specific information found in domestic formats in various legal domains.
• Additional information about tax exemption can be found in Technical guidance for tax codes in EN 16931 - v1 from 2024-07-01.

Based on extensive analysis of the above, Pagero Universal Format has been designed to meet these country-, industry-, format- and/or system-specific requirements.

Another intention of PUF has been to create a flexible, extendable format which can be updated quickly to be able to meet the requirements of the fast-changing global electronic document landscape.

Pagero Universal Format is not to be considered as a CIUS based on EN16931 or any other CIUS or format. PUF will, however, to a large extent try to follow the work done in EN16931, Peppol and other UBL based invoicing specifications. If one can create a valid and syntactically correct EN16931 based UBL-format; the threshold for implementing PUF should be negligible.

# Peppol BIS Billing 3.0

Peppol Business Interoperability Specifications (BIS) are technical specifications that can be implemented in existing eProcurement solutions and eBusiness exchange services to make them interoperable between disparate systems.

Peppol BIS defines a set of information elements (business terms) and business rules to ensure that requirements are fulfilled and to clarify any option that would otherwise be left open to implementers to decide on.

They are developed and maintained by OpenPeppol and are one of the most commonly used open standards today.

Peppol BIS Billing 3.0 is a Core Invoice Usage Specification (CIUS) of EN 16931, following the guidance given in chapter 7 of the EN 16931. Any instance documents compliant to this specification will be compliant with the European Standard (EN 16931).

# Pagero cXML v 1.2.x

cXML allows buying organizations, suppliers, service providers, and intermediaries to communicate using a single, standard, open language. Successful business-to-business electronic commerce (B2B e-commerce) portals depend upon a flexible, widely adopted protocol. cXML is a well-defined, robust language designed specifically for B2B e-commerce, and it is the choice of high volume buying organizations and suppliers.

cXML transactions consist of documents, which are simple text files containing values enclosed by predefined tags. Most types of cXML documents are analogous to hardcopy documents traditionally used in business.

We develop and maintain a separate, Pagero-focused integration guide for cXML v 1.2.049.

# Pagero UN/EDIFACT INVOIC D96A

UN/EDIFACT is an international standard for electronic data interchange (EDI) developed for the United Nations and approved and published by UNECE, the UN Economic Commission for Europe.

The EDIFACT standard provides a set of syntax rules to structure, an interactive exchange protocol and provides a set of standard messages which allow multi-country and multi-industry exchange of electronic business documents. EDIFACT is widely used across Europe, mainly due to the fact that many companies adopted it very early on.

More general information can be found here UNECE: Introducing UN/EDIFACT.

We develop and maintain our own Message Implementation Guidelines (MIG) for UN/EDIFACT D96A.

---

# Supported formats

Below is a list of invoice and credit note formats supported - but not necessarily recommended - by us.

# A-NZ Peppol BIS Billing

# ANSI X12 810

# BGC Invoice

# CIUS-PT

# Chorus PRO UBL

# Cross Industry Invoice (CEF EN16931 profile)

In addition to the EN16931 profile, the Extended profile is also supported.

# Cross Industry Invoice (XRrechnung profile)

# Cross Industry Invoice (Zugferd & Factur-X)

The example files shown are the embedded XML documents that would be expected inside the Zugferd PDF.

# e2b Invoice

# EHF Invoice and Creditnote 2.0

# ESAP6 Invoice

# ESAP20 Invoice

# FacturaE Invoice

# FatturaPA

# Finvoice XML

# IFS Finvoice 1.0

# IFS e-Invoice 2.0

# Jeeves Invoice

# OIOUBL Invoice

# Peppol BIS 5A 2.0

# Svefaktura 1.0

# SG Peppol BIS Billing

# SI-UBL (SimplerInvoicing)

# TEAPPS XML

# xCBL Invoice

# XRechnung

---

# Customer specific formats

We can build support for any proprietary/closed source format you and your ERP system may require.

For more information, please see the proprietary or closed source formats section.