Reward Coin Liability Accounting: Breakage, Expiry, Caps

Reward coin liability accounting is the discipline of recording what you owe members for coins they hold but have not yet used. A rewards app hands out coins every day. Each unspent coin is a promise, and the sum of those promises sits on your books and in your cash plan whether or not your dashboard shows it. Founders who ignore this discover it as a cash shortfall in the month a campaign works.

This guide explains the kinds of coin, what the revenue standards say about points that customers earn, how breakage and expiry fit, and which caps keep the promise affordable. It is for the owner of a rewards short video app and the accountant who will keep its books. It is general information, not accounting or tax advice; your auditor decides how the rules apply to your company and country.

What is reward coin liability accounting?

A liability is an obligation to hand over value in the future. A coin in a member's wallet is such an obligation when the member can exchange it for something that costs you money: a gift to a creator that you later pay out, an ad-free perk, a discount, or cash. Accounting for it means answering three questions each month. How many coins are outstanding? What is each worth when redeemed? How many will never be redeemed?

The reason this matters beyond bookkeeping is that the liability grows without any cash leaving. Issuing coins is free on the day; paying for them comes later. A program can look profitable for months while its outstanding balance climbs, then lose money in the month redemptions catch up. The economics of the earning side are in watch to earn app economics. This guide covers the other side of that ledger.

Which kinds of coin do you hold?

Do not run one balance. Every coin should carry a type from the moment it is created, because the accounting, the store rules and the expiry options differ.

The right-hand columns are directions to discuss, not answers; the right treatment depends on your accounting framework and what you promised. The ledger split is what makes any of them possible. Our wallet keeps a coin balance per member that rises with purchases, gifts and reward credits you configure, and transaction records give finance staff what they need to match purchases, gifts and payouts with gateway reports. Keep the types in separate fields from day one.

What do the revenue standards say about earned points?

The two main revenue standards are IFRS 15 and the US ASC 606. The IFRS Foundation's page for IFRS 15 states that the standard sets the principles for reporting the nature, amount and timing of revenue and cash flows from customer contracts, and records that it replaced IFRIC 13 on customer loyalty programmes, effective for annual periods starting on or after 1 January 2018. A joint FASB and IASB staff paper from 2014 summarizes the part that matters for points.

The paper explains that an option to acquire additional goods or services, such as award credits, gives rise to a performance obligation only if it provides a material right that the customer would not receive without entering into the contract, for example a discount beyond what that class of customer usually gets. When it does, the customer in effect pays in advance for future goods or services, and the entity recognizes revenue when those are transferred or when the option expires. The transaction price is allocated between the purchased product and the option on a relative stand-alone selling price basis, and if the option's price is not directly observable it is estimated, reflecting the discount the option gives and the likelihood that it will be exercised. The paper also notes that marketing and promotional offers that exist independently of a present contract are outside this issue.

That last point is why the table above separates bonus coins from free activity coins. A coin that arrives with a purchase is part of the sale. A coin handed out for a daily check-in with no purchase tied to it is a different animal, and your auditor has to decide where it sits.

What does the official loyalty example look like in numbers?

The paper reproduces the standard's Example 52, a loyalty program, which is the clearest picture of the mechanics you will find from a standard setter. A customer earns one point per $10 spent, and each point can be redeemed for a $1 discount. In one period customers buy products worth $100,000 and earn 10,000 points. The entity expects 9,500 points to be redeemed, so it estimates a stand-alone selling price of $0.95 per point, $9,500 in total, based on the likelihood of redemption.

Four lessons carry over to a coin app. First, the unredeemed portion sits as a liability, here $8,676 at first, rather than disappearing into sales. Second, the expectation of non-redemption, 500 of 10,000 points, lowers the amount set aside, which is why your redemption data has monetary value. Third, the estimate is revisited: in period two the entity expected more points to be redeemed and the numbers moved. Fourth, revenue for the points arrives as they are used, in proportion to redemptions, and not on issue. This is an example for loyalty points sold with products; your coin types may be treated differently, so use it for the logic, not the numbers.

How do breakage and expiry fit together?

Breakage is the share of coins that never get used. Your estimate of it is the lever that lowers the liability, so it needs more care than any other number. Estimate it from your own history, by coin type and by cohort, not from a rule of thumb. A new program has no history, and a cautious estimate of low breakage is safer than a hopeful one. The IFRS Foundation text and the US codification contain specific guidance on unexercised rights; we could not open the standard text itself, which the IFRS site restricts to subscribers, so ask your auditor to confirm the paragraph that governs your case.

Expiry is a contract choice and a policy choice, and it is where store rules enter. Apple's guideline 3.1.1 bars expiry for credits and in-game currency bought via in-app purchase. That rule is about purchased value. It does not tell you what to do with free coins, but it shows how the store treats wallets, and a rule that quietly confiscates purchased value is the fastest way to a rejection or a complaint. On the earning side, Google's AdMob policy for rewards requires clear disclosure of the action and the reward before each rewarded ad, requires the publisher to deliver the promised reward, and allows non-monetary rewards only if they are redeemable inside your app and non-transferable.

The honest version of breakage is that a good share of it comes from members who left, and you do not earn it by being clever. Write your expiry and inactivity rules before issuing the first coin, show them where coins are earned, and read them again with a lawyer in each country you sell to. The store side is covered in more depth in our explainer on store billing rules.

Which caps keep the liability inside your cash?

Accounting records the promise; caps decide how large it can get. The same limits that control reward spending on the earning side control the liability on the other side.

• Issue cap per member per day and per lifetime. Limits how many coins any account can add to the pool.
• Global daily issue budget. Bounds the total new promises in a day.
• Redemption cap per member per month. Limits how much one account can cash out or spend in a period.
• Global monthly redemption pool. Sets the most you can owe in cash in a month, with a visible queue when it fills.
• Minimum balance and hold before payout. Slows the outflow and gives staff time to review suspect accounts.

Every cap must be in the terms and rules screen before the coins are earned. A cap added after the fact looks like a promise broken. In our admin panel, staff review withdrawal requests, approve or decline them from one queue and keep a logged trail of each payout, and commission rates and coin prices live in admin settings, so changing them needs no release. A global redemption pool, expiry for free coins and a budgeted reward schedule are available as tailored work and scoped with us, so the rule you write in your terms is the rule the system enforces.

What should the monthly coin ledger look like?

The single most useful report is a roll-forward by coin type: opening balance, plus coins issued, minus coins redeemed, minus coins expired, equals closing balance. Multiply the closing balance by the redemption value and you have the gross liability. The figures below are illustrative, with 100 coins worth R$1; replace them with your own.

The opening balance plus issues less redemptions and expiries gives the closing balance, and the closing value of R$34,000 is the number to compare with cash. Issues in this month were R$50,000 against redemptions of R$32,000, so the liability grew by R$14,000 even though cash paid out was R$32,000. A month where issues outrun redemptions by that margin is normal in growth. A year of it is a debt to your members.

Add two more lines for control: redemption rate (redeemed divided by issued, by monthly cohort) and the age of the oldest outstanding coins. Falling redemption can mean breakage is rising, which is good for the books, or that members have lost interest, which is not. The reading needs the engagement numbers beside it.

When does the program sink the business?

Run one stress test before launch. Take closing outstanding coins and ask what happens if a large share of them redeem in one month, for example after a promotion, a viral week, or a change that makes redemption easier. Compare that cash call with your reserve and your monthly contribution.

If the stress row exceeds what you can fund, the redemption pool cap, the issue budget or the redemption value must change, preferably before launch and by rule. The signs that the program is already in trouble are plain: the liability grows faster than active users, cash reserved for redemptions is borrowed for other costs, and payout requests wait longer each month. The fraud side adds to this, since farmed accounts collect coins they never intend to spend on gifts. The controls are described in referral rewards without fake accounts, and the market-specific rules for Brazil are discussed in our Brazil market guide. For a view of how coins, gifts and creator earnings move, see how a coin economy works.

How do you close the coin books each month?

A repeatable close turns the ideas above into a habit. The steps below suit a small team with one finance person and an outside accountant. They assume the ledger keeps each coin type separate.

1. Freeze the period. Export wallet transactions up to the last second of the month, in one time zone that you always use. Late entries after the export go into next month with a note.
2. Roll the balances. For each coin type, compute opening plus issued less redeemed less expired and compare it with the closing balance in the wallet system. A difference means a missing transaction type or a bug.
3. Match cash. Tie purchased-coin sales to gateway and store payout reports, net of fees and refunds. Tie withdrawals paid to bank or wallet statements.
4. Value the balances. Multiply closing coins by the redemption value you published. For purchased coins, use the price paid; for free coins, use the method your accountant has agreed.
5. Update the estimates. Rerun the redemption and breakage estimate with the newest cohort data, and record the change and the reason.
6. Write the memo. One page: balances by type, the change from last month, any rule changes, any exceptions, and the stress-test result.

Keep the memo and the exports together, with the date the close was signed off. When an auditor asks how a number was produced, the answer should take minutes to find.

Refunds, reversals and fraud clawbacks

Three events reduce balances without a normal redemption, and each needs its own ledger line. A refund on a coin bundle should remove the purchased coins it paid for, or, if they were already spent, create a receivable from the member or a documented write-off. A reversed reward, for example when a referral is later judged fake, should take the free coins back and record the reason. A fraud clawback after an account is closed should show who approved it and which rule the account broke. If these events are lumped into a single adjustments line, you will not be able to tell honest corrections from leakage.

Check the terms before you reverse anything. A rule that lets you remove coins for abuse must exist before the abuse occurs, and members should be able to read it. Removing coins on the strength of a rule written afterward is the kind of act that turns a quiet dispute into a public one.

Gifts between members and creator earnings

When a fan spends coins on a gift, the coins leave the fan's balance and a creator earning appears, usually net of your commission. Two liabilities are then in play: the fan's unspent coins and the creator's unpaid earnings. Keep the second in its own account with its own roll-forward, because it behaves like money owed rather than like a promotion. The commission you keep is the point at which your revenue can be recognized, subject to your accountant's view of whether you act as principal or as agent in the gift. Ask that question early; the answer changes how sales are presented and which tax applies.

Payout timing then sets a second cash call. If creators can withdraw weekly and fans can spend freely, the earnings liability can swell around events and weekends. Watch the age of unpaid earnings next to the age of unspent coins. A payout queue that runs two weeks late is a liability growing in plain sight, and creators will notice before your accountant does.

Controls that make the close trustworthy

Three small controls catch most errors. First, separate duties: the person who approves withdrawals should not be the person who reconciles the ledger. Second, lock the closed period, so edits to last month's transactions need a named approver and leave a trail. Third, set a tolerance, for example any unexplained difference above a small fixed amount or a small share of the month's issues, and treat anything above it as a stop, not a note for later. Review the tolerance when volume grows, because a figure that suited a few thousand coins a day will hide real problems at millions.

Questions to bring to your auditor

1. Which framework do we report under, and does it treat bonus coins as part of the sale?
2. How should free activity coins be recorded, and when is the cost recognized?
3. What evidence supports a breakage estimate for a new program?
4. Is a withdrawable balance a financial liability, and how do we present it?
5. How do store fees and refunds on coin bundles flow through the same entries?
6. What tax applies to coin sales, gifts and payouts in each country?

Put the coin types, caps and expiry rules on one page and bring that page to the meeting. The more precisely the product is defined, the less the answer depends on guesswork.

Setting up the ledger before the first coin

Create the coin types, write the rules and set the caps before any member earns anything. Agree the estimate method with your accountant, and put the monthly roll-forward on the calendar. Platform cost sits on Kwai clone development cost, and Kwai clone business model shows where coin sales, gift commission and advertising come in.

Open the live web demo to see the wallet, gifts and the withdrawal queue, and read the published price on pricing. Technical support lasts 60 days; bug fixes for 6 months are separate; updates last 12 months. Expiry rules, a redemption pool or reward budgets tailored to your plan start with a note to contact about your market, and we will reply with a scope for your Kwai clone build.