A SKU rebate is only as accurate as its product list on the transaction date.
The person searching for this runs rebate accounting at a manufacturer or distributor whose programs pay on specific products — a per-unit amount on a new line, a percentage on a family, an exclusion on the variant Legal carved out. The math per line is trivial. The failure is the list: SKU eligibility drifts every time the catalog changes, and a stale list corrupts every accrual downstream, silently. Aurgus treats product as a first-class eligibility dimension: date-effective include and exclude lists, per-line qualification, and lineage from every accrued dollar back to the line and the SKU that earned it. Aurgus is in design-partner stage, which we state plainly.
How a material or SKU rebate actually works.
Product-scoped rebates exist to steer mix — push a launch, defend a line under attack, clear an exit. The structure is the same across industries; only the vocabulary changes (SKU, material, part number, NDC, item).
- 1
The agreement names the products.
An explicit list — SKUs, materials, families — with includes and excludes. Sometimes a hierarchy node (“all of product line X”) with carve-outs. This list is a contract term, and every accrual inherits its accuracy.
- 2
The agreement sets the basis: per-unit or percentage.
Per-unit (the SPIF shape): a fixed amount per unit, immune to price noise, easy to verify. Percentage of line value: scales with realized price but inherits every pricing question — gross or net, before or after other discounts, at what currency rate.
- 3
Every transaction line is tested for eligibility.
Is this line’s product on the list — as the list stood on the transaction date? Product catalogs churn continuously: launches, discontinuations, replacements, pack-size changes. Yesterday’s list applied to today’s lines is the root of most SKU-rebate errors.
- 4
Qualifying lines accrue; the rest must be explainably excluded.
Rate × quantity or rate × value, accumulated per agreement per period — and at settlement, the customer’s claim is reconciled against your accrual, line by line. The lines you excluded need reasons, because those are exactly the lines the customer will ask about.
Where SKU rebates go quietly wrong.
Product-scoped programs fail through the catalog, not the calculator. The Off-Invoice Control Index scores your exposure across these dimensions in about three minutes.
- New SKUs launch mid-period and never join the list. The replacement part inherits the old part’s program in everyone’s head — but not in the spreadsheet. The under-accrual surfaces at settlement, as a customer claim you can’t match.
- Discontinued and excluded SKUs keep accruing. The carve-out Legal negotiated lives in the contract PDF; the VLOOKUP list was built before the carve-out. Over-accrual, discovered by nobody, funded by margin.
- Aggregation hides eligibility. Computing the rebate on monthly product-group totals instead of per line means you cannot say which transactions produced the liability — which is precisely the question an auditor, or the customer, will ask.
- Rate changes mid-period apply to the wrong window. The per-unit amount stepped up in April; the spreadsheet applied the new rate to the whole quarter. Date-effective rates need date-aware calculation, per line.
- Pack-size and unit-of-measure changes corrupt per-unit math. The same material in a new case quantity doubles or halves the per-unit accrual unless someone catches the conversion — at line volume, someone doesn’t.
What Aurgus does for SKU rebates — and what it deliberately doesn’t.
Product is a first-class eligibility dimension in Aurgus, on the same substrate as our rebate management software. Per-unit (SPIF) and percentage bases are v1 patterns, and the accrued liability carries into your ASC 606 close with the same line-level lineage as every other program.
- 1
Product lists as governed, date-effective agreement scope.
Includes and excludes are structured properties of the agreement — versioned when amended, so each transaction line is evaluated against the list as it stood on the transaction date, not the list as it stands today.
- 2
Per-line eligibility with the outcome recorded.
Qualified lines say under which agreement and which product term; excluded lines say why. Exclusion is a first-class outcome, not a silent drop — which is what settles the settlement-time argument.
- 3
Per-unit and percentage bases computed deterministically.
Rate × quantity or rate × value, with date-effective rates applied per line — same data, same agreement, same answer every run, with lineage from the accrued dollar to the source line, the SKU, and the clause. The same bar as the rebate audit trail.
- 4
Totals that reconcile on screen.
What came in, what qualified, what was excluded, and proof the pieces sum to the whole — per agreement, per period, in front of you.
- 5
Human-approved changes and settlements.
List amendments and rate changes take effect when a named human approves; settlements are gated the same way, and the approval is part of the record. Transaction data arrives as workbook or CSV today.
Your SKU eligibility lives in per-program VLOOKUP tabs.
If the product list is maintained by hand per spreadsheet, every catalog change is a chance for silent drift. Date-effective, governed product scope is exactly what Aurgus ships.
You can’t answer “which lines earned this accrual.”
Line-level accrual with lineage — the transaction, the SKU, the clause — is the shipped core of the product, and it is what both the auditor and the customer claim reconciliation actually need.
You need automatic catalog sync from your PIM or ERP.
Aurgus does not subscribe to your product master automatically. Product data and transactions arrive as workbook or CSV today; list changes are reviewed and approved by a human, deliberately. Continuous master-data connectors are roadmap.
You need unit-of-measure conversion authority.
Aurgus computes on the quantities in your transaction data; it does not own pack-size or UoM conversion rules today. If your per-unit programs depend on case-to-each conversion, that conversion happens upstream — and we say so here rather than in the demo. Aurgus is in design-partner stage, which we state plainly.
SKU rebates, honestly answered.
- What is a SKU or material rebate?A rebate scoped to specific products rather than total purchases: a per-unit amount or percentage applying only to an agreed list of SKUs, materials, or families. Manufacturers use them to steer mix — push a launch, defend a threatened line, clear an exit. The defining property: eligibility is decided per transaction line by product identity, so program accuracy rests on the product list and the rate in effect on each transaction date.
- How do you account for SKU-level rebates?Accrue at the line level: each qualifying line contributes rate × quantity (per-unit) or rate × value (percentage), accumulated per agreement per period. The failure mode is aggregating first — monthly product-group totals hide which lines qualified, silently include lines that shouldn’t, and can’t answer the audit question of which transactions produced the liability. See rebate accrual journal entries for the posting side.
- What happens when the SKU list changes mid-period?Two failure directions: new SKUs that belong but were never added produce missed accruals, discovered at settlement when the claim exceeds the accrual; discontinued or excluded SKUs left on the list produce over-accrual, discovered by nobody. The fix is date-effective eligibility: the list is versioned, and each line is evaluated against the list as of its transaction date.
- Per-unit or percentage — which basis is better?Per-unit (the SPIF shape) is immune to price noise — easy to verify, blunt as an instrument. Percentage scales with realized price but inherits every pricing question: what basis, gross or net, what currency rate. Neither is better in general; what matters is that the basis is stated in the agreement and applied identically on every line, because ambiguous bases are where SKU spreadsheets quietly diverge from the contract.
- Can Aurgus calculate material and SKU rebates?Yes — product is a first-class eligibility dimension. Explicit include/exclude lists evaluated per line as of the transaction date; per-unit and percentage bases as v1 patterns; lineage from every accrued dollar to the line, the SKU, and the clause. Data arrives as workbook or CSV today. To pressure-test a real program, talk to one of our experts.
The adjacent mechanisms you’re probably also running.
Bring one product-scoped agreement and its SKU list.
Thirty minutes. No pitch. We’ll compare the contract’s product terms against what your spreadsheet actually tests, and tell you honestly whether Aurgus fits — including where it doesn’t yet.