KeHE Deduction Codes & Invoice Prefixes (2026)

KeHE deductions are payment reductions applied to supplier invoices through K-Solve, inside the KeHE Connect portal, for issues ranging from invoice adjustments and shortages to retailer-specific scans, audits, and promotional billbacks. Suppliers have 180 days from the deduction date to file a dispute by email or in K-Solve, and every deduction is identified by a two- or three-letter invoice prefix appended to the invoice number.

This guide is built directly from KeHE's internal Glossary of Terms and Invoice Prefix Key, updated July 2026. It covers the most common KeHE deduction codes, how they are grouped, and what action to take when you see them on an invoice or inside K-Solve.

 What Are KeHE Deductions? 

 KeHE deductions are payment reductions KeHE applies to a supplier invoice when it identifies a pricing discrepancy, a quantity shortage, a promotional billing error, an audit finding, or a retailer-level chargeback passed through from one of the stores KeHE distributes to. 

Every deduction carries an invoice prefix, a two- or three-letter code placed before the deduction line item, that tells you who initiated the charge: KeHE itself, a specific retail banner (Albertsons, Meijer, Sprouts, CVS, and dozens more), or a promotional program.

Deductions are managed inside K-Solve, which lives under the Sales Orders tab of the KeHE Connect dashboard. Suppliers can dispute deductions there, or by emailing with full backup documentation, within 180 days of the deduction date.

Because KeHE distributes for hundreds of independent, natural, and specialty retailers, not just its own DCs, a single supplier can see deduction prefixes from a dozen different banners on one check run, which is what makes the code list below worth keeping on hand

How KeHE's Deduction Code System Works

KeHE displays the invoice prefix directly in the invoice number inside K-Solve. Once you know the category structure, matching a prefix to the right dispute evidence takes seconds instead of a support ticket.

Three things shape how KeHE deductions flow:

• KeHE issues the deduction, but the retailer often originates it: Codes like AA (Albertsons Ad), MN (Meijer Scan), or CVSN (CVS Scans) are billbacks KeHE is passing through from the retail banner, not charges KeHE invented itself. 

  The dispute still goes through K-Solve, but the backup documentation needs to satisfy the retailer's program terms, not just KeHE's. 

   

• Invoice adjustments follow their own numbering: When KeHE issues a general invoice adjustment, it appends IA directly to your invoice number, so invoice INV1234567 becomes INV1234567IA in K-Solve, shown as a negative dollar amount.
•  Not every deduction is disputable the same way: Category-level deductions (shortages, pricing, audits) usually need transactional proof, a PO, BOL, or signed delivery record. Promotional and scan deductions need the signed program agreement showing the terms KeHE's system should have applied. 

Related Read: Managing Deductions on KeHE Supplier Portal with iNymbus

The Most Common KeHE Deduction Codes

DPI INVOICE PREFIXES (DEDUCTION CODES)

How to Dispute a KeHE Deduction in K-Solve

A successful KeHE dispute follows a consistent process:

1. Identify the prefix: Find the two- or three-letter code at the start of the invoice number in K-Solve's first column.

2. Match it to a category: Use the tables above to determine whether it's a KeHE administrative adjustment, a promotional/advertising billback, a retailer-specific scan, or a product/fulfillment issue.

3. Pull the right backup documentation: Administrative and shortage codes need the PO and delivery records. Promotional and scan codes need the signed program agreement and proof of execution (flyers, ad recaps, scan period dates).

4. Check it against your P&P or promotion agreement: If the deduction doesn't align with your signed terms, it's disputable.

5. File in K-Solve using the red or blue dispute icon, and attach all documentation up front, KeHE allows up to 180 days for a response, and incomplete submissions are the most common reason disputes stall.

Related Read: KeHE Deductions Guide: How to Use K-Solve

Recover KeHE Deductions Faster with iNymbus

KeHE's deduction system spans hundreds of retail banners, each with its own promotional rules, scan programs, and audit standards, all funneled through the same K-Solve interface. Matching every prefix to the right backup documentation manually, invoice by invoice, is where most AR teams lose recoverable revenue.

iNymbus automates the full KeHE deduction process. The platform connects directly to K-Solve, identifies deduction prefixes automatically, pulls the right backup documentation (POs, PODs, promotion agreements, invoices), and files disputes with the evidence each category requires.

What suppliers using iNymbus get:

• KeHE deductions disputed dramatically faster than manual, invoice-by-invoice review
• Automatic categorization by prefix, administrative, promotional, retailer-specific, or product-related
• Auto-fetching of POs, PODs, and promotion agreements matched to specific claims
• Centralized visibility across all open, in-progress, and resolved KeHE claims
• Analytics that surface root causes by prefix, retail banner, and DC

iNymbus supports 52+ retailers and carriers, so the same automation that recovers KeHE deductions also handles Walmart OTIF, Amazon Vendor Central, Target SPM, and Costco compliance chargebacks.

Schedule a free demo with iNymbus to see how much recoverable KeHE revenue is sitting in your current process.

Conclusion

KeHE invoice prefixes are not arbitrary. They are a classification system that tells you who took the deduction and why. Once you know that WG means Walmart spoils, CS means customer spoilage allowance, and IA means a general invoice adjustment, you can move from confusion to action.

Your next step: Pull your last three KeHE invoices, highlight every prefix you do not recognize, and match them to the categories above. If a charge does not align with your agreements, log into K-Solve and dispute it with the backup documentation ready.