type: credit, created through the Subledger Balance API before any money moves. It carries the product’s terms at creation and, once live, Lead’s view of the current position. Fundings draw against it; your daily Balance file reporting keeps its position current.
Naming. The API object is the Subledger Balance (
subledger_balance_* IDs); in concept pages we say Balance. Future versions will standardize the name to Balance. Use the subledger_balance_* ID as the balance_id when reporting on this object in the daily Balance file.Creating a Balance
POST /v0/subledger_balances with a required Idempotency-Key header (5–255 characters). The newly created Balance is active with status_reason: active.
Two Structures
details.structure declares how the credit behaves, and it changes what’s required:
Structure-specific fields:
Rate and Servicing Fields (both structures)
The Live Position
The Balance response carries abalances object — Lead’s current view of the position, maintained from your daily reporting:
These are the same components your daily files must reconcile —
core.amount must equal the sum of its three components, and each day’s position must equal yesterday’s plus the day’s transactions (Balance Reconciliation).
Statuses
Statuses are yours to report and maintain — see Balance Statuses for the full lifecycle. A Balance cannot be reported into a terminal status while any Funding against it is still
processing (balance_cannot_be_terminal_with_processing_funding).

