B2G · 2025Live now
Invoices to state and municipal bodies
Structured e-invoices (EN 16931) have been mandatory for public bodies since 1 January 2025.
Peppol e-invoicesFree on every plan
An e-invoice thatgets through EIS.
A structured e-invoice has been mandatory for invoices to public bodies since 2025. It becomes mandatory B2B from 2028. We write the XML, you press one button.
Invoice RKR-2026-0042UBL 2.1
RecipientRiga City Council
Endpoint (schemeID 0218)LV40003123456
Amount1 280,00 EUR
Export Peppol XML
EN 16931 and BIS 3.0 compatible. Ready for EIS.
- Peppol BIS 3.0
- EN 16931
- UBL 2.1
- EIS compatible
Who Peppol is mandatory for, and when.
B2B · 2028Coming
Between businesses
The Accounting Law provides that structured e-invoices become mandatory in B2B transactions from 1 January 2028.
You see an invoice. EIS sees this.
A Peppol BIS 3.0 file is structured XML, not a PDF. Here is a fragment of a real invoice the system generates, annotated.
invoice-RKR-2026-0042.xmlBIS 3.0 OK
01<?xml version="1.0" encoding="UTF-8"?>02<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">03<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>04<cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>05<cbc:ID>RKR-2026-0042</cbc:ID>06<cbc:IssueDate>2026-05-15</cbc:IssueDate>07<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>08<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>10<cac:AccountingSupplierParty>11<cac:Party>12<cbc:EndpointID schemeID="0218">LV40003123456</cbc:EndpointID>13<cac:PartyTaxScheme>14<cbc:CompanyID>LV40003123456</cbc:CompanyID>15<cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>16</cac:PartyTaxScheme>17</cac:Party>18</cac:AccountingSupplierParty>20<!-- AccountingCustomerParty, InvoiceLine, TaxTotal, LegalMonetaryTotal -->21</Invoice>
The UBL 2.1 root element. Peppol BIS 3.0 uses OASIS UBL.
The conformance profile: EN 16931 plus Peppol BIS Billing 3.0. This is the line that decides whether EIS accepts the invoice.
BIS Billing profile 01:1.0, the standard invoice exchange.
Code 380 = commercial invoice (the UNCL 1001 list).
schemeID=0218 is a Latvian registration number. This is how EIS finds the recipient.
The remaining blocks are filled in automatically from your invoice data, with no manual XML editing.
Identifiers, registration numbers and amounts are taken from your invoice automatically. You never have to look at the XML.
Three steps to a Peppol invoice.
I
Create the invoice
Use the normal interface or dictate it. Customer, amount, VAT. Exactly as usual.
II
Click “Export Peppol XML”
The system builds a UBL 2.1 file that conforms to EN 16931 and BIS 3.0. No samples, no configuration.
III
Submit it via eAddress or EIS, or send it to the customer
Download the XML and upload it to your eAddress on Latvija.gov.lv, submit it in the Electronic Procurement System, or pass it to your partner through an agreed channel.
Included in the free plan.
Creating, validating and downloading Peppol XML costs nothing. A format the law requires is not something we charge for. No hidden fees and no network access charge.
Peppol BIS 3.0 XML export
An EN 16931 conformant UBL 2.1 file in one click. Included in every plan, the free one included.
Free XML validator
Check any Peppol XML file before you submit it. Available without registering.
Voice commands in Latvian
Included in the Business plan. Dictate an invoice while driving or in a meeting.
Unlimited invoices
No monthly cap and no volume surcharge. From the Solo plan (€9.99/month).
Cancel at any time
A monthly subscription carries no penalty. You can export your data at any time.
Cancel the subscription at any time, with no penaltyExport your data whenever you wantFree migration help from your current software
Answers to your question.
What are Peppol and EN 16931?
Peppol (Pan-European Public Procurement OnLine) is an international network for exchanging electronic documents, built to simplify the exchange of invoices and other documents between businesses and public bodies across Europe.
EN 16931 is the European standard for electronic invoices, setting out common data elements and a format. In Latvia this standard is mandatory for every e-invoice submitted to a state or municipal body.
The B2G and B2B e-invoicing deadlines
B2G (business to government): structured e-invoices to state and municipal bodies have been mandatory since 1 January 2025. If your business bids for public contracts or supplies the public sector, compliance is needed today.
B2B (business to business): structured e-invoices between businesses become mandatory from 2028. That means every Latvian business will have to be able to send and receive e-invoices in the EN 16931 format.
Why erekini.eu
- Voice commands in Latvian: dictate the invoice and the system builds it (Business plan)
- Automatic Peppol XML generation: one click, a finished UBL 2.1 file
- A free Peppol validator: check any XML file without registering
- Peppol XML at no cost: included in every plan, the free account included
VID and EIS requirements
The State Revenue Service (VID) oversees e-invoicing compliance in Latvia. An incorrectly formed or non-conformant e-invoice can lead to rejection in the Electronic Procurement System (EIS), to late payment, or potentially to penalties. erekini.eu generates Peppol BIS 3.0 conformant XML files that can be submitted straight to EIS with no further conversion.
Everything about e-invoicing, in one place.
Practical guides to Peppol, VID and structured e-invoices in Latvia. Without the legal jargon.
Rules and deadlines
Getting started
Technical and troubleshooting
Cost and choosing
Your first Peppol invoice tonight.
Free, and no card. Peppol XML is in the free plan already.