Proof of Delivery Capture: A Practical Guide for Dealers

Receiver signing for an excavator delivery

Proof of delivery capture means recording, at the moment of handover, who received the goods, what was handed over, in what condition, where and when, and storing that record where finance, parts and service can use it. For an equipment dealer, that covers machines, attachments, parts orders, rental drop-offs and workshop returns. Done on paper, the record often arrives days late or never. Done electronically and tied to your dealer management system (DMS), it becomes the trigger for invoicing, the answer to a dispute, and clean data for any AI tools you add.

This guide covers what a delivery record must contain, how to capture it from dispatch to signature, how to treat exceptions, which Australian rules apply to storing it, and where AI inside a DMS or ERP earns its place.

Moderndms

Bring Dealer Workflows Into One System

MDMS is a purpose-built system for equipment dealerships, bringing sales, service, parts, rental and finance workflows into one platform.

Book a demo

TL;DR

A proof of delivery is the completed record of what was actually handed over, to whom, when and in what condition. A delivery docket or a tracking status is not the same thing.
Capture it on the device in the driver’s or technician’s hand, with mandatory fields and an offline mode, so nothing depends on paperwork back at the depot.
Record shortages, damage and refusals as exceptions with notes. That is where the record earns its value.
Store records so they cannot be altered, can be retrieved and read, and are kept for the period tax law expects, generally five years.
AI is only as good as the records beneath it. Structured delivery data linked to orders, assets and invoices is what makes AI in a DMS useful.

What proof of delivery is, and what it is not
What counts as proof of delivery in Australia
What an electronic delivery docket should capture
How to capture proof of delivery, step by step
Recording partial, damaged and refused deliveries
Storing and retrieving delivery records in Australia
How delivery records feed service, rental, parts and finance
Where AI fits in a DMS or ERP
Our perspective: capture first, then automate
Getting started with MDMS
A checklist before you switch
FAQ
Sources

What proof of delivery is, and what it is not

Three terms get mixed up on dealership floors, and the confusion causes real disputes.

Delivery docket: a list of what should be in the consignment. It is a plan, written before the truck leaves.
Delivery tracking: a carrier status such as “in transit”. It tells you where a shipment is, not that anyone accepted it.
Proof of delivery (POD): the completed record of what was handed over, in what condition, to whom and when. It is the only one of the three that works as evidence.

One document can serve as both docket and proof, which is why the terms blur. A docket becomes proof once it is completed at the point of handover: the receiver’s name and signature or a timed photo, the time, the count delivered and the condition on arrival. A tracking number confirms a carrier status but is not the documentation showing the item was handed over.

For dealers, this matters because your deliveries are rarely a simple parcel. A forklift delivered to a warehouse, a compact excavator dropped at a job site, a pallet of filters sent to a regional customer and a hire unit placed on a fenced yard all carry different evidence needs and different dollar values.

What counts as proof of delivery in Australia

No single form is mandated for every business delivery. Carrier terms show what the market accepts. StarTrack’s terms say proof of delivery may be a photograph of the goods at the delivery address, an acknowledgment signed there by any person present, or confirmation of a secure code entered to access a parcel locker. Notice the phrase “any person present”. A signature from a stranger at the gate proves handover to someone, not to your customer’s authorized receiver. If your goods are high value, your own record should capture more than the minimum a carrier accepts.

Electronic records are also recognized in law. The Electronic Transactions Act 1999 (Cth) sets rules on the validity of electronic transactions and communications under Commonwealth laws. It is not a checklist for delivery dockets, and you should confirm with your adviser how it applies to your contracts, but it is one reason a signature captured on a tablet is a normal business practice rather than a workaround.

What an electronic delivery docket should capture

A useful delivery record may include dispatch and collection times, live status updates, the recipient’s signature or name confirmation, delivery time and location, photos, and notes or exception reasons. For an equipment dealer, we would turn that into a field list your team can build into every delivery:

Field	Why it matters to a dealer
Linked order, work order or rental contract	The record triggers the next step: invoice, hire start, warranty clock
Serial numbers or asset ID	Proves which unit moved, not just “one machine”
Quantity delivered vs ordered	Catches short shipments on parts orders
Receiver name and signature	Shows who accepted, ideally with their role
Timestamped photos	Condition at handover, including existing damage
Location stamp	Confirms the right site or yard
Meter or hour reading	Starts a rental or warranty period on a fact, not a guess
Exception reason and notes	Records damage, shortages, refusals
Driver or technician ID	Accountability for the handover

The hour meter and serial number are the fields generic delivery apps tend to skip, and they are the ones that settle arguments in equipment businesses. If you hire out machines, the same discipline carries over to returns: our guide to the off-hire process and AS 2550.10 shows how condition evidence at pickup stops billing disputes later.

How to capture proof of delivery, step by step

Reliable delivery evidence starts at the dispatch stage. Systems that follow a consignment from inventory allocation through to final delivery give the most consistent data. That is the design principle behind a good setup: data should travel once, from order to dispatch to handover to invoice, without anyone re-keying it.

Create the delivery from the source record. The sales order, parts order, rental contract or completed work order should generate the docket. Nobody types the lines again.
Allocate stock and assets. Pick the parts, confirm the serial-numbered unit and mark them as on the way. This is where inventory and asset tracking pays off, because the docket reflects what actually left the yard.
Pre-delivery checks. For machines, photograph the unit and record the meter reading before it leaves.
Dispatch to a mobile device. The driver or field technician receives the docket on a phone or tablet.
Capture at the door. The receiver confirms quantities, signs with name and role, and the app takes photos and a location stamp.
Enforce mandatory fields. A job should not close without the required receiver name, signature or photo. Digital platforms can make these fields mandatory so a driver cannot finalize a job without meeting your standard.
Work offline. Rural sites and job yards often have no signal. The app should capture everything on the device and sync when coverage returns.
Sync and trigger. The completed record attaches to the order, asset and customer, and releases the invoice or starts the hire.

Our proof of delivery feature is built around this sequence for signature and photo capture, and our offline field service app covers the technicians who deliver, commission and return to the workshop.

Match the evidence to the risk

Not every drop needs a full photo set. Match the documentation to the risk of the delivery: a box of filters to a long-standing account needs a name and signature, while a A$150,000 machine needs photos, meter reading, serial confirmation and a named authorized receiver. Over-documenting low-risk work slows drivers down, and under-documenting high-risk work leaves you exposed. Set two or three delivery profiles in your system and let the order value or item type choose the profile automatically.

Evidence requirements for low- and high-risk deliveries

Recording partial, damaged and refused deliveries

The signature is the least interesting part of a delivery record. The valuable part is the exceptions: what was short, what was damaged, what was refused and what happens next. Teams should record partial deliveries, damage and refusals as clear exceptions, with notes and a defined next action.

A workable exception process looks like this:

Short shipment: the receiver confirms the actual count. The system marks the balance as back-ordered and keeps the invoice to what was delivered.
Damage at handover: photograph the damage with the receiver present, note it on the docket and open a claim or warranty case from the same screen.
Refusal: record the reason, return the goods to stock, and flag the sales or parts contact so someone calls the customer the same day.
Nobody on site: do not leave the goods under a generic “delivered” status. Record a failed attempt, with a photo of the site, and reschedule.

The last point has regulatory weight in the parcel world. In a review of Signature on Delivery, the Commonwealth Ombudsman noted that consumers reasonably expect delivery services to confirm that someone is present to accept a parcel and to record those details as agreed in the service terms. The principle carries across: if you promise a signed handover, your process must deliver one.

When exceptions connect to your warranty and parts workflows, disputes shrink. A claim raised at the door, with photos, is far easier to recover from a carrier or supplier than one reconstructed a fortnight later.

Storing and retrieving delivery records in Australia

Capturing the record is half the job. You also need to keep it in a form you can produce years later. The Australian Taxation Office’s ruling on electronic records, TR 2018/2, sets out the expectations for records that support your tax position. In summary, electronic records should be stored so unauthorized alteration is restricted, be reproducible, and be retrievable in an accessible format such as English when requested. They are generally kept for five years after preparation or obtaining, or after completion of the transactions, whichever is later. Check the ruling, and your accountant, for how it applies to your business.

Delivery records also carry personal information. Names, signatures and photographs may be personal information under the Privacy Act, and organizations covered by the Act must follow the Australian Privacy Principles, as the Office of the Australian Information Commissioner explains. Practical consequences for your process:

Limit who can view photos taken on customer sites.
Avoid photographing people when a photo of the goods will do.
Set a documented retention period that reflects tax, contract, insurer and carrier-claim requirements, then apply it consistently.
Keep records attached to the order, so a search by customer, serial number or invoice finds the proof in seconds.

Paper dockets in a ute glovebox fail every one of these tests. A DMS that stores the signed record against the order, with an audit trail, passes them by design.

How delivery records feed service, rental, parts and finance

A captured delivery should not sit in a folder. It should move other work forward.

Parts: a confirmed delivery closes the picking cycle, updates stock and releases the invoice. Short deliveries create back-orders automatically. See how our parts and warehouse management handles this.
Rental: a signed delivery with photos and a meter reading starts the hire clock on evidence. On return, the same checks create a clear before-and-after comparison. Our rental contract and fleet software ties delivery and off-hire records to the contract.
Service: a unit returned to the customer after repair gets a signed handover that closes the work order and starts any service warranty period.
Sales and commissioning: a delivered machine moves from build order to commissioned asset, with the handover record attached for the life of the unit. The asset tracking guide shows how this saves administrative hours.
Finance: a completed delivery is the cleanest trigger for invoicing. Records that sync with accounting, including Xero or MYOB, mean finance bills what was delivered, not what was ordered.

A word of caution on integration: pursue it where it solves a specific, identified pain point. For a small dealership, consistent process and responsive customer communication can matter more than a sprawling technical build. That is the reason we favor modular rollout: start with the department losing the most time, prove it, then add the next.

Where AI fits in a DMS or ERP

AI is now a standard part of the conversation about dealer management systems and ERP platforms. The honest starting point is that AI does not fix a broken delivery process. It works on the records you give it. If delivery data is scattered across paper dockets, text messages and a spreadsheet, there is little for an AI tool to reason over. If every delivery is a structured record linked to an order, a serial number, a customer and an invoice, AI has real material to work with.

Here are the kinds of jobs that structured delivery data makes possible for an AI layer in a DMS or ERP:

Finding things in plain language. Asking “which deliveries to this customer had damage notes this year?” instead of building a report.
Summarizing exceptions. Turning a week of short shipments and refusals into a list of patterns by supplier, route or product line.
Flagging gaps. Spotting deliveries closed without a signature, photo or meter reading before they become disputes.
Drafting communication. Preparing a follow-up to a customer about a refused delivery or a back-ordered balance, for a person to review and send.
Speeding up admin. Reducing the keying and chasing that eats into a service manager’s or parts counter’s week.

These are the use cases to test any vendor against, including us. Ask where the AI reads its data from, whether it can see across modules or only one, who can access what, and whether your data stays yours.

MDMS AI and AI-enabled users

MDMS AI is available as an add-on to the platform at A$449 per month, with AI-enabled users at A$29 per month per seat. That structure lets you switch AI on for the people who will use it, such as the service manager, parts lead or rental coordinator, rather than the whole company. Details of what is included are on the MDMS home page.

The reason we put delivery capture ahead of AI in the rollout order is simple: our system is designed so data travels once, from quote to order to delivery to invoice. Clean, connected records are the foundation that makes any AI feature worth paying for.

Our perspective: capture first, then automate

We build for equipment dealers, and we see the same pattern: dealerships want AI before they have fixed the handover. We would reverse that order. A dealership that captures deliveries properly, with serial numbers, photos, meter readings, named receivers and exceptions, gains time immediately. Our customers’ testimonials point to savings of up to 10 hours a week on administrative tasks, and delivery paperwork is one of the places that time hides.

Three things shape how we design delivery capture in MDMS:

Department-specific workflows. A parts delivery, a rental drop-off and a machine commissioning are different jobs. Generic dealership software treats them the same. We do not.
Modular adoption. You can begin with the module that hurts most, with set-up designed to take under an hour, and add others as your team is ready.
Data ownership. Your delivery records, signatures and photos belong to you, with no lock-in. That matters when retention rules ask you to retrieve records years from now.

When those records feed an AI layer, the answers you get are grounded in your own operation rather than a generic model’s guess.

— ModernDMS

Getting started with MDMS

If your team still closes deliveries on paper, start with one flow, such as parts orders or rental drop-offs, and run it electronically for a month. Each module on our pricing page starts at A$59 per month, including Parts, Rental, Service Workshop, Field Service and Customer Portal. A data upload service is A$259 one-off per module, and a training package is A$499 one-off per module. We offer a free trial, and our subscriptions are monthly rolling.

Moderndms

To see how delivery capture fits your business type, look at our software for heavy equipment dealers, rental and hire fleets, forklift fleets or truck and trailer operators.

A checklist before you switch

Use this list to judge any electronic proof of delivery setup, ours included:

Does every delivery generate from an order, work order or contract, with no re-keying?
Can you require a name, signature, photo and serial number before a job closes?
Does it work offline on the device your team already carries?
Can staff record partial, damaged and refused deliveries as exceptions with a next action?
Are records tamper-resistant, searchable by customer, serial and invoice, and retained for your documented period?
Does the completed delivery trigger the invoice, hire start or warranty clock?
Do you own your data and can you export it?
If AI is offered, does it read from the same connected records, and can you limit it to chosen users?

FAQ

What can be used as proof of delivery?

A signed acknowledgment from the receiver, a timestamped photo of the goods at the address, or a secure code confirming collection can all work. Carrier terms such as StarTrack’s list photos, signatures by a person present and locker codes. For high-value equipment, add the serial number, meter reading and the receiver’s name and role.

What is the difference between an electronic delivery docket and electronic proof of delivery?

A docket lists what should be delivered. Electronic proof of delivery is that docket completed at the point of handover, with signature, photos, time, location and any exceptions. In practice one digital document does both jobs, but only the completed version is evidence.

How long should we keep delivery records?

There is no single period for delivery records. For records supporting your tax position, the ATO’s TR 2018/2 generally points to five years after the later of preparation or completion of the transaction. Set a documented period that also reflects your contracts, insurers and carrier claim windows, and confirm it with your accountant.

Are signatures and photos on delivery records personal information?

They can be. Names, signatures and photographs may count as personal information under the Privacy Act, and covered organizations must follow the Australian Privacy Principles. Limit access, photograph goods rather than people where you can, and apply your retention period consistently.

Can AI help with proof of delivery?

Yes, when it works on structured records. AI can help search delivery history, summarize exceptions, flag deliveries closed without required evidence and draft follow-ups for staff to review. It depends on captured data being complete and linked to orders and assets, which is why capture comes first.

Proof of Delivery Capture: A Practical Guide for Dealers