Small businesses run on four or five disconnected tools and reconcile them by hand. IntelliSuite puts accounting, invoicing, payroll and point of sale on a single platform — one customer list, one chart of accounts, one audit trail, one bill.
In development · Accounting first
A typical South African small business keeps invoices in one package, payroll in another, the till in a third, and a spreadsheet to tie them together. Every join is manual, every month-end is a reconciliation, and no single system can answer what the business actually did.
A single sign-on across every Intelli app, and one staff roster. Add a bookkeeper once and they have the access their role allows — everywhere, immediately.
Every app posts to the same ledger through the same double-entry engine. The till, the invoice and the payroll run are the same transaction story, not three exports to reconcile.
Postings are immutable and hash-chained. Corrections are reversing entries, never edits — so the history a reviewer sees is the history that happened.
Each app owns its own domain and nothing else. They share identity, billing, entitlements and the ledger, so adding the next one is a switch you turn on rather than a migration you survive.
The flagship. Multi-tenant accounting for sole proprietors through to corporates: quotes, sales and purchase invoices, cashbook, journals, and the full MVP-1 report set.
Quoting and invoicing for businesses that don’t want a full ledger yet — the same documents and the same customer list, so moving up to Intelli-Accounting later is an entitlement change, not a data migration.
South African payroll: PAYE, UIF and SDL, with the payroll journal posting straight into the same ledger instead of arriving as a monthly spreadsheet someone has to capture.
Point of sale on Android POS hardware, offline-tolerant, settling into the same cashbook. The till becomes part of the books rather than a daily Z-read someone retypes.
Every query is tenant-scoped, and membership is checked against the token — not against a header a client can set. Tenant isolation is a property of the schema, not a convention the application layer is trusted to remember.
VAT rates and tax rules are effective-dated and resolved server-side from the tax regime, so a rate change is a data change. The jurisdiction sits behind a seam — South Africa is the first regime written, not the only one possible.
Personal information is scoped, access is logged, and a tenant can export everything it owns through a documented endpoint. Data residency and retention are design inputs rather than a policy page.
Every service is a thin OAuth2 resource server behind a gateway, authenticating against WeldForge, our own federated identity platform. One login, real MFA, and no bespoke password handling anywhere in the suite.
Built on: Java 25 and Spring Boot 3.5 · PostgreSQL with database-per-service · OIDC against WeldForge · Kubernetes · BDD and TDD throughout. Engineering notes live at cwvermaak.dev.
IntelliSuite is not generally available and is not taking sign-ups. This page describes what is being built and how far it has got — nothing here is a product you can buy today.
| Component | Status | What that means |
|---|---|---|
| Intelli-Accounting | In development | MVP-1 is feature-complete in code and under test. It has not been through its final acceptance walkthrough and is not running anyone’s real books. |
| Platform spine | In development | Gateway, account and entitlement service, and the WeldForge webhook sink are scaffolded. |
| Intelli-Invoicing | Planned | Designed against the shared spine. No implementation yet. |
| Intelli-Payroll | Planned | Designed against the shared spine. No implementation yet. |
| Intelli-POS | Planned | Designed against the shared spine. No implementation yet. |
If you run a small South African business, keep books for people who do, or would just like to be told when Intelli-Accounting opens up — send a note. A real person reads it.