Product Update

You're 18 Months Into an EMI and Your Tracker Has None of Them

August 14, 2026 · 6 min read

A user wrote in with a complaint that sounds trivial until you try to solve it yourself. He'd taken a loan in February. He started using Pocket Clear later in the year, found Recurring Transactions, and set up his EMI properly — amount, category, the day of the month it leaves his account. Then he waited for it to appear in his history.

Nothing appeared. Not February, not March, not any of the months he had genuinely paid. A recurring rule only creates an occurrence once its scheduled day has actually arrived, so a rule you save today produces its first transaction on the next due date and not a moment earlier. That is the right behaviour — a budgeting app that silently invents transactions the moment you save a rule would be a terrible budgeting app. But it left him with a loan he'd been paying for months and a tracker that thought he'd never paid it at all.

His options were to type in every missing month by hand, or to accept that his own spending history had a hole in it exactly where his largest fixed expense should be.

Why this hits EMIs hardest

Every recurring expense has this problem, but it isn't equally bad for all of them. If you set up a streaming subscription in month nine, the eight missing months are a rounding error in your annual spending. An EMI is different. It's often the single biggest line in the month, it runs for years rather than months, and its whole purpose in a tracker is to be visible — you're logging it precisely so that "where does my salary go" has an honest answer.

Leave those months out and every number downstream is wrong in the same direction. Your average monthly spend reads low. Your category totals under-report the one category you most wanted to watch. Any year-over-year comparison is comparing a year that included the EMI against a year that didn't, when in reality both did.

It's also a heavily Indian problem, in the sense that EMIs are simply how large purchases are paid for across much of India — phones, appliances, education, vehicles, homes. A tracker that can't represent a loan you're already eighteen months into isn't tracking the thing you most wanted tracked.

Fill in past months

Open a rule from Settings › Recurring Transactions and there's a new option at the bottom of the edit sheet: Fill in past months. It works out every occurrence between the rule's start date and today, and creates them.

It only appears when you're editing a rule you've already saved, not while you're creating one. That's because it works from the rule as stored — its start date, amount, category and frequency — and a half-typed rule doesn't have those things yet.

  • You see the plan before anything is written. Pocket Clear tells you how many transactions it will create, what they add up to, and the first and last date in the range. Cancel and nothing happens at all.
  • Months that already look filled are flagged. If some of those months already have a transaction in the same category for the same amount, you're told how many — and you choose whether to skip them or create everything anyway.
  • Undo is offered the moment it finishes. An alert on iPhone, a snackbar on Android. It removes exactly what the backfill created and touches nothing else.
  • Very old rules are filled in reviewable batches. One run creates at most 120 transactions — ten years for a monthly rule — starting from the most recent. Run it again for the next batch.
  • It's quiet. No notification, and it doesn't move the date your rule next fires. Filling in the past leaves the forward schedule exactly where it was.

The preview is the whole feature

Bulk-creating transactions in someone's financial history is the kind of operation that should make you nervous. Eighteen entries appearing at once, in months you can't see from the current screen, is a lot of change for one tap — and if the rule's start date is wrong by a year, or the amount is off, you've now got a mess spread across your history rather than one bad row you can spot and delete.

So the confirmation isn't a generic "are you sure". It's a count, a total, and a date range, worked out from the real plan rather than estimated. Reading "this will create 18 transactions, from February last year to July this year" is enough to catch nearly every mistake you could have made setting the rule up — the wrong start date and the wrong frequency both show up immediately in the count. If the rule has nothing behind it, because it starts today or you've already filled it, you're told that instead and nothing is offered.

The duplicate warning, and why it doesn't just decide for you

Plenty of people have been logging their EMI by hand while waiting for a better answer. If Pocket Clear ignored that, a backfill would double every month you'd already done.

So before it writes, it looks for transactions that already sit in the same category, for the same amount, in the same period as a planned occurrence, and reports what it found — something like "6 of those months already have a similar transaction in this category." You then pick: skip those six and create only the months that look empty, or create all eighteen regardless.

Both options are genuinely useful, which is why it asks instead of choosing. Same category, same amount, same month is a strong signal — and still only a signal. Two identical rent payments in one month is a real thing that happens, as is paying an EMI and a separate loan of the same size. Silently swallowing one of them would be worse than the duplicate. If every planned month looks like a duplicate, skipping is no longer offered, since skipping all of them would create nothing — you can create everything or back out.

The 120 limit, spelled out

One run creates at most 120 transactions, and it creates the most recent 120 rather than the oldest. For a monthly rule that's ten years in a single pass, which covers nearly every EMI. For a weekly rule it's a little over two years, so the same message can turn up sooner than you'd expect.

That's a limit per run, not a lifetime limit on the rule. Tap Fill in past months again and Pocket Clear plans the next batch — the occurrences the first run created are already accounted for, so it picks up where the last one stopped and never repeats a month. A genuinely ancient rule gets filled in a few passes, each with its own preview and its own count, rather than one enormous unreviewable one.

One thing to know before you tap Undo

Undo is real and immediate, and it does exactly what it says. But it is one-way: once you undo a backfill, running it again on the same rule creates nothing.

Pocket Clear remembers which occurrences a rule has already produced, and undoing doesn't make it forget them. Those months are treated as handled, so a second attempt reports that there's nothing left to fill in.

We'd rather say that plainly than let you discover it. It isn't an oversight — it's the same rule that stops Pocket Clear from resurrecting an auto-generated transaction you deleted on purpose. Without it, deleting a rent entry you didn't want would mean watching it come back the next time you opened the app. Once you've said no to a particular month, it stays no.

The practical version: treat Undo as a way out of a mistake, not as a preview you can flip on and off. If you undo and then change your mind, add those months by hand, or delete the rule and recreate it — a new rule counts as a fresh start and will backfill again.

Where to find it

Settings › Recurring Transactions, tap the rule, then Fill in past months at the bottom. It's on both iPhone and Android, and it's part of Pocket Clear Pro, like recurring transactions themselves. The full walkthrough, including every message you might see, is in the help centre: Fill in past months.

If you've been putting off setting up a loan or a subscription because the history would be wrong anyway — that reason is gone.

Give your recurring expenses their history back

Pocket Clear Pro: set up an EMI eighteen months late and fill in every month you already paid — with a preview first and Undo after.