Romania RO e-Factura v1.x

Key: ro-efactura-v1 Module: github.com/invopop/gobl.ro.anaf Support for the Romanian national e-invoicing system, RO e-Factura, operated by ANAF. The addon applies the national rules (BR-RO) RO_CIUS adds to the EN 16931 semantic model: the document types ANAF files, the ISO 3166-2:RO subdivisions and Bucharest sector codes addresses have to carry, the VAT accounting currency, the identifiers of the seller and the buyer, and the length and count limits of every element. Built on the EU EN 16931 CIUS profile, declared as a dependency.

Sources

Scenarios

Scenarios attach notes and extensions to a document when its filters match. Read more about scenarios.

bill/invoice

Tags	Type	Output
-	`standard`	`{ “ext”: { “untdid-document-type”: “380” } }`
-	`credit-note`	`{ “ext”: { “untdid-document-type”: “381” } }`
-	`corrective`	`{ “ext”: { “untdid-document-type”: “384” } }`
`accounting`	`standard`	`{ “ext”: { “untdid-document-type”: “751” } }`
`self-billed`	`standard`	`{ “ext”: { “untdid-document-type”: “389” } }`
`self-billed` custom	-	`{ “note”: { “key”: “self-billed”, “text”: “Autofactură” } }`

Validation Rules

Validation rules check each struct against a set of assertions and report any failures with a unique code and message. Read more about validation.

bill.Invoice

Field	Test	Validation Code / Message
Invoice	Invoice number has a digit	`GOBL-RO-EFACTURA-BILL-INVOICE-01` Invoice number (with series when set) must include at least one digit (BR-RO-010)
Invoice	Invoice number within length	`GOBL-RO-EFACTURA-BILL-INVOICE-02` Invoice number (with series when set) must be no more than 200 characters long (BR-RO-L200)
Invoice	Can convert to [RON]	`GOBL-RO-EFACTURA-BILL-INVOICE-03` Invoice in a currency other than RON must provide an exchange rate to RON, so VAT can be stated in RON (BR-RO-030, BR-53)
Invoice	Currency within two subunits	`GOBL-RO-EFACTURA-BILL-INVOICE-04` Invoice currency must state its amounts on no more than two decimals (BR-RO-Z2)
Invoice	Notes within count	`GOBL-RO-EFACTURA-BILL-INVOICE-05` Invoice notes, with the autofactura mention the converter adds, must contain no more than 20 entries (BR-RO-A020)
Invoice	Seller is identified	`GOBL-RO-EFACTURA-BILL-INVOICE-10` Invoice supplier must have a VAT identifier or a tax registration identifier, or its tax representative a VAT identifier (BR-RO-065)
Invoice	Outside scope stands alone	`GOBL-RO-EFACTURA-BILL-INVOICE-36` An invoice not subject to VAT (category O) cannot carry other VAT categories (BR-O-11)
`preceding`	Length at most 500	`GOBL-RO-EFACTURA-BILL-INVOICE-06` Invoice preceding must contain no more than 500 entries (BR-RO-A500)
`preceding`	Preceding numbers within length	`GOBL-RO-EFACTURA-BILL-INVOICE-07` Preceding invoice number must be no more than 200 characters long (BR-RO-L200)
`attachments`	Length at most 50	`GOBL-RO-EFACTURA-BILL-INVOICE-08` Invoice attachments must contain no more than 50 entries (BR-RO-A050)
`ordering.cost`	Rune length at most 100	`GOBL-RO-EFACTURA-BILL-INVOICE-09` Buyer accounting reference must be no more than 100 characters long (BR-RO-L100)
`ordering.seller`	Tax representative address has a street	`GOBL-RO-EFACTURA-BILL-INVOICE-16` Tax representative address line 1 is required (BR-RO-140)
`ordering.seller`	Tax representative address has a city	`GOBL-RO-EFACTURA-BILL-INVOICE-17` Tax representative city is required (BR-RO-150)
`supplier`	Supplier address has a street	`GOBL-RO-EFACTURA-BILL-INVOICE-11` Invoice supplier address line 1 is required (BR-RO-080)
`supplier`	Supplier address has a city	`GOBL-RO-EFACTURA-BILL-INVOICE-12` Invoice supplier city is required (BR-RO-090)
`customer`	Customer is identified	`GOBL-RO-EFACTURA-BILL-INVOICE-13` Invoice customer must have a legal registration identifier or a VAT identifier (BR-RO-120)
`customer`	Customer address has a street	`GOBL-RO-EFACTURA-BILL-INVOICE-14` Invoice customer address line 1 is required (BR-RO-080)
`customer`	Customer address has a city	`GOBL-RO-EFACTURA-BILL-INVOICE-15` Invoice customer city is required (BR-RO-090)
`tax.notes`	Exemption reasons within length	`GOBL-RO-EFACTURA-BILL-INVOICE-20` VAT exemption reason must be no more than 100 characters long (BR-RO-L100)
`tax.ext`	Invoice type in [credit-note] Ext ‘untdid-document-type’ in [381]	`GOBL-RO-EFACTURA-BILL-INVOICE-21` Invoice tax ext untdid-document-type must be 381 for a credit note (BR-RO-020)
`tax.ext`	Invoice is not a credit note Ext ‘untdid-document-type’ in [380, 384, 389, 751]	`GOBL-RO-EFACTURA-BILL-INVOICE-22` Invoice tax ext untdid-document-type must be one of 380, 384, 389 or 751 (BR-RO-020)
Invoice	Invoice is issued in an enforcement procedure Enforcement body identified	`GOBL-RO-EFACTURA-BILL-INVOICE-35` An enforcement invoice must name the enforcement body as payee, with its name and its legal registration identifier (BR-RO-130)

bill.DeliveryDetails

Field	Test	Validation Code / Message
DeliveryDetails	Delivery has an address Delivery address has a street	`GOBL-RO-EFACTURA-BILL-DELIVERYDETAILS-01` Invoice delivery address line 1 is required when a delivery address is provided (BR-RO-180)
DeliveryDetails	Delivery has an address Delivery address has a city	`GOBL-RO-EFACTURA-BILL-DELIVERYDETAILS-02` Invoice delivery city is required when a delivery address is provided (BR-RO-200)
DeliveryDetails	Delivery has an address Delivery address has a region	`GOBL-RO-EFACTURA-BILL-DELIVERYDETAILS-03` Invoice delivery country subdivision is required when a delivery address is provided (BR-RO-210)

bill.Discount

Field	Test	Validation Code / Message
`reason`	Rune length at most 100	`GOBL-RO-EFACTURA-BILL-DISCOUNT-01` Document level allowance reason must be no more than 100 characters long (BR-RO-L100)

bill.Charge

Field	Test	Validation Code / Message
`reason`	Rune length at most 100	`GOBL-RO-EFACTURA-BILL-CHARGE-01` Document level charge reason must be no more than 100 characters long (BR-RO-L100)

bill.LineDiscount

Field	Test	Validation Code / Message
`reason`	Rune length at most 100	`GOBL-RO-EFACTURA-BILL-LINEDISCOUNT-01` Invoice line allowance reason must be no more than 100 characters long (BR-RO-L100)

bill.LineCharge

Field	Test	Validation Code / Message
`reason`	Rune length at most 100	`GOBL-RO-EFACTURA-BILL-LINECHARGE-01` Invoice line charge reason must be no more than 100 characters long (BR-RO-L100)

org.Party

Field	Test	Validation Code / Message
`name`	Rune length at most 200	`GOBL-RO-EFACTURA-ORG-PARTY-01` Party name must be no more than 200 characters long (BR-RO-L200)
`alias`	Rune length at most 200	`GOBL-RO-EFACTURA-ORG-PARTY-02` Party trading name must be no more than 200 characters long (BR-RO-L200)
`people`	Contact name within length	`GOBL-RO-EFACTURA-ORG-PARTY-03` Contact point must be no more than 100 characters long (BR-RO-L100)
`telephones`	Telephone within length	`GOBL-RO-EFACTURA-ORG-PARTY-04` Contact telephone number must be no more than 100 characters long (BR-RO-L100)
`emails`	Email within length	`GOBL-RO-EFACTURA-ORG-PARTY-05` Contact email address must be no more than 100 characters long (BR-RO-L100)
`addresses`	Line one within length	`GOBL-RO-EFACTURA-ORG-PARTY-06` Address line 1 must be no more than 150 characters long (BR-RO-L150)
`addresses`	Line two within length	`GOBL-RO-EFACTURA-ORG-PARTY-07` Address line 2 must be no more than 100 characters long (BR-RO-L100)
`addresses`	Locality within length	`GOBL-RO-EFACTURA-ORG-PARTY-08` City must be no more than 50 characters long (BR-RO-L050)
`addresses`	Post code within length	`GOBL-RO-EFACTURA-ORG-PARTY-09` Post code must be no more than 20 characters long (BR-RO-L020)
`addresses`	ISO 3166-2:RO subdivision	`GOBL-RO-EFACTURA-ORG-PARTY-10` Country subdivision must be an ISO 3166-2:RO code, such as RO-B or RO-AB (BR-RO-110, BR-RO-170, BR-RO-210)
`addresses`	SECTOR-RO code	`GOBL-RO-EFACTURA-ORG-PARTY-11` City must be a Bucharest sector, such as SECTOR1, when the country subdivision is RO-B (BR-RO-100, BR-RO-160, BR-RO-200)

org.Item

Field	Test	Validation Code / Message
`name`	Rune length at most 100	`GOBL-RO-EFACTURA-ORG-ITEM-01` Item name must be no more than 100 characters long (BR-RO-L100)
`description`	Rune length at most 200	`GOBL-RO-EFACTURA-ORG-ITEM-02` Item description must be no more than 200 characters long (BR-RO-L200)
`attributes`	Length at most 50	`GOBL-RO-EFACTURA-ORG-ITEM-03` Item attributes must contain no more than 50 entries (BR-RO-A050)

org.Attribute

Field	Test	Validation Code / Message
Attribute	Attribute value within length	`GOBL-RO-EFACTURA-ORG-ATTRIBUTE-02` Item attribute value must be no more than 100 characters long (BR-RO-L100)
`label`	Rune length at most 50	`GOBL-RO-EFACTURA-ORG-ATTRIBUTE-01` Item attribute name must be no more than 50 characters long (BR-RO-L050)

org.Note

Field	Test	Validation Code / Message
Note	Note within length	`GOBL-RO-EFACTURA-ORG-NOTE-01` Note, with its subject qualifier when set, must be no more than 300 characters long (BR-RO-L300)
Note	Accounting reference within length	`GOBL-RO-EFACTURA-ORG-NOTE-02` Invoice line buyer accounting reference must be no more than 100 characters long (BR-RO-L100)

org.Attachment

Field	Test	Validation Code / Message
`description`	Rune length at most 100	`GOBL-RO-EFACTURA-ORG-ATTACHMENT-01` Supporting document description must be no more than 100 characters long (BR-RO-L100)
`url`	Rune length at most 200	`GOBL-RO-EFACTURA-ORG-ATTACHMENT-02` External document location must be no more than 200 characters long (BR-RO-L200)
`name`	Rune length at most 200	`GOBL-RO-EFACTURA-ORG-ATTACHMENT-03` Attached document filename must be no more than 200 characters long (BR-RO-L200)

pay.Terms

Field	Test	Validation Code / Message
`notes`	Rune length at most 300	`GOBL-RO-EFACTURA-PAY-TERMS-01` Payment terms must be no more than 300 characters long (BR-RO-L300)

pay.Instructions

Field	Test	Validation Code / Message
`detail`	Rune length at most 100	`GOBL-RO-EFACTURA-PAY-INSTRUCTIONS-01` Payment means text must be no more than 100 characters long (BR-RO-L100)
`credit_transfer`	Account name within length	`GOBL-RO-EFACTURA-PAY-INSTRUCTIONS-02` Payment account name must be no more than 200 characters long (BR-RO-L200)
`card.holder`	Rune length at most 200	`GOBL-RO-EFACTURA-PAY-INSTRUCTIONS-03` Payment card holder name must be no more than 200 characters long (BR-RO-L200)

Overview

Use Cases

Quick Start

Tax Regimes

Addons

Catalogues

Schemas (Draft 0)

Romania RO e-Factura v1.x

Sources

Scenarios

Validation Rules

​Sources

​Scenarios

​Validation Rules

Sources

Scenarios

Validation Rules