ASC 606 sets out a structured approach to recognizing revenue from customer contracts. A business identifies the distinct promises in a transaction, allocates the total price across them based on their standalone selling prices, and recognizes revenue for each promise as it is satisfied. The framework is principle based, so judgment is applied consistently rather than by mechanical rules alone.
Consider a sale that also grants loyalty points. Under the standard, the points can represent a separate promise to the customer, so part of the transaction price is allocated to them and deferred. That deferred amount is recognized as revenue when the customer redeems the points or when they expire, matching revenue to the moment the obligation is actually met.
For an enterprise operator, ASC 606 turns loyalty design decisions into reporting consequences. How points are valued, how breakage is estimated, and how obligations are defined all affect the timing of recognized revenue. Loyalty and finance teams work from the same transaction-level data so that the accounting reflects real member activity and can withstand audit scrutiny.
