> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lead.bank/llms.txt
> Use this file to discover all available pages before exploring further.

# Receivable Sale Statuses

> Lifecycle of a receivable sale, what each status and failure reason means, and how a failed sale is recovered.

Lead manages every receivable sale status. Lead creates the sale, debits your operating account, and retries a failed debit. There is no endpoint to change a status. This page explains what each status means and what you need to do.

## Lifecycle

```mermaid theme={null}
flowchart LR
    created --> settled
    created --> failed
    failed --> settled
```

On a day with nothing to buy, the sale is created already `settled`.

## Statuses

| Status | Description | Notes |
| :- | :- | :- |
| `created` | Lead created the sale. Its receivables and `purchase_amount` are fixed. | Lead debits your operating account later the same business day. Your account must hold `purchase_amount` by 4:00pm CT. A problem other than those listed under failure reasons leaves the sale `created` while Lead resolves it. |
| `settled` | Lead debited `purchase_amount` from your operating account. Terminal. | `core_transaction_id` and `settled_at` are set. The sale's receivables are now sold to you. |
| `failed` | The debit did not go through. | `failure` says why. Fix the cause and tell your Lead team. Lead then retries the debit at the same `purchase_amount`. |

## Transitions

| Transition | Triggered by | Webhook |
| :- | :- | :- |
| (none) to `created` | Lead's daily batch, at the start of the business day | `receivable_sale.created` |
| (none) to `settled` | Lead's daily batch, on a day with nothing to buy | `receivable_sale.no_receivables_for_sale` |
| `created` to `settled` | The debit succeeds | `receivable_sale.settled` |
| `created` to `failed` | The debit fails | `receivable_sale.failed` |
| `failed` to `settled` | Lead retries the debit after you fund the account, and it succeeds | `receivable_sale.settled` |

## Failure reasons

| Reason | Use when | What to do |
| :- | :- | :- |
| `non_sufficient_funds` | Your operating account did not hold enough to cover `purchase_amount`. | Fund the account, then tell your Lead team. Lead retries the debit for the same `purchase_amount`. |
| `account_closed` | Your operating account is closed. | Contact your Lead team. |

## Recovering a failed sale

1. You receive `receivable_sale.failed`. Read `failure.reason`.
2. Fix the cause. For `non_sufficient_funds`, fund your operating account with at least `purchase_amount`.
3. Tell your Lead team the account is funded.
4. Lead retries the debit. The total and member receivables are unchanged.
5. On success, the sale moves to `settled` and you receive `receivable_sale.settled`.

A failed sale does not block the next business day's sale. Lead creates it on schedule, and both debits come from the same operating account.

## Related

[The Receivable Sale Object](/v2/products/receivable-sales/receivable-sale-object) · [Receivable Sale Overview](/v2/products/receivable-sales/overview) · [The Receivable Object](/v2/products/receivables/receivable-object) · [Webhooks & Events](/api-reference/using-the-api/webhooks)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.