What is partner settlement?
Partner settlement is the financial back-end of a loyalty ecosystem. In a single-brand program, points are an internal liability and no money changes hands between parties, because there is only one party. In an ecosystem, the partners are separate businesses. When a member earns at a grocer and redeems at a fuel retailer, value has moved between two companies, and that movement has to be settled in cash.
Settlement is invisible to the member, who sees one balance that works everywhere. It is decisive for the partners, because it is the mechanism by which they get paid for the currency they issue and honor. A partner will not stay in an ecosystem whose settlement is slow, opaque or disputed, whatever the member experience looks like from the front.
This is why settlement is the question a buyer should ask first when evaluating a multi-brand platform, and the one that is easiest to gloss over in a demo. The member-facing features look similar across vendors. The difference that decides whether an ecosystem can actually run is whether settlement is native to the platform or bolted on afterward as a set of exported reports and spreadsheets. Retrofitting settlement onto an engine that was built for one brand is where multi-partner projects stall, because reconciliation, netting and revenue share were never part of the core data model.
Settlement is also where an ecosystem earns, not only where it clears. The same machinery that nets obligations tracks the revenue share between the operator and its partners: the margin the operator makes selling currency, the fees partners pay for access to members, the funded offers partners underwrite. A program that can settle can also monetize, because the ledger that records who owes whom is the ledger that records what the program is earning. Treating settlement as a back-office cost to minimize misses that it is the mechanism by which a loyalty program becomes a business with its own revenue lines rather than a cost center attached to a marketing budget.
The rest of this guide is the machinery: the obligation each transaction creates, how those obligations are netted and reconciled, and what changes when the ecosystem spans currencies and scale.
What obligation does each earn and burn create?
Every cross-partner transaction creates a financial obligation, and it runs in one of two directions.
On earn, the partner buys currency. When a member earns points at a partner, that partner pays the operator for the points issued. It is purchasing the loyalty currency, because it is handing its customer something of value that the operator will ultimately have to honor. The earning partner owes the operator.
On redemption, the partner is owed. When a member redeems at a partner, the operator pays that partner for the value it honored on the operator's behalf. The redeeming partner has delivered a reward funded by the program, so the operator owes the partner.
Each transaction is recorded with two attributes that settlement runs on: the rate and the direction. The direction is which way the obligation flows. The rate is the commercial term that sets the amount, and rates are not a single number across the ecosystem. They differ by partner, by category and by campaign. An anchor partner that drives high frequency may issue points at one negotiated rate and honor redemptions at another, and both are positions the platform has to enforce exactly, transaction by transaction.
Because the obligation is created at the moment of each earn and each burn, the ledger grows continuously. Settlement does not reconstruct these obligations after the fact from summary totals. It records each one as it happens, at the rate and direction that applied, which is the only basis on which the netting in the next step can be trusted.
How are obligations netted and reconciled?
The operator keeps the authoritative ledger. It records every transaction with each partner, the rate and the direction, and it is the single source both sides settle against. Over a settlement cycle, the many obligations between each pair of parties are netted into one balance: everything a partner owes for currency it issued, set against everything it is owed for redemptions it honored, resolved to a single figure to be paid or received.
Netting is what makes settlement tractable. Without it, thousands of individual obligations between an operator and a partner would each need to be cleared separately. With it, a cycle produces one statement per partner showing the transactions, the rates applied, the direction of each, and the net position.
Reconciliation is the harder half. Each partner checks the operator's statement against its own records, and the two have to agree. Disputes over a rate, a miscounted transaction or a timing difference have to resolve against an authoritative ledger, which is why the operator's record must be complete and traceable to the individual transaction. A settlement process that cannot show a partner exactly which transactions produced its balance turns every discrepancy into an argument. One that can show them turns reconciliation into a check rather than a negotiation.
The authoritative ledger is also the audit trail. Because settlement moves real money between companies, each side's finance and audit functions have to trace any settled balance back to the individual transactions that produced it, at the rate and direction recorded. A settlement process built on summary totals cannot do this, so a dispute becomes an exercise in reconstructing history from incomplete records. A process built on a complete transaction-level ledger turns the same dispute into a lookup, which is the difference between partners that trust the numbers and partners that audit every cycle by hand.
The scale this runs at is real. Global Hotel Alliance unites 40+ brands, with Discovery Dollars earned and settled across the ecosystem, which means every stay that earns or redeems across those brands is an obligation the ledger records, nets and reconciles.
How does settlement work across countries and scale?
Run an ecosystem across borders and the ledger takes on two more jobs. It has to convert between currencies, because a member may earn in one country and redeem in another, and the settlement between partners has to resolve in the right currency at a defensible rate. And it has to apply the correct tax treatment per jurisdiction, because the sale of loyalty currency and the funding of redemptions are taxable events that differ by country. A single-country settlement engine does neither, which is why cross-border ecosystems expose platforms that were never built for them.
Scale is the other pressure. An ecosystem with thousands of partners and millions of members generates a transaction volume that settlement has to process on a schedule partners can plan around. Statement runs, year-end processing and periodic reconciliations are heavy batch jobs, and the time they take determines whether partners are paid on time and whether members see their balances update when they expect to.
Processing throughput at this scale is a concrete engineering property, not an abstraction. WestJet's year-end tier rollover, a heavy periodic batch job of exactly the kind settlement and program processing depend on, ran in 10 days on its previous Siebel system and runs in 28 hours on GRAVTY. The class of work is the same one settlement cycles impose: large, periodic, all-at-once processing where the completion time is the difference between a program that keeps its schedule and one that misses it.
The lesson for an ecosystem operator is that settlement is a throughput problem as much as a logic problem. The rules can be correct and the program still fail its partners if the processing cannot finish inside the window the business runs on.
How does GRAVTY settle across an ecosystem?
GRAVTY®, Loyalty Juggernaut's platform, treats settlement as a platform primitive rather than an integration project. Partner onboarding, earn and burn and exchange across partners, settlement, reconciliation and revenue share are built into the core data model, which is the property that lets an ecosystem scale past the point where bolted-on settlement breaks.
The production evidence is in the numbers. Deutsche Telekom runs one program on GRAVTY with 4,000 partners across 9 countries, which means settlement across thousands of commercial relationships, multiple currencies and multiple tax jurisdictions running as normal operation. Global Hotel Alliance settles Discovery Dollars across 40+ brands, with every cross-brand earn and redemption recorded, netted and reconciled through the platform.
What this looks like operationally is per-partner commercial terms enforced transaction by transaction, obligations netted per settlement cycle, statements each partner can reconcile against its own records, and revenue share handled natively rather than in an external spreadsheet. The program runs on infrastructure with a 99.99% uptime SLA, so the ledger that every settlement depends on stays complete and available.
The point is not that GRAVTY settles. Any platform can produce a report. The point is that the partner machinery which causes most multi-brand projects to stall, the reconciliation, the netting, the multi-currency clearing and the revenue share, is the part GRAVTY ships as standard rather than the part a program has to build itself after signing.
