Gmail expense tracking in India: how it actually works
See what your inbox already knows
Your bank has been emailing you a receipt for every transaction for years. Each UPI debit, card swipe, salary credit and autopay mandate arrives as a machine-generated alert with an amount, a date and an account attached — which means a complete, timestamped record of your spending already exists, sitting unread in Gmail. The work of expense tracking in India was never collecting the data. It was reading it.
Facts checked on 11 October 2026.
What your bank actually emails you
Open Gmail and search for the sender your bank uses for alerts. What comes back is not marketing. It is a stream of automated notices, one per event, each generated by the same template every time. That consistency is the whole reason this works: a human-written receipt is unpredictable, but a system-generated alert has the amount in the same place in every single message.
Five kinds of alert carry almost everything worth tracking.
| Alert | Triggered when | Usually carries |
|---|---|---|
| UPI debit | You pay a person or merchant | Amount, payee VPA, date and time, account tail, reference number |
| Card transaction | A credit or debit card is authorised | Amount, merchant string, card tail, date, sometimes city |
| Credit received | Salary, refund or inbound transfer lands | Amount, remitter name or narration, date, account tail |
| Mandate notice | An autopay or e-mandate is due or executed | Amount, merchant, due date, mandate reference |
| Statement | A card or account billing cycle closes | Total due, minimum due, due date, full transaction list |
The first four are the live feed. The fifth is the reconciliation: a statement email is the issuer's own authoritative list, which is useful precisely because it can be checked against the individual alerts that arrived during the same cycle.
Both an SMS and an email alert contain the transaction. What sets the email apart is that it persists. Alerts sit in the mailbox until deleted, so the history is readable on the day you first connect rather than accumulating from that day forward.
Why email rather than SMS
Most Indian expense apps historically read the SMS inbox instead, because bank alerts arrive there too and the text is shorter and easier to parse. That route is narrower than it used to be, though not closed.
On Android, Google Play’s policy on SMS and Call Log permission groups restricts those permissions to apps that are the user’s default handler for SMS, phone or assistant — the constraint Android’s developer documentation describes — unless the app holds an exception. The policy’s list of exceptions includes “SMS-based money management”, with apps that track and manage a budget given as the example, so an expense tracker can apply and is reviewed case by case. What the exception does not change is the scope: an approved app can read the whole inbox, one-time passwords included. For one-time verification alone, Google directs developers to the SMS Retriever API, which hands the app a single matching message rather than the inbox.
On iOS there is no public API for reading messages at all. Apple ships MessageUI for composing a message the user then sends. The one workaround runs on the user’s side: a Shortcuts personal automation can fire when a message arrives from a sender you name and pass its text on, but you build it yourself, sender by sender.
Email sidesteps the device question. A mail API is a documented, revocable, read-only integration on both platforms, which is why it behaves identically on an iPhone and an Android phone. That platform asymmetry is the reason most Indian expense trackers were Android-only, and the reason the ones that are not keep asking for the inbox — which raises its own question, whether granting an expense app SMS permission is safe. Both sit alongside every expense-tracking method compared.
What it takes for an app to read your Gmail
Email is not a free pass either. Read-only access to a Gmail inbox is what Google calls a restricted scope, its most sensitive tier. An app that stores or processes that data on its own servers has to pass Google’s verification and an independent third-party security assessment — the Cloud Application Security Assessment, or CASA — before it can offer the access widely, and has to repeat the assessment every 12 months, as a full test even if nothing has changed.
That is the right bar for something that can read your financial mail, and it is also why few Indian trackers offer Gmail access: the review costs time and money every year. An app that instead asks you to forward your bank alerts to an address it owns avoids the review entirely, because no scope is granted — your mail simply lands on its server. It is worth asking any email-based tracker which of the two it is doing.
What a parser can pull out of one alert
Take a single UPI debit notification. Stripped of its formatting, the useful content is roughly: an amount, a payee identifier, a timestamp, the last few digits of the account, and a reference number. From those five fields a parser produces one row.
Worked example, with the assumptions stated. Suppose a month contains 180 such alerts across one bank account and two credit cards. Assume each alert yields an amount and a date reliably, since those are numerically formatted and appear in a fixed position. Assume the payee string is reliable as an identifier but not always as a name. Then:
- Every one of the 180 rows has a correct amount, date and source account. The month's total outflow is exact, because it is arithmetic on numbers that were read directly rather than typed.
- Rows whose payee string is a recognisable merchant — a chain, a utility, a subscription — categorise themselves. In practice this is the majority.
- Rows whose payee is a raw VPA, typically a phone number with an
@handle, land in an uncategorised bucket until told once what they are. A neighbourhood grocer stays a phone number until you name it. - The remainder are transfers between your own accounts, which must be excluded or they will double-count — money moved from a bank account to a wallet is not spending.
The important distinction: the total is exact from the first day, because it depends only on amounts. The breakdown improves over the first few weeks, because it depends on naming. Any tool claiming a perfect category split on day one is describing something other than what the data supports.
Where it breaks
Cash is invisible. An ATM withdrawal produces one debit alert. What the cash then bought produces nothing at all. No parsing improvement fixes this, because the information was never created.
Merchant names are frequently unhelpful. A UPI alert carries the payee's Virtual Payment Address, which the recipient's bank assigned; it is an identifier, not a shop sign. Card alerts carry the merchant descriptor from the payment network, which is often an abbreviated legal entity name bearing little resemblance to the brand on the door.
Refunds and reversals arrive as separate credits, sometimes days later, and have to be matched back to the original debit or the month looks worse than it was.
Alerts can be switched off. On some accounts email alerts are off until you enable them in net banking, while SMS alerts are on. An account whose email alerts were never enabled contributes nothing, and the gap is silent — nothing indicates that a fifth account exists.
The honest test of any tracker is whether its monthly total matches your statements. If it does, the arithmetic is sound and the remaining work is naming things. If it does not, an account is missing or transfers are being counted as spending — and no amount of category polish fixes either.
Email against typing it in
The spreadsheet is the honest competitor here, and for the first fortnight it wins. It is free, private, arbitrarily flexible, and it forces attention on every rupee in a way an automated feed never will. It usually stops in the second week, and the reason is the form, not the idea: date, amount, category, note, save, forty times a month, at the moment you are least inclined to do admin.
The two answers to that pull in opposite directions. Email parsing removes the typing and gives up what only you know — the cash, the reason for a purchase, the friend who paid you back — in exchange for never missing a digital transaction. Typing or saying a sentence keeps all of that and makes each entry take seconds instead of a form, but it still depends on you doing it.
| Email parsing | A sentence, typed or said | |
|---|---|---|
| Access you grant | Read-only access to your mail | None (the microphone, if you speak it) |
| Cash | Invisible | Captured |
| Splits, transfers, refunds | Need correcting | Logged the way you meant them |
| Digital payments you forget | Captured | Missed |
| History before you start | Readable from the inbox | Starts from today |
| Effort per transaction | None | A few seconds |
Neither is complete on its own. For the question of where the money went, completeness on digital payments favours email; for the question of what you actually spent, cash and context favour typing it. Which suits you depends mostly on which one you will keep doing.
Where TLDR Classic stands
TLDR Classic takes the second route: you type what you spent the way you’d say it and it’s saved, with the amount, category and day worked out for you, and every entry stays editable. It does not read your email at all, and it asks for no SMS access and no bank login.
Questions worth asking
Which transaction emails does an expense tracker actually read?
Only the automated alerts a bank or card issuer sends when money moves — UPI debits and credits, card authorisations, salary and other credits, autopay mandate notices, and statement emails. These are machine-generated and follow a fixed layout per sender, which is what makes them parseable. Personal email, newsletters and receipts written by humans are not part of the record and are not needed to build one.
What if my bank sends SMS alerts but not email alerts?
Most Indian banks and card issuers send both, but the email alert is often switched off by default rather than absent. It is usually enabled under alert or notification preferences in net banking, listed separately from SMS. If a particular account genuinely sends no email at all, its transactions will not appear, and the honest answer is that the account has to be handled another way rather than assumed to be covered.
Can email-based tracking see cash I spend?
No. Cash leaves no electronic trail, so an ATM withdrawal appears as a single debit and everything you then spend that cash on is invisible. This is a real limitation rather than a temporary gap. The practical effect is that a withdrawal shows up as one lump under cash, and if a large share of spending is cash, the category breakdown below it will be correspondingly incomplete.
How far back can an expense tracker read my email history?
As far back as the alerts still exist in the mailbox, which is what makes email different from a live feed. Because the emails were already delivered and stored, past months can be read on the first connection instead of starting from zero. Anything deleted, or sent before alerts were switched on, cannot be recovered — the inbox is the archive, so its gaps become the record's gaps.
Why do merchant names in UPI alerts look like gibberish?
Because the alert carries the payee's Virtual Payment Address rather than a shop name, and a VPA is an identifier chosen by the recipient's bank or payment provider. A neighbourhood store might arrive as a phone number followed by an @ handle. The amount, date and account are exact; the human-readable name often is not, which is why categorisation needs correcting occasionally even when the arithmetic never does.
Related
Every method costs something. This one costs a sentence.
TLDR Classic turns a line you type, like “auto 120 yesterday”, into a saved entry you can still edit. It asks for no email access, no SMS access and no bank login. Every new account gets Pro free for 30 days, no card needed.
Sources
- Google Play Console Help, Use of SMS or Call Log permission groups — default-handler requirement, core-functionality limit, and the exception for SMS-based money management — support.google.com
- Android Developers, Permissions used only in default handlers — developer.android.com
- Google for Developers, SMS Retriever API — the sanctioned alternative to reading the inbox — developers.google.com
- Apple Developer Documentation, MessageUI — composing messages only; no public read API — developer.apple.com
- Google for Developers, Restricted scope verification — Gmail read access and the security assessment — developers.google.com
- Google Cloud Help, Annual recertification — restricted-scope apps reassessed every 12 months — support.google.com
- Apple, Shortcuts User Guide: communication triggers — personal automations on incoming messages — support.apple.com
This is an explanation, not advice about your money. TLDR Money is not a registered investment adviser and earns no commission on any product mentioned. Figures are illustrative; your own numbers, taxes and circumstances will differ.
