If reward points have not been credited for a purchase, log it the same day you notice: the date, the merchant, the amount, the points you expected and why. Then check the next statement, raise it with the issuer if it is still missing, and record the ticket number and every follow-up date. A clear log makes the issuer's job easier and yours shorter.
When is a missing credit really missing?
Not every delay is a problem. Points may post after the statement closes, only on eligible spend, or in a later cycle. Before logging a complaint, read the card's terms for what earns points and when they are credited, and check the next statement. If the purchase is clearly eligible and the expected window has passed, it is worth raising.
What should the follow-up log capture?
| Field | Example (hypothetical) |
|---|---|
| Purchase date | 12 Sep |
| Merchant and amount | Electronics store, ₹14,500 |
| Points expected and how worked out | 290, at 2 points per ₹100 |
| Statement it should appear on | October statement |
| Date raised and channel | 28 Oct, app chat |
| Ticket number | As given by the issuer |
| Next follow-up date | 7 Nov |
| Outcome | Credited 290 on 4 Nov |
The expected points come from the card's own terms. Here, 14,500 ÷ 100 × 2 = 290. Write the working in the log so anyone reading it can follow.
How do you follow up without losing track?
- Check the statement that should have the points. If they are there, close the entry.
- If not, raise it with the issuer through its official channel, such as the app, the website or the number printed on the card.
- Give the date, merchant, amount and points expected, and attach the transaction line.
- Note the ticket number and the promised timeline in the log.
- Set a follow-up date for when that timeline ends.
How long should you wait before following up?
Wait for the period your card's terms give for points to post, and then for the next statement to close. If the terms give no period, a reasonable rule is one full statement cycle after the purchase. Write your chosen rule at the top of the log so you apply it the same way each time, and so you do not chase a purchase that is simply still pending. Purchases made through a partner portal or an offer page sometimes follow separate timelines, so note which route you used.
What does a clear message to the issuer say?
Keep it short and factual, and paste it into the app or email. For example: On 12 September I paid ₹14,500 at an electronics store with my card ending 1234. By the terms I expected 290 points on the October statement, which shows none. Please confirm whether the points will be credited and when.
Use only the last four digits of the card. State the expected points and how you worked them out, and ask a direct question. Vague complaints get vague answers, while a specific question tends to get a specific reply.
What should you keep as evidence?
- A screenshot or copy of the transaction line from the statement.
- The invoice or receipt for the purchase.
- The reward terms as they were on the date, saved or copied.
- Every reference number and the dates of every contact.
Can SpendixAI help?
Receipts can be kept with their transactions, so the invoice for the purchase sits beside the row. Importing the card statement gives you the transaction line to quote. The follow-up log itself can be a sheet or a note, since points are not tracked in SpendixAI.
Close the loop
- Write the outcome and the date in the log.
- If the points never came, note what the issuer said.
- Review the log at year end for patterns, such as one merchant type that never earns.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

