An unredeemed $50 gift card can look like easy revenue—until you need to explain where that $50 went. It may still be a customer obligation, it may eventually be reportable as unclaimed property, and its treatment can change by state. The common mistake is not choosing the wrong account; it is letting the balance disappear into sales before the facts support that conclusion.
Gift cards are useful for cash flow and customer loyalty, but they create a promise to deliver goods or services later. A sound process keeps that promise visible from the moment a card is sold through redemption, breakage analysis, and, where required, an unclaimed-property filing.
This guide explains how to build that process. It is operational guidance, not legal or tax advice: gift-card rules, accounting conclusions, and filing requirements depend on the card, the customer location, your legal entity, and state law. Use it to organize the questions for your accountant and unclaimed-property adviser.
Start With the Right Mental Model: A Gift Card Is a Liability
When a customer pays $100 for a store gift card, you have received cash but have not yet delivered the product or service. Until redemption or another valid resolution, the balance is generally a gift-card liability, often called deferred revenue or contract liability.
That distinction matters because a gift-card program has three separate questions:
- Customer terms: Can the card expire? Are fees allowed? What must you disclose?
- Financial reporting: When has enough evidence accumulated to recognize estimated non-redemption, often called breakage?
- Unclaimed property: Has the holder obligation become reportable to a state rather than income for the business?
They are related, but they are not interchangeable. A card may be old without being expired. A card may be eligible for accounting breakage without being exempt from unclaimed-property rules. And a state rule may apply even when your customer-facing terms do not allow you to cancel the card.
Federal consumer-protection rules set a floor for many retail and bank-issued gift cards: expiration generally cannot be earlier than five years, and inactivity fees are restricted and must be disclosed. State consumer laws can be more protective. Promotional cards, loyalty rewards, refunds, and network-branded prepaid cards can follow different rules, so do not assume every stored-value item belongs in one bucket.
Map the Cards You Actually Sell
Before calculating breakage or preparing a report, make a small inventory of every value-bearing product. A single retail brand may have more than it realizes:
- Physical and digital cards sold directly to customers
- E-commerce gift certificates and store credits
- Cards issued through a third-party marketplace or reseller
- Promotional, loyalty, or referral credits
- Refund credits and merchandise-return cards
- Multi-location cards where a franchisee, parent, or service provider holds the cash
For each program, document the issuer, redemption locations, original sale channel, funding source, whether cash changed hands, terms shown to the customer, and the data your point-of-sale system retains. This is not busywork. The legal holder for unclaimed-property purposes is not always the store location that accepts the card.
Separate paid value from promotional value
Suppose a customer pays $100 and receives a $20 promotional bonus. The paid amount and bonus may have different expiration, revenue, and unclaimed-property treatment. If the POS records only a $120 balance, you have made later analysis much harder.
Use separate product codes or a separate ledger field. The goal is to be able to answer, years later: how much did a customer pay, how much was a promotion, and what activity occurred on each component?
Make the Liability Reconcile Every Month
Your general ledger should not merely contain one annual gift-card adjustment. It should reconcile to a detailed balance report from your POS or card provider.
A simple monthly close routine looks like this:
- Export gift-card activity: opening balance, sales/load events, redemptions, refunds, fees if applicable, voids, and ending balance.
- Tie cash received for card sales to the payment processor or bank settlement.
- Reconcile the detailed ending balance to the gift-card liability in the general ledger.
- Investigate differences immediately—especially manual redemptions, migration adjustments, chargebacks, and cards issued after a service failure.
- Preserve the monthly report, reconciliation, and explanation of any adjustment.
Here is the core accounting flow in plain language:
| Event | Typical effect |
|---|---|
| Customer buys a $100 card | Increase cash; increase gift-card liability |
| Customer redeems $35 | Reduce gift-card liability; recognize $35 of sales revenue |
| A valid refund reverses a sale | Reduce the appropriate liability or revenue account based on the original transaction |
| A state report becomes due | Reclassify or remit according to the applicable state requirement; do not silently sweep the balance into revenue |
Keep gift-card funds distinct from sales tax collected, customer deposits, loyalty points, and merchant-processor clearing accounts. Combining them may make the balance sheet look tidy, but it prevents you from proving what an old balance represents.
Treat reconciliation breaks as operational signals
An unexplained shortage could be a fraud issue, a POS configuration problem, a location-level timing difference, or a card that was activated without a recorded payment. An unexplained excess could mean a redemption was posted to sales twice or a migration left legacy balances outside the report.
Set a documented threshold for investigation—for example, every difference, or all differences over a small dollar amount—and assign an owner. The person who can issue a manual gift card should not be the only person reviewing the reconciliation.
Breakage Is an Estimate, Not a Cleanup Button
Breakage is the portion of a prepaid balance you expect customers will not redeem. It is an accounting estimate, not a permission slip to declare all dormant cards as income.
Whether and when breakage can be recognized depends on your accounting framework and facts. A defensible estimate normally comes from a consistent historical pattern, such as cohorts of cards sold in comparable channels with comparable terms. If your program changed materially—new digital delivery, a new brand, acquisitions, major price changes, or a redesigned loyalty offer—older redemption history may no longer be a good predictor.
Avoid these shortcuts:
- "It is three years old, so it is revenue." Age alone does not establish breakage or erase potential state obligations.
- "The card has no name, so it cannot be reported." States can have special rules for anonymous cards and aggregate reporting.
- "Our card never expires, so there is no compliance issue." Some states exempt certain cards; others treat unused value as reportable after a dormancy period.
- "The POS ending balance is the liability." It is a vital input, but refunds, platform fees, settlements, and accounting estimates still need a documented reconciliation.
If you recognize breakage, retain the methodology: population definition, historical redemption data, exclusion rules, calculation, management review, and how you reconsider the estimate. If you cannot explain the estimate in a short memo, it is probably not ready for a close.
Unclaimed Property: Why State Location Matters
Unclaimed-property laws are state laws, and gift cards are not treated uniformly. The National Association of Unclaimed Property Administrators’ state-by-state directory shows a mix of exemptions, stated dormancy periods, special conditions, and different treatments for stored-value cards.
That means a five-year rule in one state is not a universal answer. The state that may have a claim can depend on the owner’s last-known address, the holder’s state of incorporation or domicile, the state where the transaction occurred, and statutory priority rules. The details are technical enough that multi-state sellers should seek specialist advice before filing.
Your job as the retailer is to preserve the evidence that lets someone apply the right rule:
- Card identifier or account identifier
- Date and amount of each load, redemption, refund, and adjustment
- Customer name and address if collected
- Sales channel and store/location information
- Terms in force when the card was issued
- Issuing legal entity and its jurisdiction
- Evidence of outreach or due diligence, if your state requires it
Do not wait until a filing deadline to reconstruct this data. A POS migration, an acquired store, or a closed location can make old balances effectively untraceable. Preserve read-only exports from retired systems and test that the card history still links to the ledger total.
Build an Annual Escheatment Calendar
Even with monthly reconciliation, unclaimed property deserves its own annual workflow. Start early enough to review old cohorts before the state’s due-diligence and report deadlines.
A workable calendar
Six to nine months before the filing date: Identify programs and legal entities in scope. Ask counsel or a specialist which states apply and whether a state-specific exemption or reduction applies.
Three to six months before: Generate the aged-card population. Validate the data against archived POS reports, remove items that were redeemed or properly refunded, and retain the exception log.
Before due diligence: Follow the applicable state’s notice process, if one is required. Do not send a generic email campaign without checking whether a statutory mailing method, timing, or content applies.
At filing: Prepare the report and remittance in the state’s required format. Retain a copy of the filing, payment confirmation, final population, and the rule applied to each exclusion.
After filing: Update the ledger, tag remitted cards so they are not reported twice, and establish a process for customer claims or reimbursements if a card is later honored.
Design Controls That Work at Store Level
The best policy fails if a cashier can create value, a manager can override a redemption, and no one can later see why. Start with practical controls:
- Require separate approval for high-value manual issues, reissues, and balance transfers.
- Limit who can alter expiration or fee settings, and log every change.
- Reconcile activation logs to payment records daily or weekly, not only at month-end.
- Restrict refunds to the original tender where possible and review exception reports.
- Assign each card program to a named finance owner and a named operational owner.
- Train customer-service staff not to promise cash conversion, extension, or reissuance that conflicts with state rules or your terms.
For a multi-location business, add a location field to every liability report. That lets you spot a store with unusual non-redemption, manual issuance, or redemption reversals before the annual compliance cycle turns it into a mystery.
A Simple Ledger Structure for Clear Audit Trails
You do not need a complicated chart of accounts, but you do need separate accounts that match the questions you will ask. A retailer might use:
Assets:Cash:OperatingAssets:Receivable:Gift-Card-ProcessorLiabilities:Gift-Cards:PaidLiabilities:Gift-Cards:PromotionalLiabilities:Unclaimed-Property:Gift-CardsIncome:Retail-SalesIncome:Gift-Card-Breakage(only when supported by your accounting policy)
Using separate liabilities makes your monthly report readable: paid cards still represent a customer obligation, promotional value is tracked separately, and balances remitted or awaiting remittance to a state do not vanish into revenue. You can review those movements in a dashboard such as Fava and keep the policy memo, exports, and reconciliations alongside the entries.
Keep Your Financial Management Organized
Gift-card obligations are easier to manage when every load, redemption, and aging adjustment has a transparent record. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready, so your financial history stays understandable as your retail program grows.