Entities

Prev Next
  • Updated on Nov 6, 2025
  • Published on Aug 19, 2024
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...
  • Updated on Jul 14, 2025
  • Published on Aug 19, 2024
An identifier is a set of attributes that combine to identify a LUSID entity in some way. See a list of identifiers for every entity . Most entities have an identifier consisting of a scope and a code . The code must be unique within the scope....
  • Updated on Dec 15, 2025
  • Published on Aug 19, 2024
Every entity in LUSID must have at least one unique identifier. Most entities in LUSID are identified by a scope and a code . The code must be unique within the scope. A scope is therefore a logical partition enabling two entities with the sam...
  • Updated on Dec 15, 2025
  • Published on Aug 19, 2024
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. More on date formats . Cut labels allow clients to s...
  • Updated on Mar 8, 2026
  • Published on Aug 20, 2024
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...
  • Published on Aug 19, 2024
To avoid any confusion around parsing of dates/times, LUSID expects all timestamps to be in the standard format documented by the W3C  here .  This format includes the date followed by a time with precision down to 6 decimal places in the ...
  • Updated on Jan 29, 2025
  • Published on Aug 19, 2024
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...
  • Updated on Oct 24, 2026
  • Published on Aug 20, 2024
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, a fund, or for lookthrough i...
  • Updated on Sep 18, 2024
  • Published on Aug 19, 2024
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...
  • Updated on Sep 4, 2026
  • Published on Aug 19, 2024
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...
  • Updated on Jul 22, 2025
  • Published on Aug 19, 2024
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...
  • Updated on Jul 22, 2025
  • Published on Aug 19, 2024
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...
  • Updated on Feb 12, 2025
  • Published on Aug 19, 2024
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 ...