Connecting a service job from booking to billing

An illustrative scenario. It describes how a service job can be kept whole from booking to invoice, not a project delivered for a named customer.

The situation.

A service business takes bookings through one system, schedules in a spreadsheet, records completion on paper or in a messaging app, and invoices from a fourth place. Every step works. The problem appears at the end of the month, when nobody can reconcile what was promised against what was done and what was billed.

Where the record breaks.

Usually at the handovers. The booking captures what the customer asked for, the schedule captures who went, and the invoice captures what was charged, but nothing carries the thread between them. Disputes are settled by whoever can find a photograph. Margin per job is unknown, so pricing is set by feel.

How the work would go.

Establish the service catalogue as a definition rather than a price list: duration, skills, checklist, evidence and entitlement, versioned so a change does not rewrite history. Connect booking, dispatch and completion to the same job record. Capture evidence at the point of work, on a device that works without a signal, because the site is where it is. Then let the invoice derive from the job rather than from a re-entry.

What the organisation ends up with.

One record per job that holds the promise, the work, the evidence and the money. Disputes answered from the record. And, for the first time, a view of which services and which contracts actually make money, which usually changes at least one commercial decision.