Formal notice (mise en demeure)
When a premium goes unpaid, a broker can issue a formal notice (mise en demeure) to the policyholder: a legally-recognised demand for payment, delivered as an electronic registered letter. It is the formal step that typically precedes suspending or cancelling a contract for non-payment.
A formal notice is a manual action a broker takes from the policy—it is not sent automatically as part of unpaid-invoice handling. It is available only on products where formal notice has been enabled, and only to users with permission to generate one.
How it works
- Generate the notice
Korint generates the formal-notice document for the policy from the product's template.
- Send as registered mail
Korint sends the document through AR24 as a simple electronic registered mailing (envoi recommandé électronique, ERE), which returns proof of sending, acceptance or refusal.
- Record and track
Korint records the notice as a notification on the policy and tracks its outcome—sent, accepted, refused, or not collected—as the provider reports it back.
When it's available
Formal notice is configured per product: the product must have registered mail enabled, with a sender and letter content set up, for the action to appear. Because it carries legal weight and a cost, it is a deliberate, permission-gated step rather than an automatic one.
Recipient status
Your product's configuration determines how AR24 classifies the recipient of each formal notice.
Korint reads ere.formalNotice.recipientStatus from that configuration:
| Value | Recipient |
|---|---|
particulier | An individual |
professionnel | A professional |
| Unset | A professional, using the professionnel default |
This is a product setting, not a parameter you supply when requesting a formal notice.
Korint sends the selected value in AR24's dest_statut field and keeps simple ERE delivery
(eidas=0). See the AR24 sending API
for the provider's parameters.
Sending one through the API
Send a formal notice with POST /notifications/send and a body of type: "ERE", reason: "FORMAL_NOTICE" and the policy's policyId. The letter goes to the policy's customer unless you pass a recipient (firstName, lastName, email, optional company).
The call is asynchronous: it returns a workflowRunId, and the notification appears in GET /notifications?externalId=<policyId> once the letter has been sent. To resend a letter, for example to a corrected address, call POST /notifications/send again with the same policyId and reason and the new recipient.
A product without formal notice enabled answers FORMAL_NOTICE_NOT_ENABLED; a reason with no letter defined yet answers ERE_REASON_NOT_SUPPORTED.
Related Documentation
- Managing unpaid invoices: The unpaid-payment flow this notice fits into
- Stops: Ending a contract, which a formal notice may precede