# Proof-of-delivery to invoice automation for Singapore logistics SMEs

> Link proof of delivery to a billing-ready job. Hold partial and disputed quantities, protect recipient evidence, and hand only the approved lines to accounting.

Source: https://www.fyadvisers.com/blog/proof-of-delivery-to-invoice-automation/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

A stop marked complete is not yet ready to invoice. A missing signature, a short quantity or a failed attempt changes what the office may bill. The workflow’s job is to attach evidence to the job reference and to hold the lines a person has not accepted.

Choosing a transport system is a different decision. The [logistics software](/industries/logistics/) page covers booking, dispatch and the products teams already use. This page is only the evidence-to-bill handoff. Customer invoices you issue still need an approval path of their own if a person must check them; supplier bills you receive are the [invoice approval](/blog/invoice-approval-workflow-automation-singapore/) problem, not this one.

## One job id across dispatch, proof and billing

Pick an identifier that dispatch, the driver app and the invoice line can all store. Do not rely on the driver’s name and a date.

| Status | Meaning for billing |
|---|---|
| Attempted | No bill for a successful delivery. A waiting-time rule applies only if the rate card says so |
| Partial | Bill only the accepted quantity. Hold the rest |
| Delivered | Required evidence is on the job. Quantity matches |
| Disputed | A named person owns the dispute. Nothing in dispute is billing-ready |
| Billing-ready | The lines and surcharges a person, or a rule they wrote, has accepted |

If warehouse and transport use different references, reconciling them by hand is the integration work. [System integration](/services/system-integration/) should carry one reference through, not invent a third.

## What to collect, and no more

Capture the delivery reference, the time, the confirmation you agreed with the customer, and the evidence the contract actually requires. A photo of a doorway can show a person, a vehicle registration or a residential address. The PDPC’s [Key Concepts guidelines](https://www.pdpc.gov.sg/-/media/Files/PDPC/PDF-Files/Advisory-Guidelines/AG-on-Key-Concepts/Advisory-Guidelines-on-Key-Concepts-in-the-PDPA-17-May-2022.pdf) expect reasonable security arrangements for personal data, and they limit retention to what a purpose, a law or the business still needs. Write the purpose (“proof this job was delivered”) on the design, restrict access to that job, and do not put the file on an open link in a tracking page unless the customer relationship requires that exact file and you have thought through who can forward it.

Business contact information is not a blanket exemption when the photo or the signature identifies a private individual.

## From evidence to invoice lines

Check that required evidence is present. Reconcile quantity delivered to quantity ordered. Draft invoice lines from the rate card that applies to that customer and that job type. Waiting time, extra drops and after-hours charges come from that card or from an exception a named person approves. A free-text note from the driver is not a price.

Do not create an invoice per photo. Photos attach to the job. The job, once billing-ready, creates or updates one draft.

## Offline, duplicates and late evidence

Drivers lose signal. The app should queue a single submission keyed by the stop. When it syncs, it updates that job. A second upload of the same proof is a duplicate event, not a second delivery. The acceptance test is the same photo sent twice.

If evidence arrives after a draft invoice exists, the draft updates or a person is asked to revise it. The workflow must not issue a second invoice for the same job id. If the accounting write succeeds and the acknowledgement is lost, replay looks up the job id first. Microsoft’s [error-handling guidance](https://learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/error-handling) is about branches and retries. It does not make a connector idempotent. You still need the business key.

Where the invoice supports GST, IRAS requires the underlying records to be kept for at least five years from the end of the accounting period. The delivery evidence that supports that invoice needs a retrievable home for that purpose. Debug copies and failed uploads do not automatically inherit the same period. See [retention](/blog/workflow-automation-data-retention-audit-logs/).

## Buy, connect, or build the missing step

Many transport products already capture proof of delivery. Commission a custom handoff only where you have checked that the product cannot emit a billing-ready event with the job id, the quantities and the evidence link. Replacing a working dispatch tool to obtain a status email is the expensive version of this project.

## Tests

1. The same proof is uploaded twice. One job, one draft.
2. Evidence arrives after the draft exists. No second invoice.
3. A user on another customer’s account cannot open the photo.

Illustrative scenario, not a client engagement: a carrier completes only part of a delivery. The driver uploads the proof offline. The later sync updates the same job. Billing stays on hold for the disputed quantity. The office approves the billable portion against the rate card. The short quantity remains a dispute, not a silent write-off and not a second invoice.

This is an operational design guide, not transport-contract or tax advice, and FYAdvisers is not a law firm. To follow one job through to the draft invoice, use the contact form or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### Which event should make a job billing-ready?

The event you define: required evidence present, delivered quantity reconciled to the order, and any surcharge either on the rate card or approved as an exception. “Driver tapped complete” is an earlier status.

### What should happen when the driver is offline?

The device keeps one submission for that stop and syncs it to the same job id. A later sync updates the job. It does not create a second job or a second invoice because the photo uploaded twice.

### Who can open another customer’s delivery photo?

Nobody who does not need that job. Test with a user from a different customer account. Signature and photo files are restricted to the job. They are not placed on a public link.

### Should we replace the transport system to get this?

Not if it already receipts delivery and can emit a job event. The gap is often the handoff into billing. See the logistics software page before commissioning a second dispatch tool.
