Business Central was designed to sell and ship items, not to rent the same physical asset over and over. A rental company's core question — "is registration ABC-1234 free from Thursday 09:00 to Sunday 18:00, including the two-hour cleaning buffer, and is its service due before then?" — has no answer on a standard Item Availability page, because inventory quantity is not the constraint; a time interval on one serialised unit is. Teams end up running the actual business outside the system: a colour-coded booking grid, a Word contract template, a phone gallery of damage photos, and a folder of unrecharged traffic fines. Business Central then only ever sees the invoice at the end, so utilisation, damage recovery and cost per vehicle stay invisible exactly where the accounting lives.

We close that gap with an AL extension delivered as a per-tenant extension or, where you prefer, an AppSource-shaped app package. A Vehicle master table carries registration, VIN, category or ACRISS-style class, a link to the Fixed Asset card for depreciation, odometer, fuel or charge type, branch and current status; a Rental Reservation table holds the datetime interval, pickup and return location, rate plan and the linked Customer record. Overlap is prevented in AL rather than by convention: an availability codeunit evaluates candidate intervals against confirmed reservations, blocked periods, turnaround buffers and scheduled maintenance windows, and a validation event subscriber on reservation insert and modify blocks the double booking before it is committed. A matrix-style availability page renders vehicles down the rows and days across the columns, so a counter agent sees the same picture they used to keep on paper — but drillable into the agreement, damage record or workshop task behind any cell.

Rates are table-driven, not hardcoded. A Rental Rate Plan structure resolves hourly, daily, weekly and monthly tiers with mileage allowance, excess-kilometre pricing, deposits, insurance and waiver options, extras such as child seat, GPS or additional driver, and customer- or contract-specific pricing, then produces the charge lines. Because we build on native posting, a completed rental converts into a standard Sales Invoice or a recurring contract invoice — G/L, dimensions, VAT and posting groups all behave as your accountant already expects, and dimensions carry vehicle, branch and rate plan so utilisation and revenue slice correctly in the standard analysis views and in Power BI. Check-out and check-in are page-driven flows capturing odometer, fuel or charge level, signature and damage marks against a body-diagram grid; photos attach through the standard Document Attachment framework so the evidence travels with the record instead of a chat thread.

Traffic fines and toll charges are logged against a vehicle and offence datetime, matched automatically to the reservation covering that moment, and recharged with your admin fee — either as an invoice line or a deduction against the held deposit, with unmatched offences parked in a review queue rather than silently absorbed. Fleet maintenance runs off both interval and odometer triggers: a job queue entry evaluates service thresholds nightly, raises the workshop task, and marks the vehicle unavailable for that booking window so it cannot be rented out of the shop. Everything is exposed for integration rather than locked in the client — API pages published as REST API v2.0 / OData v4 endpoints serve availability search, quote calculation and booking creation to a website or mobile app, and the same surface feeds Power Automate flows and Dataverse-connected canvas apps for tablet-first forecourt check-in. Dedicated permission sets separate counter agent, fleet controller, workshop and finance, and the extension is built for current Business Central release waves on both SaaS online and on-premises.

This is build-to-order, not an instant download. You request a quotation, we run a short scoping call, and we confirm exactly what your operation needs — vehicle classes, rate structure, deposit and insurance handling, branches, fine sources, integrations — before a line of AL is written. Typical delivery is one working week from confirmed scope, targeted at your Business Central version. You receive the installable app and full AL source, deployment on your sandbox for UAT with a documented rollback plan, technical and end-user documentation, a live training session, a post-go-live support window, and the git repository handed over so you are never locked to us.