I3Electrical contractorsJob sheets
Job sheets: each technician's hours, mileage and materials to invoice
Reads the week's signed job sheets and computes each technician's hours, the km and the material to invoice; the unsigned sheet first.
The problem
On Friday the job sheets come in as photos or scans, handwritten. Working out each technician's hours, the mileage and the materials, and spotting the unsigned sheet or the one passed in twice, is the work that closes the week.
Who it is for, and when
- Who it is for
- The owner or the office clerk of an installation or technical-service firm with 3–30 technicians: electricians, boilers, air conditioning.
- When
- On Friday afternoon, with the week's signed job sheets in hand: every week, and at month end for the payslips.
What you give it, what you get
You give it
The scan or the photos of the week's job sheets; if you keep one, the maintenance-contracts CSV (client, contract, from, to).
You get
The sheets the client did not sign, first; each technician's hours per day, ordinary and overtime, the km, the lines to invoice at your prices; two CSVs, for your payroll consultant and to invoice.
How it works, in three steps
- Upload the scan or the photos of the job sheets.
- Read first who did not sign and which hours to correct.
- Send the hours CSV to your payroll consultant and import the lines to invoice.
On its own, in a flow. Connect it to the webhook: on Friday you upload the sheets and get the week closed with the two CSVs — or, when a signature is missing, the question whether to invoice the rest now.
The rules it applies
In the agent's own words: what it checks and what it never does.
- Hours from start, end and pause — never estimated
- The unsigned sheet stays off the invoice, and comes first
- A sheet scanned twice is counted once
- Every total is recalculated from the lines and compared with the printed one; what cannot be read stays empty and is said in the notes, never invented.
A real example
A case from the demo catalogue, with anonymised documents.
Friday: the week's job sheets
Friday afternoon at an electrical contractor in Bologna: the office has run the week's yellow job-sheet copies through the scanner, eight pages in one file. The hours go to the payroll consultant for the payslips — on Tuesday Bertolini and Neri spent nine hours on the Santoro site —, the km to the mileage refunds, the hours and material of the paid call-outs to the invoice. One sheet went through the scanner twice, and the bakery's is not signed: the customer was out.
The recorded result
Document read.
real time 1 min 44 s17 credits
Frequently asked questions
How does it work out the hours?
From the start, end and break written on the sheet: never estimated. An unsigned sheet is not invoiced and comes first in the list, and a sheet passed in twice is counted once.
What does it cost, and how long does it take?
Usually 12–26 credits for a week of eight job sheets (≈ €0.50–1.07) and 1–3 minutes. It depends on the sheets: more of them, skewed photos or hard handwriting cost more. The recorded example cost 17 credits in about 2 minutes.
Can it run on its own, in a flow?
Connect it to the webhook: on Friday you upload the sheets and get the week closed with the two CSVs — or, when a signature is missing, the question whether to invoice the rest now.
Who checks what the agent did?
You do — and it takes a minute, not an afternoon. Every run is a trace: the live timeline, each tool call, each document read, the cost per step, the confidence and sources. Actions that leave the building wait for your approval. The platform never sends, never touches a live store, never moves money.
Where does my data live, and how do you handle GDPR?
Your data is stored in the EU, on one server in Germany. The EU/US data-region setting limits which models an agent can be saved with, not where your data is stored. A no-retention mode and a local runner on your own machine are available. Your plan sets how many days your data is kept — you can change it — and when they run out it is deleted automatically. You download each run's results and delete files, agents and connections in the console; an owner deletes the whole workspace and each person their own account from Settings. The “Your data” page names the services that handle your data.
Related agents
- I1Bill of materials for the wholesalerFrom the panel builder's list, a manual or a photocopy to the order: both codes, the boxes, the questions.
- I2Delivery notes (DDT)Reads the supplier's delivery note — photographed on site too — and tells you line by line what arrived, what is short and what is over against the order.
- I4End-of-works file and subcontractor fileReads an installation's or a subcontractor's folder — PDFs and phone photos — and tells you whether the file can be handed over or the firm may start on site, with what is missing and the law that asks for it.
Try it on your own documents
The demo shows the recorded cases without an account; with your own workspace you run it on your files.