Īsā's answer: use a form, not an XML editor
Nē, mazam utsättäm nav nejat raksitt XML kode, lai sentutu Peppol rēķinu. Peppol rēķins ir strukturēts datu fails, does it comply For Peppol BIS Billing 3.0 specification – tas sämää rēķinu, kura lauki ir mašīnlasāmi (dators tos saprot automatički, maštām nav nāmārceļl dati ar roku). Jūs aizpildāt parastu rēķina formu savā e-rēķinu vai kontaktijas programmatūrā: klienta nakams, summas, PVN, apmaksas terim. Programmatura pati no šims datum prepares an XML file and nosūta to Peppol network. 17.08.2026. became par obligātu the new BIS Billing 3.0 version, so it's worth checking whether your operators use the latest validation code.
Jūsu darbs aprobežojas ar parastu rēķina datu īvādīštu. And customers or operators say that the account "does not pass validation", it does not mean that you have to work with the XML code. This means, ka kaidas lauks programmatūrā ir neaizpildīts vai nepareizs, un jums to be checked in form.
What is Peppol and what is it not?
Peppol ir droš data exchange tīkls, pa kuru strukturēti rēķini severjas no vienas sistemas uz otru. Peppol pats nav software vai forma, ko jūs aizpildāt – tas ir kā pasta sūpis rēķiniem. Saturam, whether moved in this network, must comply Peppol BIS Billing 3.0 rules, . This structure is called UBL (Universal Business Language), and it is the most commonly used XML format. XML (Extensible Markup Language) is a simple mašīnlasāms file format, kuru datori aka datu uttätsäi - sekke to parasti gässät sägät.
Peppol rēķins nav tas pats, kas pa e-pastu zapatts PDF rēķins, un nav tas pats, kas PVN deklarācijas iesnežina tažu administratācijai. Tie ir trēs sīdādī sābībā: rēķina sīpa klientam, datu mašīnlasāmība un datu mašīnlasāmība un datu įpūte sātut. It often works together, but it's not mandatory.
Ko prokerat pēns rēķina in creation?
Before atverat rēķina formu, check šos punktus:
- Client gatavība Peppol nettām: vai pircējs gässä sägät sägät Peppol rēķinus un kaiks ir sya täkäsais Peppol ID, tas ir, adrese, uz kuru rēķins jāsūta.
- Buyer's reference or order number: according to the existing ones Peppol rules, the invoice must be either a purchase or a purchase number. Bez tā rēķina validationācija neizdosies.
- Client specific instructions: Most of the clients or public authorities want their own inner home, not your invented one. Šo numuru klivanjiet klientam directly, not nevis izmjemte pats.
Create un nosūtiet Peppol rēķinu piecos soļos
- Choose a customer and shipping method: norādiet programmatūrā, ka rēķins tiks sādāts pa Peppol kanuu, nevis pa e-pastu.
- Add the pārdevēja and pirceja in the identifier: your un klienta Peppol ID parasti aizpildās automatically no klienta kartes.
- Ievadiet rēķina in the chest, PVN un apmaksas condition: preces vai services, cenas, PVN likmi un apmaksas temudu.
- Add the buyer's reference or order number: This field is optional.
- Start validation and nosūtiet: the software automatically checks the account before sending and notifies you if it is missing.
Kuri lauki ir importanti, niéka teimt no privka acu uzmetiena?
Imagine 1200 euros rēķinu Latvijas klientam. Summa un PVN is correct, however, rēķins tik un tā var tikt ajarts, and:
- rēķina numurus nav unikāls un atkārto prevetēju rēķinu;
- currency code ir nepareizs or missing;
- PVN category un likme nesakrıt (eg 0% PVN bez pamatojuma);
- pārdevēja vai pirceja identificatori ir ħāmāini įpārītāts;
- payment data, such as IBAN or payment reference, is missing or incorrect;
- The buyer's reference or the number of the order is empty.
The last point is the most common mistake. According to Art Peppol rules šis lauks ir obligāts, un tā kākās ir fatalāla validationācijas āgātā, ne ieteikums, ko var ignorēt.
PDF, pielikumi un noraidīti rēķini
PDF rēķins ir lasāms sādām, bet tas nav Peppol rēķins. According to Art Estonian Ministry of Finance sklidojumu, e-rēķins ir mašīnlasāms fails, kura based on the recipient nav jāievada dati ar roku. Images or PDFs do not meet the requirements. Daudzas softwares prídas strukturētam rēķinam PDF kopi, lai manzēz pūzīga ātī reķīsit rēķina saturu, bet tā ir additional option, nevis azītāzējs.
Ja rēķins nesasrīds klētu, tā ir sāpis kĭume – parasti nepareizs Peppol ID vai connection problem. Ja rēķins reaches the client, but his system to noraida, tā ir biznesa kĭme, most often pirceja hāvēses kūtava vai nepareizu rekvizītu dāl. Check first exactly at this point before questioning the operation of the software.
Is ir spekke Igaunijā un Lattvija tagad un kas expectums?
Igaunijā bookkeeping subject, kas ir registrajies e-uzņēmumu registrar kā e-rēķinu saimeĹĽs, no 2025. gada var projatt pārdevējam e-invoice, and puses nav vienojušas odnaži. Eestionia atląg ħawt gan ġiġi, gan Eiropas, tas ir, Peppol, standartu, un ministrija companies recommend exactly the latter, because tas ir vaġġi ġġġġġi vġa Eiropas Sġiġi.
In Latvia, requirements are stricter and terms are clearer. No. 01.01.2025. strukturēts e-rēķins ir obligāts G2G, B2G un G2B éstos, un no 01.01.2026. šo pašu jomu rēķinu dati jānodod arī VID. B2B transaction datu iesnejnega VID ir väläätä til 31.12.2027., bet no 01.01.2028. The use of strukturēta e-rēķina un tā datu iesneštīga VID becomes obligatory also in Latvijas savstarpējos esdoso.
At the level of the European Union, the next important deadline is 01.07.2030., kad ViDA reform within e-rēķins cross-border B2B transaction becomes par noklusēto settlement type. And you already send a Peppol account today, you'll have to wait until it's time for someone to quote you.
FAQ
Does a small business need to write XML to send a Peppol invoice?
No, a small business does not need to write XML. You fill out a standard invoice form in your software and the software will create the XML file itself and send it via the Peppol network.
What is Peppol?
Peppol is a secure data exchange network for invoices. It is not software, but rather a postal service that delivers structured invoices.
What are the most common errors when sending a Peppol invoice?
The most common error is missing the buyer reference or order number. This is a required field and its absence will result in a validation error.
What is the difference between a Peppol invoice and a PDF invoice?
A PDF invoice is human-readable, but not machine-readable. A Peppol invoice is a structured XML file that computers can automatically process.