Service Order
A service order is the document a company uses to plan, carry out and invoice a service – such as maintenance, repair, installation or support. It bundles the customer, the serviced object, appointment dates, materials used and labor hours into one traceable case.
A service order is the central document a company uses to steer the delivery of a service – from maintaining a machine to a repair, an installation or technical support. It records which customer receives which service on which object, who carries out the job and when, and what material and labor hours are incurred. This makes the service order for services what the sales order is for the sale of goods: the document-level basis on which planning, execution, documentation and invoicing come together.
Unlike a pure goods order, a service order puts the service in the foreground, not the delivery of a product. It often links a specific service object – such as an installation with a serial number – one or more technician visits, and the material fitted along the way. Because effort and material only become clear during execution, the service order is typically a "living" document: it is filled with feedback from the job over its lifetime and only fully invoiced after completion. In the ERP or service module, it forms the bracket over customer data, dispatching, material withdrawal and invoicing.
At a glance
- Document to plan, execute and invoice a service (maintenance, repair, installation, support)
- Bundles customer, service object, appointment dates, material and labor hours
- Service counterpart to the sales order in the sale of goods
- "Living" document: filled with feedback during execution
- Basis for time-and-material billing, service history and maintenance planning
What belongs in a service order?
A service order bundles all the information needed to deliver and invoice a service. The header of the document holds the customer, the agreed service, the priority and – where present – the service object concerned, that is the specific installation, device or system being serviced. At line-item level follow the individual services: labor items for the time spent, material items for parts consumed, and items for travel, flat rates or third-party services.
In addition, a service order often contains a fault or task description, the agreed appointment or service level, the responsible technicians and status information on progress. After the job, feedback is added – recorded times, material withdrawn, a service report and often the customer's signature. From this data, the invoice is ultimately created, either based on actual effort or against a contractually agreed flat rate.
Labor time, material and effort
At the core of every service order is the capture of the actual effort. Technicians report their labor hours per job, the material fitted is assigned to the order and withdrawn from stock. Together, these form the basis for time-and-material billing and, at the same time, make transparent how profitable an individual service job or a service contract really is.
Service object and history
Many service orders refer to a specific object, often identified by serial number. The ERP keeps a service history for this object: which orders, repairs and replaced parts have there already been? This history speeds up fault finding, documents warranty and guarantee cases and is the basis for preventive maintenance.
How a service order runs
The life cycle of a service order begins with a request or report – triggered by a customer call, a ticket, a maintenance plan or a fault. From the report the service order is created, with customer, object and task description. Dispatching follows: a suitable technician with the required qualifications is scheduled, an appointment is arranged and – where foreseeable – the needed material is reserved. For plannable services, this is often preceded by a quote followed by an order confirmation.
On the job, the technician carries out the work and reports back times, material and result, increasingly on the go via app right on site. Once the order is technically completed, it is released for invoicing: the system produces the invoice from the feedback – by effort or by contract – and closes the case. If the case could not be resolved immediately, follow-up orders or back-deliveries arise. Across all steps the status remains visible, so that back office and customer can tell at any time where the order stands.
Why the service order matters
For many companies, service is a standalone, high-margin business alongside pure product sales. The service order is the tool that makes this business steerable and assessable in the first place. Without a structured document, hours worked and material fitted get lost, are not invoiced or cannot be assigned to individual customers and contracts – the service margin stays in the dark.
A cleanly managed service order ensures that every service is captured, documented and correctly invoiced. It improves response time through structured dispatching, creates a reliable basis for warranty and maintenance with the service history, and delivers the data to measure service quality and profitability. For the customer this means traceable, transparent services; for the company plannable capacity and a higher service rate.
The service order in the ERP system
In the ERP system the service order is not an isolated document but embedded in the same process and data world as sales, warehouse and accounting. It draws on the customer master for addresses and terms, on the material or item master for spare parts, and on price lists for service rates. Material consumed is withdrawn directly from inventory management and deducts stock, while labor hours flow into invoicing and partly into payroll.
The benefit of this integration lies in end-to-end continuity: the invoice arises from the service order without re-entry, the service history on the object updates automatically, and analyses of utilization, response times or service margin draw on a single data basis. Many systems couple the service order to a CRM or ticketing system, so that a customer request turns directly into a dispatchable order. Mobile service apps connect field technicians – with access to order, history and material stock and direct feedback of times and consumption.
Connection to maintenance contracts and ticketing system
Service orders rarely arise by chance. They are often generated automatically from maintenance contracts or framework agreements – for example as a recurring maintenance order per interval – or from an incoming support ticket. This chaining ensures that contractually promised services are actually scheduled and delivered, and cleanly separates billable additional services from jobs already covered by the contract.
Distinction: service order, sales order and maintenance contract
Service order, sales order and maintenance contract are easily confused, but they denote different levels. The sales order steers the sale and delivery of goods – the focus is a product that is picked and shipped. The service order, by contrast, steers the delivery of a service on an object; any material fitted is only one component alongside labor time and travel. In practice they overlap, for example when spare parts are sold during a service job.
The maintenance or service contract, in turn, sits one level above: it is the contractual agreement on recurring or guaranteed services – such as annual maintenance or a promised response time. From it, the individual service orders are derived as concrete executions. The contract defines the "what and how often", the service order documents the individual "when and how", and the distinction determines which jobs are covered by the flat rate and which are additionally billable.
Example
Example: machine builder structures its after-sales service
A mid-sized manufacturer of packaging machines long served its customers ad hoc: fault reports came in by phone and email, technicians noted times and material on slips of paper, and invoicing happened weeks later from memory. Regularly, hours and spare parts went unbilled, and no one could say which machine at the customer had last received which repair.
With structured service orders in the ERP, after-sales was set up anew. Every report now generates a service order that references the machine by its serial number. The back office dispatches technician and appointment, on the job the fitter reports times and material fitted on the go, and the invoice arises directly from this feedback. Recurring maintenance is generated automatically from the service contracts. The result: fully invoiced jobs, a gap-free service history per machine and a service division whose margin the company can evaluate reliably for the first time.
Frequently asked questions
Matching ERP systems
Related services
Questions about Service Order in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.