Settlement
The Settlement entity in Treasury.
A settlement is the daily roll-up of money the rail actually moved on your behalf. It groups one or more completed payouts (and any reversals, fees, and adjustments tied to them) into a single net amount that lands in — or is debited from — your funding bank account. One settlement maps to one bank-statement line item, which is what you'll ultimately reconcile against in your accounting system.
Lifecycle
OPEN— Created automatically when the first eligible event of the period occurs. New payouts continue to accrue into it.APPROVED/PROCESSING— Closed for new entries (either because the schedule rolled over or you calledPATCH /settlements/{id}to close it manually) and queued for funding.FUNDED— Net amount has hit your funding account. Thesettlement.createdwebhook fires when the record reaches this state, so you can post the journal entry on receipt.EXCEPTION— Held for review (e.g. fee miscalculation, reversed funding).is_exception: trueon the record; check theexceptionfield for context.
Relationships
Each settlement aggregates the Payouts and reversals that completed
within its window. It is per-currency (currently USD only) and per-funding
Bank Account — if you fund payouts from two different
business accounts you'll see two settlement streams. Use
GET /treasury/transactions/{id}/settlement to walk from a single payout back
to the settlement that contained it.
Fields that matter
id(string) — settlement ID. Stable.status(string) — current lifecycle state (see above).net_amount(integer, USD cents) — the line item that hits your bank statement. Already nets out fees, refunds, and adjustments.total_amount/total_fees(integer, USD cents) — gross movement and Easy's fee, useful for revenue reconciliation.currency(string) —"USD"today.is_exception(boolean) — true means manual review required.auto_close_time(stringISO-8601) — when this settlement will roll over if not closed earlier.