The essentials

The XML sample contains training data and is not intended to be sent or booked. A valid structure does not confirm that the business transaction is real or that its participants are registered.

Where can you find the complete XML e-invoice sample?

Open or save the training UBL invoice. The file contains the whole document, not just the excerpts on this page. Both the note in the invoice and the comments indicate its training purpose.

The sample is not a real invoice: do not send it, pay it or book it. The names, identifiers and references are illustrative; their presence does not confirm registration in Peppol or the existence of a business transaction. For your own invoice you must use verified data and the correct tax regime.

The model contains three hours of service at 100 euros each excluding tax, one category with an illustrative rate of 23 % and payment in cash. The tax base is 300 euros, the tax 69 euros and the amount due 369 euros. It contains no bank account and does not deal with a foreign currency, advance payments or exemptions.

What do the header and the profile identifiers mean?

The root Invoice identifies a UBL invoice. Currency data and dates are written into their own fields; CustomizationID identifies the rules and ProfileID the business process. You will find their meaning and order in the official Invoice structure.

An excerpt from the same sample:

<cbc:ID>FINPOST-UCENIE-001</cbc:ID>
<cbc:IssueDate>2026-10-01</cbc:IssueDate>
<cbc:DueDate>2026-10-15</cbc:DueDate>
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>

The excerpt is not a valid standalone XML document: the prefix cbc is declared in the complete file. Do not confuse the invoice number, the issue date and the due date. The sample also has a separate date of the taxable supply, because it differs from the issue date.

Where do the Peppol ID, IČO and IČ DPH belong?

For both the supplier and the customer, distinguish the electronic address, the legal identifier and the tax identification. These are different pieces of data, even though some of their digits may be similar.

Data in the sample Meaning
EndpointID with the scheme 0245 Electronic address for the Slovak tax identification number (DIČ)
PartyLegalEntity/CompanyID Registration identifier of the legal entity (IČO)
PartyTaxScheme/CompanyID with VAT Identifier for VAT purposes (IČ DPH)
BuyerReference Buyer's reference for its own workflow
PaymentID Payment reference

The prefix 0245: is not inserted into the value of the Slovak EndpointID, nor is SK added automatically; the scheme is in the attribute. For your own document, verify the actual identifier and the recipient's availability following Peppol ID. Do not use the sample numbers from this file to look up a partner.

The line has the quantity 3, the unit hour HUR, the price 100.00 and the net amount 300.00. The tax category is assigned to the item; the VAT breakdown groups the relevant tax base and tax. LegalMonetaryTotal contains the document's resulting amounts.

<cbc:TaxExclusiveAmount currencyID="EUR">300.00</cbc:TaxExclusiveAmount>
<cbc:TaxInclusiveAmount currencyID="EUR">369.00</cbc:TaxInclusiveAmount>
<cbc:PayableAmount currencyID="EUR">369.00</cbc:PayableAmount>

In this simple case there are no discounts, advance payments or rounding. That is why the amount including tax is the same as the amount due. In a more complex document, this assumption does not automatically apply. Examples of calculations and rules are explained in e-invoice validation.

Which checks did the sample pass?

The exact downloadable file was checked against the UBL 2.1 XSD, the CEN EN 16931 rules and Peppol BIS Billing. The Peppol release used is 3.0.21 (May 2026); CEN 1.3.16. The technical check report contains the results, the date, the versions and the SHA-256 of the file.

We compared the release with the official release notes. The Slovak transposition table, version 1.11, is assessed separately; it is not an automatically executable technical check. The relevant fields in the sample were reviewed, but the training identities have no confirmed registration and this is not an assessment of a real tax case.

We therefore do not describe the result of the technical checks as delivery, the issue of a valid commercial invoice or general legal approval. The sample remains unsent.

How should you use the sample when preparing your software?

Open it in a test environment and compare the names of the data in your software with the XML. Check the amounts, the partners and the references; then try out how a technical error is displayed when you change one piece of data. Do not include the test file in your live records.

For production, prepare your own verified scenarios. The standards are explained in EN 16931, UBL and BIS Billing; connecting a system with a service is covered by API integration.

Materials you can come back to

Verified sources

We rely on official materials. You will find the original documents under the links below. When the rules change, we update this guide too.

Content verified 1/10/2026. In a specific tax case, the applicable wording of the law and the circumstances of the supply are decisive.