| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4291 |
| Technical Name |
l10n_ro_etransport_intl |
| 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 | 4291 |
| Technical Name |
l10n_ro_etransport_intl |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Romania e-Transport International
ANAF RO e-Transport for cross-border movements — border crossing point, customs office, MRN & transit declarations
Extends the Romania e-Transport connector with everything the ANAF e-Transport system requires for international goods movements — imports, exports and intra-community acquisitions and deliveries crossing the Romanian (EU) frontier. Adds the border crossing point, the customs office, the customs declaration MRN and the transit document chain on top of the base UIT declaration.
Odoo 18 Odoo 19 ANAF SPV (BYOK) Import / Export / Intra-EU
Border crossing point & customs office
Pre-loaded catalogues of Romania's road border crossing points
(Nadlac, Bors, Giurgiu, Calafat, Albita, Siret, Galati and more) with the
ANAF codPtf, and the principal Romanian customs offices
with their codBirouVamal. Both are editable and shared
across companies, and are pre-filled on a transfer from its geography.
Customs declaration MRN
The customs Master Reference Number is validated structurally (18 characters: 2-digit year, 2-letter country, 14 alphanumeric) with the ISO 7064 MOD 37-2 check character used by the EU NCTS/AES, so a mistyped reference is rejected before it reaches ANAF.
International XML segments
On top of the base ANAF declaration the extension emits
codPtfStraina / codPtf (entry / exit border
point), codBirouVamal (customs office), the customs and
transit document block (DVI MRN, T1/T2, CMR) and the transit-country
data — spliced in the XSD-mandated element order.
International validation profile
A dedicated ro_etransport_intl rule set: import and export
require a border crossing point and a customs office; intra-community
movements require a foreign-tax-id partner; every supplied MRN must be
structurally valid. Errors are surfaced before submission, not after
ANAF rejection.
Operation inference
Outgoing transfers to non-RO destinations are classified as intra-community delivery (EU) or export (non-EU); incoming from non-RO as intra-community acquisition (EU) or import. The border crossing point and customs office are pre-filled to match, with one-click autofill.
Built on the shared engine
Reuses the e-Invoice Core Engine (canonical builder, declarative validation, BYOK REST transport) and the base l10n_ro_etransport_gb connector — the same SPV BYOK token, UIT QR and ANAF logging. No engine or base functionality is duplicated.
What's included
- Border crossing point catalogue (codPtf) with bordered country.
- Customs office catalogue (codBirouVamal), import / export aware.
- International e-Transport XML segment generator.
- Customs MRN validator (ISO 7064 MOD 37-2).
- The
ro_etransport_intlvalidation profile. - International fields and autofill on the transfer.
- International onboarding wizard.
Disclosure: this module transmits international transport-declaration data only to the ANAF e-Transport endpoint configured on the base connector. Your SPV access token, fiscal codes and customs references are stored solely on your own database and are never sent anywhere else. Requires the base Romania e-Transport module and the e-Invoice Core Engine.
gencbaris.com/odoo_plugins
Screenshots
International Import Transfe
International E Transport De
Border Crossing Points Catal
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