The AccountType property is used to define the GL account type for members of the Account Dimension. Setting this property will define the account aggregation behavior of a member within an Account Hierarchy. Examples of values for this field include, but are not limited to, the following: Unit, Header, Expense, Liability, Equity, Asset, Cash, Income, and Rate.
Account Type Behavior
Account aggregation is determined by the relationship of a child member to its parent member. For instance, an Account member that is a Credit will sum to its parent if its parent is also a Credit. However, an Account member that is a Credit will subtract from its parent if its parent is a Debit.
The table below shows the aggregation behavior between a child member and its parent in the Account Dimension.
When an Account member is tagged with an Account Type, the system will then know how to handle its aggregation behavior. The table below lists out the associated properties by each Account Type.
Let’s analyze an example Account hierarchy with the following Account Types specified. In order to determine how the aggregation will work for each member, we first need to identify the child and parent members in the hierarchy.
Once the child and parent members are identified, you can look up the Debit/Credit properties for each member based on the Account Types table. Once you have the child and parent Debit/Credit properties identified, follow the Debit/Credit Aggregation Rule to determine the correct aggregation behavior.