BR-FR-CO-07_BT-9: The due date cannot be before the invoice date

What it means

If the invoice has a payment due date (BT-9), it must be on or after the invoice issue date (BT-2). Two cases are exempt: a deposit invoice or deposit credit note (type code 386, 500 or 503), and an invoice in the framework B2, S2 or M2 (BT-23), the already-paid frameworks. An invoice with no due date passes. The message shows both dates, the type and the framework.

Why it matters

A payment cannot fall due before the invoice exists. The French platform rejects the invoice rather than pass on payment dates that contradict each other.

How to fix it

Compare the invoice date and the due date in your software. If the due date is wrong, set it to the invoice date or later, for example the invoice date plus the payment term. If the invoice date is wrong, correct that instead. If the invoice was already paid when you issued it, it belongs in the B2, S2 or M2 framework, which skips this check.

The rule as published

La date d’échéance (BT-9), si présente, doit être postérieure ou égale à la date de facture (BT-2), sauf si la facture est de type acompte (386, 500, 503) ou si le cadre de facturation (BT-23) est B2, S2 ou M2. Valeurs actuelles : Date facture = " … ", Date échéance = " … ", Type = " … ", Cadre = " … ".

Business terms: BT-2, BT-9, BT-23

Where this rule applies