What e-Factura is, in neutral terms
e-Factura is the electronic invoicing system of the State Tax Service (SFS) of Moldova, available at the SIA e-Factura portal. The invoice is registered with the tax authority in a structured electronic form instead of being sent only as a PDF by email.
The State Tax Service keeps a list of taxpayers who are obliged to use the e-Factura system. The Ministry of Finance notes that from 1 January 2026 the rule in art. 102(18) of the Tax Code, which restricted VAT deduction on non-electronic invoices from suppliers on that list, was repealed. Whether and how the system applies to your company is something to confirm with SFS or your accountant; this guide only describes how the invoicing itself works in the software.
Why transport invoicing is not like other invoicing
A haulier rarely sells one item to one client. A single invoice often covers several orders for the same customer, each one an international route with its own dates. Prices are frequently agreed in EUR while the company keeps its books in MDL, and the proof that the service was performed is a CMR note signed at unloading.
That is why invoicing works best when it is tied to the order. If the order, the route and the CMR already sit in one record, the invoice can be built from them instead of being typed again. The TMS overview explains how orders, tracking and documents fit together, and the invoicing module covers the accounting side.
Step 1: connect the company to SFS once
The setting is per issuing company. In the SFS e-Factura portal the company creates an API user, then enters those credentials in TAFI Agent one time. A test connection button checks that they work before you issue anything.
This applies to issuing companies registered in Moldova, identified by their 13-digit IDNO. If your company operates from Romania, the route is different; see the section on Romania below.
Step 2: build the invoice from finished orders
Invoices are built from finished transport orders. You can put one or several orders for the same client on one invoice. Each order becomes one line, described as the international transport route from origin to destination. VAT is applied at the company's rate, and the buyer is identified by its IDNO.
Because the lines come from the order, the route text is the one the dispatcher planned, not a phrase someone retyped at month end.
Step 3: series and number, posting, signing
Before posting, TAFI Agent reserves the series and number from SFS and saves them on every order included in the invoice, so each order shows which invoice it belongs to. Optionally, the CMR or act PDF can be attached to the e-Factura as an annex.
TAFI Agent then posts the invoice to SFS unsigned. It does not sign the invoice itself: the accountant signs it in the efactura.sfs.md portal. That is a deliberate split, since the signature belongs to the person who is responsible for the document.
Step 4: status and the signed PDF
Every 5 minutes TAFI Agent checks the invoice status with SFS. Once the invoice is signed, it downloads the signed invoice and its QR code and regenerates the invoice PDF with the QR code and a signed mark. The statuses you see in the app include:
- waiting for signature
- signed
- rejected
- cancelled
Currency: why the invoice is in MDL
The SFS invoice has no currency field, so it is issued in MDL. Orders priced in EUR are converted at the BNM (National Bank of Moldova) rate for the delivery date. If there is no rate for that date, the invoice is not sent, which prevents a wrong amount from reaching SFS.
Non-resident (foreign) clients are invoiced in EUR outside SFS. Check with your accountant which of your clients fall into each group before the first run.
Supplier invoices and corrections
Supplier invoices can be imported on demand from the SFS e-Factura inbox into purchase invoices. Duplicates are avoided by checking series and number together.
Corrections need one honest caveat. A storno can be created in TAFI Agent, but for SFS it is not sent automatically. The correction has to be made in the SFS portal.
Romania versus Moldova
For Romania, ANAF SPV is a separate integration. It is connected once with a digital certificate. Invoices are sent to SPV and show the statuses sent, accepted or rejected, with the rejection explained. Supplier invoices are downloaded from SPV daily, a storno is sent automatically when the original invoice was accepted, and e-Transport UIT declarations are sent in the background.
Both flows live in the same program. Invoices are routed separately according to the country of the issuing company, so a group with a Moldovan and a Romanian entity does not mix them. For the Moldova-specific setup, see TMS for transport companies in Moldova.
Checklist before the first invoice
- Confirm with SFS or your accountant that the company is set up in the e-Factura portal.
- Create the API user in the portal and enter its credentials in TAFI Agent; run the test connection.
- Check that the orders you plan to invoice are finished and that client IDNOs are filled in.
- Make sure BNM rates are available for the delivery dates of EUR orders.
- Decide whether the CMR PDF should go as an annex.
- Agree who signs in the portal and how often they check for invoices waiting for signature.
- Agree that corrections are done in the SFS portal.