Workflow: eTransport + eFactura — ANAF Compliance

Modules involved: eTransport · Billing (eFactura) · Invoices · Warehouse (Goods Delivery — optional reference)
Who uses it: Finance · Accounting · Logistics
Typical duration: eTransport = before departure · eFactura = on the day of issuance or automatically after N days

Overview

CRMConnect covers both ANAF obligations for companies in Romania:

Architectural note: Both systems communicate through the CRMConnect intermediary (https://einvoice.crmconnect.ro/api/e-factura/), not directly with ANAF. The ANAF OAuth token is stored on the CRMConnect server, not locally. Authentication is done once at https://einvoice.crmconnect.ro/e-factura/auth.

eTransport is not generated automatically when a delivery note or sales order is created. The user manually completes the declaration, with the option to select existing delivery notes/invoices as a reference.

Flow diagram

[INITIAL SETUP — admin, once only]
  │
  ├── Settings → General: company_vat (company VAT number), instance_id (CRMConnect account)
  ├── Settings → default_country = Romania (142) ← condition for eFactura menu
  ├── ANAF token authorization: https://einvoice.crmconnect.ro/e-factura/auth
  │     (SPV ANAF login, token stored on CRMConnect proxy)
  └── Banking: at least one bank account (IBAN) configured in Billing → Banks
  │
  ↓
════════════════════════════════════════════
E-TRANSPORT (before departure)
════════════════════════════════════════════
  │
  ├── [Optional] Create delivery note in Warehouse or Sales Order
  │
  ├── eTransport → Documents → Add Declaration
  │     ├── Operation type (from tipuri_operatii table)
  │     ├── Commercial partner (client or vendor)
  │     ├── Vehicle: license plate (+ trailer 1/2 optional)
  │     ├── Transport date (open_till)
  │     ├── Goods transported: NC tariff code, UOM, quantity, weight, value
  │     ├── Route: start (county+address / customs office / border crossing point) + end
  │     └── Transport documents: delivery note/invoice (type, series, number, date) ← optional reference
  │
  ├── Initial status: Not sent (3)
  ├── "Send to eTransport" button → POST to einvoice.crmconnect.ro/generate-xml
  │     → Response: indexIncarcare (upload_index) + uit (UIT code)
  │     → Status becomes: In processing (0)
  ├── Status polling: Get Status → transport-status endpoint
  │     → Status becomes: Validated (1) or Error (2)
  │
  ├── If needed: Vehicle modification (send_modif_vehicul → type:'modifVehicul')
  └── If needed: Declaration deletion (type:'stergere' with existing UIT)
  │
  ↓
════════════════════════════════════════════
E-FACTURA (at issuance or automatically)
════════════════════════════════════════════
  │
  ├── Invoice created → automatic eligibility check:
  │     ✓ Currency = RON (currency_id = 3)
  │     ✓ Client country = Romania (cod_tara_client = 'RO')
  │     ✓ Invoice status ≠ cancelled, ≠ draft
  │
  ├── Path A — Manual: "Send eFactura" button on invoice
  │     → POST /billing/efactura/send_invoice/{id}
  │     → estatus = 'trimis'
  │
  └── Path B — Automatic (cron): autosend_efactura = 1
        → selects invoices: estatus IS NULL AND eindex IS NULL
        AND date = today - autosend_efactura_days (default 3 days)
        → limit 1 per cron run
  │
  ↓
[ANAF PROCESSING]
  │
  ├── estatus = 'in prelucrare' (ANAF processing)
  ├── Cron sync: polls up to 10 invoices per run
  │     → estatus = 'ok' (accepted) or 'nok' (rejected)
  └── On 'nok': download ZIP archive with errors (download-invoice endpoint)
  │
  ↓
[IMPORT RECEIVED INVOICES — optional]
  │
  ├── Cron: sync_efactura_invoices() every autoimport_efactura_interval hours
  ├── Polls company-messages endpoint (filters P and R)
  └── Automatically imports vendor invoices into Purchase → Vendor Invoices

[DECLARATIONS COMPLETE ✓ · INVOICES ACCEPTED BY ANAF ✓]

Step by step

1. Initial setup (admin)

1a. General settings

Where: /admin/settings → General Settings

1b. ANAF token authorization

Navigate to:

https://einvoice.crmconnect.ro/e-factura/auth?company_id={instance_id}&fiscal_code={VAT}&partner_id=2

You will be redirected to SPV ANAF for authentication with a digital certificate or SPV username+password. The resulting token is stored on the CRMConnect server — does not require manual renewal if the connection remains active.

You can verify the token status from: Billing → eFactura → Settings → Check ANAF Token.

1c. Bank account (for eFactura)

Where: /admin/billing → Banks → Add Bank Account

The IBAN appears in the e-Factura XML. Without at least one configured account, the generated XML does not include banking details.

1d. Test vs. production mode

Where: /admin/billing → eFactura → Settings → einvoice_test_mode

• 1 = uses https://deveinvoice.crmconnect.ro/api/e-factura/ (sandbox)
• 0 = production (default after completing setup)

2. eTransport declaration

Where: /admin/etransport → Documents → Add

2a. Operation types

The operation type determines mandatory fields and whether prior notifications are required (previous_notifications = true → the notificareAnterioara field becomes mandatory).

Required fields:

Goods transported (at least one):

Route (start + end required): Each route point is one of: address (county + locality + street) / customs office (code from tbletransport_list_birou_vamal) / border crossing point (code from tbletransport_list_ptf).

Transport documents (at least one):

2b. eTransport declaration statuses

UIT validity (uit_valability — display):

2c. Vehicle modification after submission

If the vehicle changes after the UIT has been issued, use the Modify Vehicle button — sends type: 'modifVehicul' with the new license plate and existing UIT.

3. Sending eFactura

Where: invoice → Send eFactura button OR automatically via cron

3a. Eligibility conditions (checked at submission)

3b. eFactura statuses

3c. Automatic sending via cron

Where: /admin/billing → eFactura → Settings

The cron sends maximum 1 invoice per run in automatic mode. Rejected invoices (nok) are not automatically resent — manual intervention required.

3d. Importing vendor invoices from SPV

Where: /admin/billing → eFactura → Settings → autoimport_efactura_interval (hours)

The cron queries the SPV inbox and automatically imports invoices received from vendors into Purchase → Vendor Invoices. Works independently of eFactura sending.

Required permissions

Gotchas

Module references

• Invoices — standard invoices
• Warehouse — Goods Delivery — delivery notes (optional reference in eTransport)
• Purchase — Vendor Invoices — vendor invoices imported from SPV
• Integrations — eFactura — integration settings