Most companies do not buy an ERP because they want new software. They buy one because the current arrangement has become expensive: the warehouse reports one number and finance reports another, the monthly close takes two weeks, and nobody can state the margin on a single product without estimating it.
One entry, complete effect
The defining difference between an ERP and a set of separate programs is that a transaction is recorded once and takes effect everywhere at the same moment. When goods are received into a warehouse, all of the following happen in a single step:
- The item balance rises in the specified warehouse.
- The item's moving average cost is updated.
- A journal entry is raised, charging inventory and recognising the liability to the supplier.
- The related purchase order line is closed, showing any remaining quantity on a partial receipt.
- The invoice becomes available for three-way matching against the order and the receipt.
No one writes a manual journal, and no figure is carried from one screen to another. That re-keying is the source of most errors in disconnected systems.
Modules
Finance
- General ledger — multi-level chart of accounts, journals, cost centres, and financial statements built directly from transactions.
- Accounts payable — purchase invoices, three-way matching, ageing and payment scheduling.
- Accounts receivable — invoicing, collections, credit limits and debtor ageing.
- Reconciliation — bank, clearing account and supplier statement reconciliation.
- Fixed assets — asset register, periodic depreciation, disposal and revaluation.
Supply chain
- Inventory — multiple warehouses and locations, live balances, transfers, periodic and spot counts, batch and serial traceability.
- Procurement — requisition → quotation → purchase order → receipt → invoice, with approval tiers by value or expense type.
- Sales — quotations, sales orders, shipping and invoicing, with multiple price lists by customer segment.
- Fleet — vehicles, distribution routes and landed shipment cost.
Manufacturing and projects
- Manufacturing — bills of material, routing, production orders, and material requirements planning driven by sales orders and balances.
- Projects — budget per project, actual cost allocation and progress against spend.
People
- HR — employee file, org chart, contracts and document expiry tracking.
- Payroll — configurable pay elements with per-country tax and insurance rules, posting straight to the ledger. See HR & payroll.
Contracting companies
A contractor's revenue document is not an invoice but an interim payment certificate, with retention and advance recovery against a bill of quantities. That is handled by a dedicated product — Keystone Construction.
Why Oracle
The choice of database is not an internal technical detail; it sets the ceiling on what the system can do as the company grows. Three practical consequences:
- Real data isolation. Access rules are enforced at row level inside the database itself, not in interface code. A user without rights to a branch cannot see its rows even when reaching the data another way.
- Volume headroom. An active company generates millions of transaction rows per year; performance at that scale is a database design question, not a matter of server speed.
- Transactional integrity. The journal entry and the stock movement are either both committed or neither is — there is no intermediate state where stock rises without a corresponding entry.
Arabic is not a translation layer
Most foreign systems are Arabised with a translation layer over a left-to-right interface, and the familiar problems follow: negative numbers rendered with the sign on the wrong side, reports that break when Arabic and English are mixed, printed documents with reversed column order.
Keystone ERP's interface is built in Arabic from the ground up, and each user can switch to English from their own account without anything changing in the data — which is what companies with Arabic management and foreign shareholders or auditors actually need.
Cloud or on-premise
Both are available and the system is identical either way. Cloud hosting suits companies that do not want to manage servers, backups and upgrades. On-premise suits organisations whose policy or contracts require data to remain on their own premises. In practice this is a company policy decision more than a technical one.