The KeHE recovery playbook for broker agencies.

KeHE is the second-largest natural distributor in North America, and for most broker agencies working the natural channel, it accounts for a meaningful chunk of the roster’s monthly revenue. It also accounts for a meaningful chunk of the monthly reconciliation pain.

If UNFI’s deduction culture is dense and code-heavy (covered in our UNFI cheat sheet), KeHE’s is somewhat different in mechanics but equally punishing in aggregate impact. Where UNFI leans on alphanumeric codes and portal-driven disputes, KeHE routes most of its dispute activity through a purpose-built system called K-Solve — and the operational shape of the problem changes accordingly.

This guide is written for broker agencies. It covers KeHE’s deduction landscape, how disputes actually work through K-Solve, common recovery patterns, and how to structure a reconciliation workflow that scales past three principals.

Why KeHE deductions deserve a separate playbook

Brokers who treat UNFI and KeHE identically make the same set of mistakes. The distributors look similar on the surface — both serve the natural and specialty channel, both extract deductions across similar categories, both take 30–45 days to resolve disputes. But the operational reality differs in three ways that affect broker workflow.

• KeHE’s dispute infrastructure is more consolidated. K-Solve serves as a single case management system for most dispute categories, whereas UNFI splits Natural (Excel form) and Conventional (ePASS portal) into different workflows. A broker managing both distributors needs different muscle memory for each.
• KeHE’s categorization is descriptive, not alphanumeric. Fewer three-letter mysteries, more plain-language reason descriptions on the remittance. This sounds easier — it’s not, because plain language obscures the underlying accounting treatment (contra revenue vs operating expense) that determines commission impact.
• KeHE’s recovery profile is more concentrated. Dispute wins cluster in a smaller set of high-value categories (freight, shortages, unauthorized deductions) while low-value categories (small compliance fees, minor scan disputes) rarely justify the labor cost of submission. UNFI has a flatter recovery distribution.

Practical implication: your broker agency needs a KeHE-specific dispute prioritization rule, not a generic “dispute everything over $X” heuristic.

KeHE’s deduction categories: what you’ll actually see

KeHE deductions cluster into six functional categories. Understanding the category matters more than memorizing individual line-item descriptions, because the category determines the workflow.

• Billback deductions. The workhorse category. Pre-agreed promotional expenses KeHE passes through to the supplier — scan promotions, temporary price reductions, ad program allowances, category management fees. Similar to UNFI’s MCB codes in accounting treatment (contra revenue) and disputability (valid if the promotion was pre-agreed and documented; disputable if rate, period, or scope don’t match).
• Freight deductions. Charged when suppliers don’t ship prepaid or when shipments require special handling — plus backhaul fees, redelivery fees on missed appointments, and detention charges. Highly disputable when documentation exists (carrier confirmations, BOLs, receipt logs), and frequently miscategorized on the supplier side.
• Shortage and damage. Product invoiced but not received, or received in unsellable condition. Standard reconciliation territory. Recovery requires POD, BOL, and often carrier claims documentation.
• Compliance and operational. Fill rate penalties, ASN errors, appointment failures, documentation issues. These are operating expenses, not contra revenue, and rarely change the commission base. Rarely worth disputing individually unless a pattern indicates a systemic issue.
• Return-related. Product returned by retailers and pushed back to the supplier — spoils (short-dated or expired), damages discovered post-delivery, and unauthorized returns. Recovery depends heavily on the supplier’s return policy documentation and KeHE’s compliance with it.
• Cash discount. Similar to UNFI’s 2% early payment discount. Not disputable. Bake it into pricing and move on.

How K-Solve actually works

K-Solve is KeHE’s dispute management portal. For broker agencies, it’s the primary interface for recovering deducted revenue on behalf of principals. Before the mechanics, three access realities to establish:

• Access is by supplier account, not by broker. Your agency doesn’t have its own K-Solve account — you access it as an authorized user on your principal’s supplier account. Each principal requires separate credentials, requested at onboarding. Miss K-Solve access in the first 30 days and you’re reactive instead of proactive on their disputes.
• Broker and supplier logins must be kept separate. Like UNFI’s ePASS policy, KeHE expects broker access to be provisioned as broker access — not shared supplier credentials. Dispute submissions carry an audit trail of who submitted them, and principals get uncomfortable when disputes appear to come from their own AP clerks who never did the work.
• Upload limits vary by case type. K-Solve accepts file uploads with the submission, but per-attachment size limits apply. A package with multiple BOLs, promotional agreements, and email trails may need to be compressed or consolidated.

The submission workflow itself follows a standard pattern:

1. Locate the specific deduction line on the remittance
2. Open a K-Solve case referencing the deduction
3. Select the dispute category (freight, billback, shortage, etc.)
4. Enter the disputed amount and reason narrative
5. Upload supporting documentation
6. Submit and receive a case number for tracking
7. Monitor status through the portal
8. Respond to any information requests from KeHE
9. Receive resolution — approved (payback issued), denied (with explanation), or partially approved

Response times typically fall in the 30–45 day range, similar to UNFI. Approvals show up on subsequent remittances as positive line items referencing the original disputed invoice.

The broker agency’s recovery rate reality

One of the more misleading claims in the deduction-recovery vendor space is around win rates. Marketing materials often reference “80%+ dispute win rates” — which is technically achievable if you cherry-pick which disputes to file. Any category filtered aggressively can produce a high approval rate.

The metric that actually matters to a broker agency is recovery yield: total dollars recovered divided by total dollars deducted across a period, expressed as a percentage of gross deductions. This sits somewhere between 8% and 25% for well-run reconciliation programs, depending on the principal’s category, distributor mix, and documentation discipline.

Categories where recovery yield tends to be highest:

• Freight disputes: often 40–60% recovery when documentation is clean, because carrier confirmations are typically well-preserved.
• Unauthorized deductions: nearly 100% recovery when they can be identified — though these are rare, usually system errors on KeHE’s side.
• Shortage disputes with POD: 50–70% recovery when a signed POD exists showing correct quantities.

Categories where recovery yield is disappointingly low:

• Compliance fees: below 20% recovery. KeHE holds a strong position on operational compliance.
• Late appointment fees: below 15% recovery. Documentation burden is high; wins are rare.
• Small billback disputes: below 25% recovery for anything under $200. Labor cost exceeds recovery.

A useful heuristic: if a specific deduction requires more than 20 minutes of investigation to build a case, and the recovery is under $500, the labor economics don’t work. This is where the 4-outcome reconciliation framework earns its keep — it automates the categorization so ops staff spend their limited time on the disputes that actually pay for the review.

Applying the 4-outcome framework to KeHE

The reconciliation framework we built into Linecard categorizes every incoming KeHE deduction line into one of four states. The rules for KeHE differ from UNFI, but the framework structure holds.

• Enforce — deductions that match a known valid contract term. A pre-agreed billback at the correct rate for the correct promo period. The 2% cash discount. A freight charge on a shipment where the supplier owed freight per contract. These post automatically, adjust the commission base, and don’t require review.
• Check — plausible but not fully verifiable. A billback at 4.5% instead of the contract’s 4% — close enough to be a rounding or interpretation difference but worth confirming. A freight charge that looks higher than typical for the lane. These land in a review queue.
• Flag — clear anomalies. A billback for a promotion that isn’t in the calendar. A freight charge on a shipment where the terms were FOB destination. A shortage where POD confirms full delivery. These are dispute candidates, routed to the K-Solve workflow.
• Gap — can’t be matched to any known contract term. Either the contract data is incomplete, or KeHE applied something outside the agreed scope. Requires principal follow-up before dispute or acceptance.

KeHE vs UNFI: the workflow, side by side

For broker agencies handling both distributors, the operational differences are worth internalizing.

For agencies still running reconciliation in spreadsheets, this table alone highlights the structural challenge: two distributors, two workflows, two audit trails, two dispute-tracking spreadsheets, and no unified view of recovery performance. Multiply by 10 principals and the operational load compounds fast.

Common mistakes broker agencies make with KeHE

• Treating KeHE like UNFI operationally. Muscle memory built on ePASS doesn’t transfer to K-Solve. Different case structure, different evidence handling, different response patterns. Ops staff need distinct playbooks.
• Missing the freight recovery opportunity. Freight is one of the highest-yield KeHE categories when documentation is clean. Many agencies skip freight disputes because they seem complex — in practice they’re often the most straightforward wins.
• Filing individual billback disputes instead of pattern disputes. If a promotion was applied incorrectly across 50 line items for the same period, K-Solve accepts consolidated disputes referencing the pattern. Filing 50 separate cases wastes ops time and dilutes the dispute’s coherence.
• Not chaining paybacks to original disputes. When a case is approved, the payback appears on a later remittance referencing the original case. If your system doesn’t chain these automatically, paybacks show up as unexplained credits and finance investigates “phantom” income.
• Ignoring return deductions. Spoils, damages, and unauthorized returns are often accepted without review because they feel messy. Some are disputable — particularly unauthorized returns and returns outside the agreed window. Ops discipline here recovers meaningful dollars.
• No principal visibility into recovery activity. Brokers who quietly file disputes and quietly collect paybacks without surfacing recovery value to principals underprice their services. Recovery is a visible broker value-add — surface it.

Building the broker recovery workflow

For agencies moving from spreadsheet reconciliation to structured recovery, the workflow shape matters more than the tool choice. A workflow that produces sustainable recovery across a roster has four components.

• Data ingestion. Remittance data flows in from EDI 820 (increasingly common for larger principals) or PDF (still the default for smaller ones). The system must parse both. PDFs are messier and need structured extraction; EDI is cleaner but requires format handling for the ADX segments that carry deduction details.
• Contract structure. Each principal’s commission agreement, promotional calendar, and trade allowance terms need to be structured data — not PDFs in a shared drive. Without this, no amount of remittance intelligence produces meaningful reconciliation, because there’s nothing to reconcile against.
• Deduction categorization. The 4-outcome framework runs against each remittance line. This is where automation earns its keep — 70–80% of deductions get auto-classified as Enforce (post and move on).
• Dispute submission and tracking. For every Flag, the workflow generates a case with pre-filled context, uploads to K-Solve (or the equivalent), and tracks status through resolution. Paybacks chain back to original cases automatically.

The layer agencies most commonly under-invest in is the contract structure layer. Building it takes weeks of extraction and validation upfront, and there’s no shortcut. But without it, everything downstream is guesswork.

Where manual reconciliation breaks

Manual KeHE reconciliation using spreadsheets and email folders works for a broker agency managing 2–3 principals with clean documentation habits. It stops working at principal #4 or #5, and by principal #7 it actively costs money.

The failure modes are rarely dramatic. They look like this:

• A billback dispute is drafted but never submitted because the ops person got pulled onto another task
• A payback lands on a remittance but doesn’t get chained back to the dispute, so it’s logged as generic income
• A freight deduction pattern goes unnoticed for months because no one aggregates by category
• A contract renewal changes commission terms but the spreadsheet formula doesn’t get updated, so months of commission math is quietly wrong

None of these produces a fire drill. They produce quiet, consistent revenue leakage — for the principal directly and for the broker agency indirectly through underpriced services and unrecovered disputes. Somewhere between 3 and 7 principals, every agency hits the point where spreadsheet reconciliation becomes the bottleneck to growth.

The modern approach: automating KeHE reconciliation

Linecard was built for the shape of this exact problem across both KeHE and UNFI in a unified workflow. The reconciliation engine ingests remittances (PDF or EDI 820), matches every line against structured principal contracts, categorizes into the 4-outcome framework, and routes Flag-category items into the appropriate dispute workflow — K-Solve for KeHE, ePASS or Excel form for UNFI.

Principal Portal access gives your brand principals real-time visibility into what your agency is recovering on their behalf. This turns reconciliation from an invisible cost center into demonstrated broker value — which matters for principal retention and for pricing conversations at renewal.

If your agency spends 6–15 hours per remittance cycle on KeHE reconciliation, or if you suspect freight and billback disputes are slipping through unreviewed, that’s the operational signal it’s time to move off spreadsheets.

Related reading

• UNFI Deduction Codes Explained: A Food Broker Agency’s Cheat Sheet (2026)
• The Broker’s Guide to EDI 820 Remittance Advice (coming soon)
• The 4-Outcome Reconciliation Framework: Enforce, Check, Flag, Gap (coming soon)

Linecard is a modern commission reconciliation and deduction recovery platform built specifically for food broker agencies.