BR-RO-100 ANAF CIUS-RO 1.0.1 RO FATAL REJECTION
BR-RO-100 — Bucharest Addresses Require Exact 'SECTOR1'..'SECTOR6' CityName
Rule Definition & Compliance Impact
One of the highest-volume ANAF SPV rejections: whenever CountrySubentity (BT-39/BT-54/BT-78) is 'RO-B' (Bucharest), Rule BR-RO-100 requires CityName (BT-37/BT-52/BT-77) to be strictly one of 'SECTOR1', 'SECTOR2', 'SECTOR3', 'SECTOR4', 'SECTOR5', or 'SECTOR6' (uppercase, zero spaces).
Common ERP & Exporter Root Causes
CRMs and ERPs store 'București', 'Sector 1', or 'Bucuresti, Sectorul 1' in CityName, every single variant of which is fatally rejected by ANAF Schematron.
How to Fix This Violation
Normalize every Bucharest address before XML export: set CountrySubentity to 'RO-B' and map CityName strictly to 'SECTOR1', 'SECTOR2', 'SECTOR3', 'SECTOR4', 'SECTOR5', or 'SECTOR6'.
Non-Compliant vs. Compliant Payload Comparison
UN/CEFACT CII D16B (Factur-X / ZUGFeRD)
REJECTED
<ram:PostalTradeAddress>
<ram:CityName>București Sectorul 1</ram:CityName>
<ram:CountryID>RO</ram:CountryID>
<ram:CountrySubDivisionName>B</ram:CountrySubDivisionName>
</ram:PostalTradeAddress> COMPLIANT
<ram:PostalTradeAddress>
<ram:CityName>SECTOR1</ram:CityName>
<ram:CountryID>RO</ram:CountryID>
<ram:CountrySubDivisionName>RO-B</ram:CountrySubDivisionName>
</ram:PostalTradeAddress>OASIS UBL 2.1 (XRechnung / Peppol / RO e-Factura)
REJECTED
<cac:PostalAddress>
<!-- Free-text 'Bucuresti Sector 1' fails strict ANAF BR-RO-100 check! -->
<cbc:CityName>Bucuresti Sector 1</cbc:CityName>
<cbc:CountrySubentity>Bucuresti</cbc:CountrySubentity>
<cac:Country><cbc:IdentificationCode>RO</cbc:IdentificationCode></cac:Country>
</cac:PostalAddress> COMPLIANT
<cac:PostalAddress>
<cbc:CityName>SECTOR1</cbc:CityName>
<cbc:CountrySubentity>RO-B</cbc:CountrySubentity>
<cac:Country><cbc:IdentificationCode>RO</cbc:IdentificationCode></cac:Country>
</cac:PostalAddress>