From what date does equipment rent start running?

From the date on the handover protocol, not the date on the contract. The contract sets the terms, but the fact that creates the obligation to pay is a specific quantity handed over on a specific day. That is why the protocol is signed by both parties and records quantities per line item rather than in the aggregate. The same applies at the other end: rent stops with the return protocol, not when the contract term expires.

How is rent charged when equipment is returned late?

Continued use is continued rent. If the term has expired and the equipment is still on site, rent keeps accruing at the same rate until the return protocol, while any late-return penalty runs alongside it, kept separate. The separation is practical: rent is the price of use and belongs on the invoice, whereas a penalty is compensation for non-performance. Merged into one line, the two become indistinguishable exactly when they need to be proven apart.

What is the difference between a daily rate and a monthly rate?

A monthly rate is usually converted to a daily one through a fixed divisor, most often 30, because otherwise the same monthly rent would cost different amounts in February and in March. A calendar basis counts the actual days in the month. The two produce different amounts for partial months, so the basis is agreed up front and written into the contract rather than decided when the first invoice is raised.

How does a lessor guard against a client who stops paying?

The cheapest protection is the one applied before handover. A credit limit per counterparty, comparing their overdue receivables against an agreed ceiling, stops new handovers automatically. Equipment already sitting on someone else's site is slow and expensive to recover, while refusing to load the truck costs nothing.

Does a late-return penalty belong on the tax invoice?

Compensation of a punitive nature is generally outside the scope of value added tax, whereas rent is a taxable supply. The two are therefore documented separately and tracked as different receivables. The exact treatment depends on the jurisdiction, but the principle of keeping them apart is universal.

Construction equipment rental - managing it from handover to payment

Renting out formwork, scaffolding and machinery looks like the simplest contract in construction. You hand over an item, you take money per day. Which is exactly why it tends to be managed most carelessly: one spreadsheet listing what went out, plus the hope that somebody will remember when it came back.

The reality is the opposite. Rental is the only contract where revenue accrues and risk sits on someone else's site at the same time. On an ordinary delivery a wrong quantity shows up immediately; on a rental the error accumulates quietly, day by day, and surfaces months later, when it can no longer be proven.

This article walks the whole cycle: when rent starts and stops running, how the amount is calculated, what happens at the end of the term and how the lessor is protected. The examples come from Construction Team, but the principles hold regardless of what you keep your records in.

The fact is the protocol, not the contract

The first confusion is also the most expensive. The contract sets the terms: rate, term, responsibilities. But the obligation to pay is created by the handover, and that almost never coincides with the date on the contract.

This is why the handover protocol is not a formality. It records:

quantities per line item, not in the aggregate. "Scaffolding handed over" is not information; "120 frames, 240 braces, 60 props" is.
the date from which rent runs for that quantity
the condition at handover, to be compared against the condition at return
signatures from both parties, because this is the document that gets pulled out in a dispute

Returns work as a mirror image and are almost never a single event. A site returns in stages: first the foundation formwork, then the slab formwork. Each return is a new protocol against a specific handover, and the difference between what went out and what came back is the active quantity - what is on rent right now and being charged.

In Construction Team, handover and return protocols generate a stock movement and change the active quantity immediately. Losses and damage are recorded on a separate inspection protocol, which proposes compensation based on a replacement value stored in advance instead of somebody hunting for it in old invoices.

Calculating the amount: unit-days

Rent is not calculated in units and it is not calculated in months. It is calculated in unit-days: how many units were out and for how many days each.

400 m² of formwork handed over on 1 June and returned on 30 June gives 12,000 unit-days. If 100 m² came back on the 15th, the calculation is already 400 × 14 + 300 × 16, not "400 for the month".

From here follow the two decisions that need to be made before the first invoice rather than after it:

The rate basis. If the rate is monthly, the daily rate comes from a fixed divisor, usually 30. If it is calendar-based, February costs less than March under the same contract. Neither is more correct, but leaving it unagreed guarantees an argument at the first partial month.

Minimum billable days. Many lessors charge a minimum of a week even when equipment comes back on the third day, because transport and preparation do not scale with days. That is agreed, not assumed.

On top come one-off charges: transport, assembly, dismantling. They are paid once and are not inventory: they take no part in the per-day calculation and there is nothing about them to return.

The end of the term: three scenarios

The contract has an end date. The equipment comes back when it comes back. The gap between the two is where most of the money leaks, and it has exactly three outcomes.

Return on time

The rarest one. The return protocol closes the cycle, the final period is charged up to that date and the contract ends.

Late return

The term has expired, the equipment is on site. The rule is simple: continued use is continued rent. Rent keeps accruing at the same rate until the return protocol, because the item is genuinely being used.

Running alongside it is the late-return penalty, if one was agreed. The two are deliberately kept apart:

	Rent after the term	Late-return penalty
What it is	price of use	compensation for non-performance
How it is calculated	rate × days × quantity	an amount per day or a percentage of the contract
Where it goes	on the tax invoice	outside it, on a separate document

Merged into one line, the two become indistinguishable exactly when they need to be proven apart: in a dispute, or under audit.

Two safeguards make automatic accrual safe: a cap on the penalty (an amount or a percentage of the contracted value) and a maximum number of days the automatic extension will run for. Without them, a forgotten return protocol generates charges for months and nobody notices until the figure becomes awkward.

Extending the contract

If the equipment is still needed on site, the contract is renewed. This is where the most common clause hides, the one software usually gets wrong: the notice period is a deadline to opt out, not a reminder. Once it passes, renewal is a fact, not a proposal. So auto-renewal belongs to the individual contract as a setting - how long the extension is, how many days of notice, and what blocks it - rather than being behaviour baked into the system.

Credit risk is managed before handover

Rental has a property that delivery does not: the asset stays yours but sits with the client. If they stop paying, you lose twice - the receivable, and access to the item.

That is why receivables control on rentals has to happen before the truck leaves, not after the third reminder. The mechanism that works is a credit limit per counterparty:

The sum of overdue receivables across all their contracts is their exposure. A client who owes you for construction work is the same risk when they ask for formwork.
If the exposure passes the agreed ceiling, new handovers are stopped.
The stop can be overridden by someone holding an explicit right, but only after they have seen the figures they are overriding, and the decision stays in the audit trail under their name.

The third point is the one usually missing. A control that anyone can bypass without realising they bypassed it is not a control, it is decoration.

A useful companion is a regular statement of account covering all of a counterparty's rental contracts at once. One rule separates a document from noise: a statement goes only to someone who genuinely owes something. An empty statement teaches the recipient not to open the next one.

Tax treatment is decided at contract level

Rent to a foreign counterparty, rent to an exempt entity and rent under reverse charge are all taxed differently. If the regime is picked per line item or copied from the previous invoice, sooner or later a document goes out with the wrong rate.

The more reliable approach is to make the regime a property of the contract: standard rate, reduced rate, cross-border supply, export, exempt supply or reverse charge. From then on every invoice under that contract inherits it, and under the zero-rated regimes the line rates are zeroed automatically.

The same applies to corrections. Credit and debit notes inherit the regime of the document they correct - a note carrying a different rate from the invoice it amends is a discrepancy that only surfaces under audit.

The small things that quietly cost money

Everything above is the obvious set of decisions. The following four are the ones nobody looks for until they hurt.

A day is a calendar date, not a moment in time. If the system stores the start of a period as an exact timestamp, the boundary depends on the time zone of whoever entered it. A contract entered in the evening gets one day more than the same contract entered in the morning. On a rental, where everything is counted in days, that is money going wrong at the source.

Periods must not overlap. If the schedule is topped up from several places - by hand, automatically, on extension - it is easy to end up with two periods covering the same day. The client pays for it twice, and the discrepancy only shows up at reconciliation.

A cancelled invoice needs a human. If someone cancels the invoice behind a rental period, issuing a new one automatically is wrong: cancellation usually comes from accounting, that is, from someone who cannot see the contract. The period should stop and wait for a decision.

One period, at most one live invoice. Otherwise the same period appears twice in the reports and nobody can say which figure is the real one.

A short checklist

Before your next handover, check that you have an answer to each of these:

Is there a protocol with quantities per line item rather than in the aggregate?
Has the rate basis been agreed (fixed 30 days or calendar)?
Are there minimum billable days?
What happens if the term expires while the equipment is on site - renewal or late return?
Is there a cap on the penalty and a maximum number of days for the automatic extension?
Do you know what this counterparty owes you across all contracts, not just this one?
Who may release a handover to a debtor, and does it leave a trace?
Is the tax regime recorded on the contract, or decided invoice by invoice?

Every "no" on that list is a place where a rental quietly loses money. If you keep your rentals in a contract management system, most of those answers should come from it rather than from the memory of whoever was on site.