Take a typical example. It is the second business day of the month and a bookkeeper opens the company card statement: 140 lines, a dozen of them reading something like “GOOGLE*SERVICES” or “AMZN Mktp”, three in euros, two refunds and a charge nobody recognizes. Each line needs a receipt, a GL code and often a message to whoever made the purchase. The close waits while the questions go around the team.
The problem isn’t the volume of charges. It is that one card carries many purposes, so every line has to be investigated before it can be coded. Change the card setup and most of that investigation disappears. This guide explains how to structure cards so each one maps to a single vendor or ledger line, and how to run virtual card reconciliation as a short, repeatable routine.
Why card reconciliation drags out the close
Merchant descriptors are vague
The text on a card statement is set by the merchant and its payment processor. One company’s descriptor can cover several products, and the same product can appear under different names month to month. Matching a descriptor to an invoice is guesswork when the card pays for many things.
Shared cards hide who bought what
When five people use one card, every unclear charge starts a hunt for the buyer. Receipts arrive late or not at all, and the bookkeeper ends up coding from memory and assumptions.
Timing never lines up neatly
Transaction dates, posting dates and invoice dates differ. A subscription billed on the 30th may post on the 2nd, landing in the next period on the card while the invoice belongs to the old one.
Currency and fees add small differences
Foreign-currency charges convert at the card’s rate, so the amount on the statement rarely matches the vendor’s invoice exactly. Per-transaction fees add more small lines to explain.
The fix: one card, one purpose
If every card pays for exactly one vendor, project or cost center, then the card itself tells you how to code the charge. The last four digits become a coding key. You no longer ask “what is this?” for each line; you only check that the amount matches the vendor’s invoice.
| Card setup | What you match at close | Coding effort | Typical exceptions |
|---|---|---|---|
| One shared company card | Every line against receipts from many people | High: each line coded by hand | Unknown charges, missing receipts |
| One card per employee | Each person’s lines against their receipts | Medium: buyer is known, purpose is not | Mixed purposes on one card |
| One card per vendor | Each card against one vendor invoice | Low: one GL code per card | Price changes, FX differences |
| One card per cost center or project | Each card against the project budget | Low to medium: one cost center, several GL codes | Vendors that bill several projects |
Most teams combine the last two: a card per recurring vendor (software, cloud, ad platforms) and a card per project or department for irregular purchases.
How to set it up, step by step
- Pull a year of card charges. Group them by vendor and count how often each one bills. Recurring vendors are the first candidates for their own card.
- Map vendors to your chart of accounts. Decide the GL account and, if you track them, the class or cost center for each vendor or project.
- Design the card map. One row per planned card: purpose, GL code, cost center, owner and expected monthly amount. Keep it to cards you can manage; a card for a $5 annual tool may not be worth it.
- Issue the cards and move the vendors. Update the payment method on each vendor account. Note the switch date so you know which charges should still hit the old card.
- Set a standing coding rule per card. In your accounting software, create a bank rule or memorized transaction that codes each card’s charges automatically.
- Point invoices to one inbox. Change the billing email on each vendor account to a shared finance address, so invoices arrive without anyone forwarding them.
- Keep a card register. Last four digits, purpose, GL code, owner, issue date and expiry. No full card numbers or CVVs.
The monthly close checklist for card spend
- Export or list each card’s transactions for the period.
- Confirm each card has only its expected vendor or project. Anything else is an exception to investigate.
- Match each charge to the invoice in the finance inbox. Download missing invoices from the vendor’s billing page.
- Record FX differences and per-transaction fees to the accounts your policy uses for them.
- Book accruals for invoices dated in the period that haven’t posted to the card yet.
- Check each card’s balance and expected next charge, so a renewal doesn’t fail in the new month.
- Review the card map: retire cards for cancelled vendors and add cards for new ones.
Store invoices and card records for as long as your tax rules require. In the US, the IRS page on how long the IRS says to keep records sets three years as the general period, with longer periods in specific cases. Other countries set their own rules.
When a card per vendor is worth it
- The vendor bills monthly or more often: give it its own card.
- The vendor’s charges are large or variable, such as cloud or ad platforms: its own card, and a budget alert inside the platform.
- Several small tools belong to one team and one GL code: one shared card for that team and code is fine.
- The purchase is one-off: use the project or department card rather than issuing a new one.
A note on prepaid cards in the books
With a prepaid card, money moves before it is spent. Funding the provider balance and buying a card are usually transfers between asset accounts, not expenses. The expense is recorded when the card pays a vendor. Issue fees and per-payment fees go to whichever account your policy uses for card or bank fees. Confirm the treatment with your accountant, especially if you fund the balance with crypto, which can carry its own tax and valuation rules.
Example: a card map built on ZenVCC
ZenVCC is a prepaid virtual card platform that suits this structure. You fund one balance with crypto (Bitcoin, USDT on TRC-20 or Solana, TRX or SOL), each deposit is checked on its blockchain before it is credited, and you buy a separate prepaid Visa, Mastercard or American Express card for each vendor, project or teammate. Supported uses include SaaS bills such as Microsoft 365, Slack, Notion and Adobe, plus major ad platforms. Each vendor decides which cards it accepts, and some cloud and workspace providers, such as AWS and Google Workspace, restrict or refuse prepaid cards, so check billing rules before you move a vendor.
For a bookkeeper, the cost structure is easy to model, which matters when the card map has dozens of rows:
- $10 one-time issue fee per card, added to the card’s price when you buy it.
- $0.10 per card payment, one small, fixed fee line per transaction.
- $0 monthly fee, so a card for a low-volume vendor costs nothing to keep.
- Three-year validity, counted from the day the card is ready, so the card map and your bank rules stay stable for years.
- Full refund to the balance if a card can’t be prepared, including the issue fee.
Plan around two limits. Budgets aren’t set in ZenVCC, so spending caps live inside each vendor’s billing settings, and the prepaid balance is the hard ceiling. There are also no team roles or sub-accounts: whoever signs in sees every card, so keep the login with the finance owner of the card map. You can check how fees add up for your own map with its per-card pricing, which shows every card’s total before you buy.
Mistakes to avoid
- Letting a second vendor onto a dedicated card. One exception breaks the coding rule. Issue a new card instead.
- Forgetting the old card after a switch. Final charges and refunds may still land there for a cycle.
- Coding funding as an expense. Topping up a prepaid balance is not spend until the card pays a vendor.
- Creating cards nobody owns. Every card in the register needs a named owner who answers questions about it.
Key takeaways
- Card reconciliation is slow because one card carries many purposes, not because there are many charges.
- Map each card to one vendor, project or cost center, and the card number becomes the coding key.
- Automate coding with one bank rule per card and route every invoice to a shared finance inbox.
- Run a short monthly checklist: confirm, match, record differences, accrue and review the card map.
- Treat prepaid funding as a transfer and confirm the accounting with your accountant.
Start with your five most frequent vendors: give each its own card and a bank rule, then compare next month’s close with this one. If you want a prepaid option with no monthly fee per card, take a look at ZenVCC and see how it fits your card map.

Leave a Reply