A distributor running its own fleet has a real operational day that Business Central does not model. Warehouse Shipments and Posted Sales Shipments tell you what left the building, but not which van it left on, in what stop sequence, who signed for it, what came back undelivered, or how much cash the driver is carrying at 6pm. Teams fill the gap with a WhatsApp group, a printed manifest and a spreadsheet, then spend the next morning matching signed paper against posted shipments and counting COD envelopes against a cashbox. The Sales Shipment Header, Warehouse Shipment Line and Cust. Ledger Entry tables each hold part of the truth, but nothing joins them into a trip, and nothing in the base app carries a driver, a stop time, a signature or a failed-delivery reason.

We build a Dynamics 365 Business Central extension in AL that adds that missing layer inside the same database and the same posting rules. New tables model Delivery Trip, Delivery Stop and Delivery Event, with the stop pointing back at the source Warehouse Shipment or Posted Sales Shipment rather than duplicating it. A planning page lets dispatch build a trip from released warehouse shipments, assign a driver and vehicle, sequence the stops and set a delivery date and time window. Table extensions stamp the trip and stop reference onto the shipment records so a warehouse or accounts user can always answer "which run was this on" from the document they already have open. Codeunits hold the trip state machine — planned, dispatched, in progress, closed — and event subscribers on the posting codeunits keep the stop in step when a shipment is posted, corrected or undone, so the delivery layer can never drift away from the ledger.

Drivers get a mobile-web task view rather than a native app: API pages exposed over Business Central REST API v2.0 (OData v4) plus a lightweight, phone-sized page that runs in the Business Central web client, or a Power Apps canvas app on Dataverse — whichever fits your licensing and device fleet. A driver sees only their own open stops for today, in sequence, with the customer address, contact number, items and amount due. Arriving at a stop they capture proof of delivery: recipient name, a signature drawn on the phone, photos of the goods or the door, GPS coordinates and a timestamp, all stored against the stop in Media/Media Set fields so the evidence stays inside Business Central and rides your normal backup. A partial or failed delivery is captured with a configurable reason code and a line-level delivered quantity, which drives return-to-warehouse handling instead of becoming an email to the office.

Cash and COD reconciliation is the part that usually justifies the project. Every stop marked as cash-collected accrues against the driver's open run. At end of day the driver closes the run with a declared cash total; a Driver Cash Reconciliation page shows expected versus declared, the per-stop variance, and the unreturned goods. On supervisor approval the extension creates cash receipt lines applied to the correct Cust. Ledger Entry records and posts through the standard Cash Receipt Journal, using your existing bank and cash accounts, posting groups, dimensions and number series — we never write a General Ledger Entry directly. Delivery KPI reports and Power BI-ready API pages then give you on-time rate, stops per driver per day, failed-delivery reasons by cause, average dwell time per stop and COD variance by driver over any period.

This is a build-to-order product, not an AppSource download. After you request a quotation we run a scoping call, confirm your Business Central version and deployment (SaaS or on-premises), your delivery process, your COD and cash-handling rules, and how drivers will get devices. We then quote a fixed scope, build the extension against your version, deliver it to a sandbox for UAT, and go live with you. Typical delivery is one working week from confirmed scope. You receive the AL source, the deployable app package, permission sets, technical and user documentation, and a training session, and the code is handed over in a git repository you own.