Loyalty glossary · 8. Technology and architecture (25)
Real Time Accrual
Real time accrual is the posting of loyalty points or rewards to a member's account at the moment a qualifying activity is completed, with no batch delay or end-of-cycle wait. It requires event-driven architecture and is the default expectation for modern digital programmes, though it raises cost and control issues.
A loyalty programme that posts points overnight is now lying to its members about what real time means. The member sees the payment complete and expects the points instantly. Any delay is a broken promise. This is not a high bar; it is the baseline set by every modern consumer app. Programmes that batch their accrual are choosing to fall below that baseline.
Real time accrual is not a banner on a dashboard. It is an event-driven write to a member account on every qualifying transaction, with no intermediate queue. The systems that cannot do this were built for batch statements in the 1990s. Retrofits that fake real time by writing to a cache while the ledger lags are worse than honest batch, because they create two versions of the balance.
Work the arithmetic on the liability timing, because that is where batch and real time separate. A programme that earns 2 points per dollar on 1 billion dollars of annual qualifying spend will issue 2 billion points per year. At a liability of 0.8 cents per point, the deferred revenue line is 16 million dollars. A monthly batch process holds the average accrual for 15 days, tying up 657,534 dollars of working capital. Real time accrual drops that holding period to 0 days and frees the full amount.
The actuarial model that prices the liability becomes testable only when accrual is real time. A batch system allows the actuary to assume a delay and smooth the breakage rate. Real time removes that smoothing. The model must now predict redemption behaviour at the moment of accrual, which is harder but honest.
Real time accrual is not the same as real time qualification. A programme can post the points instantly but still run tier evaluation on a 30 day cycle. That split confuses members, who see points but no tier change. The two systems must be built on the same event stream, not on separate batch jobs.
The cost argument against real time accrual is usually an excuse. Programmes that claim real time is too expensive are ignoring the support calls, churn, and mistrust that delayed accrual creates. Real time accrual is now the price of admission, not a differentiator.