Three conclusions from this guide
- A points balance is a liability on the balance sheet. A partner-funded offer is a receivable. A cross-brand basket is several sets of books. The loyalty platform is where those records originate.
- Balances are not enough. Finance needs lineage: for every point, the rule, currency, brand, partner and expiry that came with it.
- If the platform cannot export transaction-level records that reproduce the liability rollforward, the number in the accounts is an estimate.
Why loyalty is a ledger before it is a marketing program
Every outstanding point is money the brand already owes. When a member earns at a pump, a front desk or a checkout, the program creates an obligation; when they redeem, it consumes one; when points expire, the obligation is released. Enterprise loyalty is financial infrastructure: it holds member balances, partner obligations and a liability the CFO signs off on. That is why the record behind the balance matters as much as the balance.
What the ledger must record for every point
| Field on every accrual | Why it matters |
|---|---|
| Originating rule or promotion | Answers "why did this member earn this", and lets a rule audit compare live behaviour with documented terms |
| Currency and sub-balance | Points, credits, vouchers and comp dollars are different obligations with different rules; they must not be netted |
| Brand and location | Each brand's ledger carries its own liability; mixed baskets resolve at the line item |
| Funding party | Who owes the cost of the reward: the brand, a vendor, a partner or a card issuer |
| Qualifying or non-qualifying | Whether the activity counts toward tier status as well as balance |
| Timestamp and expiry date | Expiry and breakage are computed from the lot, not estimated from the total |
| Reversal linkage | A cancelled transaction unwinds the points, the tier effect and the funded discount that came with it |
The liability rollforward
Finance reconciles loyalty with one identity:
Outstanding liability = Prior liability + Earned − Redeemed − Expired (± Adjustments)Each term is a sum of ledger entries over the period, valued at the program's cost per point. With point-level lineage, each term can be reproduced from exported records by brand, partner and currency. Without it, the platform reports a total and finance books an estimate, with breakage assumed rather than observed.
Burn order and attribution
When a member redeems, the platform has to decide which accruals are consumed first. First-in-first-out is the common default; tagged burn order lets a program consume a specific source first, such as vendor-funded points before brand-funded points. The choice decides who is attributed the cost of the redemption, which is why burn order is a finance decision as much as a product one, and why it must be configurable and logged.
Partner settlement and co-marketing
In coalition and co-brand programs, points arrive from partners and rewards are funded by them. The ledger has to carry partner wallets, funding allocation across parties, and billing parameters attached to rules and partners, so that settlement can be calculated from the same lineage as the member balance. Because settlement often runs weeks or months behind activity, co-marketing rules need date-relative accuracy: back-dated processing must remain correct when rates change.
Expiry, breakage and escrow
Expiry is computed per lot from the accrual date, not from the balance total. Breakage, the value of points that will never be redeemed, is then observed from expiry events rather than assumed. Some programs hold newly earned points in escrow until a qualifying condition clears; the ledger records the escrow accrual and its release as separate events so liability is recognized at the right moment.
What the audit trail must answer
- For a member
- what did they earn, from which rule, funded by whom, and what did each redemption consume?
- For a rule
- when was it created, changed, approved and published, by whom, and what did it execute?
- For a period
- can each term of the rollforward be reproduced from exported records, by brand and partner?
- For a partner
- what is owed, from which activities, at which rates, as of which dates?
How ReactorCX records it
ReactorCX maintains an extensive data model that supports enterprise-level financial accounting, including granular tracking of earn and burn activity by source, partner, location and promotion. Accrual and redemption lineage is preserved so finance teams can trace any liability or settlement back to the originating member activity. Burn allocation supports ordering rules such as FIFO and tagging that attributes redemptions to specific sources, partners, locations or promotions. Co-marketing rules support date-relative accuracy so back-dated processing remains correct when rates change. ReactorCX exports raw granular records that enterprise finance systems then journal and account for. Every liability number traces back to an originating member activity: no estimated breakage, no black-box rollups.
See Financial Integrity for the full capability set, and the glossary for definitions of sub-balance, escrow, lineage and settlement.