WALLETWATCH · PRACTICAL MONEY RECORDS

Card spending check

Compare purchase tracking and bill-payment tracking without storing your amounts.

Use this check when a purchase and its later card payment both appear in your records. It compares which amount a tracking method counts. It does not calculate an issuer's amount due. Inputs are processed in your browser; this tool does not store or send them.

Enter totals for the same scope

Choose one card or one billing group and a clear period. Purchases means the spending you recorded on that card. Bill payments means the payments you recorded to settle it. Enter non-negative amounts in rupees with at most two decimal places. If either total changes, calculate again.

Read the result through a fictional example

With purchases of ₹1,000 and a payment of ₹1,000, Detailed counts ₹1,000 of purchases. Lump-sum also counts ₹1,000 here, using the payment. Adding both as ordinary expenses would show ₹2,000 for the same spending. The tool compares these choices; it does not change any WalletWatch entries.

Now suppose an October purchase is ₹1,000, while an October payment of ₹600 relates to September purchases. Detailed counts the October purchase; Lump-sum counts the October payment. The ₹400 difference between those reports does not establish an unpaid balance. Dates, earlier purchases, fees and refunds can make period totals differ.

What to check next

• Use the card recording guide to match the method to the actual purchase and payment workflow.
• If two cards share an issuer statement, first confirm the scope with the shared-bill guide.
• Review historical entries before treating an unexpected total as a new transaction. Changing a method does not identify or repair every duplicate.

Interest, fees, refunds, starting balances and issuer-specific payment rules are outside this comparison. Check the issuer statement for the bank's amount due and deadline. Do not use this calculation as proof that a bill is paid.

Open WalletWatch