A Carrier Short Paid Your Invoice: The Dispute Packet That Gets You Paid

The short answer: do not send an email that says "you underpaid, please remit the balance." Send a one-page dispute packet that makes the payer's easiest move to pay you. The packet names the exact invoice and the exact dollar gap. It states the contract term or agreed charge that supports each disputed line, attaches the proof for that line, and says what you want and by when. Payers short pay for a reason, and the reason is usually a specific line. A packet that answers that line gets paid. A vague nudge gets filed.

This guide walks through how to build that packet, in the order that saves the most time.

Step 1: Find out what was actually short paid

Before you write anything, reconcile the remittance against your invoice, line by line. Do not work from the total.

• Pull the remittance advice, the payment record, or the deduction notice.
• Match every invoice line to what was paid, partly paid, or rejected.
• Write the gap per line, not just in total. A $412 shortfall might be one $400 accessorial and $12 of rounding. Those are two different conversations.

Many short pays are not disputes at all. Common non-disputes include a payment applied to the wrong invoice, a payment held for a missing document, and a bank or processing fee netted out. Rule these out first. If the remittance shows the money landed on a different invoice number, the fix is a short note asking for reapplication, not a dispute.

Step 2: Classify the reason

Once you have the per-line gap, put each short line into one of a few buckets. The bucket decides what proof you need.

1. Rate disagreement. The payer paid a different base rate than you billed.
2. Accessorial rejected. Detention, layover, lumper, reconsignment, extra stops, or similar charges were denied or reduced.
3. Missing or mismatched documents. The payer says the proof of delivery, the signed bill of lading, or the rate confirmation is missing or does not match.
4. Quantity or weight difference. The payer used a different weight, pallet count, or mileage than you did.
5. Offset or chargeback. The payer deducted something against this invoice, such as a claim, a prior overpayment, or a penalty.
6. No reason given. The payment is simply lower, with nothing explaining it.

If you land in bucket 6, your first message is a request for the reason code or deduction detail, not a dispute. Asking a clear question is faster than arguing with a number you do not understand.

Step 3: Assemble the packet

The packet is a single PDF or a single email thread, not a pile of attachments scattered across five messages. For each disputed line, include these items.

The cover summary (one page)

• Your invoice number, the load or shipment reference, and the dates.
• Invoiced amount, amount received, and disputed amount, per line and in total.
• One sentence per disputed line stating why you believe it is owed.
• The specific action you want: pay the balance, reapply the payment, or send the deduction detail.
• A date you would like a response by.

The agreement

• The signed rate confirmation or contract page that sets the rate or the accessorial terms. Highlight the clause. Do not make the reader hunt for it.
• If terms changed after booking, include the written approval. A verbal change with no record is a weak position, so say so to yourself honestly and decide whether the line is worth pursuing.

The proof of service

• Signed proof of delivery and bill of lading, with any notations such as times in and out, exceptions, or receiver signatures.
• For time based charges like detention, the timestamps that show arrival, start of unloading, and departure, plus the free time allowed by the agreement. Show the arithmetic: free time, time over, rate per unit, total.
• For lumper or third party fees, the receipt, and any approval you obtained before paying it.

The communication trail

• Any message where the payer or the carrier approved the charge, asked for the extra stop, or acknowledged the delay. A single approving email often settles the whole dispute.

Keep each attachment named so the reader can tell what it is without opening it. A file called "scan0042.pdf" costs you time. A file called "INV-1187_POD_signed.pdf" saves it.

Step 4: Match the packet to the reason

Different reasons call for different emphasis. Lead with the strongest proof for the bucket you identified.

• Rate disagreement: the signed rate confirmation first. Nothing else matters if the document is on your side.
• Accessorial rejected: the agreement clause, then the timestamps, then the approval. Payers often reject accessorials because the request arrived without documentation, so make the documentation the headline.
• Missing documents: simply send the missing document and ask for the payment to be released. This one should take a single message.
• Quantity or weight difference: the scale ticket, the bill of lading, or the receiver's count. If the difference comes from a reweigh or reclass by the payer, ask for their supporting document in return.
• Offset or chargeback: ask for the underlying claim or prior invoice number. If the offset is legitimate, you may owe a conversation about a different document. Cargo claims in particular follow their own filing rules and timelines, so treat them separately from billing disputes and check the contract and applicable rules.

Step 5: Send it to the right person, and track it

Send the packet to whoever actually resolves disputes: an accounts payable contact, a dispute or deductions inbox, or the account representative named in your agreement. Check your contract for a dispute procedure, because some agreements set a window for raising short payments or require the dispute to go to a specific address. If your agreement names a window, treat it as a hard deadline and start the clock from the date you received payment, not the date you noticed.

Then keep a simple log: invoice, disputed amount, date sent, who received it, response date, and outcome. Follow up on the date you stated. A polite second message that restates the amount and attaches the cover page again is normal and professional.

Step 6: Fix what caused it

Each recurring short pay is a process signal. If detention keeps getting rejected, the likely cause is that you are submitting it late or without timestamps. If documents keep going missing, attach proof at the time of billing instead of after the complaint. Track your short pay reasons for a month or two and the pattern usually shows up quickly. Fixing the top cause is worth more than winning any single dispute.

FAQ

Should I call or email first? Email, with the packet attached, so there is a record. A call is useful after that to find the person who can act on it, but follow it with a written summary.

What if I do not have the proof for a line? Be honest with yourself about the line. If the agreement is silent and no approval exists, the line may not be collectible, and spending hours on it can cost more than it returns. Pursue the lines you can prove, and fix the process so the next one is documented.

How much should I dispute? Dispute what you can support. A packet that claims everything, including weak lines, weakens the strong ones. Separate the strong lines clearly so they can be paid even if the rest is still under review.

Can I just deduct the shortfall from the next payment I owe them? Check your agreement first. Self help offsets can breach terms and damage the relationship, and they may be prohibited. When in doubt, ask whoever handles your contracts.

How long should I wait before following up? Use the response date you stated in your packet. If your agreement or the payer's process names a timeline, follow that instead of guessing.