Built for UK water hygiene· variable-frequency PPM
PPM contract billing software that knows what you've delivered
The work happens in the field; the money happens in a spreadsheet three weeks later. BlueWave keeps the contract, its jobs and your invoices in one system, so the spreadsheet stops being the only record of what you sold.
Contract-billing capabilities reviewed .
The problem it kills
A PPM contract with monthly temperature runs, quarterly cleans and an annual risk assessment doesn't fit invoice-per-job, so the billing lives in a spreadsheet someone reconciles at month-end against job sheets, memory and Sage. Services get missed off invoices, extras never get charged, and the contract's real margin is a number nobody quite trusts.
Delivered, counted against sold
Each contract row counts the visits you sold and the visits your engineers delivered. You see what's done and what's still owed at any point in the year, instead of working it out at month-end.
- Visits sold and visits delivered on every row
- A row is a service at a site, or at one asset
- Month-end becomes a review, not an investigation
Variable frequencies, one contract
Monthlies, quarterlies and annuals live in the same agreement without proration gymnastics. BlueWave makes a job from each row and the schedule produces its dates, so the year stays coherent.
- Mixed service frequencies in a single contract
- Jobs generated from the contract's rows
- No more 'which quarter does this clean belong to' debates
Extra work stays on the contract
A reactive call-out or an extra clean attaches to the contract as extra work, so it's on record beside the planned visits when you raise the invoice, instead of falling out of the month.
- Attach any job to the contract as extra work
- Attach an existing recurring job to a contract row
- Everything the contract holds, on one page
The customer gets the contract before the work starts
Once the rows are priced, the office downloads the contract as a PDF and sends it to the customer from its own email, before the work starts. The jobs then come from the same rows, so what the customer was sent and what the engineers are booked to do start from one list.
- The contract as a PDF, with your logo on it
- You send it from your own email before the work starts
- The jobs come from the same rows
Done in March. Invoiced in May. Queried in June.
That timeline is the spreadsheet month-end working as designed. And somewhere between March and June, the margin died. The client queries a stale invoice, the office digs through job sheets to defend it, and everyone loses an afternoon. Keeping the contract, its jobs and the invoices in one system shortens that lag, and with it most of the queries.
The same records that defend your invoices satisfy your auditors; that mapping lives on the compliance hub. And the invoices themselves are raised next door: see invoicing, where an issued invoice downloads as a Factur-X e-invoice.
Common questions
How do I see how much of a contract we've delivered?
Can one contract hold monthly, quarterly and annual services?
How do I invoice completed work?
Where does my accounting software fit in?
Further reading
Pricing water hygiene work without guessing
Most small water-care firms price by copying the competition and hoping. Price from your own costs and the site's asset count instead, and itemise every line.
Bring a real contract to the demo
Your messiest one: mixed frequencies, mid-year extras, the lot. We'll model it live and show you its jobs and its delivery count.