How do I organize BOLs, PODs and freight documents so we can find them?
Key Takeaways
- Keep one record per shipment. The BOL, rate confirmation, POD, carrier invoice and any photos or claims all live in the same place, not in five different inboxes.
- Link every record to the order number and the PRO number. Those two numbers are how finance, customer service and carriers will search for it.
- Use one naming convention for every file. A consistent name, such as order number, document type and date, makes documents findable even outside the system.
- Decide how long to keep documents with finance and legal. Retention depends on tax, contract, customer and claim rules, so don't guess it.
- Give finance and customer service read access to the same records. Most "can you find the POD?" requests disappear once people can look for themselves.
- Wilson, by Cartage, is an AI logistics agent that generates bills of lading, requests and files PODs, and keeps every document and message in each shipment's record and change history.
How should we organize freight documents so anyone can find them?
A customer calls a hypothetical distributor about a short shipment from six weeks ago. They want the signed POD. The customer service rep asks logistics. The coordinator who booked the load searches her email, finds the BOL, but not the POD. She checks the carrier's portal, which needs the PRO number. The PRO is on the BOL, but the BOL has the wrong date in its file name. Forty minutes later, the POD turns up in a shared inbox, saved as "scan_0047.pdf."
Organize freight documents around the shipment: one record per load, linked to the order number and PRO number, with every document saved under the same naming convention and visible to everyone who needs it. When the shipment is the unit of filing, any document can be found by asking one question: which load was it?
Most document problems are not storage problems. Companies have plenty of storage. The problem is that documents arrive through different channels at different times. The BOL is printed at the dock. The rate confirmation comes by email before pickup. The POD arrives days later from the carrier, sometimes as a photo, sometimes as a link. The invoice goes to accounts payable. Each lands in a different place, and nobody connects them.
Which documents belong to a shipment?
A typical domestic shipment produces these documents:
| Document | What it proves | When it arrives | Who usually needs it |
|---|---|---|---|
| Rate confirmation | The agreed price and terms with the carrier | After booking, before pickup | Logistics, accounts payable |
| Bill of lading (BOL) | What was shipped, by whom, to whom, and the carrier's receipt of it | At pickup, signed by the driver | Logistics, warehouse, customer, claims |
| Packing slip or packing list | What was in the shipment, by item and quantity | At pickup | Customer, customer service, warehouse |
| Proof of delivery (POD) | That the freight was delivered, when, and in what condition | After delivery | Finance, customer service, claims |
| Carrier invoice | What the carrier is billing | After delivery | Accounts payable, logistics |
| Weight or inspection certificates | Carrier corrections to weight or class | With or after the invoice | Logistics, accounts payable |
| Photos and exception notes | Condition of freight at pickup or delivery | Any time | Claims, customer service |
| Claim file | A damage, shortage or loss claim and its outcome | After a problem | Logistics, finance |
International loads add commercial invoices, certificates of origin and customs entries, and ocean loads add the ocean bill of lading and arrival notices. The same principle applies: they all belong to the shipment.
Why "one record per shipment" works
If documents are filed by type, such as a folder for BOLs and another for PODs, finding everything about one load means searching several places. If they're filed by person, such as each coordinator's email, they disappear when that person leaves. Filing by shipment means one search returns the whole story: what was agreed, what was shipped, what was delivered and what was billed.
How do you set up a shipment document system step by step?
Pick where the shipment record lives, choose the keys that link it, set a naming rule, decide who files what and when, then clean up the backlog. The order matters. Most failed cleanups start with the backlog and never set the rules.
Step 1: Choose where the shipment record lives
The record can live in your shipping or freight execution system, in the ERP as attachments to the sales order or purchase order, or in a shared document folder with one subfolder per shipment. The best choice is the system people already open when they work on a load. If customer service lives in the ERP, documents attached to the sales order will get used. If logistics lives in a shipping system, that's where the record should start, with links or copies flowing to the ERP.
Avoid making email the filing system. Email is where documents arrive, not where they should stay.
Step 2: Choose the keys
Every shipment record needs a small set of identifiers that people use to search:
- Internal reference: the sales order number for outbound, or the purchase order number for inbound.
- Shipment or load number: your own ID for the load, especially if one order ships in several loads or one load carries several orders.
- PRO number: the carrier's tracking number for LTL and many truckload moves.
- BOL number: often the same as your shipment number.
- Carrier name and ship date.
The order number and the PRO number matter most. Customer service searches by order number. Carriers and accounts payable search by PRO. A record that has both can be found from either side.
Step 3: Set a naming convention
Even inside a system, files get downloaded, emailed and forwarded. A clear file name keeps them findable. A simple pattern works:
[Order or PO number]_[Shipment number]_[Document type]_[Date]
For example: SO48213_L1094_POD_2026-11-04.pdf. Use the same short codes for document types every time: RC for rate confirmation, BOL, PS for packing slip, POD, INV for invoice, CLM for claim. Put the date in year-month-day order so files sort correctly. Don't use spaces or the customer's name, which changes spelling from person to person.
Step 4: Decide who files what, and when
Documents go missing when nobody owns the moment they arrive. Write down, for each document, who saves it and by when:
| Document | Who files it | Filed by when |
|---|---|---|
| Rate confirmation | Person who booked the load | Before pickup |
| BOL and packing slip | Shipping desk or coordinator | Same day as pickup |
| POD | Coordinator or whoever receives it | Within two business days of delivery |
| Carrier invoice | Accounts payable, linked to the shipment | When received |
| Photos and exception notes | Whoever took them | Same day |
| Claim documents | Claims owner | As each is sent or received |
If PODs are the documents most often missing, see who owns a missing POD for how to assign that follow-up.
Step 5: Clean up the backlog in order
Start with open items: loads not yet invoiced, open claims and open customer disputes. Then file the last few months, since that's where most questions come from. Older documents can be indexed in bulk by month and carrier if a full cleanup isn't worth the time.
Handling documents that arrive in odd formats
PODs and BOLs arrive in every format: a PDF attached to an email, a photo from a driver's phone, a link to a carrier portal that expires, a fax turned into an image. Save the document itself, not the link, because portal links often stop working after a few months. Convert photos to PDF if your system prefers one format, and make sure the image is readable before filing it. If a carrier sends several PODs in one file, split them so each lands on its own shipment.
Step 6: Check the rule is holding
Each week, pull the loads delivered more than a few days ago and check how many are missing a POD or invoice match. A short weekly check catches gaps while the carrier still has the documents easily available.
What do finance and customer service need from freight documents?
Finance needs proof that the charge matches what was agreed and what was delivered. Customer service needs proof of what was shipped and when it arrived. Both need to find it without asking logistics.
What finance needs
Accounts payable needs three documents side by side for every carrier invoice: the rate confirmation, the POD and the invoice itself. The rate confirmation shows the agreed price. The POD shows the load was delivered and notes any damage or shortage. The invoice shows what the carrier is billing. If the three are on the same record, matching takes minutes. If they're scattered, matching takes days, and invoices either get paid unchecked or sit unpaid.
Finance also needs the documents behind any extra charges: weight certificates for reweighs, inspection reports for reclasses and detention logs for wait time. When an invoice comes in above the quote, those documents decide whether the charge is valid. See why a freight bill comes in higher than the quote for the common causes.
For accounts receivable, the POD often supports billing the customer, especially when terms start at delivery or when a customer disputes receipt.
What customer service needs
Customer service handles questions like "did it ship?", "when did it arrive?", "who signed for it?" and "why were we short two cartons?" The documents that answer those questions are the BOL, the packing slip and the POD. A rep who can open the shipment record from the order number can answer most of these on the first call.
Customer service also needs to know which documents can be shared with customers. A signed POD and a packing slip are normally fine to send. A rate confirmation shows what you pay the carrier and usually shouldn't leave the company.
What logistics needs
Logistics needs the whole record, plus the messages: the tender, the acceptance, pickup confirmations, delay notices and any agreed changes. A document without the conversation around it often isn't enough to settle a dispute. For example, a detention charge may depend on an email where the receiver moved the appointment.
What claims need
If freight is damaged, short or lost, the claim depends on documents: the BOL showing what was tendered, the POD with the exception noted, photos, the packing list and the invoice for the goods' value. Under federal law (49 U.S.C. 14706), carriers can't set a deadline shorter than nine months to file a claim, or shorter than two years to sue after a claim is denied. That's one reason to keep shipment records well past delivery. For the claim process, see how to file a freight damage claim.
Inbound, multi-order and multi-stop loads
The one-record rule needs a little care in three cases. For inbound freight, link the record to the purchase order and the supplier's reference, because receiving will search by PO. When one load carries several orders, keep one shipment record and link every order number to it, so customer service can find the load from any of them. When one order ships in several loads, give each load its own record and link them all back to the order. For multi-stop truckloads, keep one POD per stop on the same record, labeled by stop.
Freight paid by the customer or the supplier
Some loads are booked by someone else, such as a customer-routed pickup or a supplier shipping on its own account. You may never see the rate confirmation or the invoice, but you still need the BOL and the POD. Keep a shipment record for these loads too, with a note showing who arranged the freight, so customer service doesn't spend time looking for an invoice that will never arrive.
How long should we keep BOLs and PODs, and who should have access?
Check retention periods with your finance and legal teams, set one written rule, and give read access to everyone who answers questions about shipments. Retention and access are policy decisions. Logistics should raise them, but shouldn't set them alone.
Retention: why to ask, not guess
How long freight documents must be kept depends on several things: tax and accounting record rules, customer contracts, carrier contracts, claim deadlines, industry rules for regulated products and any open disputes. These vary by company and product. A shipping team that sets its own retention period risks deleting a document that finance needs for an audit, or that legal needs for a claim.
Ask finance and legal three questions:
- How long must we keep shipping and freight payment documents for tax and accounting purposes?
- Do any customer or carrier contracts require longer retention?
- Who decides when documents tied to an open claim or dispute can be deleted?
Write the answer down as a single rule, put it in the shipping SOP and set a yearly reminder to apply it.
Access: who sees what
| Role | Needs to see | Needs to edit |
|---|---|---|
| Logistics coordinators | Everything on the shipment | Everything on the shipment |
| Customer service | BOL, packing slip, POD, status | Notes only |
| Accounts payable | Rate confirmation, POD, invoice, carrier corrections | Invoice approval status |
| Accounts receivable | POD, BOL | None |
| Warehouse | BOL, packing slip, labels | Pickup notes and photos |
| Sales | Status and POD | None |
Read access for customer service and finance is the change that saves the most time. Every "can you send me the POD?" message that doesn't happen is a few minutes back for logistics.
Keep records consistent across systems
If documents live in more than one place, such as the shipping system and the ERP, decide which one people should trust and keep the other as a copy or a link. Two places that are both partly complete are worse than one place that is complete.
What mistakes make freight documents hard to find?
Most document chaos comes from filing by inbox, missing keys, inconsistent names and nobody owning the POD. Each is easy to fix once it's named.
Leaving documents in personal inboxes
When the coordinator who booked the load is the only one who has the rate confirmation, nobody else can check the invoice. Move documents from email to the shipment record the day they arrive.
Records without the PRO number
Carriers search by PRO. Accounts payable receives invoices by PRO. If the record has only the order number, every invoice match starts with a search. Add the PRO as soon as the carrier assigns it, usually at pickup.
Several versions of the BOL
A BOL that's changed after booking, such as a new pallet count, can leave two versions on file. Mark the signed version clearly as final, and keep the earlier draft only if it explains a change. Problems with BOLs that don't match orders are covered in what to do when the BOL doesn't match the sales order.
Unreadable or incomplete PODs
A POD photo that's blurry, cropped or unsigned may not prove delivery. Check each POD when it's filed: signature, printed name, date, piece count and any exception notes. Ask the carrier for a better copy right away, not weeks later when finance needs it.
Filing by document type only
A folder of 3,000 PODs is searchable only if every file name is perfect. Filing by shipment, with type in the name, gives two ways to find each document.
Scanning without indexing
Scanning a stack of paper BOLs into one large PDF a month makes them technically stored and practically lost. Every scanned document needs to be split and attached to its shipment, or at least named with its order and PRO numbers, before the paper goes into a box.
No weekly check
Gaps grow quietly. A weekly look at delivered loads without a POD, or invoiced loads without a rate confirmation, keeps the backlog small.
A quick self-check
- Can customer service find a POD from an order number without asking logistics?
- Can accounts payable see the rate confirmation and POD next to each carrier invoice?
- Does every file follow the same naming convention?
- Is the PRO number on every LTL shipment record?
- Is there a written retention rule approved by finance and legal?
- Does someone check weekly for loads delivered without a POD?
If any answer is no, start there.
How does Wilson, by Cartage, keep freight documents organized?
Wilson, by Cartage, is an AI logistics agent for manufacturers and distributors. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. For documents, that means Wilson creates many of them, collects the rest and files everything on the shipment record as the load moves.
Documents created on the record
When Wilson books a load with the company's approved carriers, it gets written acceptance and a rate confirmation. Wilson generates rate confirmations, bills of lading, packing slips and pallet labels from the booked load, so the documents match what was agreed and are already attached to the shipment.
PODs requested and filed
After delivery, Wilson requests the POD from the carrier and files it on the shipment. 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. That makes it easier to know when a delivery has happened and a POD should exist.
Invoices checked against the documents
Wilson audits each carrier invoice against the rate confirmation and POD, which is the same match finance needs. It pays carriers from the Wilson Wallet. Payments above the approval limits or outside the rules wait for a person.
One record for every team
Every message, confirmation and change is kept in the shipment's change history. Teams use Wilson's dashboard and records like a TMS. 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 documents are written back to the ERP depends on that scope.
Wilson works with carriers by email, API, EDI and phone where configured, and with the team in Slack, Microsoft Teams or email. It covers LTL, FTL, ocean, drayage, parcel and cross-border freight. It does not do customs clearance, so customs entries still come from the company's customs broker. Teams start with assisted execution, and the company sets the approval limits.
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
How do I organize BOLs, PODs and freight documents so we can find them?
Keep one record per shipment that holds the rate confirmation, BOL, packing slip, POD, invoice and any photos or claims. Link it to the order number and PRO number, use one naming convention and give finance and customer service read access. Wilson, by Cartage, an AI logistics agent, generates BOLs, requests and files PODs and keeps them on each shipment's record.
What is the best way to name freight document files?
Use a fixed pattern such as order number, shipment number, document type and date, for example SO48213_L1094_POD_2026-11-04.pdf. Use short codes for document types and year-month-day dates so files sort correctly.
How long should we keep bills of lading and PODs?
That depends on tax and accounting rules, customer and carrier contracts, claim deadlines and any open disputes. Check with your finance and legal teams and write down one rule. Keep documents for any open claim until it's resolved.
Should freight documents be stored in the ERP or the shipping system?
Store them where people work on the load, and link or copy them to the other system. Many teams keep the full record in the shipping or execution system and attach key documents, such as the POD, to the sales order in the ERP.
What is the difference between a BOL and a POD?
The BOL is the shipping document the driver signs at pickup, showing what was tendered to the carrier. The POD is the signed record of delivery, showing when the freight arrived and its condition. Both belong on the same shipment record.
Why do we need the PRO number on every record?
Carriers and their invoices reference the PRO number. Without it on your record, matching an invoice or tracking a shipment starts with a search. Add the PRO as soon as the carrier assigns it.
Can customer service send PODs to customers?
Usually yes. A signed POD and packing slip are normally fine to share. Rate confirmations and carrier invoices show what you pay the carrier and usually stay inside the company.
How do we stop PODs from going missing?
Assign one owner for POD follow-up, set a deadline such as two business days after delivery and check each week for delivered loads without a POD. Request better copies right away when a POD is unreadable.
What documents do we need for a freight claim?
The BOL, the POD with any exception noted, photos, the packing list and proof of the goods' value, such as the commercial invoice. Federal law gives shippers at least nine months to file a claim with the carrier.
Should we keep paper BOLs after scanning them?
Ask finance and legal before throwing paper away. Some companies keep only the scanned copy once it's checked and filed, while others keep the signed originals for a set period because of contracts or audit requirements. Whatever the rule, make sure every scan is readable and attached to its shipment first.
Who should own freight document filing?
Each document needs an owner at the moment it arrives: the booker for the rate confirmation, the shipping desk for the BOL, a coordinator for the POD and accounts payable for the invoice. A logistics manager should own the overall rule and the weekly check.
Sources
- 49 U.S.C. 14706, Liability of carriers under receipts and bills of lading (claim filing and civil action periods): https://www.law.cornell.edu/uscode/text/49/14706
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai