Recurring charges leave the thinnest trail

A card statement shows £14 a month to a vendor whose name you don’t recognise, and it has been going out for two years. Nobody handed you anything, no email arrived that you can find, and there was no moment at which capturing anything was possible.

Recurring charges break the receipt-keeping model completely, because that model is built on a transaction you were present for. Nothing about a subscription satisfies that.

Why the usual habits don’t apply

There is no capture moment. Every practice on this site anchors to the instant of paying, because that is when the reason for the spend is available — the argument in writing it down at the time. A recurring charge is authorised once and then happens without you, dozens of times, each producing a payment and no event.

Notification is unreliable and unstandardised. Some vendors email an invoice every cycle. Some email nothing. Some post a document to a portal and notify you never. Some notify you only of price changes. There is no channel you can watch that catches all of them.

The descriptor is often unidentifiable. Recurring charges are disproportionately from businesses whose statement descriptor is a payment processor, a parent company, or an unrelated trading name. The merchant descriptor problem is worst exactly where you have the fewest other clues.

The amount drifts silently. Annual increases, tier changes, tax changes, currency movement. A charge you identified two years ago is a different amount now, which breaks the recognition-by-amount that carries most reconciliation.

Volume outstrips attention. A handful of subscriptions produce more transactions per year than most of your one-off purchases combined, and each is individually too small to trigger a look.

Treat the arrangement as the record

The move that fixes this is to stop trying to capture transactions and instead keep one record per arrangement.

For each recurring charge, one entry containing: what it is, in words you’d recognise; the descriptor it appears as on the statement; the amount and cycle; when it started; the account or card it’s charged to; where the invoices live if they exist anywhere; and the reason — what it’s for and why.

That entry is the record. The individual monthly charges are instances of it, and they need no annotation because the arrangement already explains them.

Two things this immediately solves. The unidentifiable descriptor becomes identifiable, permanently, because you wrote down the mapping once. And the reason field — the one that never survives — is recorded once for a hundred transactions rather than needing to be attached to each.

Keep the list as plain text, in the archive, with the year’s records. It survives everything, which matters more here than convenience — see what happens to metadata.

Building the list from a standing start

Work backwards from a statement, not from memory. Take twelve months and read every line. Memory will produce the subscriptions you value and miss the ones you forgot about, which are precisely the ones the exercise is for.

Look at both cards and any other payment route. Recurring charges accumulate on whichever card was convenient at the time, and one card’s statement is not the set.

Chase the unrecognisable ones properly. A descriptor you can’t place is worth ten minutes: check the portal of anything plausible, search email for the amount, search for the descriptor string itself. This is the only time it will be this easy — the trail gets colder, not warmer.

Then go and get the invoices. Most vendors hold a billing history behind the account page. Download the period you need now, while the account exists, for the reasons in records you don’t actually hold. This is also the point at which you discover which vendors keep only twelve months of history.

Annual charges are the ones you’ll miss. They appear once in a twelve-month window and are easy to read as a one-off. Domain renewals, insurance, memberships, software licences.

Keep or bin

KEEP OR BIN — a subscription trail

  · One plain-text entry per arrangement,
    with the statement descriptor
                    → KEEP. Explains a hundred
                      transactions at once.

  · Invoices downloaded from the vendor's
    billing history
                    → KEEP. Real documents; the only
                      itemised record that exists.

  · Note of the date and reason the
    arrangement started
                    → KEEP. Nothing else records it.

  · "Your payment was successful" email
                    → NOT A RECEIPT usually — no
                      itemisation, no tax breakdown,
                      often no amount detail. Check
                      before relying on it.

  · Statement line for a monthly charge
                    → NOT A RECEIPT. Payment evidence
                      with a descriptor that may name
                      nobody you've heard of.

  · Twelve identical monthly confirmation
    emails
                    → BIN eleven, or keep them
                      unannotated. The arrangement
                      entry carries the meaning.

  · Whether a billing-history document is
    acceptable where no invoice was ever
    issued
                    → ASK LOCALLY. Format
                      acceptability varies by
                      jurisdiction.

The annual maintenance pass

Recurring charges are the one class of record that benefits from a standing review, because the arrangements change without telling you and the changes are invisible in the statement.

Once a year, alongside the disposal pass in running a disposal review: read the current statement against your list. You are looking for four things — a charge on the statement that isn’t on the list, a charge on the list that has stopped, an amount that has changed, and a descriptor that has changed. All four are common and none announce themselves.

The list also solves a problem that has nothing to do with recordkeeping: it is the only complete answer to “what am I paying for”, which is a question most people cannot answer about their own accounts.

Cancelled is not finished

One last case. When a subscription ends, the records don’t. You still hold whatever period of it is covered by whatever retention applies, and the vendor’s billing history — your only source for the itemised documents — is now behind an account you have no reason to keep and may lose access to.

So the sensible sequence is: download the full billing history before cancelling, not after. Then mark the arrangement’s entry as closed with a date rather than deleting it, so that next year’s pass knows the charge stopping was intentional.

What this doesn’t settle

Whether a payment-confirmation email, a billing-history page, or a statement line is acceptable in place of an invoice. How long records of a recurring arrangement must be kept, or from which date. Whether a subscription’s treatment differs from a one-off purchase.

Those are rules that vary by jurisdiction and record type, and your tax authority or adviser has them. What holds regardless: a recurring charge is the only kind of spend where the reason can be recorded once and cover everything, and also the only kind where nobody will ever hand you a piece of paper to remind you to do it.