# e-Factura and e-Transport, straight from your documents.

> VITT works with ANAF's public services: it sends your issued invoices to SPV after checking them, downloads the invoices you receive, declares transports in RO e-Transport and fills in partners' details from their CUI (tax ID). You authorise VITT in SPV (Spațiul Privat Virtual, ANAF's online portal) from the company settings, with the digital certificate registered there.

Source: https://vitt.ro/en/integrations/anaf-e-factura-e-transport/

- **Company data from the CUI.** When you add a partner, their details come from ANAF's register, by CUI.
- **EU partners through VIES.** Add a company from another EU country by its VAT number, checked in VIES.
- **VAT, checked.** VAT categories, VAT on collection and exemptions are checked before the invoice leaves.
- **BNR rate on the document.** Foreign-currency invoices use the BNR (National Bank of Romania) rate, and the rate applied appears on the PDF.
- **No declaration, with a reason.** A document that needs no e-Transport declaration is marked with its reason, and the mark can be undone.
- **Comments stay with you.** Internal comments on a declaration, with @mentions, never reach ANAF, the XML or the aviz.

## Invoices reach SPV already checked.

Before it leaves, VITT checks it against the e-Factura rules, from VAT rates to the client's details. ANAF's answer appears next to the invoice, separate from the invoice's own status and from its payment.

- **Sent on the day you choose.** On the day of issue or 1–5 business days later, and the 5-business-day deadline is tracked on every invoice. It is a schedule you set, not AI.
- **Three states, never mixed up.** The invoice, e-Factura and payment each have their own state. For ANAF you see whether an invoice is pending, submitted, accepted, rejected or failed.
- **A rejected invoice gets fixed.** Amend it under the same number, issue a correction invoice, or redo just the file sent to ANAF.

## Supplier invoices arrive from SPV on their own.

VITT downloads received invoices every hour or on demand and books them with their payable. ANAF's signature is checked, and unknown suppliers are created from ANAF's data.

- **XML and ZIP archives.** UBL or CII XML invoices and ZIP archives downloaded from SPV import directly. Reading structured XML uses no AI.
- **Invoices issued before VITT, too.** Bring them in from their e-Factura XML, so each customer's history is complete.

## The declaration starts from the document that moves the goods.

On every aviz (delivery note), invoice with goods or purchase from abroad, VITT tells you whether the transport must be declared. The declaration fills in from the document, and nothing reaches ANAF until you click Get UIT.

- **Every kind of operation.** Deliveries in Romania, transfers between your own warehouses, intra-community acquisitions (AIC) and deliveries (LIC), import and export.
- **From the document, not from scratch.** The operation, partner, route and goods come from the document; from an aviz, the vehicle too. Foreign-currency values are converted to lei at the BNR rate.
- **ANAF's messages, in view.** For each declaration you see who sent every message, ANAF's answer and the XML.

## The UIT on the delivery note, and everything after it.

The UIT code and its QR code appear on the aviz and its PDF. Change the vehicle on the road and confirm delivery at the destination, all on the same declaration.

- **Corrections keep the UIT.** A correction before departure and a change of vehicle keep the same UIT code.
- **Confirmation on delivery.** Confirm, partly confirm or reject the transport. On a partial confirmation, the note for ANAF is composed from the returned quantities.
- **A UIT obtained outside VITT.** Enter it on the aviz, so the document is complete.

## Where it fits in VITT

The ANAF integration is not a separate module: it works on the documents you already issue. An invoice from [invoicing](/en/features/invoicing-e-factura/) goes to e-Factura, a received invoice from SPV lands in [purchases](/en/features/purchases-supplier-invoices/) with its payable, and an aviz from [stock](/en/features/inventory/) starts its declaration in [e-Transport](/en/features/e-transport/). Company data from the CUI fills in partners wherever you add them.

## Good to know

VITT uses ANAF's public services, like any software that works with e-Factura and RO e-Transport, and is not affiliated with ANAF. The rules, deadlines and fines are explained in the [e-Factura guide](/en/blog/e-factura-guide/) and the [e-Transport guide](/en/blog/e-transport-guide/).

## FAQ

### How does VITT connect to SPV?

From the company settings you authorise VITT in SPV, signing in to ANAF with the digital certificate registered in SPV. VITT then sends your issued invoices and downloads the ones you receive. The authorisation expires, and you renew it from the same settings.

### Is VITT approved or certified by ANAF?

No. VITT uses ANAF's public services for e-Factura, e-Transport and company data, and is not affiliated with, approved or certified by ANAF.

### Does VITT send invoices to e-Factura automatically?

If you want it to. You choose the day, the day of issue or 1–5 business days later, and VITT tracks the 5-business-day deadline. Invoices created or edited from an AI assistant over MCP wait for approval in VITT by default.

### What do I do if ANAF rejects an invoice?

ANAF's answer appears next to the invoice. Amend it under the same number, issue a correction invoice or redo just the file sent to ANAF, then send it again.

### How often does VITT fetch received invoices from SPV?

Every hour, or straight away when you ask. Each received invoice arrives booked, with the payable to the supplier, and ANAF's signature is checked.

### Does VITT send the e-Transport declaration without me?

No. VITT fills in the declaration from the document and tells you whether the transport must be declared, but nothing reaches ANAF until you click Get UIT.
