DSD Settlement Statements: AR/AP for Independent Distributors

A DSD settlement statement is the weekly document that nets an independent distributor’s product purchases against the revenue the manufacturer collected on their behalf, plus stale and damage credits, promotional allowances, retailer chargebacks, and route-loan payments — producing one number: the check (or the balance owed). If you run a direct-store-delivery operation with owner-operators, this one document is where your accounts receivable, accounts payable, and route financing all collide.

The pattern confuses almost everyone the first time they see it: the customer pays the manufacturer, and the manufacturer pays the driver. A supermarket chain remits one check to the bakery, snack maker, or beverage plant — and the independent operator who actually delivered the product gets their margin a week later, on a statement that also deducts their truck payment. That flow is not an anomaly. It is the standard settlement model across fresh bread, snacks, beverage, and dairy DSD, and this post enumerates how every variation of it works.

Who owns the receivable? Cash accounts vs. charge accounts

Everything in DSD settlement follows from one question: who owns the receivable for a given account? The answer depends on the account, not the company. The same independent operator (IO) typically services two kinds of stops:

• Cash accounts — small independents: convenience stores, delis, bodegas, independent grocers. The distributor negotiates the price and collects payment directly. The IO owns the receivable, carries the collection risk, and keeps the full retail-minus-wholesale spread.
• Charge accounts— chains with a centralized buying office. The manufacturer bills the chain and receives payment directly, then credits the IO’s share back through the weekly settlement. Large retailers demand a single EDI and payment relationship with the manufacturer — they will not cut checks to dozens of individual route operators.

This split is well documented. In a National Labor Relations Board proceeding examining Bimbo Bakeries’ distributor operations, the record describes exactly this structure: for chain accounts, “Bimbo Foods receives the payment directly from the customer by billing the customer,” and the distributor’s product cost is then “offset by the revenue that Bimbo Foods received from the customers.” The IO’s cash accounts, meanwhile, stay entirely off the manufacturer’s books.

Because virtually every real route mixes both account types, a single weekly settlement statement blends both flows — which is why the settlement engine, not the invoice, is the accounting heart of a DSD operation with independent operators.

The five money-movement models in DSD

Across food & beverage DSD there are essentially five ways money moves between the end customer, the manufacturer, and the person on the truck. Most operations run several at once.

1. Buy/sell with direct collection

The “true” independent-distributor model. The IO takes title to the product at the depot — ownership and risk of loss pass the moment it is loaded — buys at a wholesale price (commonly around 80% of retail), resells at retail or a negotiated price, and collects directly from cash accounts. The IO keeps the spread and eats their own bad debt and, depending on the return policy, their own stales.

Worked example:an IO buys $8,000 of product at wholesale for the week, sells it across their cash accounts for $10,000, and collects the $10,000 themselves. Gross margin: $2,000. If $400 of product came back stale and couldn’t be credited, the week nets about $1,600 before truck, fuel, and insurance.

2. Centralized / charge-account settlement

The model behind “the customer pays the manufacturer, the manufacturer pays the driver.” The IO still delivers and still legally owns the product, but the sale to the chain is billed by the manufacturer on the chain’s payment terms. The manufacturer floats the receivable; the IO gets their margin on the weekly settlement regardless of when the chain actually pays.

Worked example:an IO delivers $6,000 of product at retail to a chain account during the week. The manufacturer invoices the chain $6,000 (say, net 21). On the IO’s settlement, the manufacturer charges the IO’s wholesale cost of $4,800 and credits the $6,000 collected — a $1,200 margin — then deducts a $150 stale credit passed to the retailer, a $200 scan-promotion allowance, a $180 route-loan payment, and a $25 handheld fee. Net remitted for that account’s activity: roughly $645. The chain never writes the IO a check.

3. Commission / agency

In the pure commission model the IO never takes title. The manufacturer bills and collects everything, and the IO is paid a percentage of gross (or net-of-credits) weekly sales. Some wholesale bakeries run their entire route network this way, with commission rates typically landing around 19–23% of gross weekly sales for bread routes.

Worked example:a commission route grossing about $21,000 per week at a ~19% commission pays the IO roughly $4,000 per week; after ~$800 of weekly operating expenses (fuel, vehicle, insurance), the operator nets around $3,200 before any route-purchase financing. Economically this looks a lot like buy/sell — the difference is legal (who holds title) and how the payment is styled: a “discount/margin” versus a “commission.”

4. Consignment

The manufacturer retains ownership until the product sells. Product is left at the store without being charged on delivery; the store is invoiced only for what sold, measured as opening inventory minus the count at the next visit. Shrink is the supplier’s risk — the opposite of traditional DSD. Consignment breaks generic ERPs because delivery is not a sale: on-truck and in-store consigned inventory has to be tracked as the manufacturer’s own stock until the count says otherwise.

5. Pay-by-scan / scan-based trading (SBT)

The supplier owns the product until it crosses the register. Ownership transfers at the moment of POS scan, and the retailer pays on aggregated scan data (EDI 852), typically daily or weekly, often mediated by a third-party clearinghouse. Grocery-sector analysts have estimated scan-based trading at roughly $21 billion of annual grocery volume — with bakery among the most common SBT categories. The supplier bears shrink, and unsold or out-of-code product simply never gets paid for. Scan-funded promotions frequently cascade onto the IO’s settlement as deductions, which is a recurring source of distributor disputes.

Anatomy of the weekly settlement statement

Whatever the mix, everything converges on one weekly document. The settlement statement itemizes what the distributor purchased, what the manufacturer collected on their charge accounts, every credit and deduction, and the financing withholdings — then nets it to a single figure. A representative cascade:

Two properties of this document matter more than any other. First, it must support a negative net. A heavy week of credits, chargebacks, and loan payments can exceed the margin, and the operator owes the company — a real and painful scenario on struggling routes. Second, it is the system of record.The settlement ledger is what feeds the operator’s 1099 at year end, what backs up every dispute, and what a buyer scrutinizes when a route changes hands (routes are commonly valued at a multiple of average weekly sales).

Credits and chargebacks: stales, damages, and deductions

Fresh product is what makes DSD settlement genuinely hard. Bread carries a 3–7 day shelf life, and stale returns (“stales” or pull credits) typically run 2–4% of sales on a well-managed bread route — more when ordering is sloppy. Snack products with longer shelf life run far lower return rates, which is one reason snack DSD settlements are simpler than bread. Who eats the stale loss varies:

• In buy/sell, the IO absorbs unsold product unless the manufacturer’s return policy credits it. Policies range from full credit for in-code returns to caps around 15% of sales, to “drop-and-go” arrangements with no stale credit at all but a separate damage-credit policy.
• In consignment and pay-by-scan, the supplier bears shrink by construction.
• In centralized settlement, a stale credit granted to the retailer after the chain already paid becomes a credit memo against the customer’s account anda corresponding line on the IO’s next settlement — a timing mismatch that creates most of the weekly reconciliation pain.

One distinction generic accounting systems miss entirely: “good” credits versus “bad” credits. A good credit returns sellable product to the warehouse and restocks inventory. A bad credit is dumped product — tracked for tax and shrink reporting, but never re-entering stock. Collapsing the two corrupts both your inventory counts and your margin reporting, and it is a known failure point when DSD operations try to run settlement on a generic ERP.

Route financing flows through the same statement

Most independent operators finance the purchase of their territory, and the settlement is where the loan gets repaid. The large public bakers document the pattern plainly: Flowers Foods (Nature’s Own, Dave’s Killer Bread, Wonder) reported notes receivable from its independent distributor partners of $108.1 million(long-term) as of December 28, 2024 — loans collateralized by the distribution rights themselves, financed through a wholly-owned subsidiary at fixed interest, with terms up to ten years and repayments withheld from weekly settlements. Bimbo similarly offers financing covering 90–95% of a route purchase.

For the manufacturer, that means the settlement statement is not just an AP document — it is also the collection mechanism for a loan book. A route in trouble shows up first as shrinking settlement nets, and the note, the territory value, and the weekly statement all have to reconcile.

What this means for your ledgers

Put the pieces together and a DSD manufacturer with independent operators is running three sub-ledgers simultaneously, reconciled weekly:

• Customer AR— real receivables from the charge accounts the manufacturer bills centrally. (Cash accounts are the IO’s receivable and never touch these books.)
• The IO settlement ledger — effectively AP to each operator, but populated from both directions: credits (collected revenue, return credits, allowances) and debits (product cost, chargebacks, fees, loan payments).
• Notes receivable — the route-financing book, amortized through weekly settlement withholdings.

The GL treatment at the big public players is a useful fingerprint of the centralized model: Flowers recognizes revenue gross— the full customer price — and books the distributor’s discount as a selling, distribution and administrative expense, not as a reduction of sales. If your income statement shows gross customer revenue up top and “distributor discounts” in operating expense, you are running centralized settlement whether you call it that or not.

Where paper and spreadsheets break down

Most small and mid-size DSD manufacturers still run this entire machine on NCR paper tickets, a route-accounting spreadsheet, and a generic accounting package that has never heard of a stale credit. The failure modes are predictable:

• Every delivery ticket gets rekeyed at least twice — once into invoicing, once into the settlement spreadsheet — and the two drift.
• Credits arrive after the chain already paid, so the settlement shows one number, the AR aging shows another, and someone spends Friday reconciling them by hand.
• Good and bad credits collapse into one “returns” column, quietly corrupting inventory and margin.
• Negative settlements and loan balances live in a side spreadsheet nobody audits until a route changes hands.
• The 1099 total gets reassembled every January from 52 statements that were never designed to add up.