The principle
No module writes to the general ledger
It is the least negotiable rule of the product, and everything else follows from it.
What we see elsewhere
In many business suites, every module knows how to post to the accounts. Sales posts its entry, inventory posts its own, payroll posts its own. Each has its own idea of what an economic event is — and its own way of coding it.
The day two modules describe the same event in two ways, the disagreement does not show up in the ledger: it settles into it. The gap surfaces six months later, at review, with no way of saying which of the two was right.
What we do
- Sales, purchasing, inventory, payroll, fixed assets: each produces a business event, never an accounting entry
- A single component — the integration bus — turns the event into an accounting entry
- Coding follows the configured scheme, with balance checks, unbroken numbering and timestamps
- The supporting document is attached to the entry, and the trail back to its origin is kept
- A business module can be rewritten without touching the accounts
What that guarantees you
- One single truth per economic event
- An audit trail that is sound by construction
- A tax audit file export that stands up to scrutiny