Features

• Full eTransport parity for batch transfers — batch notifications go through the same ANAF Schematron v2.0.2 validation as individual transfer notifications.
• Configurable price source per batch — drive valoareLeiFaraTva from cost, purchase order, sale order, or list price.
• Correct weights, UoM, and NC8 tariff codes computed per move within the batch.
• Street/number address split on location addresses, satisfying ANAF schema requirements.
• Multiple transport documents and previous notifications on the batch form for operations 60/70.
• Post-outage declaration flag (OUG 41/2022 art. 8 par. 1³) directly on the batch.
• Delete / Confirm / Modify Vehicle ANAF actions available on the batch form via the shared action wizard.
• Batch UIT reconciliation included in the scheduled ANAF LIST sync cron job automatically.

Configuration

This module requires no dedicated configuration steps beyond installing its two dependencies (l10n_ro_edi_stock_batch and l10n_ro_edi_stock_extension). All configuration required for those modules (ANAF credentials, eTransport product settings, warehouse addresses) applies equally to batch transfers.

The only batch-specific setting is the eTransport Price Source field on each batch transfer form, which defaults to Automatic (by operation) via _l10n_ro_edi_stock_default_price_source. Change it per batch as needed before sending the notification.

How it works

This module extends the existing eTransport workflows on batch transfers. The steps below assume l10n_ro_edi_stock_batch and l10n_ro_edi_stock_extension are already in use for individual transfers.

Sending an eTransport notification from a batch transfer

1. Navigate to Inventory → Operations → Batch Transfers and open (or create) the batch you want to declare.
2. On the batch form, locate the eTransport section (added by this module).
3. Set eTransport Price Source (l10n_ro_edi_stock_price_source) to the value appropriate for the shipment — e.g. Purchase order price for inbound goods.
4. If the transport is a continuation or correction of a previous notification (operations 60/70), add entries under Previous Notifications (l10n_ro_edi_stock_previous_ids).
5. Add any accompanying Transport Documents (l10n_ro_edi_stock_document_line_ids) (CMR, waybill, etc.).
6. If the notification could not be sent during an ANAF outage, tick Post-Outage Declaration (l10n_ro_edi_stock_post_outage).
7. Click the Send eTransport button (from the action wizard). The wizard (l10n.ro.edi.stock.action.wizard) validates the batch data against ANAF Schematron v2.0.2 and uploads the XML. The returned UIT is stored on the batch.

Modifying vehicle or deleting/confirming a previously sent notification

1. Open the batch transfer that already has a UIT.
2. Use the Delete, Confirm, or Modify Vehicle actions available on the batch form (same wizard, batch_id-aware branch).
3. ANAF's response is logged on the chatter.

Monitoring batch UITs via the ANAF LIST cron

The scheduled action eTransport — ANAF LIST sync (defined in l10n_ro_edi_stock) automatically reconciles batch UITs alongside individual transfer UITs. No extra configuration is needed — batches are included in _l10n_ro_edi_stock_list_sync_one automatically.

Versions

19.0.1.0.0 (2026-06-23)

• Changelog tracking starts at this release.