WALLETWATCH · PRACTICAL MONEY RECORDS

How to record cards that share one bill

Keep a shared card bill separate from individual purchases.

Two cards can appear on one issuer statement. If you copy the whole statement payment onto each card, one payment becomes two records. Keep the purchases attached to their cards and the settlement attached to the group that receives the bill.

A fictional two-card example

In Detailed mode, the ₹800 and ₹200 purchases provide ₹1,000 of spending. The ₹1,000 settlement is a bill payment record, not another ordinary expense for each card. In Lump-sum mode, use the group bill payment for the same spending instead of also logging those individual purchases as ordinary expenses.

Confirm that the issuer really combines the bill

Read the statement or issuer's account information before linking cards. The same issuing bank, a shared credit limit or two network logos does not by itself prove that there is one statement and one payment obligation. WalletWatch can suggest cards from the same bank; that suggestion is not verification of the issuer's arrangement.

The linking screen distinguishes Two separate cards, one shared bill from Same card product, two networks. Choose the description that matches the actual arrangement. If the cards receive separate statements, keep separate billing groups even when their bank names match.

Set up and record the group

1. In Cards, add the cards with their identifying details and billing closing day. The app does not need a full card number or banking login.
2. Use the card's billing-group controls to link it with the appropriate other card, then confirm how the cards are linked. Check the group's closing day afterward; the kept group's closing day applies to the linked cards.
3. Record purchases against the card used, if you use Detailed tracking. A purchase without the correct card tag will not appear in that group's tagged-spend check.
4. Open the group's Reconcile screen and choose the correct cycle. Review All cards or filter the transaction list to a member card.
5. Use Record bill payment once for the group's actual payment. Check its paid date, amount and any payment-source splits. Reopen Edit bill payment if the saved payment needs correction.

Linking can be refused when moving a group would hide its saved bill-payment history. Do not delete payment history just to force the link. Keep a backup and review the existing groups before reorganizing cards.

A closing day is not a payment due date

WalletWatch uses the group's closing day to select purchase-cycle dates. For a group closing on day 10, a cycle can run from 11 September through 10 October, including both dates. A purchase on 11 October belongs to the next cycle. The bank's payment due date is a separate fact; the app does not fetch or infer it from the closing day.

Check dates when a purchase appears in a different cycle than expected. A purchase's recorded date, the issuer's posting date and the selected cycle may differ. Changing the closing day changes the app's cycle boundaries; it does not edit the issuer statement.

Read Matches and Difference carefully

Reconcile compares the group's Tagged spend with its recorded Bill payment. In the clean example, ₹1,000 against ₹1,000 shows Matches. If you recorded a ₹1,100 payment against ₹1,000 of tagged purchases, Difference shows ₹100. That is a comparison of your saved records, not proof of a bank error or a calculation of what remains due.

Check the correct cards and cycle, missing or repeated purchases, payment amount, fees, refunds, earlier balances and timing against the statement. Do not change a real purchase merely to make the indicator match. WalletWatch does not read statements, move money or make card payments.

Before reorganizing your records, export a JSON backup in You → Backup & export. Use the purchase-versus-payment guide for the counting method, or the CSV guide if the purchase history is in a spreadsheet.

Open WalletWatch