Romania - EDI Zip Export
Romania - EDI Zip Export
Overview
This module adds a wizard that packs every EDI XML file attached to posted invoices over a date range into a single ZIP archive. It is meant for Romanian companies that need to archive the original e-Factura documents exchanged with ANAF — either to keep them under the 10-year retention rule or to hand them over to auditors.
The wizard targets either sale invoices (outgoing — out_invoice /
out_refund / out_receipt) or purchase bills (incoming —
in_invoice / in_refund / in_receipt), and filters by the
selected company, so multi-company databases can produce one archive
per legal entity. Only invoices that carry an l10n_ro_edi_index
(meaning they actually went through the SPV) are exported, and the
matching attachment is preferred in ZIP form, falling back to the raw
XML when no ZIP is stored.
Each file inside the archive is renamed with a descriptive pattern —
partner_vat_invoice-number_invoice-date_original-name.xml — so the
content stays auditable without opening Odoo.
Built & supported by NextERP Romania
Romanian Odoo specialists, here for the long run — from implementation to localization and day-to-day production support.
What we do
Odoo Solutions
From quick-start rollouts to multi-company deployments and custom modules built for your processes.
Romanian Localization
SAF-T (D406), e-Factura, e-Transport, D300 / D390 / D394, ANAF integration, full chart of accounts and fiscal positions.
Our Services
Implementation, customization, migration, integration, support and consultancy — Romanian-speaking, SLA-backed.
Features
- One-click ZIP export of every EDI XML attached to posted
invoices for a given period, produced by the
l10n.ro.edi.zip.exportwizard. - Sale or purchase mode — pick
Sale(outgoing invoices and refunds) orPurchase(vendor bills, refunds, receipts) before running the export. - Multi-company aware — the wizard exposes the company selector when Multi Company is active, so each legal entity produces its own archive.
- Sensible defaults — by default the date range covers the previous calendar month, matching the typical monthly archiving cadence.
- Stable, auditable file names — each archive is named
<Company> - <VAT> - <date_from>-<date_to>.zipand each entry uses<partner>_<vat>_<invoice-number>_<invoice-date>_<original-name>.xml. - EDI-only scope — only invoices with a non-empty
l10n_ro_edi_index(i.e. transmitted through SPV / e-Factura) are included; drafts and non-EDI invoices are skipped. - Prefers the ZIP attachment the EDI stack stores; falls back to the plain XML attachment when no ZIP version is available.
Configuration
The module does not require any setup of its own — installing it just registers the export wizard and the related menu. The prerequisites live in the modules it depends on.
1. Make sure EDI is configured
The wizard exports the attachments produced by Romania - E-invoice
(l10n_ro_edi). For invoices to be picked up by the wizard they must:
- Belong to a company whose Romanian e-Factura credentials are set (see Settings → Accounting → Romanian Localization → E-Invoice).
- Have been transmitted through ANAF SPV, so the field
l10n_ro_edi_indexis populated. - Be in state Posted.
If your invoices are still missing the EDI index, run the standard e-Factura flow first — this module does not generate XML, it only packages what is already attached.
2. Grant access
The wizard model l10n.ro.edi.zip.export is exposed to the
Internal User group, so any accounting user with read access to
invoices can run the export. No extra security rule needs to be
added.
3. Locate the menu
The wizard is reachable from the standard Romanian accounting menu:
- Accounting → Accounting → Romania → EDI - Export Zip
The menu is created under the Romania node added by
l10n_ro_account_enterprise, so the parent module must also be
installed (it is in the manifest dependencies).
4. Optional housekeeping
The archive is built fully in memory and returned as a binary field on the wizard, so nothing is written to disk on the server side. There is no cron job, no scheduled action and no storage to monitor — the file lives only for the duration of the wizard.
How it works
To export an EDI archive for a given period:
- Go to Accounting → Accounting → Romania → EDI - Export Zip. A modal opens with the export form.
- Pick the Company (visible only in multi-company databases).
- Pick the Inv Type —
Salefor issued invoices and refunds,Purchasefor received vendor bills. - Adjust Start Date and End Date if needed. The defaults already cover the previous calendar month, which is the most common archiving period.
- Click Export.
The wizard scans all posted invoices in the period that match the
type and have a non-empty l10n_ro_edi_index, and packs every
matching EDI attachment into a single ZIP. The result appears in the
File field of the same form — click the filename to download it.
How it works
For each invoice the wizard:
- Filters the attachments first for a ZIP whose name contains the
l10n_ro_edi_index. If none is found, it falls back to an XML attachment with the same index. - Renames the entry inside the ZIP using
partner_vat_invoice-number_invoice-date_original-nameso the resulting archive is self-describing.
The output file is named
<Company> - <VAT> - <date_from>-<date_to>.zip and you can rerun the
wizard with a different period as many times as needed — nothing is
stored on the server between runs.
Versions
19.0.0.1.1 (2026-05-24)
- Changelog tracking starts at this release.
Discover the NextERP suite
Other modules from the same publisher, built to work together.
NextERP Romania
Odoo implementation, customization, Romanian localization and long-term support since 2018.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 1919 |
| Technical Name |
l10n_ro_edi_download_archive |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
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