Parameters and Structuring Features and Functions

• Fiscal calendar is defined by the user


• Calendar periods are defined by the user


• Calendar can be defined as uneven periods, adjustment periods, or to a maximum of 366 periods


• Multiple calendars


• Multi-entity financial reporting


• Twelve or thirteen fiscal months


• Calendar may be organized in a variety of ways, supporting 999 periods in a financial year


• Open any number of fiscal years or calendar periods at the same time


• Companies with different regional presences may set a default currency for the financial division of each region


• Sets reporting entity and its organizational characteristics


• Distinguishes A/P transactions (of the same type) from different entities


• Each entity's ledger can have its own calendar and chart of accounts


• Each entity's ledger can have its own accounting periods opened and closed


• User may choose between data collection and real time posting modes


• Tracks items in the G/L and sub-ledger by quantity and value (in whichever currency is used)


• Maintains unit and dollar amount postings in GL and sub-ledgers


• User-defined criteria for system purges for general ledger transactions, journal vouchers, and accounts payable data based on the number of years or months of data required to maintain--each purge type has its own unique criteria


• Sub-ledgers closed out prior to performing a purge. The closeout process sets all financial account balances in the sub-ledger to zero by posting an equal and offsetting transaction


• Specifies a key and rules to have the system automatically purge all records related to the key throughout the system--sub-ledger accounts, sub-ledger transactions, tables, rates


• Automatic check to ensure that prior to deleting a financial record, the account balance must have been "closed out" (i.e., nets to zero)


• Translation of balance sheet accounts including the ability to have a default rate (spot) that can be overridden on an exception basis (historic), on an account-by-account basis - do not want to set up a rate for every balance sheet account - the override rates will differ ledger to ledger


• Automatically inserts actual account balances into the elapsed month's bucket in a future forecast file at the end of each accounting period when the system rolls into the next period


• Prevents roll from one accounting period to the next unless the last job run is the financial statements


• Audit log required for any changes to table information that may contain rates and information used by the system in any way; log contains before and after, change, date, and user identification


• Flexible general ledger key with multiple levels


• Exception reporting with drill down capabilities


• Provision for use of standards that can be automatically propagated throughout the system to the various ledgers


• Uses the budget forecast information to create automatic postings; accruals for any potential overhead item, for example, bonus, depreciation, professional fees, new product development, and marketing expense; supports standard (automatically repeating) postings and entries that are generated each month with reference to amounts maintained in budget fields for the month. The amounts may or may not be the same from month to month


• Automatic year-end rolling of balances in sub-ledgers and general ledger control accounts


• Automatic linking and posting of control accounts from related sub-ledger accounts


• Processes jobs in edit and update mode


• Jobs required to include error and warning messages on reports


• Reports to include a control report that lists pages on which errors and warnings have occurred


• User-defined controls to allow specific jobs to update multiple times in a period


• Table master functionality--sets parameters in a table, has jobs read the table, and creates postings or reports accordingly


• User-defined field names for tables


• Method for verifying keying to ensure only appropriate records updated


• Archiving of transaction history as well as purge from active files


• Separate tax G/L


• Ties all subledger modules to the G/L