Keep a card logbook: the five-minute habit that saves hours
A short table of cards, purposes and renewal dates turns support questions, refunds and tax time into quick lookups.
In this guide
Prepaid cards are easy to start using and easy to lose track of. After a few months you might have five cards, each paying for different things, each with its own expiry date. A logbook, which is just a small table you keep somewhere handy, turns that collection into something you can manage in minutes. This guide gives you a ready-made layout and the routine that keeps it current.
Why bother with a log
Three moments make a log worth its two minutes per card:
- A charge you do not recognize. With a log, you know at once which merchant uses which card.
- A renewal that is about to fail. The log tells you the expiry date and remaining balance before the merchant does.
- Month end, tax time or a client invoice. The log shows which costs belong where.
The dashboard shows each card's status, balance, expiry date and billing address, but it does not list the purchases each card made. Your log, together with the receipts merchants email you, fills that gap.
The layout
Use a spreadsheet, a notes app or paper. Any of them works if you actually open it. Start with these columns:
| Column | Example | Why it helps |
|---|---|---|
| Card ending | 4021 | Matches the last four digits merchants show |
| Purpose | Design tools | Keeps each card to one job |
| Merchants | Font service, photo editor | Tells you who may charge it |
| Next charge | Jun 14, about $24 | Warns you before a renewal |
| Expires | 09/28 | Tells you when to plan a replacement |
| Order | BV-7Q2M… | Links back to what you paid |
| Notes | Refund pending from shop X | Anything you would otherwise forget |
What you should never put in the log: full card numbers, CVVs, passwords or authenticator codes. The last four digits are enough to identify a card. The full details stay behind the code check in My Cards, where they belong. Our article on why card details should never live in screenshots explains the reasoning.
The routine
When a card is issued
Add a row: last four digits, purpose, expiry date and the order reference. Copy the reference from the order page; it is the quickest way to find the order later.
When you add the card to a merchant
Write the merchant in the Merchants column and the date of its next charge in Next charge. For services that bill on usage, note a typical monthly amount instead.
Once a month
Spend five minutes going down the list. For each card, compare the balance in My Cards with the next charges you expect. If a card will not cover its next charge, plan a replacement. If a card has finished its job, decide what to do with the remainder. The month-end close guide extends this check into proper bookkeeping if you need it.
When a card retires
Do not delete the row. Mark it as retired with the date. Old rows answer questions months later, like "which card paid that annual renewal?"
Small additions that pay off
- A color for each purpose. Ads in one color, subscriptions in another. Patterns jump out at a glance.
- A renewal calendar. Copy each Next charge into a calendar reminder a few days early. This guide shows a simple setup.
- Receipt links. If you keep receipts in a folder, add the folder name in Notes so evidence is one click away.
- Client tags. Freelancers can add a Client column and total it each month for billing tool costs back.
What the log does not replace
The log is your view of how cards are used. The authoritative figures stay in two places: the order pages, which record exactly what you paid (the balance, 15% of it as the top-up charge, and $5.00 for issuing the card), and My Cards, which shows each card's current balance and status. When the log and the dashboard disagree, the dashboard wins, and the difference is usually a charge or hold you have not written down yet.
Starting from a messy situation
If you already have several cards and no log, start with what the dashboard shows: list every card with its last four digits, balance and expiry date. Then go through your email for receipts mentioning each card ending. In half an hour you will have a usable log, and from then on it takes a minute per change. For planning future cards, see planning your first few cards and the pricing page.
Sharing the log with others
If a partner, bookkeeper or teammate needs to see where card money goes, share the log rather than your account. Give them view access to the document, not your sign-in. They can then answer their own questions about which card pays for what, while the card details themselves stay locked behind your authenticator app. For teams with several card users, a written one-page card policy pairs well with a shared log.
Quick answers
Is it safe to keep the log in a cloud document?
Yes, as long as it contains only last four digits and no full numbers, CVVs or codes.
How detailed should the Merchants column be?
Detailed enough that an unexpected charge on that card would surprise you. That is the point of writing it down.
New to ordering? How it works walks through each stage of an order.
BuyVCC Team
The people who review BuyVCC orders write these guides from the questions customers send us. Notice something outdated? Let us know.