diff --git a/guide/bis/appendix/cii.adoc b/guide/bis/appendix/cii.adoc index ea9fc9cd..0447296c 100644 --- 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 <> diff --git a/guide/bis/appendix/national_rules.adoc b/guide/bis/appendix/national_rules.adoc index 48516ab3..60d6316c 100644 --- 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 index cc7ba091..6fc09bc9 100644 --- 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 index 8ee6fb31..c76522fe 100644 --- 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 index 316673a5..806b52df 100644 --- 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 index 7c608d58..6830ab25 100644 --- 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 index b4a0db98..7431a566 100644 --- 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 index 466caa97..40eb2527 100644 --- 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 index c11e3775..237412c9 100644 --- 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 index c983f0e4..f4f8daba 100644 --- 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 index 4d31a2a0..3dfdd4e9 100644 --- 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 index 8bc93b6c..9c20c67b 100644 --- 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 index a7a2d29b..4144e1ca 100644 --- 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 index 396550ab..f0cba174 100644 --- 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 index 0b3dc2e6..81df5dd9 100644 --- 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 index af1c50a4..35b2cd07 100644 --- 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 index 1ace72b0..8118fc4c 100644 --- a/guide/compliance/main.adoc +++ b/guide/compliance/main.adoc @@ -1,5 +1,5 @@ = Compliance to BIS -openPEPPOL AISBL +openPeppol AISBL :icons: font :source-highlighter: coderay :toc: left diff --git a/guide/migration/main.adoc b/guide/migration/main.adoc index 922e8bcd..d6270416 100644 --- 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 index 26c3d1fe..439d0f7e 100644 --- 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 index 4ce248a6..d466c786 100644 --- 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. **** \ No newline at end of file diff --git a/guide/national-rules/development.adoc b/guide/national-rules/development.adoc index 9acc28de..3dc8cdf1 100644 --- 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. diff --git a/guide/national-rules/introduction.adoc b/guide/national-rules/introduction.adoc index 407a37f6..94cb912b 100644 --- a/guide/national-rules/introduction.adoc +++ b/guide/national-rules/introduction.adoc @@ -3,7 +3,7 @@ == Country specific validation rules -The PEPPOL BIS Billing v3 allows for validation rules which are triggered based on the country code of the supplier, and which is not in conflict with any other rules for the profile or transaction. +The Peppol BIS Billing v3 allows for validation rules which are triggered based on the country code of the supplier, and which is not in conflict with any other rules for the profile or transaction. [IMPORTANT] ==== @@ -14,9 +14,9 @@ By *"country code of the supplier"* is meant (in prioritised order) . The seller country code (BT-40) ==== -Country-qualified rule sets can be added to the PEPPOL BIS on request from the PEPPOL Authority of the specific country. -The PEPPOL Authority is responsible for the development, testing and maintenance of the rules. The country specific rules makes it possible to use the PEPPOL BIS without the need of creating a country specific CIUS. -The same specification and validation rules can be used by all PEPPOL users and no need to specifically identify the customization neither in the XML message or in the SMP-registration. +Country-qualified rule sets can be added to the Peppol BIS on request from the Peppol Authority of the specific country. +The Peppol Authority is responsible for the development, testing and maintenance of the rules. The country specific rules makes it possible to use the Peppol BIS without the need of creating a country specific CIUS. +The same specification and validation rules can be used by all Peppol users and no need to specifically identify the customization neither in the XML message or in the SMP-registration. The below diagram shows a simplified view of the validation steps. An invoice issued by a Swedish supplier goes through all validation steps but only invokes the country specific rule sets which is intended for Swedish suppliers. diff --git a/guide/national-rules/main.adoc b/guide/national-rules/main.adoc index 48987daf..0b64c895 100644 --- a/guide/national-rules/main.adoc +++ b/guide/national-rules/main.adoc @@ -3,7 +3,7 @@ include::settings.adoc[] = {doctitle} {name-op-en} v{revision} -:description: This PEPPOL methodology document has been developed by the OpenPEPPOL AISBL Post Award Coordinating Community. +:description: This Peppol methodology document has been developed by the OpenPeppol AISBL Post Award Coordinating Community. :doctype: book :icons: font :stem: diff --git a/guide/national-rules/settings.adoc b/guide/national-rules/settings.adoc index 6c646f56..45b52a4d 100644 --- a/guide/national-rules/settings.adoc +++ b/guide/national-rules/settings.adoc @@ -1,11 +1,11 @@ :lang: en -:doctitle: image:../shared/images/peppol.jpg[float="right", width=100%] PEPPOL methodolgy for national rules based on Sellers country +:doctitle: image:../shared/images/peppol.jpg[float="right", width=100%] Peppol methodolgy for national rules based on Sellers country :minor: 0.0 :revision: 0.0.1 :shared-dir: ../../shared -: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/national-rules/testfiles.adoc b/guide/national-rules/testfiles.adoc index beda88ba..36d5bada 100644 --- a/guide/national-rules/testfiles.adoc +++ b/guide/national-rules/testfiles.adoc @@ -2,7 +2,7 @@ [[testfiles]] = Test files -Test files for each national rules must be present in the deliverable from the PEPPOL Authority in order to have the national rules approved. +Test files for each national rules must be present in the deliverable from the Peppol Authority in order to have the national rules approved. The test files should include both positive and negative tests, meaning tests that both fire the rule, and tests where the rule is not fired. diff --git a/guide/profile/annex/processes.adoc b/guide/profile/annex/processes.adoc index f5ce9a92..81ac9007 100644 --- a/guide/profile/annex/processes.adoc +++ b/guide/profile/annex/processes.adoc @@ -9,6 +9,6 @@ P10 - Corrective invoicing:: The process as descibed for corrective invoicing was seen as unclear as to the differentiating between a corrective invoice and a credit note, and this process was set to be out of scope. P11 - Partial and final invoicing:: -Due to the fact that partial and final invoices does not require all information that is mandated, this process is out of scope for this PEPPOL BIS. +Due to the fact that partial and final invoices does not require all information that is mandated, this process is out of scope for this Peppol BIS. P12 - Self billing:: Directive 2006/112/EC (Article 224) requires a specific process to be observed, involving prior agreement and a procedure where the supplier is to accept each invoice. Self-billing requires a specific set-up due to the requirements for prior agreement and procedure for the acceptance of each self-bill. Specific milestones have to be observed at time of setting it up as well as in the operation of self-billing. diff --git a/guide/profile/codes/index.adoc b/guide/profile/codes/index.adoc index d9391e70..cb58d60c 100644 --- a/guide/profile/codes/index.adoc +++ b/guide/profile/codes/index.adoc @@ -1,7 +1,7 @@ = Code list for invoice type code (BT-3) -The following sub-chapters give an overview of the restricted set of invoice type codes (BT-3) that is used in this PEPPOL BIS Billing. +The following sub-chapters give an overview of the restricted set of invoice type codes (BT-3) that is used in this Peppol BIS Billing. The table 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/profile/codes/invoice-specific.adoc b/guide/profile/codes/invoice-specific.adoc index b8ef2695..33c5a555 100644 --- a/guide/profile/codes/invoice-specific.adoc +++ b/guide/profile/codes/invoice-specific.adoc @@ -6,7 +6,6 @@ include::../../syntax/codelists/inv-type.adoc[] - [cols="1h,2s,4a,1,2m", options="header"] .Code list |=== @@ -16,20 +15,23 @@ include::../../syntax/codelists/inv-type.adoc[] | Synonym with | UBL Message type - | 380 | Commercial invoice | Document/message claiming payment for goods or services supplied under conditions agreed between seller and buyer. | | Invoice - -| 393 -| Factored invoice -| Invoice assigned to a third party for collection. +|71 +|Request for payment +|Document/message issued by a creditor to a debtor to request payment of one or more invoices past due. | 380 | Invoice +| 80 +| Debit note related to goods or services +| Debit information related to a transaction for goods or services to the relevant party. +| 380 +| Invoice | 82 | Metered services invoice @@ -37,20 +39,65 @@ include::../../syntax/codelists/inv-type.adoc[] | 380 | Invoice +| 84 +| Debit note related to financial adjustments +| Document/message for providing debit information related to financial adjustments to the relevant party. +| 380 +| Invoice -| 80 -| Debit note related to goods or services -| Debit information related to a transaction for goods or services to the relevant party. +|102 +|Tax notification +|Used to specify that the message is a tax notification | 380 | Invoice +|218 +|Final payment request based on completion of work +|The final payment request of a series of payment requests submitted upon completion of all the work. +| 380 +| Invoice -| 84 -| Debit note related to financial adjustments -| Document/message for providing debit information related to financial adjustments to the relevant party. +|219 +|Payment request for completed units +|A request for payment for completed units. +| 380 +| Invoice + +|331 +|Commercial invoice which includes a packing list +|Commercial transaction (invoice) will include a packing list. +| 380 +| Invoice + +|382 +|Commission note +|Document/message in which a seller specifies the amount of commission, the percentage of the invoice amount, or some other basis for the calculation of the commission to which a sales agent is entitled. +| 380 +| Invoice + +|383 +|Debit note +| Document/message for providing debit information to the relevant party. | 380 | Invoice +|386 +|Prepayment invoice +|An invoice to pay amounts for goods and services in advance; these amounts will be subtracted from the final invoice. +| 380 +| Invoice + +|388 +|Tax invoice +|An invoice for tax purposes. +| 380 +| Invoice + +| 393 +| Factored invoice +| Invoice assigned to a third party for collection. +| 380 +| Invoice | 395 | Consignment invoice @@ -58,6 +105,11 @@ include::../../syntax/codelists/inv-type.adoc[] | 380 | Invoice +|553 +|Forwarder's invoice discrepancy report +|Document/message reporting invoice discrepancies indentified by the forwarder. +| 380 +| Invoice | 575 | Insurer's invoice @@ -65,30 +117,45 @@ include::../../syntax/codelists/inv-type.adoc[] | 380 | Invoice - | 623 | Forwarder's invoice | Invoice issued by a freight forwarder specifying services rendered and costs incurred and claiming payment therefore. | 380 | Invoice - | 780 | Freight invoice | Document/message issued by a transport operation specifying freight costs and charges incurred for a transport operation and stating conditions of payment. | 380 | Invoice -|383 -|Debit note -| Document/message for providing debit information to the relevant party. +|817 +|Claim notification +|Document notifying a claim. | 380 | Invoice +|870 +|Consular invoice +|Document/message to be prepared by an exporter in his country and presented to a diplomatic representation of the importing country for endorsement and subsequently to be presented by the importer in connection with the import of the goods described therein. +| 380 +| Invoice -|386 -|Prepayment invoice -|An invoice to pay amounts for goods and services in advance; these amounts will be subtracted from the final invoice. +|875 +|Partial construction invoice +|Partial invoice in the context of a specific construction project. +| 380 +| Invoice + +|876 +|Partial final construction invoice +|Invoice concluding all previous partial construction invoices of a completed partial rendered service in the context of a specific construction project. +| 380 +| Invoice + +|877 +|Final construction invoice +|Invoice concluding all previous partial invoices and partial final construction invoices in the context of a specific construction project. | 380 | Invoice diff --git a/guide/profile/introduction.adoc b/guide/profile/introduction.adoc index 20499555..9b3ef3af 100644 --- a/guide/profile/introduction.adoc +++ b/guide/profile/introduction.adoc @@ -1,5 +1,5 @@ [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. @@ -11,13 +11,13 @@ The purpose of this document is to facilitate an efficient implementation and in .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. **** @@ -30,7 +30,7 @@ This document is structured as follows: * *Chapters 7 - 9* describes VAT, calculations and rounding. * *Chapter 10* provides examples of selected parts of the invoice * *Chapter 11* gives details and links to all code lists used -* *Chapter 12* gives information on PEPPOL identifiers +* *Chapter 12* gives information on Peppol identifiers * *Chapter 13* describes in detail central information elements. * *Chapters 14 and 15* provides information on validation and validation rules * *Annexes* give information on restrictions according to {EN16931}, use of Cross Industry Invoice syntax and national and syntax rules. @@ -41,7 +41,7 @@ This document is concerned with clarifying requirements for ensuring interoperab == 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) @@ -54,4 +54,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/profile/process/process.adoc b/guide/profile/process/process.adoc index 17082002..70a8e9b5 100644 --- a/guide/profile/process/process.adoc +++ b/guide/profile/process/process.adoc @@ -14,7 +14,7 @@ An invoice may also refer to a contract or a frame agreement. The invoice may sp .. The customer completely rejects the invoice, contacts the supplier and requests a credit note. .. The customer disputes parts of the invoice, contacts the supplier and requests a credit note and a new invoice. -The diagram below shows the basic invoicing process with the use of this PEPPOL BIS profile. This process assumes that both the invoice and the credit note are exchanged electronically. +The diagram below shows the basic invoicing process with the use of this Peppol BIS profile. This process assumes that both the invoice and the credit note are exchanged electronically. image::../shared/images/process.png[The invoicing process, align="center"] diff --git a/guide/profile/profiles/index.adoc b/guide/profile/profiles/index.adoc index a7a2d29b..4144e1ca 100644 --- a/guide/profile/profiles/index.adoc +++ b/guide/profile/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/release-notes/main.adoc b/guide/release-notes/main.adoc index 238c7916..1e4fb01f 100644 --- a/guide/release-notes/main.adoc +++ b/guide/release-notes/main.adoc @@ -1,5 +1,5 @@ -= Release notes for PEPPOL BIS Billing v3 -openPEPPOL AISBL += Release notes for Peppol BIS Billing v3 +openPeppol AISBL :icons: font :source-highlighter: coderay :toc: left @@ -9,11 +9,13 @@ openPEPPOL AISBL :title-logo-image: peppol.png **** -IMPORTANT: Changes in code lists are also reflected by changes in the validation artefacts enforcing only valid codes. All validation changes apply to both UBL and CII validation rules. +IMPORTANT: Changes in code lists are also reflected by changes in the validation artefacts enforcing only valid codes. All validation changes apply to both UBL and CII validation rules. **** :leveloffset: +1 +include::v3.0.13.adoc[] + include::v3.0.12.adoc[] include::v3.0.11-hotfix.adoc[] diff --git a/guide/release-notes/v3.0.13.adoc b/guide/release-notes/v3.0.13.adoc new file mode 100644 index 00000000..0bee8a4b --- /dev/null +++ b/guide/release-notes/v3.0.13.adoc @@ -0,0 +1,36 @@ += Version 3.0.13 +[horizontal] +Release date:: 2022-05-15 + +== Changes to BIS document + + + +== Changes to code lists and validation artefacts + +* An error has been corrected which is causing some XSL-transformers/tools to raise errors when loading/using the schematron-files. + +* Rule PEPPOL-COMMON-R043 (ICD 0208) changed from severity warning to fatal (as announced in the november 2021 release) + +* Added rule to check format for Swedish organisation numbers (ICD/EAS 0007) with severity warning, will be changed to fatal in future release. + +* An error has been corrected in PEPPOL-EN16931-R080 as it should not be triggered in Invoice (only CreditNotes) + +* Added codes 0214, 0215 and 0216 to the ICD code list and support added in validation artefacts. [505] + +* Added codes 0147, 0170, 0188, 0215 and 0216 to the EAS code list and support added in validation artefacts. [481,473,505,506] + +* Double entry of code TSP removed from code list UNCL7143. [488] + +* Added support for additional invoice type codes 71, 102, 218, 219, 331, 382, 553, 817, 870, 875, 876 and 877. This is in line with update made by TC434/EC-DIGITAL. Added to BIS instructions that these additional invoice types codes shall be handled as synonyms to the 380 and thus do not require change in processing. [505] + +* Added support for invoice type code 0388. Added to BIS instructions that this additional invoice type code shall be handled as synonyms to the 380 and thus do not require change in processing. [452] + +== Changes to country specific rules for Denmark +* DK-R-003 PEPPOL CII - changes to new UNSPEC code "TST" +* DK-R-004 PEPPOL UBL & CII - error text is updated +* DK-R-015 PEPPOL UBL & CII is removed + +== Changes to country specific rules for The Netherlands (correction to release notes) + +The 2021 November release contained country rule changes for the Netherlands which were not mentioned in the release notes. Specific details on these rules can be viewed here https://github.com/peppolautoriteit-nl/publications/blob/master/PeppolBIS_NL_RULES/PeppolBIS_NL_rules.md diff --git a/guide/shared/settings.adoc b/guide/shared/settings.adoc index 243088ed..56d55f76 100644 --- a/guide/shared/settings.adoc +++ b/guide/shared/settings.adoc @@ -8,21 +8,21 @@ :ubl-cn-mapping: link:../syntax/ubl-creditnote/tree/[UBL Credit note message table] -//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] -:link-transaction: https://test-vefa.difi.no/peppolbis/poacc/billing/3.0/transaction-spec/[PEPPOL Invoice transaction specification] +//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] +:link-transaction: https://test-vefa.difi.no/peppolbis/poacc/billing/3.0/transaction-spec/[Peppol Invoice transaction specification] :eas: link:/poacc/billing/3.0/codelist/eas/[Code list for electronic address] //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] -:EN16931: https://standards.cen.eu/dyn/www/f?p=204:110:0::::FSP_PROJECT:60602&cs=1B61B766636F9FB34B7DBD72CE9026C72[EN 16931] +:tc434: https://standards.cencenelec.eu/dyn/www/f?p=205:7:0::::FSP_ORG_ID:1883209&cs=1FB866C0AE6E1605133D6363716BED68E[CEN/TC 434] +:EN16931: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:71870&cs=1D0C36D84F6C30D746A7F9FB3E16CC355[EN 16931] :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 :TC434-docs: https://standards.cen.eu/dyn/www/f?p=204:32:0::::FSP_ORG_ID,FSP_LANG_ID:1883209,25&cs=126F1BDBC8D6D6141F550EB578B4A9CF4 diff --git a/guide/transaction-spec/functionality/auditing.adoc b/guide/transaction-spec/functionality/auditing.adoc index fff2b943..ad7ddb7e 100644 --- a/guide/transaction-spec/functionality/auditing.adoc +++ b/guide/transaction-spec/functionality/auditing.adoc @@ -3,7 +3,7 @@ Companies audit themselves as means of internal control or they may be audited by external parties as part of a legal obligation. Accounting is a regular, ongoing process whereas an audit is a separate review process to ensure that the accounting has been carried out correctly. The auditing process places certain information requirements on an invoice. These requirements are mainly related to enable verification of authenticity and integrity of the accounting transaction. -Invoices, conformant to this PEPPOL BIS support the auditing process by providing sufficient information for: +Invoices, conformant to this Peppol BIS support the auditing process by providing sufficient information for: * identification of the relevant Buyer and Seller * identification of the products and services traded, including description, value and quantity diff --git a/guide/transaction-spec/functionality/intro.adoc b/guide/transaction-spec/functionality/intro.adoc index 6847b830..a9189097 100644 --- a/guide/transaction-spec/functionality/intro.adoc +++ b/guide/transaction-spec/functionality/intro.adoc @@ -1,7 +1,7 @@ -An invoice may support functions related to a number of related (internal) business processes. This PEPPOL BIS shall support the following functions: +An invoice may support functions related to a number of related (internal) business processes. This Peppol BIS shall support the following functions: * Accounting * Invoice verification against the contract, the purchase order and the goods and service delivered @@ -9,7 +9,7 @@ An invoice may support functions related to a number of related (internal) busin * Auditing * Payment -In the following chapters an assessment is made of what information is needed for each of the functions listed above and whether it is in scope or out of scope for this PEPPOL BIS. +In the following chapters an assessment is made of what information is needed for each of the functions listed above and whether it is in scope or out of scope for this Peppol BIS. Please also see <> for further details. diff --git a/guide/transaction-spec/rules/peppol_rules.adoc b/guide/transaction-spec/rules/peppol_rules.adoc index bb6642eb..57e8132c 100644 --- a/guide/transaction-spec/rules/peppol_rules.adoc +++ b/guide/transaction-spec/rules/peppol_rules.adoc @@ -1,12 +1,12 @@ [[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* profiles that use this transaction specification. Please also see <> for further details on the restrictions imposed by these rules. -.PEPPOL transaction business rules +.Peppol transaction business rules [cols="1,4", options="header"] |==== |Rule diff --git a/guide/transaction-spec/rules/tc434_rules.adoc b/guide/transaction-spec/rules/tc434_rules.adoc index 65bb1fa3..99b4c38e 100644 --- a/guide/transaction-spec/rules/tc434_rules.adoc +++ b/guide/transaction-spec/rules/tc434_rules.adoc @@ -2,7 +2,7 @@ = EN 16931 transaction business rules The following {EN16931} rules apply to invoice and credit note transaction as it is used in this {peppol} BIS. -This PEPPOL BIS uses a forked version of the validation rules from {EN16931}. +This Peppol BIS uses a forked version of the validation rules from {EN16931}. Further details can be found at https://github.com/OpenPEPPOL/tc434-validation. .EN 16931 business rules diff --git a/guide/transaction-spec/validation/index.adoc b/guide/transaction-spec/validation/index.adoc index ad97dd9e..beb9c39e 100644 --- a/guide/transaction-spec/validation/index.adoc +++ b/guide/transaction-spec/validation/index.adoc @@ -1,7 +1,7 @@ = Validation -To optimize the flexibility in the validation process, each PEPPOL document is validated in different stages with shifting focus in every stage. The diagram below illustrates the different stages. +To optimize the flexibility in the validation process, each Peppol document is validated in different stages with shifting focus in every stage. The diagram below illustrates the different stages. image::../shared/images/validation-new.png[Validation stages, align="left"] diff --git a/project.xml b/project.xml index 74ca5308..ebfb1f83 100644 --- a/project.xml +++ b/project.xml @@ -1,7 +1,7 @@ - PEPPOL BIS Billing 3.0 + Peppol BIS Billing 3.0 Business Interoperability Specifications (BIS) BIS compliance @@ -47,7 +47,7 @@ ubl-peppol native:Schematron rules/sch/PEPPOL-EN16931-UBL.sch - Rules for PEPPOL BIS 3.0 Billing + Rules for Peppol BIS 3.0 Billing diff --git a/rules/sch/CEN-EN16931-CII.sch b/rules/sch/CEN-EN16931-CII.sch index 34875c72..24b025ef 100644 --- a/rules/sch/CEN-EN16931-CII.sch +++ b/rules/sch/CEN-EN16931-CII.sch @@ -4,7 +4,7 @@ Licensed under European Union Public Licence (EUPL) version 1.2. --> - + @@ -25,7 +25,7 @@ [BR-52]-Each Additional supporting document (BG-24) shall contain a Supporting document reference (BT-122). - [BR-51]-Only the last 4 to 6 digits of the Payment card primary account number (BT-87) shall be present if Payment card information (BG-18) is provided in the Invoice. + [BR-51]-In accordance with card payments security standards an invoice should never include a full card primary account number (BT-97). At the moment PCI Security Standards Council has defined that the first 6 digits and last 4 digits are the maximum number of digits to be shown. [BR-50]-A Payment account identifier (BT-84) shall be present if Credit transfer (BG-16) information is provided in the Invoice. @@ -98,8 +98,8 @@ [BR-IC-01]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Intra-community supply" shall contain in the VAT breakdown (BG-23) exactly one VAT category code (BT-118) equal with "Intra-community supply". [BR-G-01]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Export outside the EU" shall contain in the VAT breakdown (BG-23) exactly one VAT category code (BT-118) equal with "Export outside the EU". [BR-O-01]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Not subject to VAT" shall contain exactly one VAT breakdown group (BG-23) with the VAT category code (BT-118) equal to "Not subject to VAT". - [BR-IG-01]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "IGIC" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "IGIC". - [BR-IP-01]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "IPSI" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "IPSI". + [BR-AF-01]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "IGIC" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "IGIC". + [BR-AG-01]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "IPSI" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "IPSI". [BR-B-01]-An Invoice where the VAT category code (BT-151, BT-95 or BT-102) is “Split payment” shall be a domestic Italian invoice. [BR-B-02]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is “Split payment" shall not contain an invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is “Standard rated”. @@ -188,38 +188,38 @@ [BR-AE-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Reverse charge" the Invoiced item VAT rate (BT-152) shall be 0 (zero). - [BR-IG-08]-For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "IGIC", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "IGIC" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119). - [BR-IG-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "IGIC" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119). - [BR-IG-10]-A VAT Breakdown (BG-23) with VAT Category code (BT-118) "IGIC" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120). + [BR-AF-08]-For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "IGIC", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "IGIC" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119). + [BR-AF-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "IGIC" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119). + [BR-AF-10]-A VAT Breakdown (BG-23) with VAT Category code (BT-118) "IGIC" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120). - [BR-IG-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). - [BR-IG-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IGIC" the invoiced item VAT rate (BT-152) shall be greater than 0 (zero). + [BR-AF-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). + [BR-AF-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IGIC" the invoiced item VAT rate (BT-152) shall be greater than 0 (zero). - [BR-IG-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). - [BR-IG-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IGIC" the Document level allowance VAT rate (BT-96) shall be 0 (zero) or greater than zero. + [BR-AF-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). + [BR-AF-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IGIC" the Document level allowance VAT rate (BT-96) shall be 0 (zero) or greater than zero. - [BR-IG-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). - [BR-IG-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IGIC" the Document level charge VAT rate (BT-103) shall be 0 (zero) or greater than zero. + [BR-AF-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). + [BR-AF-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IGIC" the Document level charge VAT rate (BT-103) shall be 0 (zero) or greater than zero. - [BR-IP-08]-For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "IPSI", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "IPSI" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119). - [BR-IP-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "IPSI" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119). - [BR-IP-10]-A VAT Breakdown (BG-23) with VAT Category code (BT-118) "IPSI" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120). + [BR-AG-08]-For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "IPSI", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "IPSI" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119). + [BR-AG-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "IPSI" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119). + [BR-AG-10]-A VAT Breakdown (BG-23) with VAT Category code (BT-118) "IPSI" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120). - [BR-IP-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). - [BR-IP-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IPSI" the Invoiced item VAT rate (BT-152) shall be 0 (zero) or greater than zero. + [BR-AG-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). + [BR-AG-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IPSI" the Invoiced item VAT rate (BT-152) shall be 0 (zero) or greater than zero. - [BR-IP-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). - [BR-IP-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IPSI" the Document level allowance VAT rate (BT-96) shall be 0 (zero) or greater than zero. + [BR-AG-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). + [BR-AG-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IPSI" the Document level allowance VAT rate (BT-96) shall be 0 (zero) or greater than zero. - [BR-IP-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). - [BR-IP-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IPSI" the Document level charge VAT rate (BT-103) shall be 0 (zero) or greater than zero. + [BR-AG-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). + [BR-AG-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IPSI" the Document level charge VAT rate (BT-103) shall be 0 (zero) or greater than zero. [BR-E-08]-In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Exempt from VAT" the VAT category taxable amount (BT-116) shall equal the sum of Invoice line net amounts (BT-131) minus the sum of Document level allowance amounts (BT-92) plus the sum of Document level charge amounts (BT-99) where the VAT category codes (BT-151, BT-95, BT-102) are "Exempt from VAT". @@ -297,7 +297,7 @@ [BR-S-08]-For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "Standard rated", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "Standard rated" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119). - [BR-S-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "Standard rated" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119). + [BR-S-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "Standard rated" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119). [BR-S-10]-A VAT Breakdown (BG-23) with VAT Category code (BT-118) "Standard rate" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120). @@ -936,7 +936,7 @@ - [BR-CL-01]-The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001. + [BR-CL-01]-The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001. [BR-CL-03]-currencyID MUST be coded using ISO code list 4217 alpha-3 @@ -954,13 +954,13 @@ [BR-CL-07]-Object identifier identification scheme identifier MUST be coded using a restriction of UNTDID 1153. - [BR-CL-08]-Subject Code MUST be coded using a restriction of UNTDID 4451. + [BR-CL-08]-Subject Code MUST be coded using a restriction of UNTDID 4451. - - [BR-CL-10]-Any identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. + + [BR-CL-10]-Any identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. - [BR-CL-11]-Any registration identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. + [BR-CL-11]-Any registration identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. [BR-CL-13]-Item classification identifier identification scheme identifier MUST be coded using one of the UNTDID 7143 list. @@ -981,13 +981,13 @@ [BR-CL-18]-Invoice tax categories MUST be coded using UNCL 5305 code list - [BR-CL-19]-Coded allowance reasons MUST belong to the UNCL 5189 code list + [BR-CL-19]-Coded allowance reasons MUST belong to the UNCL 5189 code list [BR-CL-20]-Coded charge reasons MUST belong to the UNCL 7161 code list - [BR-CL-21]-Item standard identifier scheme identifier MUST belong to the ISO 6523 ICD + [BR-CL-21]-Item standard identifier scheme identifier MUST belong to the ISO 6523 ICD code list @@ -1000,10 +1000,10 @@ [BR-CL-24]-For Mime code in attribute use MIMEMediaType. - [BR-CL-25]-Endpoint identifier scheme identifier MUST belong to the CEF EAS code list + [BR-CL-25]-Endpoint identifier scheme identifier MUST belong to the CEF EAS code list - [BR-CL-26]-Delivery location identifier scheme identifier MUST belong to the ISO 6523 ICD + [BR-CL-26]-Delivery location identifier scheme identifier MUST belong to the ISO 6523 ICD code list diff --git a/rules/sch/CEN-EN16931-UBL.sch b/rules/sch/CEN-EN16931-UBL.sch index 6a927cd7..d880fad7 100644 --- a/rules/sch/CEN-EN16931-UBL.sch +++ b/rules/sch/CEN-EN16931-UBL.sch @@ -4,7 +4,7 @@ Licensed under European Union Public Licence (EUPL) version 1.2. --> - + @@ -33,7 +33,7 @@ [BR-11]-The Buyer postal address shall contain a Buyer country code (BT-55). - [BR-51]-The last 4 to 6 digits of the Payment card primary account number (BT-87) shall be present if Payment card information (BG-18) is provided in the Invoice. + [BR-51]-In accordance with card payments security standards an invoice should never include a full card primary account number (BT-87). At the moment PCI Security Standards Council has defined that the first 6 digits and last 4 digits are the maximum number of digits to be shown. [BR-57]-Each Deliver to address (BG-15) shall contain a Deliver to country code (BT-80). @@ -796,7 +796,7 @@ [UBL-CR-411]-A UBL invoice should not include the PaymentMeans ID [UBL-CR-412]-A UBL invoice should not include the PaymentMeans PaymentDueDate [UBL-CR-413]-A UBL invoice should not include the PaymentMeans PaymentChannelCode - [UBL-CR-414]-A UBL invoice should not include the PaymentMeans InstructionID + [UBL-CR-414]-A UBL invoice should not include the PaymentMeans InstructionID [UBL-CR-415]-A UBL invoice should not include the PaymentMeans CardAccount CardTypeCode [UBL-CR-416]-A UBL invoice should not include the PaymentMeans CardAccount ValidityStartDate [UBL-CR-417]-A UBL invoice should not include the PaymentMeans CardAccount ExpiryDate @@ -868,7 +868,7 @@ [UBL-CR-484]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme Name [UBL-CR-485]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme TaxTypeCode [UBL-CR-486]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme CurrencyCode - [UBL-CR-487]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme JurisdiccionRegionAddress + [UBL-CR-487]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme JurisdictionRegionAddress [UBL-CR-488]-A UBL invoice should not include the AllowanceCharge TaxTotal [UBL-CR-489]-A UBL invoice should not include the AllowanceCharge PaymentMeans [UBL-CR-490]-A UBL invoice should not include the TaxExchangeRate @@ -893,7 +893,7 @@ [UBL-CR-509]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme Name [UBL-CR-510]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme TaxTypeCode [UBL-CR-511]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme CurrencyCode - [UBL-CR-512]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme JurisdiccionRegionAddress + [UBL-CR-512]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme JurisdictionRegionAddress [UBL-CR-513]-A UBL invoice should not include the WithholdingTaxTotal [UBL-CR-514]-A UBL invoice should not include the LegalMonetaryTotal PayableAlternativeAmount [UBL-CR-515]-A UBL invoice should not include the InvoiceLine UUID @@ -987,7 +987,7 @@ [UBL-CR-604]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme Name [UBL-CR-605]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme TaxTypeCode [UBL-CR-606]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme CurrencyCode - [UBL-CR-607]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme JurisdiccionRegionAddress + [UBL-CR-607]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme JurisdictionRegionAddress [UBL-CR-608]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty ID [UBL-CR-609]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty NameCode [UBL-CR-610]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty TestMethod @@ -1045,8 +1045,8 @@ [UBL-CR-662]-A UBL invoice should not include the AllowanceChargeReasonCode listID [UBL-CR-663]-A UBL invoice should not include the unitCodeListID [UBL-CR-664]-A UBL invoice should not include the FinancialInstitutionBranch FinancialInstitution - [UBL-CR-665]-A UBL invoice should not include the AdditionalDocumentReference ID schemeID unless the ID equals '130' - [UBL-CR-666]-A UBL invoice shall not include an AdditionalDocumentReference simultaneously referring an Invoice Object Identifier and an Attachment + [UBL-CR-665]-A UBL invoice should not include the AdditionalDocumentReference ID schemeID unless the DocumentTypeCode equals '130' + [UBL-CR-666]-A UBL invoice shall not include an AdditionalDocumentReference simultaneously referring an Invoice Object Identifier and an Attachment [UBL-CR-667]-A UBL invoice should not include a Buyer Item Identification schemeID [UBL-CR-668]-A UBL invoice should not include a Sellers Item Identification schemeID [UBL-CR-669]-A UBL invoice should not include a Price Allowance Reason Code @@ -1061,6 +1061,8 @@ [UBL-CR-678]-A UBL invoice should not include the TaxCategory/ID schemeID [UBL-CR-679]-A UBL invoice should not include the ClassifiedTaxCategory/ID schemeID [UBL-CR-680]-A UBL invoice should not include the PaymentMeans/PayerFinancialAccount + [UBL-CR-681]-A UBL invoice should not include the PaymentMeans InstructionNote + [UBL-CR-682]-A UBL invoice should not include the Delivery DeliveryAddress [UBL-DT-08]-Scheme name attribute should not be present [UBL-DT-09]-Scheme agency name attribute should not be present [UBL-DT-10]-Scheme data uri attribute should not be present @@ -1102,7 +1104,7 @@ [UBL-SR-29]-Bank creditor reference shall occur maximum once [UBL-SR-39]-Project reference shall occur maximum once. [UBL-SR-40]-Buyer trade name shall occur maximum once - [UBL-SR-44]-Payment ID shall occur maximum once + [UBL-SR-44]-An Invoice may only have one unique PaymentID, but the PaymentID may be used for multiple PaymentMeans [UBL-SR-45]-Due Date shall occur maximum once [UBL-SR-46]-Payment means text shall occur maximum once [UBL-SR-47]-When there are more than one payment means code, they shall be equal @@ -1140,7 +1142,7 @@ - [BR-CL-01]-The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001. + [BR-CL-01]-The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001. [BR-CL-03]-currencyID MUST be coded using ISO code list 4217 alpha-3 @@ -1158,10 +1160,10 @@ [BR-CL-07]-Object identifier identification scheme identifier MUST be coded using a restriction of UNTDID 1153. - [BR-CL-10]-Any identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. + [BR-CL-10]-Any identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. - [BR-CL-11]-Any registration identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. + [BR-CL-11]-Any registration identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. [BR-CL-13]-Item classification identifier identification scheme identifier MUST be @@ -1183,13 +1185,13 @@ [BR-CL-18]-Invoice tax categories MUST be coded using UNCL5305 code list - [BR-CL-19]-Coded allowance reasons MUST belong to the UNCL 5189 code list + [BR-CL-19]-Coded allowance reasons MUST belong to the UNCL 5189 code list [BR-CL-20]-Coded charge reasons MUST belong to the UNCL 7161 code list - [BR-CL-21]-Item standard identifier scheme identifier MUST belong to the ISO 6523 ICD code list + [BR-CL-21]-Item standard identifier scheme identifier MUST belong to the ISO 6523 ICD code list [BR-CL-22]-Tax exemption reason code identifier scheme identifier MUST belong to the CEF VATEX code list @@ -1202,10 +1204,10 @@ [BR-CL-24]-For Mime code in attribute use MIMEMediaType. - [BR-CL-25]-Endpoint identifier scheme identifier MUST belong to the CEF EAS code list + [BR-CL-25]-Endpoint identifier scheme identifier MUST belong to the CEF EAS code list - [BR-CL-26]-Delivery location identifier scheme identifier MUST belong to the ISO 6523 ICD code list + [BR-CL-26]-Delivery location identifier scheme identifier MUST belong to the ISO 6523 ICD code list diff --git a/rules/sch/PEPPOL-EN16931-CII.sch b/rules/sch/PEPPOL-EN16931-CII.sch index 97fcaf19..37ae6b6a 100644 --- a/rules/sch/PEPPOL-EN16931-CII.sch +++ b/rules/sch/PEPPOL-EN16931-CII.sch @@ -1,9 +1,8 @@ - Rules for PEPPOL BIS 3.0 Billing @@ -86,7 +85,7 @@ Last update: 2021 November release. ) else ( - if(($arg castable as xsd:integer)) then true() else false() + if(($arg castable as xs:integer)) then true() else false() ) ) @@ -101,11 +100,11 @@ Last update: 2021 November release. ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz - + + + + + Business process MUST be provided. @@ -271,7 +286,7 @@ Last update: 2021 November release. Danish organization number (CVR) MUST be stated in the correct format. - Belgian enterprise number MUST be stated in the correct format. + Belgian enterprise number MUST be stated in the correct format. IPA Code (Codice Univoco Unità Organizzativa) must be stated in the correct format @@ -288,6 +303,13 @@ Last update: 2021 November release. Italian VAT Code (Partita Iva) must be stated in the correct format + + Swedish organization number MUST be stated in the correct format. + + + Australian Business Number (ABN) MUST be stated in the correct format. + + @@ -494,7 +516,7 @@ Last update: 2021 November release. - + Invoice type code MUST be set according to the profile. diff --git a/rules/sch/PEPPOL-EN16931-UBL.sch b/rules/sch/PEPPOL-EN16931-UBL.sch index a7ad517f..7a0d8c6c 100644 --- a/rules/sch/PEPPOL-EN16931-UBL.sch +++ b/rules/sch/PEPPOL-EN16931-UBL.sch @@ -2,7 +2,7 @@ Rules for PEPPOL BIS 3.0 Billing @@ -92,7 +92,7 @@ Last update: 2021 November release. ) else ( - if(($arg castable as xsd:integer)) then true() else false() + if(($arg castable as xs:integer)) then true() else false() ) ) @@ -107,11 +107,11 @@ Last update: 2021 November release. ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz - + + + + + @@ -181,6 +197,11 @@ Last update: 2021 November release. R1XX - Line level R11X - Invoice period --> + + + Only one project reference is allowed on document level + + @@ -193,7 +214,6 @@ Last update: 2021 November release. Only one tax total without tax subtotals MUST be provided when tax currency code is provided. Invoice total VAT amount and Invoice total VAT amount in accounting currency MUST have the same operational sign Only one invoiced object is allowed on document level - Only one project reference is allowed on document level VAT accounting currency code MUST be different from invoice currency code when provided. @@ -307,7 +327,7 @@ Last update: 2021 November release. Danish organization number (CVR) MUST be stated in the correct format. - Belgian enterprise number MUST be stated in the correct format. + Belgian enterprise number MUST be stated in the correct format. IPA Code (Codice Univoco Unità Organizzativa) must be stated in the correct format @@ -324,6 +344,12 @@ Last update: 2021 November release. Italian VAT Code (Partita Iva) must be stated in the correct format + + Swedish organization number MUST be stated in the correct format. + + + Australian Business Number (ABN) MUST be stated in the correct format. + @@ -652,7 +678,7 @@ Last update: 2021 November release. - + Invoice type code MUST be set according to the profile. diff --git a/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R043.xml b/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R043.xml index de61007d..a9be9016 100644 --- a/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R043.xml +++ b/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R043.xml @@ -70,7 +70,7 @@ - PEPPOL-COMMON-R043 + PEPPOL-COMMON-R043 @@ -97,7 +97,7 @@ - PEPPOL-COMMON-R043 + PEPPOL-COMMON-R043 @@ -123,7 +123,7 @@ - PEPPOL-COMMON-R043 + PEPPOL-COMMON-R043 diff --git a/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R049.xml b/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R049.xml new file mode 100644 index 00000000..76019f0c --- /dev/null +++ b/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R049.xml @@ -0,0 +1,97 @@ + + + + ICD (0007) provided. + PEPPOL-COMMON-R049 + + + + + PEPPOL-COMMON-R049 + + + + + 380 + + + + + + 5544332211 + + + + + 5544332211 + + + + + + + + + + + + + PEPPOL-COMMON-R049 + + + + + + 380 + + + + + + 554433-2211 + + + + + + + + + + + PEPPOL-COMMON-R049 + + + + + + 380 + + + + + + SE5544332211 + + + + + + + + + + + diff --git a/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R050.xml b/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R050.xml new file mode 100644 index 00000000..092b3de2 --- /dev/null +++ b/rules/unit-CII-PEPPOL/PEPPOL-COMMON-R050.xml @@ -0,0 +1,97 @@ + + + + ICD (0151) provided. + PEPPOL-COMMON-R050 + + + + + PEPPOL-COMMON-R050 + + + + + 380 + + + + + + 51824753556 + + + + + 51824753556 + + + + + + + + + + + + + PEPPOL-COMMON-R050 + + + + + + 380 + + + + + + ERR51824753556 + + + + + + + + + + + PEPPOL-COMMON-R050 + + + + + + 380 + + + + + + 51824753550 + + + + + + + + + + + diff --git a/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R043.xml b/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R043.xml index dd306e0c..340e2248 100644 --- a/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R043.xml +++ b/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R043.xml @@ -66,7 +66,7 @@ - PEPPOL-COMMON-R043 + PEPPOL-COMMON-R043 @@ -82,7 +82,7 @@ - PEPPOL-COMMON-R043 + PEPPOL-COMMON-R043 @@ -98,7 +98,7 @@ - PEPPOL-COMMON-R043 + PEPPOL-COMMON-R043 diff --git a/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R049.xml b/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R049.xml new file mode 100644 index 00000000..588cca07 --- /dev/null +++ b/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R049.xml @@ -0,0 +1,49 @@ + + + + ICD (0007) provided. + PEPPOL-COMMON-R049 + + + + + + PEPPOL-COMMON-R049 + + + + + 5566221100 + + + + + + + + + PEPPOL-COMMON-R049 + + + + + 556622-1100 + + + + + + + + PEPPOL-COMMON-R049 + + + + + SE5566221100 + + + + + + diff --git a/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R050.xml b/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R050.xml new file mode 100644 index 00000000..c73f86ac --- /dev/null +++ b/rules/unit-UBL-PEPPOL/PEPPOL-COMMON-R050.xml @@ -0,0 +1,49 @@ + + + + ICD (0151) provided. + PEPPOL-COMMON-R050 + + + + + + PEPPOL-COMMON-R050 + + + + + 51824753556 + + + + + + + + + PEPPOL-COMMON-R050 + + + + + ERR51824753556 + + + + + + + + PEPPOL-COMMON-R050 + + + + + 51824753550 + + + + + + diff --git a/structure/codelist/UNCL1001-inv.xml b/structure/codelist/UNCL1001-inv.xml index 9f6e95a0..b8b197de 100644 --- a/structure/codelist/UNCL1001-inv.xml +++ b/structure/codelist/UNCL1001-inv.xml @@ -8,7 +8,12 @@ openPEPPOL - + + 71 + Request for payment + Document/message issued by a creditor to a debtor to request payment of one or more invoices past due. + + 80 Debit note related to goods or services @@ -30,12 +35,34 @@ 84 Debit note related to financial adjustments - Document/message for providing debit information related - to financial adjustments to the relevant party. + Document/message for providing debit information related to financial adjustments to the relevant party. - + + 102 + Tax notification + Used to specify that the message is a tax notification. + + + + 218 + Final payment request based on completion of work + The final payment request of a series of payment requests submitted upon completion of all the work. + + + + 219 + Payment request for completed units + A request for payment for completed units. + + + + 331 + Commercial invoice which includes a packing list + Commercial transaction (invoice) will include a packing list. + + 380 Commercial invoice @@ -45,6 +72,12 @@ + + 382 + Commission note + Document/message in which a seller specifies the amount of commission, the percentage of the invoice amount, or some other basis for the calculation of the commission to which a sales agent is entitled. + + 383 Debit note @@ -61,7 +94,13 @@ invoice. - + + + 388 + Tax invoice + An invoice for tax purposes. + + 393 Factored invoice @@ -75,7 +114,13 @@ one involving a sale. - + + + 553 + Forwarder's invoice discrepancy report + Document/message reporting invoice discrepancies indentified by the forwarder. + + 575 Insurer's invoice @@ -102,5 +147,34 @@ transport operation and stating conditions of payment. - + + + 817 + Claim notification + Document notifying a claim. + + + + 870 + Consular invoice + Document/message to be prepared by an exporter in his country and presented to a diplomatic representation of the importing country for endorsement and subsequently to be presented by the importer in connection with the import of the goods described therein. + + + + 875 + Partial construction invoice + Partial invoice in the context of a specific construction project. + + + + 876 + Partial final construction invoice + Invoice concluding all previous partial construction invoices of a completed partial rendered service in the context of a specific construction project. + + + + 877 + Final construction invoice + Invoice concluding all previous partial invoices and partial final construction invoices in the context of a specific construction project. + \ No newline at end of file diff --git a/structure/codelist/UNCL7143.xml b/structure/codelist/UNCL7143.xml index d550d8da..f33489ba 100644 --- a/structure/codelist/UNCL7143.xml +++ b/structure/codelist/UNCL7143.xml @@ -855,12 +855,6 @@ IMDG main hazard class Main hazard class as defined in the International Maritime Dangerous Goods (IMDG) specification. - - TSP - EU Combined Nomenclature - The number is part of, or is generated in the context ofand maintained by the - European Union (EU). - TSP diff --git a/structure/codelist/eas.xml b/structure/codelist/eas.xml index fe8f16aa..c490d904 100644 --- a/structure/codelist/eas.xml +++ b/structure/codelist/eas.xml @@ -53,10 +53,18 @@ 0142 SECETI Object Identifiers + + 0147 + Standard Company Code + 0151 Australian Business Number (ABN) Scheme + + 0170 + Teikoku Company Code + 0183 Numéro d'identification suisse des enterprises (IDE), Swiss Unique Business @@ -66,6 +74,10 @@ 0184 DIGSTORG + + 0188 + Corporate Number of The Social Security and Tax Number System + 0190 Dutch Originator's Identification Number @@ -137,6 +149,14 @@ 0213 Finnish Organization Value Add Tax Identifier + + + 0215 + Net service ID + + + 0216 + OVTcode 9901 diff --git a/structure/codelist/icd.xml b/structure/codelist/icd.xml index b4cf4894..3cba1877 100644 --- a/structure/codelist/icd.xml +++ b/structure/codelist/icd.xml @@ -1044,24 +1044,40 @@ Classes moyennes et Energie GS1 identification keys Intended Purpose/App. Area: GS1 identification keys and key qualifiers may be used by an information system to refer unambiguously to an entity such as a trade item, logistics unit, physical location, document, or service relationship. Issuing agency: GS1, a global organization. - + 0210 CODICE FISCALE Intended Purpose/App. Area: Electronic Invoicing and e-procurement. Issuing agency: Agenzia delle Entrate, Italy. - + 0211 PARTITA IVA Intended Purpose/App. Area: Electronic Invoicing and e-procurement. Issuing agency: Agenzia delle Entrate, Italy. - + 0212 Finnish Organization Identifier Intended Purpose/App. Area: Identification scheme will be used for electronic trade purposes in e-invoicing, purchasing, electronic receipts. Issuing agency: State Treasury of Finland / Valtiokonttor. - + 0213 Finnish Organization Value Add Tax Identifier Intended Purpose/App. Area: Identification scheme will be used for electronic trade purposes in e-invoicing, purchasing, electronic receipts. Issuing agency: State Treasury of Finland / Valtiokonttor. + + 0214 + Tradeplace TradePI Standard + Intended Purpose/App. Area: Tradeplace is an independent company, set up as a joint venture of several Home Appliance- and Consumer Electronics manufacturers. Tradeplace has launched their TradePI (Product Information) initiative for home appliances, consumer electronics, DIY and affiliated industries that are connected to Tradeplace. The initiative introduces an enhanced standard structure for product information. The TradePI Standard helps retailers to take full advantage of electronic communication and data processing, as the Internet and ICT are fundamentally changing how products and services are offered, bought, and sold. Issuing agency: Tradeplace B.V., The Netherlands. + + + 0215 + Net service ID + Intended Purpose/App. Area: Identification scheme will be used for electronic trade purposes in e-invoicing, purchasing, electronic receipts. Issuing agency: Tieto Finland Oy, FINLAND. + + + 0216 + OVTcode + Intended Purpose/App. Area: Identification scheme will be used for electronic trade purposes in e-invoicing, purchasing, electronic receipts. Issuing agency: TIEKE- Tietoyhteiskunnan kehittamiskeskus, FINLAND. + + diff --git a/structure/syntax/part/customer-party.xml b/structure/syntax/part/customer-party.xml index 6b430537..0aa7116e 100644 --- a/structure/syntax/part/customer-party.xml +++ b/structure/syntax/part/customer-party.xml @@ -28,6 +28,8 @@ PEPPOL-COMMON-R046 PEPPOL-COMMON-R047 PEPPOL-COMMON-R048 + PEPPOL-COMMON-R049 + PEPPOL-COMMON-R050 PEPPOL-EN16931-CL008 @@ -63,6 +65,8 @@ PEPPOL-COMMON-R046 PEPPOL-COMMON-R047 PEPPOL-COMMON-R048 + PEPPOL-COMMON-R049 + PEPPOL-COMMON-R050 schemeID @@ -210,6 +214,9 @@ PEPPOL-COMMON-R046 PEPPOL-COMMON-R047 PEPPOL-COMMON-R048 + PEPPOL-COMMON-R049 + PEPPOL-COMMON-R050 + SE8765456787 diff --git a/structure/syntax/part/supplier-party.xml b/structure/syntax/part/supplier-party.xml index b5074323..2412656c 100644 --- a/structure/syntax/part/supplier-party.xml +++ b/structure/syntax/part/supplier-party.xml @@ -27,7 +27,10 @@ PEPPOL-COMMON-R045 PEPPOL-COMMON-R046 PEPPOL-COMMON-R047 - PEPPOL-COMMON-R048 + PEPPOL-COMMON-R048 + PEPPOL-COMMON-R049 + PEPPOL-COMMON-R050 + PEPPOL-EN16931-CL008 @@ -65,6 +68,9 @@ PEPPOL-COMMON-R046 PEPPOL-COMMON-R047 PEPPOL-COMMON-R048 + PEPPOL-COMMON-R049 + PEPPOL-COMMON-R050 + schemeID Seller or bank assigned creditor identifier identification scheme identifier @@ -244,6 +250,8 @@ PEPPOL-COMMON-R046 PEPPOL-COMMON-R047 PEPPOL-COMMON-R048 + PEPPOL-COMMON-R049 + PEPPOL-COMMON-R050 NO999888777