For Finance: know that the numbers are right
ReactorCX is the enterprise loyalty platform that treats a points balance as a liability, a partner-funded offer as a receivable and a cross-brand basket as three sets of books. Every accrual carries its source rule, brand, partner, timestamp and expiry. Prior liability plus earned minus redeemed minus expired equals outstanding, with no estimated breakage and no black-box rollups.
Enterprise loyalty is financial infrastructure
Most loyalty platforms are bought as marketing tools and discovered to be ledgers at the first audit. ReactorCX was built the other way round.
Liability you can defend
Outstanding points tracked and dated by brand, partner, currency and expiry bucket. Breakage flagged and recognized under your rules, not estimated.
Settlement from lineage
Partner wallets, vendor funding, escrow and date-relative billing. The settlement file and the dispute come from the same activity records.
Controls on the rules that create liability
Every rule change is versioned, approved and logged. A promotion that changes liability cannot go live without a name on it.
Per brand, per partner, per period
Bring your program rules, partners and expiry policy. We walk through liability, settlement and audit with them.
Book a financial controls reviewThe financial capabilities, by name
| Capability | What it does | Why finance cares |
|---|---|---|
| Multi-currency wallets and sub-balances | Points, comps, free play, cents-off-per-gallon and other currencies held as separate purses with their own rules. | Each currency is a distinct liability with its own valuation. |
| Qualifying and non-qualifying points | Tier-qualifying activity tracked separately from redeemable value. | Status cost and redemption liability are not confused. |
| Source attribution | Every accrual tagged with rule, brand, partner, channel, timestamp and expiry. | Attribution and partner billing are provable at line level. |
| Burn order | FIFO or tagged burn order configurable per program. | Which liability is extinguished first is a policy, not an accident. |
| Expiry and breakage lineage | Expiry events recorded per accrual; breakage recognized under your rules. | Breakage is supportable in audit. |
| Partner wallets, vendor funding, escrow | Funded value held per partner; hold or vest until conditions are met. | Receivables and settlement obligations are visible, not implied. |
| Date-relative co-marketing billing | Settlement rates applied by the date of the activity when rates change. | No retroactive disputes over which rate applied. |
| Liability reporting and reconciliation exports | Pre-built liability dashboards plus transaction-level export and SQL access to the data model. | Finance reconciles to the general ledger from primary records. |
| Audit trail | Access, configuration-change and transaction activity logged; every outcome traceable to the rule and data that produced it. | Controls over the rules that create liability. |
Full model on Financial Integrity.
A mixed basket across four brands, reconciled at the line item
Gap Inc.'s Encore program runs Old Navy, Gap, Banana Republic and Athleta as one membership. A basket spanning several brands splits earning to the right brand, so each brand keeps clean economics while the shopper sees one program. The migration reconciled the historical transaction records before cutover.
How this is measured
Historical transaction records migrated and reconciled for Gap Inc. Encore. As of February 2026.
How this is measured
Historical transaction records loaded into ReactorCX and reconciled against legacy outputs during SafeSwitch migrations. As of 2026-Q3.
What to request before approval
| You want | Where | How |
|---|---|---|
| How liability is calculated and reported | Financial Integrity | Public |
| Sample liability and reconciliation reports, redacted | Financial Controls Review | Session, produces documents you can circulate |
| Controls on configuration changes | Architecture and Extensibility | Public |
| Reconciliation evidence from a migration | Safe Migration · See a Parallel Migration | Public summary; redacted report on request |
| SOC 2 Type II (controls, not only security) | Trust Center · Request Security Pack | Report via request |
| Commercial model, indexation, exit terms, data ownership, audit rights | Contact | Through your account team |
Questions finance leaders ask
Can ReactorCX report points liability by brand, partner and expiry bucket, and reconcile to the general ledger?
Yes. Every accrual carries its source rule, currency, brand, partner, timestamp and expiry, so liability can be reported and filtered on any of those dimensions. Transaction-level records export for journaling, and the identity prior liability plus earned minus redeemed minus expired equals outstanding holds per brand and per partner.
Who funds what when a partner issues points, and how is it settled?
Funding source is tagged on every earn and burn. Partner wallets hold funded value, settlement and partner billing allocate funding and reimbursement with date-relative accuracy when rates change, and the same lineage supports the settlement file and the dispute.
If we migrate, how do we know balances are correct on day one?
SafeSwitch reconciles balances, tiers and historical transactions between the legacy platform and ReactorCX across the full member base before cutover, and the reconciliation reports are part of the go or no-go decision. The legacy system stays live until you confirm.
Review the controls with your own program rules.
The Financial Controls Review covers liability, settlement, audit and reconciliation using your currencies, partners and expiry policy, and leaves you with sample reports.