One ledger. Many entities. Permissions that hold.
The architecture in business terms — what it is, and what it means on a Tuesday when your buyer tries to open a payslip.
A worked example
A cashier at your Centurion store rings up a R1 247,50 basket at 14:32 on a Saturday. In most setups that becomes a till file, which becomes an import, which becomes a journal on Monday. Here it is one transaction, and it writes all of this at once:
| Account | Posting | Debit | Credit |
|---|---|---|---|
| 1100 | Cash on hand | 1 247,50 | — |
| 4000 | Revenue | — | 1 084,78 |
| 2200 | VAT output | — | 162,72 |
| 5000 / 1300 | Cost of sales · stock on hand | 874,19 | 874,19 |
| — | Balanced | 2 121,69 | 2 121,69 |
Cash goes up. Revenue is recognised net of VAT. VAT output is a liability from that second. Cost of sales is charged and stock on hand at that store drops by the same R874,19. Your gross margin for the day is correct at 14:32, not on Monday.
Multi-tenant and multi-entity
Your group is not one company and the system does not pretend otherwise. Origin360 models legal entities, sites, warehouses and storage locations as real structures, with separate purchasing and sales entities where your trading arrangements need them.
Each entity keeps its own books. You consolidate without exporting anything, because the detail never left.
- Legal entities — each with its own chart of accounts, tax registration and financial periods
- Sites — stores, plants, depots, mines
- Warehouses and storage locations — down to the bin, aisle or stockpile
- Purchasing and sales entities — so intercompany trade is captured as trade
Enforced in the database, not by hiding a menu
209 permission keys, checked against 531 row-level security policies that live in the database itself.
Most systems control access in the interface. The menu item disappears, the button greys out, and the data is still one crafted request away. That is not access control. That is a curtain.
Said plainly: your buyer cannot read payroll. Not by opening a different screen, not by editing the address bar, not by calling the API directly with their own valid login. The database refuses the row. There is no path around it, because the check is not in the part of the system a person can talk to.
Offline where it actually matters
The till is the one place where waiting for a network is not an option. The Origin360 point of sale runs on a local database on the till itself. When the line drops, the cashier keeps ringing up sales. When the network returns, the till reconciles and every sale posts to the ledger in order.
The warehouse and driver apps are installable too — they go onto the device from a link, and they keep working on a bad signal in a yard or a delivery route.
Your finance team will still want a spreadsheet
That is fine, as long as the spreadsheet is reading the ledger rather than becoming a second one.
- Live Excel and Google Sheets connections — a sheet that refreshes against real data instead of a monthly export
- Edge functions — your own logic where your business does something nobody else does
- Document templating — your invoice, your delivery note, your payslip, your letterhead
- A notification engine — rules that raise the thing that needs a person, to that person