A transaction is an economic change to a portfolio.
Transactions can be one sided e.g. cash inflow, or two sided for example an equity trade purchasing stock and settling cash.
This model is intended to be flexible and customisable by the client. A client configures transaction types in LUSID which maps from the fields and properties on the Transaction onto a set of movements which represent the economic changes.
A minimal set of mandatory transaction fields have been defined for each domain type. The transaction data model can be extended by adding additional properties to a transaction.
LUSID comes pre-configured with a number of default transaction types. These are intended to cover a standard usage of LUSID, and can also be used as a template for implementing your own transaction type schemes.
You can find further details on the mandatory transaction fields and see how to upsert them into your portfolios in our technical documentation.