System 04
Collect the money
Does every invoice reconcile without an argument?
An invoice that reconciles without an argument is rarer than it sounds — GST-correct documents, part payments tracked against the right invoice, credit limits enforced before a sale rather than reviewed after, and an online payment integration that genuinely cannot double-charge. This layer is the billing, invoicing and ledger work that closes cleanly every time, not most of the time.
What exists once this is in place
- GST-correct invoices, credit notes and returns exports
- Credit limits enforced at the point of sale
- Online payments wired idempotently — no double charges
- Receivables ageing you can act on, not compile
Built by these services
Collect the money FAQ
Before you ask
Isn't billing just a feature inside an ERP, not its own thing?
In a full build it usually is bundled in — this pillar is listed separately because a business can need correct billing and payments long before it needs a full operations system, and buying just that first is often the right call.
How do you actually prevent a payment gateway from double-charging?
Idempotent request handling — every payment attempt carries a unique reference the gateway and our system both check before processing, so a retried request (a flaky connection, a double-tap) is recognised and ignored rather than charged twice.
The other five systems