A DETAIL line has no quantity unit of measure
In the extended profile, a line of subtype DETAIL — or without a subtype — must carry the unit code of its invoiced quantity (BT-130).
Only the issuer holds this value: Factlint reports it and never fabricates it. 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-FREXT-23]-An Invoice line (BG-25) shall have an Invoiced quantity unit of measure code (BT-130), 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.
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
A quantity without a unit compares to nothing: three hours, three pieces or three pallets do not cost the same. The code is most often missing because the item master carries none for services. 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
Add the unit code — C62 for a unit, HUR for an hour — or give the line the GROUP subtype if it only structures. Factlint does not choose a unit.
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.
XML correction example
<cbc:InvoicedQuantity>2</cbc:InvoicedQuantity>
<cbc:InvoicedQuantity unitCode="HUR">2</cbc:InvoicedQuantity>