Based on an standardization request from the European Commission, the CEN Project Committee (PC 434) was created in 2014 in order to provide a semantic model for standardizing electronic invoices.
This Test Scenario aims at providing a GITB-compliant Test Case to allow the validation of
electronic invoices created using different syntaxes against the PC 434 semantic standard for e-Invoicing.
The scope of the test is checking that the instance is created using an accepted syntax, its compliance to this underlying syntax and to the semantic model and business rules as defined by the CEN PC 434 semantic model.
List the parties/actors that takes some role in this business process.
Customer: The customer is the legal person or organization who is in demand of a product or service. Examples of customer roles: buyer, consignee, debtor and contracting authority.
Supplier: The supplier is the legal person or organization that provides a product or service. Examples of supplier roles: seller, consignor, creditor, and economic operator.
These actors play the following roles in this business process.
Creditor: One to whom a debt is owed. The party that claims the payment and is responsible for resolving billing issues and arranging settlement. The party that sends the invoice. Also known as invoice issuer, accounts receivable, or seller.
Debtor: One who owes debt. The party responsible for making settlement relating to a purchase. The party that receives the invoice. Also known as invoicee, accounts payable, or buyer.
The System Under Test (SUT) produces the electronic invoice document. The Test Bed only validates the document instance, not the business process. The operator submits or uploads the electronic invoice to the GITB-Compliant Test Bed. He wants to know whether the XML document instance is compliant according to the PC 434.
1. Conformance criteria: The document belongs to an accepted syntax. How to test: Check namespace for the root document being in the list of accepted syntaxes
2. Conformance criteria: The document structure is valid. How to test: The electronic document is valid according to the XSD structure of the identified syntax.
3. Conformance criteria: The electronic invoice is conformant to PC 434. How to test: The electronic invoice is valid according to the CEN PC 434 Schematron semantic model and rules.
4. Conformance criteria: Identification of additional elements. How to test: Use an Schematron file to identify elements of the XML electronic invoice not defined in the CEN PC 434.