| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3149 |
| Technical Name |
l10n_ro_etransport_gb |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3149 |
| Technical Name |
l10n_ro_etransport_gb |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Romania e-Transport (ANAF UIT)
ANAF RO e-Transport declarations for high-fiscal-risk goods — UIT code & verification QR on every delivery
Connect Odoo to Romania's RO e-Transport system, operated by ANAF and the Customs Authority. Stock transfers carrying goods classified as high fiscal risk are declared to the SPV gateway before dispatch and the returned UIT code is stored on the delivery — ready for the full enforcement in force since 1 January 2026.
SPV upload & UIT
The declaration is uploaded over the documented ANAF e-Transport REST API; the issued UIT code is parsed and processing status can be polled. Test and production endpoints are editable; requests retry with exponential backoff and every call is logged.
UIT code + verification QR
The UIT and a printed UIT/vehicle reference are stored on the transfer. An ANAF e-Transport verification-URL QR is generated and rendered to a PNG for presentation at roadside control.
Accurate e-Transport document
ANAF schema mfp:anaf:dgti:eTransport:declaratie:v2 XML:
declarant CUI, operation scope and type, commercial partner, transport
(vehicle plate, trailer, carrier, date), route start/end and per-line
goods with NC tariff code, quantity, gross/net weight and RON value.
Real CUI checksum validation
The official ANAF weighted control-digit algorithm (key 7 5 3 2 1 7 5 3 2, mod 11) validates the Romanian CUI / CIF on the company, partners and the carrier before a declaration reaches ANAF.
Business-rule validation
A Romanian rule set checks the declarant CUI, operation codes, the vehicle plate, the transport date, the commercial-partner requirement by operation type and each goods line's NC code, quantity, weight and value — surfaced before submission so ANAF rejections are avoided.
High-fiscal-risk products
Products carry an NC tariff code, a high-fiscal-risk flag and an ANAF unit of measure. Done transfers carrying flagged goods are queued for declaration; an optional cron drains the queue in bulk.
Bring Your Own Key
The ANAF SPV OAuth2 access token is held on the connection record, never bundled with the module, and transmitted only to the ANAF e-Transport endpoint you configure. An onboarding wizard validates the CUI and wires the company, county and connection in one step.
Compatible with Odoo 18 and Odoo 19.
Disclosure
This module transmits transport-declaration data only to the ANAF e-Transport endpoint you configure. Your SPV access token and fiscal codes are stored solely on your own database and are never sent anywhere else.
Screenshots
Outgoing Transfer With E Tra
E Transport Declaration Reco
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