Product
Modules that post to one ledger
Seven modules over one database. Switch on what the operation needs now and add the rest later without a migration project.
Accounting is the core, not an add-on
Most systems bolt the books on at the end. Here the ledger comes first, and buying, selling, stock and production are simply the places where entries originate.
Chart of accounts
Structured per company and cost centre, with multi-currency where you trade in more than one.
Journals and taxes
Recurring entries, VAT and withholding handled at the point the document is raised.
Period closing
Lock a period once it is reconciled, with an audit trail behind every adjustment.
The rest of the operation
Each module is useful on its own and stronger with the others. Nothing here needs a separate database or a nightly sync.
Finance
Cash positions, receivables and payables in one view, with bank reconciliation against the statement rather than against a spreadsheet.
Stock
Multi-warehouse balances, transfers, batch and serial tracking, and a valuation that moves with each receipt and issue.
Buying
Requests, approvals, purchase orders and supplier terms, matched to the goods receipt and the invoice.
Selling
Quotations, sales orders, delivery notes and invoicing, checked against live stock before a promise is made.
Project
Tasks, timesheets, budgets and billing measured against the job rather than against the month.
Manufacturing
Bills of materials, routing and work orders, with material and labour cost landing in the ledger as production happens rather than being estimated at the end of the month.
How a rollout actually goes
Scoping
We walk the current process with the people who run it and agree what the first phase covers.
Configuration
Chart of accounts, warehouses, approval flows and document formats set up against your own rules.
Data migration
Opening balances, master data and open documents moved across and reconciled before go-live.
Support
Training for each team, then a support window while the first close runs on the new system.
Where it runs is your call
The licence does not change with the deployment, and neither does the upgrade path. If you move later, the database moves with you.
Cloud, managed by us
We host, patch and back it up. You keep an export of the database whenever you want one.
Your own server
Runs on infrastructure you control, inside your network, with us on call for upgrades.
On-premise
For operations that cannot depend on a connection, with the same codebase and the same upgrades.
Which modules would you start with?
Tell us how the operation runs today and we will map it against the modules, then propose a first phase that pays for itself before the second one starts.