Expense tracking on iPhone in India: what actually works
You can track expenses on an iPhone in India — but not with an app that reads your bank SMS on its own, because iOS does not let any app do that. Apple has never shipped an API for reading the Messages inbox, and most expense trackers built for India were built on exactly that. What works on an iPhone is email alerts, a bank or Account Aggregator connection, a Shortcuts automation you set up yourself, statement imports, and telling the app what you spent. The methods that don’t depend on the handset — email, Account Aggregator and telling it yourself — behave the same on iPhone and Android.
Last updated
Public iOS APIs for reading your SMS inbox
The one platform rule that explains everything
In India, almost every rupee that moves generates a text message. A UPI debit, a card swipe, an ATM withdrawal, a salary credit — each one lands in your Messages app within seconds, in a fairly predictable format, from a fairly small set of senders. For anyone building an expense tracker, that inbox is the single richest source of transaction data in the country, and it needs no bank partnership, no regulatory approval and no integration work.
On Android, an app can ask for permission to read it. On iOS, it cannot ask at all.
Apple deliberately does not expose the Messages database to third-party apps, and there is no entitlement you can apply for that changes it. iOS does include a narrow message-filtering extension, intended to help sort texts from unknown senders into a junk folder — but it runs in a locked-down sandbox, it cannot hand message content back to the app that ships it, and it is useless as a transaction feed.
There is one workaround, and it runs on your side rather than the app’s. Apple’s Shortcuts app lets you build a personal automation that fires when a message arrives from a sender you name, or containing words you choose, and passes the text to a shortcut — which can hand it to an app that supports it. A few Indian apps rely on this. It works, with the catch that you build it yourself, sender by sender, and it stops matching when your bank changes the sender ID or the wording.
So an expense tracker whose automation is built on SMS parsing does not have a slightly worse iPhone app. Without that Shortcuts setup, it has no capture layer on iPhone at all. What usually happens next is one of two things: the app stays Android-only, or it ships an iOS version where the automation turns out to be manual entry. That single platform decision is why India’s expense-tracking market looks the way it does.
If you are shopping for an iPhone expense tracker
Ask one question before you install anything: where does this app get its transaction data on iOS specifically? If the answer is “SMS”, the automation you saw in the screenshots is Android-only unless you build a Shortcuts automation for it. If the answer is vague, assume manual entry.
What iOS actually allows
Here is every realistic way an app can learn about a transaction on an iPhone in India, and how each one holds up. This compares capture methods, not specific products — because the method is what determines whether an app can work on your phone at all. If you would rather see the same ground covered as a walkthrough, what actually works for tracking expenses on an iPhone takes each option in turn and states what it misses.
| Method | Works on iPhone | Automatic | The catch |
|---|---|---|---|
| An app reading bank SMS | No | — | No iOS API exists. Android-only by construction. |
| Shortcuts automation on bank SMS | Yes | Once set up | You build it yourself, per sender, and it breaks when the sender or wording changes. |
| Reading app notifications | No | — | Android exposes a notification listener; iOS has no equivalent. |
| Reading email alerts | Yes | Yes | Only covers accounts that actually email you. You may need to switch email alerts on in netbanking. |
| Bank login / Account Aggregator | Yes | Yes | Needs credentials or AA consent. Coverage varies by bank, and it is a much broader grant of access. |
| PDF statement import | Yes | No | Retrospective. You are reconciling last month, not seeing this one. |
| A sentence, typed or said | Yes | No | You still have to remember, but it takes seconds, and it is the only method that catches cash. |
| Manual entry, field by field | Yes | No | Works, but a form per purchase is what makes people stop by the second week. |
Two things fall out of that table. First, the iPhone problem is real and structural — the two techniques that made Indian expense tracking effortless on Android are both unavailable to an app. Second, the methods that never depended on the handset in the first place work on both phones without any porting at all.
Why some methods travel and others don’t
Email parsing works on an iPhone for a slightly boring reason: it never runs on your iPhone. Your mailbox lives on Google’s servers, and reading it is an account-level permission rather than a device-level one. An Account Aggregator connection is the same: it is a consent between your bank and the app, with the phone only as the place you tap “approve”.
Telling the app yourself travels for an even simpler reason: there is nothing to port. A sentence typed or said into an app behaves identically on iOS and Android, keeps working whatever Apple or Google change in their permission models, and needs no sensitive permission on either — at most the microphone. That argument gets its own page: expense tracking without SMS permission.
What email parsing does not fix
If you are considering an email-based tracker, check these limits before you commit:
- Coverage depends on your bank emailing you. Most major Indian banks and card issuers do send transaction and statement emails, but not universally and not for every alert type. Some accounts need email alerts switched on in netbanking first.
- Pure-cash spending is invisible. Nothing generates an alert when you hand over a note. That is true of SMS parsing too, and of every automatic method.
- Alert formats change. Banks redesign their emails. Any parser needs maintenance, exactly as SMS parsers do.
- It is not a bank feed. An alert tells you a transaction happened. It is not the same as a reconciled statement, and the numbers that matter are still worth checking.
Two very different ways to read your email
“It reads your email” describes two arrangements that have almost nothing in common, and the difference is the most useful thing to check on an iPhone tracker that offers it. One of them asks you to send your bank mail somewhere else. The other asks you to grant scoped access to where it already is.
| Forward to an alias | Scoped API access | |
|---|---|---|
| Where your bank mail lands | On a mail server the app owns | Stays in your mailbox |
| What you set up | A forwarding rule or filter | One permission grant |
| Scope | Whatever the rule matches, and anything it over-matches | Declared, and reviewed against the feature |
| Consent screen | None | Google’s own |
| How you revoke it | Remember the rule exists, then delete it | Your Google Account permissions page |
| Independent security review | None required | Required before the scope is granted, and every year after |
The revocation row is the one that matters most in practice. A forwarding rule has no expiry, no audit trail and no page listing it as an active connection. It keeps working after you delete the app, after you forget you set it up, and after the company is acquired by someone else. A scoped grant appears in your Google Account alongside every other app you have connected, and withdrawing it takes one click without the app’s cooperation.
Google classifies mailbox read access as a restricted scope — its most sensitive tier — and an app cannot simply request it and ship. It has to pass an independent third-party security assessment first, against the Cloud Application Security Assessment framework, and be re-verified every year. Asking someone to forward mail to an address you control routes around that entirely, because no scope is being granted at all.
The question to ask an email-based tracker
Does my bank mail stay in my mailbox, and can I revoke access without asking you? Both arrangements will honestly describe themselves as reading your email. Only one of them leaves the mail where it is and the off switch in your hands.
How TLDR Classic does it
TLDR Classic is on the App Store and Google Play, the same app on both. Nothing in it reads the handset: you type what you spent the way you’d say it, or say it, and it’s saved. “₹250 auto and ₹180 chai” becomes two entries, each categorised and dated.
Type it, or say it
A line becomes one entry or several, each categorised and dated, and every entry stays editable after it saves.
Ask what you spent
Ask how much went on food last month and the app counts the answer from your own entries, never the AI, and shows the entries behind it.
Built for both phones
No feature depends on SMS or reading notifications, so the iPhone version is not a reduced one. On iPhone it adds Siri and Lock Screen widgets.
There is no connection to your bank, your SMS or your mail, so there is no route into your accounts: moving money, placing a trade and opening an account are not things the app could do. Speech is turned into text on your phone and the audio is never recorded or sent, and Ask sends Claude, by Anthropic, your question with your category names, currency and date, never your totals or amounts, and only after you agree. What leaves your phone is set out on the security page, and your rights over the data are in the TLDR Classic privacy policy.
On iPhone, Pro can also log tap-to-pay Apple Pay purchases for you, through a Shortcuts automation you set up once. TLDR Money is funded by TLDR Classic’s Pro subscription alone: no ads on any plan, no referral fees, no fund distribution commissions, no lending arm. That argument is on the about page.
What to check before you pick one
- Ask where the iOS data comes from. If the automation is SMS-based, it is not coming to your iPhone unless you build a Shortcuts automation for it yourself.
- If it reads email, ask whether your mail moves. Being asked to set up forwarding to an address the app owns is a different arrangement from granting scoped access to your own mailbox. Both are described as reading your email.
- Ask how you switch it off. If the answer runs through the app’s own settings, you are trusting the app. A scoped grant is revoked from your Google Account without opening it.
- Check whether “automatic” means automatic for you. Some iOS builds of Android-first apps fall back to manual entry or statement upload, and setup that requires you to build a Shortcuts automation is worth knowing about before you install.
- Read the permission list and the scope. Broader access is not better; it is just broader. The least access that does the job is what you want.
- Find out how the app makes money. If nobody pays for it, the revenue comes from somewhere, and that somewhere shapes what the product shows you.
Keep reading
Questions worth asking
Can an iPhone app read my SMS to track expenses automatically?
Not on its own. iOS provides no public API that lets a third-party app read your Messages inbox, and Apple has never offered one. The SMS filtering extension sorts messages from unknown senders but cannot pass their content back to the app. The one workaround is a Shortcuts personal automation that you build yourself: it can run when a message from a sender you name arrives and hand the text to an app that supports it. Without that setup, an Indian expense tracker whose automation depends on reading bank SMS cannot deliver it on an iPhone.
Why are most automatic expense tracker apps in India Android-only?
Because they were built around bank SMS. In India nearly every UPI debit, card spend and salary credit generates an SMS, which made the inbox the cheapest reliable source of transaction data — and Android has a permission that lets an app read it. iOS has no equivalent. An app built on SMS parsing has no capture layer at all on iPhone, so it either ships Android-first or asks iPhone users to enter transactions by hand.
How can an expense tracker work on iPhone then?
By using a source that isn’t the SMS inbox. The realistic options are email alerts from your bank and card issuer, an Account Aggregator or bank connection, a Shortcuts automation you set up on your bank’s messages, importing PDF statements, or telling the app yourself — typing a sentence or saying it. Email, Account Aggregator and telling it yourself behave the same on iOS and Android, because none of them depends on the handset.
Can an iPhone app read notifications from my bank apps instead?
Not on iOS. Android exposes a notification listener service that an app can use to read notifications posted by other apps, which is how some trackers capture transactions without SMS. iOS has no equivalent API — an app cannot read another app’s notifications. This is the second reason capture techniques that work on Android don’t transfer to iPhone.
Is email-based expense tracking safe?
It depends on the scope the app requests and what it does with the data. Read-only access to your mail cannot move money, place trades or open accounts — those actions are not possible through a mail scope at all. What matters is whether the app requests the narrowest scope it can, whether your mail is parsed on the device or shipped to its servers, and whether it sells or shares the data. You can revoke a Google connection at any time from your Google Account permissions page, independently of the app.
Is TLDR Classic available on iPhone in India?
Yes. TLDR Classic is on the App Store, and on Google Play for Android. Nothing in it reads the handset, because you type what you spent the way you’d say it, or say it, so the iPhone version is not a reduced one. On iPhone it also has Siri, Lock Screen widgets and, on Pro, an Apple Pay automation that logs tap-to-pay purchases for you.
An expense tracker built for both phones
Type it or say it, ask what you spent, and see what’s left of each budget, on iPhone and Android. Every new account starts with 30 days of Pro, no card needed.
Platform behaviour described here reflects iOS and Android as of October 2026 and can change with an OS release. This is an explanation of how transaction capture works on each platform, not advice about your own money.
