Food Distributors Write Off Short-Pays Under $250. An Overnight Agent Rebuilds the Deduction File by 7 AM.

$17,516. That is the gap between the check and the invoices.

A regional grocery chain sends an ACH for $186,402 against $203,918 of open invoices. The 820 remittance lists 41 deduction lines: seven shorts, eleven damages, nine spoils allowances, six promotional billbacks, five unsaleables, three coded only "PRICE DIFF." Some of those are legitimate. Some are the same short they already took last month. At least one is a promo they ran in a market you don't even service.

Your AR clerk has until Friday to close the month. Researching one deduction properly — pull the invoice, pull the signed proof of delivery out of DispatchTrack or Roadnet, pull the driver's route settlement sheet, check whether a credit memo was already issued, check the deal sheet for the promo period — takes her twenty-five minutes when everything is where it should be. Forty-one lines is seventeen hours. She has three, because she also has to post today's cash, release two accounts off credit hold before the trucks roll, and get the COD envelopes from the drivers' check-in reconciled.

So the shop rule everyone has and nobody writes down kicks in: anything under $250 gets written off. It costs more to chase than it's worth. Multiply that rule by a year and it is one of the largest uncontested transfers of money out of a food distribution business.

What "reconciled by morning" has always meant in this trade

Distribution has always had a night shift. Selectors pull, loaders load, the night dispatcher builds routes, and by 4 AM the trucks are staged. The office side has never had one. Everything that needs matching — POD to invoice, driver's return sheet to credit memo, deduction to backup, vendor ASN to what actually came off the inbound trailer — waits for people to arrive at 7:30 and starts as a pile.

Here is the plain definition of what changed: a long-running agent is software you hand a job to at 6 PM that works on it unattended all night and hands you back a sorted queue at 7 AM — matched items closed, unmatched items flagged with the reason and the document attached. Not a report. A queue with the research already done.

The 2024 version of this idea could read one document if you fed it one document. The 2026 version, on Claude Cowork and ChatGPT Work, takes a goal — "match every line on this remittance to a POD, a credit memo, or a deal sheet, and tell me which ones have no backing" — connects to the systems that hold those records, and grinds through it for six hours without anyone watching. ChatGPT Work landed 9 July 2026 doing exactly that; Claude Cowork has been at it since January and went to web and mobile this month.

The overnight run, in the order it actually happens

flowchart LR
  A["6:15 PM: drivers checked in, PODs synced"] --> B["Agent pulls 820 remittances and open deductions"]
  B --> C["Matches each line to POD, credit memo, or deal sheet"]
  C --> D["Rebuilds evidence packet per disputed line"]
  D --> E["Valid: draft credit memo queued"]
  D --> F["Invalid: chargeback rebuttal drafted with signed POD"]
  D --> G["No backup found: flagged for AR clerk"]
  E --> H["7:00 AM: controller reviews and approves"]
  F --> H
  G --> H

Notice what the chart does not contain. There is no node where the agent sends money, issues a credit, or answers the chain's accounts payable department. Every path ends at a human at 7 AM. That is the design, and it is what makes the whole thing safe enough to run while you sleep.

What the controller's Tuesday looks like instead

At 7:05 AM the controller opens one screen. Twenty-eight of the 41 lines are closed: the POD is signed for the short, the credit memo already exists from the 12th, the promo period matches the deal sheet. Nine are drafted as rebuttals — for each one there is a scanned delivery ticket signed by the receiver at the store, a photo from the driver's handheld, and a two-sentence letter ready to go to the chain's deduction portal. Four are flagged: no backup anywhere, needs a human call.

She reads for thirty minutes, approves the credits, sends the nine rebuttals, and assigns the four calls to the AR clerk. What used to be seventeen hours of nobody's-favorite work is now half an hour of judgment plus four phone calls.

The same overnight window handles the other pile nobody loves. Inbound receiving: the ASN said 22 pallets of shelf-stable, the receiver scanned 21, and one lot number doesn't match the certificate of analysis on the supplier's email. That exception is on the buyer's screen before he takes his coat off, with the supplier's own document attached, instead of surfacing three weeks later when accounting can't match the vendor invoice. Route settlement: driver 14's COD envelope is $180 light against his return sheet, flagged for the transportation supervisor rather than discovered at month end.

Running the numbers on deductions alone

Illustration with stated assumptions. Take a distributor doing $48 million a year, roughly 60% into retail and chain accounts where deductions are a way of life.

That $38,808 is not new revenue. It is cash that was already yours, going straight to the bottom line at 100% — which at a 2% net margin is the equivalent of finding $1.9 million of new sales. And it is recovered without hiring a deduction analyst, which is the only other way to get it, and which costs more than the money in a house this size.

Prove it cheaply: take one chain customer and one quarter of remittances, run the overnight match by hand for two weeks, and count how many lines had valid backup nobody had looked for. If the answer is "almost none," this project isn't for you. In most food houses the answer is uncomfortable.

Where this breaks, and what stays with a person

It breaks on documents that were never captured. If your drivers still take a paper delivery ticket and the signed copy lives in a rubber-banded bundle in the transportation office, an overnight agent has nothing to match against. Getting signature capture onto the handhelds is the prerequisite, not the AI.

It breaks on the deal sheet that lives in a sales manager's email. Promotional billbacks and manufacturer chargebacks are the messiest deduction category in the business precisely because the agreement is often a forwarded message with an attachment. The agent will flag those as unbacked, correctly, and you will spend the first month cleaning up how promotions get recorded. That cleanup is worth more than the automation.

And it must never close a dispute or write off a balance on its own. Writing off a receivable is money leaving the company. Approving a credit memo is money leaving the company. Both stay with your controller, every time, no exceptions and no thresholds — because a threshold is exactly the thing a bad input would aim at.

Keep the customer relationship human too. A chain's AP contact who hears from a person about a repeated short is a contact who fixes the underlying receiving problem at store 118. An automated rebuttal letter every week just makes you the vendor they slow-pay.

Frequently asked questions

Where do I start if I don't want to touch AR yet?

Start with inbound receiving exceptions. Have the overnight run compare each ASN to what was actually scanned off the trailer and produce a short list for the buyer by 6:30 AM. It touches no money, the answer is verifiable the same morning, and it will tell you within a week whether your data is clean enough for the AR work.

My ERP is old. Does that kill it?

No, but it changes the plumbing. Older food ERPs — and there are a lot of long-serving installs out there — usually can export what you need on a schedule even if they can't be queried live. An overnight job is the friendliest possible use case for that, because it can work off a nightly export instead of needing anything real time.

What about the summer? Our volume doubles from Memorial Day to Labor Day.

That is when the deduction file gets worst, because the same clerk is covering vacations and the promo calendar is at its heaviest. The overnight queue does not care that it is the second week of July. If anything, the case for it is strongest in your peak season and weakest in February.

Who owns this internally?

The controller, not IT. The person who defines what "matched" means and who approves the queue at 7 AM is the person who has to own the setup. If it gets handed to whoever runs your servers, the rules will be technically correct and commercially wrong.

One footnote on the daylight side of this. Every unresolved short and every disputed credit eventually turns into a phone call from a chef, a store receiver, or a chain's AP department, and those calls land on the same desk that takes orders. CallSphere builds voice and chat agents that answer those lines around the clock, capture the account, invoice number, and what the caller is disputing, and route it to the right person with the details already written down — so the morning queue and the phone queue stop being two separate messes.