A disputed invoice is not a slow invoice, and a factor that works it on the collections calendar will get both wrong. Classify what arrived, pull the invoice out of the dunning ladder, decide who owns the conversation with the debtor and who owns the one with your client, and park it somewhere your reporting can still see it.
Five of our own guides lean on this desk and none of them describes it. Our collections guide gives the short-pay a paragraph and the right instinct, that it “is not a collections failure; it’s a signal that needs coding and routing.” Our cash application guide owns catching it at posting. Our pricing guide makes the reserve the thing that “absorbs disputes, short-pays, deductions, and chargebacks.” Our metrics guide builds dilution out of the same four words. Our client exit guide calls disputes in flight the part that makes the timing of an exit genuinely hard. Every one of them points at a desk nobody has written down.
Search the question and you get two things: pages telling a business thinking about factoring that disputes pause funding, and generic accounts receivable deduction management software. Neither has any freight in it. There is no cargo claim, no detention, no accessorial, no overage short and damaged. That is the gap, and it is a strange one, because in freight most deductions are not payment behavior at all. They are claims, and a claim is a different instrument with a different clock.
What actually arrives, and why the shape matters
Deductions reach a factor in four shapes and the shape tells you how much work is ahead.
Sometimes a debtor remits less than face with a reason code and backup attached, which is the best case and still needs classifying. Sometimes a debtor remits less than face with nothing, which is the most common case and the most expensive, because your first task is reconstructing what they think they are doing. Sometimes a formal claim letter arrives naming an amount and a cause. And sometimes nothing arrives at all: the invoice simply does not pay, and six weeks into your dunning ladder somebody mentions a pallet that showed up wet.
That fourth shape is the one that does the damage, and it is a cash application problem before it is a collections problem. A payment that came in short against a batch, posted on account or spread across invoices to make the remittance balance, hides the dispute inside your aging. The invoice looks current. It is not current. It is contested, and nobody knows. Our cash application guide owns that discipline and it is the upstream control for everything on this page.
Classify before you work it
Work a deduction without classifying it and you will apply a collections motion to a claim, which never works. The classes are not interchangeable and each one needs something different from somebody different.
A rate discrepancy is an argument about the agreed price of the move, and it is settled by the rate confirmation. A missing or late document deduction says the debtor never got what their payment process requires, and it is settled by producing the document. A denied accessorial, detention or lumper, says the debtor disputes a charge that sits on top of the linehaul, and it is settled by whatever evidence the agreement between your client and the debtor requires for that charge. A shortage or damage deduction is a cargo claim wearing a short-pay’s clothes. And an administrative deduction with no backing at all, the one that arrives as a round number against a batch, is not a dispute until the debtor says what it is for.
Write the class onto the file, not into somebody’s memory. The reason code is what lets you tell the difference between a client whose paperwork is bad, a debtor who deducts as a matter of policy, and a lane where the freight keeps arriving damaged. Three completely different problems that look identical on an aging report.
Most of the evidence is not yours
Here is the structural awkwardness of the whole desk, and it is why generic deduction content never helps.
You own the receivable. You do not own the proof. The signed bill of lading, the delivery receipt with the consignee’s notation on it, the arrival and departure times behind a detention charge, the lumper receipt, the photographs of the damaged pallet, the email where the broker approved the extra stop: all of it sits with your client or with the consignee. You are the party with the money at risk and the party with the least access to the facts.
So the collection you are running is a documentation collection before it is a cash collection, and your client is the counterparty. That reframing changes the operational design. Set the document standard at onboarding rather than inventing it during the first dispute, because our onboarding guide is where the client is still motivated and still listening. Give the client a deadline on producing evidence and a stated consequence when they do not, and make the deadline short enough that it lands inside the windows that matter. A client who cannot produce a proof of delivery three weeks after the fact will not be able to produce it three months after the fact either, and the cost of finding that out late falls on you.
A cargo claim runs on its own clock, and it is not your aging
This is the part the industry’s dispute content skips entirely, and it is the single most useful thing to understand about freight deductions.
When a deduction is really a loss or damage claim, there is a federal framework underneath it. Carrier liability for freight moving in interstate commerce runs through 49 U.S.C. § 14706, which makes the carrier “liable to the person entitled to recover under the receipt or bill of lading,” and which sets floors on time: a carrier “may not provide by rule, contract, or otherwise, a period of less than 9 months for filing a claim against it under this section and a period of less than 2 years for bringing a civil action.”
The processing of those claims has its own regulation. Under 49 CFR § 370.3, a communication counts as a valid claim when it identifies the shipment, asserts liability for the alleged loss, damage, injury or delay, and makes claim “for the payment of a specified or determinable amount of money.” The same section says what does not count, and this is the sentence worth taping to the desk. Bad order reports, appraisal reports of damage, and “notations of shortage or damage” on freight bills, delivery receipts or other documents do not, standing alone, meet the filing requirements.
Read that against what actually lands on a factor’s desk. A debtor short-pays and points at a damage notation on the delivery receipt. Under the regulation that notation by itself is not a claim. That does not tell you the deduction is wrong, and it is emphatically not a position to assert at a debtor out of a web page. What it tells you is what to ask for, which is the claim itself: the shipment identification, the assertion of liability, and the amount. A deduction that cannot produce those three things is an unexplained short-pay, and an unexplained short-pay is a different conversation from a claim.
The clocks matter just as much. Section 370.5 requires a carrier to acknowledge a proper claim in writing “within 30 days after the date of its receipt” unless it has already paid or declined it. Section 370.9 requires the carrier to “pay, decline, or make a firm compromise settlement offer in writing to the claimant within 120 days after receipt of the claim,” and if it cannot, to tell the claimant in writing why, and again at the end of every succeeding 60 day period while the claim is pending.
Now compare that to your aging buckets. A properly filed cargo claim can legitimately sit open for a hundred and twenty days before anyone is obliged to dispose of it, and longer with written status updates. Your 30, 60 and 90 day columns were built for payment behavior and they are measuring something else here. This is the operational reason a disputed invoice has to come off the normal dunning ladder: not out of politeness, but because the ladder is calibrated to a clock that does not apply.
One line, and it is firm. Part 370 governs how carriers process claims. It does not decide whether a particular deduction against a particular invoice you purchased is owed, and nothing above is a legal opinion. Carmack liability, setoff rights, whether your client’s contract validly shortened a filing period, and your own standing as assignee are questions for qualified factoring counsel. The pattern is the same one our notice of assignment guide uses: know the mechanism, and hand the position to a lawyer.
Who talks to the debtor, and who talks to the client
No source answers this and every factor has to decide it, usually badly, under pressure.
The instinct is to let the client handle it, since the client has the documents and the relationship. The problem is that you are the one who gets paid, and a client negotiating a deduction on an invoice you already bought is negotiating with your money. Deals get made that you learn about when the remittance arrives.
The instinct in the other direction is just as awkward. A factor that takes over every conversation with a debtor is now defending the quality of freight service it did not perform, on documents it does not hold, against a party whose relationship belongs to its client.
The workable split is to own the receivable conversation and let your client own the service conversation, with one rule across both: no settlement of an amount on an invoice you own without your approval, in writing, before it is agreed. Say it in the agreement, say it again at onboarding, and say it the first time a client tries. The client can agree the facts of what happened on the dock. Only you can agree what the receivable settles for.
And put somebody’s name on each disputed file. The single most common failure here is not a bad decision. It is no decision, by three people who each believed one of the others had it.
Where the invoice sits while it is contested
A contested invoice has to live somewhere, and “in collections” is the wrong answer.
Our pricing guide covers the reserve as a design element and describes it absorbing exactly this: disputes, short-pays, deductions, and chargebacks. The operational question underneath it is the eligibility one. An invoice under a live claim is not an ordinary receivable, and treating it as fully eligible in your own borrowing base means certifying something you know to be contested. Most factors learn this the uncomfortable way, during a field exam, when an examiner asks why a four month old invoice is still carried at face. Decide the treatment in advance and write it down.
Tell the client both halves at once, too. A disputed invoice delays the collection, and it delays the reserve release that invoice would have produced. The client feels it twice, at different times, and the second one arrives as a surprise if nobody said it out loud.
What it does to the number your lender reads
Dilution is where all of this becomes visible to people outside your building. Our metrics guide defines it as the gap between an invoice’s face value and what the debtor actually pays, built from short-pays, deductions, disputes and chargebacks, and makes the point that a book can carry almost no bad debt and still lose real margin here.
The deduction desk is the mechanism behind that number. Which means two things in practice. First, dilution that is not broken out by cause is a number you cannot act on, because “deductions are up” could be a document problem at one client, a policy change at one debtor, or a damaged lane, and the remedy is different for each. Second, a desk that writes off small deductions by default to clear the queue is manufacturing dilution quietly and calling it efficiency. We are not going to tell you that a disciplined desk reduces dilution to any particular level. What we will say is that a desk which cannot tell you the cause of last quarter’s dilution has no way to try.
When a dispute stops being a dispute
At some point a contested invoice stops being a documentation problem and becomes a recovery decision. That handoff deserves to be an event with a date on it rather than a thing that happens by exhaustion.
The trigger is not age by itself. It is the answer to a narrower question: is anything still being worked? A claim with a live file, a document the client has promised and is producing, a debtor who is responding, all of that is still a dispute. An invoice where the evidence never came, the debtor has stopped answering, and the file has not moved in weeks is not a dispute anymore, whatever the aging report calls it. At that point it goes to the recovery decision, which is its own subject: pursue, place, charge back to the client, or write it off. That decision has its own logic and we are not going to re-argue it here.
What this desk owes that decision is a clean file. The class of the deduction, what was requested and from whom, what arrived and when, what the debtor said, and who approved anything that was agreed. A recovery decision made on a file nobody documented is a guess with a date on it.
Where this stops being operational
Two lines, both firm.
How you book a deduction, how contested receivables are presented in your financial statements, allowances, and the tax treatment of any write-off are questions for your CPA. FRC is not an accounting firm and gives no accounting opinion. Our operations audit is an operational read of how the work runs, and it is neither a financial statement audit nor the freight bill auditing that the word usually means in this industry.
Carmack liability, cargo claim entitlement, setoff rights, and whether any deduction or chargeback provision is enforceable are legal questions. Read the regulations for what they say and take your position under them to qualified counsel.
Where an outside read fits
Deduction problems almost never show up as deduction problems. They show up as dilution nobody can explain, an aging report with old invoices on it that everyone has stopped looking at, a client who keeps settling things without telling you, and a quarter that came in under plan for reasons the monthly package does not contain.
The fixes are process, and they are not dramatic: a classification scheme with reason codes, a documentation standard set at onboarding with a deadline attached, a rule that disputed invoices leave the dunning ladder and get an owner, a written settlement authority, an eligibility treatment decided in advance, and dilution reported by cause. Collections, financial reporting, and onboarding are three of the six domains in FRC’s 90-Day Operational Audit, alongside risk, technology, and staffing, and the deduction desk sits across all three. The output is a written assessment and a prioritized 12-month roadmap, with no long-term commitment.
FRC’s founder, Renee Williams, built a freight factoring company from the ground up over 25+ years, leading credit and underwriting operations and designing the collections infrastructure these files move through. The operators we have worked with, MinWest Financial and MyFactor among them, came in understanding finance and not the operational realities of transportation. We cannot promise you a recovery on any deduction. We can help you build a desk where a contested invoice has a class, an owner, a clock, and a file. Call 800-648-5450 and Renee picks up directly.