e-Factura (ANAF) - sending and receiving

e-Factura is the Romanian tax authority (ANAF) electronic invoicing system: invoices travel between companies through the state platform (SPV), not on paper or as PDFs. It is mandatory for B2B transactions in Romania. The app covers both directions: sending the invoices you issue and receiving the invoices your suppliers send you.

Two flows

Outbound (issued invoices): an invoice you issue to a customer is converted into the ANAF standard format (UBL) and sent to the SPV.
Inbound (received invoices): the invoices your suppliers issue to you land in the SPV; the app brings them into a local inbox where you review and import them into your records.

Sending issued invoices

After you issue a sales invoice (see Partners and invoicing), you can transmit it through e-Factura. The app builds the document in the format ANAF requires and sends it to the SPV, tracking the send status. Authentication to ANAF uses the configured token, refreshed automatically when it expires (see Setup below), so you do not have to intervene manually on each expiry.

Receiving supplier invoices (the e-Factura inbox)

The app synchronizes the SPV messages automatically every day and collects them in an inbox. Open it from the menu at Utilities > Receive Supplier Invoices (e-Factura).

The screen lists the messages over a configurable period and colour-codes them by state:

New - a message arrived from ANAF, not yet imported and not rejected.
Imported automatically - turned into a received invoice through this screen (linked by the message’s upload index).
Imported manually - the message was matched to an already manually-entered invoice (by fiscal code
- number + date + value) and that invoice was linked to the ANAF message.
Rejected - flagged locally as refused; nothing is sent back to ANAF.

From this screen you can:

Re-query ANAF to pull new messages for the selected period.
Auto-verify (Verifică automat) - automatically links messages to already manually-entered invoices (matching by fiscal code + number + date + value), useful when you booked the invoice before importing it from ANAF.
Import (Preluare) - turn a message into a received invoice. The app identifies the supplier by the fiscal code in the message; if exactly one supplier has that code it opens the import editor directly, otherwise it asks you to resolve the supplier (pick or create). If the invoice was already entered manually, the app links it to the message instead of duplicating it.
Reject / cancel rejection - for messages that do not concern you (errors, duplicates).
Bulk reject - reject the new messages before a chosen date (already-imported ones are left untouched), handy for clearing old history.
Open - for an already-imported message, opens the created invoice directly.

This way a supplier invoice does not stay a mere SPV message: you bring it into your accounting records with a link back to its originating ANAF document.

Setup

The ANAF connection details are set in Admin / Setup > General Settings > Configuration > eFactura: Client ID, Client Secret, the identity and refresh tokens, the look-back days for receiving, and the notified group. The access token is refreshed automatically from the refresh token when it expires, with no manual step.

What the accountant sees

Received invoices imported through e-Factura enter Received Invoices and are centralized on the expense/purchase side (class 6 / stock), with deductible VAT on 4426.
From there they follow the same path as any received invoice: expense/purchase centralizer -> accounting note -> journal, and VAT is settled at month close (see Automatic accounting - the Centralizer).