B2B e-invoicing runs through e-Factura, on top of the national CIUS of EN 16931.
The facts
| Format | RO e-Factura (CIUS-RO 1.0.1) |
| Goes to | ANAF, through the SPV portal |
| Regime | Post-audit — you issue, then report |
| Invoice number | Stays ours: gap-free, sequential, yours to control |
| Seller tax ID | CUI |
| Buyer tax ID | CUI |
| Peppol EAS code | 9947 |
| Integration | SmartBill, Oblio, FGO |
The part that costs a day
CIUS-RO is stricter than plain EN 16931: it rejects documents that pass a generic Peppol validator. The usual rejection is a missing or malformed CUI on either party, followed by tax amounts that were extracted from the gross instead of computed from the base.
We issue gap-free, sequential numbers that reset on your schedule and are never reused — including for voided documents, which keep theirs. The authority takes the document as numbered.
Never extracted from the gross. The two formulas differ by a cent and the wrong one gets the file rejected. The leftover cent is declared as payment rounding (BT-114), where the standard puts it.
Straight talk
We do not hold your signing certificate, we do not file your periodic returns, and we are not your accountant.
No third-party provider is required: we build and validate the document ourselves, and you can still connect one if your accountant prefers it.
Oltrano