1
Download the remittance
Someone on the team downloads the KeHE remittance or pulls it from the portal. The file format, delivery method, and field structure vary — some arrive as portal exports, some via EDI 812, some in email.
Blog · Accounting integration
How KeHE deduction data flows into QuickBooks Online
KeHE deductions start as lines on a remittance. They need to end as credit memos in QuickBooks Online, categorized by type and attributed by retailer. This post maps the current manual workflow, the pain it creates at scale, and how the flow should work.
For CPG finance teams and fractional accountants managing KeHE wholesale accounts in QuickBooks Online.
Direct answer
The deduction classification that feeds the dispute should also feed the credit memo.
Today, most CPG brands run two separate workflows for the same deduction: one to decide whether to dispute it (operations), and one to record it in QuickBooks (finance). The classification is done twice, often by different people, using different tools. The result is a ledger that shows deductions as a flat cost line with no type, no retailer attribution, and no connection to the dispute outcome.
A CPG accountant with 20 years of experience described it: “We were consolidating all of this information with an offshore deductions person, having them put it into a Google Sheet… and then we were able to push those checks into QBO through an upload template. We did that for years. It’s so messy.”
The current workflow
Five manual steps, repeated every remittance period.
2
Decode the deduction codes
KeHE uses 111 distinct prefix codes. Without a reference, each code requires a manual lookup to understand what was deducted and why. The vast majority of time in this step is spent on interpretation, not data entry.
3
Create credit memos
Each deduction becomes a credit memo in QuickBooks Online. For brands doing this manually, this means keying in the vendor, date, amount, account, and memo field for every deduction line. At scale, this can be hundreds of entries per month.
4
Reconcile against invoices
The credit memos need to match against the original invoices. A single PO may have multiple deductions across different remittance periods, making the matching exercise non-trivial.
5
Categorize for reporting
To understand profitability by retailer or by deduction type, each credit memo needs to be tagged or categorized. Most early-stage brands skip this step entirely, which means their P&L shows deductions as a single undifferentiated line.
Why it breaks at scale
Four problems that compound with every new retailer account.
The nickel-and-dimes add up
A CPG accountant who works with scaling brands described the pattern: hundreds of small deductions that individually seem insignificant but collectively represent a meaningful cost. Without automation, most of these go unreconciled.
P&L by retailer is the hardest problem
Building a P&L by retailer requires estimating the pull-through from each distributor to each retailer, then allocating deductions and trade spend accordingly. It is an exercise outside the ledger, and most early-stage brands cannot do it.
Offshore teams inherit the complexity
Many CPG brands outsource deduction reconciliation to offshore accounting teams. Those teams consolidate information into Google Sheets, then push credit memos into QBO via upload templates. The process works but is fragile, slow, and introduces error at every handoff.
The dispute path lives outside the ledger
When a deduction is identified as disputable, the dispute itself (filing through K-Solve, tracking response, recording outcome) happens entirely outside QuickBooks. The ledger sees the deduction but not the dispute, creating a visibility gap for finance.
How the flow should work
From remittance to ledger without a spreadsheet in between.
1
Remittance ingestion
The remittance is pulled automatically from the KeHE portal or EDI stream. Each deduction line is parsed, and the prefix code is resolved to its plain-English meaning and classification.
2
Automatic classification
Each deduction is classified as contractual passthrough, potentially disputable, or requiring investigation. Contractual deductions are tagged for cost-of-sale tracking. Disputable items enter the dispute workflow.
3
Credit memo generation
Classified deductions are mapped to the correct QBO accounts and formatted as credit memos with structured fields: vendor, date, amount, deduction type, PO reference, and retailer attribution.
4
Push to QBO
Credit memos are pushed into QuickBooks Online via API. No manual entry, no upload templates, no offshore handoff for the data-entry portion.
5
Retailer-level attribution
Deductions are tagged by retailer so the P&L can be broken out by account. Trade spend, promotional passthrough, compliance fees, and operational chargebacks each go to their own category.
The accountant’s benchmark
Two features that unlock adoption.
A fractional CPG accountant who runs full accounting departments for scaling brands identified two specific capabilities as adoption unlocks for any platform that touches deductions:
Push credit memos to QBO
Ingest deductions, create credit memos, and push them to QuickBooks Online automatically. This eliminates the manual entry bottleneck and the offshore spreadsheet handoff.
P&L by retailer
True unit economics for each retail account: revenue minus deductions minus trade spend minus logistics, by retailer. Today this requires a manual exercise outside the ledger that most early-stage brands cannot do.
Source: advisory call with a CPG accountant specializing in $3M-$5M brands transitioning from DTC to wholesale, August 2026.
Frequently asked
How are KeHE deductions typically recorded in QuickBooks Online?+
Each deduction from the KeHE remittance is recorded as a credit memo against the original invoice. The credit memo captures the deduction amount, prefix code, date, and PO reference. Brands doing this manually create one credit memo per deduction line. At scale, this becomes hundreds of entries per remittance period.
Can I build a P&L by retailer using deduction data?+
Yes, but it requires attributing each deduction to the retailer whose activity generated it. Prefix codes like CN (customer-specific pass-through), SF (Sprouts refills), and GP (Publix reclamation) carry retailer identity. Others like SLF (service level fine) and IA (invoice adjustments) are KeHE-level. The attribution is possible but requires consistent tagging at the credit-memo level.
What does "push to QBO" mean in practice?+
It means creating credit memos in QuickBooks Online programmatically via the QBO API rather than manually entering them or using CSV upload templates. The result is the same ledger entry, but without the manual data entry step. This is what eliminates the offshore team bottleneck for the data-entry portion of reconciliation.
How does this relate to deduction management?+
Deduction management (classifying, disputing, recovering) and accounting reconciliation (recording in the ledger) are two sides of the same deduction. Today they live in separate workflows. The goal is for the classification that feeds the dispute decision to also feed the credit memo, so finance and operations share the same view.
Related reading