BIS Billing 3.0
OpenPeppolAISBL, Post-Award Coordinating Community
The Peppol Business Interoperablity Specification, “BIS” from here on after, has been developed by the OpenPeppolAISBL Post Award Coordinating Community and is published as part of the Peppol specifications.
1. Introduction to openPeppol and BIS
Questa Business Interoperability Specification (BIS) fornisce un insieme di specifiche per l’implementanzione della fatturazione elettronica e pubblicato come parte delle specifiche Peppol.
In questo documento le regole d’uso ed i paragrafi applicabili specificatamente al contesto italiano sono evidenziate in giallo, con chiara distinzione:
-
delle CIUS da applicare alle fatture dall’estero, ovvero cross-border (CIUS);
-
delle CIUS da applicare alle fatture domestiche (CIUS domestica);
-
delle Estensioni da applicare alle fatture domestiche (estensione).
Le regole d’uso ed i paragrafi applicabili specificatamente alla fatturazione domestica verso i privati sono invece evidenziate in verde.
Per ulteriori dettagli vedi anche i paragrafi 12.2 e Appendix A.
The purpose of this document is to facilitate an efficient implementation and increased use of electronic collaboration regarding the billing process.
1.1. Document Structure
This document is structured as follows:
-
Chapters 1 - 5 gives general information on the business processes, requirements and functionalities
-
Chapter 6 describes the semantical data types
-
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 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 EN 16931, use of Cross Industry Invoice syntax and national and syntax rules.
1.2. Scope
Questo documento fornisce le linee guida per il supporto e l’implementazione delle transazioni relative a fatture e note di credito.
This document is concerned with clarifying requirements for ensuring interoperability and provides guidelines for the support and implementation of these requirements. This document will also provide a detailed implementation guideline for the invoice and credit note transactions.
Sono supportati specificatamente i seguenti scenari di business:
-
B2G – Business to Government
-
G2G – Government to Government
-
B2B – Business to Business
-
B2C – Business to Consumer
-
G2B – Government to Business
-
G2C – Government to Consumer
1.3. 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:
-
Service providers
-
Contracting Authorities (CA)
-
Economic Operators (EO)
-
Software Developers
More specifically, roles addressed are the following:
-
ICT Architects
-
ICT Developers
-
Business Experts
For further information on Peppol/OpenPeppol, please see Peppol BIS common text and introduction
2. Benefits
The invoice and credit note provides simple support for complex invoicing, where there is a need for credit note in addition to an invoice. Other potential benefits are, among others:
-
Can be mandated as a basis for national or regional eInvoicing initiatives.
-
Procurement agencies can use them as basis for moving all invoices into electronic form. The flexibility of the specifications allows the buyers to automate processing of invoices gradually, based on different sets of identifiers or references, based on a cost/benefit approach.
-
SME can offer their trading partners the option of exchanging standardised documents in a uniform way and thereby move all invoices/credit notes into electronic form.
-
Large companies can implement these transactions as standardised documents for general operations and implement custom designed bi-lateral connections for large trading partners.
-
Supports customers with need for more complex interactions.
-
Can be used as basis for restructuring of in-house processes of invoices.
-
Significant saving can be realised by the procuring agency by automating and streamlining in-house processing. The accounting can be automated significantly, approval processes simplified and streamlined, payment scheduled timely and auditing automated.
3. Parties and roles
The diagram below shows the roles involved in the invoice and credit note transactions. The customer and invoice receiver is the same entity, as is the supplier and the invoice sender.
3.1. Parties
- Customer
-
The customer is the legal person or organisation who is in demand of a product or service. Examples of customer roles: buyer, consignee, debtor, contracting authority.
- Supplier
-
The supplier is the legal person or organisation who provides a product or service.
- Il Beneficiario
-
Il beneficiario è una persona, istituto bancario o entità di business alla quale si effettua il pagamento (es. factoring).
- Rappresentante Fiscale
-
In alcuni scenari di business, le aziende che commerciano oltre confine sono tenute secondo le autorità fiscali locali a nominare un rappresentante fiscale. Sono comprese le aziende extra-EU che operano in Europa, gli importatori in EU e i commercianti.
I rappresentanti fiscali sono responsabili per la gestione corretta e la regolarizzazione dell’IVA per conto delle aziende, in linea con le normative locali. Un rappresentante fiscale è considerato come l’agente locale del commerciante. In molti casi, il rappresentante fiscale è ritenuto responsabile in solido per le tasse del commerciante.
- Soggetto Emittente
-
Un soggetto terzo (intermediario) che emette fattura per conto del cedente / prestatore.
- Vettore
-
Il vettore è la persona giuridica o organizzazione che consegna la merce al destinatario ed è responsabile del suo trasporto.
3.2. Roles
- Creditor
-
One to whom a debt is owe. The party that claims the payment and is responsible for resolving billing issues and arranging settlement. The party that sends the invoice or credit note. 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 or credit note. Also known as invoicee, accounts payable, or buyer.
4. Business processes
4.1. General invoicing process
The invoicing process includes issuing and sending the invoice and the credit note from the supplier to the customer and the reception and handling of the same at the customer’s site.
The invoicing process is shown in this work flow:
-
A supplier issues and sends an invoice to a customer. The invoice refers to one order and a specification of delivered goods and services.
An invoice may also refer to a contract or a frame agreement. The invoice may specify articles (goods and services) with article number or article description.
-
The customer receives the invoice and processes it in the invoice control system leading to one of the following results:
-
The customer fully approves the invoice, posts it in the accounting system and passes it on to be paid.
-
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.
This profile covers the following invoice processes:
| P1 |
Invoicing of deliveries of goods and services against purchase orders, based on a contract |
| P2 |
Invoicing deliveries of goods and services based on a contract |
| P3 |
Invoicing the delivery of an incidental purchase order |
| P4 |
Pre-payment |
| P5 |
Spot payment |
| P6 |
Payment in advance of delivery |
| P7 |
Invoices with references to a despatch advice |
| P8 |
Invoices with references to a despatch advice and a receiving advice |
| P9 |
Credit notes or invoices with negative amounts, issued for a variety of reasons including the return of empty packaging |
5. Invoice functionality
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
-
VAT reporting
-
Auditing
-
Payment
In aggiunta alle funzioni core sono disponibili specifiche funzionalità domestiche necessarie alle imprese individuali e professionisti, tra cui le principali sono:
-
Ritenuta d’acconto
-
Rivalsa Cassa previdenziale
-
Marca da Bollo
-
Scissione dei pagamenti (Split 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.
Please also see Invoice and credit note business requirements for further details.
Explicit support for the following functions (but not limited to) is out of scope:
-
Inventory management
-
Delivery processes
-
Customs clearance
-
Marketing
-
Reporting
5.1. Accounting
Recording a business transaction into the financial accounts of an organization is one of the main objectives of the invoice. According to financial accounting best practice and VAT rules every Taxable person shall keep accounts in sufficient detail for VAT to be applied and its application checked by the tax authorities. For that reason, an invoice shall provide for the information at document and line level that enables booking on both the debit and the credit side.
Detailed requirements for supporing accounting functionality can be found at Accounting requirements
5.2. Invoice verification
This process forms part of the Buyer’s internal business controls. The invoice shall refer to an authentic commercial transaction. Support for invoice verification is a key function of an invoice. The invoice should provide sufficient information to look up relevant existing documentation, electronic or paper, for example, and as applicable:
-
the relevant purchase order
-
the contract
-
the call for tenders, that was the basis for the contract
-
the Buyer’s reference
-
the confirmed receipt of the goods or services
-
delivery information
An invoice should also contain sufficient information that allows the received invoice to be transferred to a responsible authority, person or department, for verification and approval.
Detailed requirements for supporing accounting functionality can be found at Invoice verification requirements
5.3. Auditing
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:
-
identification of the relevant Buyer and Seller
-
identification of the products and services traded, including description, value and quantity
-
information for connecting the invoice to its payment
-
information for connecting the invoice to relevant documents such as a contract and a purchase order
Detailed requirements for supporing accounting functionality can be found at Auditing requirements
5.4. VAT Reporting
The invoice is used to carry VAT related information from the Seller to the Buyer to enable the Buyer and Seller to correctly handle VAT booking and reporting. An invoice should contain sufficient information to enable the Buyer and any auditor to determine whether the invoice is correct from a VAT point of view.
The invoice shall allow the determination of the VAT regime, the calculation and description of the tax, in accordance with the Directive 2006/112/EC and subsequent amendments.
Detailed requirements for supporing accounting functionality can be found at VAT reporting requirements
5.5. Payment
An invoice represents a claim for payment. The issuance of an invoice may take place either before or after the payment is carried out. When an invoice is issued before payment it represents a request to the Buyer to pay, in which case the invoice commonly contains information that enables the Buyer, in the role of a debtor, to correctly initiate the transfer of the payment, unless that information is already agreed in prior contracts or by means of payment instructions separately lodged with the Buyer.
If an invoice is issued after payment, such as when the order process included payment instructions or when paying with a credit card, online or telephonic purchases, the invoice may contain information about the payment made in order to facilitate invoice to payment reconciliation on the Buyer side. An invoice may be partially paid before issuing such as when a pre-payment is made to confirm an order.
Invoices, conformant with this specification should identify the means of payment for settlement of the invoice and clearly state what payment amount is requested. They should provide necessary details to support bank transfers in accordance with the Single Euro Payments Area (SEPA) for payments in Euro and the relevant national payment practices for other currencies. Payments by means of Credit Transfer, Direct debit, and Payment Card are in scope.
Detailed requirements for supporing accounting functionality can be found at Payment requirements
5.6. Negative invoices and credit notes
In line with requirements of EN 16931 this BIS supports negative grand totals. This represents a significant change in comparison to OpenPEPPOL’s previous specifications where invoices and credit notes have non-negative total.
The argument for negative invoices is to open up for a wider spectrum of invoicing processes.
Examples of such processes are
-
Preliminary (estimated) consumption invoice that is balanced out in a later meter-based invoice;
-
Pre-payment (with or without VAT) is settled through a final invoice; and
-
Some user communities prefer to use negative invoice rather than credit note when correcting transactions.
| Buyers who value automatic matching of e-invoices to orders or invoicing objects may wish to limit the areas and situations where complex transactions can be accepted and voice their requirements at time of procurement. |
The decision has the following implications on the transaction format:
-
The invoice (now with “negative invoice capacity”) can function as an alternative to the credit note. Invoice-generating systems may implement either option, while invoice-receiving systems have to support both of them.
-
The transaction format for credit note has to be designed to accommodate for negative grand total, as well; this is because an entire negative invoice may have to be balanced out by means of a credit note.
Attention is drawn to the intrinsic differences between credit note and negative invoice when it comes to convey crediting information.
Unresolved directive in C:/Users/anbubici/OneDrive - Engineering Ingegneria Informatica S.p.A/Desktop/PEPPOL DOCS/AGID-PEPPOL-DOCS/docs/src/main/webapp/peppol-bis-invoice-3-ENG/guide/transaction-spec/functionality/_negative-invoices.adoc - include::../../syntax/negative-invoices.adoc[]
5.7. Ritenuta d’acconto (estensione)
La sezione ritenuta d’acconto serve ad evidenziare:
-
una trattenuta Irpef (per i redditi delle persone fisiche) o Ires (per le persone giuridiche: società) che viene effettuata sul totale imponibile della fattura inviata al Cliente da parte del Fornitore, che agisce come sostituto d’imposta;
-
una trattenuta previdenziale che viene effettuata sul totale imponibile della fattura inviata al Cliente da parte del Fornitore che si occuperà del successivo riversamento all’Ente previdenziale di riferimento.
Entrambe le tipologie di ritenuta d’acconto possono essere contenute nella medesima fattura.
Il tipo di ritenuta applicata deve essere indicata in testata al documento in una estensione UBL separata. Se non viene indicato alcun tipo di ritenuta ed è stata specificata almeno una ritenuta, il valore predefinito sarà RT01 per le persone fisiche ed RT02 per quelle giuridiche.
Si raccomanda l’uso di questa estensione UBL per specificare esplicitamente il tipo di ritenuta/e ove applicate.
|
L’importo complessivo delle ritenute va ricompreso nel valore inserito in cbc:PrepaidAmount. Si evidenzia che il cbc:PrepaidAmount non è supportato in FatturaPA ma viene utilizzato per valorizzare correttamente il dato cbc:PayableAmount (BT-115 Amount due for payment) che è obbligatorio per la EN 16931. |
L’ExtensionURI dovrà contenere il prefisso 'urn:fdc:agid.gov.it:fatturapa:TipoRitenuta' e il numero di occorrenza della ritenuta '::n'.
<ext:UBLExtension>
<ext:ExtensionURI>urn:fdc:agid.gov.it:fatturapa:TipoRitenuta::1</ext:ExtensionURI>
<ext:ExtensionContent>
<cbc:TypeCode>RT01</cbc:TypeCode>
</ext:ExtensionContent>
</ext:UBLExtension>
<ext:UBLExtension>
<ext:ExtensionURI>urn:fdc:agid.gov.it:fatturapa:TipoRitenuta::2</ext:ExtensionURI>
<ext:ExtensionContent>
<cbc:TypeCode>RT04</cbc:TypeCode>
</ext:ExtensionContent>
</ext:UBLExtension>Nella Fattura è possibile specificare una o più ritenute nell’elemento WithholdingTaxTotal a livello di testata, come nell’esempio riportato.
<!-- Ritenuta ENASARCO su imponibile prestazione -->
<cac:WithholdingTaxTotal>
<cbc:TaxAmount currencyID="EUR">82.50</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">1000.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">82.50</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>8.25</cbc:Percent><!-- 50% dell'aliquota 16.50% -->
<cac:TaxScheme>
<cbc:ID>SWT</cbc:ID>
<cbc:TaxTypeCode>R</cbc:TaxTypeCode><!-- provvigioni corrisposte ad agente o rappresentante di commercio plurimandatario -->
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
</cac:WithholdingTaxTotal>Nella Fattura è possibile specificare che una riga sia soggetta a ritenuta, come nell’esempio riportato.
<cac:InvoiceLine>
<!-- ... -->
<cac:Item>
<!-- ... -->
<cac:AdditionalItemProperty>
<cbc:Name>RITENUTA</cbc:Name>
<cbc:Value>SI</cbc:Value>
</cac:AdditionalItemProperty>
</cac:Item>
<!-- ... -->
</cac:InvoiceLine>Nella Nota di Credito UBL 2.1 non è presente l’elemento WithholdingTaxTotal per indicare le ritenute applicate, ma è possibile includerlo come estensione UBL in testata al documento, come nell’esempio riportato.
<ext:UBLExtension>
<ext:ExtensionURI>urn:fdc:agid.gov.it:fatturapa:Ritenuta</ext:ExtensionURI>
<ext:ExtensionContent>
<cac:WithholdingTaxTotal>
<cbc:TaxAmount currencyID="EUR">486.25</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxAmount currencyID="EUR">486.25</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>SWT</cbc:ID>
<cbc:TaxTypeCode>A</cbc:TaxTypeCode>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
<cac:TaxSubtotal>
<cbc:TaxAmount currencyID="EUR">200.25</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>4</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>SWT</cbc:ID>
<cbc:TaxTypeCode>B</cbc:TaxTypeCode>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
</cac:WithholdingTaxTotal>
</ext:ExtensionContent>
</ext:UBLExtension>5.8. Rivalsa Cassa previdenziale (CIUS domestica)
La Cassa previdenziale viene trattata come maggiorazione a livello di documento utilizzando il cac:AllowanceCharge (BG-21 Document level charge).
La base imponibile del contributo viene inserita nel cbc:BaseAmount (BT-100 Document level charghe base amount).
L’aliquota nel cbc:MultiplierFactorNumeric (BT-101 Document level charge percentage), l’importo del contributo nel cbc:Amount (BT-99 Document level charge amount).
Le informazioni tipo cassa (FPA 2.1.1.7.1), ritenuta (FPA 2.1.1.7.6) e natura (FPA 2.1.1.7.7) vengono concatenate con il simbolo "#" nel cbc:AllowanceChargeReason (BT-104 Document level charge reason).
Il cbc:AllowanceChargeReasonCode (BT-105 Document level charge reason code) viene valorizzato con "ZZZ".
Le informazioni sull’IVA vengono compilate secondo la necessità.
L’esempio si riferisce ad una prestazione di 1.000 euro soggetta IVA ordinaria con aliquota del contributo pari al 4%.
<cac:AllowanceCharge>
<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
<cbc:AllowanceChargeReasonCode>ZZZ</cbc:AllowanceChargeReasonCode>
<cbc:AllowanceChargeReason>TC02#SI#</cbc:AllowanceChargeReason>
<cbc:MultiplierFactorNumeric>4</cbc:MultiplierFactorNumeric>
<cbc:Amount currencyID="EUR">40.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">1000.00</cbc:BaseAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>22</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>L’esempio si si riferisce ad una prestazione di 1.000 euro non soggetta ad IVA con aliquota del contributo pari al 4%.
<cac:AllowanceCharge>
<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
<cbc:AllowanceChargeReasonCode>ZZZ</cbc:AllowanceChargeReasonCode>
<cbc:AllowanceChargeReason>TC04#SI#N2.2</cbc:AllowanceChargeReason>
<cbc:MultiplierFactorNumeric>4</cbc:MultiplierFactorNumeric>
<cbc:Amount currencyID="EUR">40.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">1000.00</cbc:BaseAmount>
<cac:TaxCategory>
<cbc:ID>E</cbc:ID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>5.9. Imposta di Bollo (CIUS domestica)
L’indicazione del bollo virtuale è operata sia in fattura che su nota di credito come maggiorazione a livello di testata del documento a mezzo dell’utilizzo della struttura cac:AllowanceCharge (BG-21 Document level charge) indicando:
-
l’elemento cbc:ChargeIndicator pari a “true”;
-
l’elemento cbc:AllowanceChargeReasonCode (BT-105 Document level charge reason code) pari a “SAE”;
-
l’elemento cbc:AllowanceChargeReason (BT-104 Document level charge reason) con la stringa “BOLLO”;
-
l’elemento cbc:Amount (BT-99 Document level charge amount) con il valore 0;
-
l’elemento cac:TaxCategory/cbc:ID (BT-95 Document level charge VAT category code) posto a Z (zero).
Qualora non si intenda effettuare la rivalsa del bollo non è richiesto l’inserimento di una specifica riga ad essa riferita.
<ubl:Invoice>
...
<cac:AllowanceCharge>
<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
<cbc:AllowanceChargeReasonCode>SAE</cbc:AllowanceChargeReasonCode>
<cbc:AllowanceChargeReason>BOLLO</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">0</cbc:Amount>
<cac:TaxCategory>
<cbc:ID>Z</cbc:ID>
<cbc:Percent>0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">0.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">0</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>E</cbc:ID>
<cbc:Percent>0</cbc:Percent>
<cbc:TaxExemptionReasonCode>vatex-eu-132</cbc:TaxExemptionReasonCode>
<cbc:TaxExemptionReason>N4</cbc:TaxExemptionReason>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">0.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">0.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>Z</cbc:ID>
<cbc:Percent>0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
</cac:TaxTotal>
<cac:LegalMonetaryTotal>
<cbc:LineExtensionAmount currencyID="EUR">100.00</cbc:LineExtensionAmount>
<cbc:TaxExclusiveAmount currencyID="EUR">100.00</cbc:TaxExclusiveAmount>
<cbc:TaxInclusiveAmount currencyID="EUR">100.00</cbc:TaxInclusiveAmount>
<cbc:ChargeTotalAmount currencyID="EUR">0.00</cbc:ChargeTotalAmount>
<cbc:PayableAmount currencyID="EUR">100.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>5.9.1. Rivalsa del bollo
Qualora il fornitore voglia effettuare la rivalsa del bollo sul cliente deve inserire una riga recante:
-
l’elemento cac:Item/cbc:Description (BT-154 Item description) valorizzato a “Rivalsa Bollo”;
-
gli elementi cac:Price/cbc:PriceAmount (BT-146 Item net price) e cac:AllowanceCharge/cbc:BaseAmount (BT-148 Item gross price) valorizzati a
-
2.00 in caso di fattura (vedi esempi Fattura n. 04_FT, 14_FT, 17_FT e 30_FT).
-
- 2.00 in caso di nota di credito (vedi esempio Nota di Credito n. 04_NC).
-
La riga di rivalsa ha la medesima natura della prestazione sulla quale la rivalsa viene applicata.
5.9.2. Restituzione del bollo
Qualora il fornitore, in sede di emissione di una nota di credito, voglia rimborsare il bollo su cui ha effettuato rivalsa in sede di emissione della fattura deve inserire una riga recante:
-
l’elemento cac:Item/cbc:Description (BT-154 Item description) valorizzato a “Rimborso Bollo”;
-
gli elementi cac:Price/cbc:PriceAmount (BT-146 Item net price) e cac:AllowanceCharge/cbc:BaseAmount (BT-148 Item gross price) valorizzati a 2.00 (vedi esempio Nota di Credito n. 05_NC).
La riga di rimborso ha la medesima natura della prestazione sulla quale la rivalsa era stata applicata.
5.10. Scissione dei pagamenti - Split payment (CIUS domestica)
La scissione dei pagamenti o split payment è un regime particolare che stabilisce che il debitore dell’IVA sia il cessionario/committente anziché, come avviene normalmente, il cedente/prestatore.
Per supportare questo particolare caso si valorizza il cac:TaxCategory/cbc:ID (BT-118 VAT Category code) utilizzando il TaxCategory 'B' (Transferred VAT) secondo la codifica UN/ECE 5305.
|
Il valore dell’IVA split va ricompreso nel valore inserito in cbc:PrepaidAmount. Si evidenzia che il cbc:PrepaidAmount non è supportato in FatturaPA ma viene utilizzato per valorizzare correttamente il dato cbc:PayableAmount (BT-115 Amount due for payment) che è obbligatorio per la EN 16931. |
L’esempio riportato è relativo alla fattura emessa ad una PA soggetta alla scissione pagamento.
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>B</cbc:ID>
<cbc:Percent>22</cbc:Percent>
</cac:TaxCategory>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>
<cac:LegalMonetaryTotal>
<cbc:TaxExclusiveAmount currencyID="EUR">100.00</cbc:TaxExclusiveAmount>
<cbc:TaxInclusiveAmount currencyID="EUR">122.00</cbc:TaxInclusiveAmount>
<cbc:PrepaidAmount currencyID="EUR">22.00</cbc:PrepaidAmount>
<cbc:PayableAmount currencyID="EUR">100.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>6. Invoice and credit note business requirements
The table below gives an overview of the business requirements from CEN TC434 supported by this BIS:
- Legend
-
Requirements with an id Rnn are from EN 16931 (Example R19).
| Id | Requirement (depending, as applicable, on the respective business case) |
|---|---|
R1 |
information at document level that enables the identification of the Payee, if different from the Seller |
R2 |
information at document level that enables booking on both the debit and the credit side |
R3 |
information at invoice line level that enables booking on the debit side |
R4 |
Buyer-specific booking information (account numbers) |
| Id | Requirement (depending, as applicable, on the respective business case) |
|---|---|
R5 |
information to trace to a single related purchase order from the document level |
R6 |
information to trace to a single related purchase order line from the invoice line |
R7 |
information to trace to a single contract and the underlying call for tenders from the document level |
R8 |
a reference supplied by the Buyer at document level |
R9 |
information to trace to a single despatch advice from the document level |
R10 |
information to trace to a single receiving advice from the document level |
R11 |
information to trace to a related invoice to be corrected from the document level |
R13 |
information to allow an invoice and related documents to be transferred to a responsible authority, entity, person or department, for verification and approval |
R14 |
information about net price and the quantity on which the price is based at invoice line level, additional information such as gross price and price discount may be added |
R15 |
descriptive and coded information about allowances and charges at both document level and at invoice line level |
R16 |
information about charges, (non-VAT-)taxes, duties and levies, with their VAT information, that are not included in the line amounts at document level |
R17 |
information about charges, (non-VAT-)taxes, duties and levies that compose the taxable amount and are not included in the unit price at separate invoice lines, with a proper identification and/or description |
R18 |
information about charges at invoice line level as part of the line amount |
R19 |
the amounts of allowances and charges at document and invoice line level |
R20 |
textual descriptions of invoiced goods and services at invoice line level |
R21 |
identification of invoiced goods and services by means of a Seller’s item number at invoice line level |
R22 |
identification of invoiced goods and services by means of a Buyer’s item number at invoice line level |
R23 |
identification of invoiced goods and services by means of a qualified general item identifier at invoice line level as agreed by the Buyer and the Seller |
R24 |
classification of invoiced goods and services by means of applicable classification identifiers and schema reference as agreed between the Seller and the Buyer at invoice line level |
R25 |
information about returned and credited returnable assets or packages, such as pallets, and package charges, stated as normal invoice lines |
R26 |
information about returnable asset charges, stated as normal invoice lines |
R27 |
information about returned goods, stated as normal invoice lines |
R28 |
descriptive information about attributes of goods and services at invoice line level |
R29 |
information about the country of origin of goods and services at invoice line level |
R30 |
an invoice line period at invoice line level |
R31 |
one delivery date at document level |
R32 |
one delivery location or address at document level |
R33 |
identification of the invoiced object at document and line level |
R34 |
a delivery/invoice period at document level |
R35 |
attached documents of a limited set of file types |
R36 |
multiple attached or referenced documents at document level |
R37 |
a VAT category and rate at invoice line level |
R38 |
VAT totals per category at document level |
R39 |
a quantity and a net amount (exclusive of VAT) at invoice line level |
R40 |
all amounts at document and invoice line level that make up the invoice total amount and the amount due for payment |
R41 |
Reference to a sales order, issued by the Seller at document level |
R42 |
Allowance/charge percentage and base amount at document and invoice line level |
R44 |
Information to allow automated validation of a received electronic invoice |
| Id | Requirement (depending, as applicable, on the respective business case) |
|---|---|
R45 |
information to determine the requirements of the applicable VAT legislation in force and the calculation and reporting thereof; |
R46 |
information on the date the VAT is liable at document level; |
R47 |
the necessary elements for national legal VAT requirements that apply for invoices issued to national and foreign Buyers, such as the legal registration status of the Seller; |
R48 |
information to support the following VAT use cases:
|
R49 |
the total VAT amount at document level; |
R50 |
total taxable amount per VAT rate at document level; |
R51 |
any additional information required to support the exemption evidence in case VAT is not charged based on an exemption reason at document and at invoice line level; |
R52 |
the legal registration number and the VAT registration number of the Seller and Buyer and the VAT registration number of the Tax representative of the Supplier; |
R53 |
the official postal address of the Buyer, Seller and Tax representative of the Supplier and their place of business and registered office; |
R54 |
the invoice currency and the VAT accounting currency at document level if different from the invoice currency; |
R55 |
codes for exemption reasons at document and invoice line level. |
| Id | Requirement (depending, as applicable, on the respective business case) |
|---|---|
R56 |
sufficient information to support the auditing process with regard to:
|
R57 |
identification of the parties that fulfil the following roles at the invoice level, including their legal name and address:
|
| Id | Requirement (depending, as applicable, on the respective business case) |
|---|---|
R58 |
identification of the means of settlement; |
R59 |
the requested amount due for payment; |
R60 |
the date on which payment is due; |
R61 |
necessary details to support bank transfers in accordance with SEPA and national systems; |
R62 |
a reference number and any additional reference data to be included in the payment; |
R63 |
reference number and any additional reference data to be included in the payment, in order to relate the payment to the invoice; |
R64 |
information for relating an invoice to a payment card used for settlement; |
R65 |
basic information to support national payment systems for use in domestic trade; |
R66 |
information about the amount that was pre-paid; |
R67 |
invoices that have a total amount of zero; |
R68 |
invoices that have an amount to pay of zero; |
R69 |
necessary details to support direct debits. |
R70 |
pre-payment invoices |
7. Semantic datatypes
Semantic data types are used to bridge the gap between the semantic concepts expressed by the information elements defined in the semantic model from EN 16931 and the technical implementation. The semantic data types define the allowed value domain for the content, and any additional information components (attributes) needed in order to ensure its precise interpretation.
| The details of the technical implementation can be found in [Detailed UBL message guideline] |
7.1. Primitive types
Semantic data type content may be of the following primitive types. These primitive types were taken from ISO 15000-5:2014, Annex A.
| Primitive type | Definition |
|---|---|
Binary |
A set of finite-length sequences of binary digits. |
Date |
Time point representing a calendar day on a time scale consisting of an origin and a succession of calendar ISO 8601:2004. |
Decimal |
A subset of the real numbers, which can be represented by decimal numerals. |
String |
A finite sequence of characters. |
7.2. Semantic data types
The different semantic data types are described in the tables below, where various features such as attributes, format, and decimals as well as the basic type are defined for each semantic data type. They are based on ISO 15000-5:2014.
When used in an instance of an invoice, each data element will contain data. In the below tables this is identified as the “content”. Whenever a business term is used this term shall always have content and therefore the content is always mandatory.
7.2.1. Amount
An amount states a numerical monetary value. The currency of the amount is defined as a separate business term.
| Amount is floating up to two fraction digits. |
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
Decimal |
10000.25 |
7.2.2. Unit Price Amount
A unit price amount states a numerical monetary amount value for data elements that contain item prices that may be multiplied by item quantities. The currency of the amount is defined as a separate business term.
| Unit price amount does not set restrictions on number of decimals, as contrast to the Amount type |
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
Decimal |
10000.1234 |
7.2.3. Percentage
Percentages are given as fractions of a hundred (per cent) e.g. the value 34.78 % in percentage terms is given as 34.78.
| No restriction on number of decimals for percentages. |
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
Decimal |
34.7812 |
7.2.4. Quantity
Quantities are used to state a number of units such as for items. The code for the Unit of Measure is defined as a separate business term.
| No restriction on number of decimals for quantities. |
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
Decimal |
10000.1234 |
7.2.5. Code
Codes are used to specify allowed values in elements as well as for lists of options. Code is different from Identifier in that allowed values have standardized meanings that can be known by the recipient.
| Codes shall be entered exactly as shown in the selected code list of the applicable syntax. |
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
String |
Abc123 |
7.2.6. Identifier
Identifiers (IDs) are keys that are issued by the sender or recipient of a document or by a third party.
| The use of the attributes is specified for each information element. |
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
String |
abc:123-DEF |
Scheme identifier |
Conditional |
String |
GLN |
Scheme version identifier |
Conditional |
String |
1.0 |
7.2.7. Date
Dates shall be in accordance to the “Calendar date complete representation” as specified by ISO 8601:2004, format YYYY-MM-DD.
| Dates shall not include timezone information. |
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
Date |
2017-12-01 |
7.2.8. Document Reference
Document Reference Types are identifiers that were assigned to a document or document line by the Buyer, the Seller or by a third party.
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
String |
abc:123-DEF |
7.2.9. Text
Text is the actual wording of anything written or printed. Line breaks in the text may be present, and any line breaks should be preserved and respected by the receiver’s system
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
String |
5% allowance when paid within 30 days |
7.2.10. Binary objects
Binary objects can be used to describe files which are transmitted together with the Invoice. The attachment functionality is not intended for of including a copy of the invoice in an image format (such as PDF). Attaching an invoice copy is not in compliance with this specification.
Attachments shall be transmitted together with the Invoice. The binary object has two supplementary components: a Mime Code, which specifies the Mime type of the attachment and a Filename that is provided by (or on behalf of) the sender of the invoice or credit note.
| Component | Use | Primitive Type | Example |
|---|---|---|---|
Content |
Mandatory |
Binary |
QmFzZTY0IGNvbnRlbnQgZXhhbXBsZQ== |
Mime Code |
Mandatory |
String |
image/jpeg |
Filename |
Mandatory |
String |
drawing5.jpg |
A receiver of an invoice or credit note, shall accept and process attachments that are according to the code list Media type code per i documenti allegati
8. Imposta sul valore aggiunto (IVA)
I capitoli seguenti descrivono le diverse informazioni in materia dell’IVA che possono essere fornite in una fattura o in una nota di credito PEPPOL.
Si consiglia di consultare anche i VAT category codes per dettagli sulla codifica delle categorie IVA e il Calcolo dell’IVA per una rappresentazione più dettagliata ed esempi su come eseguire i calcoli nel riepilogo IVA.
8.1. Informazioni IVA su riga
8.1.1. Regole per la fatturazione dall’estero (cross-border)
Per ogni riga della fattura deve essere indicato il codice della categoria IVA nel cac:ClassifiedTaxCategory/cbc:ID (BT-151 Invoiced item VAT category code).
Per le categorie IVA è Z, E, G, K e AE il cac:ClassifiedTaxCategory/cbc:Percent (BT-152 Invoiced item VAT rate) va posto uguale a 0.
8.1.2. Regole per la fatturazione domestica
Per ogni riga della fattura deve essere indicato il codice della categoria IVA nel cac:ClassifiedTaxCategory/cbc:ID (BT-151 Invoiced item VAT category code).
Per le categorie IVA Z, E, G, K e AE il cac:ClassifiedTaxCategory/cbc:Percent (BT-152 Invoiced item VAT rate) va posto uguale a 0.
Per le categorie IVA S e B l’aliquota IVA va inserita nel cac:ClassifiedTaxCategory/cbc:Percent (BT-152 Invoiced item VAT rate).
La gestione della natura della riga è operata a mezzo dell’utilizzo del cac:AdditionalItemProperty/cbc:Name (BT-160) e cac:AdditionalItemProperty/cbc:Value (BT-161), valorizzando il cbc:name con la stringa “NATURA” ed il cbc:value con il codice natura secondo le specifiche FatturaPA.
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID>
<cbc:InvoicedQuantity unitCode="C62">5</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">100.00</cbc:LineExtensionAmount>
<cac:Item>
<cbc:Name>Importo degli imballaggi</cbc:Name>
<cac:ClassifiedTaxCategory>
<cbc:ID>Z</cbc:ID>
<cbc:Percent>0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:ClassifiedTaxCategory>
<cac:AdditionalItemProperty>
<cbc:Name>NATURA</cbc:Name>
<cbc:Value>N1</cbc:Value>
</cac:AdditionalItemProperty>
</cac:Item>
<cac:Price>
<cbc:PriceAmount currencyID="EUR">20.00</cbc:PriceAmount>
<cbc:BaseQuantity unitCode="C62">1</cbc:BaseQuantity>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">0.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">20.00</cbc:BaseAmount>
</cac:AllowanceCharge>
</cac:Price>
</cac:InvoiceLine>8.1.3. Indicazioni per la fatturazione verso l’estero
Per la fatturazione verso l’estero verificare con l’acquirente l’eventuale presenza di CIUS.
Per approfondimenti consultare il seguente link.
8.2. Sconti e maggiorazioni a livello di testata
Per ogni sconto/maggiorazione deve essere indicato il codice della categoria IVA nel cac:ClassifiedTaxCategory/cbc:ID (BT-102 Document level charge VAT category code/BT-95Document level allowance VAT category code).
Per le categorie IVA è Z, E, G, K e AE il cac:ClassifiedTaxCategory/cbc:Percent (BT-103 Document level charge VAT rate/BT-96 Document level allowance VAT rate) va posto uguale a 0.
Per le categorie IVA S e B, l’aliquota IVA va inserita nel cac:ClassifiedTaxCategory/cbc:Percent (BT-103 Document level charge VAT rate/BT-96 Document level allowance VAT rate).
| La sezione è utilizzata solo per la fatturazione domestica per Bollo (vedi paragrafo 4.9) e Rivalsa Cassa Previdenziale (vedi paragrafo 4.8). Per gli sconti e maggiorazioni a livello di testata che non incidono sull’imponibile vedasi 10.5.Sconti e maggiorazioni. |
8.3. Riepiloghi IVA
8.3.1. Regole per la fatturazione dall’estero (cross-border)
La gestione della natura dell’operazione (FPA 2.2.2.2 Natura) per le fatture dall’estero è operata a mezzo dell’utilizzo di:
-
cac:TaxCategory/cbc:ID (BT-118 VAT category code);
-
cbc:TaxExemptionReasonCode (BT-121 VAT exemption reason code);
| La fattura non può contenere più di un TaxSubtotal. |
8.3.2. Regole per la fatturazione domestica
La gestione della natura dell’operazione (FPA 2.2.2.2 Natura) per le fatture domestiche è operata a mezzo dell’utilizzo di:
-
cac:TaxCategory/cbc:ID (BT-118 VAT category code);
-
cbc:TaxExemptionReasonCode (BT-121 VAT exemption reason code);
-
cbc:TaxExemptionReason (BT-120 VAT exemption reason text), in cui viene inserita il codice natura secondo le specifiche FatturaPA ed il Riferimento Normativo.
| Trattasi di CIUS domestica (DC) |
Deve essere fornito un solo riepilogo IVA per ogni combinazione distinta di categoria e aliquota IVA sia a livello di riga che negli sconti e maggiorazioni a livello di testata. Per alcune categorie IVA, l’aliquota deve essere posta a zero e quindi non viene utilizzata in questi casi per raggruppare il riepilogo IVA.
Per l’aliquota dell’IVA devono essere considerati solo i decimali significativi, ovvero qualsiasi differenza nei decimali non deve determinare differenti riepiloghi IVA.
| Non è possibile inserire nella medesima fattura operazioni con il medesimo Tax Category ID (BT-118 VAT category code) e natura differente. |
Esempio:
Riga 1 della fattura ha categoria IVA = S e aliquota IVA = 25,00
Riga 2 della fattura ha categoria IVA = S e aliquota IVA = 25,00
Questo dovrebbe originare un singolo riepilogo IVA.
Per altri dettagli vedi anche il paragrafo 9.4. Calcolo dell’IVA.
Caso 1 - natura diversa da N1 – esempio riferito ad un’operazione in regime di reverse charge
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">0.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">0.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>AE</cbc:ID>
</cac:TaxCategory>
<cbc:TaxExemptionReasonCode>vatex-eu-ae</cbc:TaxExemptionReasonCode>
<cbc:TaxExemptionReason>N6.3#Art.16,co.6,lett.a (prestazioni di servizi rese dai subappaltatori nel settore edilizio)</cbc:TaxExemptionReason>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>
<!-- ... -->
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID>
<cbc:InvoicedQuantity unitCode="C62">1</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">100.00</cbc:LineExtensionAmount>
<cac:Item>
<cbc:Description>Inversione contabile</cbc:Description>
<cbc:Name>Subappalto nel settore edile</cbc:Name>
<cac:ClassifiedTaxCategory>
<cbc:ID>AE</cbc:ID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:ClassifiedTaxCategory>
<cac:AdditionalItemProperty>
<cbc:Name>NATURA</cbc:Name>
<cbc:Value>N6.3</cbc:Value>
</cac:AdditionalItemProperty>
</cac:Item>
<cac:Price>
<cbc:PriceAmount currencyID="EUR">100.00</cbc:PriceAmount>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">0.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">100.00</cbc:BaseAmount>
</cac:AllowanceCharge>
</cac:Price>
</cac:InvoiceLine>Caso 2 - natura N1 – esempio riferito ad un’operazione esclusa
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">0.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">0.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>Z</cbc:ID>
<cbc:Percent>0</cbc:Percent>
</cac:TaxCategory>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>
<!-- ... -->
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID>
<cbc:InvoicedQuantity unitCode="C62">5</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">100.00</cbc:LineExtensionAmount>
<cac:Item>
<cbc:Name>Importo degli imballaggi</cbc:Name>
<cac:ClassifiedTaxCategory>
<cbc:ID>Z</cbc:ID>
<cbc:Percent>0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:ClassifiedTaxCategory>
<cac:AdditionalItemProperty>
<cbc:Name>NATURA</cbc:Name>
<cbc:Value>N1</cbc:Value>
</cac:AdditionalItemProperty>
</cac:Item>
<cac:Price>
<cbc:PriceAmount currencyID="EUR">20.00</cbc:PriceAmount>
<cbc:BaseQuantity unitCode="C62">1</cbc:BaseQuantity>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">0.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">20.00</cbc:BaseAmount>
</cac:AllowanceCharge>
</cac:Price>
</cac:InvoiceLine>8.3.3. Indicazioni per la fatturazione verso l’estero
Per la fatturazione verso l’estero verificare con l’acquirente l’eventuale presenza di CIUS.
Per approfondimenti consultare il seguente link.
8.4. Totale IVA
Il totale IVA cbc:TaxAmount (BT-110) è la somma delle imposte dei singoli riepiloghi cbc:TaxAmount (BT-117)
8.5. Data operazione ed esigibilità IVA
La gestione della data operazione e dell’esigibilità IVA è operata a mezzo dell’utilizzo di:
-
cbc:IssueDate (BT-2 Invoice issue date);
-
cac:InvoicePeriod/cbc:DescriptionCode (BT-8 Value added tax point date code);
-
cbc:ActualDeliveryDate (BT-72 Actual delivery date);
-
cac:TaxCategory/cbc:ID (BT-118 VAT category code);
Si evidenziano 6 casi distinti.
8.5.1. Caso 1 - Esigibilità immediata, data fattura coincide con data operazione
In questo caso il cbc:IssueDate (BT-2 Invoice issue date) viene valorizzato con data fattura/data operazione e il cac:InvoicePeriod/cbc:DescriptionCode (BT-8 Value added tax point date code) viene valorizzato con “3” (ovvero Invoice document issue time).
<cbc:IssueDate>2020-02-07</cbc:IssueDate>
<cac:InvoicePeriod>
<cbc:DescriptionCode>3</cbc:DescriptionCode>
</cac:InvoicePeriod>
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>22</cbc:Percent>
</cac:TaxCategory>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>8.5.2. Caso 2 - Esigibilità immediata, data fattura non coincidente con data operazione
In questo caso il cbc:IssueDate (BT-2 Invoice issue date) viene valorizzato con data fattura, il cac:InvoicePeriod/cbc:DescriptionCode (BT-8 Value added tax point date code) viene valorizzato con “35” (ovvero Delivery date, actual) ed il cbc:ActualDeliveryDate (BT-72 Actual delivery date) viene valorizzato con la data operazione.
<cbc:IssueDate>2020-01-20</cbc:IssueDate>
<!-- ... -->
<cac:InvoicePeriod>
<cbc:DescriptionCode>35</cbc:DescriptionCode>
</cac:InvoicePeriod>
<!-- ... -->
<cac:Delivery>
<cbc:ActualDeliveryDate>2020-01-15</cbc:ActualDeliveryDate>
</cac:Devlivery>
<!-- ... -->
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>22</cbc:Percent>
</cac:TaxCategory>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>8.5.3. Caso 3 - Esigibilità differita, data fattura coincide con data operazione
In questo caso il cbc:IssueDate (BT-2 Invoice issue date) viene valorizzato con data fattura/data operazione e il cac:InvoicePeriod/cbc:DescriptionCode (BT-8 Value added tax point date code) viene valorizzato con “432” (ovvero Paid to date).
<cbc:IssueDate>2020-02-07</cbc:IssueDate>
<!-- ... -->
<cac:InvoicePeriod>
<cbc:DescriptionCode>432</cbc:DescriptionCode>
</cac:InvoicePeriod>
<!-- ... -->
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>22</cbc:Percent>
</cac:TaxCategory>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>8.5.4. Caso 4 - Esigibilità differita, data fattura non coincidente con data operazione
In questo caso il cbc:IssueDate (BT-2 Invoice issue date) viene valorizzato con data fattura, il cac:InvoicePeriod/cbc:DescriptionCode (BT-8 Value added tax point date code) viene valorizzato con “432” (ovvero Paid to date) ed il cbc:ActualDeliveryDate (BT-72 Actual delivery date) viene valorizzato con la data operazione.
<cbc:IssueDate>2020-01-20</cbc:IssueDate>
<!-- ... -->
<cac:InvoicePeriod>
<cbc:DescriptionCode>432</cbc:DescriptionCode>
</cac:InvoicePeriod>
<!-- ... -->
<cac:Delivery>
<cbc:ActualDeliveryDate>2020-01-15</cbc:ActualDeliveryDate>
</cac:Devlivery>
<!-- ... -->
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>22</cbc:Percent>
</cac:TaxCategory>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>8.5.5. Caso 5 – Split payment, data fattura coincide con data operazione
In questo caso il cbc:IssueDate (BT-2 Invoice issue date) viene valorizzato con data fattura/data operazione, il cac:InvoicePeriod/cbc:DescriptionCode (BT-8 Value added tax point date code) è lasciato vuoto e il cac:TaxCategory/cbc:ID (BT-118 VAT category code) viene valorizzato con “B” (ovvero split payment).
<cbc:IssueDate>2020-02-07</cbc:IssueDate>
<!-- ... -->
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>B</cbc:ID>
<cbc:Percent>22</cbc:Percent>
</cac:TaxCategory>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>8.5.6. Caso 6 – Split payment, data fattura non coincidente con data operazione
In questo caso il cbc:IssueDate (BT-2 Invoice issue date) viene valorizzato con la data fattura, il cac:InvoicePeriod/cbc:DescriptionCode (BT-8 Value added tax point date code) è lasciato vuoto, il cbc:ActualDeliveryDate (BT-72 Actual delivery date) viene valorizzato con la data operazione ed il cac:TaxCategory/cbc:ID (BT-118 VAT category code) viene valorizzato con “B” (ovvero split payment).
<cbc:IssueDate>2020-01-20</cbc:IssueDate>
<!-- ... -->
<cac:Delivery>
<cbc:ActualDeliveryDate>2020-01-15</cbc:ActualDeliveryDate>
</cac:Devlivery>
<!-- ... -->
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">100.00</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">22.00</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>B</cbc:ID>
<cbc:Percent>22</cbc:Percent>
</cac:TaxCategory>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxSubtotal>
</cac:TaxTotal>9. Rounding
To minimize the risk of differences due to rounding, the following rules apply:
|
Please also see Calculation for details on how to calculate the different amounts.
10. Calculation
10.1. Calculation of totals
Formulas for the calculations of totals are as follows:
| Business term id | Term name | Calculation |
|---|---|---|
BT-106 |
Sum of invoice line net amounts |
\$sum("BT-131: Invoice line net amount")\$ |
BT-107 |
Sum of allowances on document level |
\$sum("BT-92: Document level allowance amount")\$ |
BT-108 |
Sum of charges on document level |
\$sum("BT-99: Document level charge amount")\$ |
BT-109 |
Invoice total amount without VAT |
\$\ \ \ \ "BT-106: Sum of invoice line net amounts"\$ |
BT-110 |
Invoice total VAT amount |
\$sum("BT-117: VAT category tax amount")\$ |
BT-112 |
Invoice total amount with VAT |
\$\ \ \ \ "BT-109: Invoice total amount without VAT"\$ |
BT-115 |
Amount due for payment |
\$\ \ \ \ "BT-112: Invoice total amount with VAT"\$ |
10.1.1. UBL syntax calculation formulas
The following elements show the legal monetary totals for an invoice or credit note
| Element | Formula |
|---|---|
<cbc:LineExtensionAmount> |
\$sum("cac:InvoiceLine/cbc:LineExtensionAmount")\$ |
<cbc:AllowanceTotalAmount> |
\$sum("cac:AllowanceCharge[ChargeIndicator='false']/cbc:Amount")\$ |
<cbc:ChargeTotalAmount> |
\$sum("cac:AllowanceCharge[ChargeIndicator='true']/cbc:Amount")\$ |
<cbc:TaxExclusiveAmount> |
\$\ \ \ \ "cac:LegalMonetaryTotal/cbc:LineExtensionAmount"\$ |
<cbc:TaxInclusiveAmount> |
\$\ \ \ \ "cac:LegalMonetaryTotal/cbc:TaxExclusiveAmount"\$ |
<cbc:PrepaidAmount> |
Not applicable |
<cbc:PayableRoundingAmount> |
Not applicable |
<cbc:PayableAmount> |
\$\ \ \ \ "cac:LegalMonetaryTotal/cbc:TaxInclusiveAmount"\$ |
10.1.2. Element for rounding amount, the PayableRoundingAmount
It is possible to round the expected payable amount.
The element cac:LegalMonetaryTotal/cbc:PayableRoundingAmount is used for this purpose and is specified on the header level. This value shall be added to the value in cac:LegalMonetaryTotal/cbc:PayableAmount.
Example: Amount 999.81 rounded to 1000. PayableRounding Amount = 0.19
10.2. Calculation on line level
10.2.1. Item net price (BT-146)
If gross price and discount exist, the Item net price has to equal with the item gross price less the item price discount.
Calculation formula:
\$"Item net price" = "Item gross price (BT-148)" - "Item price discount (BT-147)"\$
<cac:Price>
<cbc:PriceAmount currencyID="EUR">410</cbc:PriceAmount>(3)
<cbc:BaseQuantity unitCode="C62">1</cbc:BaseQuantity>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">40</cbc:Amount>(2)
<cbc:BaseAmount currencyID="EUR">450</cbc:BaseAmount>(1)
</cac:AllowanceCharge>
</cac:Price>| 1 | Item gross price |
| 2 | Item price discount |
| 3 | \$"Item price net amount" = "Item gross price" - "Item price discount"\$ |
10.2.2. Invoice line net amount (BT-131)
The invoice line net amount (BT-131) is as the name implies the net amount without VAT, and inclusive of line level allowance and charges.
The formula for calculating the invoice line net amount is:
\$"Item line net amount" = (("Item net price (BT-146)" div "Item price base quantity (BT-149)")\$
\$times ("Invoiced Quantity (BT-129)")\$
\$+ "Invoice line charge amount (BT-141)" - "Invoice line allowance amount (BT-136)"\$
|
As the line net amount must be rounded to two decimals, please note that the different parts of the calculation must be rounded separately. I.e the result of \$"Item line net amount" = (("Item net price (BT-146)" div "Item price base quantity (BT-149)") times ("Invoiced Quantity (BT-129)")\$ must be rounded to two decimals, and the allowance/charge amounts are also rounded separately. |
<cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>(3)
<cbc:LineExtensionAmount currencyID="EUR">1000.00</cbc:LineExtensionAmount>(4)
<!-- Code omitted for clarity-->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">200.00</cbc:PriceAmount>(1)
<cbc:BaseQuantity unitCode="C62">2</cbc:BaseQuantity>(2)
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">0.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">100.00</cbc:BaseAmount>
</cac:AllowanceCharge>
</cac:Price>| 1 | Item net price |
| 2 | Item price base quantity |
| 3 | Invoiced quantity |
| 4 | \$"Invoice line net amount" = (("Item net price" div "Item price base quantity") times ("Invoiced Quantity")\$ |
<cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>(4)
<cbc:LineExtensionAmount currencyID="EUR">900.00</cbc:LineExtensionAmount>(5)
<!-- Code omitted for clarity-->
<cac:AllowanceCharge>
<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
<cbc:AllowanceChargeReasonCode>CG</cbc:AllowanceChargeReasonCode>
<cbc:AllowanceChargeReason>Charge</cbc:AllowanceChargeReason>
<cbc:MultiplierFactorNumeric>1</cbc:MultiplierFactorNumeric>
<cbc:Amount currencyID="EUR">1</cbc:Amount>(2)
<cbc:BaseAmount currencyID="EUR">100</cbc:BaseAmount>
</cac:AllowanceCharge>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:AllowanceChargeReasonCode>95</cbc:AllowanceChargeReasonCode>
<cbc:AllowanceChargeReason>Discount</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">101</cbc:Amount>(3)
</cac:AllowanceCharge>
<!-- Code omitted for clarity-->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">100.00</cbc:PriceAmount>(1)
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">0.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">100.00</cbc:BaseAmount>
</cac:AllowanceCharge>
</cac:Price>| 1 | Item net price |
| 2 | Line charge amounts |
| 3 | Line allowance amount |
| 4 | Invoiced quantity |
| 5 | \$"Invoice line net amount" = ("Item net price" times "Invoiced Quantity") + "line charge amount" - "line allowance amount"\$ |
10.3. Calculation of allowance/charge amount
Allowance and charge on document- and line level consists of elements carrying information on the allowance/charge base amount and the allowance/charge percentage. These are, if present in the invoice instance, used for calculating the allowance/charge amount.
If base amount is present, the percentage shall also be present, and if percentage is present, the base amount shall also be present, and the calculation of the amount shall be:
\$"Amount" = "Base amount" times ("Percentage" div 100)\$
| Nel contesto nazionale la sezione è utilizzata solo per Bollo (vedi paragrafo 4.9) e Rivalsa Cassa Previdenziale (vedi paragrafo 4.8). |
Tipico esempio di maggiorazione espressa con importo base e percentuale è la cassa previdenziale (vedi paragrafo 4.8).
Tipico esempio di sconto/maggiorazione con solo importo base è il bollo (vedi paragrafo 4.9).
10.4. Calculation of VAT
One VAT Breakdown shall be provided for each distinct combination of VAT category code and VAT rate found in either the line VAT information or the Document level allowance or charges.
For each distinct combination of VAT category code and VAT rate the calculations are:
\$"VAT category taxable amount (BT-116)" = sum("Invoice line net amounts (BT-131)")\$
\$+ "Document level charge amount (BT-99)" - "Document level allowance amount (BT-92)"\$
\$"VAT category tax amount (BT-117)" = "VAT category taxable amount (BT-116)" times ("VAT rate (BT-119)" div 100)\$
| For VAT Breakdown where the VAT Category is "Not subject to VAT" (O), the VAT category tax amount shall be zero. |
<cac:AllowanceCharge>
<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
<cbc:AllowanceChargeReason>Cleaning</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">200</cbc:Amount>(1)
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:AllowanceChargeReason>Discount</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">100</cbc:Amount>(2)
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">1250.00</cbc:TaxAmount>
<cac:TaxSubtotal>(3)
<cbc:TaxableAmount currencyID="EUR">5000.0</cbc:TaxableAmount>(4)
<cbc:TaxAmount currencyID="EUR">1250</cbc:TaxAmount>(5)
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
<cac:TaxSubtotal>(6)
<cbc:TaxableAmount currencyID="EUR">2000.0</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">0</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>E</cbc:ID>
<cbc:Percent>0</cbc:Percent>
<cbc:TaxExemptionReason>Reason for tax exempt</cbc:TaxExemptionReason>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
</cac:TaxTotal>
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID>
<cbc:Note>Testing note on line level</cbc:Note>
<cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">4000.00</cbc:LineExtensionAmount>
<!-- code omitted for clarity -->
<cac:ClassifiedTaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25.0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:ClassifiedTaxCategory>
<!-- code omitted for clarity -->
</cac:InvoiceLine>
<cac:InvoiceLine>
<cbc:ID>2</cbc:ID>
<cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">2000.00</cbc:LineExtensionAmount>
<!-- code omitted for clarity -->
<cac:ClassifiedTaxCategory>
<cbc:ID>E</cbc:ID>
<cbc:Percent>0.0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:ClassifiedTaxCategory>
<!-- code omitted for clarity -->
</cac:InvoiceLine>
<cac:InvoiceLine>
<cbc:ID>3</cbc:ID>
<cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">900.00</cbc:LineExtensionAmount>
<!-- code omitted for clarity -->
<cac:ClassifiedTaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25.0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:ClassifiedTaxCategory>
<!-- code omitted for clarity -->
</cac:InvoiceLine>| 1 | Document level charge amount for category S and rate 25% |
| 2 | Document level allowance amount for category S and rate 25% |
| 3 | VAT Breakdown for category S and rate = 25% |
| 4 | Taxable amount = sum of line amount (line 1 and 3), plus charge amount minus allowance amount where category = S and rate = 25% |
| 5 | \$"Tax Amount" = "Taxable amount" times ("VAT rate" div 100)\$ |
| 6 | VAT Breakdown for category E, and rate = 0% |
11. Examples of selected parts of the transaction
In the subchapters below you find examples of selected parts of the transaction. Please also look into the [Detailed UBL message guideline] for details on all elements and attributes, and their rules and use of code lists.
11.1. Parties
The following roles may be specified. The same actor may play more than one role depending on the handling routine.
Further details on the roles/actors can be found in Parties and roles.
11.1.1. Seller (AccountingSupplierParty)
Seller is mandatory information and provided in element cac:AccountingSupplierParty
<cac:AccountingSupplierParty>
<cac:Party>
<cbc:EndpointID schemeID="0211">IT01234567890</cbc:EndpointID>
<cac:PartyName>
<cbc:Name>Fornitore S.p.A.</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>Indirizzo Riga 1</cbc:StreetName>
<cbc:AdditionalStreetName>Indirizzo Riga 2</cbc:AdditionalStreetName >
<cbc:CityName>Bologna</cbc:CityName>
<cbc:PostalZone>40121</cbc:PostalZone>
<cbc:CountrySubentity>BO</cbc:CountrySubentity >
<cac:AddressLine>
<cbc:Line>Zona Savena</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyTaxScheme>
<cbc:CompanyID>IT01234567890</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:PartyLegalEntity>
<cbc:RegistrationName>Azienda fornitore</cbc:RegistrationName>
<cbc:CompanyID schemeID="0210">01234567890</cbc:CompanyID>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Name>Lucio Grande</cbc:Name>
<cbc:Telephone>051102030</cbc:Telephone>
<cbc:ElectronicMail>lucio.grande@fornitore.it</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:AccountingSupplierParty>Se il Fornitore è un’amministrazione pubblica, il campo EndpointID/@schemeID deve essere valorizzato con “0201:” seguito dal Codice UFE della PA.
La Partita IVA deve essere indicata nel cac:PartyTaxScheme/cbc:CompanyID.
Il Codice Fiscale deve essere indicato nel cac:PartyLegalEntity/cbc:CompanyID, valorizzando l’attributo @schemeID con “0210”.
<cac:AccountingSupplierParty>
<cac:Party>
<cbc:EndpointID schemeID="0201">UFY9MH</cbc:EndpointID>
<cac:PartyName>
<cbc:Name>Azienda USL di Reggio Emilia</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>Via Amendola 2</cbc:StreetName>
<cbc:CityName>Reggio Emilia</cbc:CityName>
<cbc:PostalZone>42122</cbc:PostalZone>
<cbc:CountrySubentity>RE</cbc:CountrySubentity>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyTaxScheme>
<cbc:CompanyID>IT01598570354</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:PartyLegalEntity>
<cbc:RegistrationName>Azienda USL di Reggio Emilia</cbc:RegistrationName>
<cbc:CompanyID schemeID="0210">01598570354</cbc:CompanyID>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Name>Giovanni Rossi</cbc:Name>
<cbc:Telephone>0522335111</cbc:Telephone>
<cbc:ElectronicMail>giovanni.rossi@ausl.re.it</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:AccountingSupplierParty></cac:AccountingSupplierParty>
<cac:Party>
<cbc:EndpointID schemeID="9925">0999999999</cbc:EndpointID
<cac:PartyName>
<cbc:Name>Fornitore Estero</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName> Rue Emile Claus 28</cbc:StreetName>
<cbc:AdditionalStreetName>Quartiere</cbc:AdditionalStreetName>
<cbc:CityName>Bruxelles</cbc:CityName>
<cbc:PostalZone>1050</cbc:PostalZone>
<cac:AddressLine>
<cbc:Line>Deposito Consegnatario: Fornitore Estero</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode>BE</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyTaxScheme>
<cbc:CompanyID>BE0848934496</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:PartyLegalEntity>
<cbc:RegistrationName>Fornitore Estero</cbc:RegistrationName>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Name>Lucio Grande</cbc:Name>
<cbc:Telephone>003241102030</cbc:Telephone>
<cbc:ElectronicMail>lucio.grande@belgio.be</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:AccountingSupplierParty>Le informazioni relative all’Albo possono essere fornite nel cac:PartyIdentification/cbc:ID concatenando il Nome Albo, il numero e la data iscrizione con il simbolo "#" omettendo l’attributo @schemeID ma includendo il prefisso "ALBO:" come nell’esempio di seguito.
| Trattasi di CIUS domestica |
</cac:AccountingSupplierParty>
<cac:Party>
...
<cac:PartyIdentification>
<cbc:ID>ALBO:NomeAlbo#12345#YYYY-MM-DD</cbc:ID>
</cac:PartyIdentification>
...
</cac:Party>
</cac:AccountingSupplierParty>Il numero del Codice EORI (Economic Operator Registration and Identification) basato sul Regolamento (CE) n. 312 del 16 aprile 2009 ed in vigore dal 1 luglio 2009, può essere anch’esso espresso nell’elemento cac:PartyIdentification/cbc:ID omettendo l’attributo @schemeID ma includendo il prefisso "EORI:" come nell’esempio di seguito.
<cac:PartyIdentification>
<cbc:ID>EORI:12345678901</cbc:ID>
</cac:PartyIdentification>Infine, il campo cac:PartyIdentification/cbc:ID può essere usato per indicare anche le informazioni relative a FPA 1.2.4.1 Ufficio e FPA 1.2.4.2 Numero REA omettendo l’attributo @schemeID, includendo il prefisso "REA:" e concatenando i due dati con il "#", come nell’esempio di seguito.
|
Trattasi di CIUS domestica. La specifica è già concordata con Agenzia delle Entrate, che ne darà evidenza in una successiva versione delle regole tecniche. |
<cac:PartyIdentification>
<cbc:ID>REA:MI#1713601</cbc:ID>
</cac:PartyIdentification>Il campo cac:PartyLegalEntity/cbc:RegistrationName può essere usato per indicare il dato FPA 1.2.1.3.1 Denominazione preceduto dalla stringa "Denominazione:". In alternativa, lo stesso può essere usato per indicare i dati FPA 1.2.1.3.2 Nome e 1.2.1.3.3 Cognome preceduti dalla stringa "Nome&Cognome:" e concatenati dal simbolo ""#".
Il campo cac:PartyLegalEntity/cbc:CompanyLegalForm può essere usato per indicare informazioni legali addizionali quali FPA 1.2.4.3 CapitaleSociale, FPA 1.2.4.4 SocioUnico e FPA 1.2.4.5 StatoLiquidazione, concatenando i campi con il simbolo "#".
| Trattasi di CIUS domestica |
<cac:PartyLegalEntity>
...
<cbc:CompanyLegalForm>100000##</cbc:CompanyLegalForm>
...
</cac:PartyLegalEntity>Nell’utilizzo dell’aggregato informativo cac:PostalAddress, è obbligatorio l’utilizzo delle informazioni di indirizzo, CAP, Comune e nazione.
| Trattasi di CIUS domestica |
Di seguito si riportano due esempi di come compilare le informazioni dell’indirizzo.
<cac:PostalAddress>
<cbc:StreetName>Via principale 2, Palazzo 4</cbc:StreetName>
<cbc:CityName>Grande città</cbc:CityName>
<cbc:PostalZone>54321</cbc:PostalZone>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress><cac:PostalAddress>
<cbc:StreetName>Corso di Francia</cbc:StreetName>
<cbc:AdditionalStreetName>I Parioli</cbc:AdditionalStreetName>
<cbc:CityName>Roma</cbc:CityName>
<cbc:PostalZone>00197</cbc:PostalZone>
<cbc:CountrySubentity>RM</cbc:CountrySubentity>
<cac:AddressLine>
<cbc:Line>Informazioni Aggiuntive</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>11.1.2. Buyer (AccountingCustomerParty)
Buyer is mandatory information and provided in element cac:AccountingCustomerParty.
Il cliente può essere una PA, un operatore economico, un cittadino o un soggetto residente, non residente, non stabilito/identificato in Italia.
Le informazioni inerenti al cliente vengono fornite nell’elemento 'cac:AccountingCustomerParty'.
Nel caso in cui il cliente abbia la Partita IVA, la Partita IVA va indicata nel cac:PartyTaxScheme/cbc:CompanyID.
Nel caso in cui il cliente sia dotato solo di Codice Fiscale, questo va indicato nel cac:PartyLegalEntity/cbc:CompanyID, valorizzando l’attributo @schemeID con “0210”.
| Almeno uno tra Partita IVA e Codice Fiscale deve essere presente |
Il campo cac:PartyLegalEntity/cbc:RegistrationName può essere usato per indicare il dato FPA 1.2.1.3.1 Denominazione preceduto dalla stringa "Denominazione:". In alternativa, lo stesso può essere usato per indicare i dati FPA 1.2.1.3.2 Nome e 1.2.1.3.3 Cognome preceduti dalla stringa "Nome&Cognome:" e concatenati dal simbolo "#".
Il Codice EORI può essere espresso nell’elemento cac:PartyIdentification/cbc:ID omettendo l’attributo @schemeID ma includendo il prefisso "EORI:" come nell’esempio di seguito.
<cac:PartyIdentification>
<cbc:ID>EORI:12345678901</cbc:ID>
</cac:PartyIdentification>Nel contesto B2G o G2G, il Cliente deve essere identificato mediante il Codice IPA.
<cac:AccountingCustomerParty>
<cac:Party>
<cbc:EndpointID schemeID="0201">ABCDEF</cbc:EndpointID>
(1)
<cac:PartyName>
<cbc:Name>Azienda USL di Reggio Emilia</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>Via Pubblica, 712</cbc:StreetName>
<cbc:CityName>Roma</cbc:CityName>
<cbc:PostalZone>00199</cbc:PostalZone>
<cac:AddressLine>
<cbc:Line>Informazioni Aggiuntive</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyTaxScheme>
<cbc:CompanyID>IT01598570354</cbc:CompanyID>
(2)
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:PartyLegalEntity>
<cbc:RegistrationName>Azienda USL di Reggio Emilia</cbc:RegistrationName>
<cbc:CompanyID schemeID="0210">01598570354</cbc:CompanyID>
(3)
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Name>Giuseppe Verdi</cbc:Name>
<cbc:Telephone>06123456</cbc:Telephone>
<cbc:ElectronicMail>giuseppe.verdi@cliente.it</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:AccountingCustomerParty>| 1 | L’attributo schemeID è obbligatorio per indirizzi elettronici, es. EndpointID |
| 2 | Gli identificatori per il VAT/IVA devono incudere il prefisso del codice paese |
| 3 | Il codice fiscale è preceduto dall’attributo @schemeID valorizzato con “0210” |
Nel contesto B2B o G2B, il Cliente può essere identificato mediante il Codice Destinatario.
| Trattasi di CIUS domestica valida per la fatturazione verso privati |
<cbc:EndpointID schemeID="0205">L0U7KO4</cbc:EndpointID><cbc:EndpointID schemeID="0205">XXXXXXX</cbc:EndpointID>Nel contesto B2C e G2C il Cliente è una persona fisica.
| Trattasi di CIUS domestica valida per la fatturazione verso privati |
<cac:AccountingCustomerParty>
<cac:Party>
<cbc:EndpointID schemeID="0202">nome.cognome@pec-domain.it</cbc:EndpointID>
<cac:PostalAddress>
<cbc:StreetName>Via Riviera di Chiaia, 99A</cbc:StreetName>
<cbc:CityName>Napoli</cbc:CityName>
<cbc:PostalZone>80121</cbc:PostalZone>
<cac:AddressLine>
<cbc:Line> Informazioni Aggiuntive </cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyTaxScheme>
<cbc:CompanyID>IT01234567890</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:PartyLegalEntity>
<cbc:RegistrationName>Nome#Cognome:Mario#Rossi</cbc:RegistrationName>
<cbc:CompanyID schemeID="0210">RSSMRA00A01E123H</cbc:CompanyID>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Telephone>06123456</cbc:Telephone>
<cbc:ElectronicMail>nome.cognome@pec-domain.it</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:AccountingCustomerParty><cbc:EndpointID schemeID="0205">0000000</cbc:EndpointID>11.1.3. Payment receiver (PayeeParty)
Payment receiver is optional information. If this information is not supplied, the seller is the payment receiver. When payee information is sent this is indicating that a factoring situation is being documented.
To reflect the assignment of an Invoice to a factor there is a need to:
-
have a disclaimer (notification notice) on the Invoice that the Invoice has been assigned to a factor. The disclaimer should be given using the Invoice note (BT-22) on document level.
-
identify the Factor as the Payee
-
to have the bank account changed to favour of a Factor.
<cac:PayeeParty>
<cac:PartyIdentification>
<cbc:ID schemeID="0211">IT01598570354</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>Beneficiario e F.lli S.a.s</cbc:Name>
</cac:PartyName>
<cac:PartyLegalEntity>
<cbc:ID schemeID="0210">CXXNXX68M06E123H</cbc:ID>
</cac:PartyLegalEntity>
</cac:PayeeParty>Il campo cac:PartyIdentification/cbc:ID può essere inoltre usato per fornire le informazioni anagrafiche del Quietanzante indicando i dati FPA 2.4.2.9 NomeQuietanzante e FPA 2.4.2.8 CognomeQuietanzante concatenati con il simbolo "#".
11.1.4. Rappresentante fiscale del Fornitore (TaxRepresentativeParty)
In alcuni scenari di business, le aziende che commerciano oltre confine sono tenute secondo le autorità fiscali locali a nominare un rappresentante fiscale. Sono comprese le aziende extra-EU che operano in Europa, gli importatori in EU e i commercianti.
I rappresentanti fiscali sono responsabili per la gestione corretta e la regolarizzazione dell’IVA per conto delle aziende, in linea con le normative locali. Un rappresentante fiscale è considerato come l’agente locale del commerciante. In molti casi, il rappresentante fiscale è ritenuto responsabile in solido per le tasse del commerciante.
Il Codice Fiscale può essere espresso all’interno del Party nell’elemento cac:PartyIdentification/cbc:ID inserendo l’attributo @schemeID valorizzato con il codice "0210", come nell’esempio di seguito.
<cac:TaxRepresentativeParty>
<cac:PartyIdentification>
<cbc:ID schemeID="0210">CXXNXX68M06E123H</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>Commercialista Snc</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>Corso di Francia</cbc:StreetName>
<cbc:AdditionalStreetName>Blocco 1</cbc:AdditionalStreetName>
<cbc:CityName>Roma</cbc:CityName>
<cbc:PostalZone>00197</cbc:PostalZone>
<cbc:CountrySubentity>RM</cbc:CountrySubentity>
<cac:AddressLine>
<cbc:Line>Informazioni Aggiuntive</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyTaxScheme>
<cbc:CompanyID>IT07643520567</cbc:CompanyID>
(1)
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
</cac:TaxRepresentativeParty>| 1 | VAT identifiers shall be prefixed with the country code |
Il campo cac:PartyName/cbc:Name può essere usato per indicare il dato FPA 1.3.1.3.1 Denominazione preceduto dalla stringa "Denominazione:". In alternativa, lo stesso può essere usato per indicare i dati FPA 1.3.1.3.2 Nome e 1.3.1.3.3 Cognome preceduti dalla stringa "Nome&Cognome:" e concatenati dal simbolo "#".
Il Codice EORI può essere espresso nell’elemento cac:PartyIdentification/cbc:ID omettendo l’attributo @schemeID ma includendo il prefisso "EORI:" come nell’esempio di seguito.
<cac:PartyIdentification>
<cbc:ID>EORI:12345678901</cbc:ID>
</cac:PartyIdentification>11.1.5. Stabile Organizzazione del Fornitore (AccountingSupplierParty/AgentParty) - Estensione
Se il cedente/prestatore non residente ha una stabile organizzazione in Italia, si può specificare in fattura come parte dei dati del fornitore nell’elemento cac:AgentParty.
<cac:AgentParty>
<cac:PostalAddress>
<cbc:StreetName>Corso Sempione, 1</cbc:StreetName>
<cbc:CityName>Milano</cbc:CityName>
<cbc:PostalZone>20100</cbc:PostalZone>
<cbc:CountrySubentity>MI</cbc:CountrySubentity>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
</cac:AgentParty>11.1.6. Il Terzo Intermediario o Soggetto Emittente del Fornitore (AccountingSupplierParty/ServiceProviderParty) - Estensione
Nel caso sia un soggetto terzo ad emettere fattura per conto del cedente / prestatore, si può specificare in fattura come parte dei dati del fornitore nell’elemento cac:ServiceProviderParty.
Il Codice Fiscale deve essere espresso all’interno del Party nell’elemento PartyIdentification/ID inserendo l’attributo @schemeID valorizzato con il codice "0210", come nell’esempio di seguito.
<cac:ServiceProviderParty>
<cac:Party>
<cac:PartyIdentification>
<cbc:ID schemeID="0210">CXXNXX68M06E123H</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>Terzo Intermediario Srl</cbc:Name>
</cac:PartyName>
<cac:PartyTaxScheme>
<cbc:CompanyID>IT07643520567</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
</cac:Party>
</cac:ServiceProviderParty>Il Codice EORI può essere espresso nell’elemento cac:PartyIdentification/cbc:ID omettendo l’attributo @schemeID ma includendo il prefisso "EORI:" come nell’esempio di seguito.
<cac:PartyIdentification>
<cbc:ID>EORI:12345678901</cbc:ID>
</cac:PartyIdentification>11.1.7. Il Rappresentante fiscale del Cliente (AccountingCustomerParty/PowerOfAttorney) - Estensione
Nella fatturazione tra privati (B2B, B2C, G2B e G2C), se il cessionario/committente si avvale di un rappresentante fiscale in Italia, si può specificare in fattura come parte dei dati del fornitore nell’elemento PowerOfAttorney, come procura per la rappresentanza fiscale.
<cac:PowerOfAttorney>
<cbc:Description>Rappresentante Fiscale</cbc:Description>
<cac:AgentParty>
<cac:PartyTaxScheme>
<cbc:CompanyID>IT07643520567</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:PartyLegalEntity>
<cbc:RegistrationName>Rappresentante Fiscale Srl</cbc:RegistrationName>
</cac:PartyLegalEntity>
</cac:AgentParty>
</cac:PowerOfAttorney>11.1.8. Stabile Organizzazione del Cliente (AccountingCustomerParty/AgentParty) - Estensione
Nella fatturazione tra privati (B2B, B2C, G2B e G2C), se il cessionario/committente non residente ha una stabile organizzazione in Italia, si può specificare in fattura come parte dei dati del cliente nell’elemento AgentParty.
<cac:AgentParty>
<cac:PostalAddress>
<cbc:StreetName>Via Navigli, 100</cbc:StreetName>
<cbc:CityName>Milano</cbc:CityName>
<cbc:PostalZone>20100</cbc:PostalZone>
<cbc:CountrySubentity>MI</cbc:CountrySubentity>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
</cac:AgentParty>11.1.9. Il Vettore (Delivery/CarrierParty)
Nei casi di fattura "accompagnatoria", come parte delle informazioni relative al trasporto è possibile specificare i dati fiscali e anagrafici del vettore che trasporta e consegna la merce, nell’elemento CarrierParty.
Il Codice Fiscale può essere espresso all’interno del Party nell’elemento PartyIdentification/ID inserendo l’attributo @schemeID valorizzato con il codice "0210", come nell’esempio di seguito.
<cac:CarrierParty>
<cac:PartyIdentification>
<cbc:ID schemeID="0210">CXXNXX68M06E123H</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>Trasporti di Mario Rossi</cbc:Name>
</cac:PartyName>
<cac:PartyTaxScheme>
<cbc:CompanyID>IT12345678901</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:Person>
<cbc:FirstName>Mario</cbc:FirstName>
<cbc:FamilyName>Rossi</cbc:FamilyName>
<cac:IdentityDocumentReference>
<cbc:ID>MI1234567H</cbc:ID>
<cbc:DocumentTypeCode>40</cbc:DocumentTypeCode>
</cac:IdentityDocumentReference>
</cac:Person>
</cac:CarrierParty>11.2. Delivery Details (Date and Location)
Delivery details may be given at document level.
Place and date of delivery is recommended, and should be sent unless this does not affect the ability to ensure the correctness of the invoice.
The delivery element contains information on name, address and delivery location identifier (cac:Delivery/cac:DeliveryLocation/cbc:ID) which may be used if the place of delivery is defined through an identifier. For example GLN (Global Location Number)issued by GS1.
In italia, in seguito alle Regole Tecniche NSO, l’identificativo del luogo di consegna per le PA segue la codifica Punti di consegna.
Quando la fattura si riferisce ad un unico Documento di Trasporto, la data del DDT viene riportata nel cac:DespatchDocumentReference/cbc:IssueDate.
<cac:Delivery>
<cbc:ActualDeliveryDate>2017-11-01</cbc:ActualDeliveryDate>
<cac:DeliveryLocation>
<cbc:ID>01598570354-MCR-FEA</cbc:ID>
<cac:Address>
<cbc:StreetName>Viale Viali,2 - PAD.01</cbc:StreetName>
<cbc:AdditionalStreetName>CENTRO LOG</cbc:AdditionalStreetName>
<cbc:CityName>Bologna</cbc:CityName>
<cbc:PostalZone>40100</cbc:PostalZone>
<cac:AddressLine>
<cbc:Line>MCR-FEA</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode>IT</cbc:IdentificationCode>
</cac:Country>
</cac:Address>
</cac:DeliveryLocation>
<cac:DeliveryParty>
<cac:PartyName>
<cbc:Name>Nome Acquirente</cbc:Name>
</cac:PartyName>
</cac:DeliveryParty>
</cac:Delivery>11.3. References
Support for invoice verification is a key function of an invoice. The invoice should provide sufficient information to look up relevant existing documentation, electronic or paper.
| Any reference element should contain valid information, if you do not have a reference, the element should not be present in the instance document. |
The invoice and credit note transactions supports the following references to existing documentation:
11.3.1. Purchase order and sales order reference
The purchase order is conditional. If order reference exist, use that, else use Buyer reference (see Buyer reference).
The customer will issue an order with a unique order number. This unique purchase order number should be supplied as the order reference on the invoice.
- The header level
-
If order reference is stated at header level, the order reference element on line level can be used to state the order line numbers.
| In the invoice, both a purchase order and a sales order reference can be given, but be aware that an invoice instance cannot have a sales order reference, without the corresponding purchase order reference. |
<cac:OrderReference>
<cbc:ID>CE20-HF1-4001</cbc:ID>(1)
<cbc:SalesOrderID>so-12343</cbc:SalesOrderID>(2)
</cac:OrderReference>| 1 | Purchase order reference |
| 2 | Sales order reference |
Se la fattura viene emessa nell’ambito di un processo di Ordinazione elettronica, occorre riportare il riferimento all’ordine ("tripletta") nel seguente modo:
-
Nel cac:OrderReference/cbc:ID (BT-13 Purchase order reference) riportare il solo identificativo dell’ordine, deve inoltre essere riportata la data dell’ordine nel cac:OrderReference/cbc:IssueDate:
<cac:OrderReference> <cbc:ID>110</cbc:ID> <cbc:IssueDate>2018-01-30</cbc:IssueDate> </cac:OrderReference> -
Nel cbc:BuyerReference (BT-10 Buyer reference) riportare la Tripletta di identificazione completa separando i componenti (Id, data e Endpoint) con il carattere # senza interposizione di spazi, come nel seguente esempio:
<cbc:BuyerReference>110#2018-01-30#aaaaaa</cbc:BuyerReference>
Se invece la fattura viene emessa a fronte di un ordine analogico se ne può dare evidenza nel seguente modo:
<cbc:BuyerReference>#NO#</cbc:BuyerReference>Se la fattura non è stata preceduta da un ordine occorre indicarlo nel seguente modo:
<cac:OrderReference>
<cbc:ID>#NO#</cbc:ID>
</cac:OrderReference>Ove la fattura sia riferita a più ordini elettronici referenziati in riga, occorre indicarlo nel seguente modo:
<cac:OrderReference>
<cbc:ID>#MULTI#</cbc:ID>
</cac:OrderReference>A livello di riga
Il riferimento ad un ordine sulle righe di fattura avviene utilizzando gli elementi cac:OrderLineReference e cac:DocumentReference.
Riferimento all’intero ordine sulla riga di fattura
Se la riga si riferisce genericamente all’ordine senza specificare la riga dell’ordine, si procede come da esempio:
<cac:OrderLineReference>
<cbc:LineID>NA</cbc:LineID>
<cac:OrderReference>
<cbc:ID>123</cbc:ID>
<cbc:IssueDate>2020-10-01</cbc:IssueDate>
</cac:OrderReference>
</cac:OrderLineReference>Se la fattura viene messa nell’ambito di un processo di Ordinazione Semplice o Ordinazione Completa rilevante ai fini del sistema NSO, occorre riportare il riferimento all’ordine ("tripletta") nel seguente modo:
<cac:OrderLineReference>
<cbc:LineID>NA</cbc:LineID>
<cac:OrderReference>
<cbc:ID>123</cbc:ID>
<cbc:IssueDate>2020-10-01</cbc:IssueDate>
</cac:OrderReference>
</cac:OrderLineReference>
<cac:DocumentReference>
<cbc:ID schemeID="ON">123#2020-10-01#aaaaaa</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:DocumentReference>Riferimento alla riga d’ordine sulla riga di fattura
Se la riga si riferisce specificamente ad una riga d’ordine, si procede con le seguenti modalità alternative:
<cac:OrderLineReference>
<cbc:LineID>3</cbc:LineID>
</cac:OrderLineReference><cac:OrderLineReference>
<cbc:LineID>4</cbc:LineID>
<cac:OrderReference>
<cbc:ID>123</cbc:ID>
<cbc:IssueDate>2020-10-01</cbc:IssueDate>
</cac:OrderReference>
</cac:OrderLineReference>Se la fattura viene messa nell’ambito di un processo di Ordinazione Semplice o Ordinazione Completa rilevante ai fini del sistema NSO, occorre riportare il riferimento all’ordine ("tripletta") nel seguente modo:
<cac:OrderLineReference>
<cbc:LineID>4</cbc:LineID>
<cac:OrderReference>
<cbc:ID>123</cbc:ID>
<cbc:IssueDate>2020-10-01</cbc:IssueDate>
</cac:OrderReference>
</cac:OrderLineReference>
<cac:DocumentReference>
<cbc:ID schemeID="ON">123#2020-10-01#aaaaaa</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:DocumentReference>11.3.2. Buyer reference
The buyer reference, known as Your ref, is conditional. An invoice shall have either the buyer reference or the order reference (see Purchase order and sales order reference)
The element is used for the reference of who ordered the products/services. Example being the name of the person ordering, employee number or a code identifying this person or department/group. Your ref is often used for internal routing at recipient, and hence it is important to fill this element with the correct values according to the need of the recipient.
Se la fattura viene messa nell’ambito di un processo di Ordinazione Semplice o Ordinazione Completa rilevante ai fini del sistema NSO, occorre riportare nel cbc:BuyerReference (BT-10 Buyer reference) la Tripletta di identificazione completa separando i componenti (Id, data e Endpoint) con il carattere # senza interposizione di spazi, come nel seguente esempio:
<cbc:BuyerReference>110#2018-01-30#aaaaaa</cbc:BuyerReference>Se la fornitura promana da un processo di ordinazione tradizionale (ad esempio, via lettera, fax, ecc.), ovvero non gestito tramite NSO, per dare maggior evidenza a tale circostanza si può indicare il testo "#NO#" nel cbc:BuyerReference (BT-10 Buyer reference).
11.3.3. Invoiced object identifier
The invoiced object identifier is the identifier for an object on which the invoice is based, given by the Seller. Examples may be a subscription number, telephone number, meter point, vehicle, person etc., as applicable.
If it is not clear to the receiver what scheme is used for the identifier, a conditional scheme identifier should be used, that shall be chosen from the Schema per gli identificatori di un oggetto fatturato.
The invoiced object reference is provided by using the element cac:AdditionalDocumentReference with the document type code = 130
<cac:AdditionalDocumentReference>
<cbc:ID schemeID="ABT">DR35141</cbc:ID>(1)
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>(2)
</cac:AdditionalDocumentReference>| 1 | Scheme identifier from UN/CEFACT 1153 code list |
| 2 | Document type code shall be ´130´ to indicate Invoiced object |
11.3.4. Contract reference
To reference or match an invoice to a purchase contract, the contract number could be specified like this:
<cac:ContractDocumentReference>
<cbc:ID>Contratto321</cbc:ID>
</cac:ContractDocumentReference>Per riferirsi a più contratti dalle righe di fattura è necessario utilizzare cac:DocumentReference con il codice tipo documento = 130.
<cac:DocumentReference>
<cbc:ID schemeID="CT">123456</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:DocumentReference>11.3.5. Despatch and receipt advice references
To reference or match an invoice to a despatch or receipt advice use the following elements:
<cac:DespatchDocumentReference>
<cbc:ID>despadv-3</cbc:ID>(1)
<cbc:IssueDate>YYYY-MM-DD</cbc:IssueDate>
</cac:DespatchDocumentReference>
<cac:ReceiptDocumentReference>
<cbc:ID>resadv-1</cbc:ID>(2)
</cac:ReceiptDocumentReference>| 1 | Despatch advice (DDT) |
| 2 | Receipt advice |
Per fare riferimento a più DDT dalle righe di fattura è possibile utilizzare cac:DespatchLineReference, come nel seguente esempio:
<cac:DespatchLineReference>
<cbc:LineID>NA</cbc:LineID>
<cac:DocumentReference>
<cbc:ID>123</cbc:ID>
<cbc:IssueDate>2020-10-01</cbc:IssueDate>
</cac:DocumentReference>
</cac:DespatchLineReference>
<cac:DespatchLineReference>
<cbc:LineID>NA</cbc:LineID>
<cac:DocumentReference>
<cbc:ID>456</cbc:ID>
<cbc:IssueDate>2020-10-02</cbc:IssueDate>
</cac:DocumentReference>
</cac:DespatchLineReference>11.3.6. Tender reference (CIG)
To identify the call for tender or lot the invoice relates to, use the 'OriginatorDocumentReference'. The identifier is, in most cases, the Procurement Procedure Identifier.
L’indicazione del codice CIG è obbligatoria nei contesti in cui questo è richiesto, ed è necessario al fine dei processi di verifica, riconciliazione e approvazione al pagamento delle fatture.
<cac:OriginatorDocumentReference>
<cbc:ID>1Z1A3EE456</cbc:ID>
</cac:OriginatorDocumentReference>Per riferirsi a più CIG dalle righe di fattura è necessario utilizzare cac:DocumentReference con il codice tipo documento = 130.
<cac:DocumentReference>
<cbc:ID schemeID="AGB">90305884F7</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:DocumentReference>11.3.7. Project reference (CUP)
The project reference is optional to use, and is sent in an invoice in the element cac:ProjectReference/cbc:ID.
L’indicazione del Codice Unico di Progetto (CUP) è obbligatoria nei contesti in cui questo è richiesto, ed è necessario al fine dei processi di verifica, riconciliazione e approvazione al pagamento delle fatture.
In a credit note, this element does not exist, and project reference
is sent by using the element cac:AdditionalDocumentReference[cbc:DocumentTypeCode='50']/cbc:ID.
Quando si invia il riferimento al progetto, solo il cbc:ID e il cbc:DocumentTypeCode sono permessi all’interno dell’elemento cac:AdditionalDocumentReference.
|
<cac:ProjectReference>
<cbc:ID>J31E01000010004</cbc:ID>
</cac:ProjectReference><cac:AdditionalDocumentReference>
<cbc:ID>J31E01000010004</cbc:ID>(2)
<cbc:DocumentTypeCode>50</cbc:DocumentTypeCode>(1)
</cac:AdditionalDocumentReference>| 1 | Il codice 50 indica che questo è il riferimento ad un progetto |
| 2 | L’identificatore del riferimento al progetto |
Per riferirsi a più progetti (CUP) dalle righe di fattura è necessario utilizzare cac:DocumentReference con il codice tipo documento = 130.
<cac:DocumentReference>
<cbc:ID schemeID="AEP">project333</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:DocumentReference>11.3.8. Riferimento ad una Convenzione
Per fare riferimento ad una convenzione, il numero di convenzione può essere espressa come segue:
<cac:AdditionalDocumentReference>
<cbc:ID schemeID="AVV">123456</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:AdditionalDocumentReference>Per riferirsi a più convenzioni dalle righe di fattura è necessario utilizzare cac:DocumentReference con il codice tipo documento = 130.
<cac:DocumentReference>
<cbc:ID schemeID="AVV">123456</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:DocumentReference>| La specifica è già concordata con Agenzia delle Entrate, che ne darà evidenza in una successiva versione delle regole tecniche. |
11.3.9. Riferimento fase (Dati SAL)
Per fare riferimento alla fase di un SAL, il codice può essere espresso come segue:
<cac:AdditionalDocumentReference>
<cbc:ID schemeID="AOR">001</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:AdditionalDocumentReference>Per riferirsi alla fase di un SAL dalle righe di fattura è necessario utilizzare cac:DocumentReference con il codice tipo documento = 130.
<cac:DocumentReference>
<cbc:ID schemeID="AOR">001</cbc:ID>
<cbc:DocumentTypeCode>130</cbc:DocumentTypeCode>
</cac:DocumentReference>11.3.10. Riferimento alla Fattura Principale (estensione)
Nei casi di fatture per operazioni accessorie, emesse dagli 'autotrasportatori' per usufruire delle agevolazioni in materia di registrazione e pagamento dell’IVA, è possibile riferirsi alla fattura principale relativa al trasporto di beni per certificare le operazioni accessorie.
<cac:BillingReference>
<cac:InvoiceDocumentReference>
<cbc:ID>ft123</cbc:ID>
<cbc:IssueDate>2020-09-15</cbc:IssueDate>
</cac:InvoiceDocumentReference>
<cac:AdditionalDocumentReference>
<cbc:ID>ft001</cbc:ID>
<cbc:IssueDate>2020-09-15</cbc:IssueDate>
</cac:AdditionalDocumentReference>
</cac:BillingReference>11.3.11. Riepilogo riferimenti ad altri documenti
| Riferimento | Descrizione | Campo Fattura PA | Dove usarlo |
|---|---|---|---|
ORDINE |
Ordine cartaceo o elettronico |
2.1.2.2 <IdDocumento> |
In testata si usa A livello di riga |
CONTRATTO |
Estremi Contratto |
2.1.3.2 IdDocumento |
In testata si usa A livello di riga |
DDT |
Documento di Trasporto |
2.1.8.1 NumeroDDT |
In testata si usa A livello di riga |
CIG |
Codice Identificativo Gara |
2.1.3.7 CodiceCIG |
In testata si usa A livello di riga |
CUP |
Codice Unico di Progetto |
2.1.3.6 CodiceCUP |
In testata si usa A livello di riga |
CONVENZIONE |
Estremi Convenzione |
2.1.4.5 CodiceCommessaConvenzione |
In testata si usa A livello di riga |
Dati SAL |
Riferimento alla fase di un SAL |
2.1.7.1 RiferimentoFase |
In testata si usa |
11.3.12. Allegati
L’elemento per memorizzare le informazioni degli allegati (AdditionalDocumentReference) può essere ripetuto diverse volte, permettendo quindi di avere molteplici allegati.
Gli allegati possono essere utilizzati per fornire informazioni aggiuntive a supporto della richiesta di pagamento che la fattura rappresenta. Informazioni aggiuntive possono essere fogli presenze, ricevute, biglietti aerei, ecc.
Lo scopo dell’allegato non è quello di trasferire la versione pdf della fattura. |
Gli allegati possono essere grafici e immagini. Essi potrebbero essere inviati come oggetti binari o come indirizzo esterno alla posizione dove l’oggetto è memorizzato (URI). Gli allegati inviati come oggetti binari dovrebbero essere limitati alle tipologie MIME specificati nella codifica di riferimento IANA.
Si raccomanda l’invio di informazioni aggiuntive incluse nel formato del messaggio e non come indirizzi esterni (URI), in quanto molte aziende sono limitate nell’accesso a link esterni.
<cac:AdditionalDocumentReference>
<cbc:ID>Doc1</cbc:ID>
<cbc:DocumentDescription>Foglio presenze</cbc:DocumentDescription>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>http://www.fornitore.eu/foglio001.html</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
</cac:AdditionalDocumentReference><cac:AdditionalDocumentReference>
<cbc:ID>Doc2</cbc:ID>
<cbc:DocumentDescription>Disegno</cbc:DocumentDescription>
<cac:Attachment>
<cbc:EmbeddedDocumentBinaryObject mimeCode="application/pdf" filename="disegno.pdf">UjBsR09EbGhjZ0dTQUxNQUFBUUNBRU1tQ1p0dU1GUXhEUzhi
</cbc:EmbeddedDocumentBinaryObject>
</cac:Attachment>
</cac:AdditionalDocumentReference><cac:AdditionalDocumentReference>
<cbc:ID>Doc3</cbc:ID>
<cbc:DocumentDescription>UBL-PackingList</cbc:DocumentDescription>
<cac:Attachment>
<cbc:EmbeddedDocumentBinaryObject mimeCode="text/xml" filename="UBL-PackingList.xml">UjBsR09EbGhjZ0dTQUxNQUFBUUNBRU1tQ1p0dU1GUXhEUzhi
</cbc:EmbeddedDocumentBinaryObject>
</cac:Attachment>
</cac:AdditionalDocumentReference>11.4. Preceding invoice references
A credit note or negative invoice can refer to one or more initial invoice(s). This is done in the business group BG-3 Preceding invoice reference, providing the invoice number and issue date. The issue date shall be provided in case the preceding invoice reference is not unique.
In case correction applies to a large number of invoices, the invoicing period (BG-14), as necessary combined with a clarifying invoice note (BT-22), may instead be be given at document level.
<cac:BillingReference>
<cac:InvoiceDocumentReference>
<cbc:ID>123</cbc:ID>(1)
<cbc:IssueDate>2017-10-20</cbc:IssueDate>(2)
</cac:InvoiceDocumentReference>
</cac:BillingReference>
<cac:BillingReference>(3)
<cac:InvoiceDocumentReference>
<cbc:ID>124</cbc:ID>
</cac:InvoiceDocumentReference>
</cac:BillingReference>| 1 | The identifier is mandatory if cac:BillingReference is provided |
| 2 | Issue date shall be filled if the invoice reference is not unique |
| 3 | Repeat the cac:BillingReference to add several preceding invoice references |
11.5. Allowances and Charges
The Invoice and credit note transactions has elements for Allowance/charge on 3 levels.
The element cac:AllowanceCharge with sub element cbc:ChargeIndicator indicates whether the instance is a charge (true) or an allowance (false).
- The header level
-
Applies to the whole invoice and is included in the calculation of the invoice total amount.
-
Several allowances and charges may be supplied
-
Specification of VAT for allowances and charges,
cac:TaxCategorywith sub elements, shall be supplied -
The sum of all allowances and charges on the header level shall be specified in
cbc:AllowanceTotalAmountandcbc:ChargeTotalAmountrespectively. See UBL syntax calculation formulas
-
|
Per la fatturazione verso soggetti italiani la sezione è utilizzata solo per Bollo (vedi paragrafo 4.9) e Rivalsa Cassa Previdenziale (vedi paragrafo 4.8). |
Sconti e maggiorazioni che non incidono sull’imponibile.
-
Espressi mediante estensione UBL.
-
Possono essere indicati diversi sconti e maggiorazioni.
-
Non modificano nè l’imponibile, nè l’IVA.
|
La somma algebrica delle maggiorazioni (con segno meno) e degli sconti (con segno più) va ricompresa nel valore inserito in cbc:PrepaidAmount. Si evidenzia che il cbc:PrepaidAmount non è supportato in FatturaPA ma viene utilizzato per valorizzare correttamente il dato cbc:PayableAmount (BT-115 Amount due for payment) che è obbligatorio per la EN 16931. |
<ext:UBLExtension>
<ext:ExtensionURI>urn:fdc:agid.gov.it:fatturapa:ScontoMaggiorazione</ext:ExtensionURI>
<ext:ExtensionContent>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">100</cbc:Amount>
</cac:AllowanceCharge>
</ext:ExtensionContent>
</ext:UBLExtension>- The line level
-
Applies to the line level and is included in the calculation of the line amount.
-
Several allowances and charges may be supplied
-
Specification of VAT for allowances and charges shall not be specified, as the VAT category stated for the invoice line itself, applies also to the allowances or charges of that line.
-
The sum of all allowances and charges on the line level shall be taken into account, subtracted or added, when calculating the line extension amount . These line level allowances and charges shall not be calculated into the header level elements.
-
|
Per la fatturazione verso soggetti italiani la sezione sconto/maggiorazione a livello di riga non è utilizzata. |
- The line level Price element
-
A way to inform the buyer how the price is set. Is also relevant if the seller or buyer want to post the allowance in their accounting systems. The price itself shall always be the net price, i.e. the base amount reduced with a discount (allowance).
-
Il prezzo netto (cbc:PriceAmount) deve essere sempre espresso
-
L’elemento cbc:ChargeIndicator deve essere sempre espresso e valorizzato con "false".
-
Il prezzo lordo (cbc:BaseAmount) deve essere sempre espresso.
-
Il segmento cac:AllowanceCharge deve essere sempre espresso
-
Per indicare uno sconto, fornire un importo positivo nel cac:AllowanceCharge/cbc:Amount.
Per indicare una maggiorazione, fornire un importo negativo nel cac:AllowanceCharge/cbc:Amount.
Se nessuno Sconto/Maggiorazione è applicato all’articolo, valorizzare cac:AllowanceCharge/cbc:Amount con "0". -
Only one occurence of allowance (discount) is allowed.
-
Specification of VAT for allowance shall not be specified
-
Allowance related to Price shall not be part of any other calculations.
-
Allowance related to Price may specify amount and the base amount.
-
Further details of the calculation of allowance/charge amount, can be found in Calculation of allowance/charge amount
<cac:InvoiceLine>
<!-- ... -->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">5.00</cbc:PriceAmount>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">1.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">6.00</cbc:BaseAmount>
</cac:AllowanceCharge>
</cac:Price>
</cac:InvoiceLine>11.6. VAT accounting currency
Article 230 of Directive 2006/112/EC states:
The amounts which appear on the invoice may be expressed in any currency, provided that the amount of VAT payable is expressed in the national currency of the Member State in which the supply of goods or services takes place, using the conversion mechanism laid down in Article 91.
If the invoice currency is different from the national currency, this is expressed in the invoice by stating the national currency in the element VAT accounting currency (BT-6), and the amount of VAT payable in national currency is stated in the element Invoice total VAT amount in accounting currency (BT-111). The exchange rate to use for calculating is described in Article 91 of Directive 2006/112/EC. The exchange rate is not specified in the invoice instance, and hence this calculation is not validated.
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
(1)
<cbc:TaxCurrencyCode>SEK</cbc:TaxCurrencyCode>
(2)
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">1000.00</cbc:TaxAmount>
(3)
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">4000.0</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">1000</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
</cac:TaxTotal>
<cac:TaxTotal>
<cbc:TaxAmount currencyID="SEK">100017.50</cbc:TaxAmount>
(4)
</cac:TaxTotal>| 1 | Invoice currency |
| 2 | National currency |
| 3 | VAT amount in invoice currency |
| 4 | VAT amount in national currency |
11.7. Payment means information
11.7.1. Credit transfer
If payment is made by credit transfer, the Payment account identifier (BT-84) is mandatory
See Termini di pagamento type code for all allowed codes. Examples of codes for payment by credit transfer are:
-
30 - Credit transfer
-
58 - SEPA credit transfer ?
-
56 - Giroconto bancario
<cac:PaymentMeans>
<cbc:PaymentMeansCode name="Credit transfer">30</cbc:PaymentMeansCode>(1)
<cbc:PaymentID>93274234</cbc:PaymentID>(2)
<cac:PayeeFinancialAccount>
<cbc:ID>32423940</cbc:ID>(3)
<cbc:Name>AccountName</cbc:Name>
<cac:FinancialInstitutionBranch>
<cbc:ID>BIC32409</cbc:ID>(4)
</cac:FinancialInstitutionBranch>
</cac:PayeeFinancialAccount>
</cac:PaymentMeans>| 1 | Mandatory, payment means code for credit transfer |
| 2 | Remittance information |
| 3 | Mandatory, IBAN (in case of a SEPA payment) or a national account number (BBAN) |
| 4 | BIC or a national clearing code |
<cac:PaymentMeans>
<cbc:PaymentMeansCode name="SEPA Credit transfer">58</cbc:PaymentMeansCode>(1)
<cbc:PaymentID>F20150000021003</cbc:PaymentID>(2)
<cac:PayeeFinancialAccount>
<cbc:ID>IT71R1068102800000100693977</cbc:ID>(3)
<cbc:Name>Mario Rossi</cbc:Name>
<cac:FinancialInstitutionBranch>
<cbc:ID>XXXXITX0</cbc:ID>(4)
</cac:FinancialInstitutionBranch>
</cac:PayeeFinancialAccount>
</cac:PaymentMeans>| 1 | Obbligatorio, codice modalità di pagamento per il bonifico SEPA |
| 2 | Informazioni di rimessa pagamento |
| 3 | Obbligatorio, IBAN |
| 4 | BIC |
11.7.2. Card Payment
If the Buyer had opted to pay by using a payment card such as a credit or debit card, information on the Primary Account Number (PAN) shall be present in the invoice.
See Termini di pagamento type code for all allowed codes. Examples of codes for payment by card are:
-
48 - Bank card
-
54 - Credit card
-
55 - Debet card
<cac:PaymentMeans>
<cbc:PaymentMeansCode name="Credit card">54</cbc:PaymentMeansCode>(1)
<cbc:PaymentID>9387439</cbc:PaymentID>
<cac:CardAccount>
<cbc:PrimaryAccountNumberID>123236</cbc:PrimaryAccountNumberID>(2)
<cbc:NetworkID>VISA</cbc:NetworkID>(3)
<cbc:HolderName>Card holders name</cbc:HolderName>(4)
</cac:CardAccount>
</cac:PaymentMeans>| 1 | Payment means code for credit card |
| 2 | Mandatory, shall be the last 4 to 6 digits of the payment card number |
| 3 | Mandatory, used to identify the financial service network provider of the card. Examples are VISA, MasterCard, American Express. |
| 4 | Card holder name |
11.7.3. Direct debit
See Termini di pagamento type code for all allowed codes. Examples of codes for payment by direct debit are:
-
49 - Direct debit
-
59 - SEPA direct debit
<cac:AccountingSupplierParty>
<cac:Party>
<cbc:EndpointID schemeID="0088">7300010000001</cbc:EndpointID>
<cac:PartyIdentification>
<cbc:ID>99887766</cbc:ID>
</cac:PartyIdentification>
<cac:PartyIdentification>
<cbc:ID schemeID="SEPA">23123687</cbc:ID>(1)
</cac:PartyIdentification>
<!-- omitted code for clarity -->
...
</cac:Party>
</cac:AccountingSupplierParty>
<cac:PaymentMeans>
<cbc:PaymentMeansCode name="SEPA direct debit">59</cbc:PaymentMeansCode>(2)
<cbc:PaymentID>payref2</cbc:PaymentID>(3)
<cac:PaymentMandate>
<cbc:ID>123456</cbc:ID>(4)
<cac:PayerFinancialAccount>
<cbc:ID>DK12328462834823</cbc:ID>
</cac:PayerFinancialAccount>
</cac:PaymentMandate>
</cac:PaymentMeans>| 1 | Unique banking reference identifier of the Seller or Payee, schemeID shall have value "SEPA" |
| 2 | Payment means code |
| 3 | Remittance information |
| 4 | Mandate reference identifier |
11.7.4. Payment by post- or bank giro
See Termini di pagamento type code for all allowed codes. Examples of codes for payment by giro are:
-
50 - Payment by postgiro
-
? 56 - Bankgiro
<cac:PaymentMeans>
<cbc:PaymentMeansCode name="Postgiro">50</cbc:PaymentMeansCode>(1)
<cbc:PaymentID>PgPaymRef-345</cbc:PaymentID>(2)
<cac:PayeeFinancialAccount>
<cbc:ID>98765432</cbc:ID>(3)
</cac:PayeeFinancialAccount>
</cac:PaymentMeans>| 1 | Payment means code |
| 2 | Remittance information |
| 3 | Local postgiro account number |
11.7.5. Pagamento mediante contante
Vedi Termini di pagamento type code per tutti i codici ammessi. Esempio di codice per il pagamento in contante:
-
10 - Contante
<cac:PaymentMeans>
<cbc:PaymentMeansCode name="Pagamento contante">10</cbc:PaymentMeansCode>(1)
</cac:PaymentMeans>| 1 | Codice modalità pagamento per il contante |
Se il venditore non dà indicazioni su come regolarizzare il pagamento della fattura, esiste solitamente un contratto che lo regola.
Indicando il codice 1, l’acquirente non viene informato sulle modalità di pagamento della fattura e può essere indicata solo una data di pagamento.
<cac:PaymentMeans>
<cbc:PaymentMeansCode>1</cbc:PaymentMeansCode>(1)
</cac:PaymentMeans>| 1 | Codice modalità pagamento non specificata |
11.8. Intrastat
When EU member states buy from other EU members, traders commonly require some statistical information in the invoice, normally a classification code as the Combined Nomenclature.
It is recommended to use the Item classification identifier (BT-158) for this purpose, with the code "HS" as list identifier.
<cac:CommodityClassification>
<cbc:ItemClassificationCode listID="HS">080110</cbc:ItemClassificationCode>
</cac:CommodityClassification>11.9. Item information
11.9.1. Item identifiers
In an invoice line the seller item identifier, the buyer item identifier and the standard item identifier can be provided. For sellers and buyers item identifiers, no scheme attribute is used, whilst the schemeID
is mandatory for the standard item identification, and must be from the ISO 6523 ICD list.
<cac:Item>
<!-- Codice omesso per chiarezza -->
<cac:BuyersItemIdentification>
<cbc:ID>b-13214</cbc:ID>
</cac:BuyersItemIdentification>
<cac:SellersItemIdentification>
<cbc:ID>97iugug876</cbc:ID>
</cac:SellersItemIdentification>
<cac:StandardItemIdentification>
<cbc:ID schemeID="0160">97iugug876</cbc:ID> (1)
</cac:StandardItemIdentification>
<!-- Codice omesso per chiarezza -->
</cac:Item>| 1 | 0160 is the ICD value for a GTIN identifier |
In coerenza con quanto previsto per l’ordine, la gestione dell’AICFarmaco è operata a mezzo del cac:SellersItemIdentification/cbc:ID (BT-155 Item Seller’s Identifier) in cui viene inserito il codice AICFarmaco stesso preceduto dalla stringa “AICFARMACO:”.
| Trattasi di CIUS domestica (DC) |
<cac:SellersItemIdentification>
<cbc:ID>AICFARMACO:025829211</cbc:ID>
</cac:SellersItemIdentification>La gestione del tipo carburante è operata a mezzo del cac:SellersItemIdentification/cbc:ID (BT-155 Item Seller’s Identifier) in cui viene inserito il valore della tabella di riferimento per i prodotti energetici TA13 – pubblicata sul sito dell’Agenzia delle Dogane preceduto dalla stringa “CARB:”.
| Trattasi di CIUS domestica (DC) |
<cac:SellersItemIdentification>
<cbc:ID>CARB:27101249</cbc:ID>
</cac:SellersItemIdentification>11.9.2. Item classification
Several different item classification codes can be provided per invoice line, and the codes must be from one of the classification schemes in code list UNCL7143.
<cac:CommodityClassification>
<cbc:ItemClassificationCode listID="STI">09348023</cbc:ItemClassificationCode> (1)
</cac:CommodityClassification>| 1 | listID must be from UNCL7143 code list, and code STI indicates this is a CPV classification. |
<cac:CommodityClassification>
<cbc:ItemClassificationCode listID="TST" listVersionID="19.05.01">86776</cbc:ItemClassificationCode>(1)
</cac:CommodityClassification>| 1 | listID must be from UNCL7143 code list, and code TST indicates this is a UNSPSC classification, listVersionID is optional, but can be used to specify the version of UNSPSC. NOTE, in previous versions code MP was used as temporary workaround to identify UNSPSC. In fall release 2019 it is replaced with the new 7143 code TST that is specific for UNSPSC. |
<cac:Item>
<cbc:Description>Dispositivo Medico</cbc:Description>
<cbc:Name>Prodotto 1143668 DEFIBRILLATORE SEMIAUTOMATICO LIFEPAK 1000</cbc:Name>
<cac:SellersItemIdentification>
<cbc:ID>1143668</cbc:ID> (1)
</cac:SellersItemIdentification>
<cac:CommodityClassification>
<cbc:ItemClassificationCode listID="ZZZ">DM1:918674</cbc:ItemClassificationCode> (2)
</cac:CommodityClassification>
<cac:CommodityClassification>
<cbc:ItemClassificationCode listID="STO">Z12030501</cbc:ItemClassificationCode> (3)
</cac:CommodityClassification>
[…]
</cac:Item>| 1 | Codice del dispositivo medico attribuito dal Fornitore; |
| 2 | Il listID deve essere fra quelli della codifica UNCL7143, il codice ZZZ indica il numero di repertorio attribuito al dispositivo medico nella Banca Dati e Repertorio (BDR) dei Dispositivi Medici del Ministero della Salute. Il numero dovrà essere preceduto dalla seguente stringa:
|
| 3 | Il listID deve essere fra quelli della codifica UNCL7143 e il codice STO indica il codice attribuito al dispositivo medico dalla Classificazione Nazionale dei Dispositivi Medici (CND). |
11.9.3. Tipo cessione prestazione
La gestione del tipo cessione prestazione è operata a mezzo dell’utilizzo di:
-
cac:AdditionalItemProperty/cbc:Name (BT-160 Item attribute name), inserendo la stringa TipoCessionePrestazione;
-
cac:AdditionalItemProperty/cbc:Value (BT-161 Item attribute value) inserendo il valore ammesso da FatturaPA: [SC] sconto, [PR] premio, [AB] abbuono, [AC] spesa accessoria.
<cac:InvoiceLine>
<!-- ... -->
<cac:Item>
<!-- ... -->
<cac:AdditionalItemProperty>
<cbc:Name>TipoCessionePrestazione</cbc:Name>
<cbc:Value>AB</cbc:Value>
</cac:AdditionalItemProperty>
</cac:Item>
</cac:InvoiceLine>11.10. Price information
An invoice must contain information about the item net price and additional information such as gross price, item price base quantity and price discount may be added.
For details on calculating price see Item net price (BT-146).
<cac:Price>
<cbc:PriceAmount currencyID="EUR">410</cbc:PriceAmount>(4)
<cbc:BaseQuantity unitCode="XBX">1</cbc:BaseQuantity>(3)
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">40</cbc:Amount>(2)
<cbc:BaseAmount currencyID="EUR">450</cbc:BaseAmount>(1)
</cac:AllowanceCharge>
</cac:Price>| 1 | Item gross price |
| 2 | Item price discount |
| 3 | Item price base quantity |
| 4 | Item net price, must be equal to Item Gross price - item price discount (if these elements are used) |
<cac:Price>
<cbc:PriceAmount currencyID="EUR">200.00</cbc:PriceAmount>
<cbc:BaseQuantity unitCode="C62">2</cbc:BaseQuantity>
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:Amount currencyID="EUR">0.00</cbc:Amount>
<cbc:BaseAmount currencyID="EUR">100.00</cbc:BaseAmount>
</cac:AllowanceCharge>
</cac:Price>11.11. Unit of measure
Unit of measure in an invoice allows the use of codes from UNECE Recommendation No. 20 (version 11e), as well as codes from UNECE Recommendation No. 21 prefixed with an X. Please also see Unità di misura for further information on the code lists.
| Code | Name |
|---|---|
H87 |
Piece |
KGM |
Kilogram |
MTR |
Meter |
LTR |
Litre |
MTK |
Square metre |
MTQ |
Cubic metre |
KTM |
Kilometre |
TNE |
Tonne (metric ton) |
KWH |
Kilowatt hour |
DAY |
Day |
HUR |
Hour |
MIN |
Minute |
| Code | Name |
|---|---|
XBG |
Bag |
XBX |
Box |
XCT |
Carton |
XCY |
Cylinder |
XBA |
Barrel |
XPK |
Package |
XPX |
Pallet |
XRL |
Reel |
XSA |
Sack |
XST |
Sheet |
<cbc:InvoicedQuantity unitCode="H87">10</cbc:InvoicedQuantity>(1)
<cbc:InvoicedQuantity unitCode="XPX">10</cbc:InvoicedQuantity>(2)| 1 | Code H87 from Recommendation no. 20 |
| 2 | Code PX, prefixed with an X from Recommendation no. 21 |
11.12. Tipo documento (estensione)
In aggiunta al tipo di fattura indicato nell’InvoiceTypeCode (es. 380 - fattura commerciale), il tipo documento indica in modo più preciso la tipologia di fattura, come ad esempio le fatture differite, le autofatture, ecc., secondo la normativa italiana.
Se il tipo documento non viene specificato, si intende la fattura commerciale (TD01).
<ext:UBLExtension>
<ext:ExtensionURI>urn:fdc:agid.gov.it:fatturapa:TipoDocumento</ext:ExtensionURI>
<ext:ExtensionContent>
<cbc:TypeCode>TD22</cbc:TypeCode>
</ext:ExtensionContent>
</ext:UBLExtension>11.13. Regime Fiscale (estensione)
Il regime fiscale indica il regime contabile associato al fornitore e pertanto le agevolazioni o semplificazioni a cui è soggetto.
Se il regime fiscale non viene specificato, si intende il regime ordinario (RF01).
<cac:AccountingSupplierParty>
<cac:Party>
...
<cac:PartyTaxScheme>
<cbc:CompanyID>IT07643520567</cbc:CompanyID>
<cbc:TaxLevelCode>RF19</cbc:TaxLevelCode>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
...
</cac:Party>
</cac:AccountingSupplierParty>11.14. Termini di pagamento
11.14.1. Termini e condizioni di pagamento
Il campo cac:PaymentTerms/cbc:Note deve essere usato solo per indicare il dato FPA 2.4.1 CondizioniPagamento e FPA 2.4.2.4 GiorniTerminiPagamento, concatenati con il simbolo "#".
<cac:PaymentTerms>
<cbc:Note>TP02</cbc:Note>
</cac:PaymentTerms><cac:PaymentTerms>
<cbc:Note>TP02#60</cbc:Note>
</cac:PaymentTerms>11.14.2. Pagamento Anticipato (estensione)
A fronte di un pagamento anticipato è possibile offrire uno sconto specificandone l’importo e la data limite entro il quale il pagamento deve essere perfezionato.
<cac:PaymentTerms>
<cbc:Note>TP02#60</cbc:Note>
<cbc:SettlementDiscountAmount currencyID="EUR">100.00</cbc:SettlementDiscountAmount>
<cac:SettlementPeriod>
<cbc:EndDate>2020-10-31</cbc:EndDate>
</cac:SettlementPeriod>
</cac:PaymentTerms>11.14.3. Pagamento Ritardato (estensione)
A fronte di un pagamento ritardato è possibile fissare una penalità specificandone l’importo dovuto e la data di decorrenza della penale.
<cac:PaymentTerms>
<cbc:Note>TP02#60</cbc:Note>
<cbc:PenaltyAmount currencyID="EUR">100.00</cbc:PenaltyAmount>
<cac:PenaltyPeriod>
<cbc:StartDate>2020-10-01</cbc:StartDate>
</cac:PenaltyPeriod>
</cac:PaymentTerms>11.15. Arrotondamento imponibile IVA nel riepilogo (estensione)
Eventuali arrotondamenti necessari a riportare al centesimo di euro le somme dei dati di dettaglio (imponibile) nel riepilogo IVA, possono essere forniti come estensione UBL in testata alla fattura.
<ext:UBLExtension>
<ext:ExtensionURI>urn:fdc:agid.gov.it:fatturapa:RiepilogoIVA:Arrotondamento::1</ext:ExtensionURI>
<ext:ExtensionContent>
<cbc:Amount currencyID="EUR">0.5</cbc:Amount>
</ext:ExtensionContent>
</ext:UBLExtension>
<ext:UBLExtension>
<ext:ExtensionURI>urn:fdc:agid.gov.it:fatturapa:RiepilogoIVA:Arrotondamento::2</ext:ExtensionURI>
<ext:ExtensionContent>
<cbc:Amount currencyID="EUR">0.8</cbc:Amount>
</ext:ExtensionContent>
</ext:UBLExtension>11.16. Altri dati gestionali
Il campi UBL cac:AdditionalItemProperty/cbc:Name e cac:AdditionalItemProperty/cbc:Value sono utilizzati per fornire informazioni riguardo il gruppo FPA Altri dati gestionali.
Il cac:AdditionalItemProperty/cbc:Name può essere valorizzato con "DatiVeicoli" (vedi par. 10.17),"Ritenuta" (vedi par. 4.7), "TipoCessionePrestazione" (vedi par. 10.9.3), "Natura" (vedi par. 7.3) oppure come segue:
-
Se cbc:Name è valorizzato con "Testo", allora compilare il cbc:Value con il dato FPA 2.2.1.16.2 RiferimentoTesto.
-
Se cbc:Name è valorizzato con "Numero", allora compilare il cbc:Value con il dato FPA 2.2.1.16.3 RiferimentoNumero.
-
Se cbc:Name è valorizzato con "Data", allora compilare il cbc:Value con il dato FPA 2.2.1.16.4 RiferimentoData.
11.17. Dati veicoli
Il campi UBL cac:AdditionalItemProperty/cbc:Name e cac:AdditionalItemProperty/cbc:Value sono utilizzati per fornire informazioni riguardo il gruppo FPA Dati Veicoli.
-
Se cbc:Name è valorizzato con "DatiVeicoli", allora compilare il cbc:Value con i dati FPA 2.3.1 Data e FPA 2.3.2 TotalePercorso concatenati con il simbolo "#".
12. Codifiche
I capitoli seguenti forniscono una panoramica sulle restrizioni applicate alle codifiche utilizzate in questa Peppol BIS. Per la maggior parte delle codifiche le restrizioni consistono nella sola aggiunta di una data di riferimento per la codifica, ma per la codifica Invoice Type Code è stato stabilito un sottoinsieme di valori validi.
12.1. Codifiche per elementi codificati
12.1.1. Codifica per il tipo di fattura (invoice type code) (BT-3)
I sotto paragrafi seguenti forniscono una panoramica sui codici tipo fattura permessi (BT-3) secondo questa specifica Peppol BIS Billing.
La tabella indica il nome e la descrizione di ogni codice, come pure una colonna "Sinonimo di" per indicare come può essere processato questo tipo di fattura se il destinatario non ha un flusso di elaborazione separato per questo tipo e come potrete osservare, tutte le tipologie di fattura valide in questo profilo possono essere processate come una fattura commerciale (380) e tutte le tipologie di note di credito come nota di credito commerciale (381). Alcuni destinatari potrebbero avere processi separati o flussi di elaborazione per alcuni di questi tipi e possono quindi utilizzare questi processi.
La tabella fornisce anche le informazioni su quale tipo di messaggio deve essere usato nella sintassi UBL per i diversi codici.
Codici specifici per la fattura
Il codice tipo per la fattura
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
| Codice | Nome | Descrizione | Sinonimo di | Tipo messaggio UBL |
|---|---|---|---|---|
380 |
Commercial invoice |
Documento/messaggio richiedente il pagamento per beni e servizi forniti alle condizioni accordate tra Fornitore e Cliente. |
|
|
393 |
Factored invoice |
Fattura assegnata ad una terza parte per la raccolta. |
380 |
|
82 |
Metered services invoice |
Documento/messaggio richiedente il pagamento per la fornitura di servizi a tariffa (e.g., gas, elettricità, etc.) forniti con una tariffa fissa ed il quale consumo è misurato in un periodo di tempo. |
380 |
|
80 |
Debit note related to goods or services |
Informazione di addebito relativa ad una transazione di beni e servizi. |
380 |
|
84 |
Debit note related to financial adjustments |
Documento/messaggio per fornire informazioni di addebito relative ad aggiustamenti finanziari. |
380 |
|
395 |
Consignment invoice |
Fattura commerciale che copre una transazione che non riguardi una vendita. |
380 |
|
575 |
Insurer’s invoice |
Documento/messaggio rilasciato da un assicuratore specificando il costo di un’assicurazione che è stata effettuata e per la quale si richiede il pagamento. |
380 |
|
623 |
Forwarder’s invoice |
Fattura emessa da uno speditore merci specificante i servizi forniti ed i costi incorsi e richiedente quindi il pagamento. |
380 |
|
780 |
Freight invoice |
Documento/messaggio emesso circa un’operazione di trasporto specificante le spese di trasporto e le maggiorazioni incorse per il trasporto e dichiarante delle condizioni di pagamento. |
380 |
|
383 |
Debit note |
Documento/messaggio per fornire informazioni di addebito alla parte interessata. |
380 |
|
386 |
Prepayment invoice |
Un fattura per pagare un ammontare per beni e servizi in anticipo; questi importi verranno sottratti dalla fattura finale. |
380 |
|
Codici specifici per la nota di credito
Il codice tipo per la nota di credito
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
| Codice | None | Descrizione | Sinonimo di | Tipo messaggio UBL |
|---|---|---|---|---|
381 |
Credit note |
Documento/messaggio per fornire informazioni relative ad un credito alla parte interessata. |
|
|
396 |
Factored credit note |
Nota di credito relativa ad una fattura(e) assegnata. |
381 |
|
81 |
Credit note related to goods or services |
Documento/messaggio usato per fornire informazioni circa un credito relativo ad una transazione di beni o servizi alla parte interessata. |
381 |
|
83 |
Credit note related to financial adjustments |
Documento/messaggio usato per fornire informazioni circa un credito relativo ad un aggiustamento finanziario (e.g., bonus). |
381 |
|
532 |
Forwarder’s credit note |
Documento/messaggio per fornire informazioni riguardo un credito alla parte interessata. |
381 |
|
12.1.2. Codice paese
Tutti i codici paese in una fattura o nota di credito devono essere espressi secondo la codifica alpha-2 di ISO 3166-1
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
12.1.3. Currency code
Tutte le valute in una fattura o nota di credito devono essere espresse secondo la codifica ISO 4217:2015
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
12.1.4. VAT category codes
Un sottoinsieme di valori della codifica UN/CEFACT code list 5305, D.16B deve essere usato.
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
Subset of UN/CEFACT code list 5305, D.16B |
I valori validi sono elencati nella tabella di seguito:
| Codice | Descrizione | Corrispondenza italiana |
|---|---|---|
AE |
Vat Reverse Charge |
Inversione contabile |
E |
Exempt from Tax |
Esente |
S |
Standard rate |
Imposta standard |
Z |
Zero rated goods |
Esclusa ex art. 15 |
G |
Free export item, tax not charged |
Non Imponibile (per le esportazioni) |
O |
Services outside scope of tax |
Fuori campo IVA |
K |
VAT exempt for EEA intra-community supply of goods and services |
Non Imponibile (per le esportazioni intra-EEA) |
L |
Canary Islands general indirect tax |
Imposta indiretta delle Isole Canarie |
M |
Tax for production, services and importation in Ceuta and Melilla |
Imposta per la produzione, servizi e importazione in Ceuta e Melilla |
B |
Transferred (VAT), In Italy |
Regime di Split Payment |
12.1.5. Unità di misura
I codici validi devono essere espressi secondo la codifica UN/ECE Recommendation 20, Revision 11 (2015). A meno che i codici per l’unità di misura non siano normalmente usati, gli implementatori dovrebbero, ove necessario, fornire una funzionalità per chiarire il codice quando le fatture vengono visualizzate.
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
12.1.6. Allowance reason codes
Tutti i codici di sconto devono essere espressi secondo la codifica UN/CEFACT code list 5189, D.16B
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
Subset of UN/CEFACT code list 5189, D.16B |
I valori validi sono elencati nella tabella di seguito:
| Codice | Descrizione |
|---|---|
41 |
Bonus for works ahead of schedule |
42 |
Other bonus |
60 |
Manufacturer’s consumer discount |
62 |
Due to military status |
63 |
Due to work accident |
64 |
Special agreement |
65 |
Production error discount |
66 |
New outlet discount |
67 |
Sample discount |
68 |
End-of-range discount |
70 |
Incoterm discount |
71 |
Point of sales threshold allowance |
88 |
Material surcharge/deduction |
95 |
Discount |
100 |
Special rebate |
102 |
Fixed long term |
103 |
Temporary |
104 |
Standard |
105 |
Yearly turnover |
12.1.7. Charge reason codes
Tutti i codici di maggiorazione devono essere espressi secondo la codifica UN/CEFACT code list 7161, D.16B
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
12.1.8. Media type code per i documenti allegati
Subset della codifica IANA Media Types.
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
Subset of IANA |
I valori validi sono elencati nella tabella di seguito.
Documenti |
application/pdf |
|---|---|
Imagini |
image/png |
image/jpeg |
|
Testo |
text/csv |
Spreadsheet |
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet |
application/vnd.oasis.opendocument.spreadsheet |
12.1.9. Termini di pagamento type code
Tutti i codici termini di pagamento devono essere espressi secondo la codifica UN/CEFACT code list 4461, D.16B
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
12.1.10. Codice Esigibilità IVA
Un sottoinsieme di valori della codifica Subset of UN/CEFACT code list 2005, D.16B deve essere usato.
Percorso nel documento |
|
|---|---|
Sorgente della codifica |
I valori validi sono elencati nella tabella di seguito:
| Codice | Descrizione |
|---|---|
3 |
Invoice document issue date time |
35 |
Delivery date/time, actual |
432 |
Paid to date |
12.1.11. Codice motivo esenzione IVA
EN 16931 autorizza l’uso di una code list manutenuta dal Connecting Europe Facility (CEF)
Percorso nel documento |
cac:TaxTotal/TaxSubtotal/TaxCategory/cbc:TaxExemptionReasonCode |
|---|---|
Sorgente della codifica |
12.2. Codifiche per schemi di identificatori
12.2.1. Schema per gli identificatori degli indirizzi elettronici
Per BT-49 e BT-34, gli identificatori degli indirizzi elettronici dei venditori e acquirenti (Endpoint identification), la EN 16931 richiede l’uso di una codifica manutenuta da Connecting Europe Facility (CEF).
| Termine di Business | XPath applicabile | Codifica (link or estratto) |
|---|---|---|
Electronic address identifier (Endpoint) |
cbc:EndpointID/@schemeID |
12.2.2. Schemi per gli identificatori delle parti di business e per la loro registrazione legale
Tutti gli identificatori delle parti di business e quelli per la loro registrazione legale hanno un attributo opzionale per fornire lo schema su cui si basano. Se utilizzato, il valore deve essere scelto fra quelli della codifica ICD secondo ISO/IEC 6523
| Termine di Business | XPath applicabile | Codifica (link or estratto) |
|---|---|---|
Identificatori delle Parti di business (Acquirente, Venditore, Pagatore) |
cac:PartyIdentification/cbc:ID/@schemeID |
ICD list from ISO/IEC 6523 |
Identificatori per la registrazione legale (Acquirente, Venditore, Pagatore) |
cac:PartyLegalEntity/cbc:CompanyID/@schemeID |
|
Identificatore per il luogo di consegna |
cac:Delivery/cac:DeliveryLocation/cbc:ID/@schemeID |
12.2.3. Schema per gli identificatori di un oggetto fatturato
Lo schema degli identificatori per un oggetto fatturato deve basarsi su UN/CEFACT code list 1153, D.16B
| Termine di Business | XPath applicabile | Codifica (link or estratto) |
|---|---|---|
Identificatore per l’oggetto fatturato |
cac:AdditionalDocumentReference[cbc:DocumentTypeCode = '130']/cbc:ID/@schemeID |
12.2.4. Schema per gli identificatori standard degli articoli
Per un identificatore standard per gli articoli l’uso dell’attributo schema è obbligatorio. Il valore deve essere scelto dalla codifica ICD secondo ISO/IEC 6523
| Termine di Business | XPath applicabile | Codifica (link or estratto) |
|---|---|---|
Identificatore standard per l’articolo |
cac:InvoiceLine/cac:Item/cac:StandardItemIdentification/cbc:ID/@schemeID |
ICD list from ISO/IEC 6523 |
12.2.5. Identificatore per la classificazione degli articoli
Un identificatore per la classificazione degli articoli ha l’attributo dello schema obbligatorio. Il valore deve essere scelto da UN/CEFACT code list 7143, D.16B.
| Termine di Business | XPath applicabile | Codifica (link or estratto) |
|---|---|---|
Identificatore per la classificazione dell’articolo |
cac:InvoiceLine/cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode/@listID |
13. Identificatori PEPPOL
Peppol ha definito una Peppol Policy for identifiers, policy 8 che specifica come utilizzare gli identificatori sia nella sua infrastruttura di trasporto che all’interno dei documenti scambiati su questa. Essa introduce anche i principi per ogni identificatore utilizzato nell’ambiente PEPPOL. Le regole che si applicano a questo BIS sono le seguenti:
13.1. Profili e messaggi
Tutti i messaggi contengono il ProfileID e il CustomizationID. Il ProfileID identifica di quale processo di business un dato messaggio è parte, e il CustomizationID identifica il tipo di messaggio e le regole applicate.
I profili sono connessi ad un processo di business e possono contenere molteplici tipologie di documenti (transazioni). Istanze valide dei documenti devono contenere i corrispondenti ProfileID e CustomizationID.
| Il CustomizationID è una stringa senza spazi. La tabella seguente contiene spazi in CustomizationID al solo scopo di renderlo più leggibile. Bisogna assicurarsi di rimuovere tutti gli spazi intermedi prima dell’uso. |
13.2. Identificatori per la customizzazione e profilo
L’innesco delle CIUS cross-border (vedi "Annex C.1") si attiva quando il BT-55 “Buyer country code” è popolato con IT e il BT-40 "Seller country code" è diverso da IT, mentre CIUS ed Estensioni domestiche (vedi "Annex C.2, C.3, C.4 e C.5") si attivano quando il BT-40 “Seller country code” è valorizzato a IT.
Il cbc:CustomizationID viene valorizzato quindi in funzione della valorizzazione presente in BT-40 e BT-55 così come segue:
-
BT-40 diverso da IT e BT-55 pari a IT, allora:
Elemento cbc:CustomizationID(BT-24 Specification identifier) |
Elemento cbc:ProfileID(BT-23 Business process
type) |
|---|---|
urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu :2017:poacc:billing:3.0#compliant#urn:www.agid.gov.it:trns:fattura:3 (rimuovere gli spazi prima dell’utilizzo) |
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 |
-
BT-40 pari a IT e BT-55 pari a IT, allora:
Elemento cbc:CustomizationID(BT-24 Specification identifier) |
Elemento cbc:ProfileID(BT-23 Business process
type) |
|---|---|
urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu :2017:poacc:billing:3.0#conformant#urn:www.agid.gov.it:trns:fattura:3 (rimuovere gli spazi prima dell’utilizzo) |
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 |
A titolo puramente esemplificativo e non esaustivo, si riporta a seguire come viene espresso l’identificativo per la fatturazione domestica (ovvero BT-40 pari a IT e BT-55 pari a IT):
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0#conformant#urn:www.agid.gov.it:trns:fattura:3</cbc:CustomizationID>14. UBL schemas and namespaces
The XML schemas used are
-
UBL Invoice 2.1 with the target namespace
urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 -
UBL CreditNote 2.1 with the target namespace
urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2
15. 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:
15.1. Validation Principles
Stages in the validation process:
- Validation of syntax
-
For example:
-
Check well-formedness
-
Tag names and attributes shall be correctly written and follow the UBL 2.1 sequence
-
All UBL 2.1 mandatory elements shall be present.
-
The element’s contents shall be according to the element’s type definition.
-
- Validation against EN 16931
-
To verify that the instance message is compliant to the european standard, like:
-
Valid codes for currencies, countries, tax etc.
-
Mandatory elements according to EN 16931.
-
Logical correlations between information element, i.e. that start date is lower than or equal to end date, calculations give the correct result etc.
-
- CIUS - General rules
-
General rule that applies to all invoices and are triggered by the existence of one or more specific business term(s).
-
Example rule text
An invoice shall have a buyers reference or an order reference -
Context that triggers the rule
Existence of either Buyer reference (BT-10) OR Purchased order reference (BT-13)
-
- CIUS - Country qualified validation rules
-
Applies only for invoices issued in a specific country. The rule is triggered by the given country code of the seller (BT-40).
-
Example rule text
When the Seller is Swedish, the Legal Registration Number shall be numeric with 10 digits. -
Context that triggers the rule
Existence of Seller/Address/CountryCode=‘SE’ AND existence of Seller/LegalRegistrationNumber
-
16. Transaction validation rules
16.1. Peppol transaction business rules
The following rules have been defined by OpenPEPPOL in addition to the rules adopted from EN 16931. These rules apply in all profiles that use this transaction specification.
Please also see [Restrictions on EN16931] for further details on the restrictions imposed by these rules.
| Rule | Message/Context/Test |
|---|---|
PEPPOL-COMMON-R040 (fatal) |
GLN must have a valid format according to GS1 rules. |
cbc:EndpointID[@schemeID = '0088'] | cac:PartyIdentification/cbc:ID[@schemeID = '0088'] | cbc:CompanyID[@schemeID = '0088'] |
|
matches(normalize-space(), '^[0-9]+$') and u:gln(normalize-space()) |
|
PEPPOL-COMMON-R041 (fatal) |
Norwegian organization number MUST be stated in the correct format. |
cbc:EndpointID[@schemeID = '0192'] | cac:PartyIdentification/cbc:ID[@schemeID = '0192'] | cbc:CompanyID[@schemeID = '0192'] |
|
matches(normalize-space(), '^[0-9]{9}$') and u:mod11(normalize-space()) |
|
PEPPOL-COMMON-R042 (fatal) |
Danish organization number (CVR) MUST be stated in the correct format. |
cbc:EndpointID[@schemeID = '0184'] | cac:PartyIdentification/cbc:ID[@schemeID = '0184'] | cbc:CompanyID[@schemeID = '0184'] |
|
(string-length(text()) = 10) and (substring(text(), 1, 2) = 'DK') and (string-length(translate(substring(text(), 3, 8), '1234567890', '')) = 0) |
|
PEPPOL-EN16931-CL001 (fatal) |
Mime code must be according to subset of IANA code list. |
cbc:EmbeddedDocumentBinaryObject[@mimeCode] |
|
some $code in $MIMECODE satisfies @mimeCode = $code |
|
PEPPOL-EN16931-CL002 (fatal) |
Reason code MUST be according to subset of UNCL 5189 D.16B. |
cac:AllowanceCharge[cbc:ChargeIndicator = 'false']/cbc:AllowanceChargeReasonCode |
|
some $code in $UNCL5189 satisfies normalize-space(text()) = $code |
|
PEPPOL-EN16931-CL003 (fatal) |
Reason code MUST be according to UNCL 7161 D.16B. |
cac:AllowanceCharge[cbc:ChargeIndicator = 'true']/cbc:AllowanceChargeReasonCode |
|
some $code in $UNCL7161 satisfies normalize-space(text()) = $code |
|
PEPPOL-EN16931-CL006 (fatal) |
Invoice period description code must be according to UNCL 2005 D.16B. |
cac:InvoicePeriod/cbc:DescriptionCode |
|
some $code in $UNCL2005 satisfies normalize-space(text()) = $code |
|
PEPPOL-EN16931-CL007 (fatal) |
Currency code must be according to ISO 4217:2005 |
cbc:Amount | cbc:BaseAmount | cbc:PriceAmount | cbc:TaxAmount | cbc:TaxableAmount | cbc:LineExtensionAmount | cbc:TaxExclusiveAmount | cbc:TaxInclusiveAmount | cbc:AllowanceTotalAmount | cbc:ChargeTotalAmount | cbc:PrepaidAmount | cbc:PayableRoundingAmount | cbc:PayableAmount |
|
some $code in $ISO4217 satisfies @currencyID = $code |
|
PEPPOL-EN16931-CL008 (fatal) |
Electronic address identifier scheme must be from the codelist "Electronic Address Identifier Scheme" |
cbc:EndpointID[@schemeID] |
|
some $code in $eaid satisfies @schemeID = $code |
|
PEPPOL-EN16931-F001 (fatal) |
A date MUST be formatted YYYY-MM-DD. |
cbc:IssueDate | cbc:DueDate | cbc:TaxPointDate | cbc:StartDate | cbc:EndDate | cbc:ActualDeliveryDate |
|
string-length(text()) = 10 and (string(.) castable as xs:date) |
|
PEPPOL-EN16931-P0100 (fatal) |
Invoice type code MUST be set according to the profile. |
cbc:InvoiceTypeCode |
|
$profile != '01' or (some $code in tokenize('380 383 386 393 82 80 84 395 575 623 780', '\s') satisfies normalize-space(text()) = $code) |
|
PEPPOL-EN16931-P0101 (fatal) |
Credit note type code MUST be set according to the profile. |
cbc:CreditNoteTypeCode |
|
$profile != '01' or (some $code in tokenize('381 396 81 83 532', '\s') satisfies normalize-space(text()) = $code) |
|
PEPPOL-EN16931-P0104 (fatal) |
Tax Category G MUST be used when exemption reason code is VATEX-EU-G |
cac:TaxCategory[upper-case(cbc:TaxExemptionReasonCode)='VATEX-EU-G'] |
|
normalize-space(cbc:ID)='G' |
|
PEPPOL-EN16931-P0105 (fatal) |
Tax Category O MUST be used when exemption reason code is VATEX-EU-O |
cac:TaxCategory[upper-case(cbc:TaxExemptionReasonCode)='VATEX-EU-O'] |
|
normalize-space(cbc:ID)='O' |
|
PEPPOL-EN16931-P0106 (fatal) |
Tax Category K MUST be used when exemption reason code is VATEX-EU-IC |
cac:TaxCategory[upper-case(cbc:TaxExemptionReasonCode)='VATEX-EU-IC'] |
|
normalize-space(cbc:ID)='K' |
|
PEPPOL-EN16931-P0107 (fatal) |
Tax Category AE MUST be used when exemption reason code is VATEX-EU-AE |
cac:TaxCategory[upper-case(cbc:TaxExemptionReasonCode)='VATEX-EU-AE'] |
|
normalize-space(cbc:ID)='AE' |
|
PEPPOL-EN16931-P0108 (fatal) |
Tax Category E MUST be used when exemption reason code is VATEX-EU-D |
cac:TaxCategory[upper-case(cbc:TaxExemptionReasonCode)='VATEX-EU-D'] |
|
normalize-space(cbc:ID)='E' |
|
PEPPOL-EN16931-P0109 (fatal) |
Tax Category E MUST be used when exemption reason code is VATEX-EU-F |
cac:TaxCategory[upper-case(cbc:TaxExemptionReasonCode)='VATEX-EU-F'] |
|
normalize-space(cbc:ID)='E' |
|
PEPPOL-EN16931-P0110 (fatal) |
Tax Category E MUST be used when exemption reason code is VATEX-EU-I |
cac:TaxCategory[upper-case(cbc:TaxExemptionReasonCode)='VATEX-EU-I'] |
|
normalize-space(cbc:ID)='E' |
|
PEPPOL-EN16931-P0111 (fatal) |
Tax Category E MUST be used when exemption reason code is VATEX-EU-J |
cac:TaxCategory[upper-case(cbc:TaxExemptionReasonCode)='VATEX-EU-J'] |
|
normalize-space(cbc:ID)='E' |
|
PEPPOL-EN16931-R001 (fatal) |
Business process MUST be provided. |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
cbc:ProfileID |
|
PEPPOL-EN16931-R002 (fatal) |
No more than one note is allowed on document level. |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
count(cbc:Note) ⇐ 1 |
|
PEPPOL-EN16931-R003 (fatal) |
A buyer reference or purchase order reference MUST be provided. |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
cbc:BuyerReference or cac:OrderReference/cbc:ID |
|
PEPPOL-EN16931-R004 (fatal) |
Specification identifier MUST have the value 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0'. |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
starts-with(normalize-space(cbc:CustomizationID/text()), 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0') |
|
PEPPOL-EN16931-R005 (fatal) |
VAT accounting currency code MUST be different from invoice currency code when provided. |
cbc:TaxCurrencyCode |
|
not(normalize-space(text()) = normalize-space(../cbc:DocumentCurrencyCode/text())) |
|
PEPPOL-EN16931-R006 (fatal) |
Only one invoiced object is allowed on document level |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
(count(cac:AdditionalDocumentReference[cbc:DocumentTypeCode='130']) ⇐ 1) |
|
PEPPOL-EN16931-R007 (fatal) |
Business process MUST be in the format 'urn:fdc:peppol.eu:2017:poacc:billing:NN:1.0' where NN indicates the process number. |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
$profile != 'Unknown' |
|
PEPPOL-EN16931-R008 (fatal) |
Document MUST not contain empty elements. |
//[not() and not(normalize-space())] |
|
false() |
|
PEPPOL-EN16931-R010 (fatal) |
Buyer electronic address MUST be provided |
cac:AccountingCustomerParty/cac:Party |
|
cbc:EndpointID |
|
PEPPOL-EN16931-R020 (fatal) |
Seller electronic address MUST be provided |
cac:AccountingSupplierParty/cac:Party |
|
cbc:EndpointID |
|
PEPPOL-EN16931-R040 (fatal) |
Allowance/charge amount must equal base amount * percentage/100 if base amount and percentage exists |
ubl-invoice:Invoice/cac:AllowanceCharge | ubl-invoice:Invoice/cac:InvoiceLine/cac:AllowanceCharge | ubl-creditnote:CreditNote/cac:AllowanceCharge | ubl-creditnote:CreditNote/cac:CreditNoteLine/cac:AllowanceCharge |
|
not(cbc:MultiplierFactorNumeric and cbc:BaseAmount) or u:slack(if (cbc:Amount) then cbc:Amount else 0, (xs:decimal(cbc:BaseAmount) * xs:decimal(cbc:MultiplierFactorNumeric)) div 100, 0.02) |
|
PEPPOL-EN16931-R041 (fatal) |
Allowance/charge base amount MUST be provided when allowance/charge percentage is provided. |
ubl-invoice:Invoice/cac:AllowanceCharge[cbc:MultiplierFactorNumeric and not(cbc:BaseAmount)] | ubl-invoice:Invoice/cac:InvoiceLine/cac:AllowanceCharge[cbc:MultiplierFactorNumeric and not(cbc:BaseAmount)] | ubl-creditnote:CreditNote/cac:AllowanceCharge[cbc:MultiplierFactorNumeric and not(cbc:BaseAmount)] | ubl-creditnote:CreditNote/cac:CreditNoteLine/cac:AllowanceCharge[cbc:MultiplierFactorNumeric and not(cbc:BaseAmount)] |
|
false() |
|
PEPPOL-EN16931-R042 (fatal) |
Allowance/charge percentage MUST be provided when allowance/charge base amount is provided. |
ubl-invoice:Invoice/cac:AllowanceCharge[not(cbc:MultiplierFactorNumeric) and cbc:BaseAmount] | ubl-invoice:Invoice/cac:InvoiceLine/cac:AllowanceCharge[not(cbc:MultiplierFactorNumeric) and cbc:BaseAmount] | ubl-creditnote:CreditNote/cac:AllowanceCharge[not(cbc:MultiplierFactorNumeric) and cbc:BaseAmount] | ubl-creditnote:CreditNote/cac:CreditNoteLine/cac:AllowanceCharge[not(cbc:MultiplierFactorNumeric) and cbc:BaseAmount] |
|
false() |
|
PEPPOL-EN16931-R043 (fatal) |
Allowance/charge ChargeIndicator value MUST equal 'true' or 'false' |
ubl-invoice:Invoice/cac:AllowanceCharge | ubl-invoice:Invoice/cac:InvoiceLine/cac:AllowanceCharge | ubl-creditnote:CreditNote/cac:AllowanceCharge | ubl-creditnote:CreditNote/cac:CreditNoteLine/cac:AllowanceCharge |
|
normalize-space(cbc:ChargeIndicator/text()) = 'true' or normalize-space(cbc:ChargeIndicator/text()) = 'false' |
|
PEPPOL-EN16931-R044 (fatal) |
Charge on price level is NOT allowed. |
cac:Price/cac:AllowanceCharge |
|
normalize-space(cbc:ChargeIndicator) = 'false' |
|
PEPPOL-EN16931-R046 (fatal) |
Item net price MUST equal (Gross price - Allowance amount) when gross price is provided. |
cac:Price/cac:AllowanceCharge |
|
not(cbc:BaseAmount) or xs:decimal(../cbc:PriceAmount) = xs:decimal(cbc:BaseAmount) - xs:decimal(cbc:Amount) |
|
PEPPOL-EN16931-R051 (fatal) |
All currencyID attributes must have the same value as the invoice currency code (BT-5), except for the invoice total VAT amount in accounting currency (BT-111). |
cbc:Amount | cbc:BaseAmount | cbc:PriceAmount | cac:TaxTotal[cac:TaxSubtotal]/cbc:TaxAmount | cbc:TaxableAmount | cbc:LineExtensionAmount | cbc:TaxExclusiveAmount | cbc:TaxInclusiveAmount | cbc:AllowanceTotalAmount | cbc:ChargeTotalAmount | cbc:PrepaidAmount | cbc:PayableRoundingAmount | cbc:PayableAmount |
|
@currencyID = $documentCurrencyCode |
|
PEPPOL-EN16931-R053 (fatal) |
Only one tax total with tax subtotals MUST be provided. |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
count(cac:TaxTotal[cac:TaxSubtotal]) = 1 |
|
PEPPOL-EN16931-R054 (fatal) |
Only one tax total without tax subtotals MUST be provided when tax currency code is provided. |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
count(cac:TaxTotal[not(cac:TaxSubtotal)]) = (if (cbc:TaxCurrencyCode) then 1 else 0) |
|
PEPPOL-EN16931-R055 (fatal) |
Invoice total VAT amount and Invoice total VAT amount in accounting currency MUST have the same operational sign |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
not(cbc:TaxCurrencyCode) or (cac:TaxTotal/cbc:TaxAmount[@currencyID=normalize-space(../../cbc:TaxCurrencyCode)] ⇐ 0 and cac:TaxTotal/cbc:TaxAmount[@currencyID=normalize-space(../../cbc:DocumentCurrencyCode)] ⇐ 0) or (cac:TaxTotal/cbc:TaxAmount[@currencyID=normalize-space(../../cbc:TaxCurrencyCode)] >= 0 and cac:TaxTotal/cbc:TaxAmount[@currencyID=normalize-space(../../cbc:DocumentCurrencyCode)] >= 0) |
|
PEPPOL-EN16931-R061 (fatal) |
Mandate reference MUST be provided for direct debit. |
cac:PaymentMeans[some $code in tokenize('49 59', '\s')satisfies normalize-space(cbc:PaymentMeansCode) = $code] |
|
cac:PaymentMandate/cbc:ID |
|
PEPPOL-EN16931-R080 (fatal) |
Only one project reference is allowed on document level |
ubl-creditnote:CreditNote | ubl-invoice:Invoice |
|
(count(cac:AdditionalDocumentReference[cbc:DocumentTypeCode='50']) ⇐ 1) |
|
PEPPOL-EN16931-R100 (fatal) |
Only one invoiced object is allowed pr line |
cac:InvoiceLine | cac:CreditNoteLine |
|
(count(cac:DocumentReference) ⇐ 1) |
|
PEPPOL-EN16931-R101 (fatal) |
Element Document reference can only be used for Invoice line object |
cac:InvoiceLine | cac:CreditNoteLine |
|
(not(cac:DocumentReference) or (cac:DocumentReference/cbc:DocumentTypeCode='130')) |
|
PEPPOL-EN16931-R110 (fatal) |
Start date of line period MUST be within invoice period. |
ubl-invoice:Invoice[cac:InvoicePeriod/cbc:StartDate]/cac:InvoiceLine/cac:InvoicePeriod/cbc:StartDate | ubl-creditnote:CreditNote[cac:InvoicePeriod/cbc:StartDate]/cac:CreditNoteLine/cac:InvoicePeriod/cbc:StartDate |
|
xs:date(text()) >= xs:date(../../../cac:InvoicePeriod/cbc:StartDate) |
|
PEPPOL-EN16931-R111 (fatal) |
End date of line period MUST be within invoice period. |
ubl-invoice:Invoice[cac:InvoicePeriod/cbc:EndDate]/cac:InvoiceLine/cac:InvoicePeriod/cbc:EndDate | ubl-creditnote:CreditNote[cac:InvoicePeriod/cbc:EndDate]/cac:CreditNoteLine/cac:InvoicePeriod/cbc:EndDate |
|
xs:date(text()) ⇐ xs:date(../../../cac:InvoicePeriod/cbc:EndDate) |
|
PEPPOL-EN16931-R120 (fatal) |
Invoice line net amount MUST equal (Invoiced quantity * (Item net price/item price base quantity) + Sum of invoice line charge amount - sum of invoice line allowance amount |
cac:InvoiceLine | cac:CreditNoteLine |
|
u:slack($lineExtensionAmount, ($quantity * ($priceAmount div $baseQuantity)) + $chargesTotal - $allowancesTotal, 0.02) |
|
PEPPOL-EN16931-R121 (fatal) |
Base quantity MUST be a positive number above zero. |
cac:InvoiceLine | cac:CreditNoteLine |
|
not(cac:Price/cbc:BaseQuantity) or xs:decimal(cac:Price/cbc:BaseQuantity) > 0 |
|
PEPPOL-EN16931-R130 (fatal) |
Unit code of price base quantity MUST be same as invoiced quantity. |
cac:Price/cbc:BaseQuantity[@unitCode] |
|
not($hasQuantity) or @unitCode = $quantity/@unitCode |
16.2. EN 16931 transaction business rules
The following EN 16931 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 EN 16931. Further details can be found at https://github.com/OpenPEPPOL/tc434-validation.
| Rule | Message |
|---|---|
BR-01 (fatal) |
[BR-01]-An Invoice shall have a Specification identifier (BT-24). |
BR-02 (fatal) |
[BR-02]-An Invoice shall have an Invoice number (BT-1). |
BR-03 (fatal) |
[BR-03]-An Invoice shall have an Invoice issue date (BT-2). |
BR-04 (fatal) |
[BR-04]-An Invoice shall have an Invoice type code (BT-3). |
BR-05 (fatal) |
[BR-05]-An Invoice shall have an Invoice currency code (BT-5). |
BR-06 (fatal) |
[BR-06]-An Invoice shall contain the Seller name (BT-27). |
BR-07 (fatal) |
[BR-07]-An Invoice shall contain the Buyer name (BT-44). |
BR-08 (fatal) |
[BR-08]-An Invoice shall contain the Seller postal address. |
BR-09 (fatal) |
[BR-09]-The Seller postal address (BG-5) shall contain a Seller country code (BT-40). |
BR-10 (fatal) |
[BR-10]-An Invoice shall contain the Buyer postal address (BG-8). |
BR-11 (fatal) |
[BR-11]-The Buyer postal address shall contain a Buyer country code (BT-55). |
BR-12 (fatal) |
[BR-12]-An Invoice shall have the Sum of Invoice line net amount (BT-106). |
BR-13 (fatal) |
[BR-13]-An Invoice shall have the Invoice total amount without VAT (BT-109). |
BR-14 (fatal) |
[BR-14]-An Invoice shall have the Invoice total amount with VAT (BT-112). |
BR-15 (fatal) |
[BR-15]-An Invoice shall have the Amount due for payment (BT-115). |
BR-16 (fatal) |
[BR-16]-An Invoice shall have at least one Invoice line (BG-25) |
BR-17 (fatal) |
[BR-17]-The Payee name (BT-59) shall be provided in the Invoice, if the Payee (BG-10) is different from the Seller (BG-4) |
BR-18 (fatal) |
[BR-18]-The Seller tax representative name (BT-62) shall be provided in the Invoice, if the Seller (BG-4) has a Seller tax representative party (BG-11) |
BR-19 (fatal) |
[BR-19]-The Seller tax representative postal address (BG-12) shall be provided in the Invoice, if the Seller (BG-4) has a Seller tax representative party (BG-11). |
BR-20 (fatal) |
[BR-20]-The Seller tax representative postal address (BG-12) shall contain a Tax representative country code (BT-69), if the Seller (BG-4) has a Seller tax representative party (BG-11). |
BR-21 (fatal) |
[BR-21]-Each Invoice line (BG-25) shall have an Invoice line identifier (BT-126). |
BR-22 (fatal) |
[BR-22]-Each Invoice line (BG-25) shall have an Invoiced quantity (BT-129). |
BR-23 (fatal) |
[BR-23]-An Invoice line (BG-25) shall have an Invoiced quantity unit of measure code (BT-130). |
BR-24 (fatal) |
[BR-24]-Each Invoice line (BG-25) shall have an Invoice line net amount (BT-131). |
BR-25 (fatal) |
[BR-25]-Each Invoice line (BG-25) shall contain the Item name (BT-153). |
BR-26 (fatal) |
[BR-26]-Each Invoice line (BG-25) shall contain the Item net price (BT-146). |
BR-27 (fatal) |
[BR-27]-The Item net price (BT-146) shall NOT be negative. |
BR-28 (fatal) |
[BR-28]-The Item gross price (BT-148) shall NOT be negative. |
BR-29 (fatal) |
[BR-29]-If both Invoicing period start date (BT-73) and Invoicing period end date (BT-74) are given then the Invoicing period end date (BT-74) shall be later or equal to the Invoicing period start date (BT-73). |
BR-30 (fatal) |
[BR-30]-If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the Invoice line period end date (BT-135) shall be later or equal to the Invoice line period start date (BT-134). |
BR-31 (fatal) |
[BR-31]-Each Document level allowance (BG-20) shall have a Document level allowance amount (BT-92). |
BR-32 (fatal) |
[BR-32]-Each Document level allowance (BG-20) shall have a Document level allowance VAT category code (BT-95). |
BR-33 (fatal) |
[BR-33]-Each Document level allowance (BG-20) shall have a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98). |
BR-36 (fatal) |
[BR-36]-Each Document level charge (BG-21) shall have a Document level charge amount (BT-99). |
BR-37 (fatal) |
[BR-37]-Each Document level charge (BG-21) shall have a Document level charge VAT category code (BT-102). |
BR-38 (fatal) |
[BR-38]-Each Document level charge (BG-21) shall have a Document level charge reason (BT-104) or a Document level charge reason code (BT-105). |
BR-41 (fatal) |
[BR-41]-Each Invoice line allowance (BG-27) shall have an Invoice line allowance amount (BT-136). |
BR-42 (fatal) |
[BR-42]-Each Invoice line allowance (BG-27) shall have an Invoice line allowance reason (BT-139) or an Invoice line allowance reason code (BT-140). |
BR-43 (fatal) |
[BR-43]-Each Invoice line charge (BG-28) shall have an Invoice line charge amount (BT-141). |
BR-44 (fatal) |
[BR-44]-Each Invoice line charge shall have an Invoice line charge reason or an invoice line allowance reason code. |
BR-45 (fatal) |
[BR-45]-Each VAT breakdown (BG-23) shall have a VAT category taxable amount (BT-116). |
BR-46 (fatal) |
[BR-46]-Each VAT breakdown (BG-23) shall have a VAT category tax amount (BT-117). |
BR-47 (fatal) |
[BR-47]-Each VAT breakdown (BG-23) shall be defined through a VAT category code (BT-118). |
BR-48 (fatal) |
[BR-48]-Each VAT breakdown (BG-23) shall have a VAT category rate (BT-119), except if the Invoice is not subject to VAT. |
BR-49 (fatal) |
[BR-49]-A Payment instruction (BG-16) shall specify the Payment means type code (BT-81). |
BR-50 (fatal) |
[BR-50]-A Payment account identifier (BT-84) shall be present if Credit transfer (BG-17) information is provided in the Invoice. |
BR-51 (fatal) |
[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-52 (fatal) |
[BR-52]-Each Additional supporting document (BG-24) shall contain a Supporting document reference (BT-122). |
BR-53 (fatal) |
[BR-53]-If the VAT accounting currency code (BT-6) is present, then the Invoice total VAT amount in accounting currency (BT-111) shall be provided. |
BR-54 (fatal) |
[BR-54]-Each Item attribute (BG-32) shall contain an Item attribute name (BT-160) and an Item attribute value (BT-161). |
BR-55 (fatal) |
[BR-55]-Each Preceding Invoice reference (BG-3) shall contain a Preceding Invoice reference (BT-25). |
BR-56 (fatal) |
[BR-56]-Each Seller tax representative party (BG-11) shall have a Seller tax representative VAT identifier (BT-63). |
BR-57 (fatal) |
[BR-57]-Each Deliver to address (BG-15) shall contain a Deliver to country code (BT-80). |
BR-61 (fatal) |
[BR-61]-If the Payment means type code (BT-81) means SEPA credit transfer, Local credit transfer or Non-SEPA international credit transfer, the Payment account identifier (BT-84) shall be present. |
BR-62 (fatal) |
[BR-62]-The Seller electronic address (BT-34) shall have a Scheme identifier. |
BR-63 (fatal) |
[BR-63]-The Buyer electronic address (BT-49) shall have a Scheme identifier. |
BR-64 (fatal) |
[BR-64]-The Item standard identifier (BT-157) shall have a Scheme identifier. |
BR-65 (fatal) |
[BR-65]-The Item classification identifier (BT-158) shall have a Scheme identifier. |
BR-66 (fatal) |
[BR-66]-An Invoice shall contain maximum one Payment Card account (BG-18). |
BR-67 (fatal) |
[BR-67]-An Invoice shall contain maximum one Payment Mandate (BG-19). |
BR-AE-01 (fatal) |
[BR-AE-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 "Reverse charge" shall contain in the VAT Breakdown (BG-23) exactly one VAT category code (BT-118) equal with "VAT reverse charge". |
BR-AE-02 (fatal) |
[BR-AE-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Reverse charge" 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) and the Buyer VAT identifier (BT-48) and/or the Buyer legal registration identifier (BT-47). |
BR-AE-03 (fatal) |
[BR-AE-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Reverse charge" 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) and the Buyer VAT identifier (BT-48) and/or the Buyer legal registration identifier (BT-47). |
BR-AE-04 (fatal) |
[BR-AE-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Reverse charge" 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) and the Buyer VAT identifier (BT-48) and/or the Buyer legal registration identifier (BT-47). |
BR-AE-05 (fatal) |
[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-AE-06 (fatal) |
[BR-AE-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Reverse charge" the Document level allowance VAT rate (BT-96) shall be 0 (zero). |
BR-AE-07 (fatal) |
[BR-AE-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Reverse charge" the Document level charge VAT rate (BT-103) shall be 0 (zero). |
BR-AE-08 (fatal) |
[BR-AE-08]-In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Reverse charge" 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 "Reverse charge". |
BR-AE-09 (fatal) |
[BR-AE-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Reverse charge" shall be 0 (zero). |
BR-AE-10 (fatal) |
[BR-AE-10]-A VAT breakdown (BG-23) with VAT Category code (BT-118) "Reverse charge" shall have a VAT exemption reason code (BT-121), meaning "Reverse charge" or the VAT exemption reason text (BT-120) "Reverse charge" (or the equivalent standard text in another language). |
BR-B-01 (fatal) |
[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 (fatal) |
[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”. |
BR-CL-01 (fatal) |
[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 (fatal) |
[BR-CL-03]-currencyID MUST be coded using ISO code list 4217 alpha-3 |
BR-CL-04 (fatal) |
[BR-CL-04]-Invoice currency code MUST be coded using ISO code list 4217 alpha-3 |
BR-CL-05 (fatal) |
[BR-CL-05]-Tax currency code MUST be coded using ISO code list 4217 alpha-3 |
BR-CL-06 (fatal) |
[BR-CL-06]-Value added tax point date code MUST be coded using a restriction of UNTDID 2005. |
BR-CL-07 (fatal) |
[BR-CL-07]-Object identifier identification scheme identifier MUST be coded using a restriction of UNTDID 1153. |
BR-CL-08 (fatal) |
[BR-CL-08]-Invoiced note subject code SHOULD be coded using UNCL4451 |
BR-CL-10 (fatal) |
[BR-CL-10]-Any identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. |
BR-CL-11 (fatal) |
[BR-CL-11]-Any registration identifier identification scheme identifier MUST be coded using one of the ISO 6523 ICD list. |
BR-CL-13 (fatal) |
[BR-CL-13]-Item classification identifier identification scheme identifier MUST be coded using one of the UNTDID 7143 list. |
BR-CL-14 (fatal) |
[BR-CL-14]-Country codes in an invoice MUST be coded using ISO code list 3166-1 |
BR-CL-15 (fatal) |
[BR-CL-15]-Country codes in an invoice MUST be coded using ISO code list 3166-1 |
BR-CL-16 (fatal) |
[BR-CL-16]-Payment means in an invoice MUST be coded using UNCL4461 code list |
BR-CL-17 (fatal) |
[BR-CL-17]-Invoice tax categories MUST be coded using UNCL5305 code list |
BR-CL-18 (fatal) |
[BR-CL-18]-Invoice tax categories MUST be coded using UNCL5305 code list |
BR-CL-19 (fatal) |
[BR-CL-19]-Coded allowance reasons MUST belong to the UNCL 5189 code list |
BR-CL-20 (fatal) |
[BR-CL-20]-Coded charge reasons MUST belong to the UNCL 7161 code list |
BR-CL-21 (fatal) |
[BR-CL-21]-Item standard identifier scheme identifier MUST belong to the ISO 6523 ICD code list |
BR-CL-22 (fatal) |
[BR-CL-22]-Tax exemption reason code identifier scheme identifier MUST belong to the CEF VATEX code list |
BR-CL-23 (fatal) |
[BR-CL-23]-Unit code MUST be coded according to the UN/ECE Recommendation 20 with Rec 21 extension |
BR-CL-24 (fatal) |
[BR-CL-24]-For Mime code in attribute use MIMEMediaType. |
BR-CL-25 (fatal) |
[BR-CL-25]-Endpoint identifier scheme identifier MUST belong to the CEF EAS code list |
BR-CL-26 (fatal) |
[BR-CL-26]-Delivery location identifier scheme identifier MUST belong to the ISO 6523 ICD code list |
BR-CO-03 (fatal) |
[BR-CO-03]-Value added tax point date (BT-7) and Value added tax point date code (BT-8) are mutually exclusive. |
BR-CO-04 (fatal) |
[BR-CO-04]-Each Invoice line (BG-25) shall be categorized with an Invoiced item VAT category code (BT-151). |
BR-CO-05 (fatal) |
[BR-CO-05]-Document level allowance reason code (BT-98) and Document level allowance reason (BT-97) shall indicate the same type of allowance. |
BR-CO-06 (fatal) |
[BR-CO-06]-Document level charge reason code (BT-105) and Document level charge reason (BT-104) shall indicate the same type of charge. |
BR-CO-07 (fatal) |
[BR-CO-07]-Invoice line allowance reason code (BT-140) and Invoice line allowance reason (BT-139) shall indicate the same type of allowance reason. |
BR-CO-08 (fatal) |
[BR-CO-08]-Invoice line charge reason code (BT-145) and Invoice line charge reason (BT144) shall indicate the same type of charge reason. |
BR-CO-09 (fatal) |
[BR-CO-09]-The Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48) shall have a prefix in accordance with ISO code ISO 3166-1 alpha-2 by which the country of issue may be identified. Nevertheless, Greece may use the prefix ‘EL’. |
BR-CO-10 (fatal) |
[BR-CO-10]-Sum of Invoice line net amount (BT-106) = Σ Invoice line net amount (BT-131). |
BR-CO-11 (fatal) |
[BR-CO-11]-Sum of allowances on document level (BT-107) = Σ Document level allowance amount (BT-92). |
BR-CO-12 (fatal) |
[BR-CO-12]-Sum of charges on document level (BT-108) = Σ Document level charge amount (BT-99). |
BR-CO-13 (fatal) |
[BR-CO-13]-Invoice total amount without VAT (BT-109) = Σ Invoice line net amount (BT-131) - Sum of allowances on document level (BT-107) + Sum of charges on document level (BT-108). |
BR-CO-14 (fatal) |
[BR-CO-14]-Invoice total VAT amount (BT-110) = Σ VAT category tax amount (BT-117). |
BR-CO-15 (fatal) |
[BR-CO-15]-Invoice total amount with VAT (BT-112) = Invoice total amount without VAT (BT-109) + Invoice total VAT amount (BT-110). |
BR-CO-16 (fatal) |
[BR-CO-16]-Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) -Paid amount (BT-113) +Rounding amount (BT-114). |
BR-CO-17 (fatal) |
[BR-CO-17]-VAT category tax amount (BT-117) = VAT category taxable amount (BT-116) x (VAT category rate (BT-119) / 100), rounded to two decimals. |
BR-CO-18 (fatal) |
[BR-CO-18]-An Invoice shall at least have one VAT breakdown group (BG-23). |
BR-CO-19 (fatal) |
[BR-CO-19]-If Invoicing period (BG-14) is used, the Invoicing period start date (BT-73) or the Invoicing period end date (BT-74) shall be filled, or both. |
BR-CO-20 (fatal) |
[BR-CO-20]-If Invoice line period (BG-26) is used, the Invoice line period start date (BT-134) or the Invoice line period end date (BT-135) shall be filled, or both. |
BR-CO-21 (fatal) |
[BR-CO-21]-Each Document level allowance (BG-20) shall contain a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98), or both. |
BR-CO-22 (fatal) |
[BR-CO-22]-Each Document level charge (BG-21) shall contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both. |
BR-CO-23 (fatal) |
[BR-CO-23]-Each Invoice line allowance (BG-27) shall contain an Invoice line allowance reason (BT-139) or an Invoice line allowance reason code (BT-140), or both. |
BR-CO-24 (fatal) |
[BR-CO-24]-Each Invoice line charge (BG-28) shall contain an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145), or both. |
BR-CO-25 (fatal) |
[BR-CO-25]-In case the Amount due for payment (BT-115) is positive, either the Payment due date (BT-9) or the Payment terms (BT-20) shall be present. |
BR-CO-26 (fatal) |
[BR-CO-26]-In order for the buyer to automatically identify a supplier, the Seller identifier (BT-29), the Seller legal registration identifier (BT-30) and/or the Seller VAT identifier (BT-31) shall be present. |
BR-DEC-01 (fatal) |
[BR-DEC-01]-The allowed maximum number of decimals for the Document level allowance amount (BT-92) is 2. |
BR-DEC-02 (fatal) |
[BR-DEC-02]-The allowed maximum number of decimals for the Document level allowance base amount (BT-93) is 2. |
BR-DEC-05 (fatal) |
[BR-DEC-05]-The allowed maximum number of decimals for the Document level charge amount (BT-99) is 2. |
BR-DEC-06 (fatal) |
[BR-DEC-06]-The allowed maximum number of decimals for the Document level charge base amount (BT-100) is 2. |
BR-DEC-09 (fatal) |
[BR-DEC-09]-The allowed maximum number of decimals for the Sum of Invoice line net amount (BT-106) is 2. |
BR-DEC-10 (fatal) |
[BR-DEC-10]-The allowed maximum number of decimals for the Sum of allowanced on document level (BT-107) is 2. |
BR-DEC-11 (fatal) |
[BR-DEC-11]-The allowed maximum number of decimals for the Sum of charges on document level (BT-108) is 2. |
BR-DEC-12 (fatal) |
[BR-DEC-12]-The allowed maximum number of decimals for the Invoice total amount without VAT (BT-109) is 2. |
BR-DEC-13 (fatal) |
[BR-DEC-13]-The allowed maximum number of decimals for the Invoice total VAT amount (BT-110) is 2. |
BR-DEC-14 (fatal) |
[BR-DEC-14]-The allowed maximum number of decimals for the Invoice total amount with VAT (BT-112) is 2. |
BR-DEC-15 (fatal) |
[BR-DEC-15]-The allowed maximum number of decimals for the Invoice total VAT amount in accounting currency (BT-111) is 2. |
BR-DEC-16 (fatal) |
[BR-DEC-16]-The allowed maximum number of decimals for the Paid amount (BT-113) is 2. |
BR-DEC-17 (fatal) |
[BR-DEC-17]-The allowed maximum number of decimals for the Rounding amount (BT-114) is 2. |
BR-DEC-18 (fatal) |
[BR-DEC-18]-The allowed maximum number of decimals for the Amount due for payment (BT-115) is 2. |
BR-DEC-19 (fatal) |
[BR-DEC-19]-The allowed maximum number of decimals for the VAT category taxable amount (BT-116) is 2. |
BR-DEC-20 (fatal) |
[BR-DEC-20]-The allowed maximum number of decimals for the VAT category tax amount (BT-117) is 2. |
BR-DEC-23 (fatal) |
[BR-DEC-23]-The allowed maximum number of decimals for the Invoice line net amount (BT-131) is 2. |
BR-DEC-24 (fatal) |
[BR-DEC-24]-The allowed maximum number of decimals for the Invoice line allowance amount (BT-136) is 2. |
BR-DEC-25 (fatal) |
[BR-DEC-25]-The allowed maximum number of decimals for the Invoice line allowance base amount (BT-137) is 2. |
BR-DEC-27 (fatal) |
[BR-DEC-27]-The allowed maximum number of decimals for the Invoice line charge amount (BT-141) is 2. |
BR-DEC-28 (fatal) |
[BR-DEC-28]-The allowed maximum number of decimals for the Invoice line charge base amount (BT-142) is 2. |
BR-E-01 (fatal) |
[BR-E-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 "Exempt from VAT" shall contain exactly one VAT breakdown (BG-23) with the VAT category code (BT-118) equal to "Exempt from VAT". |
BR-E-02 (fatal) |
[BR-E-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Exempt from VAT" 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-E-03 (fatal) |
[BR-E-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Exempt from VAT" 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-E-04 (fatal) |
[BR-E-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Exempt from VAT" 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-E-05 (fatal) |
[BR-E-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Exempt from VAT", the Invoiced item VAT rate (BT-152) shall be 0 (zero). |
BR-E-06 (fatal) |
[BR-E-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Exempt from VAT", the Document level allowance VAT rate (BT-96) shall be 0 (zero). |
BR-E-07 (fatal) |
[BR-E-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Exempt from VAT", the Document level charge VAT rate (BT-103) shall be 0 (zero). |
BR-E-08 (fatal) |
[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". |
BR-E-09 (fatal) |
[BR-E-09]-The VAT category tax amount (BT-117) In a VAT breakdown (BG-23) where the VAT category code (BT-118) equals "Exempt from VAT" shall equal 0 (zero). |
BR-E-10 (fatal) |
[BR-E-10]-A VAT breakdown (BG-23) with VAT Category code (BT-118) "Exempt from VAT" shall have a VAT exemption reason code (BT-121) or a VAT exemption reason text (BT-120). |
BR-G-01 (fatal) |
[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-G-02 (fatal) |
[BR-G-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Export outside the EU" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63). |
BR-G-03 (fatal) |
[BR-G-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Export outside the EU" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63). |
BR-G-04 (fatal) |
[BR-G-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Export outside the EU" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63). |
BR-G-05 (fatal) |
[BR-G-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Export outside the EU" the Invoiced item VAT rate (BT-152) shall be 0 (zero). |
BR-G-06 (fatal) |
[BR-G-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Export outside the EU" the Document level allowance VAT rate (BT-96) shall be 0 (zero). |
BR-G-07 (fatal) |
[BR-G-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Export outside the EU" the Document level charge VAT rate (BT-103) shall be 0 (zero). |
BR-G-08 (fatal) |
[BR-G-08]-In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Export outside the EU" 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 "Export outside the EU". |
BR-G-09 (fatal) |
[BR-G-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Export outside the EU" shall be 0 (zero). |
BR-G-10 (fatal) |
[BR-G-10]-A VAT breakdown (BG-23) with the VAT Category code (BT-118) "Export outside the EU" shall have a VAT exemption reason code (BT-121), meaning "Export outside the EU" or the VAT exemption reason text (BT-120) "Export outside the EU" (or the equivalent standard text in another language). |
BR-IC-01 (fatal) |
[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-IC-02 (fatal) |
[BR-IC-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Intra-community supply" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48). |
BR-IC-03 (fatal) |
[BR-IC-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Intra-community supply" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48). |
BR-IC-04 (fatal) |
[BR-IC-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Intra-community supply" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48). |
BR-IC-05 (fatal) |
[BR-IC-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Intracommunity supply" the Invoiced item VAT rate (BT-152) shall be 0 (zero). |
BR-IC-06 (fatal) |
[BR-IC-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Intra-community supply" the Document level allowance VAT rate (BT-96) shall be 0 (zero). |
BR-IC-07 (fatal) |
[BR-IC-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Intra-community supply" the Document level charge VAT rate (BT-103) shall be 0 (zero). |
BR-IC-08 (fatal) |
[BR-IC-08]-In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" 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 "Intra-community supply". |
BR-IC-09 (fatal) |
[BR-IC-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" shall be 0 (zero). |
BR-IC-10 (fatal) |
[BR-IC-10]-A VAT breakdown (BG-23) with the VAT Category code (BT-118) "Intra-community supply" shall have a VAT exemption reason code (BT-121), meaning "Intra-community supply" or the VAT exemption reason text (BT-120) "Intra-community supply" (or the equivalent standard text in another language). |
BR-IC-11 (fatal) |
[BR-IC-11]-In an Invoice with a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" the Actual delivery date (BT-72) or the Invoicing period (BG-14) shall not be blank. |
BR-IC-12 (fatal) |
[BR-IC-12]-In an Invoice with a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" the Deliver to country code (BT-80) shall not be blank. |
BR-IG-01 (fatal) |
[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-IG-02 (fatal) |
[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-03 (fatal) |
[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-04 (fatal) |
[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-05 (fatal) |
[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 0 (zero) or greater than zero. |
BR-IG-06 (fatal) |
[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-IG-07 (fatal) |
[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-IG-08 (fatal) |
[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 (fatal) |
[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 (fatal) |
[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-IP-01 (fatal) |
[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-IP-02 (fatal) |
[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-03 (fatal) |
[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-04 (fatal) |
[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-05 (fatal) |
[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-IP-06 (fatal) |
[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-IP-07 (fatal) |
[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-IP-08 (fatal) |
[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 (fatal) |
[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 (fatal) |
[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-O-01 (fatal) |
[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-O-02 (fatal) |
[BR-O-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Not subject to VAT" shall not contain the Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) or the Buyer VAT identifier (BT-48). |
BR-O-03 (fatal) |
[BR-O-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Not subject to VAT" shall not contain the Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) or the Buyer VAT identifier (BT-48). |
BR-O-04 (fatal) |
[BR-O-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Not subject to VAT" shall not contain the Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) or the Buyer VAT identifier (BT-48). |
BR-O-05 (fatal) |
[BR-O-05]-An Invoice line (BG-25) where the VAT category code (BT-151) is "Not subject to VAT" shall not contain an Invoiced item VAT rate (BT-152). |
BR-O-06 (fatal) |
[BR-O-06]-A Document level allowance (BG-20) where VAT category code (BT-95) is "Not subject to VAT" shall not contain a Document level allowance VAT rate (BT-96). |
BR-O-07 (fatal) |
[BR-O-07]-A Document level charge (BG-21) where the VAT category code (BT-102) is "Not subject to VAT" shall not contain a Document level charge VAT rate (BT-103). |
BR-O-08 (fatal) |
[BR-O-08]-In a VAT breakdown (BG-23) where the VAT category code (BT-118) is " Not subject to 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 "Not subject to VAT". |
BR-O-09 (fatal) |
[BR-O-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Not subject to VAT" shall be 0 (zero). |
BR-O-10 (fatal) |
[BR-O-10]-A VAT breakdown (BG-23) with VAT Category code (BT-118) " Not subject to VAT" shall have a VAT exemption reason code (BT-121), meaning " Not subject to VAT" or a VAT exemption reason text (BT-120) " Not subject to VAT" (or the equivalent standard text in another language). |
BR-O-11 (fatal) |
[BR-O-11]-An Invoice that contains a VAT breakdown group (BG-23) with a VAT category code (BT-118) "Not subject to VAT" shall not contain other VAT breakdown groups (BG-23). |
BR-O-12 (fatal) |
[BR-O-12]-An Invoice that contains a VAT breakdown group (BG-23) with a VAT category code (BT-118) "Not subject to VAT" shall not contain an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is not "Not subject to VAT". |
BR-O-13 (fatal) |
[BR-O-13]-An Invoice that contains a VAT breakdown group (BG-23) with a VAT category code (BT-118) "Not subject to VAT" shall not contain Document level allowances (BG-20) where Document level allowance VAT category code (BT-95) is not "Not subject to VAT". |
BR-O-14 (fatal) |
[BR-O-14]-An Invoice that contains a VAT breakdown group (BG-23) with a VAT category code (BT-118) "Not subject to VAT" shall not contain Document level charges (BG-21) where Document level charge VAT category code (BT-102) is not "Not subject to VAT". |
BR-S-01 (fatal) |
[BR-S-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 "Standard rated" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "Standard rated". |
BR-S-02 (fatal) |
[BR-S-02]-An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Standard rated" 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-S-03 (fatal) |
[BR-S-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Standard rated" 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-S-04 (fatal) |
[BR-S-04]-An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Standard rated" 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-S-05 (fatal) |
[BR-S-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Standard rated" the Invoiced item VAT rate (BT-152) shall be greater than zero. |
BR-S-06 (fatal) |
[BR-S-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Standard rated" the Document level allowance VAT rate (BT-96) shall be greater than zero. |
BR-S-07 (fatal) |
[BR-S-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Standard rated" the Document level charge VAT rate (BT-103) shall be greater than zero. |
BR-S-08 (fatal) |
[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 (fatal) |
[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 (fatal) |
[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). |
BR-Z-01 (fatal) |
[BR-Z-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 "Zero rated" shall contain in the VAT breakdown (BG-23) exactly one VAT category code (BT-118) equal with "Zero rated". |
BR-Z-02 (fatal) |
[BR-Z-02]-An Invoice that contains an Invoice line where the Invoiced item VAT category code (BT-151) is "Zero rated" 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-Z-03 (fatal) |
[BR-Z-03]-An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Zero rated" 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-Z-04 (fatal) |
[BR-Z-04]-An Invoice that contains a Document level charge where the Document level charge VAT category code (BT-102) is "Zero rated" 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-Z-05 (fatal) |
[BR-Z-05]-In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Zero rated" the Invoiced item VAT rate (BT-152) shall be 0 (zero). |
BR-Z-06 (fatal) |
[BR-Z-06]-In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Zero rated" the Document level allowance VAT rate (BT-96) shall be 0 (zero). |
BR-Z-07 (fatal) |
[BR-Z-07]-In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Zero rated" the Document level charge VAT rate (BT-103) shall be 0 (zero). |
BR-Z-08 (fatal) |
[BR-Z-08]-In a VAT breakdown (BG-23) where VAT category code (BT-118) is "Zero rated" the VAT category taxable amount (BT-116) shall equal the sum of Invoice line net amount (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 "Zero rated". |
BR-Z-09 (fatal) |
[BR-Z-09]-The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "Zero rated" shall equal 0 (zero). |
BR-Z-10 (fatal) |
[BR-Z-10]-A VAT breakdown (BG-23) with VAT Category code (BT-118) "Zero rated" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120). |
Appendix A: Restrictions and Extensions on EN16931
Below is a list of the restrictions on EN 16931 that is done in this {CIUS}. In addition to these rules, some national rules gives further restrictions based on the seller country or VAT country.
A list of these national rules can be found in National rules
Nello specifico contesto italiano, valgono ulteriori restrizioni/estensioni.
Le restrizioni per la fatturazione italiana cross-border (BT-40 Seller country code diverso da IT e BT-55 Buyer country code pari a IT) sono riportate al paragrafo Annex C.1.
Le restrizioni per la fatturazione domestica italiana (BT-40 Seller country code pari da IT e BT-55 Buyer country code pari a IT) sono riportate al paragrafo Annex C.2.
Le restrizioni per la fatturazione domestica italiana (BT-40 Seller country code pari da IT e BT-55 Buyer country code pari a IT) verso i privati, sono riportate al paragrafo Annex C.3.
Le estensioni per la fatturazione domestica italiana (BT-40 Seller country code pari da IT e BT-55 Buyer country code pari a IT) sono riportate al paragrafo Annex C.4.
Le estensioni per la fatturazione domestica italiana (BT-40 Seller country code pari da IT e BT-55 Buyer country code pari a IT) verso i privati, sono riportate al paragrafo Annex C.5.
Le restrizioni sotto riportate sono espresse come indicato nel capitolo 7.3.2 della EN 16931.
A.1. Restrictions for profile 01 - Billing
| BT-ID | Business Term | Restrition Type | Description | Rule |
|---|---|---|---|---|
BT-3 |
Invoice type code |
Mark defined values as not allowed |
Allowed set of values can be found in [Invoice Type Code] |
PEPPOL-EN16931-P0100, PEPPOL-EN16931-P0101 |
A.2. Restrictions on the invoice and credit note transaction
| BT-ID | Business Term | Restrition Type | Description | Rule |
|---|---|---|---|---|
BT-2 , BT-7 , BT-9 , BT-26, BT-72, BT-73, BT-74, BT-134, BT-135 |
All date elements |
Add new non-conflicting business rule to existing element(s) |
A date shall be formatted |
PEPPOL-EN16931-F001 |
BT-6 |
VAT accounting currency code |
Add new non-conflicting business rule to existing element(s) |
VAT accounting currency code shall be different from invoice currency code when provided. |
PEPPOL-EN16931-R005 |
BT-9, BT-20 |
Payment due date or payment terms |
Change to existing CEN TC434 rule (issue reported to TC434) |
Ensure the rule only fires for invoices, not credit notes |
BR-CO-25 |
BT-10, BT-13 |
Buyer reference or Purchase order |
Add new non-conflicting business rule to existing element(s) |
A buyer reference or purchase order reference shall be provided. |
PEPPOL-EN16931-R003 |
BG-1 |
Invoice note |
Decrease number of repetitions (x..n – > x..1) |
Change cardinality from 0..n to 0..1 |
PEPPOL-EN16931-R002 |
BT-21 |
Invoice note subject code |
Mark conditional information element not to be used |
Changing cardinality 0..1 to 0..0 |
Not applicable |
BT-23 |
Business process type |
Make a conditional element mandatory (0..x – > 1..x) |
Changing cardinality 0..1 to 1..1 |
PEPPOL-EN16931-R001 |
BT-24 |
Specification identifier |
Add new non-conflicting business rule to existing element(s) |
Specification identifier shall have the value |
PEPPOL-EN16931-R004 |
BT-34 |
Seller electronic address |
Make a conditional element mandatory (0..x – > 1..x) |
Seller electronic address shall be provided |
PEPPOL-EN16931-R020 |
BT-49 |
Buyer electronic address |
Make a conditional element mandatory (0..x – > 1..x) |
Buyer electronic address shall be provided |
PEPPOL-EN16931-R010 |
BG-19 |
Direct debit |
Add new non-conflicting business rule to existing element(s) |
Mandate reference shall be provided for direct debit. |
PEPPOL-EN16931-R061 |
BT-93, BT-100, BT-137, BT-142 |
Allowance/charge base amount |
Add new non-conflicting business rule to existing element(s) |
Allowance/charge base amount shall be provided when allowance/charge percentage is provided. |
PEPPOL-EN16931-R041 |
BT-94, BT-101, BT-138, BT-143 |
Allowance/charge percentage |
Add new non-conflicting business rule to existing element(s) |
Allowance/charge percentage shall be provided when allowance/charge base amount is provided. |
PEPPOL-EN16931-R042 |
BT-92, BT-99, BT-136, BT-141 |
Allowance/charge amount |
Add new non-conflicting business rule to existing element(s) |
If base amount and percentage exists in the instance, then |
PEPPOL-EN16931-R040 |
BT-98, BT-140 |
Allowance reason code |
Mark defined values as not allowed |
Reason code shall be according to subset of UNCL 5189 D.16B. |
PEPPOL-EN16931-CL002 |
BT-110 |
Invoice total VAT amount |
Add new non-conflicting business rule to existing element(s) |
Only one tax total without tax subtotals shall be provided when tax currency code is provided. |
PEPPOL-EN16931-R054 |
BG-23 |
VAT breakdown |
Add new non-conflicting business rule to existing element(s) |
Only one tax total with tax subtotals shall be provided |
PEPPOL-EN16931-R053 |
BG-23 |
VAT breakdown |
Add new non-conflicting business rule to existing element(s) |
Only one tax total without tax subtotals shall be provided when tax currency code is provided. |
PEPPOL-EN16931-R054 |
BT-131 |
Invoice line net amount |
Add new non-conflicting business rule to existing element(s) |
Calculation shall equal
\$ ("Invoiced quantity" times ("Item net price" div "item price base quantity"))\$ |
PEPPOL-EN16931-R120 |
BT-134 |
Invoice line period start date |
Add new non-conflicting business rule to existing element(s) |
Start date of line period shall be within invoice period. |
PEPPOL-EN16931-R110 |
BT-135 |
Invoice line period end date |
Add new non-conflicting business rule to existing element(s) |
End date of line period shall be within invoice period. |
PEPPOL-EN16931-R111 |
BT-146 |
Item net price |
Add new non-conflicting business rule to existing element(s) |
Item net price shall equal (Gross price - Allowance amount) when gross price is provided. |
PEPPOL-EN16931-R046 |
BT-149 |
Item price base quantity |
Add new non-conflicting business rule to existing element(s) |
Base quantity shall be a positive number above zero. |
PEPPOL-EN16931-R121 |
BT-150 |
Item price base quantity unit of measure |
Add new non-conflicting business rule to existing element(s) |
Unit code of price base quantity shall be same as invoiced quantity. |
PEPPOL-EN16931-R130 |
Not applicable |
All currencyID attributes |
Add new non-conflicting business rule to existing element(s) |
All currencyID attributes shall have the same value as the invoice currency code (BT-5), except for the invoice total VAT amount in accounting currency (BT-111) |
PEPPOL-EN16931-R051 |
A.3. Restrictions on the supported processes
This {CIUS} has made restrictions to not explicitly support the following business processes:
- 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.
- 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.
A.4. Known Issues for profile 01 - Billing
| BT-ID | Business Term | Known Issue | Work Around |
|---|---|---|---|
BT-60, BT-90 |
Payee identifier with cardinality, Bank assigned creditor identifier |
In the EN 16931 data model BT-60 and BT-90 are business terms that are defined independently of each other. Both map onto PayeeParty/PartyIdentification/ID. However, the cardinalities stated in the syntax block simultaneous use of the BT-60 and BT-90 identifiers. This situation might arise if the payment provision is to be based on factored SEPA direct debit. |
None |
Appendix B: Cross Industry Invoice
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.
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]
Appendix C: National rules
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.
| Rule | Message/Context/Test |
|---|---|
DK-R-002 (fatal) |
Danish suppliers MUST provide legal entity (CVR-number) |
ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK'] | ubl-invoice:Invoice[$DKSupplierCountry = 'DK'] |
|
(normalize-space(cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID/text()) != '') |
|
DK-R-003 (warning) |
If ItemClassification is provided from Danish suppliers, UNSPSC version 19.0501 should be used. |
ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:CreditNoteLine | ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:InvoiceLine |
|
not((cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode/@listID = 'TST') and not((cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode/@listVersionID = '19.05.01') or (cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode/@listVersionID = '19.0501') ) ) |
|
DK-R-004 (fatal) |
When specifying non-VAT Taxes, Danish suppliers MUST use the AllowanceChargeReasonCode="ZZZ" and the 4-digit Tax category MUST be specified in 'AllowanceChargeReason' |
cac:AllowanceCharge[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK'] |
|
notcbc:AllowanceChargeReasonCode = 'ZZZ') and not((string-length(normalize-space(cbc:AllowanceChargeReason/text() = 4) and (number(cbc:AllowanceChargeReason) >= 0) and (number(cbc:AllowanceChargeReason) ⇐ 9999)) ) |
|
DK-R-005 (fatal) |
For Danish suppliers the following Payment means codes are allowed: 1, 10, 31, 42, 48, 49, 50, 58, 59, 93 and 97 |
ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:PaymentMeans |
|
contains(' 1 10 31 42 48 49 50 58 59 93 97 ', concat(' ', cbc:PaymentMeansCode, ' ')) |
|
DK-R-006 (fatal) |
For Danish suppliers bank account and registration account is mandatory if payment means is 31 or 42 |
ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:PaymentMeans |
|
not(cbc:PaymentMeansCode = '31') or (cbc:PaymentMeansCode = '42' and notnormalize-space(cac:PayeeFinancialAccount/cbc:ID/text( != '') and (normalize-space(cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cbc:ID/text()) != '')) ) |
|
DK-R-007 (fatal) |
For Danish suppliers PaymentMandate/ID and PayerFinancialAccount/ID are mandatory when payment means is 49 |
ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:PaymentMeans |
|
notcbc:PaymentMeansCode = '49') and not((normalize-space(cac:PaymentMandate/cbc:ID/text( != '') and (normalize-space(cac:PaymentMandate/cac:PayerFinancialAccount/cbc:ID/text()) != '')) ) |
|
DK-R-008 (fatal) |
For Danish Suppliers PaymentID is mandatory and MUST start with 01#, 04# or 15# (kortartkode), and PayeeFinancialAccount/ID (Giro kontonummer) is mandatory and must be 7 characters long, when payment means equals 50 (Giro) |
ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:PaymentMeans |
|
notcbc:PaymentMeansCode = '50') and not(((substring(cbc:PaymentID, 1, 3) = '01#') or (substring(cbc:PaymentID, 1, 3) = '04#') or (substring(cbc:PaymentID, 1, 3) = '15#' and (string-length(cac:PayeeFinancialAccount/cbc:ID/text()) = 7) ) ) |
|
DK-R-009 (fatal) |
For Danish Suppliers if the PaymentID is prefixed with 04# or 15# the 16 digits instruction Id must be added to the PaymentID eg. "04#1234567890123456" when Payment means equals 50 (Giro) |
ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:PaymentMeans |
|
notcbc:PaymentMeansCode = '50') and ((substring(cbc:PaymentID, 1, 3) = '04#') or (substring(cbc:PaymentID, 1, 3) = '15#' and not(string-length(cbc:PaymentID) = 19) ) |
|
DK-R-010 (fatal) |
For Danish Suppliers the PaymentID is mandatory and MUST start with 71#, 73# or 75# (kortartkode) and PayeeFinancialAccount/ID (Kreditornummer) is mandatory and must be exactly 8 characters long, when Payment means equals 93 (FIK) |
ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:PaymentMeans |
|
notcbc:PaymentMeansCode = '93') and not(((substring(cbc:PaymentID, 1, 3) = '71#') or (substring(cbc:PaymentID, 1, 3) = '73#') or (substring(cbc:PaymentID, 1, 3) = '75#' and (string-length(cac:PayeeFinancialAccount/cbc:ID/text()) = 8) ) ) |
|
DK-R-011 (fatal) |
For Danish Suppliers if the PaymentID is prefixed with 71# or 75# the 15-16 digits instruction Id must be added to the PaymentID eg. "71#1234567890123456" when payment Method equals 93 (FIK) |
ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:PaymentMeans |
|
notcbc:PaymentMeansCode = '93') and ((substring(cbc:PaymentID, 1, 3) = '71#') or (substring(cbc:PaymentID, 1, 3) = '75#' and notstring-length(cbc:PaymentID) = 18) or (string-length(cbc:PaymentID) = 19 ) |
|
DK-R-013 (fatal) |
For Danish Suppliers it is mandatory to use schemeID when PartyIdentification/ID is used for AccountingCustomerParty or AccountingSupplierParty |
ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification | ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification | ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification | ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification |
|
notboolean(cbc:ID and (normalize-space(cbc:ID/@schemeID) = '') ) |
|
DK-R-014 (fatal) |
For Danish Suppliers it is mandatory to specify schemeID as "0184" (DK CVR-number) when PartyLegalEntity/CompanyID is used for AccountingSupplierParty |
ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK'] | ubl-invoice:Invoice[$DKSupplierCountry = 'DK'] |
|
not(boolean(cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID and (normalize-space(cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID/@schemeID) != '0184')) ) |
|
DK-R-015 (fatal) |
For Danish Suppliers, if specified, AccountingSupplierParty/PartyTaxScheme/CompanyID (DK VAT number) must start with DK followed by 8 digits |
ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK'] | ubl-invoice:Invoice[$DKSupplierCountry = 'DK'] |
|
notnormalize-space(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[1]/cac:TaxScheme/cbc:ID/text( = 'VAT') and not string-length(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[1]/cbc:CompanyID/text( = 10) and (substring(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[1]/cbc:CompanyID/text(), 1, 2) = 'DK') and (string-length(translate(substring(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[1]/cbc:CompanyID/text(), 3, 8), '1234567890', '')) = 0)) or (normalize-space(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[2]/cac:TaxScheme/cbc:ID/text()) = 'VAT') and not string-length(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[2]/cbc:CompanyID/text( = 10) and (substring(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[2]/cbc:CompanyID/text(), 1, 2) = 'DK') and (string-length(translate(substring(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[2]/cbc:CompanyID/text(), 3, 8), '1234567890', '')) = 0)) ) |
|
DK-R-016 (fatal) |
For Danish Suppliers, a Credit note cannot have a negative total (PayableAmount) |
ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK'] | ubl-invoice:Invoice[$DKSupplierCountry = 'DK'] |
|
notboolean(/ubl-creditnote:CreditNote) and ($DKCustomerCountry = 'DK' and (number(cac:LegalMonetaryTotal/cbc:PayableAmount/text()) < 0)) |
|
GR-R-001-1 (fatal) |
When the Supplier is Greek, the Invoice Id should consist of 6 segments |
/ubl-invoice:Invoice/cbc:ID[$isGreekSender] | /ubl-creditnote:CreditNote/cbc:ID[$isGreekSender] |
|
count($IdSegments) = 6 |
|
GR-R-001-2 (fatal) |
When the Supplier is Greek, the Invoice Id first segment must be a valid TIN Number and match either the Supplier’s or the Tax Representative’s Tin Number |
/ubl-invoice:Invoice/cbc:ID[$isGreekSender] | /ubl-creditnote:CreditNote/cbc:ID[$isGreekSender] |
|
string-length(normalize-space($IdSegments[1])) = 9 and u:TinVerification($IdSegments[1]) and ($IdSegments[1] = //cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 3, 9) or $IdSegments[1] = //cac:TaxRepresentativeParty/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 3, 9) ) |
|
GR-R-001-3 (fatal) |
When the Supplier is Greek, the Invoice Id second segment must be a valid Date that matches the invoice Issue Date |
/ubl-invoice:Invoice/cbc:ID[$isGreekSender] | /ubl-creditnote:CreditNote/cbc:ID[$isGreekSender] |
|
string-length(normalize-space($IdSegments[2]))>0 and matches($IdSegments[2],$dateRegExp) and ($tokenizedIdDate[1] = $tokenizedUblIssueDate[3] and $tokenizedIdDate[2] = $tokenizedUblIssueDate[2] and $tokenizedIdDate[3] = $tokenizedUblIssueDate[1]) |
|
GR-R-001-4 (fatal) |
When Supplier is Greek, the Invoice Id third segment must be a positive integer |
/ubl-invoice:Invoice/cbc:ID[$isGreekSender] | /ubl-creditnote:CreditNote/cbc:ID[$isGreekSender] |
|
string-length(normalize-space($IdSegments[3]))>0 and string(number($IdSegments[3])) != 'NaN' and xs:integer($IdSegments[3]) >= 0 |
|
GR-R-001-5 (fatal) |
When Supplier is Greek, the Invoice Id in the fourth segment must be a valid greek document type |
/ubl-invoice:Invoice/cbc:ID[$isGreekSender] | /ubl-creditnote:CreditNote/cbc:ID[$isGreekSender] |
|
string-length(normalize-space($IdSegments[4]))>0 and (some $c in $greekDocumentType satisfies $IdSegments[4] = $c) |
|
GR-R-001-6 (fatal) |
When Supplier is Greek, the Invoice Id fifth segment must not be empty |
/ubl-invoice:Invoice/cbc:ID[$isGreekSender] | /ubl-creditnote:CreditNote/cbc:ID[$isGreekSender] |
|
[small]#string-length($IdSegments[5]) > 0 # |
|
GR-R-001-7 (fatal) |
When Supplier is Greek, the Invoice Id sixth segment must not be empty |
/ubl-invoice:Invoice/cbc:ID[$isGreekSender] | /ubl-creditnote:CreditNote/cbc:ID[$isGreekSender] |
|
[small]#string-length($IdSegments[6]) > 0 # |
|
GR-R-002 (fatal) |
Greek Suppliers must provide their full name as they are registered in the Greek Business Registry (G.E.MH.) as a legal entity or in the Tax Registry as a natural person |
cac:AccountingSupplierParty[$isGreekSender]/cac:Party |
|
string-length(./cac:PartyName/cbc:Name)>0 |
|
GR-R-003 (fatal) |
For the Greek Suppliers, the VAT must start with 'EL' and must be a valid TIN number |
cac:AccountingSupplierParty[$isGreekSender]/cac:Party/cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID |
|
substring(.,1,2) = 'EL' and u:TinVerification(substring(.,3)) |
|
GR-R-004-1 (fatal) |
When Supplier is Greek, there must be one MARK Number |
/ubl-invoice:Invoice[$isGreekSender] | /ubl-creditnote:CreditNote[$isGreekSender] |
|
count(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'M.AR.K'])=1 |
|
GR-R-004-2 (fatal) |
When Supplier is Greek, the MARK Number must be a positive integer |
cac:AdditionalDocumentReference[$isGreekSender and cbc:DocumentDescription = 'M.AR.K']/cbc:ID |
|
matches(.,'^[1-9]([0-9]*)') |
|
GR-R-005 (fatal) |
Greek Suppliers must provide the full name of the buyer |
cac:AccountingCustomerParty[$isGreekSender]/cac:Party |
|
matches(.,'^[1-9]([0-9]*)') |
|
GR-R-006 (fatal) |
Greek Suppliers must provide the VAT number of the buyer, if the buyer is Greek |
cac:AccountingCustomerParty[$isGreekSenderandReceiver]/cac:Party |
|
count(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID)=1 and substring(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID,1,2) = 'EL' and u:TinVerification(substring(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID,3)) |
|
GR-R-007-1 (fatal) |
When greek supplier does not have a VAT number, the tax representative must be present |
cac:AccountingSupplierParty[$isGreekSender]/cac:Party |
|
[small]# count(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID) = 1 or count(/ubl-invoice:Invoice/cac:TaxRepresentativeParty) = 1# |
|
GR-R-007-2 (fatal) |
If the Greek Suppliers do not have Greek VAT they must provide the full name of their tax representative in Greece |
cac:TaxRepresentativeParty[$isGreekSender] |
|
string-length(normalize-space(cac:PartyName/cbc:Name))>0 |
|
GR-R-007-3 (fatal) |
If the Greek Suppliers do not have Greek VAT, they must provide the VAT number of their tax representative |
cac:TaxRepresentativeParty[$isGreekSender |
|
count(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID)=1 and substring(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID,1,2) = 'EL' and u:TinVerification(substring(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID,3)) |
|
GR-R-008-2 (fatal) |
When Supplier is Greek, there should be no more than one invoice url |
/ubl-invoice:Invoice[$isGreekSender] | /ubl-creditnote:CreditNote[$isGreekSender] |
|
(count(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'INVOICE-URL']) = 0 ) or (count(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'INVOICE-URL']) = 1 ) |
|
GR-R-008-3 (fatal) |
When Supplier is Greek and the INVOICE URL Document reference exists, the External Reference URI should be present |
cac:AdditionalDocumentReference[$isGreekSender and cbc:DocumentDescription = 'INVOICE-URL'] |
|
string-length(normalize-space(cac:Attachment/cac:ExternalReference/cbc:URI))>0 |
|
GR-R-008-9 (fatal) |
Greek suppliers that send an invoice through the Peppol network must use a correct TIN number as an electronic address according to Peppol Electronic Address Identifier scheme (schemeID 9933). |
cac:AccountingSupplierParty/cac:Party[$accountingSupplierCountry='GR' or $accountingSupplierCountry='EL']/cbc:EndpointID |
|
./@schemeID='9933' and u:TinVerification(.) |
|
GR-R-009 (fatal) |
Greek suppliers that send an invoice through the Peppol network must use a correct TIN number as an electronic address according to Peppol Electronic Address Identifier scheme (schemeID 9933). |
cac:AccountingSupplierParty/cac:Party[$accountingSupplierCountry='GR' or $accountingSupplierCountry='EL']/cbc:EndpointID |
|
./@schemeID='9933' and u:TinVerification(.) |
|
GR-R-010 (fatal) |
Greek Suppliers that send an invoice through the Peppol network to a greek buyer must use a correct TIN number as an electronic address according to Peppol Electronic Address Identifier scheme (SchemeID 9933) |
cac:AccountingCustomerParty[$isGreekSenderandReceiver]/cac:Party/cbc:EndpointID |
|
./@schemeID='9933' and u:TinVerification(.) |
|
IS-R-001 (warning) |
[IS-R-001]-If seller is icelandic then invoice type should be 380 or 381 — Ef seljandi er íslenskur þá ætti gerð reiknings (BT-3) að vera sölureikningur (380) eða kreditreikningur (381). |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS'] | ubl-invoice:Invoice[$SupplierCountry = 'IS'] |
|
( ( not(contains(normalize-space(cbc:InvoiceTypeCode),' ')) and contains( ' 380 381 ',concat(' ',normalize-space(cbc:InvoiceTypeCode),' ') ) ) ) or ( ( not(contains(normalize-space(cbc:CreditNoteTypeCode),' ')) and contains( ' 380 381 ',concat(' ',normalize-space(cbc:CreditNoteTypeCode),' ') ) ) ) |
|
IS-R-002 (fatal) |
[IS-R-002]-If seller is icelandic then it shall contain sellers legal id — Ef seljandi er íslenskur þá skal reikningur innihalda íslenska kennitölu seljanda (BT-30). |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS'] | ubl-invoice:Invoice[$SupplierCountry = 'IS'] |
|
exists(cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID) and cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID/@schemeID = '0196' |
|
IS-R-003 (fatal) |
[IS-R-003]-If seller is icelandic then it shall contain his address with street name and zip code — Ef seljandi er íslenskur þá skal heimilisfang seljanda innihalda götuheiti og póstnúmer (BT-35 og BT-38). |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS'] | ubl-invoice:Invoice[$SupplierCountry = 'IS'] |
|
exists(cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:StreetName) and exists(cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:PostalZone) |
|
IS-R-004 (fatal) |
[IS-R-004]-If seller and buyer are icelandic then the invoice shall contain the buyers icelandic legal identifier — Ef seljandi og kaupandi eru íslenskir þá skal reikningurinn innihalda íslenska kennitölu kaupanda (BT-47). |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS' and $CustomerCountry = 'IS']/cac:AccountingCustomerParty | ubl-invoice:Invoice[$SupplierCountry = 'IS' and $CustomerCountry = 'IS']/cac:AccountingCustomerParty |
|
exists(cac:Party/cac:PartyLegalEntity/cbc:CompanyID) and cac:Party/cac:PartyLegalEntity/cbc:CompanyID/@schemeID = '0196' |
|
IS-R-005 (fatal) |
[IS-R-005]-If seller and buyer are icelandic then the invoice shall contain the buyers address with street name and zip code — Ef seljandi og kaupandi eru íslenskir þá skal heimilisfang kaupanda innihalda götuheiti og póstnúmer (BT-50 og BT-53) |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS' and $CustomerCountry = 'IS']/cac:AccountingCustomerParty | ubl-invoice:Invoice[$SupplierCountry = 'IS' and $CustomerCountry = 'IS']/cac:AccountingCustomerParty |
|
exists(cac:Party/cac:PostalAddress/cbc:StreetName) and exists(cac:Party/cac:PostalAddress/cbc:PostalZone) |
|
IS-R-006 (fatal) |
[IS-R-006]-If seller is icelandic and payment means code is 9 then a 12 digit account id must exist — Ef seljandi er íslenskur og greiðslumáti (BT-81) er millifærsla (kóti 9) þá skal koma fram 12 stafa reikningnúmer (BT-84) |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS'] | ubl-invoice:Invoice[$SupplierCountry = 'IS'] |
|
exists(cac:PaymentMeans[cbc:PaymentMeansCode = '9']/cac:PayeeFinancialAccount/cbc:ID) and string-length(normalize-space(cac:PaymentMeans[cbc:PaymentMeansCode = '9']/cac:PayeeFinancialAccount/cbc:ID)) = 12 or not(exists(cac:PaymentMeans[cbc:PaymentMeansCode = '9'])) |
|
IS-R-007 (fatal) |
[IS-R-007]-If seller is icelandic and payment means code is 42 then a 12 digit account id must exist — Ef seljandi er íslenskur og greiðslumáti (BT-81) er millifærsla (kóti 42) þá skal koma fram 12 stafa reikningnúmer (BT-84) |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS'] | ubl-invoice:Invoice[$SupplierCountry = 'IS'] |
|
exists(cac:PaymentMeans[cbc:PaymentMeansCode = '42']/cac:PayeeFinancialAccount/cbc:ID) and string-length(normalize-space(cac:PaymentMeans[cbc:PaymentMeansCode = '42']/cac:PayeeFinancialAccount/cbc:ID)) = 12 or not(exists(cac:PaymentMeans[cbc:PaymentMeansCode = '42'])) |
|
IS-R-008 (fatal) |
[IS-R-008]-If seller is icelandic and invoice contains supporting description EINDAGI then the id form must be YYYY-MM-DD — Ef seljandi er íslenskur þá skal eindagi (BT-122, DocumentDescription = EINDAGI) vera á forminu YYYY-MM-DD. |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS'] | ubl-invoice:Invoice[$SupplierCountry = 'IS'] |
|
(exists(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI']) and string-length(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI']/cbc:ID) = 10 and (string(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI']/cbc:ID) castable as xs:date)) or not(exists(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI'])) |
|
IS-R-009 (fatal) |
[IS-R-009]-If seller is icelandic and invoice contains supporting description EINDAGI invoice must have due date — Ef seljandi er íslenskur þá skal reikningur sem inniheldur eindaga (BT-122, DocumentDescription = EINDAGI) einnig hafa gjalddaga (BT-9). |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS'] | ubl-invoice:Invoice[$SupplierCountry = 'IS'] |
|
(exists(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI']) and exists(cbc:DueDate)) or not(exists(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI'])) |
|
IS-R-010 (fatal) |
[IS-R-010]-If seller is icelandic and invoice contains supporting description EINDAGI the id date must be same or later than due date — Ef seljandi er íslenskur þá skal eindagi (BT-122, DocumentDescription = EINDAGI) skal vera sami eða síðar en gjalddagi (BT-9) ef eindagi er til staðar. |
ubl-creditnote:CreditNote[$SupplierCountry = 'IS'] | ubl-invoice:Invoice[$SupplierCountry = 'IS'] |
|
(exists(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI']) and (cbc:DueDate) ⇐ (cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI']/cbc:ID)) or not(exists(cac:AdditionalDocumentReference[cbc:DocumentDescription = 'EINDAGI'])) |
|
IT-R-001 (fatal) |
[IT-R-001] BT-32 (Seller tax registration identifier) - For Italian suppliers BT-32 minimum length 11 and maximum length shall be 16. Per i fornitori italiani il BT-32 deve avere una lunghezza tra 11 e 16 caratteri |
cac:AccountingSupplierParty/cac:Party[$supplierCountry = 'IT']/cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) != 'VAT'] |
|
matches(normalize-space(cbc:CompanyID),'^[A-Z0-9]{11,16}$') |
|
IT-R-002 (fatal) |
[IT-R-002] BT-35 (Seller address line 1) - Italian suppliers MUST provide the postal address line 1 - I fornitori italiani devono indicare l’indirizzo postale. |
cac:AccountingSupplierParty/cac:Party[$supplierCountry = 'IT'] |
|
cac:PostalAddress/cbc:StreetName |
|
IT-R-003 (fatal) |
[IT-R-003] BT-37 (Seller city) - Italian suppliers MUST provide the postal address city - I fornitori italiani devono indicare la città di residenza. |
cac:AccountingSupplierParty/cac:Party[$supplierCountry = 'IT'] |
|
cac:PostalAddress/cbc:CityName |
|
IT-R-004 (fatal) |
"> [IT-R-004] BT-38 (Seller post code) - Italian suppliers MUST provide the postal address post code - I fornitori italiani devono indicare il CAP di residenza. |
cac:AccountingSupplierParty/cac:Party[$supplierCountry = 'IT'] |
|
cac:PostalAddress/cbc:PostalZone |
|
NO-R-001 (fatal) |
For Norwegian suppliers, a VAT number MUST be the country code prefix NO followed by a valid Norwegian organization number (nine numbers) followed by the letters MVA. |
cac:AccountingSupplierParty/cac:Party[$supplierCountry = 'NO'] |
|
cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/substring(cbc:CompanyID, 1, 2)='NO' and matches(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/substring(cbc:CompanyID,3), '^[0-9]{9}MVA$') and u:mod11(substring(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/cbc:CompanyID, 3, 9)) or not(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'VAT']/substring(cbc:CompanyID, 1, 2)='NO') |
|
NO-R-002 (warning) |
For Norwegian suppliers, most invoice issuers are required to append "Foretaksregisteret" to their invoice. "Dersom selger er aksjeselskap, allmennaksjeselskap eller filial av utenlandsk selskap skal også ordet «Foretaksregisteret» fremgå av salgsdokumentet, jf. foretaksregisterloven § 10-2." |
cac:AccountingSupplierParty/cac:Party[$supplierCountry = 'NO'] |
|
normalize-space(cac:PartyTaxScheme[normalize-space(cac:TaxScheme/cbc:ID) = 'TAX']/cbc:CompanyID) = 'Foretaksregisteret' |
|
SE-R-001 (fatal) |
For Swedish suppliers, Swedish VAT-numbers must consist of 14 characters. |
//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE' and cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2) = 'SE'] |
|
string-length(normalize-space(cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/cbc:CompanyID)) = 14 |
|
SE-R-002 (fatal) |
For Swedish suppliers, the Swedish VAT-numbers must have the trailing 12 characters in numeric form |
//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE' and cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2) = 'SE'] |
|
string(number(substring(cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/cbc:CompanyID, 3, 12))) != 'NaN' |
|
SE-R-003 (warning) |
Swedish organisation numbers should be numeric. |
//cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity[../cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE' and cbc:CompanyID] |
|
string(number(cbc:CompanyID)) != 'NaN' |
|
SE-R-004 (warning) |
Swedish organisation numbers consist of 10 characters. |
//cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity[../cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE' and cbc:CompanyID] |
|
string-length(normalize-space(cbc:CompanyID)) = 10 |
|
SE-R-005 (fatal) |
For Swedish suppliers, when using Seller tax registration identifier, 'Godkänd för F-skatt' must be stated |
//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE' and exists(cac:PartyLegalEntity/cbc:CompanyID)]/cac:PartyTaxScheme[normalize-space(upper-case(cac:TaxScheme/cbc:ID)) != 'VAT']/cbc:CompanyID |
|
normalize-space(upper-case(.)) = 'GODKÄND FÖR F-SKATT' |
|
SE-R-006 (fatal) |
For Swedish suppliers, only standard VAT rate of 6, 12 or 25 are used |
//cac:TaxCategory[//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE' and cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2) = 'SE'] and cbc:ID = 'S'] | //cac:ClassifiedTaxCategory[//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE' and cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2) = 'SE'] and cbc:ID = 'S'] |
|
number(cbc:Percent) = 25 or number(cbc:Percent) = 12 or number(cbc:Percent) = 6 |
|
SE-R-007 (warning) |
For Swedish suppliers using Plusgiro, the Account ID must be numeric |
//cac:PaymentMeans[//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE'] and normalize-space(cbc:PaymentMeansCode) = '30' and normalize-space(cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cbc:ID) = 'SE:PLUSGIRO']/cac:PayeeFinancialAccount/cbc:ID |
|
string(number(normalize-space(.))) != 'NaN' |
|
SE-R-008 (warning) |
For Swedish suppliers using Bankgiro, the Account ID must be numeric |
//cac:PaymentMeans[//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE'] and normalize-space(cbc:PaymentMeansCode) = '30' and normalize-space(cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cbc:ID) = 'SE:BANKGIRO']/cac:PayeeFinancialAccount/cbc:ID |
|
string(number(normalize-space(.))) != 'NaN' |
|
SE-R-009 (warning) |
For Swedish suppliers using Bankgiro, the Account ID must have 7-8 characters |
//cac:PaymentMeans[//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE'] and normalize-space(cbc:PaymentMeansCode) = '30' and normalize-space(cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cbc:ID) = 'SE:BANKGIRO']/cac:PayeeFinancialAccount/cbc:ID |
|
string-length(normalize-space(.)) = 7 or string-length(normalize-space(.)) = 8 |
|
SE-R-010 (warning) |
For Swedish suppliers using Plusgiro, the Account ID must have 2-8 characters |
//cac:PaymentMeans[//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE'] and normalize-space(cbc:PaymentMeansCode) = '30' and normalize-space(cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cbc:ID) = 'SE:PLUSGIRO']/cac:PayeeFinancialAccount/cbc:ID |
|
string-length(normalize-space(.)) >= 2 and string-length(normalize-space(.)) ⇐ 8 |
|
SE-R-011 (warning) |
For Swedish suppliers using Swedish Bankgiro or Plusgiro, the proper way to indicate this is to use Code 30 for PaymentMeans and FinancialInstitutionBranch ID with code SE:BANKGIRO or SE:PLUSGIRO |
//cac:PaymentMeans[//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE'] and (cbc:PaymentMeansCode = normalize-space('50') or cbc:PaymentMeansCode = normalize-space('56'))] |
|
false() |
|
SE-R-012 (warning) |
For domestic transactions between Swedish trading partners, credit transfer should be indicated by PaymentMeansCode="30" |
//cac:PaymentMeans[//cac:AccountingSupplierParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE'] and //cac:AccountingCustomerParty/cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'SE'] and (cbc:PaymentMeansCode = normalize-space('31'))] |
|
false() |
C.1. CIUS
| CIUS ID | Tipologia di regola | Terminologia di business | Elemento in XML PA | Descrizione regola |
|---|---|---|---|---|
BR-IT-001* |
Value domain for an element - Require defined structured values |
BT-24 Specification Identifier |
Se il valore dell’elemento BT-40 (Seller country
code) è diverso da "IT", il BT-24 deve essere
valorizzato come segue: (rimuovere gli spazi prima dell’utilizzo) |
|
BR-IT-010 |
Value domain for an element - Restrict text or byte array length |
BT-1 Invoice number |
2.1.1.4 Numero |
La lunghezza dell’elemento non può superare i 20 caratteri e deve includere almeno una cifra |
BR-IT-020 |
Value domain for an element - Restrict text or byte array length |
BT-11 Project reference |
2.1.3.6 CodiceCUP |
La lunghezza dell’elemento non può superare i 15 caratteri |
BR-IT-030 |
Value domain for an element - Restrict text or byte array length |
BT-12 Contract reference |
2.1.3.2 IdDocumento |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-040 |
Value domain for an element - Restrict text or byte array length |
BT-13 Purchase order reference |
2.1.2.2. IdDocumento |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-050 |
Value domain for an element - Restrict text or byte array length |
BT-15 Receiving advice reference |
2.1.5.2 IdDocumento |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-060 |
Value domain for an element - Restrict text or byte array length |
BT-16 Despatch advice reference |
2.1.8.1 NumeroDDT |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-070 |
Value domain for an element - Restrict text or byte array length |
BT-17 Tender or lot reference |
2.1.3.7 CodiceCIG |
La lunghezza dell’elemento non può superare i 15 caratteri |
BR-IT-080 |
Value domain for an element - Restrict text or byte array length |
BT-19 Buyer accounting reference |
1.2.6 RiferimentoAmministrazione |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-090 |
Value domain for an element - Restrict text or byte array length |
BT-25 Preceding Invoice number |
2.1.6.2 IdDocumento |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-120 |
Value domain for an element - Restrict text or byte array length |
BT-31 Seller VAT identifier |
1.2.1.1.1 IdPaese |
La lunghezza dell’elemento non può superare i 30 caratteri |
BR-IT-180 |
Value domain for an element - Restrict text or byte array length |
BT-48 Buyer VAT identifier |
1.4.1.1.1 IdPaese |
La lunghezza dell’elemento non può superare i 30 caratteri |
BR-IT-190A* |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BT-49 Buyer electroni caddress |
1.1.6 PECDestinatario |
Se Buyer country code (BT-55) = “IT”, allora l’elemento BT-49 (Buyer electronic address) deve contenere il Codice IPA, la PEC del destinatario della fattura oppure il Codice Destinatario. Di conseguenza, per l’elemento BT-49-1 (Buyer electronic address identification scheme identifier) sono previsti rispettivamente i valori 0201, 0202 oppure 0205 |
BR-IT-200 |
Value domain for an element - Restrict text or byte array length |
BT-49 Buyer electronic address |
1.1.4 CodiceDestinatario |
Se l’elemento BT-49-1 (Buyer electronic address identification scheme identifier) contiene il valore "0201", l’elemento BT-49 (Buyer electronic address) deve contenere un codice IPA con lunghezza pari a 6 caratteri |
BR-IT-210 |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BT-50 Buyer address line 1 |
1.4.2.1 Indirizzo |
Se Buyer country code (BT-55) = “IT”, tutti gli elementi sono obbligatori a meno del Numero Civico |
BR-IT-220 |
Value domain for an element - Require defined structured values |
BT-54 Buyer country subdivision |
1.4.2.5 Provincia |
Se Buyer country code (BT-55) = “IT”, per l’elemento BT-54 Buyer country subdivision deve essere utilizzato uno dei valori della lista delle province italiane. Altrimenti l’informazione è riportata in allegato |
BR-IT-230 |
Value domain for an element - Restrict text or byte array length |
BT-63 Seller tax representa tive VAT identifier |
1.3.1.1.1 IdPaese |
La lunghezza dell’elemento non può superare i 30 caratteri |
BR-IT-240 |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BT-75 Deliver to address line 1 |
2.1.9.12.1 Indirizzo |
Se il valore dell’elemento BT-80 Deliver to country code è ”IT”, gli elementi devono essere obbligatoriamente valorizzati |
BR-IT-250 |
Value domain for an element - Require defined structured values |
BT-79 Deliver to country subdivision |
2.1.9.12.5 Provincia |
Se l’elemento BT-80 Deliver to country code ha valore "IT", per l’elemento BT-79 Deliver to country subdivision deve essere utilizzato uno dei valori della lista delle province italiane. Altrimenti l’informazione deve essere riportata in allegato |
BR-IT-260 |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BG-16 Payment instructions |
2.4 DatIPagamento |
Il gruppo di elementi BG-16 Payment instructions deve essere obbligatorio |
BR-IT-261* |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BT-20 Payment terms |
2.4.1 CondizioniPagamento |
L’elemento BT-20 Payment Terms deve essere obbligatoriamente valorizzato |
BR-IT-270 |
Business Terms - Make semantic definition narrower |
BT-84 Payment account identifier |
2.4.2.13 IBAN |
L’identificativo del pagamento BT-84 Payment account identifier deve essere un codice IBAN |
BR-IT-280 |
Value domain for an element - Require defined structured values |
BT-86 Payment service provider identifier |
2.4.2.16 BIC |
La lunghezza dell’elemento deve essere compresa fra 8 e 11 caratteri (BIC) |
BR-IT-290 |
Value domain for an element - Require defined structured values |
BT-92 Document level allowance amount |
2.2.1.9 PrezzoUnitario |
La lunghezza dell’elemento non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-300 |
Value domain for an element - Require defined structured values |
BT-112 Invoice total amount with VAT |
2.1.1.9 ImportoTotaleDocumento |
La lunghezza dell’elemento non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-310 |
Value domain for an element - Require defined structured values |
BT-114 Rounding amount |
2.1.1.10 Arrotondamento |
La lunghezza dell’elemento non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-320 |
Value domain for an element - Require defined structured values |
BT-115 Amount due for payment |
2.4.2.6 ImportoPagamento |
La lunghezza dell’elemento non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-330 |
Value domain for an element - Require defined structured values |
BT-116 VAT category taxable amount |
2.2.2.5 ImponibileImporto |
La lunghezza dell’elemento non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-340 |
Value domain for an element - Require defined structured values |
BT-117 VAT category tax amount |
2.2.2.6 Imposta |
La lunghezza dell’elemento non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-350 |
Codes and identifiers - Mark defined values as not allowed |
BT-118 VAT category code |
I valori accettati sono esclusivamente AE E S G K Z B |
|
BR-IT-360 |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BT-124 External document location |
2.5.5 Attachment |
Se l’elemento l’elemento BT-122 Supporting document reference è valorizzato, è obbligatorio valorizzare almeno uno degli elementi BT-124 External document location e BT- 125 Attached document |
BR-IT-370 |
Value domain for an element - Restrict text or byte array length |
BT-128 Invoice line object identifier |
2.2.1.3.2 CodiceValore |
La lunghezza dell’elemento non può superare i 35 caratteri |
BR-IT-380 |
Value domain for an element - Require defined structured values |
BT-129 Invoiced quantity |
2.2.1.5 Quantita |
La lunghezza dell’elemento non deve essere superiore a 21 caratteri e l’elemento dovrà avere 8 cifre decimali |
BR-IT-390 |
Value domain for an element - Require defined structured values |
BT-131 Invoice line net amount |
2.2.1.11 PrezzoTotale |
La lunghezza dell’elemento non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-400 |
Value domain for an element - Restrict text or byte array length |
BT-132 Reference d purchase order line reference |
2.1.2.4 NumItem |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-410 |
Value domain for an element - Restrict text or byte array length |
BT-133 Invoice line Buyer accounting reference |
2.2.1.15 RiferimentoAmministrazione |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-431* |
Value domain for an element - Restrict text or byte array length |
BT-147 Item price discount |
2.2.1.10.3 Importo |
La lunghezza dell’elemento non deve essere superiore a 21 caratteri e l’elemento potrà avere fino a 8 cifre decimali. |
BR-IT-432* |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BT-148 Item gross price |
2.2.1.9 PrezzoUnitario |
Il BT-148 Item gross price deve essere obbligatoriamente valorizzato |
BR-IT-433* |
Value domain for an element - Restrict text or byte array length |
BT-148 Item gross price |
2.2.1.9 PrezzoUnitario |
La lunghezza dell’elemento non deve essere superiore a 21 caratteri e l’elemento potrà avere fino a 8 cifre decimali |
BR-IT-440 |
Value domain for an element - Restrict text or byte array length |
BT-155 Item Seller’s identifier |
2.2.1.3.1 Codice Tipo |
La lunghezza dell’elemento non può superare i 35 caratteri |
BR-IT-470 |
Value domain for an element - Restrict text or byte array length |
BT-158 Item classificati on identifier |
2.2.1.3.1 Codice Tipo |
La lunghezza dell’elemento non può superare i 35 caratteri |
BR-IT-520A* |
Add new non-conflicting business rule to existing element(s) |
BT-47 Buyer legal registration identifier |
1.4.1.2 CodiceFiscale |
Se Buyer country code (BT-55) = “IT”, almeno uno degli elementi BT-48 (Buyer VAT identifier) o BT-47 (Buyer legal registration identifier) deve essere valorizzato. |
BR-IT-520B* |
Value domain for an element - Restrict text or byte array length |
BT-47 Buyer legal registration identifier |
1.4.1.2 CodiceFiscale |
Se Buyer country code (BT-55)="IT", la lunghezza dell’elemento è compresa fra 11 e 16 caratteri. |
BR-IT-520C* |
Cardinality - Make a conditional element mandatory (0..x — > 1..x) |
BT-47-1 Buyer legal registration identifier scheme identifier |
1.4.1.2 CodiceFiscale |
Se Buyer country code (BT-55) = “IT” ed esiste l’elemento Buyer legal registration identifier (BT-47), allora l’elemento Buyer legal registration identifier scheme identifier (BT-47-1) è obbligatorio e contiene il valore "0210". |
BR-IT-521 |
Value domain for an element - Restrict text or byte array length |
BT-46 Buyer identifier |
1.4.1.3.5 Codice EORI |
Se Buyer country code (BT-55) = “IT”, il Codice EORI (BT-46 Buyer identifier) deve essere preceduto dal prefisso 'EORI:' ed avere la lunghezza del codice compresa fra 13 e 17 caratteri alfanumerici. |
(*) regola della Peppol Authority nazionale che integra le specifiche tecniche AdE
C.2. CIUS Domestiche
| CIUS ID | Tipologia di regola | Terminologia di business | Elemento in XML PA | Descrizione regola |
|---|---|---|---|---|
BR-IT-DC-002* |
Value domain for an element - Require defined structured values |
BT-24 Specification Identifier |
Se il valore dell’elemento BT-40 (Seller country code) è uguale a "IT", il BT-24 deve essere valorizzato come segue: urn:cen.eu:en16931:2017# compliant#urn:fdc:peppol.eu :2017:poacc:billing:3.0#conformant #urn:www.agid.gov.it:trns :fattura:3 (rimuovere gli spazi prima dell’utilizzo) |
|
BR-IT-DC-100A* |
Value domain for an element - Restrict text or byte array length |
BT-29 Seller identifier |
1.2.1.3.5 CodEORI |
Se il valore dell’elemento BT-40 (Seller country code) è "IT", se il valore dell’elemento BT29 Seller identifier comincia con "EORI:", la sua lunghezza deve essere compresa fra 18 e 22 caratteri. |
BR-IT-DC-100B* |
Value domain for an element - Restrict text or byte array length |
BT-29 Seller identifier |
1.2.1.4 AlboProfessionale |
Se il valore dell’elemento BT-40 (Seller country code) è "IT", se il valore dell’elemento BT29 Seller identifier comincia con "ALBO:", la sua lunghezza non può superare i 137 caratteri e può essere indicato come "ALBO:AlboProfessionale |
BR-IT-DC-100C |
Value domain for an element - Restrict text or byte array length |
BT-29 Seller identifier |
1.2.4.1 Ufficio |
Se il valore dell’elemento BT-40 (Seller country code) è "IT", se il valore dell’elemento BT-29 Seller identifier comincia con "REA:", la sua lunghezza deve essere compresa fra 8 e 27 caratteri e deve essere indicato come "REA:Ufficio#NumeroREA". |
BR-IT-DC-110A* |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BT-30 Seller legal registration identifier |
1.2.1.2 CodiceFiscale |
Se il valore dell’elemento BT-40 Seller country code è “IT”, gli elementi devono essere obbligatoriamente valorizzati. |
BR-IT-DC-110B* |
Value domain for an element - Restrict text or byte array length |
BT-30 Seller legal registration identifier |
1.2.1.2 CodiceFiscale |
Se il valore dell’elemento BT-40 (Seller country code) è "IT", se l’elemento BT-30-1 (Seller legal registration identifier scheme identifier) contiene il valore "0210", l’elemento BT-30 (Seller legal registration identifier) deve contenere un Codice Fiscale con lunghezza compresa fra 11 e 16 caratteri. |
BR-IT-DC-122* |
Value domain for an element - Restrict text or byte array length |
BT-33 Seller Additional Legal Information |
1.2.4.3 CapitaleSociale |
La lunghezza dell’elemento non può superare i 21 caratteri. |
BR-IT-DC-140 |
Cardinality - Make a conditional element mandatory (0..x -→ 1..x) |
BT-35 Seller address line 1 |
1.2.2.1 Indirizzo |
Se il valore dell’elemento BT-40 Seller country code è “IT”, gli elementi devono essere obbligatoriamente valorizzati. |
BR-IT-DC-150 |
Value domain for an element - Require defined structured values |
BT-39 Seller country subdivision |
1.2.2.5 Provincia |
Se l’elemento BT-40 Seller country code ha valore "IT", per l’elemento BT-39 Seller country subdivision deve essere utilizzato uno dei valori della lista delle province italiane. Altrimenti l’informazione è riportata in allegato |
BR-IT-DC-480 |
BT-118 VAT category code |
Se l’elemento BT-40 Seller country code ha valore "IT e la fattura è soggetta alla marca da bollo, il motivo della maggiorazione deve essere posto a "BOLLO" e l’importo deve essere superiore a 77.47 EURO. Se l’importo del bollo viene rifatturato al cliente, il suo valore deve essere posto a 2.00 EUR come operazione non imponibile IVA (TaxCategory/ID = 'Z') e il relativo riepilogo IVA deve riportare un imponibile di 2.00 EUR". |
(*) national Peppol authority rule that integrates the AdE technical specifications
C.3. CIUS Domestiche (fatturazione verso privati)
| CIUS ID | Tipologia di regola | Terminologia di business | Elemento in XML PA | Descrizione regola |
|---|---|---|---|---|
BR-IT-DC-202 |
Value domain for an element - Restrict text or byte array length |
BT-49 Buyer electroni caddress |
1.1.4 CodiceDestinatario |
Se l’elemento BT-49-1 (Buyer electronic address identification scheme identifier) contiene il valore "0205", l’elemento BT-49 deve contenere un Codice Destinatario con lunghezza pari a 7 caratteri |
BR-IT-DC-203 |
Value domain for an element - Restrict text or byte array length |
BT-49 Buyer electroni caddress |
1.1.6 PECDestinatario |
Se l’elemento BT-49-1 (Buyer electronic address identification scheme identifier) contiene il valore "0202", l’elemento BT-49 deve contenere un indirizzo PEC di lunghezza compresa fra 7 e 256 caratteri |
C.4. Estensioni Domestiche
| CIUS ID | Elemento in XML PA | Descrizione regola |
|---|---|---|
BR-IT-DE-001 |
1.6 Soggetto Emittente |
L’estensione deve contenere un elemento cbc:TypeCode valorizzato esclusivamente con i valori 'CC' o 'TZ'. |
BR-IT-DE-002 |
2.1.1.1 Tipo Documento |
L’estensione deve contenere un elemento cbc:TypeCode valorizzato esclusivamente con i valori del TipoDocumento, secondo la specifica FatturaPA 1.2.1. |
BR-IT-DE-003 |
2.1.1.5.1 Tipo Ritenuta |
L’estensione deve contenere un elemento cbcTypeCode valorizzato esclusivamente con i valori del TipoRitenuta, secondo la specifica FatturaPA 1.2.1 |
BR-IT-DE-004 |
2.1.1.12 Art73 |
L’estensione deve contenere un elemento cbcTypeCode valorizzato esclusivamente con il valore 'SI' per applicare l’Articolo 73 del DPR 633/72. |
BR-IT-DE-005 |
2.2.2.4 Arrotondamento |
L’estensione deve contenere un elemento cbcAmount la cui lunghezza non può superare i 15 caratteri incluso 2 cifre decimali. |
BR-IT-DE-006 |
2.1.1.8 Sconto Maggiorazione |
L’estensione deve contenere uno o più elementi cacAllowanceCharge. |
BR-IT-DE-007 |
2.1.1.8 Sconto Maggiorazione |
L’importo dello sconto o maggiorazione (cbcAmount) deve contenere da 4 fino a 21 caratteri incluso 2 cifre decimali |
BR-IT-DE-008 |
2.1.1.8 Sconto Maggiorazione |
L’importo dello sconto/maggiorazione in percentuale, se presente, (cbcMultiplierFactorNumeric) deve contenere da 4 fino a 6 caratteri incluso 2 cifre decimali |
BR-IT-DE-009NC1* |
2.1.1.5 Dati Ritenuta |
L’estensione deve contenere un elemento cac:WithholdingTaxTotal. |
BR-IT-DE-009FT1* |
2.1.1.5 Dati Ritenuta |
L’estensione deve contenere un elemento cac:WithholdingTaxTotal. |
BR-IT-DE-010 |
2.1.1.5 Dati Ritenuta |
L’importo totale delle ritenute (cbcTaxAmount) deve contenere da 4 fino a 15 caratteri incluso 2 cifre decimali. |
BR-IT-DE-011 |
2.1.1.5 Dati Ritenuta |
Il cac:WithholdingTaxTotal deve contenere almeno una ritenuta (cac:TaxSubtotal) |
BR-IT-DE-012 |
2.1.1.5 Dati Ritenuta |
L’importo di ogni ritenuta (cbcTaxAmount) deve contenere da 4 fino a 15 caratteri incluso 2 cifre decimali. |
BR-IT-DE-013 |
2.1.1.5 Dati Ritenuta |
Ogni ritenuta deve contenere la categoria della ritenuta (cacTaxCategory) con identificativo uguale a "S" (cbcID), percentuale della ritenuta (cbcPercent) da 4 fino a 6 caratteri incluso 2 cifre decimali e schema della ritenuta valorizzato con cacTaxScheme/cbcID = 'SWT' |
BR-IT-DE-014 |
2.1.10.1 NumeroFatturaPrincipale |
Se si vuole fare riferimento ad una fattura principale relativa al trasporto di beni devono essere obbligatoriamente valorizzati gli estremi della fattura con gli elementi ID e IssueDate. |
BR-IT-DE-015 |
2.1.10.1 NumeroFatturaPrincipale |
L’identificativo della fattura principale non può superare i 20 caratteri |
BR-IT-DE-016 |
2.1.8.2 DataDDT |
La data del documento di trasporto deve essere obbligatoriamente valorizzata a livello di documento |
BR-IT-DE-017 |
1.2.1.8 Regime Fiscale |
Il Regime Fiscale (cbcTaxLevelCode) deve essere valorizzato esclusivamente con i valori della relativa codifica. |
BR-IT-DE-018 |
1.2.3 Stabile Organizzazione |
La Stabile Organizzazione deve fornire l’indirizzo completo di via e numero civico, comune, CAP, provincia e nazione |
BR-IT-DE-019 |
1.2.3.1 Indirizzo |
La lunghezza dell’elemento non può superare i 60 caratteri. |
BR-IT-DE-020 |
1.2.3.4 Comune |
La lunghezza dell’elemento non può superare i 60 caratteri. |
BR-IT-DE-021 |
1.2.3.3 CAP |
La lunghezza dell’elemento deve essere costituita da 5 cifre |
BR-IT-DE-022 |
1.2.3.5 Provincia |
La lunghezza dell’elemento non può superare 2 caratteri. |
BR-IT-DE-023 |
1.5 Terzo Intermediario |
Il Terzo Intermediario o Soggetto Emittente deve contenere la P.IVA, lo schema fiscale = 'VAT', la ragione sociale o una persona fisica (nome e cognome). |
BR-IT-DE-024A* |
1.3.1.2 Codice Fiscale |
Il Codice Fiscale deve specificare l’attributo @schemeID valorizzato con "0210" ed avere la lunghezza del codice compresa fra 11 e 16 caratteri alfanumerici. |
BR-IT-DE-025 |
1.3.1.3.5 Codice EORI |
Il Codice EORI deve essere preceduto dal prefisso 'EORI:' ed avere la lunghezza del codice compresa fra 13 e 17 caratteri alfanumerici. |
BR-IT-DE-026A* |
2.1.9.1.2 Codice Fiscale |
Il Codice Fiscale deve specificare l’attributo @schemeID valorizzato con "0210" ed avere la lunghezza del codice compresa fra 11 e 16 caratteri alfanumerici. |
BR-IT-DE-027 |
2.1.9.1.3.1 Denominazione |
Se la Denominazione del Vettore è valorizzata, la sua lunghezza non può superare 80 caratteri, alternativamente, se è invece valorizzato il Nome e il Cognome, la loro lunghezza non potrà superare 60 caratteri |
BR-IT-DE-028 |
2.1.9.1.1 Partita IVA |
La lunghezza dell’elemento non può superare i 30 caratteri |
BR-IT-DE-029 |
L’identificativo del TaxScheme deve essere valorizzato con 'VAT' |
|
BR-IT-DE-030 |
2.1.9.1.4 Numero Licenza Guida |
Se il Numero Licenza Guida è valorizzata, la sua lunghezza non può superare 20 caratteri e il tipo documento (cbcDocumentTypeCode) deve essere '40' |
BR-IT-DE-031 |
2.1.9.7 Peso Lordo |
La lunghezza del Peso Lordo o Netto deve essere da 4 a 7 caratteri, incluse 1 o 2 cifre decimali. |
BR-IT-DE-032 |
2.1.9.4 Numero Colli |
Il Numero di Colli può essere da 1 a 9999. |
BR-IT-DE-033 |
2.1.9.5 Descrizione Merce |
La lunghezza dell’elemento non può superare i 100 caratteri. |
BR-IT-DE-034 |
2.1.9.2 Mezzo di Trasporto |
La lunghezza dell’elemento non può superare gli 80 caratteri |
BR-IT-DE-035 |
2.1.9.3 Causale Trasporto |
La lunghezza dell’elemento non può superare i 100 caratteri. |
BR-IT-DE-036 |
2.1.9.11 Tipo Resa Merce |
La lunghezza dell’elemento deve essere di 3 caratteri. |
BR-IT-DE-037 |
2.4.2.17 Sconto Pagamento Anticipato |
La lunghezza dell’elemento deve essere di almeno 4 caratteri e non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-DE-038 |
2.4.2.19 Penalita Pagamenti Ritardati |
La lunghezza dell’elemento deve essere di almeno 4 caratteri e non può superare i 15 caratteri incluso 2 cifre decimali |
BR-IT-DE-039 |
2.1.2.2 Numero Ordine |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-DE-040 |
Il riferimento ad una riga DDT dalla riga fattura non supportato da SDI, valorizzarlo sempre con 'NA'. |
|
BR-IT-DE-041 |
2.1.8.1 Numero DDT |
La lunghezza dell’elemento non può superare i 20 caratteri |
BR-IT-DE-042 |
2.1.8.2 DataDDT |
La data del documento di trasporto deve essere obbligatoriamente valorizzata a livello di riga |
(*) national Peppol authority rule that integrates the AdE technical specifications
C.5. Estensioni Domestiche (fatturazione verso privati)
| CIUS ID | Elemento in XML PA | Descrizione regola |
|---|---|---|
BR-IT-DE-043 |
1.4.3 Stabile Organizzazione |
La Stabile Organizzazione deve fornire l’indirizzo completo di via e numero civico, comune, cap, provincia e nazione. |
BR-IT-DE-044 |
1.4.3.1 Indirizzo |
La lunghezza dell’elemento non può superare i 60 caratteri. |
BR-IT-DE-045 |
1.4.3.4 Comune |
La lunghezza dell’elemento non può superare i 60 caratteri. |
BR-IT-DE-046 |
1.4.3.3 CAP |
La lunghezza dell’elemento non può superare 8 caratteri. |
BR-IT-DE-047 |
1.4.3.5 Provincia |
La lunghezza dell’elemento non può superare 2 caratteri. |
BR-IT-DE-048 |
1.4.4 Rappresentante Fiscale |
Il Rappresentante Fiscale del Cliente deve contenere la P.IVA, lo schema fiscale = 'VAT', la ragione sociale e se viene specificata una persona fisica, il nome e cognome. |
Appendix D: Syntax rules
The following EN 16931 syntax rules apply to invoice and credit note transaction as it is used in this PEPPOL BIS.
| Rule | Message |
|---|---|
UBL-CR-001 (warning) |
[UBL-CR-001]-A UBL invoice should not include extensions |
UBL-CR-002 (warning) |
[UBL-CR-002]-A UBL invoice should not include the UBLVersionID |
UBL-CR-003 (warning) |
[UBL-CR-003]-A UBL invoice should not include the ProfileExecutionID |
UBL-CR-004 (warning) |
[UBL-CR-004]-A UBL invoice should not include the CopyIndicator |
UBL-CR-005 (warning) |
[UBL-CR-005]-A UBL invoice should not include the UUID |
UBL-CR-006 (warning) |
[UBL-CR-006]-A UBL invoice should not include the IssueTime |
UBL-CR-007 (warning) |
[UBL-CR-007]-A UBL invoice should not include the PricingCurrencyCode |
UBL-CR-008 (warning) |
[UBL-CR-008]-A UBL invoice should not include the PaymentCurrencyCode |
UBL-CR-009 (warning) |
[UBL-CR-009]-A UBL invoice should not include the PaymentAlternativeCurrencyCode |
UBL-CR-010 (warning) |
[UBL-CR-010]-A UBL invoice should not include the AccountingCostCode |
UBL-CR-011 (warning) |
[UBL-CR-011]-A UBL invoice should not include the LineCountNumeric |
UBL-CR-012 (warning) |
[UBL-CR-012]-A UBL invoice should not include the InvoicePeriod StartTime |
UBL-CR-013 (warning) |
[UBL-CR-013]-A UBL invoice should not include the InvoicePeriod EndTime |
UBL-CR-014 (warning) |
[UBL-CR-014]-A UBL invoice should not include the InvoicePeriod DurationMeasure |
UBL-CR-015 (warning) |
[UBL-CR-015]-A UBL invoice should not include the InvoicePeriod Description |
UBL-CR-016 (warning) |
[UBL-CR-016]-A UBL invoice should not include the OrderReference CopyIndicator |
UBL-CR-017 (warning) |
[UBL-CR-017]-A UBL invoice should not include the OrderReference UUID |
UBL-CR-018 (warning) |
[UBL-CR-018]-A UBL invoice should not include the OrderReference IssueDate |
UBL-CR-019 (warning) |
[UBL-CR-019]-A UBL invoice should not include the OrderReference IssueTime |
UBL-CR-020 (warning) |
[UBL-CR-020]-A UBL invoice should not include the OrderReference CustomerReference |
UBL-CR-021 (warning) |
[UBL-CR-021]-A UBL invoice should not include the OrderReference OrderTypeCode |
UBL-CR-022 (warning) |
[UBL-CR-022]-A UBL invoice should not include the OrderReference DocumentReference |
UBL-CR-023 (warning) |
[UBL-CR-023]-A UBL invoice should not include the BillingReference CopyIndicator |
UBL-CR-024 (warning) |
[UBL-CR-024]-A UBL invoice should not include the BillingReference UUID |
UBL-CR-025 (warning) |
[UBL-CR-025]-A UBL invoice should not include the BillingReference IssueTime |
UBL-CR-026 (warning) |
[UBL-CR-026]-A UBL invoice should not include the BillingReference DocumentTypeCode |
UBL-CR-027 (warning) |
[UBL-CR-027]-A UBL invoice should not include the BillingReference DocumentType |
UBL-CR-028 (warning) |
[UBL-CR-028]-A UBL invoice should not include the BillingReference Xpath |
UBL-CR-029 (warning) |
[UBL-CR-029]-A UBL invoice should not include the BillingReference LanguageID |
UBL-CR-030 (warning) |
[UBL-CR-030]-A UBL invoice should not include the BillingReference LocaleCode |
UBL-CR-031 (warning) |
[UBL-CR-031]-A UBL invoice should not include the BillingReference VersionID |
UBL-CR-032 (warning) |
[UBL-CR-032]-A UBL invoice should not include the BillingReference DocumentStatusCode |
UBL-CR-033 (warning) |
[UBL-CR-033]-A UBL invoice should not include the BillingReference DocumenDescription |
UBL-CR-034 (warning) |
[UBL-CR-034]-A UBL invoice should not include the BillingReference Attachment |
UBL-CR-035 (warning) |
[UBL-CR-035]-A UBL invoice should not include the BillingReference ValidityPeriod |
UBL-CR-036 (warning) |
[UBL-CR-036]-A UBL invoice should not include the BillingReference IssuerParty |
UBL-CR-037 (warning) |
[UBL-CR-037]-A UBL invoice should not include the BillingReference ResultOfVerification |
UBL-CR-038 (warning) |
[UBL-CR-038]-A UBL invoice should not include the BillingReference SelfBilledInvoiceDocumentReference |
UBL-CR-039 (warning) |
[UBL-CR-039]-A UBL invoice should not include the BillingReference CreditNoteDocumentReference |
UBL-CR-040 (warning) |
[UBL-CR-040]-A UBL invoice should not include the BillingReference SelfBilledCreditNoteDocumentReference |
UBL-CR-041 (warning) |
[UBL-CR-041]-A UBL invoice should not include the BillingReference DebitNoteDocumentReference |
UBL-CR-042 (warning) |
[UBL-CR-042]-A UBL invoice should not include the BillingReference ReminderDocumentReference |
UBL-CR-043 (warning) |
[UBL-CR-043]-A UBL invoice should not include the BillingReference AdditionalDocumentReference |
UBL-CR-044 (warning) |
[UBL-CR-044]-A UBL invoice should not include the BillingReference BillingReferenceLine |
UBL-CR-045 (warning) |
[UBL-CR-045]-A UBL invoice should not include the DespatchDocumentReference CopyIndicator |
UBL-CR-046 (warning) |
[UBL-CR-046]-A UBL invoice should not include the DespatchDocumentReference UUID |
UBL-CR-047 (warning) |
[UBL-CR-047]-A UBL invoice should not include the DespatchDocumentReference IssueDate |
UBL-CR-048 (warning) |
[UBL-CR-048]-A UBL invoice should not include the DespatchDocumentReference IssueTime |
UBL-CR-049 (warning) |
[UBL-CR-049]-A UBL invoice should not include the DespatchDocumentReference DocumentTypeCode |
UBL-CR-050 (warning) |
[UBL-CR-050]-A UBL invoice should not include the DespatchDocumentReference DocumentType |
UBL-CR-051 (warning) |
[UBL-CR-051]-A UBL invoice should not include the DespatchDocumentReference Xpath |
UBL-CR-052 (warning) |
[UBL-CR-052]-A UBL invoice should not include the DespatchDocumentReference LanguageID |
UBL-CR-053 (warning) |
[UBL-CR-053]-A UBL invoice should not include the DespatchDocumentReference LocaleCode |
UBL-CR-054 (warning) |
[UBL-CR-054]-A UBL invoice should not include the DespatchDocumentReference VersionID |
UBL-CR-055 (warning) |
[UBL-CR-055]-A UBL invoice should not include the DespatchDocumentReference DocumentStatusCode |
UBL-CR-056 (warning) |
[UBL-CR-056]-A UBL invoice should not include the DespatchDocumentReference DocumentDescription |
UBL-CR-057 (warning) |
[UBL-CR-057]-A UBL invoice should not include the DespatchDocumentReference Attachment |
UBL-CR-058 (warning) |
[UBL-CR-058]-A UBL invoice should not include the DespatchDocumentReference ValidityPeriod |
UBL-CR-059 (warning) |
[UBL-CR-059]-A UBL invoice should not include the DespatchDocumentReference IssuerParty |
UBL-CR-060 (warning) |
[UBL-CR-060]-A UBL invoice should not include the DespatchDocumentReference ResultOfVerification |
UBL-CR-061 (warning) |
[UBL-CR-061]-A UBL invoice should not include the ReceiptDocumentReference CopyIndicator |
UBL-CR-062 (warning) |
[UBL-CR-062]-A UBL invoice should not include the ReceiptDocumentReference UUID |
UBL-CR-063 (warning) |
[UBL-CR-063]-A UBL invoice should not include the ReceiptDocumentReference IssueDate |
UBL-CR-064 (warning) |
[UBL-CR-064]-A UBL invoice should not include the ReceiptDocumentReference IssueTime |
UBL-CR-065 (warning) |
[UBL-CR-065]-A UBL invoice should not include the ReceiptDocumentReference DocumentTypeCode |
UBL-CR-066 (warning) |
[UBL-CR-066]-A UBL invoice should not include the ReceiptDocumentReference DocumentType |
UBL-CR-067 (warning) |
[UBL-CR-067]-A UBL invoice should not include the ReceiptDocumentReference Xpath |
UBL-CR-068 (warning) |
[UBL-CR-068]-A UBL invoice should not include the ReceiptDocumentReference LanguageID |
UBL-CR-069 (warning) |
[UBL-CR-069]-A UBL invoice should not include the ReceiptDocumentReference LocaleCode |
UBL-CR-070 (warning) |
[UBL-CR-070]-A UBL invoice should not include the ReceiptDocumentReference VersionID |
UBL-CR-071 (warning) |
[UBL-CR-071]-A UBL invoice should not include the ReceiptDocumentReference DocumentStatusCode |
UBL-CR-072 (warning) |
[UBL-CR-072]-A UBL invoice should not include the ReceiptDocumentReference DocumentDescription |
UBL-CR-073 (warning) |
[UBL-CR-073]-A UBL invoice should not include the ReceiptDocumentReference Attachment |
UBL-CR-074 (warning) |
[UBL-CR-074]-A UBL invoice should not include the ReceiptDocumentReference ValidityPeriod |
UBL-CR-075 (warning) |
[UBL-CR-075]-A UBL invoice should not include the ReceiptDocumentReference IssuerParty |
UBL-CR-076 (warning) |
[UBL-CR-076]-A UBL invoice should not include the ReceiptDocumentReference ResultOfVerification |
UBL-CR-077 (warning) |
[UBL-CR-077]-A UBL invoice should not include the StatementDocumentReference |
UBL-CR-078 (warning) |
[UBL-CR-078]-A UBL invoice should not include the OriginatorDocumentReference CopyIndicator |
UBL-CR-079 (warning) |
[UBL-CR-079]-A UBL invoice should not include the OriginatorDocumentReference UUID |
UBL-CR-080 (warning) |
[UBL-CR-080]-A UBL invoice should not include the OriginatorDocumentReference IssueDate |
UBL-CR-081 (warning) |
[UBL-CR-081]-A UBL invoice should not include the OriginatorDocumentReference IssueTime |
UBL-CR-082 (warning) |
[UBL-CR-082]-A UBL invoice should not include the OriginatorDocumentReference DocumentTypeCode |
UBL-CR-083 (warning) |
[UBL-CR-083]-A UBL invoice should not include the OriginatorDocumentReference DocumentType |
UBL-CR-084 (warning) |
[UBL-CR-084]-A UBL invoice should not include the OriginatorDocumentReference Xpath |
UBL-CR-085 (warning) |
[UBL-CR-085]-A UBL invoice should not include the OriginatorDocumentReference LanguageID |
UBL-CR-086 (warning) |
[UBL-CR-086]-A UBL invoice should not include the OriginatorDocumentReference LocaleCode |
UBL-CR-087 (warning) |
[UBL-CR-087]-A UBL invoice should not include the OriginatorDocumentReference VersionID |
UBL-CR-088 (warning) |
[UBL-CR-088]-A UBL invoice should not include the OriginatorDocumentReference DocumentStatusCode |
UBL-CR-089 (warning) |
[UBL-CR-089]-A UBL invoice should not include the OriginatorDocumentReference DocumentDescription |
UBL-CR-090 (warning) |
[UBL-CR-090]-A UBL invoice should not include the OriginatorDocumentReference Attachment |
UBL-CR-091 (warning) |
[UBL-CR-091]-A UBL invoice should not include the OriginatorDocumentReference ValidityPeriod |
UBL-CR-092 (warning) |
[UBL-CR-092]-A UBL invoice should not include the OriginatorDocumentReference IssuerParty |
UBL-CR-093 (warning) |
[UBL-CR-093]-A UBL invoice should not include the OriginatorDocumentReference ResultOfVerification |
UBL-CR-094 (warning) |
[UBL-CR-094]-A UBL invoice should not include the ContractDocumentReference CopyIndicator |
UBL-CR-095 (warning) |
[UBL-CR-095]-A UBL invoice should not include the ContractDocumentReference UUID |
UBL-CR-096 (warning) |
[UBL-CR-096]-A UBL invoice should not include the ContractDocumentReference IssueDate |
UBL-CR-097 (warning) |
[UBL-CR-097]-A UBL invoice should not include the ContractDocumentReference IssueTime |
UBL-CR-098 (warning) |
[UBL-CR-098]-A UBL invoice should not include the ContractDocumentReference DocumentTypeCode |
UBL-CR-099 (warning) |
[UBL-CR-099]-A UBL invoice should not include the ContractDocumentReference DocumentType |
UBL-CR-100 (warning) |
[UBL-CR-100]-A UBL invoice should not include the ContractDocumentReference Xpath |
UBL-CR-101 (warning) |
[UBL-CR-101]-A UBL invoice should not include the ContractDocumentReference LanguageID |
UBL-CR-102 (warning) |
[UBL-CR-102]-A UBL invoice should not include the ContractDocumentReference LocaleCode |
UBL-CR-103 (warning) |
[UBL-CR-103]-A UBL invoice should not include the ContractDocumentReference VersionID |
UBL-CR-104 (warning) |
[UBL-CR-104]-A UBL invoice should not include the ContractDocumentReference DocumentStatusCode |
UBL-CR-105 (warning) |
[UBL-CR-105]-A UBL invoice should not include the ContractDocumentReference DocumentDescription |
UBL-CR-106 (warning) |
[UBL-CR-106]-A UBL invoice should not include the ContractDocumentReference Attachment |
UBL-CR-107 (warning) |
[UBL-CR-107]-A UBL invoice should not include the ContractDocumentReference ValidityPeriod |
UBL-CR-108 (warning) |
[UBL-CR-108]-A UBL invoice should not include the ContractDocumentReference IssuerParty |
UBL-CR-109 (warning) |
[UBL-CR-109]-A UBL invoice should not include the ContractDocumentReference ResultOfVerification |
UBL-CR-110 (warning) |
[UBL-CR-110]-A UBL invoice should not include the AdditionalDocumentReference CopyIndicator |
UBL-CR-111 (warning) |
[UBL-CR-111]-A UBL invoice should not include the AdditionalDocumentReference UUID |
UBL-CR-112 (warning) |
[UBL-CR-112]-A UBL invoice should not include the AdditionalDocumentReference IssueDate |
UBL-CR-113 (warning) |
[UBL-CR-113]-A UBL invoice should not include the AdditionalDocumentReference IssueTime |
UBL-CR-114 (warning) |
[UBL-CR-114]-A UBL invoice should not include the AdditionalDocumentReference DocumentType |
UBL-CR-115 (warning) |
[UBL-CR-115]-A UBL invoice should not include the AdditionalDocumentReference Xpath |
UBL-CR-116 (warning) |
[UBL-CR-116]-A UBL invoice should not include the AdditionalDocumentReference LanguageID |
UBL-CR-117 (warning) |
[UBL-CR-117]-A UBL invoice should not include the AdditionalDocumentReference LocaleCode |
UBL-CR-118 (warning) |
[UBL-CR-118]-A UBL invoice should not include the AdditionalDocumentReference VersionID |
UBL-CR-119 (warning) |
[UBL-CR-119]-A UBL invoice should not include the AdditionalDocumentReference DocumentStatusCode |
UBL-CR-121 (warning) |
[UBL-CR-121]-A UBL invoice should not include the AdditionalDocumentReference Attachment External DocumentHash |
UBL-CR-122 (warning) |
[UBL-CR-122]-A UBL invoice should not include the AdditionalDocumentReference Attachment External HashAlgorithmMethod |
UBL-CR-123 (warning) |
[UBL-CR-123]-A UBL invoice should not include the AdditionalDocumentReference Attachment External ExpiryDate |
UBL-CR-124 (warning) |
[UBL-CR-124]-A UBL invoice should not include the AdditionalDocumentReference Attachment External ExpiryTime |
UBL-CR-125 (warning) |
[UBL-CR-125]-A UBL invoice should not include the AdditionalDocumentReference Attachment External MimeCode |
UBL-CR-126 (warning) |
[UBL-CR-126]-A UBL invoice should not include the AdditionalDocumentReference Attachment External FormatCode |
UBL-CR-127 (warning) |
[UBL-CR-127]-A UBL invoice should not include the AdditionalDocumentReference Attachment External EncodingCode |
UBL-CR-128 (warning) |
[UBL-CR-128]-A UBL invoice should not include the AdditionalDocumentReference Attachment External CharacterSetCode |
UBL-CR-129 (warning) |
[UBL-CR-129]-A UBL invoice should not include the AdditionalDocumentReference Attachment External FileName |
UBL-CR-130 (warning) |
[UBL-CR-130]-A UBL invoice should not include the AdditionalDocumentReference Attachment External Descriprion |
UBL-CR-131 (warning) |
[UBL-CR-131]-A UBL invoice should not include the AdditionalDocumentReference ValidityPeriod |
UBL-CR-132 (warning) |
[UBL-CR-132]-A UBL invoice should not include the AdditionalDocumentReference IssuerParty |
UBL-CR-133 (warning) |
[UBL-CR-133]-A UBL invoice should not include the AdditionalDocumentReference ResultOfVerification |
UBL-CR-134 (warning) |
[UBL-CR-134]-A UBL invoice should not include the ProjectReference UUID |
UBL-CR-135 (warning) |
[UBL-CR-135]-A UBL invoice should not include the ProjectReference IssueDate |
UBL-CR-136 (warning) |
[UBL-CR-136]-A UBL invoice should not include the ProjectReference WorkPhaseReference |
UBL-CR-137 (warning) |
[UBL-CR-137]-A UBL invoice should not include the Signature |
UBL-CR-138 (warning) |
[UBL-CR-138]-A UBL invoice should not include the AccountingSupplierParty CustomerAssignedAccountID |
UBL-CR-139 (warning) |
[UBL-CR-139]-A UBL invoice should not include the AccountingSupplierParty AdditionalAccountID |
UBL-CR-140 (warning) |
[UBL-CR-140]-A UBL invoice should not include the AccountingSupplierParty DataSendingCapability |
UBL-CR-141 (warning) |
[UBL-CR-141]-A UBL invoice should not include the AccountingSupplierParty Party MarkCareIndicator |
UBL-CR-142 (warning) |
[UBL-CR-142]-A UBL invoice should not include the AccountingSupplierParty Party MarkAttentionIndicator |
UBL-CR-143 (warning) |
[UBL-CR-143]-A UBL invoice should not include the AccountingSupplierParty Party WebsiteURI |
UBL-CR-144 (warning) |
[UBL-CR-144]-A UBL invoice should not include the AccountingSupplierParty Party LogoReferenceID |
UBL-CR-145 (warning) |
[UBL-CR-145]-A UBL invoice should not include the AccountingSupplierParty Party IndustryClassificationCode |
UBL-CR-146 (warning) |
[UBL-CR-146]-A UBL invoice should not include the AccountingSupplierParty Party Language |
UBL-CR-147 (warning) |
[UBL-CR-147]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress ID |
UBL-CR-148 (warning) |
[UBL-CR-148]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress AddressTypeCode |
UBL-CR-149 (warning) |
[UBL-CR-149]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress AddressFormatCode |
UBL-CR-150 (warning) |
[UBL-CR-150]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress Postbox |
UBL-CR-151 (warning) |
[UBL-CR-151]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress Floor |
UBL-CR-152 (warning) |
[UBL-CR-152]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress Room |
UBL-CR-153 (warning) |
[UBL-CR-153]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress BlockName |
UBL-CR-154 (warning) |
[UBL-CR-154]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress BuildingName |
UBL-CR-155 (warning) |
[UBL-CR-155]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress BuildingNumber |
UBL-CR-156 (warning) |
[UBL-CR-156]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress InhouseMail |
UBL-CR-157 (warning) |
[UBL-CR-157]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress Department |
UBL-CR-158 (warning) |
[UBL-CR-158]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress MarkAttention |
UBL-CR-159 (warning) |
[UBL-CR-159]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress MarkCare |
UBL-CR-160 (warning) |
[UBL-CR-160]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress PlotIdentification |
UBL-CR-161 (warning) |
[UBL-CR-161]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress CitySubdivisionName |
UBL-CR-162 (warning) |
[UBL-CR-162]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress CountrySubentityCode |
UBL-CR-163 (warning) |
[UBL-CR-163]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress Region |
UBL-CR-164 (warning) |
[UBL-CR-164]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress District |
UBL-CR-165 (warning) |
[UBL-CR-165]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress TimezoneOffset |
UBL-CR-166 (warning) |
[UBL-CR-166]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress Country Name |
UBL-CR-167 (warning) |
[UBL-CR-167]-A UBL invoice should not include the AccountingSupplierParty Party PostalAddress LocationCoordinate |
UBL-CR-168 (warning) |
[UBL-CR-168]-A UBL invoice should not include the AccountingSupplierParty Party PhysicalLocation |
UBL-CR-169 (warning) |
[UBL-CR-169]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme RegistrationName |
UBL-CR-170 (warning) |
[UBL-CR-170]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme TaxLevelCode |
UBL-CR-171 (warning) |
[UBL-CR-171]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme ExemptionReasonCode |
UBL-CR-172 (warning) |
[UBL-CR-172]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme ExemptionReason |
UBL-CR-173 (warning) |
[UBL-CR-173]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme RegistrationAddress |
UBL-CR-174 (warning) |
[UBL-CR-174]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme TaxScheme Name |
UBL-CR-175 (warning) |
[UBL-CR-175]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme TaxScheme TaxTypeCode |
UBL-CR-176 (warning) |
[UBL-CR-176]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme TaxScheme CurrencyCode |
UBL-CR-177 (warning) |
[UBL-CR-177]-A UBL invoice should not include the AccountingSupplierParty Party PartyTaxScheme TaxScheme JurisdictionRegionAddress |
UBL-CR-178 (warning) |
[UBL-CR-178]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity RegistrationDate |
UBL-CR-179 (warning) |
[UBL-CR-179]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity RegistrationExpirationDate |
UBL-CR-180 (warning) |
[UBL-CR-180]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity CompanyLegalFormCode |
UBL-CR-181 (warning) |
[UBL-CR-181]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity SoleProprietorshipIndicator |
UBL-CR-182 (warning) |
[UBL-CR-182]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity CompanyLiquidationStatusCode |
UBL-CR-183 (warning) |
[UBL-CR-183]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity CorporationStockAmount |
UBL-CR-184 (warning) |
[UBL-CR-184]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity FullyPaidSharesIndicator |
UBL-CR-185 (warning) |
[UBL-CR-185]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity RegistrationAddress |
UBL-CR-186 (warning) |
[UBL-CR-186]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity CorporateRegistrationScheme |
UBL-CR-187 (warning) |
[UBL-CR-187]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity HeadOfficeParty |
UBL-CR-188 (warning) |
[UBL-CR-188]-A UBL invoice should not include the AccountingSupplierParty Party PartyLegalEntity ShareholderParty |
UBL-CR-189 (warning) |
[UBL-CR-189]-A UBL invoice should not include the AccountingSupplierParty Party Contact ID |
UBL-CR-190 (warning) |
[UBL-CR-190]-A UBL invoice should not include the AccountingSupplierParty Party Contact Telefax |
UBL-CR-191 (warning) |
[UBL-CR-191]-A UBL invoice should not include the AccountingSupplierParty Party Contact Note |
UBL-CR-192 (warning) |
[UBL-CR-192]-A UBL invoice should not include the AccountingSupplierParty Party Contact OtherCommunication |
UBL-CR-193 (warning) |
[UBL-CR-193]-A UBL invoice should not include the AccountingSupplierParty Party Person |
UBL-CR-194 (warning) |
[UBL-CR-194]-A UBL invoice should not include the AccountingSupplierParty Party AgentParty |
UBL-CR-195 (warning) |
[UBL-CR-195]-A UBL invoice should not include the AccountingSupplierParty Party ServiceProviderParty |
UBL-CR-196 (warning) |
[UBL-CR-196]-A UBL invoice should not include the AccountingSupplierParty Party PowerOfAttorney |
UBL-CR-197 (warning) |
[UBL-CR-197]-A UBL invoice should not include the AccountingSupplierParty Party FinancialAccount |
UBL-CR-198 (warning) |
[UBL-CR-198]-A UBL invoice should not include the AccountingSupplierParty DespatchContact |
UBL-CR-199 (warning) |
[UBL-CR-199]-A UBL invoice should not include the AccountingSupplierParty AccountingContact |
UBL-CR-200 (warning) |
[UBL-CR-200]-A UBL invoice should not include the AccountingSupplierParty SellerContact |
UBL-CR-201 (warning) |
[UBL-CR-201]-A UBL invoice should not include the AccountingCustomerParty CustomerAssignedAccountID |
UBL-CR-202 (warning) |
[UBL-CR-202]-A UBL invoice should not include the AccountingCustomerParty SupplierAssignedAccountID |
UBL-CR-203 (warning) |
[UBL-CR-203]-A UBL invoice should not include the AccountingCustomerParty AdditionalAccountID |
UBL-CR-204 (warning) |
[UBL-CR-204]-A UBL invoice should not include the AccountingCustomerParty Party MarkCareIndicator |
UBL-CR-205 (warning) |
[UBL-CR-205]-A UBL invoice should not include the AccountingCustomerParty Party MarkAttentionIndicator |
UBL-CR-206 (warning) |
[UBL-CR-206]-A UBL invoice should not include the AccountingCustomerParty Party WebsiteURI |
UBL-CR-207 (warning) |
[UBL-CR-207]-A UBL invoice should not include the AccountingCustomerParty Party LogoReferenceID |
UBL-CR-208 (warning) |
[UBL-CR-208]-A UBL invoice should not include the AccountingCustomerParty Party IndustryClassificationCode |
UBL-CR-209 (warning) |
[UBL-CR-209]-A UBL invoice should not include the AccountingCustomerParty Party Language |
UBL-CR-210 (warning) |
[UBL-CR-210]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress ID |
UBL-CR-211 (warning) |
[UBL-CR-211]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress AddressTypeCode |
UBL-CR-212 (warning) |
[UBL-CR-212]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress AddressFormatCode |
UBL-CR-213 (warning) |
[UBL-CR-213]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress Postbox |
UBL-CR-214 (warning) |
[UBL-CR-214]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress Floor |
UBL-CR-215 (warning) |
[UBL-CR-215]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress Room |
UBL-CR-216 (warning) |
[UBL-CR-216]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress BlockName |
UBL-CR-217 (warning) |
[UBL-CR-217]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress BuildingName |
UBL-CR-218 (warning) |
[UBL-CR-218]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress BuildingNumber |
UBL-CR-219 (warning) |
[UBL-CR-219]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress InhouseMail |
UBL-CR-220 (warning) |
[UBL-CR-220]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress Department |
UBL-CR-221 (warning) |
[UBL-CR-221]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress MarkAttention |
UBL-CR-222 (warning) |
[UBL-CR-222]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress MarkCare |
UBL-CR-223 (warning) |
[UBL-CR-223]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress PlotIdentification |
UBL-CR-224 (warning) |
[UBL-CR-224]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress CitySubdivisionName |
UBL-CR-225 (warning) |
[UBL-CR-225]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress CountrySubentityCode |
UBL-CR-226 (warning) |
[UBL-CR-226]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress Region |
UBL-CR-227 (warning) |
[UBL-CR-227]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress District |
UBL-CR-228 (warning) |
[UBL-CR-228]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress TimezoneOffset |
UBL-CR-229 (warning) |
[UBL-CR-229]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress Country Name |
UBL-CR-230 (warning) |
[UBL-CR-230]-A UBL invoice should not include the AccountingCustomerParty Party PostalAddress LocationCoordinate |
UBL-CR-231 (warning) |
[UBL-CR-231]-A UBL invoice should not include the AccountingCustomerParty Party PhysicalLocation |
UBL-CR-232 (warning) |
[UBL-CR-232]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme RegistrationName |
UBL-CR-233 (warning) |
[UBL-CR-233]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme TaxLevelCode |
UBL-CR-234 (warning) |
[UBL-CR-234]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme ExemptionReasonCode |
UBL-CR-235 (warning) |
[UBL-CR-235]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme ExemptionReason |
UBL-CR-236 (warning) |
[UBL-CR-236]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme RegistrationAddress |
UBL-CR-237 (warning) |
[UBL-CR-237]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme TaxScheme Name |
UBL-CR-238 (warning) |
[UBL-CR-238]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme TaxScheme TaxTypeCode |
UBL-CR-239 (warning) |
[UBL-CR-239]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme TaxScheme CurrencyCode |
UBL-CR-240 (warning) |
[UBL-CR-240]-A UBL invoice should not include the AccountingCustomerParty Party PartyTaxScheme TaxScheme JurisdictionRegionAddress |
UBL-CR-241 (warning) |
[UBL-CR-241]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity RegistrationDate |
UBL-CR-242 (warning) |
[UBL-CR-242]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity RegistrationExpirationDate |
UBL-CR-243 (warning) |
[UBL-CR-243]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity CompanyLegalFormCode |
UBL-CR-244 (warning) |
[UBL-CR-244]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity CompanyLegalForm |
UBL-CR-245 (warning) |
[UBL-CR-245]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity SoleProprietorshipIndicator |
UBL-CR-246 (warning) |
[UBL-CR-246]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity CompanyLiquidationStatusCode |
UBL-CR-247 (warning) |
[UBL-CR-247]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity CorporationStockAmount |
UBL-CR-248 (warning) |
[UBL-CR-248]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity FullyPaidSharesIndicator |
UBL-CR-249 (warning) |
[UBL-CR-249]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity RegistrationAddress |
UBL-CR-250 (warning) |
[UBL-CR-250]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity CorporateRegistrationScheme |
UBL-CR-251 (warning) |
[UBL-CR-251]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity HeadOfficeParty |
UBL-CR-252 (warning) |
[UBL-CR-252]-A UBL invoice should not include the AccountingCustomerParty Party PartyLegalEntity ShareholderParty |
UBL-CR-253 (warning) |
[UBL-CR-253]-A UBL invoice should not include the AccountingCustomerParty Party Contact ID |
UBL-CR-254 (warning) |
[UBL-CR-254]-A UBL invoice should not include the AccountingCustomerParty Party Contact Telefax |
UBL-CR-255 (warning) |
[UBL-CR-255]-A UBL invoice should not include the AccountingCustomerParty Party Contact Note |
UBL-CR-256 (warning) |
[UBL-CR-256]-A UBL invoice should not include the AccountingCustomerParty Party Contact OtherCommunication |
UBL-CR-257 (warning) |
[UBL-CR-257]-A UBL invoice should not include the AccountingCustomerParty Party Person |
UBL-CR-258 (warning) |
[UBL-CR-258]-A UBL invoice should not include the AccountingCustomerParty Party AgentParty |
UBL-CR-259 (warning) |
[UBL-CR-259]-A UBL invoice should not include the AccountingCustomerParty Party ServiceProviderParty |
UBL-CR-260 (warning) |
[UBL-CR-260]-A UBL invoice should not include the AccountingCustomerParty Party PowerOfAttorney |
UBL-CR-261 (warning) |
[UBL-CR-261]-A UBL invoice should not include the AccountingCustomerParty Party FinancialAccount |
UBL-CR-262 (warning) |
[UBL-CR-262]-A UBL invoice should not include the AccountingCustomerParty DeliveryContact |
UBL-CR-263 (warning) |
[UBL-CR-263]-A UBL invoice should not include the AccountingCustomerParty AccountingContact |
UBL-CR-264 (warning) |
[UBL-CR-264]-A UBL invoice should not include the AccountingCustomerParty BuyerContact |
UBL-CR-265 (warning) |
[UBL-CR-265]-A UBL invoice should not include the PayeeParty MarkCareIndicator |
UBL-CR-266 (warning) |
[UBL-CR-266]-A UBL invoice should not include the PayeeParty MarkAttentionIndicator |
UBL-CR-267 (warning) |
[UBL-CR-267]-A UBL invoice should not include the PayeeParty WebsiteURI |
UBL-CR-268 (warning) |
[UBL-CR-268]-A UBL invoice should not include the PayeeParty LogoReferenceID |
UBL-CR-269 (warning) |
[UBL-CR-269]-A UBL invoice should not include the PayeeParty EndpointID |
UBL-CR-270 (warning) |
[UBL-CR-270]-A UBL invoice should not include the PayeeParty IndustryClassificationCode |
UBL-CR-271 (warning) |
[UBL-CR-271]-A UBL invoice should not include the PayeeParty Language |
UBL-CR-272 (warning) |
[UBL-CR-272]-A UBL invoice should not include the PayeeParty PostalAddress |
UBL-CR-273 (warning) |
[UBL-CR-273]-A UBL invoice should not include the PayeeParty PhysicalLocation |
UBL-CR-274 (warning) |
[UBL-CR-274]-A UBL invoice should not include the PayeeParty PartyTaxScheme |
UBL-CR-275 (warning) |
[UBL-CR-275]-A UBL invoice should not include the PayeeParty PartyLegalEntity RegistrationName |
UBL-CR-276 (warning) |
[UBL-CR-276]-A UBL invoice should not include the PayeeParty PartyLegalEntity RegistrationDate |
UBL-CR-277 (warning) |
[UBL-CR-277]-A UBL invoice should not include the PayeeParty PartyLegalEntity RegistrationExpirationDate |
UBL-CR-278 (warning) |
[UBL-CR-278]-A UBL invoice should not include the PayeeParty PartyLegalEntity CompanyLegalFormCode |
UBL-CR-279 (warning) |
[UBL-CR-279]-A UBL invoice should not include the PayeeParty PartyLegalEntity CompanyLegalForm |
UBL-CR-280 (warning) |
[UBL-CR-280]-A UBL invoice should not include the PayeeParty PartyLegalEntity SoleProprietorshipIndicator |
UBL-CR-281 (warning) |
[UBL-CR-281]-A UBL invoice should not include the PayeeParty PartyLegalEntity CompanyLiquidationStatusCode |
UBL-CR-282 (warning) |
[UBL-CR-282]-A UBL invoice should not include the PayeeParty PartyLegalEntity CorporationStockAmount |
UBL-CR-283 (warning) |
[UBL-CR-283]-A UBL invoice should not include the PayeeParty PartyLegalEntity FullyPaidSharesIndicator |
UBL-CR-284 (warning) |
[UBL-CR-284]-A UBL invoice should not include the PayeeParty PartyLegalEntity RegistrationAddress |
UBL-CR-285 (warning) |
[UBL-CR-285]-A UBL invoice should not include the PayeeParty PartyLegalEntity CorporateRegistrationScheme |
UBL-CR-286 (warning) |
[UBL-CR-286]-A UBL invoice should not include the PayeeParty PartyLegalEntity HeadOfficeParty |
UBL-CR-287 (warning) |
[UBL-CR-287]-A UBL invoice should not include the PayeeParty PartyLegalEntity ShareholderParty |
UBL-CR-288 (warning) |
[UBL-CR-288]-A UBL invoice should not include the PayeeParty Contact |
UBL-CR-289 (warning) |
[UBL-CR-289]-A UBL invoice should not include the PayeeParty Person |
UBL-CR-290 (warning) |
[UBL-CR-290]-A UBL invoice should not include the PayeeParty AgentParty |
UBL-CR-291 (warning) |
[UBL-CR-291]-A UBL invoice should not include the PayeeParty ServiceProviderParty |
UBL-CR-292 (warning) |
[UBL-CR-292]-A UBL invoice should not include the PayeeParty PowerOfAttorney |
UBL-CR-293 (warning) |
[UBL-CR-293]-A UBL invoice should not include the PayeeParty FinancialAccount |
UBL-CR-294 (warning) |
[UBL-CR-294]-A UBL invoice should not include the BuyerCustomerParty |
UBL-CR-295 (warning) |
[UBL-CR-295]-A UBL invoice should not include the SellerCustomerParty |
UBL-CR-296 (warning) |
[UBL-CR-296]-A UBL invoice should not include the TaxRepresentativeParty MarkCareIndicator |
UBL-CR-297 (warning) |
[UBL-CR-297]-A UBL invoice should not include the TaxRepresentativeParty MarkAttentionIndicator |
UBL-CR-298 (warning) |
[UBL-CR-298]-A UBL invoice should not include the TaxRepresentativeParty WebsiteURI |
UBL-CR-299 (warning) |
[UBL-CR-299]-A UBL invoice should not include the TaxRepresentativeParty LogoReferenceID |
UBL-CR-300 (warning) |
[UBL-CR-300]-A UBL invoice should not include the TaxRepresentativeParty EndpointID |
UBL-CR-301 (warning) |
[UBL-CR-301]-A UBL invoice should not include the TaxRepresentativeParty IndustryClassificationCode |
UBL-CR-302 (warning) |
[UBL-CR-302]-A UBL invoice should not include the TaxRepresentativeParty PartyIdentification |
UBL-CR-303 (warning) |
[UBL-CR-303]-A UBL invoice should not include the TaxRepresentativeParty Language |
UBL-CR-304 (warning) |
[UBL-CR-304]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress ID |
UBL-CR-305 (warning) |
[UBL-CR-305]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress AddressTypeCode |
UBL-CR-306 (warning) |
[UBL-CR-306]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress AddressFormatCode |
UBL-CR-307 (warning) |
[UBL-CR-307]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress Postbox |
UBL-CR-308 (warning) |
[UBL-CR-308]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress Floor |
UBL-CR-309 (warning) |
[UBL-CR-309]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress Room |
UBL-CR-310 (warning) |
[UBL-CR-310]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress BlockName |
UBL-CR-311 (warning) |
[UBL-CR-311]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress BuildingName |
UBL-CR-312 (warning) |
[UBL-CR-312]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress BuildingNumber |
UBL-CR-313 (warning) |
[UBL-CR-313]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress InhouseMail |
UBL-CR-314 (warning) |
[UBL-CR-314]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress Department |
UBL-CR-315 (warning) |
[UBL-CR-315]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress MarkAttention |
UBL-CR-316 (warning) |
[UBL-CR-316]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress MarkCare |
UBL-CR-317 (warning) |
[UBL-CR-317]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress PlotIdentification |
UBL-CR-318 (warning) |
[UBL-CR-318]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress CitySubdivisionName |
UBL-CR-319 (warning) |
[UBL-CR-319]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress CountrySubentityCode |
UBL-CR-320 (warning) |
[UBL-CR-320]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress Region |
UBL-CR-321 (warning) |
[UBL-CR-321]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress District |
UBL-CR-322 (warning) |
[UBL-CR-322]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress TimezoneOffset |
UBL-CR-323 (warning) |
[UBL-CR-323]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress Country Name |
UBL-CR-324 (warning) |
[UBL-CR-324]-A UBL invoice should not include the TaxRepresentativeParty PostalAddress LocationCoordinate |
UBL-CR-325 (warning) |
[UBL-CR-325]-A UBL invoice should not include the TaxRepresentativeParty PhysicalLocation |
UBL-CR-326 (warning) |
[UBL-CR-326]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme RegistrationName |
UBL-CR-327 (warning) |
[UBL-CR-327]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme TaxLevelCode |
UBL-CR-328 (warning) |
[UBL-CR-328]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme ExemptionReasonCode |
UBL-CR-329 (warning) |
[UBL-CR-329]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme ExemptionReason |
UBL-CR-330 (warning) |
[UBL-CR-330]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme RegistrationAddress |
UBL-CR-331 (warning) |
[UBL-CR-331]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme TaxScheme Name |
UBL-CR-332 (warning) |
[UBL-CR-332]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme TaxScheme TaxTypeCode |
UBL-CR-333 (warning) |
[UBL-CR-333]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme TaxScheme CurrencyCode |
UBL-CR-334 (warning) |
[UBL-CR-334]-A UBL invoice should not include the TaxRepresentativeParty PartyTaxScheme TaxScheme JurisdictionRegionAddress |
UBL-CR-335 (warning) |
[UBL-CR-335]-A UBL invoice should not include the TaxRepresentativeParty PartyLegalEntity |
UBL-CR-336 (warning) |
[UBL-CR-336]-A UBL invoice should not include the TaxRepresentativeParty Contact |
UBL-CR-337 (warning) |
[UBL-CR-337]-A UBL invoice should not include the TaxRepresentativeParty Person |
UBL-CR-338 (warning) |
[UBL-CR-338]-A UBL invoice should not include the TaxRepresentativeParty AgentParty |
UBL-CR-339 (warning) |
[UBL-CR-339]-A UBL invoice should not include the TaxRepresentativeParty ServiceProviderParty |
UBL-CR-340 (warning) |
[UBL-CR-340]-A UBL invoice should not include the TaxRepresentativeParty PowerOfAttorney |
UBL-CR-341 (warning) |
[UBL-CR-341]-A UBL invoice should not include the TaxRepresentativeParty FinancialAccount |
UBL-CR-342 (warning) |
[UBL-CR-342]-A UBL invoice should not include the Delivery ID |
UBL-CR-343 (warning) |
[UBL-CR-343]-A UBL invoice should not include the Delivery Quantity |
UBL-CR-344 (warning) |
[UBL-CR-344]-A UBL invoice should not include the Delivery MinimumQuantity |
UBL-CR-345 (warning) |
[UBL-CR-345]-A UBL invoice should not include the Delivery MaximumQuantity |
UBL-CR-346 (warning) |
[UBL-CR-346]-A UBL invoice should not include the Delivery ActualDeliveryTime |
UBL-CR-347 (warning) |
[UBL-CR-347]-A UBL invoice should not include the Delivery LatestDeliveryDate |
UBL-CR-348 (warning) |
[UBL-CR-348]-A UBL invoice should not include the Delivery LatestDeliveryTime |
UBL-CR-349 (warning) |
[UBL-CR-349]-A UBL invoice should not include the Delivery ReleaseID |
UBL-CR-350 (warning) |
[UBL-CR-350]-A UBL invoice should not include the Delivery TrackingID |
UBL-CR-351 (warning) |
[UBL-CR-351]-A UBL invoice should not include the Delivery DeliveryLocation Description |
UBL-CR-352 (warning) |
[UBL-CR-352]-A UBL invoice should not include the Delivery DeliveryLocation Conditions |
UBL-CR-353 (warning) |
[UBL-CR-353]-A UBL invoice should not include the Delivery DeliveryLocation CountrySubentity |
UBL-CR-354 (warning) |
[UBL-CR-354]-A UBL invoice should not include the Delivery DeliveryLocation CountrySubentityCode |
UBL-CR-355 (warning) |
[UBL-CR-355]-A UBL invoice should not include the Delivery DeliveryLocation LocationTypeCode |
UBL-CR-356 (warning) |
[UBL-CR-356]-A UBL invoice should not include the Delivery DeliveryLocation InformationURI |
UBL-CR-357 (warning) |
[UBL-CR-357]-A UBL invoice should not include the Delivery DeliveryLocation Name |
UBL-CR-358 (warning) |
[UBL-CR-358]-A UBL invoice should not include the Delivery DeliveryLocation ValidationPeriod |
UBL-CR-359 (warning) |
[UBL-CR-359]-A UBL invoice should not include the Delivery DeliveryLocation Address ID |
UBL-CR-360 (warning) |
[UBL-CR-360]-A UBL invoice should not include the Delivery DeliveryLocation Address AddressTypeCode |
UBL-CR-361 (warning) |
[UBL-CR-361]-A UBL invoice should not include the Delivery DeliveryLocation Address AddressFormatCode |
UBL-CR-362 (warning) |
[UBL-CR-362]-A UBL invoice should not include the Delivery DeliveryLocation Address Postbox |
UBL-CR-363 (warning) |
[UBL-CR-363]-A UBL invoice should not include the Delivery DeliveryLocation Address Floor |
UBL-CR-364 (warning) |
[UBL-CR-364]-A UBL invoice should not include the Delivery DeliveryLocation Address Room |
UBL-CR-365 (warning) |
[UBL-CR-365]-A UBL invoice should not include the Delivery DeliveryLocation Address BlockName |
UBL-CR-366 (warning) |
[UBL-CR-366]-A UBL invoice should not include the Delivery DeliveryLocation Address BuildingName |
UBL-CR-367 (warning) |
[UBL-CR-367]-A UBL invoice should not include the Delivery DeliveryLocation Address BuildingNumber |
UBL-CR-368 (warning) |
[UBL-CR-368]-A UBL invoice should not include the Delivery DeliveryLocation Address InhouseMail |
UBL-CR-369 (warning) |
[UBL-CR-369]-A UBL invoice should not include the Delivery DeliveryLocation Address Department |
UBL-CR-370 (warning) |
[UBL-CR-370]-A UBL invoice should not include the Delivery DeliveryLocation Address MarkAttention |
UBL-CR-371 (warning) |
[UBL-CR-371]-A UBL invoice should not include the Delivery DeliveryLocation Address MarkCare |
UBL-CR-372 (warning) |
[UBL-CR-372]-A UBL invoice should not include the Delivery DeliveryLocation Address PlotIdentification |
UBL-CR-373 (warning) |
[UBL-CR-373]-A UBL invoice should not include the Delivery DeliveryLocation Address CitySubdivisionName |
UBL-CR-374 (warning) |
[UBL-CR-374]-A UBL invoice should not include the Delivery DeliveryLocation Address CountrySubentityCode |
UBL-CR-375 (warning) |
[UBL-CR-375]-A UBL invoice should not include the Delivery DeliveryLocation Address Region |
UBL-CR-376 (warning) |
[UBL-CR-376]-A UBL invoice should not include the Delivery DeliveryLocation Address District |
UBL-CR-377 (warning) |
[UBL-CR-377]-A UBL invoice should not include the Delivery DeliveryLocation Address TimezoneOffset |
UBL-CR-378 (warning) |
[UBL-CR-378]-A UBL invoice should not include the Delivery DeliveryLocation Address Country Name |
UBL-CR-379 (warning) |
[UBL-CR-379]-A UBL invoice should not include the Delivery DeliveryLocation Address LocationCoordinate |
UBL-CR-380 (warning) |
[UBL-CR-380]-A UBL invoice should not include the Delivery DeliveryLocation SubsidiaryLocation |
UBL-CR-381 (warning) |
[UBL-CR-381]-A UBL invoice should not include the Delivery DeliveryLocation LocationCoordinate |
UBL-CR-382 (warning) |
[UBL-CR-382]-A UBL invoice should not include the Delivery AlternativeDeliveryLocation |
UBL-CR-383 (warning) |
[UBL-CR-383]-A UBL invoice should not include the Delivery RequestedDeliveryPeriod |
UBL-CR-384 (warning) |
[UBL-CR-384]-A UBL invoice should not include the Delivery PromisedDeliveryPeriod |
UBL-CR-385 (warning) |
[UBL-CR-385]-A UBL invoice should not include the Delivery CarrierParty |
UBL-CR-386 (warning) |
[UBL-CR-386]-A UBL invoice should not include the DeliveryParty MarkCareIndicator |
UBL-CR-387 (warning) |
[UBL-CR-387]-A UBL invoice should not include the DeliveryParty MarkAttentionIndicator |
UBL-CR-388 (warning) |
[UBL-CR-388]-A UBL invoice should not include the DeliveryParty WebsiteURI |
UBL-CR-389 (warning) |
[UBL-CR-389]-A UBL invoice should not include the DeliveryParty LogoReferenceID |
UBL-CR-390 (warning) |
[UBL-CR-390]-A UBL invoice should not include the DeliveryParty EndpointID |
UBL-CR-391 (warning) |
[UBL-CR-391]-A UBL invoice should not include the DeliveryParty IndustryClassificationCode |
UBL-CR-392 (warning) |
[UBL-CR-392]-A UBL invoice should not include the DeliveryParty PartyIdentification |
UBL-CR-393 (warning) |
[UBL-CR-393]-A UBL invoice should not include the DeliveryParty Language |
UBL-CR-394 (warning) |
[UBL-CR-394]-A UBL invoice should not include the DeliveryParty PostalAddress |
UBL-CR-395 (warning) |
[UBL-CR-395]-A UBL invoice should not include the DeliveryParty PhysicalLocation |
UBL-CR-396 (warning) |
[UBL-CR-396]-A UBL invoice should not include the DeliveryParty PartyTaxScheme |
UBL-CR-397 (warning) |
[UBL-CR-397]-A UBL invoice should not include the DeliveryParty PartyLegalEntity |
UBL-CR-398 (warning) |
[UBL-CR-398]-A UBL invoice should not include the DeliveryParty Contact |
UBL-CR-399 (warning) |
[UBL-CR-399]-A UBL invoice should not include the DeliveryParty Person |
UBL-CR-400 (warning) |
[UBL-CR-400]-A UBL invoice should not include the DeliveryParty AgentParty |
UBL-CR-401 (warning) |
[UBL-CR-401]-A UBL invoice should not include the DeliveryParty ServiceProviderParty |
UBL-CR-402 (warning) |
[UBL-CR-402]-A UBL invoice should not include the DeliveryParty PowerOfAttorney |
UBL-CR-403 (warning) |
[UBL-CR-403]-A UBL invoice should not include the DeliveryParty FinancialAccount |
UBL-CR-404 (warning) |
[UBL-CR-404]-A UBL invoice should not include the Delivery NotifyParty |
UBL-CR-405 (warning) |
[UBL-CR-405]-A UBL invoice should not include the Delivery Despatch |
UBL-CR-406 (warning) |
[UBL-CR-406]-A UBL invoice should not include the Delivery DeliveryTerms |
UBL-CR-407 (warning) |
[UBL-CR-407]-A UBL invoice should not include the Delivery MinimumDeliveryUnit |
UBL-CR-408 (warning) |
[UBL-CR-408]-A UBL invoice should not include the Delivery MaximumDeliveryUnit |
UBL-CR-409 (warning) |
[UBL-CR-409]-A UBL invoice should not include the Delivery Shipment |
UBL-CR-410 (warning) |
[UBL-CR-410]-A UBL invoice should not include the DeliveryTerms |
UBL-CR-411 (warning) |
[UBL-CR-411]-A UBL invoice should not include the PaymentMeans ID |
UBL-CR-412 (warning) |
[UBL-CR-412]-A UBL invoice should not include the PaymentMeans PaymentDueDate |
UBL-CR-413 (warning) |
[UBL-CR-413]-A UBL invoice should not include the PaymentMeans PaymentChannelCode |
UBL-CR-414 (warning) |
[UBL-CR-414]-A UBL invoice should not include the PaymentMeans InstructionID |
UBL-CR-415 (warning) |
[UBL-CR-415]-A UBL invoice should not include the PaymentMeans CardAccount CardTypeCode |
UBL-CR-416 (warning) |
[UBL-CR-416]-A UBL invoice should not include the PaymentMeans CardAccount ValidityStartDate |
UBL-CR-417 (warning) |
[UBL-CR-417]-A UBL invoice should not include the PaymentMeans CardAccount ExpiryDate |
UBL-CR-418 (warning) |
[UBL-CR-418]-A UBL invoice should not include the PaymentMeans CardAccount IssuerID |
UBL-CR-419 (warning) |
[UBL-CR-419]-A UBL invoice should not include the PaymentMeans CardAccount IssuerNumberID |
UBL-CR-420 (warning) |
[UBL-CR-420]-A UBL invoice should not include the PaymentMeans CardAccount CV2ID |
UBL-CR-421 (warning) |
[UBL-CR-421]-A UBL invoice should not include the PaymentMeans CardAccount CardChipCode |
UBL-CR-422 (warning) |
[UBL-CR-422]-A UBL invoice should not include the PaymentMeans CardAccount ChipApplicationID |
UBL-CR-424 (warning) |
[UBL-CR-424]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount AliasName |
UBL-CR-425 (warning) |
[UBL-CR-425]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount AccountTypeCode |
UBL-CR-426 (warning) |
[UBL-CR-426]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount AccountFormatCode |
UBL-CR-427 (warning) |
[UBL-CR-427]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount CurrencyCode |
UBL-CR-428 (warning) |
[UBL-CR-428]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount PaymentNote |
UBL-CR-429 (warning) |
[UBL-CR-429]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount FinancialInstitutionBranch Name |
UBL-CR-430 (warning) |
[UBL-CR-430]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount FinancialInstitutionBranch FinancialInstitution Name |
UBL-CR-431 (warning) |
[UBL-CR-431]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount FinancialInstitutionBranch FinancialInstitution Address |
UBL-CR-432 (warning) |
[UBL-CR-432]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount FinancialInstitutionBranch Address |
UBL-CR-433 (warning) |
[UBL-CR-433]-A UBL invoice should not include the PaymentMeans PayeeFinancialAccount Country |
UBL-CR-434 (warning) |
[UBL-CR-434]-A UBL invoice should not include the PaymentMeans CreditAccount |
UBL-CR-435 (warning) |
[UBL-CR-435]-A UBL invoice should not include the PaymentMeans PaymentMandate MandateTypeCode |
UBL-CR-436 (warning) |
[UBL-CR-436]-A UBL invoice should not include the PaymentMeans PaymentMandate MaximumPaymentInstructionsNumeric |
UBL-CR-437 (warning) |
[UBL-CR-437]-A UBL invoice should not include the PaymentMeans PaymentMandate MaximumPaidAmount |
UBL-CR-438 (warning) |
[UBL-CR-438]-A UBL invoice should not include the PaymentMeans PaymentMandate SignatureID |
UBL-CR-439 (warning) |
[UBL-CR-439]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerParty |
UBL-CR-440 (warning) |
[UBL-CR-440]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount Name |
UBL-CR-441 (warning) |
[UBL-CR-441]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount AliasName |
UBL-CR-442 (warning) |
[UBL-CR-442]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount AccountTypeCode |
UBL-CR-443 (warning) |
[UBL-CR-443]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount AccountFormatCode |
UBL-CR-444 (warning) |
[UBL-CR-444]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount CurrencyCode |
UBL-CR-445 (warning) |
[UBL-CR-445]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount PaymentNote |
UBL-CR-446 (warning) |
[UBL-CR-446]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount FinancialInstitutionBranch |
UBL-CR-447 (warning) |
[UBL-CR-447]-A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount Country |
UBL-CR-448 (warning) |
[UBL-CR-448]-A UBL invoice should not include the PaymentMeans PaymentMandate ValidityPeriod |
UBL-CR-449 (warning) |
[UBL-CR-449]-A UBL invoice should not include the PaymentMeans PaymentMandate PaymentReversalPeriod |
UBL-CR-450 (warning) |
[UBL-CR-450]-A UBL invoice should not include the PaymentMeans PaymentMandate Clause |
UBL-CR-451 (warning) |
[UBL-CR-451]-A UBL invoice should not include the PaymentMeans TradeFinancing |
UBL-CR-452 (warning) |
[UBL-CR-452]-A UBL invoice should not include the PaymentTerms ID |
UBL-CR-453 (warning) |
[UBL-CR-453]-A UBL invoice should not include the PaymentTerms PaymentMeansID |
UBL-CR-454 (warning) |
[UBL-CR-454]-A UBL invoice should not include the PaymentTerms PrepaidPaymentReferenceID |
UBL-CR-455 (warning) |
[UBL-CR-455]-A UBL invoice should not include the PaymentTerms ReferenceEventCode |
UBL-CR-456 (warning) |
[UBL-CR-456]-A UBL invoice should not include the PaymentTerms SettlementDiscountPercent |
UBL-CR-457 (warning) |
[UBL-CR-457]-A UBL invoice should not include the PaymentTerms PenaltySurchargePercent |
UBL-CR-458 (warning) |
[UBL-CR-458]-A UBL invoice should not include the PaymentTerms PaymentPercent |
UBL-CR-459 (warning) |
[UBL-CR-459]-A UBL invoice should not include the PaymentTerms Amount |
UBL-CR-460 (warning) |
[UBL-CR-460]-A UBL invoice should not include the PaymentTerms SettlementDiscountAmount |
UBL-CR-461 (warning) |
[UBL-CR-461]-A UBL invoice should not include the PaymentTerms PenaltyAmount |
UBL-CR-462 (warning) |
[UBL-CR-462]-A UBL invoice should not include the PaymentTerms PaymentTermsDetailsURI |
UBL-CR-463 (warning) |
[UBL-CR-463]-A UBL invoice should not include the PaymentTerms PaymentDueDate |
UBL-CR-464 (warning) |
[UBL-CR-464]-A UBL invoice should not include the PaymentTerms InstallmentDueDate |
UBL-CR-465 (warning) |
[UBL-CR-465]-A UBL invoice should not include the PaymentTerms InvoicingPartyReference |
UBL-CR-466 (warning) |
[UBL-CR-466]-A UBL invoice should not include the PaymentTerms SettlementPeriod |
UBL-CR-467 (warning) |
[UBL-CR-467]-A UBL invoice should not include the PaymentTerms PenaltyPeriod |
UBL-CR-468 (warning) |
[UBL-CR-468]-A UBL invoice should not include the PaymentTerms ExchangeRate |
UBL-CR-469 (warning) |
[UBL-CR-469]-A UBL invoice should not include the PaymentTerms ValidityPeriod |
UBL-CR-470 (warning) |
[UBL-CR-470]-A UBL invoice should not include the PrepaidPayment |
UBL-CR-471 (warning) |
[UBL-CR-471]-A UBL invoice should not include the AllowanceCharge ID |
UBL-CR-472 (warning) |
[UBL-CR-472]-A UBL invoice should not include the AllowanceCharge PrepaidIndicator |
UBL-CR-473 (warning) |
[UBL-CR-473]-A UBL invoice should not include the AllowanceCharge SequenceNumeric |
UBL-CR-474 (warning) |
[UBL-CR-474]-A UBL invoice should not include the AllowanceCharge AccountingCostCode |
UBL-CR-475 (warning) |
[UBL-CR-475]-A UBL invoice should not include the AllowanceCharge AccountingCost |
UBL-CR-476 (warning) |
[UBL-CR-476]-A UBL invoice should not include the AllowanceCharge PerUnitAmount |
UBL-CR-477 (warning) |
[UBL-CR-477]-A UBL invoice should not include the AllowanceCharge TaxCategory Name |
UBL-CR-478 (warning) |
[UBL-CR-478]-A UBL invoice should not include the AllowanceCharge TaxCategory BaseUnitMeasure |
UBL-CR-479 (warning) |
[UBL-CR-479]-A UBL invoice should not include the AllowanceCharge TaxCategory PerUnitAmount |
UBL-CR-480 (warning) |
[UBL-CR-480]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxExemptionReasonCode |
UBL-CR-481 (warning) |
[UBL-CR-481]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxExemptionReason |
UBL-CR-482 (warning) |
[UBL-CR-482]-A UBL invoice should not include the AllowanceCharge TaxCategory TierRange |
UBL-CR-483 (warning) |
[UBL-CR-483]-A UBL invoice should not include the AllowanceCharge TaxCategory TierRatePercent |
UBL-CR-484 (warning) |
[UBL-CR-484]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme Name |
UBL-CR-485 (warning) |
[UBL-CR-485]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme TaxTypeCode |
UBL-CR-486 (warning) |
[UBL-CR-486]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme CurrencyCode |
UBL-CR-487 (warning) |
[UBL-CR-487]-A UBL invoice should not include the AllowanceCharge TaxCategory TaxScheme JurisdiccionRegionAddress |
UBL-CR-488 (warning) |
[UBL-CR-488]-A UBL invoice should not include the AllowanceCharge TaxTotal |
UBL-CR-489 (warning) |
[UBL-CR-489]-A UBL invoice should not include the AllowanceCharge PaymentMeans |
UBL-CR-490 (warning) |
[UBL-CR-490]-A UBL invoice should not include the TaxExchangeRate |
UBL-CR-491 (warning) |
[UBL-CR-491]-A UBL invoice should not include the PricingExchangeRate |
UBL-CR-492 (warning) |
[UBL-CR-492]-A UBL invoice should not include the PaymentExchangeRate |
UBL-CR-493 (warning) |
[UBL-CR-493]-A UBL invoice should not include the PaymentAlternativeExchangeRate |
UBL-CR-494 (warning) |
[UBL-CR-494]-A UBL invoice should not include the TaxTotal RoundingAmount |
UBL-CR-495 (warning) |
[UBL-CR-495]-A UBL invoice should not include the TaxTotal TaxEvidenceIndicator |
UBL-CR-496 (warning) |
[UBL-CR-496]-A UBL invoice should not include the TaxTotal TaxIncludedIndicator |
UBL-CR-497 (warning) |
[UBL-CR-497]-A UBL invoice should not include the TaxTotal TaxSubtotal CalulationSequenceNumeric |
UBL-CR-498 (warning) |
[UBL-CR-498]-A UBL invoice should not include the TaxTotal TaxSubtotal TransactionCurrencyTaxAmount |
UBL-CR-499 (warning) |
[UBL-CR-499]-A UBL invoice should not include the TaxTotal TaxSubtotal Percent |
UBL-CR-500 (warning) |
[UBL-CR-500]-A UBL invoice should not include the TaxTotal TaxSubtotal BaseUnitMeasure |
UBL-CR-501 (warning) |
[UBL-CR-501]-A UBL invoice should not include the TaxTotal TaxSubtotal PerUnitAmount |
UBL-CR-502 (warning) |
[UBL-CR-502]-A UBL invoice should not include the TaxTotal TaxSubtotal TierRange |
UBL-CR-503 (warning) |
[UBL-CR-503]-A UBL invoice should not include the TaxTotal TaxSubtotal TierRatePercent |
UBL-CR-504 (warning) |
[UBL-CR-504]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory Name |
UBL-CR-505 (warning) |
[UBL-CR-505]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory BaseUnitMeasure |
UBL-CR-506 (warning) |
[UBL-CR-506]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory PerUnitAmount |
UBL-CR-507 (warning) |
[UBL-CR-507]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TierRange |
UBL-CR-508 (warning) |
[UBL-CR-508]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TierRatePercent |
UBL-CR-509 (warning) |
[UBL-CR-509]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme Name |
UBL-CR-510 (warning) |
[UBL-CR-510]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme TaxTypeCode |
UBL-CR-511 (warning) |
[UBL-CR-511]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme CurrencyCode |
UBL-CR-512 (warning) |
[UBL-CR-512]-A UBL invoice should not include the TaxTotal TaxSubtotal TaxCategory TaxScheme JurisdiccionRegionAddress |
UBL-CR-513 (warning) |
[UBL-CR-513]-A UBL invoice should not include the WithholdingTaxTotal |
UBL-CR-514 (warning) |
[UBL-CR-514]-A UBL invoice should not include the LegalMonetaryTotal PayableAlternativeAmount |
UBL-CR-515 (warning) |
[UBL-CR-515]-A UBL invoice should not include the InvoiceLine UUID |
UBL-CR-516 (warning) |
[UBL-CR-516]-A UBL invoice should not include the InvoiceLine TaxPointDate |
UBL-CR-517 (warning) |
[UBL-CR-517]-A UBL invoice should not include the InvoiceLine AccountingCostCode |
UBL-CR-518 (warning) |
[UBL-CR-518]-A UBL invoice should not include the InvoiceLine PaymentPurposeCode |
UBL-CR-519 (warning) |
[UBL-CR-519]-A UBL invoice should not include the InvoiceLine FreeOfChargeIndicator |
UBL-CR-520 (warning) |
[UBL-CR-520]-A UBL invoice should not include the InvoiceLine InvoicePeriod StartTime |
UBL-CR-521 (warning) |
[UBL-CR-521]-A UBL invoice should not include the InvoiceLine InvoicePeriod EndTime |
UBL-CR-522 (warning) |
[UBL-CR-522]-A UBL invoice should not include the InvoiceLine InvoicePeriod DurationMeasure |
UBL-CR-523 (warning) |
[UBL-CR-523]-A UBL invoice should not include the InvoiceLine InvoicePeriod DescriptionCode |
UBL-CR-524 (warning) |
[UBL-CR-524]-A UBL invoice should not include the InvoiceLine InvoicePeriod Description |
UBL-CR-525 (warning) |
[UBL-CR-525]-A UBL invoice should not include the InvoiceLine OrderLineReference SalesOrderLineID |
UBL-CR-526 (warning) |
[UBL-CR-526]-A UBL invoice should not include the InvoiceLine OrderLineReference UUID |
UBL-CR-527 (warning) |
[UBL-CR-527]-A UBL invoice should not include the InvoiceLine OrderLineReference LineStatusCode |
UBL-CR-528 (warning) |
[UBL-CR-528]-A UBL invoice should not include the InvoiceLine OrderLineReference OrderReference |
UBL-CR-529 (warning) |
[UBL-CR-529]-A UBL invoice should not include the InvoiceLine DespatchLineReference |
UBL-CR-530 (warning) |
[UBL-CR-530]-A UBL invoice should not include the InvoiceLine ReceiptLineReference |
UBL-CR-531 (warning) |
[UBL-CR-531]-A UBL invoice should not include the InvoiceLine BillingReference |
UBL-CR-532 (warning) |
[UBL-CR-532]-A UBL invoice should not include the InvoiceLine DocumentReference CopyIndicator |
UBL-CR-533 (warning) |
[UBL-CR-533]-A UBL invoice should not include the InvoiceLine DocumentReference UUID |
UBL-CR-534 (warning) |
[UBL-CR-534]-A UBL invoice should not include the InvoiceLine DocumentReference IssueDate |
UBL-CR-535 (warning) |
[UBL-CR-535]-A UBL invoice should not include the InvoiceLine DocumentReference IssueTime |
UBL-CR-537 (warning) |
[UBL-CR-537]-A UBL invoice should not include the InvoiceLine DocumentReference DocumentType |
UBL-CR-538 (warning) |
[UBL-CR-538]-A UBL invoice should not include the InvoiceLine DocumentReference Xpath |
UBL-CR-539 (warning) |
[UBL-CR-539]-A UBL invoice should not include the InvoiceLine DocumentReference LanguageID |
UBL-CR-540 (warning) |
[UBL-CR-540]-A UBL invoice should not include the InvoiceLine DocumentReference LocaleCode |
UBL-CR-541 (warning) |
[UBL-CR-541]-A UBL invoice should not include the InvoiceLine DocumentReference VersionID |
UBL-CR-542 (warning) |
[UBL-CR-542]-A UBL invoice should not include the InvoiceLine DocumentReference DocumentStatusCode |
UBL-CR-543 (warning) |
[UBL-CR-543]-A UBL invoice should not include the InvoiceLine DocumentReference DocumentDescription |
UBL-CR-544 (warning) |
[UBL-CR-544]-A UBL invoice should not include the InvoiceLine DocumentReference Attachment |
UBL-CR-545 (warning) |
[UBL-CR-545]-A UBL invoice should not include the InvoiceLine DocumentReference ValidityPeriod |
UBL-CR-546 (warning) |
[UBL-CR-546]-A UBL invoice should not include the InvoiceLine DocumentReference IssuerParty |
UBL-CR-547 (warning) |
[UBL-CR-547]-A UBL invoice should not include the InvoiceLine DocumentReference ResultOfVerification |
UBL-CR-548 (warning) |
[UBL-CR-548]-A UBL invoice should not include the InvoiceLine PricingReference |
UBL-CR-549 (warning) |
[UBL-CR-549]-A UBL invoice should not include the InvoiceLine OriginatorParty |
UBL-CR-550 (warning) |
[UBL-CR-550]-A UBL invoice should not include the InvoiceLine Delivery |
UBL-CR-551 (warning) |
[UBL-CR-551]-A UBL invoice should not include the InvoiceLine PaymentTerms |
UBL-CR-552 (warning) |
[UBL-CR-552]-A UBL invoice should not include the InvoiceLine AllowanceCharge ID |
UBL-CR-553 (warning) |
[UBL-CR-553]-A UBL invoice should not include the InvoiceLine AllowanceCharge PrepaidIndicator |
UBL-CR-554 (warning) |
[UBL-CR-554]-A UBL invoice should not include the InvoiceLine AllowanceCharge SequenceNumeric |
UBL-CR-555 (warning) |
[UBL-CR-555]-A UBL invoice should not include the InvoiceLine AllowanceCharge AccountingCostCode |
UBL-CR-556 (warning) |
[UBL-CR-556]-A UBL invoice should not include the InvoiceLine AllowanceCharge AccountingCost |
UBL-CR-557 (warning) |
[UBL-CR-557]-A UBL invoice should not include the InvoiceLine AllowanceCharge PerUnitAmount |
UBL-CR-558 (warning) |
[UBL-CR-558]-A UBL invoice should not include the InvoiceLine AllowanceCharge TaxCategory |
UBL-CR-559 (warning) |
[UBL-CR-559]-A UBL invoice should not include the InvoiceLine AllowanceCharge TaxTotal |
UBL-CR-560 (warning) |
[UBL-CR-560]-A UBL invoice should not include the InvoiceLine AllowanceCharge PaymentMeans |
UBL-CR-561 (warning) |
[UBL-CR-561]-A UBL invoice should not include the InvoiceLine TaxTotal |
UBL-CR-562 (warning) |
[UBL-CR-562]-A UBL invoice should not include the InvoiceLine WithholdingTaxTotal |
UBL-CR-563 (warning) |
[UBL-CR-563]-A UBL invoice should not include the InvoiceLine Item PackQuantity |
UBL-CR-564 (warning) |
[UBL-CR-564]-A UBL invoice should not include the InvoiceLine Item PackSizeNumeric |
UBL-CR-565 (warning) |
[UBL-CR-565]-A UBL invoice should not include the InvoiceLine Item CatalogueIndicator |
UBL-CR-566 (warning) |
[UBL-CR-566]-A UBL invoice should not include the InvoiceLine Item HazardousRiskIndicator |
UBL-CR-567 (warning) |
[UBL-CR-567]-A UBL invoice should not include the InvoiceLine Item AdditionalInformation |
UBL-CR-568 (warning) |
[UBL-CR-568]-A UBL invoice should not include the InvoiceLine Item Keyword |
UBL-CR-569 (warning) |
[UBL-CR-569]-A UBL invoice should not include the InvoiceLine Item BrandName |
UBL-CR-570 (warning) |
[UBL-CR-570]-A UBL invoice should not include the InvoiceLine Item ModelName |
UBL-CR-571 (warning) |
[UBL-CR-571]-A UBL invoice should not include the InvoiceLine Item BuyersItemIdentification ExtendedID |
UBL-CR-572 (warning) |
[UBL-CR-572]-A UBL invoice should not include the InvoiceLine Item BuyersItemIdentification BareCodeSymbologyID |
UBL-CR-573 (warning) |
[UBL-CR-573]-A UBL invoice should not include the InvoiceLine Item BuyersItemIdentification PhysicalAttribute |
UBL-CR-574 (warning) |
[UBL-CR-574]-A UBL invoice should not include the InvoiceLine Item BuyersItemIdentification MeasurementDimension |
UBL-CR-575 (warning) |
[UBL-CR-575]-A UBL invoice should not include the InvoiceLine Item BuyersItemIdentification IssuerParty |
UBL-CR-576 (warning) |
[UBL-CR-576]-A UBL invoice should not include the InvoiceLine Item SellersItemIdentification ExtendedID |
UBL-CR-577 (warning) |
[UBL-CR-577]-A UBL invoice should not include the InvoiceLine Item SellersItemIdentification BareCodeSymbologyID |
UBL-CR-578 (warning) |
[UBL-CR-578]-A UBL invoice should not include the InvoiceLine Item SellersItemIdentification PhysicalAttribute |
UBL-CR-579 (warning) |
[UBL-CR-579]-A UBL invoice should not include the InvoiceLine Item SellersItemIdentification MeasurementDimension |
UBL-CR-580 (warning) |
[UBL-CR-580]-A UBL invoice should not include the InvoiceLine Item SellersItemIdentification IssuerParty |
UBL-CR-581 (warning) |
[UBL-CR-581]-A UBL invoice should not include the InvoiceLine Item ManufacturersItemIdentification |
UBL-CR-582 (warning) |
[UBL-CR-582]-A UBL invoice should not include the InvoiceLine Item StandardItemIdentification ExtendedID |
UBL-CR-583 (warning) |
[UBL-CR-583]-A UBL invoice should not include the InvoiceLine Item StandardItemIdentification BareCodeSymbologyID |
UBL-CR-584 (warning) |
[UBL-CR-584]-A UBL invoice should not include the InvoiceLine Item StandardItemIdentification PhysicalAttribute |
UBL-CR-585 (warning) |
[UBL-CR-585]-A UBL invoice should not include the InvoiceLine Item StandardItemIdentification MeasurementDimension |
UBL-CR-586 (warning) |
[UBL-CR-586]-A UBL invoice should not include the InvoiceLine Item StandardItemIdentification IssuerParty |
UBL-CR-587 (warning) |
[UBL-CR-587]-A UBL invoice should not include the InvoiceLine Item CatalogueItemIdentification |
UBL-CR-588 (warning) |
[UBL-CR-588]-A UBL invoice should not include the InvoiceLine Item AdditionalItemIdentification |
UBL-CR-589 (warning) |
[UBL-CR-589]-A UBL invoice should not include the InvoiceLine Item CatalogueDocumentReference |
UBL-CR-590 (warning) |
[UBL-CR-590]-A UBL invoice should not include the InvoiceLine Item ItemSpecificationDocumentReference |
UBL-CR-591 (warning) |
[UBL-CR-591]-A UBL invoice should not include the InvoiceLine Item OriginCountry Name |
UBL-CR-592 (warning) |
[UBL-CR-592]-A UBL invoice should not include the InvoiceLine Item CommodityClassification NatureCode |
UBL-CR-593 (warning) |
[UBL-CR-593]-A UBL invoice should not include the InvoiceLine Item CommodityClassification CargoTypeCode |
UBL-CR-594 (warning) |
[UBL-CR-594]-A UBL invoice should not include the InvoiceLine Item CommodityClassification CommodityCode |
UBL-CR-595 (warning) |
[UBL-CR-595]-A UBL invoice should not include the InvoiceLine Item TransactionConditions |
UBL-CR-596 (warning) |
[UBL-CR-596]-A UBL invoice should not include the InvoiceLine Item HazardousItem |
UBL-CR-597 (warning) |
[UBL-CR-597]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory Name |
UBL-CR-598 (warning) |
[UBL-CR-598]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory BaseUnitMeasure |
UBL-CR-599 (warning) |
[UBL-CR-599]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory PerUnitAmount |
UBL-CR-600 (warning) |
[UBL-CR-600]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxExemptionReasonCode |
UBL-CR-601 (warning) |
[UBL-CR-601]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxExemptionReason |
UBL-CR-602 (warning) |
[UBL-CR-602]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TierRange |
UBL-CR-603 (warning) |
[UBL-CR-603]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TierRatePercent |
UBL-CR-604 (warning) |
[UBL-CR-604]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme Name |
UBL-CR-605 (warning) |
[UBL-CR-605]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme TaxTypeCode |
UBL-CR-606 (warning) |
[UBL-CR-606]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme CurrencyCode |
UBL-CR-607 (warning) |
[UBL-CR-607]-A UBL invoice should not include the InvoiceLine Item ClassifiedTaxCategory TaxScheme JurisdiccionRegionAddress |
UBL-CR-608 (warning) |
[UBL-CR-608]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty ID |
UBL-CR-609 (warning) |
[UBL-CR-609]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty NameCode |
UBL-CR-610 (warning) |
[UBL-CR-610]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty TestMethod |
UBL-CR-611 (warning) |
[UBL-CR-611]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty ValueQuantity |
UBL-CR-612 (warning) |
[UBL-CR-612]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty ValueQualifier |
UBL-CR-613 (warning) |
[UBL-CR-613]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty ImportanceCode |
UBL-CR-614 (warning) |
[UBL-CR-614]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty ListValue |
UBL-CR-615 (warning) |
[UBL-CR-615]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty UsabilityPeriod |
UBL-CR-616 (warning) |
[UBL-CR-616]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty ItemPropertyGroup |
UBL-CR-617 (warning) |
[UBL-CR-617]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty RangeDimension |
UBL-CR-618 (warning) |
[UBL-CR-618]-A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty ItemPropertyRange |
UBL-CR-619 (warning) |
[UBL-CR-619]-A UBL invoice should not include the InvoiceLine Item ManufacturerParty |
UBL-CR-620 (warning) |
[UBL-CR-620]-A UBL invoice should not include the InvoiceLine Item InformationContentProviderParty |
UBL-CR-621 (warning) |
[UBL-CR-621]-A UBL invoice should not include the InvoiceLine Item OriginAddress |
UBL-CR-622 (warning) |
[UBL-CR-622]-A UBL invoice should not include the InvoiceLine Item ItemInstance |
UBL-CR-623 (warning) |
[UBL-CR-623]-A UBL invoice should not include the InvoiceLine Item Certificate |
UBL-CR-624 (warning) |
[UBL-CR-624]-A UBL invoice should not include the InvoiceLine Item Dimension |
UBL-CR-625 (warning) |
[UBL-CR-625]-A UBL invoice should not include the InvoiceLine Item Price PriceChangeReason |
UBL-CR-626 (warning) |
[UBL-CR-626]-A UBL invoice should not include the InvoiceLine Item Price PriceTypeCode |
UBL-CR-627 (warning) |
[UBL-CR-627]-A UBL invoice should not include the InvoiceLine Item Price PriceType |
UBL-CR-628 (warning) |
[UBL-CR-628]-A UBL invoice should not include the InvoiceLine Item Price OrderableUnitFactorRate |
UBL-CR-629 (warning) |
[UBL-CR-629]-A UBL invoice should not include the InvoiceLine Item Price ValidityPeriod |
UBL-CR-630 (warning) |
[UBL-CR-630]-A UBL invoice should not include the InvoiceLine Item Price PriceList |
UBL-CR-631 (warning) |
[UBL-CR-631]-A UBL invoice should not include the InvoiceLine Item Price OrderableUnitFactorRate |
UBL-CR-632 (warning) |
[UBL-CR-632]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge ID |
UBL-CR-633 (warning) |
[UBL-CR-633]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge AllowanceChargeReasonCode |
UBL-CR-634 (warning) |
[UBL-CR-634]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge AllowanceChargeReason |
UBL-CR-635 (warning) |
[UBL-CR-635]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge MultiplierFactorNumeric |
UBL-CR-636 (warning) |
[UBL-CR-636]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge PrepaidIndicator |
UBL-CR-637 (warning) |
[UBL-CR-637]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge SequenceNumeric |
UBL-CR-638 (warning) |
[UBL-CR-638]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge AccountingCostCode |
UBL-CR-639 (warning) |
[UBL-CR-639]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge AccountingCost |
UBL-CR-640 (warning) |
[UBL-CR-640]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge PerUnitAmount |
UBL-CR-641 (warning) |
[UBL-CR-641]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge TaxCategory |
UBL-CR-642 (warning) |
[UBL-CR-642]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge TaxTotal |
UBL-CR-643 (warning) |
[UBL-CR-643]-A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge PaymentMeans |
UBL-CR-644 (warning) |
[UBL-CR-644]-A UBL invoice should not include the InvoiceLine Item Price PricingExchangeRate |
UBL-CR-645 (warning) |
[UBL-CR-645]-A UBL invoice should not include the InvoiceLine DeliveryTerms |
UBL-CR-646 (warning) |
[UBL-CR-646]-A UBL invoice should not include the InvoiceLine SubInvoiceLine |
UBL-CR-647 (warning) |
[UBL-CR-647]-A UBL invoice should not include the InvoiceLine ItemPriceExtension |
UBL-CR-648 (warning) |
[UBL-CR-648]-A UBL invoice should not include the CustomizationID scheme identifier |
UBL-CR-649 (warning) |
[UBL-CR-649]-A UBL invoice should not include the ProfileID scheme identifier |
UBL-CR-650 (warning) |
[UBL-CR-650]-A UBL invoice shall not include the Invoice ID scheme identifier |
UBL-CR-651 (warning) |
[UBL-CR-651]-A UBL invoice should not include the SalesOrderID scheme identifier |
UBL-CR-652 (warning) |
[UBL-CR-652]-A UBL invoice should not include the PartyTaxScheme CompanyID scheme identifier |
UBL-CR-653 (warning) |
[UBL-CR-653]-A UBL invoice should not include the PaymentID scheme identifier |
UBL-CR-654 (warning) |
[UBL-CR-654]-A UBL invoice should not include the PayeeFinancialAccount scheme identifier |
UBL-CR-655 (warning) |
[UBL-CR-655]-A UBL invoice shall not include the FinancialInstitutionBranch ID scheme identifier |
UBL-CR-656 (warning) |
[UBL-CR-656]-A UBL invoice should not include the InvoiceTypeCode listID |
UBL-CR-657 (warning) |
[UBL-CR-657]-A UBL invoice should not include the DocumentCurrencyCode listID |
UBL-CR-658 (warning) |
[UBL-CR-658]-A UBL invoice should not include the TaxCurrencyCode listID |
UBL-CR-659 (warning) |
[UBL-CR-659]-A UBL invoice shall not include the AdditionalDocumentReference DocumentTypeCode listID |
UBL-CR-660 (warning) |
[UBL-CR-660]-A UBL invoice should not include the Country Identification code listID |
UBL-CR-661 (warning) |
[UBL-CR-661]-A UBL invoice should not include the PaymentMeansCode listID |
UBL-CR-662 (warning) |
[UBL-CR-662]-A UBL invoice should not include the AllowanceChargeReasonCode listID |
UBL-CR-663 (warning) |
[UBL-CR-663]-A UBL invoice should not include the unitCodeListID |
UBL-CR-664 (warning) |
[UBL-CR-664]-A UBL invoice should not include the FinancialInstitutionBranch FinancialInstitution |
UBL-CR-665 (warning) |
[UBL-CR-665]-A UBL invoice should not include the AdditonalDocumentReference ID schemeID unless the ID equals '130' |
UBL-CR-666 (warning) |
[UBL-CR-666]-A UBL invoice should not include the AdditonalDocumentReference referring to an Invoice Object Identifier should not include an Attachment |
UBL-CR-667 (warning) |
[UBL-CR-667]-A UBL invoice should not include a Buyer Item Identification schemeID |
UBL-CR-668 (warning) |
[UBL-CR-668]-A UBL invoice should not include a Sellers Item Identification schemeID |
UBL-CR-669 (warning) |
[UBL-CR-669]-A UBL invoice should not include a Price Allowance Reason Code |
UBL-CR-670 (warning) |
[UBL-CR-670]-A UBL invoice should not include a Price Allowance Reason |
UBL-CR-671 (warning) |
[UBL-CR-671]-A UBL invoice should not include a Price Allowance Multiplier Factor |
UBL-CR-672 (warning) |
[UBL-CR-672]-A UBL credit note should not include the CreditNoteTypeCode listID |
UBL-CR-673 (warning) |
[UBL-CR-673]-A UBL invoice shall not include an AdditionalDocumentReference simultaneously referring an Invoice Object Identifier and an Document Description |
UBL-CR-674 (warning) |
[UBL-CR-674]-A UBL invoice should not include the PrimaryAccountNumber schemeID |
UBL-CR-675 (warning) |
[UBL-CR-675]-A UBL invoice should not include the NetworkID schemeID |
UBL-CR-676 (warning) |
[UBL-CR-676]-A UBL invoice should not include the PaymentMandate/ID schemeID |
UBL-CR-677 (warning) |
[UBL-CR-677]-A UBL invoice should not include the PayerFinancialAccount/ID schemeID |
UBL-CR-678 (warning) |
[UBL-CR-678]-A UBL invoice should not include the TaxCategory/ID schemeID |
UBL-CR-679 (warning) |
[UBL-CR-679]-A UBL invoice should not include the ClassifiedTaxCategory/ID schemeID |
UBL-CR-680 (warning) |
[UBL-CR-680]-A UBL invoice should not include the PaymentMeans/PayerFinancialAccount |
UBL-DT-01 (fatal) |
[UBL-DT-01]-Amounts shall be decimal up to two fraction digits |
UBL-DT-06 (fatal) |
[UBL-DT-06]-Binary object elements shall contain the mime code attribute |
UBL-DT-07 (fatal) |
[UBL-DT-07]-Binary object elements shall contain the file name attribute |
UBL-DT-08 (warning) |
[UBL-DT-08]-Scheme name attribute should not be present |
UBL-DT-09 (warning) |
[UBL-DT-09]-Scheme agency name attribute should not be present |
UBL-DT-10 (warning) |
[UBL-DT-10]-Scheme data uri attribute should not be present |
UBL-DT-11 (warning) |
[UBL-DT-11]-Scheme uri attribute should not be present |
UBL-DT-12 (warning) |
[UBL-DT-12]-Format attribute should not be present |
UBL-DT-13 (warning) |
[UBL-DT-13]-Unit code list identifier attribute should not be present |
UBL-DT-14 (warning) |
[UBL-DT-14]-Unit code list agency identifier attribute should not be present |
UBL-DT-15 (warning) |
[UBL-DT-15]-Unit code list agency name attribute should not be present |
UBL-DT-16 (warning) |
[UBL-DT-16]-List agency name attribute should not be present |
UBL-DT-17 (warning) |
[UBL-DT-17]-List name attribute should not be present |
UBL-DT-18 (warning) |
[UBL-DT-18]-Name attribute should not be present |
UBL-DT-19 (warning) |
[UBL-DT-19]-Language identifier attribute should not be present |
UBL-DT-20 (warning) |
[UBL-DT-20]-List uri attribute should not be present |
UBL-DT-21 (warning) |
[UBL-DT-21]-List scheme uri attribute should not be present |
UBL-DT-22 (warning) |
[UBL-DT-22]-Language local identifier attribute should not be present |
UBL-DT-23 (warning) |
[UBL-DT-23]-Uri attribute should not be present |
UBL-DT-24 (warning) |
[UBL-DT-24]-Currency code list version id should not be present |
UBL-DT-25 (warning) |
[UBL-DT-25]-CharacterSetCode attribute should not be present |
UBL-DT-26 (warning) |
[UBL-DT-26]-EncodingCode attribute should not be present |
UBL-DT-27 (warning) |
[UBL-DT-27]-Scheme Agency ID attribute should not be present |
UBL-DT-28 (warning) |
[UBL-DT-28]-List Agency ID attribute should not be present |
UBL-SR-01 (warning) |
[UBL-SR-01]-Contract identifier shall occur maximum once. |
UBL-SR-02 (warning) |
[UBL-SR-02]-Receive advice identifier shall occur maximum once |
UBL-SR-03 (warning) |
[UBL-SR-03]-Despatch advice identifier shall occur maximum once |
UBL-SR-04 (warning) |
[UBL-SR-04]-Invoice object identifier shall occur maximum once |
UBL-SR-05 (warning) |
[UBL-SR-05]-Payment terms shall occur maximum once |
UBL-SR-06 (warning) |
[UBL-SR-06]-Preceding invoice reference shall occur maximum once |
UBL-SR-07 (warning) |
[UBL-SR-07]-If there is a preceding invoice reference, the preceding invoice number shall be present |
UBL-SR-08 (warning) |
[UBL-SR-08]-Invoice period shall occur maximum once |
UBL-SR-09 (warning) |
[UBL-SR-09]-Seller name shall occur maximum once |
UBL-SR-10 (warning) |
[UBL-SR-10]-Seller trader name shall occur maximum once |
UBL-SR-11 (warning) |
[UBL-SR-11]-Seller legal registration identifier shall occur maximum once |
UBL-SR-12 (warning) |
[UBL-SR-12]-Seller VAT identifier shall occur maximum once |
UBL-SR-13 (warning) |
[UBL-SR-13]-Seller tax registration shall occur maximum once |
UBL-SR-14 (warning) |
[UBL-SR-14]-Seller additional legal information shall occur maximum once |
UBL-SR-15 (warning) |
[UBL-SR-15]-Buyer name shall occur maximum once |
UBL-SR-16 (warning) |
[UBL-SR-16]-Buyer identifier shall occur maximum once |
UBL-SR-17 (warning) |
[UBL-SR-17]-Buyer legal registration identifier shall occur maximum once |
UBL-SR-18 (warning) |
[UBL-SR-18]-Buyer VAT identifier shall occur maximum once |
UBL-SR-19 (warning) |
[UBL-SR-19]-Payee name shall occur maximum once, if the Payee is different from the Seller |
UBL-SR-20 (warning) |
[UBL-SR-20]-Payee identifier shall occur maximum once, if the Payee is different from the Seller |
UBL-SR-21 (warning) |
[UBL-SR-21]-Payee legal registration identifier shall occur maximum once, if the Payee is different from the Seller |
UBL-SR-22 (warning) |
[UBL-SR-22]-Seller tax representative name shall occur maximum once, if the Seller has a tax representative |
UBL-SR-23 (warning) |
[UBL-SR-23]-Seller tax representative VAT identifier shall occur maximum once, if the Seller has a tax representative |
UBL-SR-24 (warning) |
[UBL-SR-24]-Deliver to information shall occur maximum once |
UBL-SR-25 (warning) |
[UBL-SR-25]-Deliver to party name shall occur maximum once |
UBL-SR-26 (warning) |
[UBL-SR-26]-Payment reference shall occur maximum once |
UBL-SR-27 (warning) |
[UBL-SR-27]-Payment means text shall occur maximum once |
UBL-SR-28 (warning) |
[UBL-SR-28]-Mandate reference identifier shall occur maximum once |
UBL-SR-29 (warning) |
[UBL-SR-29]-Bank creditor reference shall occur maximum once |
UBL-SR-30 (warning) |
[UBL-SR-30]-Document level allowance reason shall occur maximum once |
UBL-SR-31 (warning) |
[UBL-SR-31]-Document level charge reason shall occur maximum once |
UBL-SR-32 (warning) |
[UBL-SR-32]-VAT exemption reason text shall occur maximum once |
UBL-SR-33 (warning) |
[UBL-SR-33]-Supporting document description shall occur maximum once |
UBL-SR-34 (warning) |
[UBL-SR-34]-Invoice line note shall occur maximum once |
UBL-SR-35 (warning) |
[UBL-SR-35]-Referenced purchase order line identifier shall occur maximum once |
UBL-SR-36 (warning) |
[UBL-SR-36]-Invoice line period shall occur maximum once |
UBL-SR-37 (warning) |
[UBL-SR-37]-Item price discount shall occur maximum once |
UBL-SR-38 (warning) |
[UBL-SR-38]-Invoiced item VAT exemption reason text shall occur maximum once |
UBL-SR-39 (warning) |
[UBL-SR-39]-Project reference shall occur maximum once. |
UBL-SR-40 (warning) |
[UBL-SR-40]-Buyer trade name shall occur maximum once |
UBL-SR-42 (warning) |
[UBL-SR-42]-Party tax scheme shall occur maximum twice in accounting supplier party |
UBL-SR-43 (warning) |
[UBL-SR-43]-Scheme identifier shall only be used for invoiced object (document type code with value 130) |
UBL-SR-44 (warning) |
[UBL-SR-44]-Payment ID shall occur maximum once |
UBL-SR-45 (warning) |
[UBL-SR-45]-Due Date shall occur maximum once |
UBL-SR-46 (warning) |
[UBL-SR-46]-Payment means text shall occur maximum once |
UBL-SR-47 (warning) |
[UBL-SR-47]-When there are more than one payment means code, they shall be equal |
UBL-SR-48 (warning) |
[UBL-SR-48]-Invoice lines shall have one and only one classified tax category. |
UBL-SR-49 (warning) |
[UBL-SR-49]-Value tax point date shall occur maximum once |
UBL-SR-50 (warning) |
[UBL-SR-50]-Item description shall occur maximum once |