How to Build a Gift Card Liability Roll-Forward in QuickBooks Online

October 2, 2026

Bottom line: A gift card reconciliation should explain how the opening liability became the closing liability. It needs separate evidence for cards sold, cards redeemed, refunds or cancellations, and any approved expiration or breakage entry. The virtual assistant can collect records, rebuild the activity, and isolate differences. The owner or accountant retains decisions about revenue recognition, expiration, unclaimed property, and correcting entries.

Why the cash deposit is not the whole story

When a customer buys a gift card, cash may reach the bank before the business provides goods or services. Later, the card can be redeemed in one visit, used over several purchases, refunded under an approved policy, or remain outstanding. A payment processor may also deduct fees or combine gift card activity with ordinary card sales. Those events make the bank deposit a poor substitute for a gift card subledger.

A QuickBooks liability can drift even when the processor dashboard appears reasonable. Sales may be posted directly to income, redemptions may reduce sales without relieving the liability, or a processor import may record only the net settlement. Old cards may have been cleared without a documented policy decision. The purpose of a roll-forward is not to force the books to the processor total. It is to show each movement and the evidence behind it.

The IRS recordkeeping overview describes the need to retain supporting business records. For a gift card review, source evidence includes card issuance and redemption reports, settlement files, sales receipts, refund records, and approved accounting memos. Recordkeeping guidance supports the evidence trail; it does not decide revenue timing or state-law obligations.

Freeze the population and the cutoff

Choose a reconciliation date and export the gift card detail before making changes. Record the processor or point-of-sale system, merchant account, locations included, report names, filters, time zone, export time, and whether the report measures issued value, current balance, or transaction activity. A current-balance report alone cannot explain the period's movement.

Also export the QuickBooks general-ledger detail for the gift card liability from the day after the last trusted reconciliation through the cutoff. Preserve the opening balance, every debit and credit, transaction type, date, name, memo, and source reference. If the business uses separate liabilities by location or brand, do not combine them until each account has been tested.

Timing matters. A card purchased online at 11:58 p.m. may appear in one system date and settle at the bank on the next day. A redemption near month end may be included in the point-of-sale close but imported later. Keep transaction time, reporting date, and bank settlement date in separate fields rather than moving an item merely to make totals agree.

Construct the roll-forward

Start with the last supported closing liability. Add new value issued during the period and subtract value redeemed. Show other movements separately: customer refunds, chargebacks, promotional cards, manual balance changes, transfers between programs, and reviewer-approved expiration or breakage adjustments. The arithmetic is straightforward:

Opening supported liability + issued value - redeemed value +/- separately supported changes = expected closing liability.

Do not net issuance and redemption into one activity number. A month with 20,000 issued and 19,000 redeemed is operationally different from a month with 1,000 issued and no redemptions, even though both increase the liability by 1,000. Gross columns make import gaps and unusual activity visible.

For example, a salon begins with 8,400 of outstanding card value. Its platform shows 3,250 issued and 2,100 redeemed. One 150 customer refund restored value to a card, and a 75 manual reduction has no note. The expected balance before the unexplained change is 9,700. If the platform closing report shows 9,625, the 75 movement explains the arithmetic but not its business purpose. The packet should flag the manual change, identify its user and timestamp, and request evidence. It should not label the difference revenue.

Tie issuance and redemption to source records

Sample issuance by tracing each selected card transaction to a customer receipt, payment tender, processor activity, and settlement batch. Confirm face value and any separate activation fee rather than assuming the entire receipt is card value. Promotional cards with no customer payment should remain distinguishable from purchased cards because the reviewer may need a different policy.

For redemption, trace the card identifier, original or prior balance, sales document, amount used, and remaining balance. A redemption should connect to the actual sale rather than only to a daily summary. When the processor masks card numbers, retain a safe partial identifier or system transaction ID. Avoid exporting customer information that the review does not require.

Then compare the gross source activity with QuickBooks. Identify whether entries arrive through a sales integration, summarized journal, manual transaction, or clearing account. A daily journal may be acceptable under an approved workflow, but the roll-forward still needs to tie its totals to the underlying report. If a journal combines ordinary sales, gift card issuance, tax, tips, and redemptions, build a bridge showing each component.

Keep policy questions out of balancing entries

Old unredeemed balances often invite a convenient cleanup. Resist it. Whether an amount can expire, when expected nonredemption can be recognized, and whether unclaimed-property rules apply are legal and accounting questions. The assistant should prepare an aging by issuance period and jurisdictional facts available in the record, then route the decision to a qualified reviewer.

Use explicit statuses such as “outstanding and supported,” “redemption awaiting import,” “manual change lacks evidence,” “policy review required,” and “approved adjustment posted.” Avoid “earned,” “forfeited,” or “safe to clear” unless the authorized reviewer supplied that conclusion. Keep the policy memo or approval with the resulting entry.

The same boundary applies to processor differences. A processor total is external evidence, but it may exclude cards from a legacy program, recently migrated balances, or offline redemptions. Document the report's scope before treating it as complete. A difference can remain open without being silently plugged.

Deliver a reviewable packet

The cover sheet should state the cutoff, systems and locations included, opening balance source, expected closing balance, QuickBooks balance, and unresolved difference. Follow it with the gross roll-forward, transaction-level exception list, aging, general-ledger detail, and source-report index. Every exception needs an owner and next question.

After an entry is approved, retain the approver, date, rationale, affected period, and QuickBooks transaction link. Re-run the liability detail and confirm the posted entry matches the approval. Carry unresolved differences into the next reconciliation without changing their original age.

A recurring monthly control can track supported opening balance, gross issuance and redemption, manual changes, unmatched activity, and oldest open exception. Consistent fields make trends meaningful. A declining difference is useful only when the population and cutoff rules remain the same.

QBOAssistant can help assemble reports, tie activity, maintain the exception register, and prepare an owner-ready handoff. Learn more about QuickBooks virtual assistant services and the bookkeeping tasks a VA can prepare. To define a gift card reconciliation cadence and approval boundary, request a consultation.

Sources

• IRS: Recordkeeping
• SBA: Manage your finances