The customer won't pay until we send the POD. How do we get it faster?

Bills of lading guideNov 17, 202617 min read

The customer won't pay until we send the POD. How do we get it faster?

It is the 28th of the month. The controller is looking at receivables. A distributor has 14 customer invoices past their due date, and the customers on 9 of them have said the same thing: "Send us the signed POD and we'll pay." The freight delivered weeks ago. The logistics coordinator has asked some carriers for PODs, but not all, and two carriers sent documents that are hard to read. Finance did not know any of this until the customers replied.

To get PODs faster, request them from the carrier on the day the freight delivers, follow up on a set timeline, check that each POD has what the customer needs and attach it to the customer invoice as soon as it arrives. Most PODs are slow because nobody asks until a customer refuses to pay, and by then the carrier has to dig through old paperwork.

When customers require a POD before paying, the POD is part of the invoice. A missing POD means the invoice is incomplete, and the company is lending the customer money for free until the document shows up.

Why customers ask for the POD

Customers ask for proof of delivery for good reasons. Their accounts payable team may not be allowed to pay a supplier invoice until the receiving team confirms the goods arrived. Some customers match three documents before paying: their purchase order, the receiving record and the supplier invoice. When their receiving record is unclear, the signed POD fills the gap. Large retailers and distributors often write the requirement into their vendor terms.

Whatever the reason, the requirement is not going away. The company can either fight it customer by customer, or build a process that delivers the POD before the customer has to ask.

What the delay costs

The cost has three parts:

  • Cash tied up. Every day an invoice waits is a day the company is funding the customer's inventory.
  • Team time. Finance chases sales, sales chases logistics, logistics chases the carrier. The same POD gets asked for four times.
  • Weaker disputes. If the customer later claims a shortage or damage, a POD found weeks later is harder to use than one filed the day after delivery.

A hypothetical example

Consider a hypothetical distributor that ships 200 loads a month, with a third of them going to customers that require a POD before paying. If PODs take an average of ten days to reach those customers after delivery, and a better process cuts that to three, each of those invoices gets paid about a week sooner. The exact value depends on invoice size and the cost of money, but the effect on cash is often larger than the effort to fix the process.

Who should own the POD

In most companies, logistics owns getting the POD from the carrier, and finance owns sending it to the customer with the invoice. The handoff between them is where many PODs get stuck. Decide who does each step and write it down.

Let's review your open invoices that are waiting on a POD. You don't need to prepare anything: Cartage maps the workflow with you on the call.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.

Book a demo →

How do you get PODs from carriers faster?

Start the request the day the freight delivers, ask in the way each carrier answers fastest, and follow up on a fixed schedule. Speed comes from starting early and never letting a request sit.

Step 1: Know when the load delivered

The POD request should be triggered by delivery, not by a customer's complaint. Check tracking on every load due to deliver each day. When the carrier marks a load delivered, it is time to request the POD.

Step 2: Use the fastest source for each carrier

Carriers make PODs available in different ways:

  • The carrier's website or document portal, often searchable by PRO number. Many LTL carriers post delivery receipts there within a day or two.
  • An API or EDI document feed, where the company has one set up.
  • Email to the carrier's billing or customer service team.
  • The driver or dispatcher, who may be able to send a photo of the signed delivery receipt the same day.

Write down the fastest source for each main carrier. For a carrier whose portal posts PODs within a day, check the portal first. For a small truckload carrier, ask dispatch for a photo from the driver at delivery.

Step 3: Ask for the POD with the right reference

Make the request easy to answer. Include the PRO number, the BOL number, the pickup date, the consignee and the order or PO number. A request that only says "please send the POD for our load to Phoenix" will wait while someone at the carrier searches.

Step 4: Follow up on a fixed timeline

A simple timeline works for most freight:

Day after delivery Action
Day 0 Delivery confirmed; request POD from the carrier's fastest source
Day 1 Check portal or inbox; if no POD, send a follow-up in the same thread
Day 2 Call the carrier's billing or customer service line
Day 3 to 5 Escalate to the carrier's account contact; tell finance the POD is late
After day 5 Ask the consignee for their signed receiving copy as a backup

Adjust the days for each carrier and mode. The guide on when to chase a missing POD goes deeper into timelines and what to do when a POD never arrives.

Step 5: Check the POD before filing it

When the POD arrives, check it before saving it. A POD that is unreadable, unsigned or for the wrong load is not a POD the customer will accept. The next section covers what to check.

Step 6: File it on the load and send it on

Save the POD on the shipment record, linked to the order and the invoice. Then send it to finance or straight to the customer, depending on who sends invoices. Do not leave it in an inbox attachment.

Prevent POD problems at the BOL

Many POD problems start before pickup. The delivery receipt the driver gets signed is usually based on the BOL, so whatever is missing from the BOL is often missing from the POD. Put the customer's PO number and the company's order number on every BOL. Write the piece count clearly, and use the same units the invoice will use: if the invoice says 12 cartons, the BOL should not say 2 pallets with no carton count. When the reference and count are on the BOL, they are far more likely to appear on the signed POD, and the customer can match it without asking.

What should a POD show before you send it to the customer?

A usable POD shows who received the freight, when, how much and for which order, with any exceptions noted. If any of these are missing, the customer's accounts payable team may reject it, and the clock starts again.

The minimum a customer usually needs

  • A signature from someone at the receiving location.
  • A printed name next to the signature, so the customer can tell who signed.
  • The delivery date, and often the time.
  • A reference the customer recognizes: their PO number, the company's order number or the BOL number.
  • The count received: pallets, cartons or pieces, matching the shipment.
  • Exception notes, if any: "2 cartons damaged," "1 pallet short," "subject to count."

Some customers have extra requirements, such as a receiving stamp or a specific document format. Write these down per customer.

Common POD problems

Problem Why it slows payment What to do
Unreadable scan Customer cannot confirm the signature or count Ask the carrier for a clearer copy or the original image
No signature Customer may not accept it as proof Ask the carrier for the signed copy; see the note below
No order or PO number Customer cannot match it to the invoice Match it by PRO and BOL, then send it with a cover note naming the PO
Wrong load Customer rejects it or, worse, accepts the wrong one Request the right POD; correct the record
Exceptions noted Customer may short-pay or open a dispute Tell sales and finance; check whether a claim is needed
Count differs from the invoice Customer pays only for what the POD shows Check the BOL and packing list; open a claim if freight was lost

When a POD arrives without a signature, the guide on whether a load is complete when the POD has no signature covers what to accept and what to send back. When the POD has no order number, the guide on matching a signed POD that has no order number shows how to tie it to the right order.

Exceptions change the invoice conversation

A POD with "1 pallet short" or "damaged" on it is not just proof of delivery. It is a warning that the customer may pay less than the invoice. When the POD shows an exception, tell finance and sales right away, check the BOL and packing list, and decide whether to open a freight claim with the carrier. Waiting until the customer short-pays makes the claim harder.

What slows POD collection, and how do you fix it?

Most slow PODs come from five habits: starting late, asking the wrong way, losing the POD in an inbox, sending it to the customer late and never measuring the delay. Each has a simple fix.

Mistake 1: Waiting for the customer to ask

If the first POD request goes out when the customer refuses to pay, the company has already lost the time between delivery and that email, often weeks. Start on delivery.

Mistake 2: Asking every carrier the same way

A carrier that posts PODs on its website within a day does not need an email. A carrier that answers only by phone will not answer the email. Keep the fastest source per carrier on the contact list.

Mistake 3: Losing the POD after it arrives

PODs that arrive as email attachments often stay in one coordinator's inbox. Finance never sees them, and the customer keeps waiting. File every POD on the load as soon as it arrives.

Mistake 4: Splitting the job between logistics and finance with no handoff

Logistics gets the POD and assumes finance will send it. Finance waits for logistics to tell them. Write the handoff down: "Logistics files the POD on the load and tells finance the same day. Finance sends it with the invoice or to the customer's AP contact within one business day."

Mistake 5: Sending the invoice before the POD is ready

For customers that require a POD, an invoice sent without it often goes straight to a hold queue. Some companies send the invoice and POD together. Others send the invoice on shipment and the POD as soon as it arrives. Either can work, but the customer's AP team should get both without having to ask.

Mistake 6: Never measuring the delay

If nobody counts how long PODs take, the delay stays invisible. Track two numbers: days from delivery to POD received, and days from POD received to sent to the customer. The first shows carrier and follow-up problems. The second shows internal handoff problems.

Talk to the customer's accounts payable team

Many POD delays end with one short conversation. Ask each customer that requires PODs three things: where the POD should be sent, what it must show and whether the invoice and POD should arrive together or separately. Some AP teams want both in one email with the invoice number in the subject line. Some want the POD sent to receiving, not to AP. Some accept a delivery scan for small orders and require a signed POD only above a set amount. Write the answers on the customer record so everyone sends PODs the same way.

The same conversation is a good time to ask how long the customer's AP team takes to release payment once it has a complete invoice and POD. That number tells finance what the POD delay is actually costing, and which customers to prioritize in the weekly review.

When to send the invoice without waiting

For customers that do not require a POD, send the invoice on shipment as usual. Holding every invoice until the POD arrives slows cash for no reason. Keep the POD rule for the customers who ask for it, and keep that list current.

Which carriers and customers need special rules

Some carriers are always slow with PODs. Some customers always require them before paying. Put both on a short list. For slow carriers, start follow-ups earlier. For strict customers, check the POD more carefully and send it the same day it arrives.

Which POD checklist should logistics and finance agree on?

Logistics and finance should agree on one checklist so every POD moves from carrier to customer without waiting in between.

The POD-to-payment checklist

Item Question to answer Owner
Trigger Is the POD requested the day the load delivers? Logistics
Carrier source Do we know the fastest POD source for each carrier? Logistics
Request details Does each request include PRO, BOL, date, consignee and order number? Logistics
Follow-up timeline What happens on day 1, 2, 3 and 5 after delivery? Logistics
Quality check Is each POD checked for signature, name, date, count and reference? Logistics
Customer requirements Which customers need extra items, such as a stamp or a format? Sales and finance
Filing Is the POD saved on the load, linked to the order and invoice? Logistics
Handoff How does finance learn the POD is ready? Both
Sending Who sends the POD to the customer, and how fast? Finance
Exceptions Who is told when a POD shows damage or shortage? Logistics
Measures Are days to POD and days to send tracked each month? Both
Backup source When do we ask the consignee for their receiving copy? Logistics

A weekly POD review

Once a week, pull every delivered load without a POD on file and every POD on file that has not been sent to the customer. Sort by invoice amount and age. The top of that list is where cash is waiting. This review takes 15 minutes and often finds PODs that arrived days ago and were never forwarded.

What good looks like

For most LTL and truckload freight, a company with a working process gets the POD within a few days of delivery and sends it to strict customers the same day it arrives. The exact numbers depend on carriers and modes, so set your own baseline in the first month and improve from there.

How the POD helps beyond payment

A POD filed on time does more than speed up one payment. It supports the carrier invoice audit, because the delivery date and count can be checked against what the carrier billed. It supports freight claims, because exceptions are caught while the evidence is fresh. And it answers the customer service question "did it arrive?" without a call to the carrier.

How does Wilson, by Cartage, get PODs faster?

Wilson, by Cartage, is an AI logistics agent that requests and files PODs as each load delivers, follows up with carriers until it gets them and keeps each POD on the shipment record with the order, the BOL and the invoice. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Wilson works as a free logistics department, built on four parts.

The labor. Wilson does the labor from the first quote to the final POD. It tracks each load with the best source available: carrier API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, and email or phone calls when nothing else is current. When a load delivers, it requests the POD and follows up with the carrier persistently, by phone and email, with persistence rules per carrier, until it gets an answer. It can also request, chase, file and attach other documents configured in the workflow. Customers and consignees can be reached by email or SMS where configured. Wilson does not upload documents to customer portals.

The data. Wilson keeps the data on record as it works: every order, load, document and contact. The POD sits on the same shipment as the order, the BOL, the rate confirmation and the carrier invoice, so finance does not have to search an inbox to find it. Wilson replaces the TMS for freight execution and connects to the company's ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope. Whether the POD and delivery status are written back to the ERP depends on scope.

The network. Wilson gives access to the network: the shipper's volume counts with every other Wilson customer's, which helps get better rates on every lane. The network includes carriers and brokers. The company still approves who hauls its freight.

The payments. Wilson handles the payments on the carrier side. It audits each carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules are held and flagged for a person. When a POD shows damage or shortage, Wilson can handle the freight claim: it asks the receiver for photos and to set the product aside, opens the claim with the carrier and tells the team what it did.

Control stays with the company. Wilson starts with assisted execution, the company sets the approval limits and routine actions run automatically within those rules as the workflow is proven. Every message, confirmation and change is kept in the shipment's change history.

Pricing

Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.

FAQs

Can Wilson get PODs to us faster so customers pay sooner?

Wilson, by Cartage, an AI logistics agent, requests the POD when each load delivers and follows up with the carrier by phone and email until it gets it. It files the POD on the shipment record next to the order and invoice, so finance can send it without searching. How the POD reaches the customer or the ERP depends on the workflow and scope.

Why do customers require a POD before paying?

Their accounts payable team often needs proof the goods arrived before paying a supplier invoice. Some match the PO, the receiving record and the invoice, and use the POD when the receiving record is unclear. Many put the requirement in their vendor terms.

When should we request the POD from the carrier?

On the day the load delivers. Waiting until a customer asks adds days or weeks. A fixed follow-up timeline after that keeps requests from sitting.

What should a POD show?

A signature, a printed name, the delivery date, a reference the customer recognizes such as the PO or order number, the count received and any exceptions. Some customers need extra items, such as a receiving stamp.

What if the carrier never sends the POD?

Escalate to the carrier's account contact after a few days, and ask the consignee for its signed receiving copy as a backup. Keep the delivery scan and tracking record on the load in case the customer accepts other proof.

What if the POD shows damage or a shortage?

Tell finance and sales right away, because the customer may pay less than the invoice. Check the BOL and packing list and decide whether to open a freight claim with the carrier. Wilson can handle the claim steps the company defines during onboarding.

Does Wilson upload PODs to customer portals?

No. Wilson can request, chase, file and attach documents configured in the workflow, and reach customers by email or SMS where configured. It does not upload documents to customer portals.

How do we measure POD speed?

Track days from delivery to POD received and days from POD received to sent to the customer. The first shows carrier and follow-up problems. The second shows handoff problems between logistics and finance.

Does Wilson use the POD when checking carrier invoices?

Yes. Wilson audits each carrier invoice against the rate confirmation and the POD before paying from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person.

Sources

Let's review your open invoices that are waiting on a POD. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google