Back to the error catalogue
BR-FREXT-26BT-146
blocked

A DETAIL line has no item net price

In the extended profile, a line of subtype DETAIL — or without a subtype — must carry the item net price (BT-146).

A financial field: the expected value is computed and offered, never written into the document — the correction is the issuer's to make. Test your invoice to find out whether it is affected.

The message your validator prints

Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.

[BR-26]-Each Invoice line (BG-25) shall contain the Item net price (BT-146), if the "Subtype of invoice line item" (EXT-FR-FE-163 / BT-X-8) has the value "DETAIL" or is not specified.

Quoted from schematron-fnfe 1.4.0.03, licensed under Apache-2.0.

Common searches around this code

These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.

BR-FREXT-26 A DETAIL line has no item net priceBR-FREXT-26 FNFE Schematron packageBR-FREXT-26 BT-146[BR-26]-Each Invoice line (BG-25) shall contain the Item net price (BT-146), if the "Subtype of invoice line item" (EXT-FR-FE-163 / BT-X-8) has the value "DETAIL" or is not specified.BR-FREXT-26 correction

Test your file with this error in mind

Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.

To automate this check in an ERP flow, call the validation API and link every returned code to its public page.

Why this error happens

Quantity, price and net amount form a triangle the recipient recomputes; without a price, it can neither verify the line nor match it with an agreed tariff. The extended profile only exempts structural lines. It only applies to documents that declare the EXTENDED-CTC-FR profile — the profile sheet replaces the CEN package and adds its own rules for hierarchical lines.

How to fix it

Fill in the price in your system, or give the line the GROUP subtype. Factlint never writes a price: rule 1 would at most propose it.

Severity returned by the rule set

Blocking since 1 September 2026: the current base, `fr-2026-09`, seals the FNFE 1.4.0.03 artefact in fatal mode, and it is the one the pinned engine applies by default. An invoice issued in August 2026 is judged against `fr-2026-08`, where the same rule comes out as a warning — which already rules out a “compliant” verdict. The API returns the severity of the rule set pinned for the judged invoice.

Reason it is blocked:

financial_field_policy

XML correction example

BEFORE (invalid)
<cac:Price></cac:Price>
AFTER (compliant)
<cac:Price><cbc:PriceAmount currencyID="EUR">124.17</cbc:PriceAmount></cac:Price>