Central control
Catch errors at draft. Fixing a charge here is the difference between a quick edit and a credit note next month.
n
Skip to main contentCentral Billing is a configurable platform for businesses that invoice national-account customers for work carried out by a network of independent service providers. It validates, prices and approves every document before it reaches a customer or your ledger, then delivers it through Acume as an eInvoice or PDF.
When one job touches a customer, a service provider and your own ledger, the billing splits into several transactions that have to reconcile. Run that by hand, at volume, and the cost is rarely in any single step. It is in the chasing, the re-keying and the credits left sitting on provider accounts.
The provider quotes the customer and waits for a reply before any work can be approved.
The customer’s purchase order arrives by email and is keyed into a spreadsheet or the ERP.
Products and services are typed again to raise the customer invoice, with no line-level check.
The provider is settled with a credit note that lingers on their account instead of being paid out.
Finance untangles sales, stock and provider settlements after the money has already moved.
Every charge is handled three times before anyone confirms it is correct. The cost is the handling, not the work. Observed in the field
Central Billing sits between job completion and financial impact. Every billing document moves through the same path and is validated, approved and audited before it leaves the system. Nothing reaches your customer or your ledger by accident.
Catch errors at draft. Fixing a charge here is the difference between a quick edit and a credit note next month.
Asset, customer and line-level validation, then sign-off, on every document. Approved is approved. It does not drift.
Real-time spend across documents, customers and assets, with a timestamped audit trail that is a by-product of the workflow.
A central billing transaction moves from supply through to the end customer, with a buy-back in between. Each stage carries its own GL coding, financial allocation and ownership, so the money is correctly attributed at every step rather than reconstructed afterwards.
When the work is complete, Central Billing raises a purchase order back to the service provider so they invoice and get paid cleanly, rather than carrying a credit that sits on their account. The provider is settled the way they expect to be, and your payables stay clean. A dealer-credit model is also supported where that is the agreed arrangement.
Master data flows from your systems into Acume and on to Central Billing. A job is raised, completed and billed. The customer is invoiced, the service provider is issued a purchase order, and that provider’s invoice returns through Acume to be matched and settled. Money in and money out, on one trail.
Three configurable layers drive every transaction: commission by product category, customer tier matrices, and the loaded price file that results. Renegotiate a contract without rebuilding your catalogue, and keep the historical record intact when terms change.
Tier markups are configured to suit your contracted rates. Service codes such as fitting, alignment, disposal and call-out are set up separately with GST handling and part numbers.
A job moves through seven stages: request, allocation, creation, entry, draft confirmation, invoice creation and provider payment. Central Billing supports two operating models, and the only thing that changes is where job allocation and creation sit. Head Office keeps financial control in both.
| Scenario 01 · Customer priced, Head Office managed | Request | Allocate | Create | Entry | Confirm | Invoice | Pay |
|---|---|---|---|---|---|---|---|
| Customer | · | · | · | · | · | · | |
| Head Office | · | · | |||||
| Service provider | · | · | · | · | · | · |
| Scenario 02 · Customer unpriced, provider managed, HO confirmation | Request | Allocate | Create | Entry | Confirm | Invoice | Pay |
|---|---|---|---|---|---|---|---|
| Customer | · | · | · | · | · | · | |
| Head Office | · | · | · | · | |||
| Service provider | · | · | · | · |
Customers, suppliers, products, services and user access are all governed centrally. Head Office sees everything. Each service provider sees only what it should.
One source of truth for every customer and provider relationship. Control credit status, terms and which providers see which customers.
Tiered pricing per provider, agreement and customer cohort. Retire a line without breaking past invoices or the audit trail.
Service revenue tracked on its own ledger, separate from products, so margin and attach rates stay clear without spreadsheet work.
Every provider user gets unique credentials through a logged, three-step activation. Administrators set the permission ceiling.
The same engine assembles recurring and annuity billing at volume. Use Central Billing to aggregate and collect the source data, apply the contract logic, then feed it into Acume for delivery as an eInvoice across the Peppol network or as a PDF. One compilation step, one delivery channel, one audit trail.
Collect transactions, usage and charges across the period into a single structured set, ready for billing.
Validate the billing file against the contract so what goes out is correct the first time. No MIA files.
Send as a Peppol eInvoice or a PDF, with supplementary billing detail attached where the customer needs it.
Validation at draft means errors are resolved on the spot, not chased through credit notes, emails and reconciliations.
Every document, every approver, every change. The audit trail is the workflow, not a separate month-end exercise.
One workflow, one access model, one source of truth, in place of spreadsheets, email approvals and ad-hoc rules.
A real conversation about how your central and volume billing runs today. We will walk your transaction flow with you and show Central Billing against your contracts, your providers and your delivery, and you decide from there.