| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3059 |
| Technical Name |
l10n_ee_einvoice |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
Estonia e-arve for Odoo
Generate standards-compliant Estonian e-invoices — EVS 923 / EN 16931 UBL 2.1 — and transmit them through your own e-invoice operator (Finbite or RIK e-arveldaja), directly from Odoo.
What It Does
This module makes Odoo ready for Estonian e-invoicing. It builds the national e-arve document — historically described by EVS 923 and now equivalently carried as EN 16931 / Peppol BIS Billing 3.0 UBL 2.1 — from your customer invoices and credit notes, validates it against the Estonian business rules, and transmits it through your own e-invoice operator to the recipient. Estonia already requires structured e-invoices on a buyer's request (since 1 July 2025), with a B2B trajectory toward 2027.
One-Screen Operator Setup
Configure your operator (Finbite or RIK e-arveldaja), authentication and sender id, with a sandbox toggle and a one-click connection test. Credentials are bring-your-own-key and stay on your database.
Key Features
EVS 923 / EN 16931 UBL 2.1
Invoices and credit notes with the Estonian customization, Peppol 0191 (EE:CC) electronic-address scheme, buyer reference and VAT categories — standard 24%, reduced 13% / 9%, zero, exempt, reverse charge, intra-Community and export.
BYOK Operator Submission
Send the UBL document to Finbite or RIK e-arveldaja with bearer, API-key or basic auth, editable sandbox/production endpoints, automatic retry/backoff, delivery-status polling and full call logging.
Registry & KMKR Validation
Validates the 8-digit company registry code (registrikood) with its MOD 11-10 check digit and the KMKR VAT number (EE + nine digits) on the company and partners.
Pre-Send Validation
Checks the Estonian e-arve business rules (seller registry/VAT, EUR currency, VAT categories, exemption reasons, buyer reference, credit-note references) before anything leaves Odoo.
SEPA Pay-by-QR
Each invoice carries an EPC069-12 SEPA Credit Transfer QR with the IBAN, amount and structured creditor reference (viitenumber with 7-3-1 check digit), rendered as an image.
Onboarding Wizard
A guided setup wizard captures the company registry code, KMKR number and operator credentials in one step, with an optional connection test.
Status & QR on Every Invoice
A dedicated Estonia e-arve tab on each invoice: delivery status (To Send / Generated / Sent / Delivered / Rejected), operator document id, payment reference, the SEPA pay-by-QR and the generated UBL payload.
Built on the e-Invoice Core Engine
This connector builds on the shared e-Invoice Core Engine (UBL 2.1 builder, validation framework, BYOK REST transport and the e-invoicing document model). It does not duplicate engine functionality — it registers an Estonian jurisdiction profile, a UBL profile and a validation profile, so the same audited core powers every country connector.
Requirements
- Odoo 18.0 or 19.0 (Community or Enterprise).
- The e-Invoice Core Engine module (dependency).
- An account with an Estonian e-invoice operator (Finbite or RIK e-arveldaja) or a Peppol access point.
- Python libraries: lxml, qrcode, requests (standard with most Odoo deployments).
Screenshots
Posted Eur Invoice With Esto
Generated Evs 923 En 16931 U
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3059 |
| Technical Name |
l10n_ee_einvoice |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module