IAInvestigate
Invoice Adjustments
KeHE adjusted the invoice to match what was actually received or owed. Four sub-types: product short, missed allowance, supplier return, price discrepancy. Read the K-Solve backup sections independently.
Gold-standard field guide · K-Solve
How to audit a KeHE K-Solve export
For CPG operations teams auditing KeHE deductions — whether it is your first K-Solve export or your hundredth.
K-Solve shows that money was deducted. The investigation connects the line to the order, governing requirement, operational event, and evidence. This guide walks through the complete audit path with a worked example.
Direct answer
An audit connects a K-Solve line to its cause, evidence, and best next action.
KeHE uses 111 distinct deduction prefix codes. Each line in a K-Solve export represents a deduction against a specific invoice. The prefix tells you the type of charge. The investigation determines whether it is contractual, disputable, or still requires more information.
The audit path
Eight controlled steps from export to operational learning.
1Export
+
Start with the relevant K-Solve deduction data and preserve the original file. K-Solve retains up to two years of historical transaction detail. Export the grid as Excel, then protect the original before any manipulation.
2Normalize
+
Connect each line to the PO, invoice, deduction date, amount, and reason code. The prefix code on each line identifies the deduction type. KeHE uses 111 distinct prefix codes, many without public documentation.
3Classify
+
Separate contractual passthroughs from items that may warrant investigation or dispute. Not every deduction is recoverable. In a typical audit, the majority of deduction dollars are contractual.
4Trace
+
Identify the governing requirement, transaction, shipment event, or document behind each deduction. This means matching the line to the specific PO, the applicable fee schedule version, and the operational event that triggered it.
5Gather
+
Bring together BOLs, packing lists, photos, EDI records, appointment evidence, and messages. The evidence must be specific to the PO and the deduction date, not a general document.
6Prioritize
+
Order the work by dollar value, evidence readiness, dispute-window deadlines, and likely operational impact. Disputes must be filed within 180 days of the deduction date.
7Act
+
File through K-Solve (the only accepted channel) or route the next step internally. Include the dispute text, supporting evidence, and the specific PO and deduction references.
8Learn
+
Carry the root cause back into the PO workflow to reduce repeat issues. A recurring shortages pattern, for example, may indicate a labeling, packing, or appointment-timing problem upstream.
What you will see
Common prefix codes and what they mean in practice.
KeHE uses 111 prefix codes. These six appear most often and illustrate how different codes require different investigative approaches. See the full reference for all 111 codes.
SLFInvestigate
Service Level Fine
Fill rate fell below 95%, triggering a 3% fee on the shortage. Check whether your BOL and POD support the shipped quantity — DC count governs, but evidence can overturn it.
CNUsually contractual
Weekly Pass-Through
Retailer-initiated weekly charges routed through KeHE. Not a compliance chargeback. KeHE is the billing intermediary. Dispute route is the retailer, not K-Solve.
MCBInvestigate
MCB Processing Fee
The 8% processing fee on manufacturer chargebacks (promotional funding). AAP-enrolled suppliers are exempt. Verify enrollment status and fee math against the Fee Schedule.
CSUsually contractual
Customer Spoilage Allowance
Fixed-rate spoilage deposit taken on every PO. Verify the rate matches your Terms Form. Disputable only if rate is wrong, you are not enrolled, or there is a duplicate invoice.
GInvestigate
Damages or Spoils
Per-event damage charges for individual units. Requires photos, POD, temperature logs. Distinguish from CS (the proactive deposit) and Q (date-code failures). 48-hour UDR response window applies.
Decision guide
Is this deduction disputable?
Three questions, in order. Stop at the first “no.”
1
Can you match it to a PO?
If the deduction cannot be connected to a specific purchase order, invoice, and shipment, it needs investigation — not a dispute.
No match → Investigate first
2
Is it contractual?
Check the prefix code against your Terms Form and Fee Schedule. If the charge follows an agreed term, verify the math — do not dispute.
Contractual → Verify, log, move on
3
Is the evidence ready?
Do you have the BOL, POD, or other documents specific to this PO and deduction date? A dispute without evidence is worse than no dispute.
Evidence ready → File through K-Solve
Free audit tool
Let the audit tool run the classification pass for you.
The tool classifies deductions using validated rules for 48 of KeHE’s 111 prefix codes, each at 100% accuracy across 144 held-out test rows. 11 of those codes are validated against the domain rulings of a 20-year KeHE operations expert.
Upload
Drop your K-Solve export at the free audit tool. Excel or CSV. No EDI project, no sign-up, and no credit card required.
Gap analysis
The audit separates deductions that appear disputable from contractual passthrough. In one audit, $140,914 (88%) was identified as contractual passthrough, while $10,757 was flagged as disputable.
Ranked queue
Disputable items are ranked by win probability and dollar value. Estimated recoverable value is stated upfront, so effort goes where it can matter.
The audit reads your export. It does not see evidence held in email, warehouse systems, or carrier records. Final dispute decisions still rely on the operational story around each PO.
Frequently asked
Should every KeHE deduction be disputed?+
No. In the Sky & Sol audit, 88% of deduction dollars were contractual passthrough. Disputing those wastes time and credibility. A sound process distinguishes passthrough from genuinely disputable items.
What does K-Solve actually show?+
K-Solve shows that money was deducted and provides a reason code. It does not show the operational evidence (BOLs, photos, appointment records, carrier events) needed to dispute. That evidence lives in your 3PL, carrier, email, and EDI systems.
How long do I have to file a dispute?+
KeHE requires disputes to be filed within 180 days of the deduction date. Disputes are accepted only through the K-Solve portal. Email submissions are no longer accepted.
What evidence does KeHE expect?+
It depends on the deduction type. For shortages, a signed BOL or proof of delivery is decisive. For pricing disputes, the PO and signed deal sheet. For compliance chargebacks, timestamped EDI records and appointment documentation.
How does the free audit tool work?+
You upload your K-Solve export. The tool classifies each line using validated rules for 48 of KeHE's 111 prefix codes (100% accuracy across 144 test rows). It separates contractual from disputable, ranks by value, and estimates recoverable dollars. It does not see your email, 3PL, or carrier evidence.
How does prevention connect to auditing?+
The same patterns that surface during an audit, such as recurring shortages at specific DCs or repeated timing violations, indicate operational issues that can be addressed upstream through routing, documentation, and fulfillment changes.
Evidence boundary: This guide is an operating framework, not a substitute for current KeHE documents or a determination that any specific deduction is recoverable. Always verify current terms, evidence, and deadlines through the KeHE CONNECT Supplier portal.
The bridge