errorROUubl-2.1

RO-R-002:e-Factura submission required

Romanian B2B/B2G invoices must go through e-Factura (SPV).

Severity
Fatal
Rule set
ubl-2.1
Country
ROU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: Romanian B2B/B2G invoices must be submitted through e-Factura (SPV - Sistemul Național de Facturare Electronică). This requires API integration with ANAF (Romanian tax authority) and cannot be accomplished by modifying the invoice XML. Use invoicing software with e-Factura integration or submit manually through the SPV portal.

What is RO-R-002?

RO-R-002 is a fatal validation rule defined in the ubl-2.1 specification (ROU national rules). It validates the e-Factura platform integration element in the UBL invoice XML.

When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Target path: e-Factura platform integration

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Romanian e-Factura mandatory from 2024.

RO-R-002 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

Validator Behavior

  • ·Causes invoice rejection
  • ·Fails UBL schema validation
  • ·Error returned: RO-R-002
  • ·Specification: ubl-2.1

How to Fix It

1.

Connect to SPV

Get SPV credentials from ANAF

2.

Submit invoice

Via SPV API

3.

Get index

Invoice index number

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Triggers validation error -->
<e-Factura platform integration></e-Factura platform integration>
After
<!-- Corrected -->
<e-Factura platform integration>VALID_VALUE</e-Factura platform integration>

Technical Reference

XPathe-Factura platform integration
Specubl-2.1

Common Causes

  • ·Not submitted to SPV
  • ·Missing e-Factura index

Seeing this in production? The API handles RO-R-002 automatically. See the fix response →

Frequently Asked Questions

Romanian B2B/B2G invoices must go through e-Factura (SPV).

Submit invoice to ANAF e-Factura system. Invoice Navigator can help identify and fix this issue.

Yes, RO-R-002 is a critical error that must be fixed.

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle RO-R-002 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.