PostERP

Satisfy your versatile needs with few screens

PostERP provides only a few number of data-entry forms making itself look like a kid's toy because of its simplicity. However, it copes with most of users' diverse requirements. Take sales as an example,

  • A sales# associates with one or more item#.
  • For every item#, there can be more than one sold shoe size.
  • Every shoe size can be delivered on multiple dates designed by the customer.
  • Every delivery can write-off one or more sales order.

This example explains that users can ship in a single sales# multiple times and multiple items to their customers' various locations in various quantities for unlimited number of sales orders. All these delivery conditions are handled by a single form.

ERP users need a software system that is simple to use, not the ones with numerous forms and switches.

One-segment of General Journal Account Codes

One of the important PostERP characteristics is its leading accounting codes mechanism.

Many other ERP systems require their users to invent a segmented coding rule for their Account Codes like these:

Bad Account Codes System
Account Code Meanings
1226-EXDH3883HA Account Code: 1226 (raw material)
Item Code: EXDH3883HA

1141-C-00001234 Account Code: 1141 (accounts receivable)

C means: the following segment
of code is customer code, which is neither supplier code nor employee ID

customer code: 00001234

It is not uncommon to see an account code with 5 or more segments in such systems! How to keep account codes consistent with the "coding rules" throughout the entire enterprise organization becomes an "art" using such ERP systems. Such ERP systems appear to have been too far away from users' ultimate goal of the usage of ERP systems - to simplify their business processes rather than complicate them.

PostERP does not apply accounts segmentation. It treats account code nothing more than a mere code. Hence there is no need to embed meanings in account codes. Thus, theoretically, you are always able to get the correct financial reports from PostERP regardless of whatever account codes system you use.

Examples: 1111 (raw material), 1141(accounts receivable). Refer to the pre-entered accounts on form [M4F2].

Consult on-line help for Tag# on form [M4P1]. PostERP adopts the leading writeoff mechanism: A single segment of account code 1111(raw material) is enough to record, track, and report all different raw materials' financial information as detailed as: Bin#, Item Code, Lot#, Quantity, Cost. A single segment of account code 1141 (accounts receivable) is enough to record, track, and report all accounts receivable as detailed as: Customer ID or Supplier ID, and amount.

The advantages of such design are apparent: (1) There is no "coding rule of Account Codes" for users to worry about. (2) PostERP runs fast because it does not need to analyze and guess the meanings of Account Codes.

Pages

Subscribe to RSS - PostERP