Auditing settlement status

Updated
  • Updated on Sep 17, 2025
  • Published on Sep 16, 2025
Prev Next

Imagine we have a Buy transaction of 100 units of BP @ £5 per share:

  • The transaction date is 1 September 2025 at 00:00:00.

  • The contractual settlement date is 5 September 2025 at 00:00:00.

For the purposes of this example, LUSID is configured as follows:

  • The Buy transaction type has a settlement mode of External for both the StockMovement and CashCommitment movement types.

  • The parent portfolio has Automatic set for stock settlement method but Instructed for cash settlement method.

If we examine the Portfolio Management > Holdings dashboard (or call the GetHoldings API) on the transaction date, we see both stock and cash holdings are unsettled, as expected:

If we fast-forward to the contractual settlement date, we see that LUSID has automatically settled the stock holding in full, but the cash holding remains unsettled and the units are now overdue. Note the holding type is also still classified as a temporary, unsettled Cash Commitment:

We can call the GetTransactionSettlementStatus API for this transaction on the contractual settlement date to understand the cause. For the cash holding we can see that:

  • The settlementMode on the transaction type is External (in yellow) and configuredSettlement on the portfolio is Instructed (in green), so LUSID has negated the contractual settlement date.

  • No settlementInstructions have been received (in red), so the status remains Unsettled (in blue):