Picture a retailer with stores in Dubai and Riyadh and a shared loyalty app. A shopper earns points online, spends some in a store and returns one item through customer service. The app shows one balance, the cashier sees another and the service agent adds goodwill points to end the conversation. Loyalty points reconciliation begins where those apparently small corrections stop being explainable.
The executive question is not whether the programme can issue rewards. It is whether the business can explain what a customer is entitled to use after every transaction. Campaigns amplify any disagreement. More enrolments and bonus-point weekends make an unreliable balance more visible, not more valuable.
I would establish the movement ledger before expanding the programme. Marketing owns the offer, operations owns execution and finance needs a reliable view of obligations and activity. None of those teams should be able to repair a disagreement by silently replacing the balance with a number that feels reasonable.
Loyalty points reconciliation needs explicit states
Separate pending points from available points. Separate points reserved for an unfinished checkout from points already spent. Track expired, reversed and manually adjusted movements. Tier-qualifying activity may follow different rules from spendable rewards. One number labelled points cannot carry every meaning without creating hidden exceptions.
Microsoft's Commerce loyalty documentation distinguishes earning and redemption rules, participating channels, vesting periods and return handling. It also describes batch posting for offline earning. Those are product-specific behaviours, but they expose the operating questions every retailer must answer: when is a reward usable, and what happens when the sale changes?
Write the rules for each programme and market. Record eligible products, earning basis, redemption restrictions, effective dates and treatment of returns. Keep AED and SAR transactions identifiable rather than allowing an undocumented currency conversion to decide rewards. Agree whether a regional account can spend across entities; the app's shared login does not make that commercial policy automatic.
Reconcile movements, not screenshots
Choose one authoritative reward ledger. Each movement needs a unique event reference, customer or card identifier, programme, point type, quantity, source transaction, market, event time and rule version. A correction must reference the movement it corrects. Preserve original events so another reviewer can reconstruct the balance.
For available points, the basic bridge is opening balance plus newly available earnings and restored redemptions, minus completed redemptions, earning reversals and applicable expiry, plus approved adjustments. Account for transfers separately on both sides. Pending and reserved states need their own bridges, so movement between states cannot look like a new reward.
Reconcile at customer and event level before trusting the regional total. Two wrong accounts can offset each other. A duplicated award and a missing award may leave the headline number unchanged while both shoppers receive the wrong promise. Compare the ledger with commerce orders, return records and channel receipts using durable identifiers.
The adjacent note on customer identity resolution matters here. Merging two profiles can move reward ownership. Require evidence for the merge, preserve its history and provide a controlled reversal route. A matching phone number should not silently transfer spendable value between customers.
Make the return policy executable
A return changes more than sales. It may reverse points earned, restore points spent or change tier qualification. A partial return requires line-level allocation. A later exchange can create another earning event. Define these cases before the support team encounters them during a busy weekend.
Consider an illustrative test: a customer earns points on two items, spends the reward on a later purchase and then returns one original item. Decide how the programme handles the earned points that have already been used. Possible policies involve a negative reward balance or a defined recovery process, but the retailer must approve the approach and customer terms. The integration should not improvise one.
Keep rewards, promotional discounts and refund credit distinct. Shopify's store-credit documentation shows a concrete hazard: a later refund to the original payment method does not itself reverse previously issued store credit. That is not a universal loyalty rule. It is a reason to test the complete value movement in your chosen platform rather than assuming every refund automatically undoes every benefit.
Put time beside the balance
A reward can be correct in the ledger and unavailable in a channel that has not synchronised. Show the last successful update and the expected posting delay. Give staff a clear explanation for pending rewards. Never encourage a cashier to issue replacement points simply because an offline transaction has not reached headquarters yet.
Expiry needs its own rule version and point cohort. Microsoft's reward-point setup documentation allows expiry in days, months or years and a setting for points that never expire. The available configuration does not establish which policy is appropriate. Confirm the customer terms and applicable requirements before enabling a destructive expiry job.
State the timezone and cutoff. Test a purchase near midnight, a redemption reservation crossing the cutoff and a delayed offline earning event. Establish what happens when a restored reward originally had an expiry date that has passed. A nightly batch should execute an agreed decision, not create the decision because the database needs an answer.
Test concurrency and correction authority
Two channels must not spend the same available reward at once. Reserve points when appropriate, complete the reservation only after the sale succeeds and release it after failure or timeout. Retried messages must not issue a second award or repeat a reversal. Keep failed and uncertain transactions in an owned queue rather than hiding them through balance edits.
Limit manual adjustments by role, reason and amount. Require a source case and reviewer for material corrections. Inspect patterns by store, employee and integration. The purpose is not to punish customer-service discretion; it is to distinguish legitimate recovery from an exception that repeatedly conceals a broken return or synchronisation path.
Start a pilot with a normal sale, partial return, mixed payment, offline purchase, expired reward, account merge and simultaneous redemption attempt. For each, require agreement between the customer display, the transaction ledger and the store receipt. Review unresolved differences daily with one programme owner who can change the underlying rule.
This belongs inside business automation once the policy is explicit. Measure unexplained movements, aged reservations, correction volume and time to resolve, alongside commercial programme results. Loyalty points reconciliation earns its place when the retailer can explain one shopper's balance without a favour from the person who built the integration. Do not launch the next bonus campaign until that ordinary promise survives a return.