Latvia e-Invoice (Peppol BIS Billing 3.0)
Structured e-invoicing for Latvia over the Peppol network — UBL 2.1, EN 16931, BYOK Access Point delivery
Connect Odoo to Latvia's structured e-invoicing regime. Under the Latvian Accounting Law, structured e-invoicing has been mandatory B2G since 1 January 2025, with e-invoice data reporting to the State Revenue Service (SRS) from 1 January 2026, and becomes mandatory B2B from 1 January 2028 (postponed by the June 2025 amendments), exchanged over the Peppol network using Peppol BIS Billing 3.0 (the European standard EN 16931). Your customer invoices and credit notes are transformed into the Peppol UBL 2.1 document, validated against the Latvian business rules, and delivered to the recipient through your own Peppol Access Point.
Compatible with Odoo 18 and Odoo 19.
What it does
Peppol BIS Billing 3.0 UBL 2.1
Generate the EN 16931-compliant Invoice and CreditNote UBL 2.1 XML, built with the significant Peppol element ordering and the Latvian electronic-address schemes 9939 (LV:VAT) and 0218 (LV:RegEnt), in EUR.
Peppol Access Point delivery
Participant (SMP) lookup, document send and message-status polling over a configurable AP gateway, with editable sandbox / production base URLs and automatic retry / backoff inherited from the engine transport.
Real Latvian VAT (PVN) validation
The published check-digit algorithm for legal persons (weight vector 9,1,4,8,3,10,2,5,7,6) and the personal-code modulus for natural persons, applied on the company and partner records.
UNCL5305 VAT categories
21% standard (S), 12% / 5% reduced (AA), zero (Z), exempt (E), reverse charge (AE) and out of scope (O), emitted per line and per tax subtotal with the exemption-reason code when needed.
EN 16931 + Latvian business-rule validation
A Latvian rule set layered on the engine's core profile: seller / buyer VAT, EUR currency, buyer reference, valid VAT categories, endpoint presence and credit-note referencing of the original invoice.
BYOK credentials
The Access Point API key is held on the connection record, never bundled, and transmitted only to the gateway you configure. An onboarding wizard, a connection model, an optional batch-submission cron and full transport logging round out the connector.
Screenshots
Built for Latvia
Network: Peppol (4-corner model). Customisation: Peppol BIS Billing 3.0 (EN 16931). Document: OASIS UBL 2.1 Invoice / CreditNote. Currency: Euro (EUR). The connector builds on the shared e-Invoice Core Engine (validation framework and BYOK REST transport) and registers its own Latvian profile, UBL generator and validation rule set.
Disclosure: this module transmits invoice data only to the Peppol Access Point gateway you configure. Your API key is stored solely on your own database and is never sent anywhere else.
Support
Questions? Write to support@pokutsoft.com. More Odoo apps at pokutsoft.com/.
Update date: 2026-07-02