Merge pull request #104 from OpenPEPPOL/2022-Spring-ReleaseCandidate

2022 spring release candidate
OpenPEPPOL · May 4, 2022 · 4d6ed10 · 4d6ed10
2 parents dbde71c + 63930cf
commit 4d6ed10
Show file tree

Hide file tree

Showing 56 changed files with 772 additions and 206 deletions.
diff --git a/guide/bis/appendix/cii.adoc b/guide/bis/appendix/cii.adoc
@@ -3,6 +3,6 @@
 
 This {peppol} BIS supports the *optional* use of the UN/CEFACT XML Cross Industry Invoice, D16B (CII), meaning that receivers of invoices can register in the SMP to receive CII invoices alongside the mandatory UBL version.
 
-All invoice instances expressed in CII shall be compliant to the restrictions and rules made by this BIS, and hence a CII instance document, shall be validated against the PEPPOL specific rules, just as the UBL instance documents.
+All invoice instances expressed in CII shall be compliant to the restrictions and rules made by this BIS, and hence a CII instance document, shall be validated against the Peppol specific rules, just as the UBL instance documents.
 
 Specification identifier (BT-24) and business process type (BT-23) are the same in a CII instance as for the UBL instance, see <<prof-01>>
diff --git a/guide/bis/appendix/national_rules.adoc b/guide/bis/appendix/national_rules.adoc
@@ -2,10 +2,10 @@
 [[national_rules]]
 = National rules
 
-The following rules have been defined by PEPPOL Authorities in addition to the rules for {peppol} BIS in general.
+The following rules have been defined by Peppol Authorities in addition to the rules for {peppol} BIS in general.
 These rules are affected based on the country of the seller, and will not affect invoices issued in other countries. They apply in *all* profiles that use this transaction specification.
 
-National rules are provided by each country's PEPPOL Authority, and if you need any changes or additions to these rules, please contact your PEPPOL Authority.
+National rules are provided by each country's Peppol Authority, and if you need any changes or additions to these rules, please contact your Peppol Authority.
 
 
 .National transaction business rules

diff --git a/guide/bis/codes/index.adoc b/guide/bis/codes/index.adoc
@@ -2,7 +2,7 @@
 [[codelist]]
 = Code lists
 
-The following chapters give an overview of the restricted set of codes that is used in this PEPPOL BIS. For most codes the restriction is only to add a dated reference of the code list, but for the Invoice Type Code a subset of valid values have been established.
+The following chapters give an overview of the restricted set of codes that is used in this Peppol BIS. For most codes the restriction is only to add a dated reference of the code list, but for the Invoice Type Code a subset of valid values have been established.
 
 
 :leveloffset: +1

diff --git a/guide/bis/introduction.adoc b/guide/bis/introduction.adoc
@@ -1,28 +1,28 @@
 
-= Introduction to openPEPPOL and BIS
+= Introduction to openPeppol and BIS
 
 [preface]
 This {peppol} BIS provides a set of specifications for implementing a {peppol} business process. The document is concerned with clarifying requirements for ensuring interoperability of pan-European Public eProcurement and provides guidelines for the support and implementation of these requirements.
 
 This specification is a Core Invoice Usage Specification (CIUS) of {EN16931}, following the guidance given in chapter 7 of the {EN16931}. Any instance documents following this CIUS will always be compliant with the European Standard ({EN16931}).
 
-The purpose of this document is to describe the use of the invoice and credit note messages in PEPPOL, and to facilitate an efficient implementation and increased use of electronic collaboration
+The purpose of this document is to describe the use of the invoice and credit note messages in Peppol, and to facilitate an efficient implementation and increased use of electronic collaboration
 regarding the billing process based on these formats.
 
 .Statement of copyright
 ****
-This PEPPOL Business Interoperability Specification (PEPPOL BIS) document is a Core Invoice Usage Specification (CIUS) based on CEN/EN 16931:2017. The restrictions on CEN/EN 16931:2017 implemented in this PEPPOL BIS appear from the conformance statement provided in appendix A.
+This Peppol Business Interoperability Specification (Peppol BIS) document is a Core Invoice Usage Specification (CIUS) based on CEN/EN 16931:2017. The restrictions on CEN/EN 16931:2017 implemented in this Peppol BIS appear from the conformance statement provided in appendix A.
 
 The copyright of CEN/EN 16931:2107 is owned by CEN and its members - the European National Standards Bodies. A copy of CEN/EN 16931-1:2017 may be obtained free of charge from any CEN member.
 
-OpenPEPPOL AISBL holds the copyright of this PEPPOL BIS, developed and published subject to the conditions of the agreement between the European Commission and CEN allowing derivate works to be developed and distributed with no additional licensing requirements. CEN and the National  Standards Bodies bears no liability from the content and implementation of this PEPPOL BIS.
+OpenPeppol AISBL holds the copyright of this Peppol BIS, developed and published subject to the conditions of the agreement between the European Commission and CEN allowing derivate works to be developed and distributed with no additional licensing requirements. CEN and the National  Standards Bodies bears no liability from the content and implementation of this Peppol BIS.
 
-This PEPPOL BIS document may not be modified, re-distribute, sold or repackaged in any other way without the prior consent of OpenPEPPOL AISBL.
+This Peppol BIS document may not be modified, re-distribute, sold or repackaged in any other way without the prior consent of OpenPeppol AISBL.
 ****
 
 == Audience
 
-The audience for this document is organisations wishing to be PEPPOL enabled for exchanging electronic invoices, and/or their ICT-suppliers. These organisations may be:
+The audience for this document is organisations wishing to be Peppol enabled for exchanging electronic invoices, and/or their ICT-suppliers. These organisations may be:
 
      * Service providers
      * Contracting Authorities (CA)
@@ -35,4 +35,4 @@ More specifically, roles addressed are the following:
     * ICT Developers
     * Business Experts
 
-For further information on PEPPOL/OpenPEPPOL, please see {common}
+For further information on Peppol/OpenPeppol, please see {common}
diff --git a/guide/bis/main.adoc b/guide/bis/main.adoc
@@ -3,7 +3,7 @@ include::settings.adoc[]
 = {doctitle}
 {name-op-en}
 v{version}
-:description: The PEPPOL Business Interoperablity Specification, “BIS” from here on after, has been developed by the OpenPEPPOL AISBL Post Award Coordinating Community and is published as part of the PEPPOL specifications.
+:description: The Peppol Business Interoperablity Specification, “BIS” from here on after, has been developed by the OpenPeppol AISBL Post Award Coordinating Community and is published as part of the Peppol specifications.
 :doctype: book
 :icons: font
 :stem:

diff --git a/guide/bis/settings.adoc b/guide/bis/settings.adoc
@@ -1,11 +1,11 @@
 :lang: en
 
-:doctitle: image:../shared/images/peppol.jpg[float="right", width=100%] PEPPOL BIS Billing
+:doctitle: image:../shared/images/peppol.jpg[float="right", width=100%] Peppol BIS Billing
 :version: 3.0.10
 :shared-dir: ../../shared
 :snippet-dir: ../../rules/snippets
 
-:name-op-en: OpenPEPPOL AISBL, Post-Award Coordinating Community
+:name-op-en: OpenPeppol AISBL, Post-Award Coordinating Community
 
 
 include::../shared/settings.adoc[]
diff --git a/guide/cius/codes/index.adoc b/guide/cius/codes/index.adoc
@@ -2,7 +2,7 @@
 [[codelist]]
 = Code lists
 
-The following chapters give an overview of the restricted set of codes that is used in this PEPPOL BIS. For most codes the restriction is only to add a dated reference of the code list, but for the Invoice Type Code a subset of valid values have been established.
+The following chapters give an overview of the restricted set of codes that is used in this Peppol BIS. For most codes the restriction is only to add a dated reference of the code list, but for the Invoice Type Code a subset of valid values have been established.
 
 
 For the invoice type code (BT-3) the tables indicates the name and description of each code, as well as a column "Synonym with" to indicate how this invoice type can be processed if the recipient does not have a separate process/work flow for this code, and as you will see, all invoice types valid in this profile can be processed as a commercial invoice (380) and all credit note types as Commercial credit note (381). Some recipients might have separate processes or work flows for some of these types, and can then use these processes.

diff --git a/guide/cius/implementation/index.adoc b/guide/cius/implementation/index.adoc
@@ -1,9 +1,9 @@
 
-= Implementation of this PEPPOL BIS
+= Implementation of this Peppol BIS
 
 Due to copyright from {CEN} this BIS cannot provide detailed implementation guidelines.
 
-To implement this BIS as a {CIUS}, the implementer shall use the published standards from {tc434}, as found {TC434-docs}[here], in addition to the restrictions and rules found in this PEPPOL BIS.
+To implement this BIS as a {CIUS}, the implementer shall use the published standards from {tc434}, as found {TC434-docs}[here], in addition to the restrictions and rules found in this Peppol BIS.
 
 Specific attention is drawn to the following documents:
 

diff --git a/guide/cius/introduction.adoc b/guide/cius/introduction.adoc
@@ -1,16 +1,16 @@
 [preface]
-= Introduction to openPEPPOL and BIS
+= Introduction to openPeppol and BIS
 
 This {peppol} BIS provides a set of specifications for implementing a {peppol} business process. The document is concerned with clarifying requirements for ensuring interoperability of pan-European Public eProcurement and provides guidelines for the support and implementation of these requirements.
 
 This specification is a Core Invoice Usage Specification (CIUS) of {EN16931}, following the guidance given in chapter 7 of the {EN16931}. Any instance documents following this CIUS will always be compliant with the European Standard ({EN16931}).
 
-The purpose of this document is to describe the use of the invoice and credit note messages in PEPPOL, and to facilitate an efficient implementation and increased use of electronic collaboration
+The purpose of this document is to describe the use of the invoice and credit note messages in Peppol, and to facilitate an efficient implementation and increased use of electronic collaboration
 regarding the billing process based on these formats.
 
 == Audience
 
-The audience for this document is organisations wishing to be PEPPOL enabled for exchanging electronic invoices, and/or their ICT-suppliers. These organisations may be:
+The audience for this document is organisations wishing to be Peppol enabled for exchanging electronic invoices, and/or their ICT-suppliers. These organisations may be:
 
      * Service providers
      * Contracting Authorities (CA)
@@ -23,4 +23,4 @@ More specifically, roles addressed are the following:
     * ICT Developers
     * Business Experts
 
-For further information on PEPPOL/OpenPEPPOL, please see {common}
+For further information on Peppol/OpenPeppol, please see {common}
diff --git a/guide/cius/links.adoc b/guide/cius/links.adoc
@@ -1,18 +1,18 @@
 //links used in the BIS document
 
-//PEPPOL
-:peppol: https://peppol.eu/?rel=undefined[PEPPOL]
-:common: https://joinup.ec.europa.eu/svn/peppol/PEPPOL%20BIS%20Common%20text%20and%20introduction%20-%20ver%201%202014-04-14.pdf[PEPPOL BIS common text and introduction]
-:openpeppol: https://peppol.eu/about-openpeppol/?rel=tab41[OpenPEPPOL]
-:policy8: https://peppol.eu/downloads/the-peppol-edelivery-network-specifications/[PEPPOL Policy for identifiers, policy 8]
-:migration-policy: https://github.com/OpenPEPPOL/documentation/blob/master/LifecycleManagement/ReleaseManagement/Migration%20Policy%20-%20Common%20Document%202014-02-24%20rev%202014-08-27.pdf[OpenPEPPOL Migration Policy]
+//Peppol
+:peppol: https://peppol.eu/?rel=undefined[Peppol]
+:common: https://joinup.ec.europa.eu/svn/peppol/PEPPOL%20BIS%20Common%20text%20and%20introduction%20-%20ver%201%202014-04-14.pdf[Peppol BIS common text and introduction]
+:openpeppol: https://peppol.eu/about-openpeppol/?rel=tab41[OpenPeppol]
+:policy8: https://peppol.eu/downloads/the-peppol-edelivery-network-specifications/[Peppol Policy for identifiers, policy 8]
+:migration-policy: https://github.com/OpenPEPPOL/documentation/blob/master/LifecycleManagement/ReleaseManagement/Migration%20Policy%20-%20Common%20Document%202014-02-24%20rev%202014-08-27.pdf[OpenPeppol Migration Policy]
 
 
 //CEN
 :CEN: https://www.cen.eu/Pages/default.aspx[CEN]
 
 //CEN TC434
-:tc434: https://standards.cen.eu/dyn/www/f?p=204:7:0::::FSP_ORG_ID:1883209&cs=1E81C9C833655EEDC7010C8D0A2FB786C[CEN TC434]
+:tc434: https://standards.cen.eu/dyn/www/f?p=204:7:0::::FSP_ORG_ID:1883209&cs=1E81C9C833655EEDC7010C8D0A2FB786C[CEN/TC434]
 :EN16931: https://standards.cen.eu/dyn/www/f?p=204:110:0::::FSP_PROJECT:60602&cs=1B61B766636F9FB34B7DBD72CE9026C72[EN 16931-1-2017]
 :ubl-binding: https://standards.cen.eu/dyn/www/f?p=204:110:0::::FSP_PROJECT:63740&cs=141ABC6EDBD750DFA4EC61F187628828F
 :cii-binding: https://standards.cen.eu/dyn/www/f?p=204:110:0::::FSP_PROJECT:63741&cs=1FA9686BFF2EEFD10B83676518F8C1AFE

diff --git a/guide/cius/principles/index.adoc b/guide/cius/principles/index.adoc
@@ -1,7 +1,7 @@
 [[principles]]
 = Principles and prerequisites
 
-This chapter describes the principles and assumptions that underlie the use of PEPPOL Invoice and Credit Note. It is
+This chapter describes the principles and assumptions that underlie the use of Peppol Invoice and Credit Note. It is
 based on {EN16931} and its corresponding set of documents.
 
 This BIS will identify, explain and justify the restrictions made for this {CIUS}.

diff --git a/guide/cius/process/process.adoc b/guide/cius/process/process.adoc
@@ -13,6 +13,6 @@ An invoice may also refer to a contract or a frame agreement. The invoice may sp
   1. The customer completely rejects the invoice, contacts the supplier and requests a credit note.
   1. The customer disputes parts of the invoice, contacts the supplier and requests a credit note and a new invoice.
 
-The diagram below shows the invoicing process with the use of PEPPOL BIS 5a - Invoice and Credit note. This process assumes that both the invoice and the credit note are exchanged electronically.
+The diagram below shows the invoicing process with the use of Peppol BIS 5a - Invoice and Credit note. This process assumes that both the invoice and the credit note are exchanged electronically.
 
 // image::images/invoicing-process.png[The invoicing process, align="center"]
diff --git a/guide/cius/profiles/index.adoc b/guide/cius/profiles/index.adoc
@@ -1,9 +1,9 @@
 
 = Peppol Identifiers
 
-PEPPOL has defined a {policy8} that specifies how to use identifiers in both
+Peppol has defined a {policy8} that specifies how to use identifiers in both
 its transport infrastructure and within the documents exchanged across that infrastructure. It also introduces
-principles for any identifiers used in the PEPPOL environment. The policies that apply to this BIS are the
+principles for any identifiers used in the Peppol environment. The policies that apply to this BIS are the
 following:
 
 

diff --git a/guide/cius/rules/index.adoc b/guide/cius/rules/index.adoc
@@ -1,7 +1,7 @@
 [[rules]]
 = Business rules
 
-As previously stated, this {peppol} BIS is a {CIUS} that is restricting the {EN16931}, with specific requirements and rules found in the openPEPPOL community, to ensure necessary information that is needed in the link:https://peppol.eu/downloads/?rel=tab87[PEPPOL Transport infrastructure].
+As previously stated, this {peppol} BIS is a {CIUS} that is restricting the {EN16931}, with specific requirements and rules found in the openPeppol community, to ensure necessary information that is needed in the link:https://peppol.eu/downloads/?rel=tab87[Peppol Transport infrastructure].
 
 :leveloffset: +1
 

diff --git a/guide/cius/rules/peppol_rules.adoc b/guide/cius/rules/peppol_rules.adoc
@@ -1,11 +1,11 @@
 [[peppol_rules]]
-= PEPPOL transaction business rules
+= Peppol transaction business rules
 
 The following rules have been defined by {openpeppol} in addition to the rules adopted from {EN16931}.
 These rules apply in *all* implementations that follow this {peppol} BIS.
 
 
-.PEPPOL transaction business rules
+.Peppol transaction business rules
 [cols="1,4", options="header"]
 |====
 |Rule

diff --git a/guide/cius/settings.adoc b/guide/cius/settings.adoc
@@ -1,11 +1,11 @@
 :lang: en
 
-:doctitle: image:../shared/images/peppol.jpg[float="right", width=100%] PEPPOL BIS Invoice and Credit Note
+:doctitle: image:../shared/images/peppol.jpg[float="right", width=100%] Peppol BIS Invoice and Credit Note
 :minor: 0.0
 :revision: 3.0.0
 :shared-dir: ../../shared
 
-:name-op-en: OpenPEPPOL AISBL, Post-Award Coordinating Community
+:name-op-en: OpenPeppol AISBL, Post-Award Coordinating Community
 
 include::links.adoc[]
 

diff --git a/guide/compliance/main.adoc b/guide/compliance/main.adoc
@@ -1,5 +1,5 @@
 = Compliance to BIS
-openPEPPOL AISBL <http://www.peppol.eu/>
+openPeppol AISBL <http://www.peppol.eu/>
 :icons: font
 :source-highlighter: coderay
 :toc: left

diff --git a/guide/migration/main.adoc b/guide/migration/main.adoc
@@ -2,7 +2,7 @@ include::../cius/links.adoc[]
 include::settings.adoc[]
 
 = Migration plan
-OpenPEPPOL AISBL, Post-Award Community
+OpenPeppol AISBL, Post-Award Community
 :doctype: book
 :icons: font
 :toc: left

diff --git a/guide/migration/overview.adoc b/guide/migration/overview.adoc
@@ -43,7 +43,7 @@ h| {phase-out}
 | Optional
 | Discontinued
 
-| PEPPOL BIS Billing, version 3.0
+| Peppol BIS Billing, version 3.0
 | Optional
 | Mandatory
 | Mandatory

diff --git a/guide/migration/rules.adoc b/guide/migration/rules.adoc
@@ -1,7 +1,7 @@
 
-= Migration rules ‐ PEPPOL participants affected by the Migration Policy
+= Migration rules ‐ Peppol participants affected by the Migration Policy
 
-This OpenPEPPOL BIS Billing Migration Policy affects all end-users registered in a SMP for invoice/billing according to the following rules:
+This OpenPeppol BIS Billing Migration Policy affects all end-users registered in a SMP for invoice/billing according to the following rules:
 
 .End-users registered in a SMP before the phase-in date ({phase-in})
 ****
@@ -25,5 +25,5 @@ After the transition, the Peppol BIS Billing 3.0 becomes mandatory and the Peppo
 .For all end-users after the Phase Out ({phase-out})
 ****
 Rule::
-OpenPEPPOL will no longer support the use of Peppol BIS 5a and 4a (version 2.3 or their older versions) in any way. This includes maintenance of validation artefacts and service desk support. Any further use of Peppol BIS 5a and 4a is strongly discouraged and done at the Service Providers’ own risk.
+OpenPeppol will no longer support the use of Peppol BIS 5a and 4a (version 2.3 or their older versions) in any way. This includes maintenance of validation artefacts and service desk support. Any further use of Peppol BIS 5a and 4a is strongly discouraged and done at the Service Providers’ own risk.
 ****
diff --git a/guide/national-rules/development.adoc b/guide/national-rules/development.adoc
@@ -1,9 +1,9 @@
 
 = Development procedure
 
-* The PEPPOL Authority who wish to include country specific rules notifies the PoAcc CMB, following the deadlines for the release schedule of PoAcc.
-* The PEPPOL Authority must ensure to only add rules that are valid for ALL invoices and credit notes in the specific county, both B2G, B2B and B2C.
-* The PEPPOL Authority must ensure that the suggested national rules does not affect other countries, and it must not be in conflict with the any other rules for the profile/transaction.
-* The PEPPOL Authority create sets of test files which triggers each rule with positive and negative outcome.
-*	The PEPPOL Authority documents and tests the country specific rule set.
-*	The PEPPOL Authority must have resources available to make adjustments to the rules if issues are found during the review and test process in PEPPOL.
+* The Peppol Authority who wish to include country specific rules notifies the PoAcc CMB, following the deadlines for the release schedule of PoAcc.
+* The Peppol Authority must ensure to only add rules that are valid for ALL invoices and credit notes in the specific county, both B2G, B2B and B2C.
+* The Peppol Authority must ensure that the suggested national rules does not affect other countries, and it must not be in conflict with the any other rules for the profile/transaction.
+* The Peppol Authority create sets of test files which triggers each rule with positive and negative outcome.
+*	The Peppol Authority documents and tests the country specific rule set.
+*	The Peppol Authority must have resources available to make adjustments to the rules if issues are found during the review and test process in Peppol.