Entities

LUSID's data model is designed to be flexible rather than constrain your data to our view of the world. We require you to model only a small set of real-world objects as entities.  For example: An instrument represents a real-world financ...

Most entities in LUSID reside within a logical data partition known as a scope . A scope is an identity namespace allowing two entities with the same code to co-exist in individual address spaces. For most entities, therefore, the scope forms par...

All entities in LUSID have a  Code  which is used to uniquely identify each instance of the entity. The code must consist entirely of the following characters: Lowercase and uppercase letters Numbers Dash ("-") Underscore ("_")...

In order to simplify the usage of LUSID in a global scenario (with times across multiple timezones), LUSID allows you to pre-configure "cut labels" which can then be used in place of timestamps. Cut labels allow clients to specify a timestamp to th...

You are required to specify a tenor in various places in LUSID, for example in a flow convention or index convention , as part of a complex market data object such as a FX forward curve, and also optionally in a recipe to specify a 'look back...

A transaction type is one of the most important data structures in LUSID. It defines the precise economic impact of all the transactions belonging to that type on holdings . Note the following: A transaction must have a transaction type. If i...

A recipe is a hierarchical, modular document containing rules that govern numerous LUSID operations. See how to create or generate a recipe . You require a recipe to: Generate a valuation report, for a portfolio or a fund. Perform a reconcil...

An event in LUSID can refer to either a system event or to an instrument event (these are not the same). System events LUSID emits a  system event  when an internal operation completes. This can be within LUSID itself, or in one o...

LUSID has a set of built-in entities that represent real-world objects central to the task of managing investment data, such as portfolios, instruments, quotes and so on. You can create a custom entity to model a real-world object or concept th...

You can create a legal entity  to represent an institution of interest to your LUSID domain, for example an international bank, investment firm or pension company. See a list of the built-in entity types . Note the following: A legal enti...

You can create a person entity to represent a person of interest to your LUSID domain, for example a portfolio manager, trader or sales representative. See a list of the built-in entity types . Note the following: A person entity must have at...

You can create a relationship between any two of the following types of  entity  in LUSID, to represent a real-world connection between them: Portfolio Portfolio Group Legal Entity Person Instrument ...