Gift card breakage under ASC 606 and IFRS 15: proportional vs remote
A retailer that sells a gift card receives cash for goods it has not yet delivered, so the full amount is recorded as a contract liability. Some of those balances are never redeemed. That unredeemed portion is called breakage, and both ASC 606 Revenue from Contracts with Customers and IFRS 15 Revenue from Contracts with Customers answer the same question about it: when does the seller stop carrying the balance as a liability and recognize it as revenue.
The answer under both frameworks depends on one estimate. If the entity expects to be entitled to a breakage amount, it recognizes that expected breakage as revenue in proportion to the pattern of rights the customers actually exercise. If it does not expect to be entitled to breakage, or cannot estimate it reliably, it waits and recognizes the residual balance only when the likelihood of the customer exercising its remaining rights becomes remote. Under US GAAP the guidance sits in ASC 606-10-55-46 through 55-49; under IFRS it sits in paragraphs B44 to B47 of IFRS 15.
A third rule overrides both methods. Any part of an unredeemed balance that the entity must hand over to another party, typically a state under unclaimed property (escheat) laws, never becomes revenue. It stays a liability until it is remitted, which makes the jurisdiction mix of a gift card program a direct input to the revenue number.
··········
WHEN GIFT CARD BREAKAGE ARISES.
Breakage arises whenever a customer pays in advance for a right to future goods or services and some of that right goes unused. Gift cards are the familiar case, but the same logic applies to prepaid service packages, nonrefundable vouchers, prepaid phone minutes and similar prepayments. The accounting starts at sale: the entity debits cash and credits a contract liability for the full amount received, because no performance obligation has yet been satisfied.
Revenue is then recognized as the customer redeems the card and the entity transfers goods or services. The breakage question concerns only the portion that history suggests will never be redeemed. Recording that portion too early overstates revenue and understates liabilities; recording it too late, often years after sale, leaves a liability on the balance sheet that the entity does not expect to settle.
The breakage estimate is usually built from the entity's own redemption history for similar cards, grouped by issue period, denomination or channel. A program with years of stable redemption data can support a reliable estimate; a new program, a new market or a recent change in card terms often cannot.
··········
HOW ASC 606 RECOGNIZES BREAKAGE.
Under ASC 606, a nonrefundable prepayment gives the customer a right to receive goods or services in the future and obliges the entity to stand ready to transfer them. The entity recognizes a contract liability for the prepayment and recognizes revenue when it transfers the goods or services. For the unexercised portion, ASC 606-10-55-46 through 55-49 set out the two methods described above.
The proportional method applies when the entity expects to be entitled to breakage. The expected breakage is spread over the redemption pattern: if customers have redeemed half of the balances expected to be redeemed, half of the expected breakage is recognized. The estimate is subject to the same constraint that applies to variable consideration under ASC 606, so breakage is recognized only to the extent it is probable that a significant reversal of cumulative revenue will not occur when the uncertainty is resolved. In practice the constraint pushes entities with thin or volatile data toward a lower breakage rate or toward the remote method.
The remote method applies when the entity does not expect to be entitled to breakage. The full unredeemed balance stays in the contract liability until the likelihood of redemption becomes remote, for example after a period of inactivity that history shows is rarely followed by redemption.
US GAAP also covers prepaid stored-value products that fall outside ASC 606. ASU 2016-04 added ASC 405-20-40-3 and 40-4 for financial liabilities arising from products such as network-branded prepaid gift cards, prepaid telecommunication cards and traveler's checks. For those liabilities, the issuer derecognizes expected breakage in proportion to the pattern of rights expected to be exercised, to the extent it is probable that a significant reversal will not subsequently occur, or derecognizes the balance when redemption becomes remote. The ASU excludes products redeemable only for cash, products attached to a segregated bank account such as a customer depository account, customer loyalty programs, and portions of breakage that must be remitted under unclaimed property laws.
··········
HOW IFRS 15 RECOGNIZES BREAKAGE.
IFRS 15 follows the same structure in paragraphs B44 to B47. A prepayment is a contract liability. If the entity expects to be entitled to a breakage amount, it recognizes that amount as revenue in proportion to the pattern of rights exercised by the customer. If it does not expect to be entitled to breakage, it recognizes the residual as revenue when the likelihood of the customer exercising its remaining rights becomes remote.
The difference lies in the threshold that governs the estimate. IFRS 15 applies its variable consideration constraint, which allows an amount in the transaction price only to the extent that it is highly probable that a significant reversal will not occur. "Highly probable" under IFRS is generally read as a higher threshold than "probable" under US GAAP, although in most gift card programs with long redemption histories the two thresholds lead to the same estimate.
IFRS has no equivalent of ASU 2016-04. A card issued by a retailer for its own goods is within IFRS 15. A card that represents a financial liability of the issuer, such as a card redeemable at unrelated merchants, falls under IFRS 9 Financial Instruments, where a financial liability is derecognized when the obligation is discharged, cancelled or expires. Issuers of such cards need a separate analysis under IFRS, and the result can differ from the US GAAP treatment of the same product.
Under both frameworks, amounts that must be remitted to a government or another party on behalf of the customer are recorded as a liability and are excluded from breakage revenue.
··········
BREAKAGE: ASC 606 VS IFRS 15 COMPARISON.
........
Issue | ASC 606 / US GAAP | IFRS 15 / IFRS |
Initial recognition | Contract liability for full prepayment | Contract liability for full prepayment |
Expected breakage | Proportional to redemption pattern | Proportional to redemption pattern |
No expected breakage | Recognize when redemption is remote | Recognize when redemption is remote |
Estimate threshold | Probable no significant reversal | Highly probable no significant reversal |
Escheat amounts | Liability, never revenue | Liability, never revenue |
Third-party stored-value cards | ASC 405-20 (ASU 2016-04) | IFRS 9 derecognition rules |
Change in estimate | Cumulative catch-up | Cumulative catch-up |
........
Readers who want the contract liability mechanics in more depth can see how deferred revenue and contract liabilities are treated under IFRS 15 and ASC 606, and how the constraint works in variable consideration under IFRS 15 and ASC 606.
··········
[[ADPLUS_300x250_1]]
GIFT CARD BREAKAGE WORKED EXAMPLE WITH JOURNAL ENTRIES.
The figures are illustrative. A retailer sells $500,000 of its own gift cards in Year 1. The cards can be redeemed only for the retailer's goods, no unclaimed property remittance applies in the relevant jurisdictions, and the retailer's redemption history supports an expected breakage rate of 8%. Expected breakage is therefore $40,000 and expected redemptions are $460,000.
During Year 1 customers redeem $230,000, which is 50% of expected redemptions, so 50% of expected breakage, $20,000, is recognized. At the end of Year 1 the contract liability is $250,000.
During Year 2 customers redeem a further $184,000, bringing cumulative redemptions to $414,000. At the end of Year 2 updated data show that the breakage rate is 10%, so expected breakage rises to $50,000 and expected redemptions fall to $450,000. Cumulative redemptions now represent 92% of expected redemptions, so cumulative breakage is $46,000. Because $20,000 was recognized in Year 1, Year 2 breakage revenue is $26,000. Without the revised estimate, Year 2 breakage would have been $16,000, so the change in estimate adds a $10,000 cumulative catch-up.
In Year 3 customers redeem the remaining $36,000 of expected redemptions and the last $4,000 of expected breakage is recognized, which brings the liability to zero. Total revenue across the three years equals the $500,000 of cash received.
........
Year | Redemptions | Breakage revenue | Liability at year-end |
Year 1 | $230,000 | $20,000 | $250,000 |
Year 2 | $184,000 | $26,000 | $40,000 |
Year 3 | $36,000 | $4,000 | $0 |
Total | $450,000 | $50,000 | n/a |
........
The journal entries follow from the schedule. Each entry balances.
........
Entry | Account | Debit | Credit |
Year 1 sale of cards | Cash | $500,000 | |
Year 1 sale of cards | Contract liability (gift cards) | $500,000 | |
Year 1 redemptions | Contract liability (gift cards) | $230,000 | |
Year 1 redemptions | Revenue | $230,000 | |
Year 1 breakage | Contract liability (gift cards) | $20,000 | |
Year 1 breakage | Revenue (breakage) | $20,000 | |
Year 2 redemptions | Contract liability (gift cards) | $184,000 | |
Year 2 redemptions | Revenue | $184,000 | |
Year 2 breakage incl. catch-up | Contract liability (gift cards) | $26,000 | |
Year 2 breakage incl. catch-up | Revenue (breakage) | $26,000 | |
Year 3 redemptions | Contract liability (gift cards) | $36,000 | |
Year 3 redemptions | Revenue | $36,000 | |
Year 3 breakage | Contract liability (gift cards) | $4,000 | |
Year 3 breakage | Revenue (breakage) | $4,000 |
........
The same retailer launches a new card program in a market where it has no redemption history and concludes it cannot make a reliable estimate. It sells $100,000 of cards and customers redeem $95,000. Under the remote method the $5,000 residual stays in the contract liability until redemption becomes remote, and only then does the retailer debit the contract liability and credit breakage revenue for $5,000. If a state required that $5,000 to be remitted as unclaimed property, the entry would instead debit the contract liability and credit an unclaimed property payable, and no revenue would be recognized.
··········
PRESENTATION AND DISCLOSURE OF BREAKAGE.
Breakage on an entity's own gift cards is revenue under ASC 606 and IFRS 15 and is presented with revenue from redemptions. The unredeemed balance is a contract liability; entities that expect a portion of it to be redeemed within twelve months split it between current and noncurrent where a classified balance sheet is presented.
Both standards require disclosure of opening and closing contract liability balances and of revenue recognized in the period that was included in the opening contract liability, which captures redemptions and breakage together. Significant judgments, including the method used to estimate breakage and the data behind the rate, are part of the required judgment disclosures. For stored-value products within ASC 405-20, ASC 405-20-50-2 separately requires disclosure of the breakage methodology and the significant judgments made in applying it.
Gift card programs often sit alongside loyalty points, which raise a related but distinct question about material rights; the site's analysis of customer loyalty programs under ASC 606 and of nonrefundable upfront fees and material rights covers those cases.
··········
COMMON ERRORS AND JUDGEMENT AREAS IN BREAKAGE ACCOUNTING.
The most frequent error is recognizing the full expected breakage at the date of sale. Both standards tie breakage to the redemption pattern, so day-one recognition is only correct if redemption of the remaining balance is already remote, which is rarely the case.
A second error is applying a breakage rate company-wide when unclaimed property rules differ by state. A program sold across several US states can have balances that are subject to escheat in some states and not in others, so the breakage pool must exclude amounts that will be remitted. Changes in state law or in the card terms also require the estimate to be revisited.
A third error is treating a change in the breakage rate prospectively. Under both frameworks the cumulative revenue is recalculated with the updated estimate, so the effect of the revision is recognized in the period of change, which is how the $10,000 catch-up arises in Year 2 of the example.
The main judgement areas are the level of aggregation of historical data, the length of history needed for a reliable estimate, the effect of card features such as inactivity fees or expiry dates where they are permitted, and the point at which redemption becomes remote under the remote method.
··········
GIFT CARD BREAKAGE UNDER ASC 606 AND IFRS 15: PRACTICAL CHECKLIST.
Confirm whether the card is redeemable only for the entity's own goods and services, which places it within ASC 606 or IFRS 15, or whether it is a stored-value financial liability that falls under ASC 405-20 or IFRS 9.
Map every jurisdiction in which cards are sold to its unclaimed property rules and remove amounts subject to remittance from the breakage estimate.
Decide whether redemption history supports an estimate of expected breakage after applying the constraint, which is "probable" under US GAAP and "highly probable" under IFRS; if it does not, use the remote method and document the point at which redemption is considered remote.
Recognize expected breakage in proportion to redemptions, update the estimate at each reporting date, and record any change as a cumulative catch-up in the period of change.
Reconcile the contract liability roll-forward each period: opening balance, cards sold, redemptions, breakage, remittances and closing balance, and use it to support the revenue and contract liability disclosures.
The established position is that breakage is revenue earned through the redemption pattern, never at sale, and never on amounts owed to a state. What remains entity-specific is the estimate itself: the reliability of redemption data, the escheat profile of the program, and, for issuers of third-party cards reporting under IFRS, the separate derecognition analysis under IFRS 9.
··········
FOLLOW US FOR MORE.
·····
DATA STUDIOS
·····
datastudios.org
