The buyer's electronic address is missing

BT-49 carries the buyer's electronic address, which routes the invoice to their platform.

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.

cii
BR-FR-12/BT-49 : Le BT-49 est obligatoire. Valeur actuelle : BT-49=" ".

ubl
[BR-FR-12/BT-49] : Le BT-49 (cbc:EndpointID) est obligatoire. Valeur actuelle : BT-49=" ".

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-FR-12 The buyer's electronic address is missingBR-FR-12 French BR-FR-CTC rulesBR-FR-12 BT-49BR-FR-12/BT-49 : Le BT-49 est obligatoire. Valeur actuelle : BT-49=" ".BR-FR-12 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.

Open the validator See the API

Why this error happens

This address is how the recipient's platform is found in the directory. Without it the invoice is syntactically correct but cannot be routed — a rejection downstream, not at generation time.

How to fix it

Fill in the electronic address agreed with your customer, together with its identification scheme. It belongs to the commercial relationship and cannot be derived from any other field.

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

BEFORE (invalid)

<!-- ram:BuyerTradeParty/ram:URIUniversalCommunication absent -->

AFTER (compliant)

<ram:URIID schemeID="EM">[email protected]</ram:URIID>