Legal Entity Dimension


Return to Models Overview

Elements in the Legal Entity dimension represent the companies within a group. All legal entities should aggregate to the grand total element Total Group. The elements may be structured by a hierarchy of intermediate levels or be directly assigned to Total Group.

In addition to the company elements, there are two elements with a special meaning:

  • ~ (Not Applicable): data that is not broken down by a legal entity is stored on this element. This type of element is sometimes also referred to as a “dummy element”.
  • Unassigned: this is a bucket that should be empty most of the time. It may refer to legal entities that are missing when data is imported from a source system yet are in the legal entity dimension. During the data load the missing elements are created on the fly under the parent Unassigned. When the dimension is maintained later, the new elements will be relocated to their correct parent.

The elements Total Group, ~, and Unassigned should not be deleted. Otherwise, the reports using these elements would be broken.

New legal entities can also be created using an existing entity as a source. See Legal Entity Administration Report.

The legal entity elements can be configured through their attributes:




Readable name of the legal entity, visible in the report. Localized translations can be provided. There is no hard-coded behavior implemented upon this name. (string)


Combination of element name, a dash (“ – “), and the localized name attribute. (calculated, string)


Country of the legal entity. Valid values are two-letter codes defined by ISO 3166, e.g. US for United States of America. (string)

On aggregated levels where all descendants have one common country, this country code should also be assigned to the aggregated element. For aggregations of legal entities in mixed countries, this attribute must be empty.


Currency of the legal entity. Valid elements are three-letter codes defined by ISO 4217, e.g. USD for US dollar. (string)

On aggregated levels where all descendants have one common currency, this currency code should also be assigned to the aggregated element. For aggregations of legal entities using mixed currencies, this attribute must be empty,

For  more information, see the articles Currency Conversion and Conversion from Implicit Local Currency


Number of months that tax payments are delayed. For example, the number “1” would indicate taxes paid in the next consecutive sales month. This feature is used by a business logic planned for future models.

Sign Standard

Sign representation of financial figures in the local accounting systems. This attribute can be used by interfaces importing figures from databases or files into the Jedox model. By comparing this value with the model setting Sign Standard, sign reversal can be automatically handled.

Valid values are a four-character sequence with either + or -. The characters represent the sign of stored amounts for

  1. Assets
  2. Equity and Liabilities
  3. Income
  4. Expenses

Example: in SAP ERP, assets and expenses are internally stored as positive figures, while equity, liabilities, and income are stored as negative figures. The sequence for a SAP ERP-based source would thus be +--+.