Repairs, installations, maintenance: when your technicians are out on site, the job often goes missing between the call-out and the invoice. Here is how Odoo Field Service ties planning, the signed on-site report and Luxembourg accounting into one flow.
In short. Odoo Field Service is the app that runs on-site jobs for an SME whose technicians work at the customer's premises: repairs, installations, maintenance, after-sales. Each job starts from a quotation or an order, is scheduled on a calendar with a route, is closed on site by the technician (time spent, parts fitted, worksheet and customer signature), then invoiced without re-keying. The entry then lands in Luxembourg accounting in the same database, on the PCN 2020 chart of accounts and at the right VAT rate. The gain is not a gadget: it closes the gap where hours and parts disappear between the job and the invoice.
An SME that sends technicians into the field loses money in two precise places: jobs no one remembers to invoice, and parts fitted but never charged. The technician's notebook, the office planner and the month-end invoice live in three separate worlds, and the margin leaks through the gaps between them. Odoo Field Service, the app built for on-site work, closes those gaps by tying scheduling, the report filled in on site and the accounting into a single flow. Here is how it works in practice, and what it changes for a Luxembourg SME.
What is Odoo Field Service for?
Field Service is the Odoo app designed for trades that work at the customer's site: installers, maintenance firms, repair crews, IT technicians, technical cleaning providers, anything done at the client rather than at a desk. Where classic project management follows long files, Field Service follows short, frequent jobs: one task, one location, one slot, one technician, one report.
What sets it apart from a shared calendar is what happens after the appointment. In Field Service, the job carries its customer, its order, the parts used, the time actually spent and a worksheet completed on site. All of that data then flows through to the invoice and to the accounts, without a single line being re-keyed. That continuity, from the planner all the way to the accounting entry, is what separates an ERP from a standalone scheduling tool.
How a job runs, from planner to invoice
A typical job in Odoo 19 runs through five stages, from the office to the field and back.
| Stage | Where | What happens |
|---|---|---|
| 1. Creation | Office | The job starts from a quotation or an order, with the customer, the address, the service product and, where relevant, an under-warranty flag. |
| 2. Scheduling | Office | The job is placed on the calendar and assigned to a technician. With a valid address, the day's route shows on a map. |
| 3. On site | Field | The technician signs in, fills the worksheet, adds photos and parts fitted, then closes. Start and end times are worked out automatically. |
| 4. Report | Field | A customer report is generated: services, parts, time spent, worksheet result. The customer signs on screen and it is sent by email. |
| 5. Invoice | Office | With the job linked to its order, the invoice picks up validated parts and time, at Luxembourg VAT, and posts to the accounts. |
Two details change life for a field team. First, the technician works from a phone: they open their round, sign in, tick the worksheet, photograph the meter or the swapped part, and collect a signature. Second, the on-site customer signature stands as proof of work: no more dispute over "the technician never came" or over what was actually done. The signed report is dated, time-stamped and filed against the job.
Invoicing it right: parts fitted, fixed price or time, and the correct VAT
This is where the gain sits. When the technician adds a part to the job, that part is added automatically to the customer's order: it will be invoiced, at the right price, without anyone at the office having to remember that a filter or a hard drive was fitted. Parts covered by a warranty come out at zero but stay traced. Time spent is billed according to the model you choose.
| Model | What you invoice | In Odoo |
|---|---|---|
| Time and materials | The time actually spent, at an hourly rate | The invoice picks up the validated hours from the job |
| Fixed-price call-out | A set price per visit or per service | The service product carries the price; time feeds margin tracking |
| Maintenance contract | A recurring subscription | Scheduled jobs attach to the contract |
And because the invoice is born in Odoo, it carries Luxembourg VAT at the right rate and the correct accounting posting from the outset. No export to a separate accounting package, no month-end reconciliation: the VAT return is prepared on the same entries, as we set out in our guide to filing Luxembourg VAT returns in Odoo. A follow-up quotation can also be raised straight from the job when the technician spots extra work on site, which heads off the classic "I'll get back to you with a quote" that never arrives.
Do your on-site jobs end up mis-invoiced, late or not invoiced at all? We look at your actual flow and what Odoo would change.
Book a diagnosticField Service or project management: which for which need?
The two modules share building blocks (tasks, timesheets, invoicing) but answer two different realities. The simple rule: if you sell long files with several people and milestones (consulting, engineering, development), you are on project management, which we describe in our article on Odoo for service companies. If you run a stream of short on-site jobs, with route planning, mobile use and a signed report, you are on Field Service. Plenty of SMEs use both: an installation project in project mode, then recurring maintenance in job mode.
What this flow changes for a Luxembourg SME
Beyond the comfort of the technicians, three effects show up in the accounts. The billing rate rises: jobs and parts no longer slip through, because they are captured where they happen rather than reconstructed from memory. The collection time shortens: the invoice can go out the same day, with the signed report attached, which cuts disputes short. And the accounting keeps pace: each invoice posts to the PCN 2020 in the same database, so you read your revenue and your margin in real time, not eight months later, as a live financial dashboard allows. It is the same principle that governs all our work: the information while it can still inform a decision.
Who this module is not for
Let us be straight. Field Service is built for an intervention business with several technicians on the road and a real scheduling challenge. If you work alone, with two jobs a week always for the same clients, the module is oversized: a plain calendar and standard invoicing will do. Likewise, a purely sedentary activity, with no travel to the customer, has no need for the field layer. And Field Service is not fleet-tracking software or telematics: it plans and documents jobs, it does not steer vehicles. Better to know that before switching it on than to pay for complexity you will not use.
Frequently asked questions
Does Odoo Field Service work on mobile?
Yes. The technician opens their round, signs in, fills the worksheet, adds photos and parts, then collects the customer's signature, all from the phone browser. The office sees the job close in real time.
Can parts and time on a job be invoiced automatically?
Yes. Parts added to the job are added to the customer's order and will be invoiced. Time spent is billed on time and materials, at a fixed price, or through a maintenance contract, depending on the model set on the service product.
How does it differ from the project management module?
Project management follows long files with milestones and several people. Field Service follows short, frequent on-site jobs, with route planning, mobile use and a signed report. An SME can use both.
Does the job invoice feed Luxembourg accounting?
Yes. The invoice is born in Odoo, at Luxembourg VAT and on the PCN 2020 chart of accounts. It posts straight to the accounts, with no export to a separate tool, and feeds the VAT return from the same entries.
Do you need an extra paid module for Luxembourg?
Not for accounting compliance: the PCN 2020, eCDF VAT and FAIA export are part of the Luxembourg localisation included in Odoo. Field Service is a standard catalogue app, counted within your Enterprise licence.
Read on
- Odoo in Luxembourg: is it the right ERP for your SME?
- Odoo for service companies: projects, time and invoicing
- Odoo pricing in 2026: licence, implementation and real cost
- Filing Luxembourg VAT returns in Odoo
- Financial dashboards in Odoo: steering your SME in real time
Why Advena?
- The field wired to the books: we configure Field Service all the way to the accounting entry and the VAT, not just to the planner.
- Finance and digital under one roof: the tool is set up by people who also keep Luxembourg books.
- Clear fixed fees, no hourly meter: you know the project price before it starts.
- Sized for SMEs: we switch on what serves you, and tell you plainly when a module is one too many.
Want every job to end in a correct invoice, the same day? Let's talk about your field operation.
Talk to us about your project
