Accounting Data Model

The Account Entity and the GL Batch Entity are the main entities in this data model.

Account Entity

The structure of the chart of accounts is different from country to country - so we have tried to make the design as general as possible.

The data models do not care or enforce any type of "structure" for the AccountID.

It is up to the developer, to enforce any kind of structure for the AccountID, for his specific implementation.

GL Batch Entity

The GL Batch Entity is General Ledgers only "Business Document type entity" - and it is not "related" with the Universal Business Document.

Like the Universal Business Document Object, every GL Batch Object can be in one of the following states:

• Posted
• nonPosted

When a GL Batch Object is unposted, it has NOT created any records (entries) in the GL transaction table (aAccountingTransaction).

These entries will be created when the GL Batch Object is posted, along with updates to various SUM tables (aAccountingRPSum and aAccountingFYSum).

A general and simplified graph of the Accounting Data Model

Understanding the Accounting Implementation

In contrast to other ERPs, the Accounting module in the alpha360 is just a "bucket" that receives, holds and organizes accounting only information from the other functional areas of the app. Various Business Documents - like Sales Invoices, Payments etc - are "transfered" or "posted" to the General Ledger with the help of BPs, either automatically or manually.

But

There is NO such thing as a Business Document when doing direct entries in the Accounting area.

You cannot say add a Sales Invoice directly from the Accounting area - not because the GL entry would be wrong, but because you cannot add from "here" important information for the Invoice, like the Customers, terms etc.

next -> Account Business Processes