When a stop is completed, the system asks the address one question: how is this work type paid here? The answer is the pricing type, and there are five.
Per task
The everyday answer. Every completed stop becomes one invoice line, quantity 1, at the address's price for that work type. Two dispatches on one day: two lines (the second flagged Possible duplicate for a human to judge). Two routes over the same address in one dispatch: one stop, one line.
Per task by snow depth
Per task for plowing contracts priced by how much snow fell. The address carries depth bands (0-3 in, 3-6 in, 6 in and above, or the same in centimetres) shared by every work type on it, one price per work type and band, and every completed stop becomes one line priced by the band the recorded snow depth falls in. The depth comes from the dispatch, or from the stop's own override; a stop with no depth at all bills the lowest band, and the line says so. It is switched on for the address with the Snow depth rules panel, not picked per work type. The whole model, from the bands to the invoice badge and the minimum depth, is in Pricing by snow depth.
Hourly
Every completed stop becomes one line whose quantity is the hours between check-in and check-out, to two decimals. This is why an hourly stop cannot be completed without a check-in: without it there is no duration. If the times are missing anyway, the line is drafted with quantity 0 and a note, so it is visible rather than silently wrong. Routes with Hourly time tracking switched on record the time per stop for exactly this purpose.
Per season
The customer pays a fixed amount for the season, so completed stops produce no lines. The work is still recorded and shown in the portal, but the money comes through Seasonal invoicing, which splits Price per season into the number of instalments set under Payment rates and drafts them as "Season fee 1/2", "2/2", and so on. An address whose contract has ended is no longer offered for seasonal or fee invoicing.
Note that per season only silences the customer side. If a subcontractor does the work, the owner's cost for the stop is still settled per stop: the subcontractor is not on a seasonal deal unless its own price rows say so.
No price
Nothing is billed, and nothing is drafted, but the work is not forgotten. A completed stop without a price stays billable: the moment a real price is set on the address, the system offers Bill completed work? for this season's unbilled dispatches (see Bill completed work that had no price). The same is true when a work type's price row is simply empty. The address list shows Missing prices as a reminder.
An address may be saved with no pricing type at all; it behaves as No price until one is chosen.
Per work type
Turn on Set pricing type per work type and each work type gets its own answer: salting per task, snow removal hourly, on the same address. A work type's own pricing type wins over the address's; work types without one follow the address.
Which price, then
Once the type is known, the amount comes from the first of these that exists:
- a rule price on the address whose period matches the planned time,
- the address's price for the work type,
- the generic work-type price from Settings → Work types.
Owner and subcontractor each have their own rows, so each link of the chain answers the question for itself. Extra fees (Material and Fee) sit on top of all of this and are billed through fee invoices, not per stop.