This page describes how accounts are handled in Studio. Studio is designed to handle complex legal entity and account structures.

Topology

Below is a visual representation of how organizations, entities and accounts are organized. An organization is a collection of entities, and an entity is a collection of accounts. An entity is a legal entity, which means it can be an individual or a company with an issued tax identifier.

.
└── org
    ├── entity-1
    │   ├── account-1.1
    │   ├── account-1.2
    │   └── account-1.3
    ├── entity-2
    │   ├── account-2.1
    │   ├── account-2.2
    │   └── account-2.3
    └── entity-3
        └── account-3.1

Attributes

There are certain important attributes for an organization, entity, and account that are helpful to know, particularly when dealing with Studio's API.

• An organization has a client_code which is a shorthand way to identify it. For example, ACME Investments LP might have a client_code of ACME
• An org has a unique ID that is used to uniquely refer to it, as an alternative to client_code
• A legal entity has a unique ID that is used to uniquely refer to it
• An account has a unique identifier account_id, consisting of only digits that is used to uniquely refer to it.
• An account also has an identifier account_number that can either be the same as the account_id or be a different unique value containing both characters and digits. This identifier can be used in place of account_id where in requests to the Studio API that require account_id as an input parameter.