BR-FREXT-05

Num Fact : … , Code : … - [BR-FREXT-05]-The code for the subtype of the invoice line item (EXT-FR-FE-163) must be used from the Line Status Reason code list.

Official rule text

Num Fact : … , Code : … - [BR-FREXT-05]-The code for the subtype of the invoice line item (EXT-FR-FE-163) must be used from the Line Status Reason code list.

Code : ' … ' - [BR-FREXT-05]-The code for the subtype of the invoice line item (EXT-FR-FE-163) must be used from the Line Status Reason code list.

Where the rule applies

Fatal and error findings make the invoice invalid (valid: false); warnings and information do not.

Technical check

Syntax

CII · French rules BR-FR, EXTENDED-CTC-FR (1.4.0.04)

Context

//ram:IncludedSupplyChainTradeLineItem

Test (must be true)

not(exists($subLineCode)) or (exists($subLineCode) and not(contains($subLineCode, ' ')) and contains(' DETAIL GROUP INFORMATION ', concat(' ', $subLineCode, ' ')))

Syntax

UBL · French rules BR-FR, EXTENDED-CTC-FR (1.4.0.04)

Context

(cac:InvoiceLine|cac:CreditNoteLine)

Test (must be true)

not($isSublineCode) or (((not(contains(normalize-space(cac:BillingReference/cac:InvoiceDocumentReference/cbc:DocumentStatusCode), ' ')) and contains(' DETAIL GROUP INFORMATION ', concat(' ', normalize-space(cac:BillingReference/cac:InvoiceDocumentReference/cbc:DocumentStatusCode), ' ')))))

How the API reports this rule

Every finding of POST /v1/validate carries the rule id, severity, message, location (XPath) and rule set, and links this page (docUrl):

{
  "severity": "fatal",
  "ruleId": "BR-FREXT-05",
  "message": "Num Fact : … , Code : … - [BR-FREXT-05]-The code for the subtype of the invoice line item (EXT-FR-FE-163) must be used from the Line Status Reason code list.",
  "xpath": "/…",
  "source": "schematron:france-rfe@1.4.0.04",
  "docUrl": "https://einvoice-api.eu/rules/br-frext-05.html"
}

Rule text and severity are taken unchanged from the official rule set; this page is generated from the API's configuration. Not legal advice.