System Accounts

Use system accounts to assign and maintain system account (transaction) codes for the integrated packages in the selected dataset, for example: Payroll, Bank Account, Accounts Receivable, Accounts Payable, Inventory Activity, and Commodity Settlements.

The primary purpose of system account codes is to direct the repetitive G/L distribution for most types of transactions to specific ledger accounts. Disk space is conserved since the transactions contain the system account code, not the actual G/L distribution.

The assignment of system account codes should be completed prior to creating system journal entries in the live dataset. If the Agris General Ledger System is available in the dataset, the Chart of Accounts should be defined prior to attempting to assign the system account codes and integration with the LDG should be activated in Setup Information for validation purposes. The order of assigning the system account codes for each package or module is unimportant.

The system account codes may be assigned to any valid posting ledger account. The software checks the Chart of Accounts to make sure that the ledger account exists and that it is a posting account. The software does not check the logic of your assignments. For example: if you assign the SL transaction code for A/R sales to the asset account for a bank, the asset account is updated -- not the revenue account. The assignment of system account codes should be based on sound accounting practices and should be reviewed by the company accountant.

This process is also referred to as Mapping to LDG

Learn more about System Accounts feature:

 

Greenstone Home

 

 

AGRIS Home