DECODING THE TREND Vol. 16 The Cash-Trail Odometer Why Property Buyers Cannot Treat ₹2 Lakh as a Safe Harbour

DECODING THE TREND | Vol. 16

The Cash-Trail Odometer

Why Property Buyers Cannot Treat ₹2 Lakh as a Safe Harbour

**By Arindam Bose| BeEstates Intelligence | Finance & Funding | Vol. 16 | AUGUST 2026**

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

Every Friday I promise myself this column will be the one that finally moves past compliance mechanics into pure market strategy. And every Friday, a reader's transaction reminds me why that promise keeps breaking — because in Indian real estate right now, the mechanics are the strategy.

The ₹1.85 Lakh Illusion

The buyer has paid ₹1.85 lakh in cash, six times.

No individual payment crossed ₹2 lakh. The broker says the limit was respected. The seller says the paperwork is clean. The buyer believes the transaction has been carefully engineered around the law.

But the tax system does not see six envelopes.

It sees one apartment. One buyer. One seller. One registration event. One PAN trail. One bank history. And one question that gets harder to answer with every fragment added to the pile: where did the money come from?

This is the mistake a surprising number of property investors are still making in 2026 — treating a statutory cash ceiling as a planning allowance rather than what it actually is: a compliance boundary. The ₹2 lakh restriction under Section 269ST was never written as an invitation to split a transaction into smaller cash portions. It applies not merely to what one person receives from another in a single day, but to a single transaction, and separately, to a set of payments connected to one underlying event or occasion. Six cash instalments of ₹1.85 lakh do not become six legally distinct events simply because someone paused between them.

The investor thinks in instalments. The system, increasingly, thinks in patterns. That gap is what this piece calls the Cash-Trail Odometer — the point at which scattered actions stop being separate acts and become one cumulative financial story.

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

THE THREE CASH BOUNDARIES INVESTORS CONFUSE

Most investors know exactly one number — ₹2 lakh — usually secondhand, from a broker or a relative or a WhatsApp forward. That shorthand is incomplete enough to be genuinely dangerous, because Indian property transactions actually run into at least three distinct cash-law ceilings, each built for a different kind of payment.

Provision	Core threshold	What it governs	Where property gets caught
Section 269ST	₹2 lakh	Cash receipts — daily aggregate, per transaction, or per connected event	Sale consideration, instalments, any single connected property deal
Sections 269SS / 269T	₹20,000	Cash loans, deposits, and "specified sums," plus their repayment	Token money, refundable deposits, informal advances, hand loans for a down payment
Section 40A(3)	₹10,000 per person, per day	Business-expenditure payments	Developers, contractors, brokers, material suppliers — not ordinary personal buyers

Each of these addresses a different actor in the same transaction. A homebuyer paying a seller in cash sits under Section 269ST. A buyer handing over token money or a refundable booking advance sits under Sections 269SS/269T — regardless of whether the deal later falls through. And a developer settling a contractor or a broker distributing commission in cash sits under Section 40A(3), where the consequence isn't a penalty on the recipient but a disallowed deduction for the payer.

The three provisions rarely get confused in isolation. They get confused in combination — when a single property transaction generates a booking token, an instalment schedule, and a developer's own supplier payments, all moving in the same rough window, each governed by a different rule with a different threshold and a different party on the hook.

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

WHY ₹2 LAKH IS NOT A SAFE HARBOUR

The phrase "below ₹2 lakh" has become one of the most misused sentences in informal property finance. It shows up in familiar forms: pay ₹1.90 lakh today, the balance later; split the token between family members; make separate cash payments for parking, interiors, and the flat itself; don't mention the full figure in one place.

None of it changes the underlying economic question, because Section 269ST was deliberately drafted to close exactly this gap. It doesn't test only whether a single receipt crossed ₹2 lakh in a day — it also asks whether the payments relate to one transaction, and separately, whether they relate to transactions tied to a single event or occasion. A buyer cannot argue that six cash instalments for the same apartment were legally unconnected merely because each fell under the ceiling. The apartment purchase is the economic event; the payment sequence is the evidence trail around it.

The penalty structure reflects how seriously this is treated: a breach under Section 271DA exposes the recipient — typically the seller, developer, or broker — to a penalty equal to the entire amount received in contravention, subject only to a "good and sufficient reasons" defence that the taxpayer must affirmatively establish. The fact that the penalty lands on the receiver, not the payer, doesn't make the payer safe. It simply means both sides carry different exposures on the same transaction.

The investor's mental model needs to shift from what is the largest cash amount I can move today to can I reconstruct the entire financial chain of this transaction, from source to settlement, a year from now if asked. That second question is the one that actually reflects how scrutiny works in 2026.

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

THE PROPERTY TRANSACTION AS A BUILT-IN DATA TRAIL

What makes a fragmented cash strategy so fragile is that a resale property purchase in India is no longer a private bilateral arrangement observed only by the two parties. It automatically generates a data trail across at least four separate reporting channels, each feeding the same PAN — and under the Income Tax Rules, 2026, effective April 1, 2026, that trail has actually widened rather than narrowed.

Identity. The mandatory PAN-quoting threshold for buyers and sellers at the registry desk now sits at ₹20 lakh, up from the historical ₹10 lakh under the old Rule 114B. Cross this figure — on either the declared consideration or the stamp-duty valuation — and both parties must furnish and digitally verify PAN/Aadhaar before the deed can proceed.

Reporting. Separately, and at a materially higher figure, the Sub-Registrar's own SFT reporting obligation — now governed by the successor framework to old Rule 114E — has moved to ₹45 lakh. Cross that mark and the registry is statutorily required to transmit buyer and seller PAN, declared consideration, stamp-duty value, and full property identifiers to the Income Tax Department, now via Form No. 165, populating both parties' Annual Information Statements. The 2026 framework also expanded what counts here: gift deeds and Joint Development Agreements above ₹45 lakh are now captured by the same reporting net, closing off two routes that previously sat outside it.

Valuation. The sub-registrar's system independently computes the circle-rate/ready-reckoner value for the property and compares it against the declared consideration. Where the declared figure falls short, the higher stamp-duty value is used for stamp duty purposes and simultaneously flagged toward the Income Tax Department as a potential valuation gap.

Withholding. Since April 1, 2026, a buyer's TDS obligation on property consideration above the Section 194-IA/393(1) threshold is filed through the new consolidated Form No. 141 — replacing four legacy forms, including the old Form 26QB — with the certificate to the seller issued as Form No. 132 in place of Form 16B.

The practical result of the dual-threshold structure is worth stating plainly: PAN identity capture now kicks in at ₹20 lakh, but the outward reporting to the tax department doesn't wait for that same figure — it fires independently at ₹45 lakh, or immediately for a gift deed or JDA crossing that mark regardless of whether cash was ever involved. A transaction can clear the PAN-quoting bar quietly and still land squarely inside the SFT dragnet once its value crosses the higher line.

The current dual-threshold position

Trigger	Threshold	What activates
PAN Mandate	≥ ₹20 lakh	Buyer and seller must furnish and verify active PAN/Aadhaar at the registry
SFT Reporting (Form No. 165)	≥ ₹45 lakh	Sub-Registrar automatically reports sale, purchase, gift deed, or JDA to the IT Department

None of these four channels needs the others to function. Each fires independently. That's precisely why a cash instalment doesn't sit in a vacuum — it sits beside a registered deed, a PAN match, a TDS filing, and now a wider SFT net than existed even a year ago.

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

THE AGGREGATE CASH-TRAIL ODOMETER

The registry trail is only one instrument in a larger data orchestra. Banks separately report aggregate cash deposit behaviour once it crosses statutory thresholds — historically pitched at ₹10 lakh a year for savings accounts and ₹50 lakh for current accounts — and that aggregation runs at the entity level, not the branch level. Depositing ₹4 lakh at one branch, ₹4 lakh at another, and ₹3 lakh at a third of the same bank in a year does not produce three invisible events; it produces one visible ₹11 lakh figure against a single PAN.

The same aggregation logic governs credit-card cash settlements, term-deposit placements, and mutual fund subscriptions — each independently reported once a threshold is crossed, each independently landing in the same Annual Information Statement.

This is the Odometer at work: a buyer who thinks in isolated events — a cash deposit here, a token payment there, a property registered somewhere else entirely — is, from the tax department's side, generating one continuous reading. The AIS ties salary, bank interest, mutual fund activity, share transactions, and immovable-property matches into a single ledger under one PAN. The Taxpayer Information Summary condenses that ledger into the figures that auto-populate a return. And a mismatch anywhere in that chain — an ₹80 lakh property purchase sitting beside a return that shows ₹6 lakh in annual income — doesn't require a raid to surface. It surfaces automatically, through the department's own compliance-portal matching engine, well before any human officer looks at the file.

What the investor thinks vs. what actually becomes visible

Event	What the investor assumes	What actually becomes visible
Cash instalment below ₹2 lakh	"No threshold crossed"	May still connect to one property event across the transaction as a whole
Property purchase above ₹45 lakh	"It's a registry-office matter"	Automatic SFT transmission via Form No. 165 to both parties' AIS
Gift deed / JDA above ₹45 lakh	"No cash changed hands, so no trail"	Now independently reportable under the 2026 framework
Bank cash deposit	"It's my own account"	Aggregate deposit behaviour, PAN-wide, can independently become reportable
TDS on the purchase	"A filing formality"	A direct data match linking buyer, seller, property value, and payment date

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

WHEN UNEXPLAINED MONEY BECOMES EXPENSIVE

The moment a mismatch surfaces, the conversation shifts from procedural TDS compliance to something considerably more punitive: the deeming provisions under Sections 68 through 69D, which cover unexplained cash credits, unexplained investments, unexplained money, undervalued or undisclosed investments, and unexplained expenditure.

Any amount swept into these categories is taxed under Section 115BBE at a flat rate that strips away nearly every normal defence — a 60% base rate, a 25% surcharge on that base, and a 4% cess on the combined figure, landing at an effective 78%. No deduction for acquisition cost or associated expenditure is permitted against this figure, and no set-off against current-year losses, unabsorbed depreciation, or carried-forward capital losses is allowed. If the discrepancy surfaces through an assessing officer's own inquiry rather than the taxpayer's voluntary disclosure, an additional penalty under Section 271AAC pushes the effective extraction to roughly 84%.

Before any of that, though, the department's e-Verification workflow typically runs a gentler first pass: an automated SMS or email flag, a request to respond via a drop-down — correct, not fully correct, belongs to another PAN, or denied — and, where the taxpayer concedes the transaction but cannot evidence a legitimate source, an invitation to file an updated return under Section 139(8A) to settle the gap voluntarily before it escalates into a full assessment.

The pattern that keeps surfacing in tribunal rulings reported across the tax press is a familiar one: a cash deposit made shortly before a property payment, with the taxpayer explaining it as accumulated family savings or a relative's hand loan, and the explanation failing because the taxpayer could not independently establish the lender's identity, creditworthiness, and the genuineness of the transaction — the three-part test tribunals routinely apply. Where that test fails, the shortfall gets swept into Section 69 or 69A and taxed at the flat 78% rate, with no room to argue the money was "just a loan." Readers researching this vertical should treat the specific case names circulating in secondary tax commentary as illustrative of the mechanics rather than as independently verified citations — the pattern is well documented; the exact tribunal references deserve a direct check against ITAT records before being printed as case law.

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

THE ₹1 CRORE PURCHASE — A FORENSIC WALK-THROUGH

Consider a Bengaluru resale flat priced at ₹1 crore, funded through ₹20 lakh of the buyer's own money and an ₹80 lakh home loan — the same illustrative structure this column used for Vol. 15's programmable-rupee scenario, run here through the cash-and-reporting lens instead.

Booking stage. The buyer pays a token advance to reserve the unit. If any part of that token is paid in cash and equals or exceeds ₹20,000, it falls squarely within the Section 269SS "specified sum" category — a rule that applies whether or not the sale ultimately completes. A cash refund of that same token later, if the deal collapses, triggers the mirror rule under Section 269T.

Funding stage. The buyer's ₹20 lakh contribution and the lender's ₹80 lakh disbursal both move through banking channels, as RBI end-use monitoring for home loans effectively requires. Any cash component layered on top of this — say, an "on-money" adjustment to bridge a circle-rate-to-market-value gap — immediately falls under the Section 269ST receipt test from the seller's side.

Registration stage. At the sub-registrar's office, PAN and Aadhaar are captured and verified for both parties since the deal clears the ₹20 lakh identity threshold. Because the transaction value also clears the ₹45 lakh SFT threshold, it is automatically reported to the Income Tax Department via Form No. 165, populating both PANs' AIS entries — independent of, and in addition to, the PAN capture itself.

Withholding stage. Since the deal exceeds the Section 194-IA/393(1) threshold, the buyer deducts 1% TDS on the higher of consideration or stamp value, files Form No. 141, and issues the seller a Form No. 132 certificate — a transaction-level data point that independently corroborates the registry filing.

Reconciliation stage. Roughly a year later, the system cross-references all four trails against each other and against both parties' filed returns. A seller whose declared sale consideration doesn't match the stamp-duty value gets flagged under Section 50C/56(2)(x). A buyer whose bank statements show a cash deposit shortly before any instalment gets flagged for source-of-funds explanation. Anything that survives that first automated pass and still doesn't reconcile moves toward the deeming provisions discussed above.

What this walk-through actually demonstrates

Point in the transaction	Reporting channel triggered
Booking token in cash ≥ ₹20,000	Section 269SS specified-sum exposure
Buyer/seller PAN at registration (≥ ₹20 lakh)	Rule-based PAN verification, digitally checked
Declared value vs. stamp value	Section 50C/56(2)(x) valuation-gap flag
TDS deduction and filing	Form 141/132 — direct buyer-seller-property match
Transaction above ₹45 lakh	Form No. 165 — Sub-Registrar to AIS, both parties
Cash deposit near payment dates	Bank SFT — separate, PAN-wide aggregation

No single one of these six triggers is dramatic in isolation. Together, they leave very little room for a transaction to exist off the record.

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

WHAT HIGH-VOLUME BUYERS SHOULD TRACK QUARTERLY

For an investor active across multiple property transactions in a year, the useful discipline isn't a tax-avoidance checklist — it's a reconciliation habit, run every quarter, well before any of it becomes a department query.

Match every property payment — cash or otherwise — against the specific transaction and event it belongs to, not just the day it was paid, since that's exactly the test Section 269ST applies.
Keep booking tokens, refundable deposits, and informal advances documented from day one; treat anything at or above ₹20,000 as a "specified sum" regardless of how preliminary it feels.
Track any gift deed or Joint Development Agreement against the ₹45 lakh SFT line separately from cash transactions — the 2026 framework now reports these even where no cash is involved at all.
Track cash deposits made in the weeks around any property payment as a linked event, not an isolated banking action — the system already treats them that way.
Confirm the declared consideration on every deed against the local circle rate before signing, since the gap itself is the trigger, not the intent behind it.
Retain a documented, verifiable source for every large fund movement — salary history, loan sanction, prior asset sale — before the AIS mismatch engine asks for one.

Context worth flagging for readers: with the top-8 metro market now running 50%+ of unit sales above ₹1 crore, most ordinary urban resale transactions today clear both the ₹20 lakh PAN threshold and the ₹45 lakh SFT threshold as a matter of course — meaning the share of transactions structurally outside this reporting net is shrinking every quarter, not growing.

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

THE FALSE COMFORT OF FRAGMENTATION

Return, for a moment, to the buyer who paid ₹1.85 lakh six times.

Nothing about that sequence changes the underlying economic event: one apartment changed hands, for one price, between one buyer and one seller. Splitting the payment doesn't split the transaction — it simply adds six additional data points to a trail that was already going to exist through the registry, the TDS filing, and the SFT report. If anything, the fragmentation itself becomes evidence of intent, since the law's "single transaction" and "one event or occasion" tests exist precisely to catch this pattern.

The comfort a buyer feels from staying under ₹2 lakh per payment is real — but it's comfort borrowed against a system that was specifically redesigned, through the 2026 rules widening both the PAN and SFT nets, to stop caring about the size of any one envelope and start caring about the shape of the whole transaction.

⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡

THE CLOSING QUESTION

The right question was never how much cash can I use today without crossing a line.

It's can I explain the entire financial chain of this property transaction — source, sequence, and settlement — one year from now, to someone who has already seen all four trails before I've said a word.

For most buyers in 2026, the honest answer to that second question, not the first, is what now determines whether a property purchase stays a routine registry event or becomes the opening move in a source-of-funds inquiry.