ELT — Work — Documentation

Creating and dispatching tasks

Mon, 01 Jan 0001 00:00:00 +0000

Creating and dispatching tasks#

Tasks are typically created from the office side based on a customer request (phone call, email, customer portal). The foreman is responsible for making sure each task has a suitable installer and that the work progresses.

Creating a task#

Field Service → Orders → Create or via the landing-page shortcut.

Required fields:

Field	Purpose
Customer	Customer (contact). If new, create in Contacts first
Location	Customer site — if there are several, pick the right one
Description	Brief for the installer — what to do, where to start
Scheduled date	Planned start date — required for the planning calendar

Optional:

Customers (contacts and locations)

Mon, 01 Jan 0001 00:00:00 +0000

Customers (contacts and locations)#

ELT customer data is split across two levels:

Contacts (res.partner) — a company or individual, one entity
Locations (fsm.location) — a single customer can have multiple sites (e.g. a housing company with several addresses)

Creating a customer#

Contacts → Create.

Required:

Name — company name or person name
Company / Individual — radio choice important for Netvisor sync
Address — primary billing address

Recommended:

Business ID (Y-tunnus) (companies, format 1234567-8) — needed for the Netvisor link
VAT — if different from business ID (e.g. foreign)
Email — invoices go here
Phone — installer will need this

**Don't use company.partner_id or similar "base partner" as fsm.location.partner_id.** OCA fieldservice propagates name/active changes between partner ↔ location, so if the location's data changes, the entire company name might change. This is a big bug source (200.x).

Creating a location#

One customer can have 1–N locations. Creating one:

Installing the PWA on your phone

Mon, 01 Jan 0001 00:00:00 +0000

Installing the PWA on your phone#

The ELT Field Service app (PWA, Progressive Web App) runs in a browser, but you should install it to your phone’s home screen: it then launches like a normal app, hides the browser’s address bar, and push notifications + background sync work more reliably.

Android (Chrome)#

Adding to the home screen#

Open https://mobile.work.elt.systems in Chrome.
Register this device with the enrollment code from the office — see Device setup and login.
Open Chrome’s three-dot menu (⋮) and pick “Install app” (or “Add to Home screen”).
Confirm — the icon appears on your home screen as ELT FSM.
Launch it from there → it looks like a real app, no browser chrome.

Enabling push notifications#

Notifications are not on by default — you activate them once. After that you’ll get a notification each time you’re assigned a task or an assistant-installer request comes in.

Device setup and login

Mon, 01 Jan 0001 00:00:00 +0000

The PWA uses biometric login — fingerprint or face recognition. You never type a password or an API key. Your phone is paired to you once using a code from the office, and after that you open the app with a single biometric unlock.

**The old method has been removed.** Logging in used to require a server URL, database, username and API key (plus a PIN). That's gone — the only way now is biometric device registration, which is both safer and faster.

How it works in short#

The office or your foreman creates a 9-character enrollment code for you on the desktop (valid for 15 minutes).
On your phone you open https://mobile.work.elt.systems → Register this device → enter the code or scan the QR.
The phone asks for your fingerprint / face (or device lock code) → the device is paired.
From then on, logging in is a single biometric unlock. No password, no API key.

1. Registering the device (once per phone)#

You only do this once for a new phone.

Planning calendar

Mon, 01 Jan 0001 00:00:00 +0000

Planning calendar#

The planning calendar is the foreman’s main tool — it shows all installers and their tasks side by side at a glance.

Open: Field Service → Planning Calendar.

Core view elements#

Days on the horizontal axis, installers on the vertical.
Each task is a coloured bar whose width = estimated duration.
Task colour = state or priority (office configures).
Green border = task complete. Can be filtered if desired.

Time-range zoom#

Top-bar buttons / quick selectors:

Products and inventory

Mon, 01 Jan 0001 00:00:00 +0000

Products and inventory#

ELT’s product catalogue has 170,000+ products — the vast majority imported via the LVISnet wholesaler channel. Manually entered products are for special measurements or non-LVISnet items (e.g. own tools, equipment).

Product family#

Odoo distinguishes two levels:

product.template — the “abstract” product (e.g. “Nibe S1255 heat pump”)
product.product — variant (e.g. different colours, sizes — at ELT mostly 1:1 with the template)

Generally ELT works at the template level.

Inviting an assistant installer

Mon, 01 Jan 0001 00:00:00 +0000

Inviting an assistant installer#

The primary installer invites assistants onto a task when an extra pair of hands is needed at the site. This is an organic social flow: foreman doesn’t need to micro-manage, installers arrange amongst themselves and work agile.

Invitation from the PWA (installer side)#

Primary installer opens the task in the PWA.
Top of the task: “Request help” button.
Pick another installer from the list.
The task sends a push notification to the selected installer.

Accepting the invitation (assistant side)#

The assistant sees:

LVISnet wholesale price import

Mon, 01 Jan 0001 00:00:00 +0000

LVISnet wholesale price import#

LVISnet is the joint product and price catalogue of Finnish HVAC and electrical wholesalers. ELT uses it for real-time wholesale prices in the installer’s PWA product search: when an installer scans a barcode on site, they see the right wholesale price and availability.

We support these wholesalers: Onninen, Dahl, Ahlsell, Sonepar.

How the import works#

Field Service → LVISnet → Fetch Sources lists the wholesalers. Each row has:

Working with tasks

Mon, 01 Jan 0001 00:00:00 +0000

Working with tasks#

A task — Field Service Order — is one unit of work: one customer, one site, one visit. The installer sees their tasks in the PWA.

Task states#

State	Meaning
Planned	Office has created the task, work hasn’t started
In progress	You’ve started the work — clock running
Done	You marked the task complete, foreman approves for invoicing
Cancelled	Won’t happen (e.g. customer not on site)

Using the task list#

The PWA home view shows:

Approving hours and expenses

Mon, 01 Jan 0001 00:00:00 +0000

Approving hours and expenses#

Weekly rhythm: the foreman reviews the week’s hours and expenses before they move to invoicing or payroll.

Why approval matters#

Installer-submitted lines can contain errors (wrong day, wrong task, wrong amount).
Business needs review: approved line → billed to customer → ELT’s revenue. A bad line → customer complains.
Tax authority requires: mileage and per diems must be documented sensibly before payroll.

Approving hours#

Field Service → Timesheets or HR → Timesheets.

Invoicing (sales invoices)

Mon, 01 Jan 0001 00:00:00 +0000

Invoicing (sales invoices)#

ELT invoices mostly from two sources:

Field Service tasks — when work is done, the task’s hours + expenses + products flow to the invoice
Direct invoices — e.g. periodic invoice for a contract customer, advance payment, non-task-based

Typical flow: task → invoice#

Installer marks the task done (state = “Done”).
Foreman approves hours and expenses weekly (Approvals).
Office creates the invoice:
- Open the task → Action → “Create Invoice”.
- Odoo creates an account.move (Draft state).
- The installer’s logged hours × installer rate, expenses and product lines flow over automatically.
Review: open the Draft invoice.
- Check that rows, prices, VAT classes are correct.
- The Resolution text (installer’s summary) appears in the invoice header / memo — the customer sees this.
Confirm: Action → Post.
Sending to customer and Netvisor:
- To customer: Action → Send & Print (PDF + email).
- To Netvisor: see Netvisor integration.

Invoice structure#

Odoo’s account.move parts:

Logging hours

Mon, 01 Jan 0001 00:00:00 +0000

Logging hours#

You can add hours from two places: per task or via the general Hours view. The result is the same; the choice is about ergonomics.

Per-task hour entry#

When you’re in a task:

Open the Hours tab.
"+ Add hours" button.
In the modal:
- Date — calendar picker. You can collapse the calendar if you don’t need it.
- Hours — e.g. 1.5 or 1:30. Both decimal and colon work.
- Custom task dropdown — optional, if you want to specify which sub-task (“Electrical”, “Travel”, “Break”).
- Description — optional note.
Save → the line appears in the list and syncs to the server (or queues if you’re offline).

General Hours view#

When you want to see all your hours for the day/week/month in one list:

Drive time and route tracking

Mon, 01 Jan 0001 00:00:00 +0000

Drive time and route tracking#

Drive time is logged separately from work time. The reason is working-hours law: drive time doesn’t count as actual working time, but it does affect pay (in some collective agreements drive-time pay can be e.g. half of the work rate). The split also gives a clean audit trail for yearly working-hours tracking.

Start drive / End drive#

In the task view, below the work buttons, there’s a 🚗 Start drive button.

Installer status

Mon, 01 Jan 0001 00:00:00 +0000

Installer status#

This page gathers the views from which the foreman can see in real time what installers are doing and where things are slowing down.

Workers list#

Field Service → Workers.

Shows all fsm.person rows at ELT — practically every installer with rights to take tasks. Columns:

Name + Email
User — Odoo user link (elt_user_id, 200.7+)
This week’s hours — summary
Active tasks — how many
Certificates / competencies (if used)

Click a row → the person’s detail view, calendar, history.

Logging expenses

Mon, 01 Jan 0001 00:00:00 +0000

Logging expenses#

Expenses are all work-related costs not yet billed to the customer: mileage, per diems, materials (if you bought something on site from a reseller), and other (parking, waste fees, toll/ferry fees).

Typical expense categories#

Category	What it is	Tax-free limit
Mileage	Use of your own vehicle	Set yearly by the tax authority
Per diem (partial / full)	Working more than 6 h away from home	Set yearly by the tax authority
Meal allowance	Lunch on a trip	Set yearly by the tax authority
Material	Item bought on site	Per the receipt
Toll fee	Tunnel, ferry, parking	Per the receipt
Other	Anything else work-related	Per the receipt

**The office defines the exact reimbursement classes and amounts** annually, following the tax authority's rules. The PWA's expense- category dropdown shows the currently valid options.

Adding an expense to a task#

When you’re in a task:

Netvisor accounting integration

Mon, 01 Jan 0001 00:00:00 +0000

Netvisor accounting integration#

ELT’s accounting is done in Netvisor, but task invoicing, payroll, and inventory management are done in Odoo. The bridge between them is the netvisor_integration module.

What flows in which direction#

Direction	What	Schedule	Status
NV → Odoo	Purchase invoices	Daily 06:00	✅ Active cron
NV → Odoo	Payment status	Daily 07:00	✅ Active cron
Odoo → NV	Sales invoices	Automatic + manual	✅
Bi-directional	Customer sync	Manual wizard	✅
Bi-directional	Product sync	Manual wizard	✅
Odoo → NV	Payroll	Monthly, 1st day at 08:00	⚠ Cron off, manual activation
Odoo → NV	Expenses as purchase invoices	–	⚠ Cron off

Settings (admin only)#

Settings → Netvisor Integration.

Device enrollment (PWA devices)

Mon, 01 Jan 0001 00:00:00 +0000

Device enrollment (PWA devices)#

An installer’s phone is paired to the PWA biometrically. Starting the pairing and managing devices is done from the desktop (work.elt.systems): a lost phone cannot enrol or revoke itself, so creating a code and revoking a device are deliberately desktop‑only.

Where to open it#

From the installer’s card: HR → Employees (or the FSM person card) → open the installer → the “Device code / PWA” button (mobile icon) in the top button box. Visible only if the card has a user.
From the planning calendar: the “Create device code” button in the toolbar. From the calendar an installer enrols themselves; a foreman can target another installer via the person card.

This opens the Device enrollment dialog.

Payroll (HR Payroll)

Mon, 01 Jan 0001 00:00:00 +0000

Payroll (HR Payroll)#

In payroll, hours + expenses + contracted pay are combined into payslips (hr.payslip). They then flow to Netvisor for payment.

Monthly rhythm#

Typical month:

Day	Task
1–31	Installers log hours via the PWA, foreman approves weekly
30–31	Office closes the month, verifies all approvals are done
1st of next month	Payslip creation from previous month’s data
1.–5.	Payslip review, corrections
5.–10.	Sending to Netvisor for payment
14./15.	Pay date (via Netvisor)

Creating a payslip#

HR → Payroll → Payslips → Create.

Registering equipment

Mon, 01 Jan 0001 00:00:00 +0000

Registering equipment#

When you install a new device at a customer site (heat pump, ceiling heater, AC unit, lighting sensor, …), you should register it in the customer’s equipment list. This pays off in:

Warranty handling — when a fault comes up in 2 years, any installer can see which device, from which supplier, when installed.
Service history — for each device, all tasks involving it are shown.
Contract customers — the office reports the equipment in the registry.

Registering from a product line#

The easiest path: you’ve already added a product line to the task (e.g. a Nibe F-series heat pump). From there:

Adding photos to tasks

Mon, 01 Jan 0001 00:00:00 +0000

Adding photos to tasks#

Photos are the primary way to document work. They protect both the installer (“I did exactly this”) and the customer (“this is how it was before”). You can add unlimited photos — the old 10-photo limit is gone.

When to take a photo#

Before starting — overall site, the old device, wiring you’re about to remove.
During the work — phases if something turns out differently than expected (e.g. “behind the electrical panel was not what I expected”).
When done — the final result. Customers want this as a record.
Defective parts you replaced — sometimes the supplier wants a photo for warranty processing.
Wiring diagrams / device internals — helps a future installer who comes to the same site.

Adding a photo to a task#

When you’re in a task:

Equipment and warranties

Mon, 01 Jan 0001 00:00:00 +0000

Equipment and warranties (maintenance.equipment)#

Equipment registered by installers (heat pumps, AC units, electrical distribution panels, …) lives in the maintenance.equipment model. From the office, you see the overall picture, warranty info and service history.

Overview#

Maintenance → Equipments.

The list shows all ELT-registered equipment:

Name — device description + serial number
Category — device type (heat pump, AC, etc.)
Customer — customer (site)
Install date — installation date
Warranty date — expiry of warranty
Active orders — count of tasks mentioning this device

Customer-specific equipment list#

The customer form’s Equipment tab shows all devices at that customer’s sites. Easy way to find “which customer has a Nibe S1255”.

Admin

Mon, 01 Jan 0001 00:00:00 +0000

Admin#

This section is for the system administrator (group_system). It contains operational tasks that are not part of the daily office routine.

New user#

Settings → Users & Companies → Users → Create.

Required:

Name + Login (usually email)
Password (temporary, user changes)

Permissions by role:

Role	Required groups (manual)
Installer	`fieldservice.group_fsm_user`, `maintenance.group_equipment_manager`, `hr.group_hr_user`
Foreman	+ `fieldservice.group_fsm_manager`
Office (invoicing)	+ `account.group_account_invoice`
Office (full)	+ `account.group_account_manager`, `hr.group_hr_manager`
Admin	+ `base.group_system`

**v1.200.17+:** `fieldservice.group_fsm_user` now automatically brings in `stock.group_stock_user` + `hr_timesheet.group_hr_timesheet_user` via implied_ids — you no longer have to tick them manually. Existing installations (pre-1.200.17) that already have those groups set keep working; new users just need fewer clicks now.

Installer groups in detail — different PWA features need different groups:

Offline mode

Mon, 01 Jan 0001 00:00:00 +0000

Offline mode#

The PWA is designed to work in the field without internet: basements, parking garages, remote sites, “5G not here yet” country roads.

What works offline#

✅ Browsing tasks — last-fetched tasks and their details are cached.

✅ Logging hours — the modal works normally, the saved line queues.

✅ Logging expenses — same as hours, including receipt photos stored locally.

✅ Adding photos — camera opens, photo stores locally, queues for upload.

Notifications (push)

Mon, 01 Jan 0001 00:00:00 +0000

Notifications (push)#

Push notifications are the fastest way to know that you’ve been assigned a new task or that the foreman needs help. They arrive in the phone’s notification bar even when the PWA is closed or the phone is locked.

What notifications you’ll see#

Situation	Notification
New task assigned to you	“Assigned to task: FO023 — Electrical work”
Assistant request	“Help requested: Kalle / FO024”
Approval received (hours / expenses)	“Your hours for week 21 approved”
Other foreman message	Subject as the title

Tap the notification → the PWA opens directly on the right task.

Completing work and the work report

Mon, 01 Jan 0001 00:00:00 +0000

Completing work and the work report#

When the job is done you mark the task complete, optionally take the customer’s signature, and the system builds a work report PDF (hours, drive time, km, photos, route map, costs and signatures).

First, once: your own signature#

Draw your own signature once in settings — it is automatically stamped onto every work report under “EL‑Tekniikka / Installer”.

Settings → the “Signature” section.
Tap "✍️ Create signature".
Turn the phone landscape (or tap the ⟳ button) — the signing pad needs landscape orientation.
Draw your signature on the white area and tap “Save”.

The signature is saved on the server. You can replace it any time ("Sign again") or remove it ("Delete"). Saving requires internet once.

Completing the task (“Done”)#

First make sure hours, drive, products and photos are entered. Add photos from the Photos tab before marking the task done — see Adding photos.
On the task screen tap "✓ Done" → the summary screen “Work complete” opens.
Review the summary: Work hours, Drive time, Breaks, Products and the preliminary cost estimate.
Edit the “Task & summary” text into a customer‑friendly form (saves automatically). This text appears on the work report and the invoice.
Customer signature (optional): tap "✍️ Sign the task", let the customer sign → the signing time is shown. You can delete it or sign again.
Tap "✓ Confirm" → the confirmation prompt “Mark the task as done?” → “Confirm”.

**After confirming you can no longer edit the task yourself** — the timer stops, materials are recorded as consumed, and the task moves to billing‑ready. Undoing it needs a foreman. So add photos and check the details **before** confirming (or within 7 days — see [Documents and completed tasks](../dokumentit/)).

Confirmation requires internet, because the summary is saved on the server.

Documents and completed tasks

Mon, 01 Jan 0001 00:00:00 +0000

Documents and completed tasks#

Two related things: the PDF documents attached to a task, and the 7‑day finishing window for recently completed tasks.

Documents (PDFs on a task)#

A task can have PDF files attached — for example work instructions, floor plans, or the finished work report.

Opening: open the task → tap the tab selector at the top (defaults to “General”) → choose "📄 Documents".

PDFs attached by the office appear in the list with an “office” badge. You can open them but not delete them.
Add your own PDF: tap "📄 Add PDF" → pick a PDF file (max 25 MB) → add a caption if you like (“Optional caption, e.g. Floor plan 1st floor”) → “Save”.
Open a PDF: tap the row → the file opens in your phone’s PDF viewer.
Delete: only PDFs you uploaded yourself (trash icon). You can’t delete ones the office attached.

Documents attached by the office sync with the task (visible offline too). Adding a new file requires an internet connection.

Completed tasks (7‑day finishing window)#

Opening: menu (☰) → “Completed tasks”.

Updates

Mon, 01 Jan 0001 00:00:00 +0000

Updates#

Important system updates and new features in chronological order (newest on top).

28 June 2026#

You now log in to the PWA biometrically (fingerprint/face). The phone is paired once with a 9‑character code or QR code from the office. The old API key + PIN login has been removed.
The app locks automatically after inactivity and every time it starts fresh. From the desktop you can create codes, see the installer’s device list, and revoke a lost device.

Work report PDF, signature and route map#

A completed task produces a work report PDF: hours, km, photos, a daily route map, a cost breakdown and signatures. The installer creates their own signature in settings.

Drive time, allowances, documents#

Drive time is separated from work time, with automatic mileage tracking from GPS.
Allowances (km / accommodation / per‑diem / parking) appear as their own section, separate from materials.
Tasks can have PDF documents attached, and the Completed tasks view gives 7 days to finish the work report.

Office#

The PWA app name can now be set (white‑label): Settings → Field Service → PWA app name.

Address change#

The documentation site is now at docs.work.elt.systems and the development environment at dev.work.elt.systems. The old addresses still work for now.

24 May 2026#

PWA v1.3.4 — “Check for updates” button + install option restored#

A new “Check for updates” button in Settings forces the service worker to check for new versions. One click → new version in use. No more closing/opening the app multiple times.
“Install app” in the Chrome menu works again — manifest file fix.
Diagnostic panel for push-support checks (Settings → Notifications → “Show technical details” if notifications don’t work).

Faster LVISnet wholesale imports (elt_fsm v200.15)#

Watchdog now allows 4 h (previously 60 min) so 90+ min imports no longer get cut short.
Real-time progress is visible in the lvisnet.fetch.run list: “Importing OLTUOTE.txt: 87,000 / 171,540 rows…” updates every ~40 seconds.

Netvisor accounting integration installed (v18.0.1.12.3)#

Module installed in the production database, crons active (06:00 purchase invoices, 07:00 payment status).
Credentials need to be entered on the Settings page before syncs work.

This documentation site has been live since 24 May 2026. Older version updates are documented in the development machine's `Roadmap.md` and the modules' git history. Only user-visible big changes are collected here.

ELT — Work — Documentation

Creating and dispatching tasks

Creating and dispatching tasks#

Creating a task#

Customers (contacts and locations)

Customers (contacts and locations)#

Creating a customer#

Creating a location#

Installing the PWA on your phone

Installing the PWA on your phone#

Android (Chrome)#

Adding to the home screen#

Enabling push notifications#

Device setup and login

Device setup and login#

How it works in short#

1. Registering the device (once per phone)#

Planning calendar

Planning calendar#

Core view elements#

Time-range zoom#

Products and inventory

Products and inventory#

Product family#

Inviting an assistant installer

Inviting an assistant installer#

Invitation from the PWA (installer side)#

Accepting the invitation (assistant side)#

LVISnet wholesale price import

LVISnet wholesale price import#

How the import works#

Working with tasks

Working with tasks#

Task states#

Using the task list#

Approving hours and expenses

Approving hours and expenses#

Why approval matters#

Approving hours#

Invoicing (sales invoices)

Invoicing (sales invoices)#

Typical flow: task → invoice#

Invoice structure#

Logging hours

Logging hours#

Per-task hour entry#

General Hours view#

Drive time and route tracking

Drive time and route tracking#

Start drive / End drive#

Installer status

Installer status#

Workers list#

Logging expenses

Logging expenses#

Typical expense categories#

Adding an expense to a task#

Netvisor accounting integration

Netvisor accounting integration#

What flows in which direction#

Settings (admin only)#

Device enrollment (PWA devices)

Device enrollment (PWA devices)#

Where to open it#

Payroll (HR Payroll)

Payroll (HR Payroll)#

Monthly rhythm#

Creating a payslip#

Registering equipment

Registering equipment#

Registering from a product line#

Adding photos to tasks

Adding photos to tasks#

When to take a photo#

Adding a photo to a task#

Equipment and warranties

Equipment and warranties (maintenance.equipment)#

Overview#

Customer-specific equipment list#

Admin