To find out what a reward points redemption was worth, divide the rupee value you received by the points you spent. The rupee value is the cash price you would otherwise have paid, less anything you paid extra in cash. Log it every time and your own average, not a catalogue promise, tells you whether the points are worth chasing.
What does the redemption log contain?
- A: Date of the redemption.
- B: Points used.
- C: What you received and the route, such as a voucher, a booking or a statement credit.
- D: Comparable cash price, the amount you would have paid in cash for the same thing.
- E: Cash you paid on top, such as fees or a top-up.
- F: Value received, calculated as D minus E, limited to what you would really have used.
- G: Value per point, calculated as F divided by B.
How do you fill it in without fooling yourself?
The honest part is column D. Use a price you would actually have paid. A voucher with a face value of ₹1,000 is worth ₹1,000 to you only if you would have spent that money at that shop anyway; if you will use ₹600 of it, enter 600. A flight priced at its usual market fare on the same date is a fair comparison; a never-discounted list price is not.
What does a worked example look like?
The three rows below are hypothetical.
| Item | Points used | Comparable cash price | Cash paid on top | Value received | Value per point |
|---|---|---|---|---|---|
| Flight booking | 10,000 | ₹5,200 | ₹700 | ₹4,500 | ₹0.45 |
| Shopping voucher, part used | 3,000 | ₹600 | ₹0 | ₹600 | ₹0.20 |
| Statement credit | 5,000 | ₹1,250 | ₹0 | ₹1,250 | ₹0.25 |
Value for the flight is 5,200 − 700 = ₹4,500, and 4,500 ÷ 10,000 = ₹0.45. Across all three, 18,000 points bought 4,500 + 600 + 1,250 = ₹6,350 of value, so the weighted average is 6,350 ÷ 18,000, about ₹0.35 per point.
Which formulas do you need?
- Value received in F2: =D2-E2
- Value per point in G2: =F2/B2
- Weighted average across all rows: =SUM($F$2:$F$500)/SUM($B$2:$B$500)
- Average of the per-row values, for comparison: =AVERAGE($G$2:$G$500)
Use the weighted average when you decide what points are worth to you, because a big redemption should count for more than a small one. The simple average of the per-row values can mislead when one row is tiny.
What if you redeem only part of a voucher or travel booking?
Count only the part you used. If a ₹1,000 voucher leaves ₹400 unspent at the year's end, the redemption was worth ₹600 to you, and the log should say so. If the balance is still usable later, you can note it and revise the row when you use it. A redemption that expires unused is a loss, and it is better to see it in the log than to forget it.
What should you do with the numbers?
Compare the routes. In the example, the flight gave ₹0.45 a point and the voucher ₹0.20, so the voucher route was the weakest for this person. Next time you consider a redemption, check the quote against your own average before confirming. If a route is consistently low, leave points for a route that is not.
Where does SpendixAI come in?
The log is best kept in a sheet. If a redemption shows up as a statement credit or a card purchase, the matching row will appear when you import the card statement, with the card as the account, and you can review it before saving. Keep a note in the log so you can match the two.
After each redemption
- Add a row the same day.
- Write the comparable cash price from a quote you saw.
- Update the weighted average.
- File the confirmation where you can find it.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


