Equipment Rental and Hire Management

The problem rental companies hit in SAP Business One

SAP Business One is built around ownership transfer. You buy an item, you hold it in a warehouse, you sell it, it leaves. A rental business does the opposite: the asset never leaves your balance sheet, it goes out and comes back, and what you sell is time.

That mismatch breaks almost every standard document. A Sales Order cannot express "three excavators from the 4th to the 19th" — there is no period, no return date, and no way to stop the same excavator being promised to two customers next Tuesday. Stock levels tell you an item exists in a warehouse but not whether it is on hire, in for service, quarantined after damage or genuinely available. Invoicing is worse: hire is billed weekly or monthly in arrears for whatever was actually out, pro-rated for part periods, adjusted for a late off-hire, plus consumables, transport, fuel, operator hours and damage recharges. In standard B1 someone rebuilds that in a spreadsheet every cycle and keys the invoices manually.

The result is double-booked kit, revenue leaking on unbilled extension days, and no reliable utilisation figure to decide what to buy next.

What ECOSIRE builds

We build a SAP Business One add-on that models the hire lifecycle properly, inside your company database, posting to your existing General Ledger.

Rental asset register

Each hireable unit is tracked as a serialised or batch-managed Item, extended with User-Defined Fields for asset number, acquisition cost, current status, service interval, meter reading and current location. Where you need a richer record — ownership, depreciation reference, certification expiry — we add a Rental Asset User-Defined Object (UDO) linked to the Item master, so it inherits B1 authorisations and Change Log history. Status is a controlled list: available, on hire, in transit, under inspection, in workshop, damaged, written off. Only assets in an available state can be committed.

Availability calendar and reservations

A reservation engine stored in User-Defined Tables holds every committed and provisional booking with start and end datetimes per asset or asset group. The calendar view runs inside the B1 client and shows, per asset class and per warehouse or depot, what is out, what is booked, what is in the workshop and what is free — with overlap detection that blocks a double booking at the point of entry rather than at dispatch. Group-level bookings allocate a specific unit at dispatch time so the sales desk can quote a class without pinning a serial.

Rate cards and pricing

Rate cards are implemented as UDTs keyed by item or asset class, customer or Business Partner price group, and period type — hourly, daily, weekly, four-weekly, monthly — with minimum hire period, day-rate tapering for longer hires, weekend and public holiday handling, and non-working-day exclusions. Contract-specific and customer-specific overrides are supported, along with an approval step for discounts beyond a threshold using a native B1 approval procedure.

Rental contracts, on-hire and off-hire

A Rental Contract is a UDO with its own numbering series, carrying the Business Partner, hire period, rate card, delivery and collection addresses, deposit, insurance terms and lines of assets or asset classes. On-hire generates a dispatch note, moves the asset by Inventory Transfer into an on-hire warehouse or location so your stock report is truthful, records the outbound meter reading and condition with checklist and photo references, and flips the asset status. Off-hire records the return date and time, the inbound meter reading, a damage and cleanliness inspection, and any missing accessories. If the asset comes back late, the extension days are automatically brought into the next billing run rather than being noticed by chance.

Periodic rental invoicing

A billing run computes charges for every open contract in a period: hire days by rate card with pro-rating for part periods, minimum-period enforcement, extension days after a late off-hire, credit for an early off-hire where the contract permits, plus consumables, transport in and out, fuel, operator hours and standing charges. The run produces A/R Invoices through the Service Layer against your normal item and tax setup, so VAT, customer ageing and statements are correct with no manual journal. Runs are previewable and reversible before posting, and each invoice line traces back to the contract line and the date range it billed.

Damage, loss and deposits

Damage identified at off-hire raises a Damage Charge document that either recharges the customer through an A/R Invoice against a damage revenue account, draws against the held deposit, or routes to insurance — with a workflow so a large recharge needs approval. Lost or unreturned assets post a write-off to the account you nominate and move the asset to a written-off status so it can never be booked again. Deposits are tracked per contract with receipt and refund against a deposit control account.

Maintenance and utilisation

Service schedules are driven by meter reading or elapsed time. A due asset is automatically blocked from booking and a workshop job is raised; on completion the parts consumed post as an Inventory Issue and labour as a Journal Entry so maintenance cost accumulates per asset. Utilisation, revenue per asset, revenue per asset class, downtime and cost-per-hour reports are delivered as queries and Crystal Reports layouts, giving you an evidence-based fleet purchasing decision.

Who this is for

Plant and equipment hire firms, scaffolding and formwork hire, event and AV equipment rental, portable accommodation and site facilities, generator and power hire, and construction companies with an internal plant division that cross-charges projects. You should already be running SAP Business One 10.0 and have a fleet large enough that spreadsheet availability tracking is failing.

If you rent a handful of items and bill a flat monthly fee with no returns, availability logic or damage recharges, this is more than you need.

Technical approach

Built on the SAP Business One Service Layer (REST/OData) for document creation and posting, with the DI API for objects the Service Layer does not cover. Rental Contracts, Rental Assets, Damage Charges and Workshop Jobs are registered as UDOs so they get standard B1 authorisations, approval procedures, data ownership and Change Log. Reservations, rate cards and meter history live in UDTs. Inventory movement uses real Inventory Transfers between depot and on-hire locations rather than a shadow stock table, so your stock and asset reporting never diverges. Supported on SAP Business One 10.0, SQL Server and SAP HANA, on-premise or cloud-hosted.

How delivery works

1. Scoping call. We go through your fleet structure, depots, rate cards, minimum hire rules, billing cycle, damage and deposit policy, and how you currently track availability. Output is a written functional specification. 2. Fixed quote. Price and timeline against that specification, in writing. 3. Build. Developed against a copy of your company database with your real item masters, warehouses, tax codes and chart of accounts. 4. Install in test. Deployed to your test company. You re-run a closed billing period and reconcile our billing run against what you actually invoiced. 5. Install in production. Cutover including the asset register, open contracts, assets currently on hire with their outbound meter readings, and deposits held. 6. Support. A support window covering defect fixes against the agreed specification, with source code handed over.

Typical lead time is two to four weeks from signed quote. This is built to order for your company file — there is no shelf version to download.