Skip to content

Latest commit

 

History

History
34 lines (24 loc) · 2.42 KB

A2BMovementRecord.md

File metadata and controls

34 lines (24 loc) · 2.42 KB

A2BMovementRecord

A2B Movement Record - shows A2B category based changes relating to a specific movement

Properties

Name Type Description Notes
portfolioId ResourceId [optional]
holdingType String The code for the type of the holding e.g. P, B, C, R, F etc. [optional]
instrumentScope String The unique Lusid Instrument Id (LUID) of the instrument that the holding is in. [optional]
instrumentUid String The unique Lusid Instrument Id (LUID) of the instrument that the holding is in. [optional]
subHoldingKeys Map<String, PerpetualProperty> The sub-holding properties which identify the holding. Each property will be from the 'Transaction' domain. These are configured on a transaction portfolio. [optional]
currency String The holding currency. [optional]
transactionId String The unique identifier for the transaction. [optional]
movementName String The name of the movement. [optional]
effectiveDate OffsetDateTime The date of the movement. [optional]
units java.math.BigDecimal The number of units of the instrument that are affected by the movement. [optional]
start A2BCategory [optional]
flows A2BCategory [optional]
gains A2BCategory [optional]
carry A2BCategory [optional]
end A2BCategory [optional]
properties Map<String, Property> The properties which have been requested to be decorated onto the holding. These will be from the 'Instrument' domain. [optional]
groupId String Arbitrary string that can be used to cross reference an entry in the A2B report with activity in the A2B-Movements. This should be used purely as a token. The content should not be relied upon. [optional]
errors List<ResponseMetaData> Any errors with the record are reported here. [optional]

Back to Model list • Back to API list • Back to README