Every part of the business, on one ledger.
Finance, supply chain, manufacturing, people, and projects share a single ledger with one set of permissions and one audit trail. There is no integration tax between the modules you were always going to need.
16 modules·One ledger·No per-record fees
Sixteen modules, none of them sold separately.
Grouped the way the business is grouped rather than the way a price list is. Every module posts into the same ledger, which is the property the rest of this page depends on.
Finance
The ledger everything else posts into, and the close that runs off it.
Accounting
Double-entry ledger, payables, receivables, tax by rule, budgets that act on the document, and multi-currency with revaluation.
Assets
Capitalisation from the invoice that bought it, depreciation on a schedule that posts itself, and several finance books per asset.
Immutable postings
Entries are never edited. A cancellation posts its own reversal, so the trail shows what happened and when somebody changed their mind.
Accounting dimensions
Project, region, vehicle, campaign — your own dimensions as first-class fields on every posting, with mandatory rules per account.
Supply chain
What you buy, what you hold, and what it is worth.
Procurement
Requests, RFQs answered on a supplier portal, orders, receipts, and a three-way match that runs on the record.
Inventory
Warehouses, batches, serials, expiry, and perpetual valuation posting to the ledger as each movement happens.
Manufacturing
Multi-level BOMs, routings against real workstation capacity, work orders, job cards, and subcontracting.
Quality
Reading-level inspection criteria that can refuse a receipt or a delivery, and non-conformance against the procedure it breached.
Commerce
Selling, in whichever channels the business actually uses.
Sales
Quotation to order to delivery to invoice, with pricing decided by rule and margin read against real valuation.
CRM
Leads, prospects, opportunities, and campaigns on the same records as the orders they become — no CRM-to-ERP sync.
E-Commerce
A catalogue built from the item master, with checkout producing a sales order rather than a record awaiting import.
Point of Sale
Tills that hold their own catalogue and keep selling through an outage, then settle into the same ledger.
People and delivery
The cost of doing the work, on the same record as the work.
HR
One employee record from offer to exit, with leave kept as a ledger and attendance built from real check-ins.
Payroll
Structures written as formulas, a run that reads attendance and leave from the same records, posting straight to the ledger.
Projects
Tasks with real dependencies, timesheets carrying both a costing and a billing rate, and margin visible during delivery.
Support
Tickets beside the orders and serial numbers they concern, with SLAs measured against real support hours.
Vertical
Where a trade needs records the core does not have.
Education
Students, programmes, courses, attendance, and assessment, with fees posting as receivables into the same ledger.
Healthcare
Patients, appointments, encounters, lab tests, and inpatient stays, billed from the activity rather than transcribed from it.
Upstream named plainly
Both are separate Frappe-ecosystem apps rather than ERPNext core, and each module page says which repository and what its status is.
What makes it one system
The properties that stop this being a suite of integrated products.
One ledger
A delivery, a payroll run, and a depreciation entry post to the same general ledger. There is nothing between the modules to reconcile.
One permission model
Row-level permissions apply identically in the interface, the API, the mobile apps, and to every agent.
One audit trail
Every version of every document, with who changed what and when, on the record rather than in a separate log product.
One set of masters
A customer, an item, and a cost centre are defined once and mean the same thing in every module that uses them.
A cutover you can reverse.
The same four steps run for every wave, so the second go-live is a repeat of a process the business has already been through rather than a new event.
- 01
Map
Your chart of accounts, item master, and approval limits are taken as they are, not redesigned.
- 02
Migrate
Open balances, open orders, and master data move first. History follows behind them.
- 03
Run parallel
One period on both systems, reconciled daily, before anyone is asked to switch.
- 04
Cut over
At a period boundary, with the old system readable and a rollback still available.
The specification.
The answers an architect asks for in the first call, rather than in the third.
- Ledger
- Multi-company, multi-currency, multi-book
- Tax
- VAT, GST, withholding, statutory filing by region
- Valuation
- FIFO or moving average, per company or per item
- Audit
- Immutable trail and full version history on every posting
- Close
- Period lock by document type, accruals, deferrals, reposting
- Extensibility
- Custom record types with the same permissions and workflow
- Upstream
- ERPNext and Frappe HRMS, under GNU GPLv3
- Licensing
- No per-record, per-document, or per-transaction fees
What this is not.
Worth reading before a demo rather than after one. None of the below is on a roadmap slide we are hiding.
- Not a replacement for everything
- Where you run a genuinely specialist system — a treasury platform, a clinical device integration, a trading engine — the honest answer is to integrate it, not to rebuild it here.
- Not a no-code product
- A great deal is configuration, but a business with unusual records will want a developer for the parts that are genuinely theirs. We would rather say so than let you discover it.
- Not free of migration work
- Open balances reconcile cleanly; twenty years of history with three different customer-numbering schemes does not migrate itself, and that work is real.
- Not a reason to keep bad process
- Lifting a broken approval chain into a new system produces a broken approval chain with better reporting. We will say so during mapping.
Next step