# From proof of delivery to invoice

The POD-to-invoice workflow starts when a delivery is reported complete and ends when the carrier has checked the evidence and approved an invoice for issue. The biggest risk is treating a status update as proof that every financial detail is ready.

## Billing-ready checklist

1. Match the proof of delivery to the correct load and customer reference.
2. Check delivery date, signature or receipt details, and any noted shortage or damage.
3. Compare the invoice basis with the approved rate confirmation and revisions.
4. Verify each accessorial and its supporting approval or document.
5. Resolve missing or conflicting items with a named owner before issue.
6. Record the final invoice number and the system that owns it.

For example, a signed POD might arrive but show an exception for a damaged pallet. The billing queue should surface that note beside the rate and customer instructions; it should not quietly issue a standard invoice. The operations team may need to resolve the discrepancy before finance proceeds.

## Measure the handoff

Track time from delivery to complete document packet, time from packet to approved invoice, and the share of invoices reopened for correction. These are internal process metrics, not universal performance targets. Keep customer-specific requirements visible rather than relying on a single generic template.

RunaboutX's [AI Billing](/features/ai-billing/) and [document automation](/features/document-automation/) aim to make this work reviewable. Confirm current accounting export and approval behavior during a demo. The [driver settlement workflow](/resources/learn/driver-settlement-workflow/) covers the parallel pay handoff.

---

Canonical: https://www.runaboutx.com/resources/learn/pod-to-invoice/
Last reviewed: 2026-10-14