Proof Season: Collecting 80C Evidence Without 80 Phone Calls

A business client has an accountant whose job includes answering you. An individual client has a job that has nothing to do with you, six investment apps, and a vague memory of an LIC policy. Proof season is the purest form of the document chase, and the most automatable. What follows is the full list itemised down to where each document actually lives, a week-by-week look at what changes when the ask goes out in April instead of January, and the three questions every firm eventually has to answer about regime choice, job switches and unprovable claims.

The list that never changes

Every individual client's proof list is knowable in the first week of April, before a single rupee of this year's tax planning has even happened. The categories don't change from client to client; only which rows apply does. That's the whole opportunity: a list you already know, sent to two hundred people who don't know they need it yet.

Why individuals procrastinate (and what breaks it)

Not defiance: decision fatigue. "Send your investment proofs" requires them to reconstruct what they own; that's a Sunday project, indefinitely postponed. "Download the ELSS statement from your mutual-fund app: takes two minutes" gets done from the metro. Specificity converts a project into an errand, and errands get done.

This is the entire design principle behind the table above. A generic ask produces a generic response: nothing, for weeks, followed by a panicked WhatsApp message on the last Friday of July asking what exactly is needed. An itemised ask, split row by row, produces small completions you can actually track. Ten rows sent as one paragraph feel like a chore. Ten rows sent as ten separate lines feel like ten two-minute tasks, and clients do those in whatever order is easiest, which is fine, because you're going to chase the leftovers anyway.

One client's proof week, twice

Take a salaried client we'll call Priya: a mid-level manager with a home loan, an LIC policy from her twenties, an ELSS SIP she barely thinks about, health cover for herself and her parents, and a rented flat she pays for by bank transfer every month. Nothing unusual, which is exactly why she's a good test case; most individual clients look like her.

Run her through a January ask. The message that reaches her reads something like "please share your investment proofs for filing." She reads it on her phone between meetings, means to deal with it that weekend, and doesn't. February passes with a reminder that says the same generic sentence. By March, the ask has been repeated three times without a single document arriving, because the ask never told her which app to open or what the file is called once she's in there. By June, with the deadline visibly close, she finally sits down for an hour on a Sunday, opens six apps she'd forgotten the passwords to, and sends everything at once, in one folder, with the rent receipts missing because she still hasn't messaged her landlord for his PAN. Filing happens in the last week of July, under pressure, with a gap in the file.

Now run her through an April ask instead. The financial year just closed; her ELSS SIP and LIC premium are still on her mind because she just made the last instalment. The message she receives is the itemised list, split by row, each one naming the exact app and the exact screen. She clears four of the eleven rows that same evening, because each one really did take two minutes. A reminder in May, listing only the seven rows still open, nudges three more. A message flags that her landlord's PAN is the one item that needs a person, not an app, giving her six weeks of runway to ask him instead of a panicked message on July 25th. By the third week of June, before anyone else's crunch has even started, her file is complete. Nothing about Priya changed between the two scenarios. The ask did.

Run it as a campaign, not a correspondence

Two hundred individual clients times eleven documents is not a correspondence a human should conduct one thread at a time. It's a campaign with a start date, a cadence, and a dashboard. Send the itemised list in April. Acknowledge every receipt the moment it lands, so clients aren't left wondering if the file they uploaded actually reached anyone. Auto-nudge only the specific rows still open for each client, never a generic "still waiting on documents" that makes them re-read the whole list to figure out what's missing.

By mid-June, the dashboard should show exactly which clients are complete, which are missing one or two specific rows, and which have gone quiet altogether. That last group, typically a small fraction of the roster, is the only one that needs a human phone call. July becomes filing month, which is what it was always supposed to be, instead of collection month wearing a filing-season costume.

Why April beats January, and January beats June

The timing of the first ask matters more than the wording of it. Right after the financial year closes, in April, a client's investment decisions are the freshest they will be all year: the last ELSS instalment was days ago, the home-loan certificate request just went in, the health-cover renewal is still in the inbox. Asking then means the client is retrieving something they just did, not reconstructing something they did nine months ago and half-forgot.

Ask in January instead, and you're asking someone to remember an LIC payment from the previous May. Ask in June, and you're asking them to do it under a deadline that's already visible on the calendar, which produces stress and gaps, not documents. April doesn't just buy more calendar time; it buys a client whose own memory is doing most of the work for you.

What about clients who switched jobs mid-year and have multiple Form 16s?

They need a slightly different first line in the ask, nothing more. Instead of "share your Form 16," the itemised list should say "share Form 16 from each employer you worked for this financial year," naming the number if you already know it from last year's data or from their onboarding. The document itself isn't harder to produce; the client just needs to be told explicitly that one Form 16 isn't the whole answer, because plenty of them assume it is and file with a gap in reported income that surfaces later as a mismatch against Form 26AS or AIS.

What if a client claims a deduction they can't actually produce proof for?

This is a documentation problem to surface early, not a legal question to resolve in a WhatsApp thread. The itemised ask, sent in April, is itself the early-warning system: a row that stays open for weeks, with no proof and no explanation, is a client who either hasn't gotten around to it or genuinely doesn't have the document. An acknowledgement-and-reminder ladder surfaces that gap in May, when there's time to have the conversation about what's actually claimable, rather than in the last week of July, when the pressure is to file something and sort out the evidence later. Catching the gap early doesn't resolve the underlying question of what to claim; it just makes sure that question gets asked by a person, on purpose, instead of getting skipped by accident.

Should the proof ask go out before or after the regime choice?

Before, generally. The itemised proof list and the old-versus-new regime decision are two separate questions that get needlessly tangled if you wait for one to answer the other. Collecting proofs doesn't commit anyone to claiming them; a client can gather every 80C and 80D document and still land on the new regime once the numbers are run, in which case the proofs simply go unused. Waiting until the regime is settled before asking for documents only shortens the collection window for no benefit, since the comparison itself is usually easier to do with the proofs already in hand: it's hard to compare what the old regime saves against the new regime's flat slabs when you don't yet know what a client's actual deductions add up to.