Skip to content
Rented heavy equipment on a project site
Fleet & assets

What you pay the supplier is built on documented hours

Manage equipment rented from external suppliers: the contract and its terms, a daily timesheet documenting actual operating hours, and invoice matching against what was recorded — not what was ordered.

Before

What happens today without this module

  • 01The invoice arrives with numbers no daily record can be checked against
  • 02Downtime days get counted as operation because nobody documented them
  • 03The contract and its terms live in one file, the operation in another
Capabilities

Exactly what this module does

  • Supplier contracts

    The billing unit (hours, kilometers, daily, monthly…), the weekend rule, and fuel and maintenance responsibility clauses.

  • A public scan station

    The operator opens and closes a shift by scanning the machine’s code — with a meter photo and location, and without seeing a single financial figure.

  • 14 fraud-detection flags

    From meter rollback to a photo reused from another day — critical ones halt billing until reviewed.

  • Supervisor sign-off with signature

    Batch approval of closed days with an uploaded signature, and deductions documented with their reason and photo.

  • Statement, then invoice

    An invoice can only be issued from a signed statement — no invoice written from thin air.

  • Supplier portal

    Read-only access through a secure link created once and revocable anytime, with a dispute option on a specific day.

Inside the service

How it actually works in your company

A machine rented from an outside supplier usually gets its invoice paid against numbers the supplier himself sends — no daily log to review, no documented distinction between operation, standby, and breakdown. This service starts from the contract and its terms, documents every operating day through a field scan carrying the meter photo and its location, and passes it through fraud-detection rules before it ever enters a statement. No invoice is issued except from a documented statement, and the company pays no hour that a record has not proven.

01

The contract governs every operating day

A supplier contract is registered with its billing unit from six options — hours, kilometers, trips, tonnage, flat daily, or flat monthly — along with a weekend rule of full count, half, or exclusion, and clauses assigning fuel, routine maintenance, and emergency maintenance responsibility between the company and the supplier. These clauses are not ink on paper: the field scan page displays them to technicians and blocks any action that falls on the supplier under his own contract.

02

A scan station with no accounts and no figures

The operator opens and closes the machine's shift by scanning the code stuck on it from his phone, with no login. He picks his name from the list of operators approved for that specific machine, captures the meter photo, and records the reading along with coordinates and the device fingerprint; at closing he documents standby and breakdown hours each on its own. The page shows no financial figure at all — whoever operates the machine never sees what is billed for it.

03

Rules that refuse before recording

Eight rules turn a record away at the very moment: a reading lower than the last known one, a meter delta physically impossible for a single day, hours exceeding the actual shift duration, an operator not approved on the machine, a shift shorter than the minimum, a photo that is not a live camera capture, a location outside the project's boundary, and a signal weaker than the acceptable threshold. Whatever is refused here never reaches any statement at all.

04

Critical flags stop billing

Whatever passes but carries suspicion is flagged, never deleted: a photo matching another day's, a reading that contradicts the machine-read digits of its own photo, excessive daily hours, heavy operation with no matching diesel dispensing, approval done in rapid bursts, and a month-end jump. The flags that cast doubt on the billed quantity itself hold the day out of the automatic statement until administration explicitly approves it from a dedicated alerts board.

05

Signature, then statement, then portal

The supervisor's approval of closed days requires his signature uploaded with the approval, and deductions are recorded against their days with their reasons. The periodic statement is built automatically from qualifying days, an invoice can only be created from an existing statement — never written from nothing — and the monthly hours sheet is produced as a print-ready document. The supplier views through a secure link created once and revocable at will: read-only access, with the ability to open a dispute on a specific day.

The flow

How the process runs end to end

  1. 01

    Contract

    Record its terms, billing unit, and clauses

  2. 02

    Operate by scanning

    Daily open and close from the public scan station

  3. 03

    Signed approval

    The supervisor approves the days with his signature and deductions

  4. 04

    Statement and invoice

    A periodic statement gets signed, then the invoice is issued from it

After rollout

What actually changes

No promises built on numbers we don’t know about your company. What follows is the structural difference of wiring this module into the rest of the platform.

A vetted invoice
checked against a daily record
Downtime counted
not paid as operation
The contract at hand
its terms next to its operation

Limits of this module

The supplier holds no account and signs nothing inside the system; the portal is read-only.

Try Renting from Suppliers on your own assets — not a generic example

We tailor the demo to your operation, starting with the module that blocks your team today.