Coalition Loyalty Programs: Settle Partner Economics First

The short version: Coalition loyalty programs should not issue a point until partners have priced earning and redemption, assigned liability, defined ledger settlement, restricted data access, and funded an exit. Treat every earn, burn, refund, and reversal as a linked transaction with a named payer.

Key takeaways

• Set partner-specific earn funding and redemption reimbursement rates.
• Reconcile gross obligations before netting cash.
• Assign liability, reserves, breakage, refunds, and insolvency losses.
• Give partners only the customer fields required by an agreed data flow.
• Test fraud and wind-down rules against measurable pass criteria.

Price coalition loyalty programs earn and burn separately

A shared point does not create shared economics. A grocery partner operating on a 3–5% gross margin cannot fund rewards like a hotel selling otherwise perishable inventory. One internal point price transfers value between partners without showing who benefits.

Define two rates for each partner: the amount paid when it issues a point and the amount reimbursed when it accepts one. For illustration, an issuer might fund each point at 1.1 cents while a redeemer receives 0.9 cents. Replace those figures with rates derived from expected redemption cost, margin, breakage, tax, and administration.

Here is the settlement lifecycle. Partner A issues 1,000 points and owes the coalition $11: 1,000 × $0.011. Partner B accepts those points and earns $9: 1,000 × $0.009. The coalition records the $2 spread for the contractually stated purpose, such as operations or reserve funding.

If the original purchase is returned, create a reversal linked to the earn event. Do not delete either record. If the points have already been redeemed, Partner A still owes the funded earn unless the contract assigns that loss elsewhere; the member balance may become negative or the issuer may fund recovery. Gross obligations remain $11 due and $9 payable before the final $2 net cash movement is calculated.

Failure mechanism: a nominal one-cent value hides different wholesale rates. High-cost redeemers absorb generous issuance until redemption volume exposes the transfer. Produce a monthly partner contribution statement showing funded earn, reimbursed burn, fees, reversals, reserve movements, gross obligations, and net cash.

Assign liability and reserves before issuance

Name the legal entity obligated to satisfy outstanding balances. Issuer-level liability, a central coalition entity, or a contractual split can work. Ambiguity cannot. Finance and auditors determine accounting treatment; the contract still needs to specify cash funding and loss allocation.

Define who holds reserves, who funds redemptions when expiry assumptions change, and who receives breakage benefit. Estimate breakage by earn cohort and elapsed age rather than applying one permanent percentage. Loyalty Program Breakage: Measure It Without Fooling Yourself provides the related measurement framework.

Refund policy must match point availability. If goods have a 30-day return window, holding points as pending for 30 days is derived directly from that policy. If immediate redemption remains available, assign the loss created when a member earns 1,000 points, spends them at another partner, then returns the purchase.

Define reserve coverage as cash reserve ÷ stressed net exposure. Stressed net exposure should include forecast redemption reimbursement, unsettled accepted burns, pending reversals, partner concentration, forecast error, and enforceable recoveries. A 60-day forecast window is only an illustrative starting point; replace it with the observed redemption cycle, settlement lag, and time required to suspend a partner.

Failure mechanism: allocating breakage income to the coalition while one partner carries redemption liability separates benefit from obligation. Review reserve coverage on every settlement close and after material changes to redemption cost, expiry policy, partner mix, or credit quality. That cadence follows the production of updated exposure data, not a generic quarterly calendar.

Reconcile the ledger and test fraud rules

Every event needs a unique transaction_id, member_id, partner ID, timestamp, event type, point quantity, cash value, currency, and linked reversal ID. Daily delivery is an operating convention suited to programs offering near-real-time balances; slower programs can match delivery to their promised balance-update time. Reject duplicate IDs and malformed events deterministically.

For each partner, calculate gross_due = accepted_earn × earn_rate and gross_receivable = accepted_burn × burn_rate. Add fees and linked reversals separately, then calculate net cash. Exact point quantities must reconcile exactly; currency differences may include only documented rounding at the contracted precision.

A $5,000 net payment does not validate $120,000 due and $115,000 receivable. Reconcile both gross totals to event counts and values. Use an illustrative 15-business-day dispute window only if finance teams can close, exchange evidence, and correct the next settlement within that period.

Fraud review needs a defined population and denominator. As an illustrative pilot, rank active accounts by points earned and redeemed across different partners within 24 hours. Review the top 0.1% plus every account exceeding the contractual exposure cap, with at least 50 reviewed accounts per week where volume permits; replace 0.1% and 50 with review capacity and observed score distributions.

Track confirmed abuse, legitimate cases, total reviewed, blocked value, and customer-service cost. Do not automate blocking until the operator sets and meets an acceptable confirmed-abuse precision target based on its own loss tolerance. Rare abuse may produce no confirmed cases, so retain deterministic exposure caps even when model precision cannot yet be estimated.

Failure mechanism: net-only reconciliation conceals earn-return-burn loops, reversals, and partner concentration. Apply the six controls described in Loyalty Program Fraud Prevention: Six Minimum Controls, then contractually assign losses to the party whose system accepted the invalid event.

Restrict data and make partner exit executable

Map each purpose to explicit fields. Redemption can require a member token, available balance, requested amount, authorization result, partner ID, and timestamp. It does not require another partner’s item-level purchase history. Marketing records need controller or sender, purpose, channel, territory, consent timestamp, and withdrawal status.

Review permissions at launch, after every scope change, and on access-role changes. A fixed quarterly review is useful only as a governance convention for otherwise unchanged access; increase frequency when partner or staff turnover makes the access inventory stale. If data goes to a coalition platform or partner, identifiers, transactions, or consent records leave the collecting partner’s systems; contracts and customer notices should identify the recipient and purpose.

Failure mechanism: a shared export turns technical convenience into unauthorized prospecting. Purpose-to-field mapping exposes the problem before access is granted.

Exit terms need suspension triggers, final ledger delivery, reserve top-ups, settlement deadlines, customer communications, data deletion, and surviving audit rights. Run a yearly wind-down exercise as a governance convention, plus another after any material partner or ledger change.

Use a named scenario: the largest redemption partner becomes insolvent at noon with 60 days of forecast redemptions outstanding. Finance calculates gross exposure and reserve coverage; operations stops new earn within the contracted suspension time; engineering exports the final accepted ledger; legal triggers guarantees; customer service approves member messaging.

Pass only if point totals reconcile exactly, currency reconciles within documented rounding, access is revoked within the contracted deadline, funding covers the promised redemption window, and every customer communication has an owner and release time. Record failures, owners, and retest dates. An annual checkbox without these inputs and pass criteria proves nothing.

Frequently asked questions

How often should coalition partners settle?

Daily ledger delivery and monthly cash settlement are practical conventions for near-real-time programs. Shorten settlement when gross exposure approaches the partner’s contractual credit limit; derive the cadence from exposure growth and available security.

Should every partner use the same point value?

Use one customer-facing unit if it improves comprehension, but retain partner-specific earn funding and redemption reimbursement rates. Common presentation does not require identical wholesale economics.

Who carries the points liability?

The entity obligated to satisfy redemption should carry or fund the related obligation under the accounting treatment agreed with its auditors. The contract must align reserve funding, breakage benefit, and insolvency loss with that obligation.

What happens when a partner becomes insolvent?

Suspend new earning, secure the accepted ledger, calculate gross obligations, activate reserves or guarantees, and publish funded redemption options. Without enforceable security, remaining partners must fund continuity or narrow the customer promise.