Author Business & Productivity

How do I read a royalty statement?

By the WriteLoom editorial teamUpdated 2026-06-03
Key facts
  • A royalty statement reports sales, returns, and what you are owed.
  • Key lines: units sold, returns, net units, rate, and earnings.
  • Reserves against returns withhold some earnings temporarily.
  • Net vs list royalties change how the rate is applied.
  • Reconciling against your own records catches mistakes.
Direct answer

Read a royalty statement by working through its columns: gross units sold, returns, net units, the royalty rate, and the resulting earnings — plus any reserve against returns that withholds part of your payment. Confirm whether the rate applies to net receipts or list price, since that changes the math. Then reconcile the figures against your own sales records; statements can contain errors, and only your own tracking will reveal them.

Chapter i·Why it matters

Royalty statements are notoriously opaque, and many authors simply trust the bottom line — which is how underpayments and errors go unnoticed. Understanding the columns (especially reserves against returns and the net-versus-list basis) lets you see what you are actually being paid and why. Reconciling against your own records is the only way to catch mistakes, making statement literacy a basic protection for your income.

Chapter ii·What to include

  • Gross units sold and returns.
  • Net units and the royalty rate.
  • The net-vs-list basis for the rate.
  • Reserves held against future returns.
  • The period the statement covers.
  • A reconciliation against your own sales records.

Chapter iii·Example

An author opens her statement and traces it line by line: 1,200 units sold, 150 returns, a 25%-of-net rate, and a reserve holding back part of the payment. She reconciles against her own tracker and spots that one channel's sales are missing — an error she only catches because she kept her own records.

In WriteLoom

WriteLoom keeps your own sales records in one place, so reconciling a royalty statement and catching errors is straightforward.

See WriteLoom