Views:

When you configure your transaction types inside LUSID you can specify one or more of the built-in 'movement types'.

Every transaction that is entered into LUSID is deconstructed into a set of underlying economic movements. Each movement has one or more movement types associated with. The movement type controls how the movement is categorised and when it is applied.

For example, on the sale of an equity you typically have two movements: a reduction in the quantity of the equity that you just sold, and an increase in your cash balance. For each movement you can control when the movement is applied using movement types. 

For the reduction in the equity you should specify the StockMovement type. This ensures the movement is first updated on the trade date and then settled on the settlement date. 

For the increase in your cash balance you could specify the CashReceivable type. This ensures the cash shows as receivable from the trade date and settled from the settlement date.

You can combine any of the movement types below to reflect the underlying movements made by a transaction type. 

An up-to-date list can be found by searching for "MovementType" in the REST API documentation. At the time of writing, these are:

  1. StockMovement: On the transaction date, updates the number of units in the instrument position (holding type P). On the settlement date, updates the number of settled units.
  2. CashForward: On the transaction date, creates two holdings of type F to represent each leg of the forward. On the settlement date, updates the cash balances (holding type B) of both currencies. Note that in a valuation, this movement type preserves the two legs of the forward.
  3. CashCommitment: On the transaction date, creates a holding of type C to reflect the commitment to settling a trade. On the settlement date, updates the cash balance (holding type B).
  4. CashReceivable: On the transaction date, creates a holding of type R to reflect the expectation of income from settling a trade. On the settlement date, updates the cash balance (holding type B).
  5. CashAccrual: On the transaction date, creates a holding of type A to reflect accrual of income from an interest-bearing instrument. On the settlement date, updates the cash balance (holding type B).
  6. CashFxForward: On the transaction date, creates two holdings of type F to represent each leg of the forward. On the settlement date, updates the cash balances (holding type B) of both currencies. Note that in a valuation, this movement type collapses the forward to a single leg.
  7. Carry:
  8. CarryAsPnl:

The following movement types are now deprecated:

  • Traded. Please use StockMovement.
  • Settlement. Please use StockMovement.
  • ForwardFx. Please use CashFxForward.
  • Commitment. Please use CashCommitment.
  • Receivable. Please use CashReceivable.
  • Accrual. Please use CashAccrual.
  • CashSettlement. Please use one of CashCommitmentCashReceivableCashAccrual.
  • FutureCash. Please use CashForward.
  • UnsettledCashTypes. Please use one of the Cash* types.