Seamore now connects to RO e-Factura and RO e-Transport
Invoices and road transport declarations go to ANAF straight from Seamore, and their status comes back into the same view as the orders and shipments behind them.
/Integrations · Compliance/1 min read
AI narration · ElevenLabs
Seamore now integrates with RO e-Factura and RO e-Transport, ANAF’s national systems for electronic invoicing and for monitoring the road transport of goods. Both are mandatory for most companies operating in Romania, and until now both usually sat outside the operation: an accounting add-on for invoices, a separate portal for transport codes, and a lot of copying in between.
e-Factura
Invoices issued in the connected ERP are converted to the RO_CIUS format, checked before they leave, and submitted to ANAF. Seamore follows each one until ANAF accepts it. A rejection comes back with its reason attached, so it can be fixed and resent instead of discovered at month end. Supplier invoices received through the SPV are downloaded into Seamore as well.
e-Transport
For goods that have to be declared, Seamore prepares the e-Transport notification from the shipment it already knows: goods, quantities, vehicle, route and parties. The UIT code ANAF returns is attached to the shipment and its route, so the office, the warehouse and the driver work from the same code. When a declared shipment changes, Seamore flags the declaration that needs updating.
Obligations in the operating view
Compliance work is operational work. A rejected invoice holds up a payment, and a missing UIT code holds up a truck. With both systems connected, Seamore treats them like any other signal: a rejection or an undeclared shipment shows up in Insights next to the order, stock and route it affects, with an owner and a next step.
Availability
Both integrations are part of the Seamore platform and are included in our first pilot deployments in Romania. Connecting a company uses its existing ANAF SPV access. If you’d like to see them working on your own data, get in touch.