Use it for the routine part: sorting an open-invoice export by days overdue, drafting the reminder for each stage and listing delivered loads with no signed proof of delivery (POD). A person sends anything firm, handles disputes and makes the calls. AI cannot find a POD that was never captured, so the biggest gain is catching gaps on delivery day.
Many invoices that look late are really incomplete: no signed proof of delivery, a reference that does not match the rate confirmation, or extra charges with no paperwork behind them. Chasing the money before the package is complete burns goodwill with the one person in the customer's accounts team who can help you, so the routine below starts with the documents and only then with the dates.
What a twelve-truck carrier's open invoices look like
Start with a carrier that runs twelve trucks and bills about 150 loads a month at an average of $2,000 a load, so $300,000 a month, on net-30 terms. Every figure here is illustrative. On the last day of the month the receivables list ages out like this.
| Age of invoice | Invoices | Value |
|---|---|---|
| Not yet due | 150 | $300,000 |
| 1 to 7 days overdue | 30 | $60,000 |
| 8 to 14 days overdue | 20 | $40,000 |
| 15 to 30 days overdue | 15 | $30,000 |
| 31 to 45 days overdue | 7 | $14,000 |
| Over 45 days overdue | 3 | $6,000 |
| Overdue in total | 75 | $150,000 |
Billing runs at about $10,000 a day, so the $150,000 overdue is fifteen days of revenue sitting with customers, and the average invoice takes about 45 days to be paid ($450,000 open divided by $10,000 a day). Separately, the delivered-loads list shows 11 loads, about $22,000, with no signed proof of delivery two days after the drop, and four of those still missing at day seven.
Every day taken off the average payment time frees about $10,000 of cash, once. If the routine below moved the average from 45 days to 38, roughly $70,000 would come back and stay free. That is an if, not a promise. It is plausible where the delay is paperwork and unlikely where a customer pays slowly by policy, so the first job is to find out which kind of lateness you have.
An invoice package has four parts: the invoice; the rate confirmation (the agreed rate and terms for the load); the signed bill of lading or delivery receipt, which most offices call the POD; and receipts or notes for extras such as detention, unloading or layover charges. Packages break in four ways. The POD is unsigned or illegible. The load or reference number does not match the rate confirmation. Extras are claimed without paperwork. Or the invoice went to a dispatcher when the customer wanted it in a portal or at an accounts address. Check each overdue invoice against that list before you chase it. Where detention is part of the bill, tracking detention waits and invoicing them keeps the extra charge attached to the right load.
Two lists the AI works from
List one: open invoices. Export it from your accounting software or transport management system as a spreadsheet. Keep these columns: customer, invoice number, load number, invoice date, due date, amount, contact first name and email, how this customer wants invoices submitted (email, portal, address to use), POD received (Y or N), DISPUTE flag, PROMISE date, last chase date and notes. Add a days-overdue column built with a formula (today's date minus the due date). Do not ask the assistant to count days; a spreadsheet never miscounts a date.
List two: delivered loads. Columns: load number, delivery date and time, driver, customer, receiver, reference or PO number, POD received (Y or N), date received, days since delivery. It comes from dispatch records, and the POD column is ticked the moment a document is uploaded.
The submission column earns its place. A broker's accounts team may want the invoice uploaded to a portal with the POD and rate confirmation merged into one file, and a reminder emailed to a dispatcher goes nowhere. Put the right route in the sheet and make the assistant use it in every message.
Both lists hold customer names and amounts. Paste only the columns a task needs, leave out bank details and anything personal about drivers, and use a plan where your content is not used for training by default, or switch the model-training setting off on a personal plan. Settings labels change, so look at the privacy page for the plan you actually have. The guide to load paperwork without retyping covers how the documents reach these lists in the first place.
The reminder sequence, day by day
Count from the due date. The table shows who does what, and the rule behind it is that the AI drafts and a person sends once the tone gets firm.
| When | What goes out | Tone | Who sends |
|---|---|---|---|
| 3 days before, invoices over $5,000 | Check that the invoice and POD arrived and ask if anything is missing | Friendly | AI drafts, person sends |
| Day 1 | Reminder that the invoice was due yesterday, with invoice and POD attached | Friendly | Template, can be scheduled |
| Day 7 | Second reminder asking for an expected payment date | Neutral | AI drafts, person scans and sends |
| Day 14 | Phone call to accounts, then a two-line email recap | Firm, polite | Person calls; AI drafts the recap from the notes |
| Day 21 | Email naming a date by which payment or a reason is needed | Firm | AI drafts, manager approves |
| Day 30 | Final notice and a call; new loads for the account paused, if your terms allow it | Firm | Person |
| Day 45 | Owner-to-owner conversation: payment plan, collections or stopping work | Formal | Owner decides |
| Day 60 and beyond | Hand to a collections agency or a lawyer, after an adviser has read your agreement | Formal | Owner |
Four things stop the sequence and move the invoice to its own track. A dispute is logged: a person handles it with the evidence. The customer gives a payment date within the next five working days: log it, and send one reminder only if the date passes. The POD is missing: switch to the POD recovery steps below. Or you have reason to think the customer is in financial trouble: the owner decides. A reminder that lands on a customer who promised to pay tomorrow is the commonest way this routine annoys people, which is why the PROMISE and DISPUTE columns exist.
Read your agreement before the day-30 step. Pausing new loads or adding late charges only works if your terms provide for it, and a message should only say what you will actually do. If you want a wider look at reminder wording, reminders that sound human goes through the tone side for any business.
The same sequence bends to the customer. The table shows how the four usual cases differ, and the submission column in the sheet tells the assistant which row applies.
| Customer type | How the sequence changes |
|---|---|
| Broker with an invoice portal | Send reminders through the portal or its accounts address. Attach the POD and rate confirmation as one file and quote the portal reference. A dispatcher does not pay invoices. |
| Shipper with an accounts-payable team | Write to the accounts contact, not the dispatcher, and include their purchase order number. Ask which payment run the invoice is in. |
| Small direct customer | Phone first, then send the Day 1 email as a recap. This customer values a conversation more than a template. |
| Customer that pays late by policy, whatever the terms | Take them out of the sequence. Deal with it through the agreement or the price of their loads. |
Firm but polite: five messages to copy
Firm means specific. Every message names the invoice, the amount and the due date, attaches the documents, asks one question, and gives a date for the answer. The assistant fills the brackets from your table and leaves [MISSING] where the table has no value.
DAY 1
Subject: Invoice [invoice number], load [load number]: due [due date]
Hi [first name],
A quick reminder that invoice [invoice number] for $[amount], load [load number],
delivered [delivery date], was due on [due date]. The invoice and the signed
proof of delivery are attached. If anything is missing or doesn't match your
records, tell me what and I'll fix it today. Otherwise, could you confirm it is
scheduled for payment?
Thanks,
[your name]
DAY 7
Subject: Invoice [invoice number]: expected payment date?
Hi [first name],
Following up on invoice [invoice number] for $[amount] (load [load number]),
now [n] days past due. Could you let me know the date we can expect payment? If
it is waiting on a document or an approval, tell me which one and who holds it,
and I'll chase it from our side. Invoice and POD are attached again.
Thanks, [your name]
DAY 21
Subject: Invoice [invoice number] is 21 days past due
Hi [first name],
Invoice [invoice number] for $[amount] is 21 days past its due date of
[due date]. We sent it with the signed POD on [date] and again on [date] and have
not had a payment date. Please confirm by [date, three working days ahead] when
payment will be made. If there is a dispute, I'd like to hear it now so we can
settle it quickly. We value the work we do for you and want to keep the account
running smoothly.
Regards, [your name], [phone]
DAY 30
Subject: Final reminder: invoice [invoice number], 30 days past due
Hi [first name],
We haven't received payment or a payment date for invoice [invoice number],
$[amount], now 30 days past due. Under the terms we agreed, we won't be able to
take new loads on this account until it is cleared. I would rather not do that,
so please tell me today when payment will arrive, or call me on [phone].
Regards, [your name]
PROMISE TO PAY
Subject: Thanks: payment for invoice [invoice number] expected [date]
Hi [first name],
Thanks for the call today. To confirm: payment of $[amount] for invoice
[invoice number] will be made on [date] by [method]. I'll check on [next day]
and come back to you only if it hasn't arrived.
Regards, [your name]Include the day-30 sentence about new loads only if your agreement lets you do it and you will. The same goes for any late charge. Here is the Day 21 message filled in from one row of the sheet (illustrative figures, with the bracketed names left for you).
Subject: Invoice 10455 is 21 days past due
Hi [first name],
Invoice 10455 for $2,150 is 21 days past its due date of 3 November. We sent it
with the signed POD on 4 October and again on 10 November and have not had a
payment date. Please confirm by 27 November when payment will be made. If there
is a dispute, I'd like to hear it now so we can settle it quickly. We value the
work we do for you and want to keep the account running smoothly.
Regards, [your name], [phone]The swaps below turn the vague or heated versions an office writes at the end of a long day into something a customer can act on.
| Instead of | Write |
|---|---|
| "Why haven't you paid yet?" | "Invoice [number] for $[amount] was due on [date]. Can you confirm the payment date?" |
| "Hi, just checking on that invoice, thanks" | The Day 1 message: invoice, load, amount, due date, attachments, one question |
| "As per my last email" | "I've attached the invoice and POD again in case they were missed." |
| "Pay ASAP" | "Please confirm by [date] when payment will be made." |
| "We'll take legal action" | "If we don't have a date by [date], we'll pause new loads on the account, as our terms allow." |
Chasing a missing POD: driver, receiver, customer
A POD is complete when it shows a legible signature or dock stamp, the receiver's name, the delivery date and time, the piece or pallet count, any exceptions noted, and load and reference numbers that match the rate confirmation. Anything less is a likely rejection. The cheapest fix is on the day: the driver photographs the signed paperwork before leaving the dock, and dispatch ticks the POD column. If the box is not ticked two hours after the delivery time, a text goes to the driver.
When a POD is still missing, work up a ladder, one rung per day.
- Driver, same day. They may hold a photo or the paper copy. If the receiver did not sign, you need to know why and what the driver has instead.
- Receiver's dock or shipping office, next morning. Ask for a scan, or a written confirmation of the date, time and quantity received.
- The customer or broker, by day three. They may have the document through their own tracking, or the receiver may answer them faster than you.
- Your own supporting records. Keep the driver's photos of the freight on the dock, the seal number, the arrival time from your tracking system and any gate or dock receipt. Whether that is accepted in place of a signed POD is for the customer's agreement to say, so tell them exactly what you hold.
A POD also decides when cash arrives. Freight factoring companies generally will not fund an invoice until signed paperwork shows the load was delivered, and their own guidance lists the usual reasons a submission sits in pending: a bill of lading with no signature or no delivery date and time, a scan they cannot read, or an invoice total that does not match the rate confirmation because an extra such as an unloading (lumper) fee went in without its receipt. If you factor, a missing POD can hold up cash the same day, so check what your own agreement accepts.
TEXT TO THE DRIVER
Hi [first name], load [load number] to [receiver name] on [date]: no signed POD in
the system yet. Please send a clear photo of the signed paperwork by [time]
today. If the receiver didn't sign, tell me why, and send what you have (photo of
the freight on the dock, dock number, name of whoever checked you in) so I can
ask them.
EMAIL TO THE RECEIVER
Subject: Copy of signed delivery receipt: load [load number], delivered [date]
Hello [first name],
Our driver delivered load [load number] ([reference or PO]) to your dock on
[date] at about [time]. We don't have a copy of the signed delivery receipt.
Could you send a scan or photo of the signed copy, or reply to confirm the date,
time and quantity received? We need it to complete our invoice.
Thank you, [your name], [company], [phone]
EMAIL TO THE CUSTOMER OR BROKER
Subject: Missing POD: load [load number]
Hi [first name],
Load [load number] was delivered on [date]. We haven't received a signed POD
from the receiver and have asked them for it. Do you have a copy through your
tracking or from the receiver? If the receiver confirms delivery in writing,
will you accept that, together with our arrival record and delivery photos, to
release payment? Please tell me what you need.
Thanks, [your name]An assistant can also read a photo of a POD and list what is missing: signature, date, receiver name, piece count, reference. A prompt for that check, and a plausible reply, look like this.
Here is a photo of a delivery receipt for load 7731. List: receiver signature
(present, absent or unclear); printed name; delivery date; delivery time; pieces
or pallets; reference or PO number; exceptions written on it. Write UNCLEAR for
anything you cannot read with confidence. Do not guess.
Reply (illustrative):
Signature: present. Printed name: UNCLEAR. Date: 12 November. Time: UNCLEAR.
Pallets: 27 (handwritten). Reference: 55-2210. Exceptions: none written.The receipt actually says 22 pallets, and the assistant read a handwritten 2 as a 7. That is the typical failure with photographed paperwork: digits in handwriting. So the assistant's job is to flag what is missing or unclear, and counts, reference numbers and signatures are always checked by eye against the document. A person also looks at anything labelled UNCLEAR. Clear photos help more than any prompt, which is another reason to train drivers to photograph the receipt flat, in daylight, with all four corners in the frame.
A prompt that turns two exports into today's chase list
Save the sequence table and the templates in an assistant project (a ChatGPT Project or a Claude Project both hold standing instructions and files), then paste the two lists each morning with a prompt like this.
You are the billing assistant for a small carrier. I will paste two tables,
both exported today ([export date]). Use no other source.
Table 1: open invoices (customer, invoice no., load no., amount, due date, days
overdue, POD received Y/N, DISPUTE flag, PROMISE date).
Table 2: loads delivered in the last 14 days (load no., delivery date, driver,
receiver, POD received Y/N).
Task A: for every invoice with POD = Y, no DISPUTE and no future PROMISE date,
give the stage from my sequence (Day 1, 7, 14 call, 21, 30) and a one-line next
action. For stages 1, 7, 21 and 30 write the email from my templates, filling
the brackets from the table; write [MISSING] where the table has no value.
Task B: list loads with POD = N and delivery more than 1 day ago: load no.,
driver, receiver, days since delivery, who to contact first (the driver if under
3 days, the receiver if 3 or more).
Never invent invoice numbers, dates, amounts or names. Put anything that does
not add up under QUESTIONS.A typical reply (illustrative) starts with two small tables.
| Customer | Invoice | Days overdue | Stage | Next action |
|---|---|---|---|---|
| Customer A | 10482 | 8 | Day 7 | Email asking for a payment date |
| Customer B | 10455 | 21 | Day 21 | Firm email, manager to approve |
| Customer C | 10431 | 31 | Day 30 | Call first, then final notice |
| Load | Driver | Receiver | Days since delivery | Contact first |
|---|---|---|---|---|
| 7731 | Driver A | Receiver 1 | 2 | Driver |
| 7702 | Driver B | Receiver 2 | 6 | Receiver |
Below the tables come the drafts, and a QUESTIONS line such as "invoice 10468 shows POD = Y but the load list has no POD for load 7690; which is right?" That cross-check is where the second list repays its cost. Before anything goes out, check four things. The stage matches the days overdue in the sheet. No invoice with a DISPUTE flag or a PROMISE date has an email. No [MISSING] is left in a draft. And the amounts and dates in any Day 21 or Day 30 draft match the export line by line. Read the firm drafts for tone as well as facts.
Where the AI stops and a person takes over
- Disputes and short-pays. A deduction for damage, a claimed late delivery or a changed rate needs evidence and a decision. The assistant can summarise the email thread and list what each side says. It cannot judge who is right.
- Payment plans. A person agrees the dates. The assistant drafts the confirmation.
- Legal wording. Anything that threatens collections or court goes through an adviser first.
- Credit holds. Refusing loads is the owner's call. The assistant can list the accounts that have reached day 30.
- Substitute proof. Whether a customer accepts GPS records and photos instead of a signed POD is the customer's decision. You record the answer on the load.
- Anything about a customer's finances. Keep guesses about solvency out of messages and out of the assistant's hands.
For approvals inside a drafting tool, the tutorial on drafting, checking and chasing invoices with approval steps shows the pattern. And where a customer account has a credit limit and a hold rule, credit control for distribution companies is a close cousin of day 30 for a carrier.
The stale export: a slip to design against
Here is how it goes wrong. The export is Monday's and the emails go out on Tuesday. The assistant faithfully produces a final notice for invoice 10431, 31 days overdue, but the customer paid at 4 pm on Monday, after the export. The notice lands at 9 am. The customer's accounts clerk phones the owner, and the next call about a POD is a little less friendly. Nothing in the assistant's reply was wrong; the data was a day old.
Three guards prevent it. Put the export date in the file name and on the first line of the prompt. Refresh both lists before every run. And add a last step for any Day 21 or later message: look the invoice up in the accounting software for a payment received since the export, which takes about ten seconds each and only applies to a handful a day.
One week to set up, fifteen minutes a day to run
- Day 1, about two hours. Export both lists. Add the days-overdue formula and the POD, DISPUTE, PROMISE and submission columns. Tidy customer names so one customer is one name.
- Day 2, about 90 minutes. Rewrite the templates in your own voice and save them with the sequence table in an assistant project.
- Day 3, about 90 minutes. Dry run on ten old invoices. Compare the stage and wording with what you would have done, and adjust the instructions.
- Day 4. Run live in draft-only mode. Nothing sends without a person pressing the button.
- Day 5. Review the week, fix the wording that needed editing most often, and agree who runs the daily routine.
The daily routine is short: refresh both exports (one minute), paste them with the saved prompt (two), check the output against the four checks above (five), send or approve (five), and log call notes in the sheet (two). A chat assistant plan at about $20 a month list price is enough to start. Check whether your accounting package or transport management system already sends scheduled invoice reminders before adding anything; they know the due date but usually not your POD status. Once drafts have been right for a month, an automation tool can place the Day 1 and Day 7 drafts in your email as unsent drafts. Zapier's free plan covers 100 tasks a month, and its Professional plan lists from $19.99 a month billed annually for 750 tasks. Keep sending by hand until corrections are rare, and see which trucking accounting software has AI features worth paying for if you are choosing a package.
Six numbers that show whether the chasing is working
Record a baseline for four weeks before you start, then compare these monthly: average days to pay; the share of invoices paid on or before the due date; loads with a POD in the system within 24 hours of delivery; loads still missing a POD at day seven; office hours a week spent chasing; and disputes opened, which may rise at first because earlier chasing surfaces problems sooner.
An illustrative result after eight weeks for the twelve-truck carrier: average days to pay down from 45 to 40, which frees about $50,000 of cash; PODs within 24 hours up from 85% to 95%, which on 150 loads a month means about 22 late PODs falling to about 8, with the loads still missing at day seven dropping from four to one or two; and chasing time down from six hours a week to three. Do not judge the first fortnight. Old stuck invoices get paid, the average can rise before it falls, and a customer who pays 60 days late by policy will not change because of a better email. For those accounts the answer is in the contract or in how you price their loads.
Questions carriers ask about AI invoice chasing
Can AI send invoice reminders to trucking customers automatically?
It can for the early, low-risk stages, such as a friendly reminder a day after the due date with the invoice and POD attached, once the drafts have been correct for several weeks. Keep firm notices, disputes and anything past day 21 with a person. Check first whether your accounting software already sends scheduled reminders.
What if the receiver never signed the delivery paperwork?
Ask the driver what happened at the dock, then ask the receiver for written confirmation of the date, time and quantity. Keep your own records, such as the driver's photos and arrival time, and tell the customer exactly what you hold. Whether that substitute is accepted is the customer's decision and depends on your agreement.
How firm can a reminder be without harming the relationship?
Firm means specific, not harsh: name the invoice, the amount, the date it was due and the date by which you need an answer. State only consequences your agreement supports and that you will carry out, such as pausing new loads. Threats of legal action belong with an adviser, not an AI draft.
Is it safe to paste invoice lists into a chat assistant?
Paste only what the task needs: invoice and load numbers, amounts, dates and contact first names. Leave out bank details and personal data, and use a plan where training on your content is off by default, or switch the model-training setting off. Setting labels change, so check the privacy settings for your plan.
Further reads
- AI Software for Trucking Companies: What to Check for a Small Fleet — What to check before buying AI software for a small fleet.
- Chasing Unpaid Invoices With AI: Polite Reminders for Trades — The same reminder idea, written for trades with shorter terms.
- Trucking Price Quote Template: Build One and Check Rates With AI — A quote template that keeps rates and terms consistent.
- AI in Logistics for Small Delivery Firms: Routes, ETAs and Messages — A three-van worked example covering route planning, delivery windows, delay messages and proof-of-delivery replies, with named tools and monthly costs.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: a freight factoring company's guide to paperwork mistakes that slow funding (checked October 2026); Zapier's pricing page; the data-use settings of ChatGPT and Claude plans.