One commitment's plan of record at cost, on its own fiscal months
One commitment's plan of record at cost, in integer cents, on the commitment's own 4-5-4 fiscal months (each keyed by the calendar year-month it maps to).
The plan of record is five declared terms per category and month, planned sales, planned markdown, planned closing stock, planned intake margin and the receipts they imply, and the identity that closes on them. It is the line a variance is measured against, so the figures are what a planner typed and not what an engine would say today.
AN ABSENCE STAYS AN ABSENCE. A month with no modelled demand is null in its array, because a 0 there would read as "plan for nothing", while a month the order book expects nothing in is a measured 0. Every null carries its reason in the category's unavailable list, in a planner's words. open_to_commit is receipts needed less what is already on order, and it is the same figure the Open to buy report and the cash gate's planned_out are built from.
company_declaration carries the finance lead's cover target, in weeks, and markdown rate, in basis points, for the plan's fiscal year, served once for the grid rather than per cell. A category's plan cell may hold a different figure, and this block is how a reader tells the two apart; either figure reads null where the company has declared neither.
For the versions of this plan, frozen as they were locked, read list_plan_versions.
Scope: planning:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/commitments/{commitment_id}/money
- Auth: HTTP bearer
Path parameters
The commitment's id.
Query parameters
Named company plan supplying the rolling calendar.
Exact reviewed company plan version.
Hash of the reviewed named calendar.
Rolling only; first day of a complete fiscal period.
Rolling only; last day of a complete fiscal period, at most 24 periods.
Explicit reviewed calendar anchor; all three horizon fields required together.
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
Response
The commitment's money position.
The plan block carries what has actually been MARKED DOWN beside what was planned, on the same months. realised_markdown is at COST, the plan's own basis, which is the only pair that may be subtracted; realised_markdown_at_retail is what the season handed over at the till, beside it and never subtracted from a plan stated at cost. markdown_left_to_close_cents is the subtraction, with markdown_left_to_close_reason where it cannot be made. A month still ahead carries null and never a zero, and realised_markdown_reason says why a whole row has none -- a season that has not opened, a channel scope, or a read that could not be taken.
The order book arrives in three bands on those same months, off one scan and under one refusal. on_order is placed purchase-order money at its expected delivery month, the envelope ladder's own definition of placed. drafted is purchase-order money still in draft at the same grain: written up, no envelope consumed, and its own band because a draft is not an order. received is the delivered subset of the placed lines at the same expected delivery month, so it is the landed slice of that month's on-order figure rather than an actual-arrival series, and it is never more than on_order for a month. A month the book was read for that holds nothing in a band is a measured 0; all three bands are null together, with the reason on the category, where the book cannot answer for the scope at all.
Changes
No recorded changes to this operation across all 1 revision of this API.