The customer → asset → invoice chain

This page describes how your data connects: customer, site, asset, contract, work order, technieker, report and invoice. Use it when setting up your environment and when cleaning up existing data.

What you use this for

• Creating a new customer completely and in the right order.
• Identifying the missing link when a report or figure doesn’t add up.
• Deciding what you register as an asset and what you don’t.
• Attaching existing interventions to the right asset afterwards.

Who can use it

Administrators and service managers setting up the environment or cleaning data.

Prerequisites: rights to create customers, sites and assets.

The chain

Customer
  └── Site / location
        └── Asset / installation
              └── Maintenance contract
                    └── Work order (intervention)
                          └── Technieker
                                └── Report + signature
                                      └── Invoice

Every link hangs off the previous one. Skip one, and everything after it loses meaning.

What each link provides

Link	What you gain when it’s right	What you lose when it’s missing
Customer	One file per customer	Loose contacts nobody sees together
Site	Work per location, correct addresses, routes	Techniekers looking for the wrong building
Asset	History per device, warranty, health	A pile of interventions with no pattern
Contract	Recurring revenue, automatic maintenance	Maintenance that depends on who remembers
Work order	Schedulable, measurable work	Work that only exists in someone’s head
Technieker	Hours, performance, accountability	No view of capacity
Report	Proof for the customer, knowledge for your team	Disputes you cannot win
Invoice	Revenue that matches delivered work	Invoices nobody can justify

Do not skip the asset

The asset. It is tempting to attach an intervention straight to a customer — it is quicker to enter. But then you build no history per device, and without history per device, warranty tracking, reliability figures and substantiated replacement advice simply do not exist.

Building the chain

1. Create the customer in Customers & assets.

2. Add their sites — one per location, not one address field with everything in it. See Sites.

3. Register the devices on the correct site, with brand, type, installation date and warranty.

4. Set up a maintenance contract if there is recurring work. See Maintenance contracts.

5. Create work orders from the contract, a customer report or a QR report — always with the asset attached.

6. Assign a technieker and schedule the job. See Planning.

7. Have the technieker write the report and get it signed in the app.

8. Invoice the delivered work. See Invoicing.

Where the chain is used

Once the chain is right, the instruments come free — they all read the same chain:

• The Customer File 360° shows the whole chain per customer.
• Asset Intelligence calculates reliability and health per device.
• The Service network map shows the chain geographically.
• Parts Readiness predicts what a job needs based on what happened to this asset before.

Troubleshooting

Do I really have to register every device? Register what you maintain or repair. Not loose consumables.

My customer has one address. Do I need a site? Yes. One site is enough, but the link has to exist — everything hangs off it.

Can I attach interventions to an asset afterwards? Yes, and it is worth it. Your history immediately becomes more usable.

What if a device moves to another site? Change the site on the device. The history moves with it.

Next step

• Full service flow — the same chain, as a process
• Maintenance flow — recurring maintenance
• Customer File 360°
• Asset Intelligence
• Sites
• Invoicing