Field note · 18 June 2026
Store Proceeds, Billings and Revenue Are Not Interchangeable
A field guide to the timing, fee, tax and refund differences that cause subscription reports to disagree.
A product event can confirm access in seconds. A store financial report can settle proceeds weeks later. Calling both figures “revenue” hides important differences.
Name the measure before comparing it
Customer billings describe the amount charged. Developer proceeds usually reflect commission and may reflect certain taxes or adjustments. Recognised revenue belongs to an accounting policy and can be spread across a service period. None is automatically wrong; each answers a different question.
Expect timing differences
Event timestamps, store transaction dates and fiscal calendars do not always align. Billing retries can grant grace access before cash settles. Refunds may appear in a later report than the original purchase. Currency conversion can introduce another date and rate.
A useful reconciliation starts with one market, one plan and one settled month. Match transaction identifiers where governance permits, then bridge gross amount, tax, commission, refunds and currency effects. Document residual differences rather than forcing them to zero.
Product teams can then use entitlement events for behavioural analysis while finance uses settled reports for proceeds—with a known bridge between them.