Magellan
Build the handoff from delivered load to invoice-ready
Define document review, charge approval and invoice readiness so delivered loads reach billing with the right evidence and clear exceptions.
The dispatch screen says delivered. Billing opens the load and finds an unreadable proof of delivery, an unresolved accessorial and two versions of the rate confirmation. The truck has finished the movement. The office has not finished the commercial record.
When a TMS uses one status for both events, missing work disappears behind a successful operational milestone. Billing either delays the invoice or sends it with assumptions that become a dispute later. The useful improvement begins by defining what “ready” means for the person receiving the load next.
Define delivered as the confirmed operational event under the company's process. Define invoice-ready as the point at which the required commercial evidence and authorized billing decisions are established. Define invoiced and paid separately, using the actual accounting process.
These are suggested workflow distinctions, not mandatory names for every TMS. The software can use different labels as long as employees understand the transitions and the evidence behind them.
The person receiving the file should be able to see when the load moved, which documents were reviewed, who authorized the invoice and whether payment was reconciled. Keep the source and time for each event where relevant.
Identify the documents and approvals the business needs for each relevant customer or load type. That may include the controlling rate terms, proof of delivery, supporting receipts and approved accessorial records. Do not assume a universal packet when agreements differ.
Give dispatch and drivers clear collection instructions before the documents are needed. A billing checklist discovered after delivery creates rework at the point when the driver and facility are least available to help.
Keep the checklist practical. Each required item should have a purpose and an owner. If nobody can explain why a document is needed, review the requirement with the responsible person rather than allowing an old template to create permanent work. If a requirement is contractual, record the relevant source instead of relying on a colleague's memory.
A file can exist and still be unusable. Confirm that it belongs to the correct load, is legible, contains the relevant pages and supports the required information. A thumbnail icon cannot establish those facts.
The receiving employee should be able to distinguish “uploaded” from “reviewed.” If the system stores both in one box, create an explicit review step appropriate to the workload. Avoid automatically moving a load to invoice-ready merely because any attachment appeared.
Preserve the original document and record corrections transparently. If a driver resends a clearer photograph, retain the relationship between versions. Do not modify a third party's document to create missing information. A clean-looking file is not more useful if its contents no longer represent the source accurately.
An accessorial can be requested, supported, approved, rejected or still disputed. Those states have different billing implications. The person issuing an invoice needs to know which one applies and who may decide the next action.
Establish the business's approved process for partial invoicing, pending charges and later adjustments where relevant. Do not let individual billing clerks invent different financial treatment because the TMS has no obvious status for an unresolved item.
Consider an illustrative customer agreement that permits the undisputed base freight to be invoiced while an accessorial is considered separately. Load 214’s acceptance record could read: “Controlling rate confirmation version 2 checked; complete POD reviewed and legible; base amount matched to those terms; detention request supported but awaiting customer approval; commercial owner authorizes base invoice under the cited term; billing to issue base only; detention follow-up remains assigned.”
The packet records the actual authorizing person, date and source reference in practice. It preserves the verified work and sends the pending charge to its own decision route. Another agreement may require a different treatment; billing follows that agreement rather than an upload-trigger default.
For each delivered load that is not ready to invoice, show what is missing, who will resolve it and what they need to do. Keep document collection, commercial approval and system errors separate so the task reaches the right person.
Sort work by meaningful factors such as age, service impact and the business's priorities. Avoid a queue in which a recently uploaded duplicate pushes a genuinely overdue missing document out of view.
Show the latest factual update. “Awaiting POD” may be correct, but “driver resent at 10:15; billing reviewing legibility” describes a different point in the process. Clear states prevent dispatch from repeatedly contacting a driver after the document has already arrived. They also help a supervisor intervene where a decision is actually stuck.
Topics
- TMS
- Billing workflow
- Proof of delivery
- Load statuses