Credit card statements never reconcile like bank statements — here's why

Bookkeepers who can reconcile a bank account in their sleep still stumble on credit cards, and it isn't carelessness. A card statement is a different document wearing the same clothes: the columns look alike, the totals are in the same places, and nearly every convention is reversed. Here are the five differences that cause the trouble, and the handling that avoids it.

1. The signs are backwards

A bank account is an asset: money in is positive, money out is negative. A card account is a liability: the statement shows your spending as positive (because it increases what you owe) and your payments and refunds as negative, or marked "CR". Import a card statement with bank-account signs and every purchase becomes income.

Decide the convention before you import, not after. Most accounting software wants a credit card account fed in bank style — spend negative, payments positive — and will tell you which on the import mapping screen. Convert the statement, look at one transaction you recognise (last month's payment to the card is ideal), and check its sign before the rest go in.

2. There's often no running balance

Bank statements print a balance after every line. Most card statements don't; they print a previous balance, a new balance, and summary totals for purchases, payments, interest and fees in a box at the top. That means the row-by-row check a bank statement allows — each balance equals the last plus the amount — isn't available. What is available is the statement-level check:

previous balance + purchases + interest + fees − payments − credits = new balance

It proves completeness for the statement as a whole rather than pinning an error to a row. NoRekey runs it on every card statement that declares those totals, and marks the ones that don't as unverifiable rather than pretending — a distinction that matters more for cards than anywhere else, because some card statements genuinely publish no totals at all.

3. The period isn't a month

A card cycle runs from statement date to statement date — the 14th to the 13th, say — and the payment due date is later still. Three consequences:

• Year-end spending sits on the January statement, not December's. Include the first statement after year-end when you gather records.
• "This month's card expenses" and "the January statement" are different numbers. Pick one definition for the books — most practices go by transaction date, which the converted rows give you — and stop thinking in statements.
• The balance you owe at year-end is a liability on the balance sheet, and it's the running position on that date, not the last statement's new balance.

4. The payment appears twice

You pay the card from the bank account. That payment is on the bank statement (money out) and on the card statement (a credit). It is the same transaction, and it is neither an expense nor income — it's a transfer between two of your own accounts. Book it as a transfer once; in the bank account it reduces cash, in the card account it reduces the liability, and nothing hits the profit and loss.

Booking the card payment as an expense and booking the card's individual purchases as expenses is the single most common double-count in small-business books, and it's silent: the total looks plausible, the reconciliation balances on both sides, and the profit is simply understated by the card spend.

5. The extras

Interest and fees are expenses in their own right, on a business card. They're in the summary box and as lines; use the lines.

Foreign transactions arrive as the converted amount, with the foreign-exchange fee sometimes folded in and sometimes on its own line the following day. Keep them together when categorising.

Refunds are negative purchases, not payments. They belong against the expense category they reverse.

Pending transactions on the app aren't on the statement; the statement is the record.

Multiple cardholders share a statement; if you need spend by person, the statement usually shows the last four digits of the card used on each line.

The routine

1. Gather the cycle's statement — and at year-end, the first one after it.
2. Convert it. Check the statement-level arithmetic; if the converter does that for you, look for the verdict.
3. Fix the sign convention to match the destination account before importing.
4. Import into the card account in your software, never the bank account.
5. Match the month's payment from the bank as a transfer, once.
6. Categorise the spend. Refunds against their categories; interest and fees to finance costs.

The help-centre guide has the converter-specific details, and card statements from American Express and the bank-issued cards convert the same way as any other statement. The document is different; the discipline is the same. Prove it's complete, get the signs right, and count the payment once.