Engines

The expensive part
is already built.

Underneath almost every business system is the same machinery: a ledger that has to balance, tax that has to be filed, people who have to be paid, approvals that have to hold, and data that has to survive a phone with no signal. We own that machinery, tested and in production. Your build starts on top of it.

Double-entry ledger

Tax and compliance

People and payroll

Offline sync

Approval workflow

Natural language entry

Assembled per client. Never rebuilt.

One by one

What each engine actually does.

Double-entry ledger

The accounting core

Every amount that moves creates a balanced pair of entries. Nothing is a loose number in a table. This is why a trial balance actually balances, why a report can be drilled down to the entry that caused it, and why nobody can quietly change history — corrections are entries too.

  • Trial balance, P&L and balance sheet from the same source
  • Full audit trail with the person and timestamp on every entry
  • Period locking so closed months stay closed
  • Multi-currency with the rate stored at the time of the entry

Tax and compliance

Filing without the panic

Tax rules are data, not code, so a new rate or a new country is a configuration rather than a rebuild. Returns are generated from the same ledger the accounts come from, which means the return and the books cannot disagree.

  • Return-ready statutory formats generated from live books
  • Input and output reconciliation before you file
  • Withholding and deduction handled at the point of entry
  • Configurable per country, per state, per registration

People and payroll

Attendance through to payslip

Attendance, overtime and advances feed wage and salary runs directly, so the amount someone is paid traces back to the days they were marked present. Statutory deductions are applied by rule and land in the ledger as real postings.

  • Daily wage, monthly salary and contract labour in one model
  • Advances recovered automatically across pay periods
  • Statutory deductions and payslips generated per run
  • Cost allocated to the site, branch or project worked on

Offline sync

Data captured where there is no network

Field devices hold what they capture and reconcile when a connection appears. The hard part is not storing offline — it is merging without duplicates or lost work when several people were offline at once. That is what this engine handles.

  • Queued capture with no data loss on flat batteries or dead zones
  • Conflict handling that never silently overwrites
  • Attachments and photos synced alongside the records
  • Same behaviour on Android, iOS and the browser

Approval workflow

Control without a bottleneck

Who may raise something, who must approve it, what limits apply and what it locks once approved. Field entries stay submissions until the office confirms them, so the books are never at the mercy of the fastest typist.

  • Role and amount-based approval chains
  • Submissions held separately from posted records
  • Maker-checker separation on reversals and voids
  • Every decision recorded with who and when

Natural language entry

For people who will not fill in forms

A person writes or says a line the way they would tell a colleague, and gets back a properly categorised draft entry to confirm. It is a drafting aid, not an autopilot — nothing posts without a human agreeing to it.

  • Free-text and voice input into a structured draft
  • Learns the categories and parties your business actually uses
  • Works in the languages your staff speak
  • Always confirmed by a person before posting

Reporting and drilldown

Numbers you can defend

Every figure on every report is a link back to the entries behind it. When someone asks why a number looks wrong, the answer takes seconds instead of an afternoon in a spreadsheet.

  • Drill from any total to the underlying entries
  • Profitability by branch, project, client or product
  • Ageing for both receivables and payables
  • Exports that keep their structure, not flat dumps

Tenancy and permissions

Separation you can trust

Each organisation's data lives in its own store, not in a shared table with a filter on it. Inside that, roles decide what each person can see and do. This is what makes it safe to run several companies, branches or institutions on one deployment.

  • Separate data store per organisation
  • Role-based permissions on every operation, checked server-side
  • Session, rate-limit and CSRF protection as standard
  • Backups and restores per organisation
Questions

About the engines.

Why does it matter that you already have these engines?
Because they are the expensive, slow, easy-to-get-wrong part of any business system, and they are the part that is the same everywhere. A ledger that balances and an approval chain that holds are not what makes your business different. Starting with them built and tested means your budget goes into the part that is actually yours.
Is this a template product with a new logo on it?
No. A template gives you the same screens with your name at the top. An engine is the machinery underneath, with your process built on top of it. Two clients on the same engines can end up with systems that look and behave nothing alike.
Can you use only some of them?
Yes. A field app might use offline sync, approvals and permissions and nothing else. A school build uses the ledger, tax, payroll and reporting engines with an entirely different set of screens on top.
Are the engines proven, or new?
They are in production, running real businesses with real money passing through them, and they carry an automated test suite covering the accounting integrity and security behaviour. That is the point of using them.

Your process, on machinery that already works.

Tell us what your business does. We will tell you which engines it needs and what has to be built fresh.

No sales call needed to look around. Every product on this site is live and usable right now.