Status: Delivered. Described from our own delivery records. Client identity, brand and commercial terms are withheld. Figures, where given, cover the period stated and nothing beyond it.
Context
A maintenance contractor working on customer sites across a petroleum retail network.
Its work is dispatched, performed, consumed parts from stock, and eventually generated an invoice — but each of those four things lived in a different place, so the chain from work performed to revenue recognised was manual and slow.
The problem
- Work orders and the parts consumed against them were recorded separately, so stock and job cost were reconciled after the fact.
- Billing lagged completion, because the evidence needed to raise an invoice arrived late and incomplete.
- Purchasing had no reliable signal from field consumption.
- Accounting entries were assembled from operational records rather than produced by them.
- Nobody could see which contracts were profitable at the job level.
What we built
A single operational chain
Work orders, inventory, sales, purchasing and accounting configured as one system, so completing a job moves stock, generates the timesheet and cost lines, and produces the invoice.
Consumption-driven replenishment
Parts used in the field raise the purchase signal rather than waiting for someone to notice a gap.
Job-level cost visibility
Material and labour attributed to the work order rather than absorbed into an overhead pool.
How we delivered it
- 1
Process mapping
Of the dispatch-to-cash chain, with the people who run it.
- 2
Foundation
Entities, chart of accounts, stock locations, environments.
- 3
Work-order and inventory build
Configured to the real job types and parts catalogue.
- 4
Billing wiring
Completion and sign-off producing the invoice.
- 5
Pilot on one region
Through a full billing cycle, before wider roll-out.
- 6
Ongoing managed operation
On a shared-resource basis.
How it was phased
Indicative phasing for work of this shape. Actual duration varies with data quality, access and decision speed.
What the client keeps
- The production system
- Configuration documentation
- The job-type and parts configuration
- Runbooks
- The reporting layer