Log in to KeHE Connect
Navigate to the KeHE supplier portal and sign in with your credentials. K-Solve is accessed through the main Connect platform.
Field guide · K-Solve data
How to read, export, and audit your KeHE K-Solve data
The K-Solve export is where your KeHE deductions live. Every charge, every code, every dollar deducted from your invoices. This guide shows you how to pull the data, understand what each column means, spot the patterns that signal recoverable money, and audit what's disputable — manually or in 5 minutes with the free tool.
For CPG operations and finance teams managing KeHE deductions through the K-Solve portal.
Understanding K-Solve
What K-Solve is and why it matters
K-Solve is KeHE's supplier-facing deduction and dispute portal. It is the single source of truth for every deduction KeHE applies against your invoices, and the only accepted channel for filing disputes. Email dispute submissions are no longer accepted.
The portal contains transaction-level detail for every charge: the date it was applied, the amount, the prefix code that identifies the deduction type, the PO it was charged against, and the DC where the receiving event occurred. This data is exportable to Excel or CSV for offline analysis.
Quick Search: Covers approximately the last 90 days of deduction activity
Advanced Search: Reaches back up to 2 years of historical transaction detail
Dispute filing: The only accepted channel — submit directly through the portal
Export: Download the grid as Excel or CSV for offline review and audit
Key deadline
180
days to dispute
KeHE requires disputes filed through K-Solve within 180 days of the deduction date. A valid claim filed one day late is unrecoverable. This deadline drives everything in your review cadence.
Step by step
How to export your K-Solve data
The export is your starting point. Whether you're reviewing manually or uploading to the audit tool, you need a clean K-Solve export with the right date range.
Navigate to K-Solve deductions
From the main menu, find the K-Solve section. This is your deduction and dispute surface — the only channel KeHE accepts for dispute filing.
Select your date range
Quick Search covers roughly the last 90 days. Advanced Search reaches back up to 2 years. For a quarterly review, use Advanced Search and select the full quarter. For dispute-window awareness, export at least 180 days back.
Apply filters if needed
You can filter by DC, prefix code, amount range, or status. For a full audit, export unfiltered — let the classification tool or your review process handle the filtering.
Export to Excel or CSV
Click the export button to download the grid. Save the original file immediately and work from a copy. The original is your audit trail — never modify it directly.
Verify the export
Check that the row count matches what K-Solve displayed. Confirm the date range and total dollar amount. A mismatched export creates false conclusions downstream.
Column reference
What each column in the K-Solve export means
The K-Solve export contains several columns. The prefix code is the most important — it determines the deduction type and whether the charge may be disputable. Here's what each column tells you.
| Column | What it means |
|---|---|
| Transaction Date | The date the deduction was applied to your account. This starts the 180-day dispute clock. The further back the date, the more urgently you need to evaluate it. |
| Amount | The dollar value deducted. Negative values are charges against your invoice. Sort by this column descending to triage the largest deductions first. |
| Prefix Code | The two-to-four character code that identifies the deduction type. KeHE uses 111 distinct prefix codes. This is the single most important field for classification — it tells you what kind of charge this is. |
| Reference / Check Number | The remittance or payment reference linking the deduction to a specific settlement. Use this to cross-reference against your bank statement or accounts receivable ledger. |
| PO Number | The retailer-issued purchase order this deduction was charged against. This is your anchor — every piece of dispute evidence must trace back to this PO. |
| DC / Location | The distribution center where the receiving event occurred. Recurring deductions at a specific DC often indicate a systemic issue (routing, receiving practices, or label scanning) rather than a one-off error. |
| Description | Free-text description of the charge. Quality varies: some lines carry detailed explanations, others are terse codes. The prefix code is more reliable for classification than the description. |
KeHE uses 111 distinct prefix codes. See the full prefix code library for every code explained in plain English with confidence levels.
Manual review
How to read the export manually
If you are reviewing K-Solve data without a tool, this is the process. A 400-line export typically takes 4-8 hours to review thoroughly. The steps are straightforward — the time cost is in the matching and evidence gathering.
1
Sort by amount (descending)
Start with the largest deductions. A $9,300 shortage matters more than a $12 EP processing fee. Your time is finite; prioritize by dollar impact.
2
Identify the prefix code on each line
The prefix code tells you the deduction type. Without knowing the code, you cannot classify the charge. Cross-reference against the 111-code library to understand what each code means.
3
Match each line to its PO
The PO number in the export must match a real purchase order in your system. An unmatched line needs investigation before it can be classified or disputed. Do not dispute a deduction you cannot tie to a PO.
4
Check the dispute window
Calculate days remaining from the Transaction Date. Anything approaching the 180-day deadline gets priority regardless of amount. A valid dispute filed one day late is unrecoverable.
5
Separate contractual from disputable
Most deduction dollars are contractual passthrough — charges that follow agreed terms. In one verified audit, 88% of deduction dollars were contractual. Identify these first so your dispute capacity goes to the lines that actually have a chance.
6
Assemble evidence for disputable items
For each line you intend to dispute, gather the BOL, POD, packing list, ASN, and any communication that speaks to the specific cause. Generic documents get rejected. The evidence must be PO-specific.
Time estimate
A manual review of a typical quarterly K-Solve export (200-400 lines) takes 4-8 hours for an experienced ops person. This includes identifying codes, matching POs, checking windows, and assembling evidence for the disputable lines. The same analysis takes about 5 minutes with the free audit tool.
Patterns to watch
Five patterns that signal recoverable money
Most deduction dollars are contractual. But inside the noise, certain patterns consistently indicate charges that should not have been taken or were taken incorrectly. Here are the five most common patterns to look for in your K-Solve export.
Double deductions (IA + KC on same PO)
KeHE takes an IA (Invoice Adjustment) at receiving and then a KC (post-receipt audit) on the same PO for the same shortage. The same charge appears twice under different codes. These have a historically high win rate because KeHE's own records show the duplicate.
Always check: does a prior IA exist for this PO before disputing a KC?
Recurring CN charges that spike
Weekly CN (Credit Note) pass-throughs are contractual by default — promotional costs, slotting fees, MCB charges. But when the weekly amount jumps 2x above the trailing 4-week average, or a CN appears for a DC you do not ship to, it may be a billing anomaly.
Flag CN lines that exceed the trailing average by 2x or appear on unexpected DCs.
Fill-rate fees on POs where you shipped 100%
The SLF (Service Level Fine) charges a 3% fee when fill rate drops below 95%. But the fill rate is measured at the DC receiving count, not at your warehouse. If your 3PL shipped 100% and KeHE's DC counted short, the evidence is in the BOL and pick confirmation.
Compare your pick confirmation and BOL against the KeHE receiving count.
OTD penalties where the DC rescheduled
On-time delivery penalties are calculated on a rolling quarter. But if the delivery was late because the DC rescheduled the appointment, the lateness is DC-initiated. The evidence is in the C3 Reservations appointment history showing who moved the date.
Pull the C3 appointment history before accepting any OTD penalty.
EP fees on AAP-enrolled accounts
The EP (Expedited Processing) fee is 8% of the invoice. But AAP (Automated Accounts Payable) enrolled suppliers are exempt from the MCB processing fee. If you are AAP-enrolled and seeing EP or MCB charges, verify your enrollment status and dispute.
Confirm AAP enrollment status. AAP-enrolled brands should not see MCB charges.
The faster path
Or upload it and get the answer in 5 minutes
The free EasyOps audit tool reads the same K-Solve export you would review manually. It classifies every deduction line using validated rules for 48 of 111 KeHE prefix codes at 100% accuracy, separates contractual passthrough from disputable items, estimates recoverable value, and ranks disputes by priority.
$151,671
classified in one audit
Every deduction traced to its cause and rule
88%
contractual passthrough
Identified instantly — stop wasting time on those
$5,940
recoverable surfaced
The disputable dollars your manual review would have found in 4-8 hours
Real numbers from a real K-Solve audit. Results vary by distributor, volume, and deduction mix.
No sign-up·Free·Excel or CSV·Results in 5 minutes
Frequently asked
K-Solve export questions
How often should I export and review K-Solve data?+
At minimum, monthly. Weekly is better for brands with high PO volume. The 180-day dispute window means a deduction from six months ago is about to expire. A monthly cadence catches everything with at least 150 days of window remaining. A quarterly cadence risks losing disputable items.
Can I export more than 90 days of K-Solve data?+
Yes. K-Solve Quick Search covers approximately the last 90 days, but Advanced Search reaches back up to 2 years of historical transaction detail. For a comprehensive audit, always use Advanced Search and export the full period you want to review.
What if I cannot find a deduction in K-Solve?+
Some deductions appear on the remittance but not yet in K-Solve. There can be a lag between when the charge posts to your account and when it appears in the K-Solve interface. If a remittance line has no K-Solve match, note the date and check again in 3-5 business days. If it still does not appear, escalate to your KeHE account representative.
Should I dispute every deduction I find?+
No. In one verified audit, 88% of deduction dollars ($140,914 of $151,671) were contractual passthrough — charges that follow agreed terms and should be verified, not disputed. Disputing contractual charges wastes your time, erodes your credibility with KeHE, and diverts capacity from genuinely recoverable items. Classify first, then dispute only the lines with supporting evidence.
Where does EasyOps fit in the K-Solve workflow?+
EasyOps reads the same K-Solve export you would review manually. The free audit tool classifies every line using validated rules for 48 of 111 KeHE prefix codes at 100% accuracy, separates contractual from disputable, estimates recoverable value, and ranks items by dispute priority. What takes hours manually takes about 5 minutes. The ongoing platform then connects the K-Solve data to your POs, shipments, and evidence so deductions are caught and disputed continuously.
Evidence boundary: This guide describes the K-Solve export structure and review process based on current KeHE portal documentation and EasyOps audit experience. KeHE may update the K-Solve interface, export format, or dispute procedures independently. Always verify current portal instructions before filing disputes.
Go deeper
Related KeHE deduction guides
All 111 KeHE prefix codes
Every deduction code explained in plain English with confidence levels.
Read →
KeHE deduction evidence checklist
Cause-by-cause checklist of what evidence KeHE expects for each type.
Read →
How to dispute a KeHE deduction
The 7-step dispute path from deduction line to resolution.
Read →
Complete deduction management guide
The operating loop from remittance to root cause.
Read →
Start now