Per-tenant isolation
Every organization gets its own logical Postgres database and its own object-storage bucket. Tenant boundaries are physical, not column filters. A bug in one tenant cannot leak into another.
Loading
A multi-tenant ERP, audit-grade by default and multi-entity from day one. One platform, every suite your operation needs.
Budget · Operations 2026
| Document | Period | Committed | Consumed | Remaining | State |
|---|---|---|---|---|---|
Operations · Q2 BUD-2026-OPS | 2026-Q2 | $ 240,000.00 | $ 92,180.50 | $ 147,819.50 | Active |
Programmes · annual BUD-2026-PROG | 2026 | $ 480,000.00 | $ 218,940.00 | $ 261,060.00 | Active |
Capital · Q2 BUD-2026-CAP | 2026-Q2 | $ 85,000.00 | $ 85,000.00 | $ — | Closed |
IT infra · annual BUD-2026-IT | 2026 | $ 64,200.00 | $ 51,840.00 | $ 12,360.00 | Active |
| 4 documents · computed at read time | $ 869,200.00 | $ 447,960.50 | $ 421,239.50 | ||
Above: a real Budget root document mid-month. Remaining is not stored; it's read from the ledger.
1 Database per org. ∞ Entities per tenant. Every Write audited.
Every organization gets its own logical Postgres database and its own object-storage bucket. Tenant boundaries are physical, not column filters. A bug in one tenant cannot leak into another.
Budget remaining, PO committed, invoice balance: calculated at read time from underlying transactions. The ledger is the source of truth, always.
Every business document has a status lifecycle, audit history, attachments, and an activity timeline. Uniformly. Across every suite, every domain, every type of work.
Settrium is a modular ERP. Each business capability ships as an independent suite, with the same audit substrate, same multi-entity model, same permission system. New suites plug in without rewriting old ones.
Budget through invoice and payment. Six domains, one chain, audit-grade.
See the suite →Stock levels, warehouse management, item master, stock movement.
Chart of accounts, journal entries, period close, financial reporting.
Customer orders, invoicing, accounts receivable, collections.
Employees, org hierarchy beyond the platform user model, payroll prep.
Project plans, time-tracking, project-bound budgets and procurement.
Customers, contacts, pipeline, deal-to-order handoff into Order-to-Cash.
Fixed assets, depreciation schedules, maintenance, asset-bound procurement.
Suites land independently. Today only Procure-to-Pay is live. The others ship as the platform matures, and sequencing follows customer demand.
Six domains, one chain. Each document carries every other's state, so the budget always knows what the invoice consumed, and the invoice always knows what the PO promised.
Budget
Annual + multi-year, multi-entity, dimensional
Requisition
Per-line budget allocation, policy-gated
RFQ
Vendor portal, structured comparative analysis
Purchase Order
Frozen post-receipt, contract-aware
Receiving
Goods + service confirmation, partial + reversal
Payables
3-way match with override, many-to-many payments
Drag the rail to see every step.
Every REQUIRES X rule reads policy.X_required. Tighten or loosen for a given organization without forking the engine. An NGO and a corner bakery share one codebase.
NGO · donor-funded
Commercial · mid-market
Small business
Whichever preset you pick at signup, every relaxed action writes the policy state at action time into the audit event. An auditor years later sees exactly why a rule was bypassed.
We onboard organizations by invitation. Tell us about yours and we'll set you up with your own isolated workspace.