Financials
General ledger, receivables, payables, banking, fixed assets and multi-entity consolidation, with period control and a reversal trail on every posting.
The same financial core underneath, the workflows and terminology of your sector on top. Compare what each edition adds, then look at the modules every one of them shares.
One financial core, six industry configurations. A retailer, a manufacturer and a university all report on the same ledger — with the workflows each one actually needs.
An industry edition is not a separate product. It is the same data model, the same posting engine and the same audit trail, configured with the documents, terminology and controls a sector actually uses — which is why a retailer, a manufacturer and a university can all be reported on from one financial core.
Each one arrives configured for the documents, controls and reporting its sector runs on, so the first workshop starts from something recognisable rather than a blank system.
Multi-outlet POS, real-time stock across locations, loyalty, promotions and margin reporting that updates as the tills ring.
Explore retail ERPMulti-level BOMs, production planning, shop-floor data capture and true landed cost for discrete and process operations.
Explore manufacturing ERPRun a whole client portfolio from one console — multi-entity books, compliance calendars, audit trails and practice billing.
Explore practice ERPAdmissions through alumni — attendance, fee collection, examinations, payroll and a parent portal on one campus record.
Explore education ERPFleet and driver records, trip planning, fuel and maintenance costs, freight billing and settlement in a single operating picture.
Explore transport ERPBudget control, procurement, payroll and citizen-facing services with the audit trail and access control the public sector requires.
Explore government ERPThese six run underneath all six industry configurations. Whatever your sector adds on top posts back into them.
General ledger, receivables, payables, banking, fixed assets and multi-entity consolidation, with period control and a reversal trail on every posting.
Item and batch masters, multi-location stock, transfers, counts, valuation methods and the movement history behind every variance.
Requisitions, approvals, purchase orders, goods receipt and three-way matching, with vendor terms and landed cost carried through to the ledger.
Quotations, orders, dispatch, invoicing, returns and credit control, with pricing and discount rules that hold across channels and outlets.
Employee records, attendance and leave, payroll processing and statutory deductions, posted straight to the accounts rather than re-keyed.
Statutory reports, management packs, role dashboards and ad-hoc enquiry — all reading the live ledger instead of an overnight extract.
The intelligence layer is not a separate product bolted to an export. It sits on the same data model every module writes to, which is the only reason it can compare a purchase price, a production cost and a sales margin in one thought.
Because every industry configuration shares one core, the same intelligence applies whether the document in question is a store transfer, a work order or a fee receipt.
Duplicate invoices, margin drift, stock that has stopped moving and approvals sitting too long are raised with the transaction trail attached.
Demand, cash position and lead times are modelled from the transactions you have actually posted, not from a sector benchmark that never matched you.
The core is the data model, the posting engine and the six shared modules. An edition is that core configured with the documents, terminology, controls and reports a sector runs on — plus the industry-specific functionality it needs, such as point of sale for retail or examinations for education.
No. Editions share the same core, so a group running a manufacturing arm and a retail arm can operate both configurations against one chart of accounts and consolidate without moving data between systems. We map that structure during discovery.
Yes. Most rollouts begin with financials and the operational module that hurts most, then extend. Because later modules post into the same core, adding one is a configuration and training exercise rather than a second implementation.
Configuration covers most of it. Where a genuine requirement falls outside the standard product, our own engineers build a custom extension, interface or configuration and record it in the solution design — the same team then supports it afterwards.
In a company-owned exclusive cloud facility that we operate ourselves rather than resold capacity, which means performance, patching and escalation are handled by the same organisation that builds the software and answers your support requests.
Tell us the industry and the process you are trying to fix, and we will walk the matching configuration on a live environment — the modules, the documents and the reports, not a slide deck.