Inside the service
When a company rents its machines out to an external customer, readings are usually collected late at contract closing, and the amount due is an estimate one side accepts and the other rejects. This module runs the opposite direction of inbound rental: a contract carrying its terms and the customer's site with its geographic boundary, and daily documentation of every operation through a photographed reading captured in its moment — so the amount due is computed from the difference between two documented readings, not an estimate, and a statement is issued that both sides accept because it stands on a record.
01
A contract that knows its customer and site
The customer is registered with a record of their own, and the contract carries its duration, price, and billing unit from the same six options — from hours to a flat monthly rate — plus the weekend rule, a billing cycle of monthly, biweekly, or weekly, and the customer's site with a geographic boundary defining where field recording is valid. Everything the contract will later be settled on is written into it from day one, never left to end-of-term judgment.
02
Two recording modes, set by the contract
If your own operator is with the machine at the customer's site, he scans its code at the very same public scan station used for inbound rental — each direction has its own independent serial range, so the two never mix. If the customer operates with their own driver, their supervisor records through a dedicated secure link with no account, and the scan station outright refuses customer-operated contracts, so no record slips in through the wrong channel.
03
One strictness for both sides
The customer's recording is subject to exactly what yours is: the geographic boundary is enforced whenever the customer's site has one defined, and a record without location capture is refused; a reading lower than its predecessor is turned back; and a meter photo is required wherever the billing unit is hours or kilometers, while trips, tonnage, and flat-rate contracts are settled on attendance and counts. The party doing the recording never gets to soften the controls that govern it.
04
From reading to invoice, no gap
Documented operating days accumulate into a periodic statement tied to the contract, the amount due is computed from the recorded readings' difference rather than an end-of-term estimate, and the invoice is generated exclusively from the statement — no invoice exists without a statement behind it. The module is fully independent from inbound supplier rental, so a company activates only the direction it works in, or both together.
