Chapter 1: General Information
Special Considerations for Initial Setup Phase
Before beginning Initial Setup and prior to making any substantial changes to your system, your company should consider several issues and options that may affect system operation. This chapter provides information which should be considered when installing General Ledger.
Master Files
Initial Setup procedures are designed to establish master file records and to facilitate transfer of information from existing records to General Ledger.
The first step in Initial Setup involves entering master file and historical data for the application. Data can be entered into the following files:
Parameters Chart of Accounts Types Budgets Unit Accounts Summary Accounts Allocation Accounts Recurring Entries Exchange Rates Foreign Accounts Intercompany Names
Much of the information utilized by the General Ledger may be found in other applications. For example, General Ledger receives sales information from Accounts Receivable, and purchasing data from Accounts Payable and/or Inventory Control. If any of these applications have not been implemented, the information which would normally be received from those applications must be manually entered.
In the next step, Opening Entries functions are used to establish the balances in each account and to verify the data by printing the Trial Balance and account history reports.
Process Initial Setup is then run to ensure that required records have been entered accurately. An error log is created if any mistakes are found. Once the errors have been corrected, Initial Setup reports should be reprinted to check information for accuracy.
The final step in Initial Setup is End Initial Setup. Once this menu option is selected, the system begins Live Operations.
Transaction Control
As a function of setting up the General Ledger, you should decide how much detail you need to keep for Transaction Control. In general, the term "Transaction Control" means the maintaining of the audit trail of transactions that are entered and posted in General Ledger. Regardless of the level of detail that you choose to keep, all transactions will be entered, printed on journals, and posted by Operator ID and Control Number. Beyond that, you have several options. These options are controlled by several fields in the General Ledger parameters file, called "Ask for Operator ID?" and Use Transaction Control?"
If you enter "N" (No) for "Ask for Operator ID?", the system will assume that the answer to "Use Transaction Control?" is also 'N' (No). The Operator ID and Control Number for each group of transactions will be automatically assigned, and the system will not allow any operator to edit another operator's transactions. No control or hash totals will be kept, and no data will be posted to the Transaction Control file. Also, you will not be able to enter transactions in a foreign currency.
If you enter "Y" (Yes) for "Ask for Operator ID?" and "N" (No) for "Use Transaction Control?", the system will assign the Operator ID and Control Number for each group of transactions but the Control Number can be changed. Additionally any operator will be allowed to edit any other operator's transactions. No control or hash totals will be kept, and no data will be posted to the Transaction Control file. Also, you will not be able to enter transactions in a foreign currency.
If you enter "Y" (Yes) for "Ask for Operator ID?" and "Y" (Yes) for "Use Transaction Control?", the system will assign the Operator ID and Control Number for each group of transactions, and the Control Number can be changed. In addition the Control and hash totals can be entered and will be balanced against the sum of transactions. Each control group can have a unique description. An "Operator Exclusive?" option allows any operator to restrict access to his or her transactions, and the transactions can be entered in foreign currencies. One record will be written to the Transaction Control file for each group of transactions posted, detailing the Operator ID, Control Number, Description, Number of Transactions, Last Transaction Posted, Total Amount Posted, Number of Errors, and Number of Warnings. This file can be printed on reports and viewed through an inquiry.
The third option described above will provide you with the greatest possible detail for transaction control.
Establishing a Transition Date
It is important to carefully consider when your system is to begin Live Operations, since this affects the balances that are entered. When the transition date has been established, you must identify the first month of Live Operations by entering it as the Fiscal Month and Fiscal Year on the General Ledger Parameters file.
When establishing a transition date and determining the way in which account history records can be entered, the following options should be considered.
Option 1: You may choose to enter monthly ending balances as history for as many years as you want; however, each year of history must be balanced. During the processing of Initial Setup, the ending balance for the month prior to the first month of Live Operations is rolled forward. For example, if the first month of Live Operations is fiscal month 7, fiscal year 94, then month end balances for fiscal month 6 should be entered in each account. This provides the beginning balance for the current month. If the first month of Live Operations is the first month of the fiscal year, you must enter an End of Year (EOY ) balance for the previous fiscal year. Do this by putting the balance in End of Year (EOY), not in Start of Year (SOY) or month 12 (or 13).
If you choose this option, you may make all journal entries for the current month, but only after ending Initial Setup.
Note that this option requires a greater amount of entry time than other operations.
Option 2: You may choose to enter no history. With this option, you enter all the master files, Process Initial Setup, and End Initial Setup. This will put you into Live Operations. Once in Live Operations, you enter the current month's beginning balances as journal entries and then enter the current month's entries.
This option requires less data entry time, and will probably allow you to select an earlier transition date. However, you will have no historical balances prior to the current month to use for historical or comparative reports or statements.
Option 3: If you want to keep year-to-date detail, and you transition date is not the first month of the fiscal year, then all current fiscal year entries should be made in Live Operations using the Journal Entries function in Transaction Processing. These entries can be made in one of the following two ways:
1. Enter as prior period postings.
2. Set the application's parameters to reflect the first month's entry period, then enter the journal entries for each period, closing the month as each period is completed.
Note that if the first month for which data is being entered in transaction form is not the first month of the fiscal year, and if prior-period postings are not being made, the YTD General Ledger report in Live Operations will include only a summary posting for the difference between the Start of Year balance and the balance of the first month of Live Operations.