Accounts Notes

· Describe the steps to create and add to the Chart of Accounts.

Accounts can be added to a group by selecting Edit > Insert > Account in the Accounts window.

· Describe the Global Account Group and identify valid members.

The Global account group contains account information used by all the entities in a category. This reduces the storage space applications require and the amount of data that needs to be maintain. The most common use of the Global account group is to store currency exchange rates though it can also be used to store other rates, for example imperial/metric conversions rates.

· Identify what effects adding, deleting, and moving accounts have on the application.

Action	Effect
Adding	The account is added to chart of accounts.
Deleting	The account, account attributes and data are deleted.
Moving	The Account, account attributes and data are moved. In Hyperion Enterprise accounts are moved by selecting Edit > Copy not Edit > Cut as you would expect.

· Describe the effect and appropriate use of account attributes such as consolidate, currency, codes, scale, and dynamic view.

Attribute	Effect
Decimal	Determines how many decimal places are displayed in the Data Entry and Database windows.
Scaled	Determines if the account values can be scaled in the Data Entry and Database windows. Accounts containing monetary values are normally scaled but it does not make sense to scale some types of values, for example ratios.
Consolidated	Determines if the account is consolidated. Accounts containing monetary values are normally consolidated but it does not make sense to consolidated some types of values, for example ratios.
Currency	Determines if the account is a currency account. Currency account are converted on the appropriate exchange rate but non-currency account, for example headcount, are not converted.
Dynamic View	Determines if the account is a dynamic view account. Dynamic view accounts are normally used for ratios and percentages.
Code	Determines codes for accounts.

· Describe the business intelligence of the attributes income, expense, asset, liability, flow, and balance and when you should use and not use these attributes, identify valid account attributes.

These attributes effect how movements and debits and credits are displayed. Assets, Liability and Balance attributes are used for accounts for which you do not want to see movements. These are normally balance sheet and statistics accounts. Income, Expense and Flow types are used for accounts for which you want to see movements. These are normally profit and loss accounts.

Income and Liability attributes are used for accounts which normally have credit (negative) balances which you want to display as positive numbers. Expense and Asset types can be used for account which normally have debit (positive) balances which you want to display as positive numbers.

· Describe the effect of editing account attributes.

Decimal, Scaled, Consolidated, Currency and Dynamic View attributes can be changed at any time even after data has been input. The Type attribute cannot be changed after data has been input because data is not updated to reflect the change. This implies that Hyperion Enterprise does not store data as absolute debits and credits.

· Describe the effect of adding a sub-account table to an existing account and deleting a sub-account table from an existing account.

When a subaccount table is added to a major account that has not previously had a subaccount the data in the major account is deleted. When a subaccount table is deleted from a major account neither the subaccount or major account data are deleted.

· Describe the effect of maintaining system generated sub-account tables, (CURRENCY, INTERCOMPANY).

The CURRENCY and INTERCOMPANY system generated sub-account tables cannot be manually maintained.

· Describe how to create a sub-account table and attach it to a major account.

Subaccounts are created in the Subaccounts window. They are attached to accounts on the Subaccount Table table of the Accounts window.

· Identify the effect on the chart of account size when Subaccounts are added and deleted.

Stage	Accounts	application.exa	Data Directory
Simple application with 5 major accounts	5	537,496	26,008
Add subaccount table with 100 subaccounts to 5 major accounts	500	564,060	26,008
Enter data in 1 subaccount per major account	500	564,060	43,448
Enter data in 100 subaccounts per major account	500	564,060	63,944
Delete subaccount table from 5 major accounts	5	564,060	63,944
Consolidate application	5	564,060	63,944

· Describe the system effects that fixed and validated Subaccounts have.

Fixed subaccounts always appear in the Data Entry and Database windows, whether or not they contain data. Validated subaccounts appear in the Data Entry and Database windows only if they contain data. New validated subaccounts can be added by selecting Edit > Insert Subaccounts in the Data Entry window.

· Describe how to build fixed and dynamic account lists.

Fixed lists are created by selecting the Fixed attribute when a list is created. Accounts are then added to fixed lists by selecting individual accounts or groups of accounts. Once a fixed list has been created it is not automatically updated when new accounts are added to the chart of accounts. Dynamic lists are created in the same as fixed lists expect that individuals accounts cannot be added. Once a dynamic list has been created accounts are automatically added to the list when they are added to the groups in the list.

· Identify where account lists may be used.

Hyperion Allocations
Hyperion Enterprise Data entry module
Hyperion Enterprise Database module
Hyperion Reporting

· Describe how to build account conversion tables.

Select Navigate > Account Conversion Tables and create a new table by pressing New.
Enter a name and description for the table and whether it is a load and/or extract table and press OK.
Enter the mappings for the table

· Given an exhibit, determine if the exhibit represents a load table or an extract table, or both.

Load tables can have many to one mappings:

External	Enterprise	ADD/SUB
revenue_new_cars	revenue	ADD
revenue_used_cars	revenue	ADD
revenue_parts	revenue	ADD
revenue_forecourt	revenue	ADD

Extract tables can have one to many mappings:

External	Enterprise	ADD/SUB
operating_expenses	other_op_inc	ADD
operating_expenses	distribution_costs	ADD
operating_expenses	admin_exp	ADD
operating_expenses	other_op_exp	ADD
operating_expenses	restructuring_costs	ADD

Both load and extract tables can only have one to one mappings:

External	Enterprise	ADD/SUB
other_op_inc	other_op_inc	ADD
distribution_costs	distribution_costs	ADD
admin_exp	admin_exp	ADD
other_op_exp	other_op_exp	ADD
restructuring_costs	restructuring_costs	ADD

· Identify where entity conversion tables may be used in the system.

Database module

· Describe how to set up intercompany matching, and given an exhibit of intercompany groups, describe the output that will occur when values are entered into the application and consolidated.

In Entities module set Intercompany attribute for entities which will have intercompany balances. These are normally all base entities except for elimination entities.
In Entities module set Elimination attribute for entities eliminations will be posted to.
In Accounts module attach Intercompany subaccount table to intercompany accounts.
In Accounts module setup Intercompany Matching.

The following table shows how a single intercompany account is eliminated.

Account	Total	North	South	East	West	Elim	HQ
interco_loans - North	0	0	0	0	0	-2,000	2,000
interco_loans - West	0	0	0	0	0	-2,000	2,000
interco_loans - South	0	0	0	0	0	-2,000	2,000
interco_loans - East	0	0	0	0	0	-2,000	2,000
interco_loans - HQ	0	-1,980	-2,000	-2,000	-2,010	7,990	0
Intercompany loans	0	-1,980	-2,000	-2,000	-2,010	-10	8,000

Intercompany loans plug	10	0	0	0	0	10	0

The following table shows how a two intercompany accounts are eliminated.

Account	Total	North	South	East	West	Elim	HQ
interco_debtors - North	0	0	0	0	0	-1,000	1,000
interco_debtors - West	0	0	0	0	0	-1,000	1,000
interco_debtors - South	0	0	0	0	0	-1,000	1,000
interco_debtors - East	0	0	0	0	0	-1,000	1,000
Interco debtors	0	0	0	0	0	-4,000	4,000

interco_creditors - HQ	0	-980	-1,000	-1,000	-1,010	3,990	0
Intercompany creditors	0	-980	-1,000	-1,000	-1,010	3,990	0

Intercompany plug	10	0	0	0	0	10	0

· Describe the effect of using shared sub-account signatures on the chart of accounts, administration, and tools.

In a shared signature application subaccounts with the same id share the same attributes. This is useful if one subaccount table is a subset of another subaccount table as only one account has to be maintained and all instances of the subaccount are guaranteed to be the same. For example a car dealer might have a subaccount table of all cars and two subaccount tables of new cars and used cars.

· Describe how the Reverse Sign attribute affects data added to an implied subtotal.

The Reveres Sign attribute subtracts the subaccount value instead of adding it when the implied subtotals are calculated.

Account	Value
Reverse sign - No	1,000
Reverse sign - Yes	1,000
Implies subtotal	0

· Identify the effect of sub-account maintenance on intercompany and non-intercompany tables.

The default intercompany table cannot be maintained manually. Entities can only be added by selecting the Intercompany attribute for entities.

· Given a situation, identify whether the system-generated intercompany table or a user-defined intercompany table would be more appropriate.

User-defined intercompany tables might be used if there was a need to have different intercompany subaccounts for different accounts.

· Describe intercompany sub-account tables and shared signatures.

Shared signatures could be used to ensure all intercompany tables are consistent.

· Describe the Attached First Level Only option and describe how flags affect data added.

This option attaches only first level subaccounts for subaccount tables with second level subaccounts.