Skip to content

Computed / Derived — settlement — Data Flow

Why this page is structured this way: This is the field-first view for the computed/derived [settlement] pseudo-section. These fields don’t exist at KYC onboarding time; they’re produced by operations (trade execution, margin computation, settlement files, etc.). To see the same data from the destination’s perspective, jump from the atlas overview.

  • 4 unique fields in this section.
  • 4 field-destination relationships total.

Sorted by field_id, then destination.

field_idfield_namedestinationdestination_field_namedestination_formatfrequencytransformationquirks_notesspec_source
sett-auction_differenceAuction Differenceregulatory-reportsAuctionDiffNUMBER(15,2)on-eventderived from Ycollected from short-delivering member when auction rate exceeds settlement price; auction T+2NCL/CMPT/71441
sett-internal_shortage_valuationInternal Shortage Valuationregulatory-reportsInternalShortageValNUMBER(15,2)on-eventderived from Yvaluation at settlement price + 20% mark; payment due by noon on settlement dayNCL/CMPT/66779
sett-pay_in_obligationPay-in Obligationregulatory-reportsPayInObligationNUMBER(15,2)dailyderived from Yclient-level pay-in obligation in CC obligation file; gross pay-in to CC required for direct payoutNCL/CMPT/66779
sett-pay_out_amountPay-out Amountregulatory-reportsPayoutAmountNUMBER(15,2)dailyderived from Ysecurities direct-credited to client demat by CC (CDSL) or earmarked (NSDL); not via broker poolNCL/CMPT/63669

2026-05-14


AI-generated and not legal advice. See the project README for full disclaimer.