Skip to main content
A receivable sale is the daily purchase of your program’s loans from Lead. Each business day, Lead groups every receivable that has reached its sale date into one receivable sale, fixes the total, and debits it from your operating account in a single entry. You don’t accept or approve the sale. Lead creates and settles it on a fixed schedule. The receivable sale replaces the daily Sales Request and Sales Response file exchange. The daily grain and whole-sale settlement work as they do today. What changes is that you read the sale and its receivables through the API and get webhooks instead of exchanging files.
The Receivable Sales API is currently in preview with a planned beta release in January 2027. Preview APIs are not yet available in sandbox or production and can change before beta. Use these pages to plan an integration, not to build one. Once released in beta, it will be available to all partners in sandbox, and in production for select programs. Beta APIs may change without a version increment, and changes will be announced in advance. See Versioning and backwards compatibility.

​
The daily schedule

Your operating account must hold the full purchase_amount by 4:00pm CT on the sale’s business day. Settlement is all or nothing: if the account can’t cover the full purchase_amount, the whole sale fails. Lead creates a receivable sale every business day, even when there is nothing to buy. On those days the sale is created already settled, with a purchase_amount of 0, and Lead sends receivable_sale.no_receivables_for_sale. This lets you confirm the day’s sale ran even when there was nothing to buy.

​
How receivable sales relate to the rest of the model

  • Receivables. A receivable sale contains many receivables. Each member receivable’s receivable_sale_details.receivable_sale_id points to the sale. List them with GET /v2/receivables?receivable_sale_id={id}. See Receivable.
  • Core account. Lead debits your operating account, which is a core account. See Core Account.
  • Core transaction. A settled sale’s core_transaction_id points to the debit, and will have a type receivable_sales.

​
What you can do

​
Authentication

  • receivable_sale/read for all Receivable Sales endpoints. The API is read only, so there is no read_write scope.
Webhooks:

​
What you cannot do

  • Create, accept, or reject a receivable sale. Lead creates and settles every sale.
  • Buy part of a sale. Settlement covers the whole purchase_amount or nothing.
  • Retry a failed sale yourself. Your Lead team retries it after you fund your account.
  • Change a sale after it is created. A receivable that becomes eligible after the sale is created joins the next business day’s sale.

​
Operating the daily sale

  • Reconcile by sale, then by receivable. Book the sale’s purchase_amount against the debit, then list its receivables to book each loan.
  • Fund your operating account by 4:00pm CT. You can estimate the amount before the sale date by listing the receivables due that day, and the exact amount is fixed once the sale is created.
  • Treat receivable_sale.no_receivables_for_sale as a success.

​
In this section