Code a credit-card payment
Record a payment from checking to a card once, without double-counting the original expenses.
Recognize It
A credit-card payment moves money from checking to the card liability. The expenses were already recorded when the individual charges posted — the payment itself is not an expense.
LedgerHQ marks the row possible card payment and offers no plain Post action. Trying to post one tells you why:
This looks like a credit card payment. Match or record it as a transfer instead of posting it as income.
That block is deliberate. Posting a card payment as an expense counts the same spending twice — once on the individual charges and again on the payment.
Record It As A Transfer
Both accounts are the company's own, so this is a pair:
- Confirm both the checking account and the card are connected in this company.
- Find the matching row on the card feed.
- Record the pair rather than posting either side alone.
See Code an internal transfer for the pair controls.
Tally settles most of these automatically and only asks when it cannot find the funding side. See How Tally settles transfers and card payments.
When The Funding Side Is Missing
If the payment came from an account that is not connected in LedgerHQ, there is no second leg to match. That is the single most common cause, and it is why Tally asks the company owner which account the payment came from.
Connect that account — see Connect a bank or credit card — and the pair settles.
Leave the payment row unposted meanwhile. Do not code it to an expense account to clear the queue.
Verify
After recording, check both registers: checking decreases and the card liability decreases by the same amount. Net expense should not change.
If the treatment is unclear — a partial payment, a payment from outside this company, or one covering more than one card — create a support ticket with the company, both accounts, date, and amount rather than guessing.