How Should an Ecommerce Business Account for Gift Cards and Store Credit?

Which balances must be separated before posting anything?

This article is for an ecommerce operator selling paid gift cards, issuing promotional credit, or converting refunds into store credit. The decision is how to close the liability without overstating revenue or losing track of customer obligations. Separate at least four populations: paid gift cards, refund credits, promotional credits, and loyalty rewards. They may look identical at checkout but arise from different economic events.

This four-ledger separation is the first original-value component. It prevents a marketing coupon from being confused with customer cash held by the business.

How does the liability roll-forward work?

Maintain a subledger using unique card or credit IDs. The control equation is:

Opening gift-card and credit liability + new value issued + reinstatements - value redeemed - valid expirations or recognized breakage - administrative reversals = closing liability.

Run the equation separately for paid cards and other credit types. Tie issuance to cash receipts or the transaction that created the credit. Tie redemptions to orders. Tie expirations and reversals to a policy and approval record. The general ledger should equal the subledger closing value after every month-end close.

Revenue at redemption follows the goods or services delivered, not the face value originally sold. If a $100 card buys an $80 item and leaves $20 unused, the liability falls by $80 and the remaining $20 stays open. Sales tax or VAT timing varies by jurisdiction and product mix, so the accounting ledger should preserve location, redemption date, and product tax category rather than guessing at issuance.

Which exception should be investigated first?

Use an exception decision tree. If the general ledger differs from the platform liability report, first test duplicate imports and cutoff dates. If card value is negative, look for refunds posted as new redemptions or manual adjustments applied twice. If issued value has no cash or source order, classify whether it is promotional, customer-service, fraud, or migration activity. If old balances are growing, confirm whether cards are genuinely outstanding, migrated from a prior platform, legally subject to unclaimed-property rules, or operationally unusable.

Assign risk. High risk includes unsupported manual reductions, bulk expiration, missing customer obligation records, or revenue booked at issuance and again at redemption. Medium risk includes stale but identifiable balances and timing differences. Low risk includes next-day settlement cutoff differences with complete IDs. This exception tree is the second original-value component.

Worked hypothetical example: paid cards, refunds and partial redemption

Hypothetical example—not a customer result. Assume a skincare store begins June with a $18,000 paid-card liability and $4,000 refund-credit liability. It sells $12,500 of new paid cards for cash, issues $3,200 of store credit for returned orders, records $10,600 of paid-card redemptions, records $2,700 of refund-credit redemptions, reinstates $400 after a cancelled redemption, and has $150 of documented administrative reversals caused by duplicate migration records. It recognizes no breakage.

The store records $12,500 of cash with a liability when the cards are sold. It recognizes revenue for goods delivered on the $10,600 redemption, subject to its ordinary revenue and return policy. Interpretation: cash increased before revenue, while the closing $24,650 remains an obligation. Limits: the example excludes loyalty rewards, escheatment, taxes, multi-currency cards and any proportional breakage estimate.

What controls should the monthly close include?

1. Export the full gift-card and store-credit activity ledger, not only the outstanding balance.
2. Deduplicate on card/credit ID plus event ID.
3. Map each issuance to cash, a refunded order, a promotion approval or loyalty event.
4. Map each redemption to an order and product-tax category.
5. Run the liability roll-forward by population and currency.
6. Tie the subledger closing amount to the general ledger.
7. Age old balances and document legal, accounting and operational status.
8. Review manual adjustments independently.

Common failure modes are recording paid cards as revenue immediately, reducing revenue twice when a refund becomes store credit, including promotional codes in the paid-card liability, recognizing all aged balances as income without a policy, losing balances during platform migration, and allowing customer support to adjust value without an audit trail.

Definition of done: every liability movement has a source event, the population roll-forwards equal the general ledger, manual changes are approved, redemption revenue is not duplicated, and stale balances are assigned for legal/accounting review.

How should migration, fraud and customer-service adjustments be controlled?

Platform migration creates a special control problem because the old system may export only current balances, not the event history. Freeze issuance and redemption during the cutover window, extract both balance and activity files, hash or archive the raw files, and reconcile total value plus card counts before enabling the new platform. Test zero, partial, full and cancelled redemptions. Keep the old-to-new card ID mapping under restricted access.

Fraud and customer-service adjustments need different approval paths. Fraud teams may suspend value without extinguishing the liability; customer service may reinstate value after a failed order; finance may reverse a proven duplicate. Require reason codes, ticket IDs, operator identity and independent approval above a defined threshold. Review unusual clusters by operator, IP, issuance channel and redemption location. Never solve a liability variance with an unsupported bulk adjustment.

When does this guidance not apply?

Seek qualified advice for material breakage recognition, state unclaimed-property obligations, expiry restrictions, loyalty programs that create material rights, marketplace-issued cards, multi-merchant programs, and cards redeemable across legal entities. Rules differ by jurisdiction and contract. Caigeek can use platform exports, bank data and order records to produce the liability roll-forward, population mapping and exceptions; it does not replace legal advice on expiry or escheatment.

Also pause before applying this method to crypto-denominated value, cards issued by a regulated financial institution, or arrangements where a marketplace—not the merchant—is legally obligated to the holder. In those cases, the merchant may be an agent, a distributor, or merely accepting third-party tender. Contract ownership matters more than the checkout label.

Self-check before sign-off

• The first paragraph directly answers the title question.
• All calculations can be reproduced from named source data.
• The hypothetical example is labeled and not presented as a customer result.
• Timing items are separated from income and expenses.
• Every unresolved exception has an owner and next action.
• Legal, tax and professional-advice limits are visible.

Sources and last updated

Last updated: 14 August 2026. Operational references reviewed for this article:

• FASB, Revenue Recognition implementation resources
• IRS Publication 538, Accounting Periods and Methods
• Shopify Help Center, Gift cards

The latest user instruction waived live query-signal research for this run. The article therefore avoids claims about search volume and does not present its title as a measured ranking opportunity.

FAQ

Is a gift card sale revenue when the customer pays?

Usually it creates a liability because the business still owes goods or services. Revenue is generally recognized as the obligation is satisfied through redemption.

How should a partial gift card redemption be recorded?

Reduce the liability only by the value applied to the order. Keep the unused balance outstanding.

Is refund store credit the same as a paid gift card?

No. Both can be liabilities, but their source and offset differ. Track them in separate subledgers.

Can old unused gift cards simply be written to income?

Not automatically. Breakage, expiry and unclaimed-property treatment require documented legal and accounting analysis.