How to rebuild a month of spending you never logged

You want to start tracking your spending and you need a starting point: how much you spend a month, on what, and what your floor is. But you logged nothing.

It can be reconstructed. It'll come out worse than if you'd logged it as you went, but it's enough for what's needed: a base month to budget against.

Before you start: what you're doing it for

It matters, because it changes how much precision you need.

If it's for budgeting or calculating your emergency fund, the large and medium expenses are enough. A 10% error changes no decision.

If it's for your accountant or a tax deduction, don't reconstruct from memory: request the formal records.

If it's to "see where my money goes", reconstruction doesn't help much. That understanding comes from logging in the moment, not from reading an old list. Start logging today and use the reconstruction only for the base number.

The sources, in order of yield

Work through them in this order. Each one covers what the previous left out.

1. The credit card statement. It's the most complete source and the easiest to read, and it usually covers a good share of large spending. Watch two things: the statement date isn't the purchase date, and the instalments showing up may be from previous months. How to read it is in how to read a card statement.

2. The bank statement. Direct debits, transfers, debit card. This is where the fixed costs show up — the ones you forget precisely because they pay themselves.

3. Digital wallets. Each has its own history and none of them share it. If you use two or three, that's two or three passes.

4. Your email. Search "receipt", "invoice", "your order" and "confirmation" over the period. Almost all the online spending that lives nowhere else turns up here.

5. Active subscriptions. On iOS: Settings → your name → Subscriptions. On Android: Google Play → Payments and subscriptions. This is where what you pay for and don't use shows up.

6. Cash withdrawals. And here comes the awkward part.

Cash can't be reconstructed: it gets estimated

An ATM withdrawal is one line; the six expenses it turned into are nowhere. Nobody remembers them.

The honest way to handle it: add up the month's withdrawals and log them as a single expense in a "cash (estimated)" category. Don't split it into invented categories — that turns one estimate into six false data points you'll later treat as real.

If cash is a big share of your month, the number will be rough. That's fine: it still works as a floor, and from now on it gets logged in the moment.

The three reconstruction mistakes

Double counting. The classic case: the transfer from bank to wallet AND the expense paid with the wallet. Only the second is an expense; the first is a movement between your own pockets.

Counting the full purchase of something bought in instalments. If you bought it eight months ago over twelve instalments, this month's figure is one instalment, not the purchase. It's in interest-free instalments.

Reconstructing a single month. One month lies: it might be the birthday month or the annual insurance month. With two or three, the structural stuff appears and the odd events average out.

When it isn't worth it

If what you want is a budget and you already know this month was unusual, reconstructing gives you a bad number wearing the appearance of data. In that case it's better to go the other way: log one complete month in real time — it's thirty days — and use that.

In one line

Work through card, bank, wallets, email and subscriptions in that order, estimate cash as a single line without inventing categories, don't double count transfers between your own accounts, and do it across two or three months rather than one.

Kesef is free, on iPhone and Android

Shared expenses with no cap, 60+ currencies, and the numbers explained.