01
ACT/360, ACT/365, and day-count conventions — Measurement contract
Define one observation and decide whether cost is recognized at order, fill, exit, statement, or another event. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
02
ACT/360, ACT/365, and day-count conventions — Unit ledger
State price unit, contract quantity, P&L currency, account currency, and one-way or round-trip scope in separate fields. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
03
ACT/360, ACT/365, and day-count conventions — Timestamp alignment
Place order, fill, conversion, and charging events on one explicit clock rather than relying on a quoted schedule time. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
04
ACT/360, ACT/365, and day-count conventions — Baseline scenario
Store gross profit, total cost, net profit, and break-even under the conditions regarded as ordinary. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
05
ACT/360, ACT/365, and day-count conventions — Conservative scenario
Replace central inputs with adverse but plausible quantiles, quote sides, and extra charges. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
06
ACT/360, ACT/365, and day-count conventions — Stress scenario
Calculate low-frequency boundaries such as holidays, discontinuities, specification changes, and liquidity shocks separately. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
07
ACT/360, ACT/365, and day-count conventions — Missing data and corrections
Do not turn unknown values into zero; retain an unresolved state and replace it when a statement or correction arrives. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
08
ACT/360, ACT/365, and day-count conventions — Statement reconciliation
Decompose model-to-statement differences into rate, base amount, event count, rounding, and timestamp effects. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
09
ACT/360, ACT/365, and day-count conventions — Version retention
Save fee schedules, contract specifications, calendars, conversion rules, and equations with effective dates. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.
10
ACT/360, ACT/365, and day-count conventions — Decision record
Record which input changed the conclusion and what action followed, with a concise economic reason. For ACT/360, ACT/365, and day-count conventions, bind the boundary “Calculate with an explicit basis and never compare headline annual rates alone; treat a basis change as a separate net-P&L scenario.” to the required evidence “Annual rate, notional, actual days, day-count basis, simple or compound treatment, timing, rounding and the schedule definition.”.