Finance needs to know which loads delivered by month end. How do we give them that list?
Short answer
Give finance one list of loads delivered by month end that have no carrier invoice yet. Use the signed POD as proof of delivery, not the carrier's status alone. Add the agreed rate from the rate confirmation and any confirmed extra charges. Mark loads that delivered without a POD. Wilson, by Cartage, an AI logistics agent, keeps these loads, PODs and rates on one record your team can search and export.
Book 15 minutes with the team →How do you give finance a list of loads delivered by month end?
It is the second business day of the month. The controller sends logistics a message: "We need every freight load delivered in October that we haven't been billed for, with an estimated cost, by noon tomorrow." The logistics coordinator opens a spreadsheet, the ERP, three carrier websites and two inboxes. By the end of the day she has a list of 64 loads. Eleven have no POD on file. For nine, she is not sure of the rate, because the quote was in an email thread with three versions. Finance gets the list a day late and adds a note: "Estimates may be incomplete."
To give finance a month-end list of delivered loads, pull every load from one shipment record with its delivery date, POD status, carrier invoice status and agreed rate, filter to loads delivered on or before the cutoff that the carrier has not invoiced, and flag the loads delivered without a POD. Then send the list in the format finance already uses, with the expected cost from the rate confirmation, so finance can record the cost in the right month.
The hard part is not the filter. It is having the data in one place. Delivery dates come from carriers. PODs come by email, from carrier websites or from drivers. Invoices go to accounts payable. Rates sit on rate confirmations. If those four pieces live in four places, the month-end list is a manual project every month.
Why finance asks
Under accrual accounting, a cost generally belongs to the month when the service happened, not the month when the bill arrived. Carrier invoices often arrive days or weeks after delivery. Without a list of delivered, uninvoiced loads, freight cost lands in the wrong month and the monthly numbers swing for reasons that have nothing to do with freight. Each company's accounting policy sets the exact rule; logistics provides the facts that policy needs.
What finance actually wants
Finance usually does not want shipment details. It wants a defensible number and the list behind it. That means:
- Which loads were delivered by the cutoff.
- Which of those have not been invoiced yet.
- The expected cost of each, and where that number came from.
- Which loads are uncertain, and why.
Where to start
Let's review what finance asks logistics for at month end. 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.15 minutes with the team behind Wilson. No prep needed.
Book 15 minutes →What should the month-end delivered-loads list contain?
The list should have one row per load, with the fields finance needs to accrue the cost and the fields logistics needs to defend it. Keep it short enough to read and complete enough to check.
The core fields
| Field | Why finance needs it | Where it comes from |
|---|---|---|
| Load or shipment ID | To tie the row to the ERP order and later to the invoice | Shipment record |
| ERP order or PO number | To match cost to the sale or the cost center | Order |
| Carrier | To match the future invoice | Rate confirmation |
| Pickup date | Context for long transits | Carrier confirmation |
| Delivery date | Decides which month the cost belongs to | POD or carrier status |
| POD on file | Proof the service was performed | Filed POD |
| Agreed rate | Base for the accrual | Rate confirmation |
| Known accessorials | Detention, lumper or liftgate already confirmed | Load record, carrier messages |
| Expected total | The amount to accrue | Rate plus known accessorials |
| Invoice status | Not received, received not approved, approved, paid | Accounts payable |
| Cost center or plant | To book the cost in the right place | Order or ERP |
| Note | Anything uncertain | Logistics |
The four states
Every load that shipped in the month falls into one of four states at the cutoff:
- Delivered, invoiced. The cost is already in the books, or in the approval queue. Finance usually does not need to accrue it again, but the list should show it so totals reconcile.
- Delivered, not invoiced, POD on file. The clearest accrual case. The service happened and is proven.
- Delivered, not invoiced, no POD. The carrier says delivered, but the proof is missing. Finance still may need to accrue it, but logistics should chase the POD and mark the row.
- Not delivered by the cutoff. In transit, or picked up late. These usually belong to the next month, but the shipping terms and the company's policy decide.
Expected cost, not a guess
The expected cost should come from the rate confirmation. If the team only has a quote in an email, use it and mark the row. If the load picked up accessorials during the trip, add the ones that are confirmed in writing. Leave out charges that are only possible. If a carrier mentioned detention but has not billed it, put it in the note so finance can decide.
A hypothetical example
Consider a hypothetical plant with 210 loads delivered in October. At the cutoff:
- 140 are invoiced.
- 52 are delivered with a POD, not invoiced. Expected total from rate confirmations: $118,400.
- 11 are delivered without a POD. Carrier status says delivered. Expected total: $24,900.
- 7 are still in transit on November 1.
Finance accrues the 52, decides on the 11 under its policy and leaves the 7 for November. Logistics chases the 11 PODs first thing in the new month.
Loads that need special handling
Some loads do not fit the simple rule, and the list should show them clearly:
- Multi-stop truckloads. A load with three drops may deliver the first stop on the 30th and the last on the 2nd. Agree whether the delivery date is the last stop or each stop, and write the rule down.
- Split shipments. One ERP order may ship on two carriers or two days. Each shipment is its own row, with its own POD and invoice, tied back to the same order.
- LTL with terminal transfers. The carrier's status may show delivered at a terminal for a will-call pickup. That is not delivery to the customer unless the terms say so.
- Ocean and drayage. An ocean leg, a port pickup and a final dray may be billed by different parties at different times. List each leg as its own cost line, with its own proof.
- Cancelled loads with a charge. A truck ordered and not used can still cost money. If the carrier confirmed a TONU in writing, it belongs on the list.
- Collect shipments. If the customer pays the carrier, there may be no carrier cost for the shipper at all. Mark these loads so they are not accrued by mistake.
What the controller should be able to answer from the list
A good list lets the controller answer the usual month-end questions without calling logistics:
- How much freight cost belongs to this month but has not been billed?
- How much of that is backed by a POD?
- Which carriers are slow to invoice, and by how much?
- Which loads carry extra charges that were confirmed during the trip?
- Which loads are uncertain, and when will they be resolved?
If the controller still has to call logistics for these answers, a column is missing.
How do you build the list each month without a scramble?
Build the list from data the team already collects on every load, and keep the month-end step to a filter and a check. The scramble happens when delivery dates, PODs, rates and invoice status are collected only at month end.
Step 1: Capture the delivery date on every load
Each load should get a delivery date on the shipment record when it delivers. The carrier's status gives a first date. The POD confirms it. If the two disagree, the POD date should win, and the difference is worth a note. See what to do when the carrier POD and the ERP delivery status don't match for that check.
Step 2: Request the POD at delivery, not at month end
PODs are easiest to get the day the load delivers. A week later, the driver has moved on and the carrier's back office is slower to answer. A request on delivery day keeps the month-end list clean. The guide on when to chase a missing POD explains timing and escalation.
Step 3: Keep the agreed rate on the load
The rate confirmation should be attached to the shipment. If the rate changed after booking, the new confirmation replaces the old one, and the change should be visible. At month end, the expected cost is then a lookup, not a search through email.
Step 4: Track invoice status in the same place
Accounts payable knows which invoices arrived. Logistics knows which loads delivered. If the two lists are separate, someone has to match them by hand. When invoice status sits on the same shipment record, the delivered-not-invoiced filter is one step.
Step 5: Note confirmed extra charges as they happen
When a carrier confirms detention, a lumper fee or a redelivery during the trip, write it on the load the same day, with the carrier's message attached. At month end, these confirmed charges go straight into the expected cost. Without that habit, the team has to remember which loads had trouble weeks ago, and the accrual comes out too low. The same note helps when the invoice arrives, because the charge can be checked against what was confirmed.
Step 6: Run the list at the cutoff
At the agreed time, filter the loads:
- Delivered on or before the cutoff date.
- Invoice status: not received or not approved.
Sort by state: POD on file first, no POD second.
Step 7: Review the exceptions
A short review catches most errors:
- Loads with no rate confirmation.
- Loads with a delivery date but no pickup date.
- Loads delivered without a POD more than a few days ago.
- Loads with a large accessorial not yet confirmed.
Step 8: Send it in finance's format
Finance usually wants a spreadsheet export with fixed columns, or an import file for the ERP. Agree on the format once. Do not change columns from month to month.
Step 9: Close the loop next month
When the invoices for accrued loads arrive, they should be checked against the rate confirmation and the POD like any other invoice. If an invoice is far above the accrued amount, that difference is useful for finance and for the next month's estimate. The article on what freight audit data a finance team needs covers the fields that make that check easy.
Step 10: Keep the history
Save each month's list as it was sent. When auditors or the controller ask in March how the October accrual was built, the team should be able to show the list, the cutoff rule and the records behind each row. A record with change history makes that easy: it shows when the POD arrived, when the rate changed and when the invoice came in.
What goes wrong with month-end freight lists?
Most problems come from missing PODs, unclear cutoffs, wrong rates and lists built by hand from several systems. These mistakes are common and fixable.
Mistake 1: Using "delivered" status as proof
A carrier status can be wrong. Loads are sometimes marked delivered when they reached the terminal, or when a different load delivered. Use the POD as proof, and mark rows that rely on status only.
Mistake 2: No agreed cutoff
Does a load delivered at 9:00 p.m. on the last day, in a different time zone, belong to this month? Agree on one rule: the time zone of the delivery location or of the company's books, and the date on the POD. Write it down.
Mistake 3: Accruing quotes instead of agreed rates
A quote is not the agreed rate. The rate confirmation is. If the team accrues from quotes, the accrual can be off by the amount negotiated after the quote, or by a rate change before pickup.
Mistake 4: Leaving out known accessorials
If the load had six hours of detention that the carrier already confirmed in writing, the cost is real. Leaving it out makes the accrual too low and the next month's invoice a surprise.
Mistake 5: Counting invoiced loads twice
If the list includes loads already invoiced and approved, finance may accrue them on top of the invoice. Show invoice status on every row and exclude invoiced loads from the accrual total.
Mistake 6: Building the list by hand every month
When the list is assembled from carrier websites, inboxes and a spreadsheet, it takes days and depends on one person. If that person is out at month end, the list is late or incomplete.
Mistake 7: Not explaining the gaps
Finance can handle uncertainty if it is labeled. A row that says "POD requested on Oct 30, carrier says delivered Oct 29" is useful. A blank cell is not.
Mistake 8: Treating the list as a logistics favor
When the month-end list is an extra task that logistics does for finance, it gets done late and in a hurry. Treat it as part of closing each load. A load is not closed when the truck delivers. It is closed when the POD is filed, the invoice is checked against the rate confirmation and the POD, and the carrier is paid. If every load is closed that way during the month, the month-end list is just the loads that are not closed yet.
A short decision guide
| Load at cutoff | Include in accrual list? | Action for logistics |
|---|---|---|
| Delivered, POD on file, not invoiced | Yes | None, wait for invoice |
| Delivered by status, no POD, not invoiced | Yes, flagged | Chase POD now |
| Delivered, invoiced, not yet approved | Show, exclude from accrual total | Help approve if questions |
| Delivered, invoice disputed | Show with note | Resolve with carrier |
| In transit at cutoff | No, unless policy says so | Track to delivery |
| Cancelled after pickup was scheduled, TONU charged | Yes, if the charge is confirmed | Confirm the TONU in writing |
What checklist should logistics and finance agree on?
Agree once on the fields, the cutoff, the proof and the format, and the monthly list becomes routine. This checklist covers the decisions.
| Item | Question to answer | Owner |
|---|---|---|
| Cutoff | What date and time zone decide "delivered this month"? | Finance |
| Proof | Is the POD required, or is carrier status enough with a flag? | Finance |
| Rate basis | Is the rate confirmation the basis for expected cost? | Finance and logistics |
| Accessorials | Which confirmed accessorials are included? | Finance and logistics |
| Fields | Which columns does the list have? | Finance |
| Format | Spreadsheet export or ERP import file? | Finance |
| Timing | When is the list due after month end? | Finance |
| POD chase | Who chases missing PODs, and how fast? | Logistics |
| Invoice status | Where does logistics see whether an invoice arrived? | Accounts payable |
| Shipping terms | Do any loads shift months because of shipping terms? | Finance |
| Review | Who reviews the exceptions before sending? | Logistics manager |
| True-up | Who compares accruals with final invoices next month? | Finance |
How to roll it out
Run the first month with the current process and the checklist side by side. Look at where the data came from for each column. Every column that needed a manual search is a step to fix during the month, not at month end. Usually the first fix is POD collection on delivery day, and the second is invoice status on the shipment record.
What finance gains
When the list comes from one record, finance gets it on time, with proof and with fewer surprises the next month. Logistics stops spending the first days of each month digging through old email.
How does Wilson, by Cartage, help logistics give finance a month-end list?
Wilson, by Cartage, is an AI logistics agent that runs the freight work on each load and keeps the delivery, POD, rate and invoice facts on one record, so a month-end list comes from data already collected. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
The labor
The labor is what fills the record. Wilson quotes, books with written acceptance and a rate confirmation, schedules pickups and tracks each load with the best source available. It requests and files PODs, and it follows up with carriers by phone and email until it gets an answer. A missing POD is chased as part of the load, not at month end.
The data
The data is what makes the list possible. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. Records are searchable and exportable with change history. Wilson can produce reports on request from the loads it runs, so a list of delivered loads with their POD and invoice status can be pulled from the same record. Whether results are written back to the ERP depends on scope. 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.
The network
The network gives the shipper better freight rates on every lane, because its volume counts with every other Wilson customer's. The network includes carriers and brokers, and the company still approves who hauls its freight.
The payments
The payments close the month. Wilson 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 wait for a person. A duplicate invoice is attached to the load, not paid twice, and a corrected invoice counts only in its latest version. A change in remit-to or bank details is flagged to the team as a possible fraud signal. With the Wallet, the shipper funds the wallet and Wilson pays carriers from it, with payments going out on Fridays.
Control
Control starts with assisted execution: the company sets approval limits, and routine actions run automatically within those rules as the workflow is proven. Teams reach Wilson by email, Slack, Microsoft Teams, SMS, WhatsApp or phone. Timing depends on scope: most teams start on a few lanes and expand from there.
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.
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.15 minutes with the team behind Wilson. No prep needed.
Book 15 minutes →FAQs
Can Wilson give finance a list of delivered loads that aren't invoiced yet?
Wilson, by Cartage, an AI logistics agent, keeps every load, POD, rate and invoice on a searchable, exportable record with change history. It can produce reports on request from the loads it runs, so a list of delivered, uninvoiced loads can come from that record. The exact format is agreed with the team.
Why does finance need delivered loads, not invoiced loads?
Because the cost generally belongs to the month the service happened. Carrier invoices can arrive weeks after delivery, so finance needs the delivered list to record freight cost in the right month under its accounting policy.
Is carrier tracking status enough to prove delivery?
It is a signal, not proof. The signed POD is the proof. If the POD is missing at the cutoff, include the load with a flag and chase the POD.
What number should finance accrue for each load?
Usually the agreed rate on the rate confirmation plus accessorials already confirmed in writing. Possible charges that are not confirmed should go in a note.
What if the carrier invoice is much higher than the accrual?
Check the invoice against the rate confirmation and the POD before paying. The difference is either a valid charge the accrual missed or a charge to question with the carrier.
When should missing PODs be chased?
On delivery day or the day after. Waiting until month end makes PODs harder to get and leaves gaps in the list.
Does Wilson write the delivered status back to our ERP?
Wilson connects to the company's ERP, and write-back depends on scope. The exact data flow is agreed during setup.
How often should the list be run?
At least at each month end. Some finance teams also want it weekly, so the month-end list holds no surprises.
What happens to loads in transit on the last day?
They usually belong to the next month, but shipping terms and the company's accounting policy decide. List them separately so finance can see them.
Can Wilson produce carrier or lane reports for finance?
Wilson does not keep permanent scorecards by default, but it can produce carrier-performance and lane-rate reports on request from the loads it runs.
Should logistics or finance own the month-end list?
Finance owns the accrual and the policy. Logistics owns the facts behind it: delivery dates, PODs and agreed rates. The list works best when logistics keeps those facts current during the month and finance pulls the list at the cutoff.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
Let's review what finance asks logistics for at month end. You don't need to prepare anything: Cartage maps the workflow with you on the call.
