A matching creation approval workflow returns HTTP 202 with invoice_id, approval_request_id, and status PENDING.
This is a proposal, not a created invoice. Retrieve its contents using retrieve-an-invoice-creation-proposal.
For approval proposals, pass idempotency_key on the initial call and retain it across retries.
The key is optional; each call without one creates a new submission, including retries.
The key does not deduplicate legacy creation when approvals are disabled or the invoice belongs to a contract.
A rejected proposal remains closed; a deliberate new invoice uses a new key.

Rillet supports two invoice scope types: FULL and REVENUE_RECOGNITION_ONLY. The selected scope determines how the invoice is created and what information the user needs to provide.

The FULL scope is used when the invoice is generated and sent directly from Rillet. In this case, Rillet automatically assigns the invoice number.

The REVENUE_RECOGNITION_ONLY scope is intended for situations where the invoice is issued from another system and only needs to be recorded in Rillet for accounting purposes. In this workflow, users must provide the invoice number manually. Other fields can be populated based on the data imported from the external system.

For example, if your organization issues invoices through an external billing platform but tracks financials in Rillet, you should select REVENUE_RECOGNITION_ONLY. If Rillet handles the entire invoicing and sending process, choose the FULL scope.