Apparel returns and royalty true-ups
Returns lag is the single largest source of mid-period adjustments in apparel royalty reporting. A jersey sold in March may not be returned to the retailer until May, and the wholesale credit back to the brand may not post until June. The royalty paid to the licensor in March needs to true up — but if the true-up corrupts the original March statement, the audit trail is gone.
Why returns lag is structural
Apparel returns lag has structural roots in the wholesale channel. A retailer receives shipment in February, the consumer purchases in March, returns to the retailer in April, the retailer takes credit in May, and the wholesale credit posts back to the brand in May or June. The royalty owed to the licensor was calculated and reported in March based on the original sale.
DTC returns post faster — typically within 30 days of original sale — but the basic principle is the same: the royalty calculation reflects sales at a point in time, and subsequent returns require adjustment.
Why "rewrite the prior statement" is wrong
A common spreadsheet pattern is to go back to the original-sale period's workbook, subtract the return units, recalculate, and resubmit. This breaks audit trail. The original statement that the licensor received in April is no longer reconcilable to the current workbook in June.
The right pattern: preserve the original statement intact. Apply the adjustment in the current period with explicit attribution back to the original-sale period. The audit trail shows what was reported then, what is being adjusted now, and how the adjustment ties back.
Returns reserves vs. true-ups
Returns reserves are a cash-flow management tool, not a returns-lag accounting tool. A reserve holds back a percentage of current-period royalty payments to account for expected future returns. The reserve trues up periodically as actual returns post.
Returns reserves smooth cash flow for the licensee but do not change the underlying accounting reality — the royalty owed for an original-sale period is what it is, and adjustments tie back to that period regardless of whether a reserve smoothed payment timing.
How structured-data platforms handle this
In a structured-data royalty platform, returns are first-class entities with original-sale-period attribution. When a return posts, the calculation engine identifies the original-sale period, generates an adjustment with that attribution, applies it to the current-period statement as a true-up line, and preserves the audit trail through recompute history.
The licensor sees the adjustment in the current statement with full reference to the original period. Year-end audits can produce per-period reconciled royalty history at any level of granularity — by school, by team, by SKU — without manual reconstruction.