> ## 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. # The Receivable Object > Field-level reference for the Receivable object, its amounts and source details, and how to follow a receivable from origination into a receivable sale. A receivable is Lead's claim on a loan your program originated while that loan is on Lead's books. Lead creates it when a funding posts or a card network settles. You read receivables with `GET /v2/receivables` and `GET /v2/receivables/{receivable_id}`. ```json theme={null} { "id": "receivable_9TbQ3wEr5YuIoPaSdFgHjKlZxCv", "currency_code": "USD", "type": "user_credit_balance", "held_for": "sale", "origination_date": "2026-06-04", "amount": 251000, "amount_breakdown": { "principal": 250000, "interest": 500, "interest_rate": "9.99", "fees": 500 }, "receivable_sale_details": { "receivable_sale_id": null, "request_date": "2026-06-05" }, "user_credit_balance_details": { "user_credit_balance_id": "user_credit_balance_1HCpXwx2EK9oYluWbacgeCnFcLf", "user_credit_transaction_id": "user_credit_transaction_2JdQyVm8LpT4nWxZ7aBcEfGhKjR" }, "created_at": "2026-06-04T08:05:00Z", "updated_at": "2026-06-04T08:05:00Z" } ``` ## Fields | Field | Type | Description | | :- | :- | :- | | `id` | string | Unique identifier, prefixed `receivable_`. | | `currency_code` | enum | ISO 4217 code. `USD` only. | | `type` | enum | What created the receivable: `user_credit_balance` or `card_network_settlement`. Never changes. See [Types](#types). | | `held_for` | enum | Whether the loan was originated to sell (`sale`) or is kept on Lead's balance sheet (`investment`). The API returns only `sale` today. Accept other values. | | `origination_date` | date | The date the loan originated. For `card_network_settlement`, the settlement date. For `user_credit_balance`, the date the source user credit transaction was created. | | `amount` | integer | The receivable's total, in minor units. Equals `principal` + `interest` + `fees`. Fixed once the receivable is created. | | `amount_breakdown` | object | What makes up `amount`. See [The amount\_breakdown block](#the-amount-breakdown-block). | | `receivable_sale_details` | object | When the receivable is sold, and in which receivable sale. See [The receivable\_sale\_details block](#the-receivable-sale-details-block). | | `user_credit_balance_details` | object | Present when `type` is `user_credit_balance`. Omitted otherwise. | | `card_network_settlement_details` | object | Present when `type` is `card_network_settlement`. Omitted otherwise. | | `created_at`, `updated_at` | timestamp | RFC 3339, UTC. `updated_at` changes when Lead sets `receivable_sale_id`. | ## Types * **`user_credit_balance`.** Created from a user credit transaction that drew principal on a user credit balance, such as the `funding` user credit transaction Lead posts when a funding posts. One receivable per draw. * **`card_network_settlement`.** Created from a card network settlement of your program's card spend. One receivable per settlement. ## The amount\_breakdown block | Field | Type | Description | | :- | :- | :- | | `principal` | integer | Principal, in minor units. | | `interest` | integer | Borrower interest owed, in minor units. `0` when the source carries no interest. | | `interest_rate` | string or null | The borrower's annual interest rate as a decimal percent. `"9.99"` means 9.99%. This is a rate, not an amount. `null` for `card_network_settlement`. | | `fees` | integer | Borrower fees owed, in minor units. `0` when the source carries no fees. | `amount` is fixed when the receivable is created. A refund, payment, or charge-off reported during the hold period does not change it. You settle those with your borrower, and the receivable sells at its original amount. `amount` is what you pay Lead for the loan. It does not include partner-owed fees and premiums. Lead bills those separately under your program agreement. ## The receivable\_sale\_details block | Field | Type | Description | | :- | :- | :- | | `request_date` | date or null | The business day the receivable is due to be sold. Lead sets it from `origination_date` plus your program's hold period. Once the receivable joins a receivable sale, this matches the sale's `request_date`. | | `receivable_sale_id` | string or null | The receivable sale this receivable belongs to. `null` until the sale is created. | If Lead receives origination data late, `origination_date` can be earlier than `created_at`. If the hold period has already passed, the receivable joins the next receivable sale. ## The user\_credit\_balance\_details block | Field | Type | Description | | :- | :- | :- | | `user_credit_balance_id` | string | The user credit balance the loan was drawn on. | | `user_credit_transaction_id` | string | The user credit transaction that drew the principal. For a funding, this is the `funding` user credit transaction. | ## The card\_network\_settlement\_details block | Field | Type | Description | | :- | :- | :- | | `settlement_reporting_id` | string | Your program's reporting ID for the settlement on that network. | | `card_network` | enum | `visa`, `mastercard`, `pulse`, `accel`, `maestro`, `tabapay`, `amex`, `star`, or `interlink`. | | `settlement_date` | date | The network settlement date. | ## Lifecycle A receivable has no `status` field. Read where it is from `receivable_sale_details` and the receivable sale it belongs to. | Stage | How to tell | | :- | :- | | Waiting for sale | `receivable_sale_id` is `null`. `request_date` is the day it will be sold. | | In a receivable sale | `receivable_sale_id` is set. Membership and amounts are now fixed. | | Sold | The receivable sale has `status: settled`. | The receivable sale is the authority on whether a receivable has been sold. If the sale fails, its receivables stay in that sale, and Lead retries the sale at the same total. See [Receivable Sale Statuses](/v2/products/receivable-sales/statuses). ## List and retrieve `GET /v2/receivables` returns your program's receivables, most recently created first. Filters: * `type`. `user_credit_balance` or `card_network_settlement`. * `receivable_sale_id`. Receivables in one receivable sale. * `request_date`, `request_date[after]`, `request_date[on_or_after]`, `request_date[before]`, `request_date[on_or_before]`. Receivables due to be sold on a day or in a range. * `limit` (1 to 100, default 10), `starting_after`, `ending_before`. Cursor pagination. Cursors are receivable IDs. `GET /v2/receivables/{receivable_id}` returns one receivable. It returns `404` if the ID does not exist or belongs to another program. ## Sandbox For a funding program, create a funding and advance it with `POST /v2/fundings/{id}/advance`. Lead creates the receivable. For a card program, call `POST /v2/simulate/card_network_settlements` to simulate a settlement. ## Related [Receivable Overview](/v2/products/receivables/overview) · [The Receivable Sale Object](/v2/products/receivable-sales/receivable-sale-object) · [The Funding Object](/v2/products/fundings/funding-object) · [The User Credit Balance Object](/v2/products/user-credit-balance/user-credit-balance-object) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.