
Breakage Is an Estimate About Human Behaviour
Cards sold years ago sit as a liability that only shrinks when somebody redeems or when finance makes an estimate nobody enjoys defending.
- The liability is easy to record and difficult to release, because releasing it depends on predicting behaviour.
- Redemption follows a curve: heavy in the first months, then a long tail that never quite reaches zero.
- Breakage estimates built on an industry percentage rather than your own redemption history are hard to defend.
- Some jurisdictions treat unredeemed balances as unclaimed property, which changes the answer entirely.
- ChatFin tracks cohorts against actual redemption, reconciles to the processor, and drafts the estimate with its evidence.
A gift card is cash today and an obligation for as long as it stays unredeemed. Most of the accounting is simple until the point where you want the balance to stop growing.
Breakage, the portion that will never be redeemed, is real and recognisable in many circumstances. It is also an estimate about consumer behaviour, made by finance, against income, which is a combination that gets examined closely.
This page covers how redemption actually behaves, why cohorts matter more than a blanket percentage, and how a governed agent can build the evidence a breakage estimate needs.

Redemption is a curve, not a rate
Most redemption happens quickly, often within the first few months of issue. After that the rate falls sharply and settles into a long tail that continues for years at low volume.
A single percentage applied to the whole balance ignores that shape, which means it is wrong for recently issued cards and wrong in the other direction for old ones.
The escheatment question comes first
In several jurisdictions unredeemed balances are unclaimed property and must be reported rather than recognised as income. In others breakage may be recognised in proportion to redemption.
That determination governs everything else, and it depends on where the card was sold and what the programme terms say.
Getting the sequence right matters. Recognising breakage on balances that are legally reportable creates an exposure that is hard to unwind once several years have passed.

Issued at the till, tracked by a processor
Cards are sold and redeemed in the point of sale system and balances are held by a card processor, while the liability sits in the ledger as a single number. Reconciling the three at cohort level is the work, and it rarely happens outside year end.
What the agent needs to see
Ledger detail from the ERP, plus card issuance and redemption records taken from the source they arrive in, read through the API surface your ERP already exposes rather than the database.
What it should be allowed to do
Prepare a breakage entry and a liability schedule by cohort and leave it for the controller to approve. Reading widely and writing narrowly is the line that keeps this safe.
That division matters more than which model sits underneath. An agent that can read card issuance and redemption records, programme terms and expiry rules and prior breakage analyses while posting only through the validated path a person uses gives you the coverage without handing over the ledger, and ChatFin works that way on every ERP it connects to.
Reconciling to the processor
The processor holds the authoritative card balances and the ledger holds a liability that was built from transaction feeds. They drift, usually through failed transactions, adjustments and manually issued cards.
Tying them each period keeps the liability real and gives the breakage estimate a base that somebody can verify.
It also surfaces operational issues, such as cards issued outside the normal process, which are worth knowing about for reasons beyond accounting.

What the analysis gives the business
The same cohort data answers commercial questions that marketing usually cannot: how quickly cards are redeemed, how much incremental spend they generate, and whether digital cards behave differently from physical ones.
That is a better return on the work than a single liability figure, and it comes from the same reconciliation.
A defensible estimate
Breakage supported by your own redemption curves, reconciled to processor balances by cohort.
Programme insight
Redemption speed, incremental spend and channel differences visible without a separate analysis.
Breakage is an estimate, and it stays one
Recognising breakage takes income into the accounts against cards that may still be redeemed, and escheatment rules in some jurisdictions restrict it entirely. ChatFin builds the redemption evidence and drafts the entry, and the estimate and its jurisdictional treatment stay with your controller and advisors.
The record kept against gift card liability is deliberately plain: the card issuance and redemption records the agent read, the reasoning it applied, the draft it produced, what the controller changed, and the moment it posted. That is the trail an auditor asks for, and it is assembled while the work happens rather than reconstructed afterwards.
The wider argument for that design sits in governed write-back and a controller's guide to reviewing AI generated entries.
A is prepared, reviewed and approved before it posts, and every step is logged from the source document to the entry. breakage entry and a liability schedule by cohort
How ChatFin tracks the liability
Cards are grouped into issuance cohorts and redemption is tracked as a curve rather than a percentage, so the pattern that supports a breakage estimate comes from your own programme. The liability schedule reconciles to the processor balance each period instead of once a year.
It connects to the ERP, the point of sale system and the card processor platform through the interfaces those systems already expose, which keeps the security review short and the setup measured in days rather than quarters.
Build issuance cohorts
Cards grouped by issue period, channel and programme with their terms attached.
Track redemption curves
Actual redemption timing and value per cohort used to establish the pattern.
Reconcile to the processor
Ledger liability tied to the processor balance with differences itemised.
Draft breakage and schedule
Entry prepared with the cohort evidence and the remaining exposure shown.
A first run is usually read only against a period you have already closed, so you can compare what the agent found against what your team found before anything is trusted with a breakage entry and a liability schedule by cohort.
Nothing here is single purpose. The connection into NetSuite, SAP Business One or Acumatica serves every other agent you switch on later.
Breakage is an estimate about human behaviour, made by finance, recognised in income. Expect it to be tested.
ChatFin
Frequently Asked Questions
Can we recognise breakage if we have never done it before?
That depends on your jurisdiction, your programme terms and your ability to support an estimate with redemption history. It is a policy decision for your controller and auditors, and the work here is building the evidence that decision needs.
How much history does a redemption curve need?
Enough to see the tail flatten, which usually means several years of issuance. Where a programme is newer, the estimate is more conservative and the curve firms up as cohorts mature.
Does it handle cards sold in multiple jurisdictions?
Cards are grouped by the jurisdiction of sale as well as by cohort, because the treatment differs. That grouping is what allows a reportable balance to be separated from one that may support breakage.
This page is general information about finance operations and software, not legal, accounting, or tax advice. Confirm treatment for your own entity with your advisors.
Track gift card liability by cohort, not by percentage.
ChatFin groups cards into issuance cohorts, tracks actual redemption behaviour, and reconciles the ledger liability to the processor balance each period.
The breakage entry is drafted with the cohort evidence attached, and the jurisdictional treatment stays with your team.
Book a DemoSee your card liability split by cohort.
Bring issuance and redemption history and the processor balance. We will show the redemption curve by cohort, the reconciliation, and the breakage evidence.