WALLETWATCH · PRACTICAL MONEY RECORDS

Are you counting credit card spending twice?

A worked example of purchase tracking versus bill-payment tracking.

You buy groceries for ₹1,000 on a card, then pay a ₹1,000 bill. Your bank account has a payment and your purchase history has groceries. That does not turn the groceries into ₹2,000 of spending. The first decision is what your expense report should count: purchases or bill payments.

Watch the practical walkthrough

The demo uses fictional amounts, cropped product steps and English synthetic narration. The written examples below explain the same method without requiring the video.

One purchase, two ways to keep the record

Use Detailed when you want purchase categories

1. Open You → Credit card tracking and choose Detailed.
2. Record each purchase as an expense with its category and card. The ₹1,000 grocery purchase belongs in the category where you want to review that spending.
3. When you pay the issuer, open Cards → Reconcile for that card's billing group, then Record bill payment. Use the payment amount and paid date from your own records.
4. Do not also create an ordinary expense called “card bill” for the same settlement. In Detailed mode the saved bill payment is excluded from the expense dashboard; the purchases already count.

The purchase category answers “what did I buy?” The bill payment record answers “when and how did I settle the card?” Both records can be useful, but they serve different purposes.

Use Lump-sum when you only record bill payments

Choose Lump-sum under You if you prefer to record card bills rather than purchase-level expenses. Record the payment through Cards → Reconcile → Record bill payment. WalletWatch counts saved bill payments by their paid date in this mode. Keep ordinary individual expenses for the same card spending out of that approach, or the report can include both.

This saves entry work but loses the grocery-versus-travel detail of individual purchases. Ordinary non-card expenses still need their own records. Selecting Lump-sum does not delete any individual expenses you saved earlier.

Why monthly totals can still differ

Suppose the groceries were bought on 27 October and the bill was paid on 5 November. With only this example in the records, Detailed reports ₹1,000 in October and no new purchase expense in November. Lump-sum reports no October bill payment and ₹1,000 in November. The lifetime amount is the same, but the timing is different. A single month's totals are not a fair like-for-like comparison between these methods.

If your records already contain a duplicate

Export a JSON backup under You → Backup & export first. Find the original purchase, the ordinary expense that repeats its payment, and any separate bill payment record. Check dates, amounts and notes against your source before correcting the duplicate. Changing the tracking setting does not inspect or remove those entries for you. Do not remove a genuine second purchase just because its amount matches a payment.

Try the card spending check to compare the two counting methods. For cards on one issuer statement, continue to shared card bills. If your history is in a spreadsheet, use the CSV preparation guide before importing it.

The calculator and this example do not calculate the bank's amount due. Fees, interest, refunds, earlier balances and statement timing need separate review against the issuer's records.

Open WalletWatch