Office on ELT — Work — Documentation

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:

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.

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:

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:

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.

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.

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
Installer	`fieldservice.group_fsm_team`, `stock.group_stock_user`, `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`

* hr.group_hr_user is needed for installers to log their own hours and expenses.