Debt

A card bill payment is not spending: avoiding the double count

When a credit card bill is paid from a bank account, the money moves between your own accounts. Counting it as an expense on top of the purchases already recorded doubles the picture.

Editorial illustration for A card bill payment is not spending: avoiding the double count

Where the double count begins

Imagine you buy groceries for 2,000, fuel for 3,000 and a few small things for 1,000 on a card. Six thousand units of spending, recorded across three days. At month end you pay the card bill of 6,000 from your bank account. If both the purchases and the bill payment are logged as expenses, your report now says you spent 12,000. You did not.

What the payment actually is

The bill payment settles a debt the purchases created. It moves money from your bank account to reduce what you owe the card issuer. In a clean view, it is a transfer between two of your accounts, bank to card, and not a new cost. The real cost was recorded when you bought the groceries and the fuel.

Two ways it appears in your data

  • Via a bank statement import, where the card bill shows as a debit with a description like ‘card payment’
  • Via manual entry, where the instinct is to log the payment as a bill

In both cases, the bank-side entry should be marked as a transfer to the card account, not as spending. If you track both the bank and the card as accounts in SpendixAI, the transfer links the two and leaves your expense totals alone.

A quick test for whether you are double counting

CheckHealthy signWarning sign
Monthly spend vs card purchases plus bank debitsTotals match roughlySpend is far higher than your real outflow
A category named ‘Credit card’Does not exist as expenseAppears with a large figure
Bank debit labelled card paymentMarked as transferMarked as expense

If the third row shows a warning, open the transaction and change its type. Your totals will fall to a more truthful figure at once.

What if you only track the bank account

Some people do not track the card as an account and rely on the bank debit alone. This is a valid choice, but then the purchases are invisible and the bill payment is the only record. The catch is that categories become meaningless, since a single payment mixes groceries, fuel and small things. If you want category-level insight, the card needs to be its own account with its own entries.

Month-end routine

When the bill arrives, tick off each purchase on the statement against your entries. Whatever is missing, add. Then record the payment as a transfer. If the card balance in SpendixAI equals the statement total, the loop is closed and the numbers can be trusted.

What happens with refunds

Returns are another place where numbers drift. A refund to a card appears as a credit on a later date, sometimes in a different cycle from the purchase. Record the refund as a negative expense in the original category, not as income. That way the category’s total reflects what you actually spent, and the card account balance shows the credit when it arrives.

If the refund is slow, note the expected date in the transaction description. Checking back a week later is easier when the note says what you are waiting for.

Handling shared cards

If more than one person uses the card, add a note or tag for the user on each purchase. At month end, the tags show who spent what, and the settling-up conversation is about facts. Without tags, a shared card quickly becomes a source of friction, and the bill payment looks like one mysterious lump.

If you have been double counting for months, fix it going forward rather than rewriting history. Change the type of the last two or three bill payments to transfers, check that the monthly totals now look sensible, and move on. Old months can stay as they are, with a short note in your review that the figures were overstated by the card payments.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports