How to track credit card spending across multiple cards

Why several cards escape tracking

• Misaligned cycles. Each card closes its month on its own date, so no two statements cover the same days, and adding three bills adds three different stretches of time that happen to share a due month
• One app per issuer. Each card's app shows that card and nothing else, so the combined figure for the month never exists anywhere
• EMI conversions and add-on cards. A purchase converted to EMI appears once at full price on the day you bought it, then returns every month as an instalment with interest and GST on top. An add-on card's spending lands on your statement while its alerts go to someone else's phone
• Lines that are not purchases. Cashback, reversals, annual fees, GST, interest and surcharges sit in the same list as your shopping, so the list's total is neither what you spent nor what you chose to buy
• UPI on a credit card. A payment from a RuPay credit card through GPay, PhonePe or Paytm feels like a bank payment but never touches the bank account, so tracking from the bank statement misses it

One month, three cards, six statements

• Judge September by October's bills and you would say ₹70,000. You spent ₹86,800. The ₹16,800 gap is timing, not missing money, and it runs the other way in a quiet month
• Only ₹53,100 of the ₹70,000, about 76 percent, is September at all. The other ₹33,700 of September sits elsewhere: ₹4,200 was billed on 5 September and paid on the 25th, and ₹29,500 has not been billed yet and falls due in November
• An ₹18,000 purchase on card B on 22 September appears on no statement until 18 October and is due on 8 November, 47 days later. That is the interest-free period working, and why a heavy month surfaces nearly seven weeks late

What one missed due date costs

• ₹3,541 is 14.8 percent of the ₹24,000 bill, for being ten days late with money you had. Most of it, ₹2,951, is interest and GST on interest; the late fee is the smallest part and the only one people expect
• About half of that interest is on purchases not yet billed: the interest-free period being withdrawn, the line nobody sees coming
• More than 3 days late can also be reported to the credit bureaus as past due, and a late mark in payment history generally weighs on a score longer than a high balance does

Three things to track on every card

• Spend by transaction date, all cards together, for the calendar month. This is the number for a budget and the only one that answers what September cost. Leave out fees, interest and cashback
• Outstanding by statement, card by card: what you owe on each due date, with interest, fees, EMI instalments and credits. Pay this one in full; it will almost never equal the first
• Due date, one per card. An autopay mandate for the full statement amount removes the missed-date cost above; one for the minimum removes only the late fee, and interest still runs

Utilisation: per card and across cards

• Card C, the smallest limit, is carrying more than half of it while the overall figure is 24.1 percent. The total hides the card a lender notices first
• Moving ₹12,000 of monthly groceries from card C to card B takes C to 21.5 percent and B to 24 percent. The overall ratio stays at 24.1 percent: moving spend changes the per-card picture, never the total
• Only paying down, or paying before the statement date, lowers both. Why the statement-date balance is the one the bureau sees is worked through in statement date vs due date on a credit card

Which card each spend should have gone on

A 10-minute review, and what a tool must see

• Does it see every card? One built on a single issuer's data, or on your bank account, sees one card, or none of your UPI payments on credit. Test it against last month's statements
• Does it read statements, or only alerts? Alerts give the transaction-date view but miss interest, fees and some EMI lines; statements give the owed view weeks later. You need both, with duplicates removed
• Does it show due dates? Totalling spending without them covers the view with no penalty and ignores the one that has one