A simplified invoice can no longer name an identified recipient

ChangelogSep 22, 2026Breaking

BeeL. no longer issues a simplified invoice that names an identified recipient: an invoice that identifies its recipient is issued as a standard one, whatever the amount. A simplified invoice that named one used to be accepted, up to 3,000 €. It is now rejected on create and on update.

This is a BeeL. rule. A simplified invoice without an identified recipient, the ticket for a final consumer, works as before.

What breaks

The trap: a customer_id counts too. The check runs on the resolved recipient, so a SIMPLIFIED invoice that points at a stored customer with a NIF is rejected, even if the body carries no NIF of its own.
Both writes are affected. POST a new invoice, or PATCH a draft, with type: SIMPLIFIED and a recipient carrying nif or alternative_id: 400 SIMPLIFIED_INVOICE_FORBIDS_IDENTIFIED_RECIPIENT, where it used to succeed. Send type: STANDARD with the full recipient instead.

Does this affect you?

Grep your client for SIMPLIFIED. Any path that sets it and also sends nif, alternative_id or a customer_id for a business customer needs to switch to STANDARD.

What else changed

The cap is unchanged: 3,000 € (VAT included) on a simplified invoice without an identified recipient, as before (SIMPLIFIED_INVOICE_EXCEEDS_LEGAL_LIMIT). The RD 1619/2012 sets 400 € as the general limit (art. 4.1) and 3,000 € for the operations listed in its art. 4.2, such as retail and hospitality; which one applies depends on the issuer's activity.
Invoices generated from a Stripe connection are not affected. They follow the connection's own simplified threshold, as described in the Stripe guide.
Correctives are not affected.

Endpoints

POST/v1/companies/{company_id}/invoices400 SIMPLIFIED_INVOICE_FORBIDS_IDENTIFIED_RECIPIENT
PATCH/v1/companies/{company_id}/invoices/{invoice_id}Same check on the resulting draft

Where to go next

Simplified vs standard SIMPLIFIED_INVOICE_FORBIDS_IDENTIFIED_RECIPIENT Create an invoice