What should a rebate accrual audit checklist cover?

Q: What should a rebate accrual audit checklist cover?

Five domains, in dependency order: the agreements the accrual rests on, the qualifying base it is computed from, the estimate inside it, the lineage that makes it reproducible, and the settlement & classification that close the loop. A checklist that only re-performs the arithmetic misses the point — the arithmetic is almost never where accruals fail. Use it as a quarterly self-audit: every “no” below is the location of a future audit finding, found early and fixed cheaply.

Also: rebate audit preparation · variable consideration audit checklist · rebate program controls

The short answer

Five domains, in dependency order: the agreements the accrual rests on, the qualifying base it is computed from, the estimate inside it, the lineage that makes it reproducible, and the settlement & classification that close the loop. A checklist that only re-performs the arithmetic misses the point — the arithmetic is almost never where accruals fail.

Use it as a quarterly self-audit: every “no” below is the location of a future audit finding, found early and fixed cheaply.

A · The agreement layer

Every accruing program has a signed, current agreement — no accrual resting on an email thread or an expired contract rolled forward by habit.
Amendments are versioned, not overwritten — the terms in force for any past period are still retrievable.
The tier mechanic is named in writing — retroactive or incremental — not inferred from a table; the money difference is on retroactive rebate.

B · The qualifying base

The base is defined as a computation — returns, freight, surcharges, currency, and entity scope each explicitly in or out.
The same definition was applied every period — twelve slightly different bases produce a difference nobody can attribute.
Entity eligibility is a rule with an as-of date — membership changes, M&A, and affiliates resolve mechanically, not by negotiation.

C · The estimate

The estimation method is documented per program — most-likely or expected value, with the reasoning; the selection logic is on estimating a tiered accrual.
The forecast basis is written and dated — what the finishing-rate call rested on, as of when.
The estimate has an owner and a revision log — every rate change dated, with its trigger.
The constraint was considered and documented — and considered in the right direction: for rebates, doubt pushes the accrual up, not down.

D · Lineage

Any prior accrual is reproducible today — same number, from the inputs as they stood at booking, with the transactions underneath; the structural requirement is on rebate audit trail.
Corrections reference the original — supersession, never overwrite; the figure certified at close still exists.
Approvals are attached to the calculation — who approved which number, captured when it was made, not reassembled from email at audit time.

E · Settlement & classification

The true-up decomposes into named causes — rate estimate, late data, base drift — not one plug; the test is on rebate true-up.
Classification is supported — contra-revenue by default, with fair-value documentation for anything expensed, and vendor rebates on the buy side reducing cost, not income.

How to run it

Score one material program end-to-end each quarter rather than all programs shallowly. Fifteen yeses means the audit is a review. Each no localizes the finding before the auditor does — and the three artifacts that answer most of these checks at once (the calculation record, the estimate memo, the true-up bridge) are described on defending a rebate accrual to auditors. The free assessment runs a compressed version of this checklist in about three minutes.