This action validates the given settlement report and accepts it for partner invoice generation. The settlement report must have a B2B invoice processor configured on its operator and must not already have been invoiced. Both balance directions are eligible. When expenses are greater than or equal to revenue, the action produces a regular partner invoice on which the operator is the seller. When expenses are lower than revenue, the balance is in the partner's favor and the action produces a self-billing invoice on which the partner is the seller.

Invoice generation runs asynchronously after the request is accepted; the 202 confirms acceptance of the request, not the outcome. Poll the settlement report read endpoint:

• Generated — partnerInvoiceId is present and identifies the new partner invoice.
• Not generated — generation failed after acceptance. No partner invoice record exists and partnerInvoiceId remains absent. Causes include a missing or invalid tax identification number on the partner, a report currency the operator's B2B invoice processor does not support, a tax rate not configured on that processor, and a report whose invoiceable total nets to zero. The failure is reported to the operator through the platform; poll with a bounded number of attempts rather than indefinitely.

Where the operator's B2B invoice processor certifies documents with a fiscal authority, partnerInvoiceId appearing means the invoice record exists — not that a legally issued document exists. Certification runs as a second asynchronous stage; read fiscalization.status on the single-invoice endpoint to follow it to certified or failed.