After PostERP's database backup file is restored, pre-entered list of account# becomes available.
PostERP has an exclusive advanced design:
PostERP does not enforce segmented general account codes. It manages single segment general account codes. Multiple levels of sub-accounts or detail accounts are not required. Here are some examples of general account codes:
1111 (raw material), 1141 (accounts receivable). Please refer to the shipped general accounts on screeen .
PostERP was designed to run single-segment general account codes system since year 2007 by leveraging our innovation mechanism - tag: A single segment of account code 1111 (raw material) is able to track site#, item#, lot#, quantity, and cost. A single segment of account 1141 (accounts receivable) is able to track customer# or vendor#, and amount.
This simplicity brings obvious advantages: (1) Users will not be confused by the general account code system they invent. (2) The overall system performs in high speed. (3) It easy for programmers to write SQL text to extract records from accounting journal entries to produce statistic reports.
Some ERP systems demand their users construct general accounts system with varialbe number of segments. For example,
Table 10-1. How Inadequately Designed ERP Systems Treat General Accounts
|General Account Code||Meanings|
|1226-EXDH3883HA||general account: 1226(raw material); item#: EXDH3883HA|
|1141-C-00001234||general account: 1141(accounts receivable); C indicates: The following segment is a customer# rather than a supplier# or employee#; customer#: 00001234|
Total number of segments can reach 5 or 6!
Follow this order to enter fundmental data for accounting module:
, , , , , , , , , , , ,
Assuming today is 2012/12/15 and 2013/1/1 is the first day start using module, please do the following tasks for every company:
Enter on screen one opening journal whose transaction date being any day in December 2012. This must be done before 2013/1/1. This journal records the balances of all general accounts.
Have every user get off line from PostERP and run business logic processor CloseBook before any transaction is entered by any user on or before 2013/1/1 and provide the following parameters to this business logic processor:
After business logic processor CloseBook finishes, an initial journal will be created whose journal date being 2013/1/1 00:00:00. This system is now welcoming its users' data entries to be started at 2013/1/1 09:00.