Credit Card Accounting - Part 1
Paying by company card feels like paying. For the books, almost nothing has happened: a third party paid the vendor, and you now owe the third party. Between your receipts and your bank account sits a small revolving debt — and replicating it faithfully is one of the quietly hard problems of pre-accounting. This series is about that problem.
Two streams, one gap
Pre-accounting sees a business month as two streams. Receipts and invoices arrive and become expenses; the bank statement arrives and says what was actually paid. With a credit card, the two stop meeting. The receipts are real and the expenses are real — but the bank shows a single line, weeks later, that mentions none of them. One card month, which will follow us through the whole series:
| Item | CHF | Where it surfaces |
|---|---|---|
| Restaurant meal | 50 | A receipt |
| Office supplies | 30 | A receipt |
| Software licence | 120 | A receipt |
| Card fee | 5 | Only on the card statement |
| The bank statement | −205 | One line: payment to the card company |
No amount on the bank statement matches any receipt. The 205 is the sum of three receipts plus a fee nobody invoiced, and it arrives on its own schedule — possibly before the receipts, possibly long after. To connect the two streams at all, the books need the thing in the middle: the card.
A small revolving debt
Because the card is not a payment method; it is a debt that revolves. Each statement opens with the balance you still owed, adds what you bought, subtracts what you paid, and closes with what you owe next. Pay everything, pay an instalment, pay nothing — at any given moment something is outstanding:
| Statement line | CHF | What it is |
|---|---|---|
| Previous balance | 320 | Carried forward from last month |
| New purchases | +200 | Our three receipts |
| Card fee | +5 | Invoiced by no one |
| Your payment | −320 | The lump sum that hits the bank — settling last month's statement |
| Closing balance | 205 | What next month opens with |
Notice what the lump sum just did: it paid last month's statement, not this month's purchases. The money you see moving and the expenses you are booking belong to different periods — and where the holder pays in instalments, the closing balance may never reach zero at all. A faithful replica must carry this rolling balance somewhere in the books, every day of the year.
The short circuit, and its phantom payments
The tempting shortcut is to ignore the card: book every card purchase as if the bank had paid the vendor directly, then absorb the real lump sum with an offsetting entry so nothing double-counts. The expenses land in the right accounts and the totals work out. But look at what the bank journal now claims:
| Bank account movement | CHF | Real? |
|---|---|---|
| Restaurant meal | −50 | The bank never paid this |
| Office supplies | −30 | …or this |
| Software licence | −120 | …or this |
| Card fee | −5 | …or this |
| Payment to the card company | −205 | The only real movement |
| Offsetting entry | +205 | Synthetic, to cancel the lump sum |
| Net | −205 | Correct — but five of six movements are fiction |
The sum matches reality; the journal does not — and a bank journal that records movements which never happened is the opposite of the complete, truthful record the law asks for (art. 957a para. 2 CO). Reconciling against the actual bank statement becomes an exercise in remembering which entries are real. And the moment the card is not fully settled — an instalment of 150 instead of 205 — the fiction leaks: the bank account is now over-drawn by 55 francs that never left it, and a manual correction must park the remainder on some liability account this method never wanted to have. The outstanding debt ends up smeared across accounts, readable nowhere.
What a faithful replica needs
Take the failures and invert them, and the requirements write themselves. The card must exist in the books as what it is — a liability carried at its nominal value, on its own account (art. 960e para. 1 CO). Purchases build the debt item by item, settlements reduce it, and whatever stays open is simply the account's balance:
| Requirement | Why |
|---|---|
| The bank journal shows only real movements | Reconciliation stays mechanical |
| The card debt is readable on one account | The books can answer: how much do we owe the card company? |
| Partial payments need no corrections | An instalment just leaves a balance standing |
| The order of arrival must not matter | Receipts, statements and bank lines come when they come |
| New channels must not need new machinery | The next card — or employee expenses — should work the same way |
None of this is exotic accounting; it is the discipline of giving the middleman an account. The genuinely interesting question is architectural. Pre-accounting systems hold receipts and payments in a staging ledger and match them before anything becomes a booking — so where does the card live there?
The card can get its own staging ledger — clean, explicit, and demanding to feed. Or the staging area itself can generalize until any settlement path fits. Part 2 builds both, and lets fiduciary reality pick the winner.
About Vektor AG
Vektor AG is a growing network of independent fiduciary firms in Switzerland. We combine the strengths of individual companies with the resources and innovative power of a strong group.