Investment Declarations and Proofs: A Payroll Guide

Every Indian payroll team runs the same loop each year, and most of them run it badly. In April you ask employees to commit to an investment declaration — a forward-looking statement of the deductions and exemptions they expect to claim. You use that statement to work out how much tax to withhold from each month's salary. Then, somewhere in the last quarter of the financial year, you ask the same employees to prove what they claimed. Whatever they cannot prove gets stripped out, the year's tax is recomputed, and the shortfall has to come out of the payslips that are still left. That is the entire mechanism, and almost every February and March complaint you receive traces back to it.

The difference between a calm season and a chaotic one is not tax expertise. It is operations. Teams that handle the tax declaration process well set dates early, publish a written verification standard, tell employees three times what is coming, and use a system that tracks status per employee per category instead of a shared folder of email attachments. Teams that handle it badly discover in the second week of February that four hundred people submitted nothing, that the rent receipts have no landlord details, and that the recompute has pushed a third of the workforce into take-home numbers they were not warned about. This guide walks through the full cycle — the timeline, the regime choice, category-by-category investment proof submission standards, the verification playbook, the communication plan, the edge cases, and what changes when you stop running proof of investment payroll on spreadsheets.

One standing caveat before anything else: tax rules, deduction limits, thresholds, regime parameters and filing dates change, sometimes every year. Nothing here quotes a rate, a limit or a date on purpose. Confirm every current figure with the income tax department's official site or your tax advisor before you publish anything internally.

What the Declaration Cycle Actually Is

Why the employer sits in the middle

Salary in India is taxed at source. The employer is required to estimate each employee's tax for the full financial year and deduct roughly one-twelfth of it every month, adjusting as circumstances change. That estimate cannot be made without knowing what the employee intends to claim — rent paid, insurance premiums, retirement contributions, home loan interest, and so on. So the employer asks. The employee answers with a declaration. The employer withholds on that basis.

This is a trust-then-verify arrangement, and the trust half comes first by design. An employee who plans to buy an insurance policy in the third quarter is allowed to declare it in April and receive the benefit of lower monthly deductions from month one. The employer is not required to hold back the benefit until the money is actually spent. What the employer is required to do is confirm, before the year closes, that the declared item actually happened — and to fix the withholding if it did not.

Declare first, prove later

Think of the financial year as two halves that behave differently.

The first half is estimation. The declaration is a forecast. Nobody has spent anything yet in many cases. Payroll applies the declared amounts, computes projected annual tax, divides by the remaining months, and deducts. Employees see a comfortable take-home number and stop thinking about tax.

The second half is substantiation. Payroll collects documents, checks them against what was declared, and accepts, reduces or rejects each line. The accepted total replaces the declared total. Payroll recomputes the year's tax on the revised figure, subtracts everything already deducted in the earlier months, and spreads the balance across the months that remain.

That last sentence is the whole problem. The balance does not get spread over twelve months. It gets spread over however many months are left — often two or three. A modest gap between declaration and proof produces a very immodest jump in a single payslip.

What "reversal" means on a payslip

When an employee declares an amount and cannot support it, payroll does not penalise them. It simply removes the unsupported amount from the computation. The tax that should have been deducted all along becomes payable now. Employees experience this as a punishment — "you cut my salary" — when it is arithmetic catching up. The quality of your communication determines which of those two stories the employee believes.

There is a second, quieter consequence. The year-end salary tax statement the employer issues reflects only what the employer accepted. If an employee genuinely made an investment but missed your proof window, the deduction will not appear in that statement. They can still claim it when filing their personal return and seek a refund, but that is a slower and more anxious path than getting it right in payroll. Say this out loud to employees. It reduces panic considerably.

The Annual Timeline of the Tax Declaration Process

Below is a working calendar used by many Indian payroll teams. Treat the months as typical practice, not legal fact — your organisation's internal dates are yours to set, and statutory deposit and filing dates must be confirmed separately with the income tax department or your advisor.

Build the calendar backwards

Most teams pick the proof window first and let everything else fall where it may. Work in the other direction. Decide the last payroll in which you can absorb a recompute comfortably, then count backwards:

1. Final payroll input freeze. The last date payroll inputs lock for the year.
2. Recompute completion. At least one full payroll cycle before that freeze, so the numbers can be checked.
3. Verification completion. At least two weeks before recompute, allowing a query-and-resubmit round.
4. Proof window close. At least three weeks before verification completion, so the reviewing team is not verifying and recomputing simultaneously.
5. Proof window open. Four to six weeks before it closes. Shorter windows generate a submission spike your reviewers cannot absorb.
6. Advance notice. Two to three weeks before the window opens, so employees have time to request documents from insurers, banks and landlords, which take time to arrive.

Publish all six dates in April, in the same message as the declaration form. Employees who know in April when proofs are due behave differently in December.

Why the mid-year revision window earns its keep

Plenty of teams skip the mid-year window because it creates work. It prevents far more work than it creates. Between April and December, people change rented houses, close home loans, stop paying premiums on lapsed policies, get married, have children, take on education loans, or simply realise their April declaration was aspirational. Catching those changes at the mid-point means the correction is spread over six months instead of two. A revision window is the cheapest shock absorber available to you.

Keep it short — a week or ten days — and make one rule explicit: revisions must be realistic, because December is not far away and the proofs will be checked.

Regime Choice: The Decision That Shapes Everything Else

India currently operates two personal income tax regimes for salaried individuals. One is the older structure, which permits a wide range of exemptions and deductions in exchange for a different rate structure. The other is the newer structure, which pairs a different rate structure with a much shorter list of permitted deductions. Rates, thresholds and the precise list of what survives in each regime change from time to time, and the default that applies when an employee says nothing has also changed in the past. Check the current position on the income tax department's site every single year before you publish internal guidance. Do not recycle last year's comparison sheet.

What the choice actually changes for payroll

The regime choice is upstream of everything else in the declaration. If an employee selects the newer regime, most of the categories in your declaration form stop mattering to their computation, and collecting proofs for them is wasted effort on both sides. If they select the older regime, the entire proof matrix applies and verification workload rises sharply.

This has three operational implications:

• Your declaration form should ask for the regime first, then show only the relevant categories. A form that asks a newer-regime employee to declare rent, insurance and tuition is generating noise you will have to clean later.
• Your proof reminder emails should be segmented by regime. Sending a full proof checklist to employees for whom it is irrelevant destroys the credibility of your reminders.
• Your verification capacity planning depends on the regime split. Count heads by regime in April and you will know in April roughly how many proof files you will be reviewing in January.

A decision framework, not advice

Payroll should never tell an employee which regime to pick. That is personal tax advice, and it is not your role or your risk to carry. What you can do is give people a structured way to think, and point them to the official calculator and to their own advisor.

The honest framework is short:

• Deduction-heavy profiles tend to favour the older regime. Someone paying substantial rent in a metro, servicing a home loan, contributing meaningfully to retirement savings, paying health insurance premiums for themselves and dependent parents, and paying school fees has a large stack of claimable items. When that stack is big enough relative to their salary, the older regime's broader allowances can outweigh the newer regime's rate structure.
• Simple salary profiles tend to favour the newer regime. Someone living with family or in company-provided accommodation, with no housing loan, modest insurance, and no dependants generating claims has little to claim. For them the newer regime is usually both simpler and cheaper, and it removes the entire proof burden.
• The break-even is personal and it moves. It depends on salary level, salary structure, actual spending, and the current year's parameters. It is not a rule of thumb you can publish. Two employees on identical CTC can land on opposite answers.
• Discipline matters as much as arithmetic. An employee who declares a large stack of deductions under the older regime and then fails to actually invest or fails to collect documents will end up worse off than if they had chosen simply. The older regime rewards people who follow through.

Give employees the official calculator link, a plain-language description of the two structures, and a firm statement that payroll cannot choose for them. Offer an optional session with an external advisor if your budget allows; it pays for itself in reduced helpdesk volume.

Mechanics payroll must get right

• Capture the choice in writing, per employee, per year. Not in an email thread. In a stored record with a timestamp.
• Know and publish the default. If an employee does not respond, something happens by default. Employees must be told what that default is before it is applied, and told again when it has been applied.
• Decide your internal switch policy. The law governs what an individual can do when filing their own return; your payroll policy governs what you will process and when. These are different things and employees confuse them constantly. Write down the internal position: switching is permitted until a stated internal cut-off, after which payroll will not reprocess, and any remaining benefit must be pursued by the employee when filing their own return. Apply it uniformly.
• Flag inconsistencies. An employee in the newer regime who uploads a stack of insurance receipts either misunderstood the regime or intended to switch. Catch it during verification rather than after the recompute.

What Employees Declare and What Proof Looks Like

Below is a reference matrix covering the categories that appear on almost every Indian declaration form. Use it as the backbone of both your employee checklist and your reviewer checklist. Availability of each item depends on the regime chosen and on current rules — verify before publishing.

House rent

This is the highest-volume, highest-risk category in Indian payroll, so it gets its own treatment further down. At the matrix level, remember that the rent exemption only applies if the employee's salary structure actually contains a rent allowance component and the employee actually pays rent for accommodation they occupy and do not own. Employees frequently declare rent when neither condition holds.

Verifiers should check that receipts cover the exact months claimed, that the monthly amount matches the agreement, and that the landlord is identified. Partial-year claims are legitimate and common — someone moves in July, or moves between cities — so do not reject a partial claim, just confirm the period.

Home loan interest and principal

Two separate claim lines come from one document. The lender's certificate shows both the interest charged and the principal repaid for the year, and employees routinely declare the total EMI as though it were all deductible. Verifiers should split the two and apply each to its own category.

Ownership matters more than payment. A person who pays the EMI on a property owned solely by a parent is not the claimant. Where there are co-borrowers and co-owners, the claim should be proportionate and the same amount should not be claimed in full by two people in two different companies. You cannot police what happens at another employer, but you can ask the employee to state the share they are claiming and keep that statement on file.

Property status matters too. A property still under construction is treated differently from one that has been handed over, and a let-out property brings rental income into the picture. If an employee declares a large housing loss, ask for the interest certificate and the rent position together.

Life and health insurance

Life insurance proof is simple in concept and messy in practice: employees upload policy documents instead of premium receipts, or receipts from a previous year, or a premium notice showing an amount due rather than paid. The verifier's job is to confirm the amount was paid within the financial year and the policy is in force.

Health insurance adds two wrinkles. First, coverage for dependent parents is often treated separately from coverage for the employee's immediate family, so the receipt needs to show who is covered. Second, the payment mode can matter for eligibility. A cash premium receipt should trigger a query rather than an automatic accept. Preventive check-up expenses, where they are claimable, need their own evidence and are commonly confused with general medical bills.

Retirement savings and pension contributions

Employer-routed contributions are usually already visible in your own payroll data and should be pre-populated rather than declared. It is the employee's voluntary contributions and personally held accounts that need proof — a contribution statement, a passbook extract or a transaction confirmation showing the date, amount and account holder.

The single most common error is a contribution made after the financial year closes being claimed for the year that just ended. Date discipline is the whole verification here. The second most common is a statement that shows a balance rather than the contributions made during the year; a balance tells you nothing about what was deposited when.

Children's tuition fees

School receipts in India often bundle tuition, transport, activity charges, building fund and admission fees into a single figure. Only the tuition component is claimable. If the receipt does not break the fee out by head, the verifier should ask for a fee structure or a revised receipt rather than guess.

Other frequent issues: receipts for more children than the rules permit, receipts in the name of a grandparent who actually paid, receipts covering an academic year that straddles two financial years without a date breakdown, and coaching class or tuition centre receipts which are not the same thing as school tuition fees.

Savings-scheme deposits and small savings

These are usually straightforward — a passbook page, a deposit certificate or a bank statement line. The verifier checks that the deposit falls inside the financial year, that the account holder is the employee or an eligible family member under current rules, and that the scheme is one that qualifies. Watch for employees submitting the same deposit twice under two different categories, and for term deposits that are ordinary deposits rather than the tax-saving variant.

Donations

Donations are the category most likely to be deferred to the employee's own return. Some contributions can be given effect through payroll and some cannot, and the answer depends on the receiving institution's category under current rules. Rather than making a judgement call per receipt, decide a clear organisational position: either payroll processes only a defined and named set of institutions and defers everything else, or payroll defers all donation claims to the personal return. Publish whichever you choose in April. Employees can still claim what payroll declines when they file.

Where you do process donations, the receipt must identify the institution, carry its registration details and PAN, state the donor's name correctly, and show a payment mode that is acceptable under current rules.

Education loan interest

The proof is a lender certificate showing interest paid during the year. Only the interest counts; employees routinely submit the total repayment. The relationship between the borrower and the student matters and is defined in the rules, so a loan taken for a sibling or a nephew is not automatically claimable. Check the certificate names before accepting.

Disability and medical treatment claims

These are sensitive categories and should be handled by a named senior reviewer, not by a general queue. Two things matter: the certificate must come from the prescribed authority, and it must be valid for the year claimed. Certificates carry validity periods and expire; an employee claiming for the fourth consecutive year on a certificate issued years ago may need a fresh one.

For treatment-related claims, any amount reimbursed by an insurer or by the employer reduces what can be claimed, so the disclosure of reimbursement is part of the proof, not an optional extra. Handle all of this with discretion. Restrict document access, avoid circulating details in group email, and do not ask for medical information beyond what the claim requires.

Previous employer salary and TDS

When someone joins mid-year, your payroll only sees the part of their income you paid. If you compute tax only on that part, you will under-deduct, because the earlier income pushes the employee's total higher. The fix is to collect the prior employer's salary and tax statement, or the prescribed disclosure, and fold it into the annual projection.

Employees resist this. They do not want the new employer to see the old salary, and they would rather deal with it at filing time. Explain the trade-off plainly: disclose now and the tax is spread across your remaining months here; withhold it and you will face a lump sum when you file, plus possible interest. Make the ask part of onboarding, not part of December.

If an employee declines, record the refusal, compute on what you can see, and warn the employee in writing that their tax may be under-deducted. Do not quietly assume it will sort itself out.

Income or loss from house property

Employees may ask you to consider a loss from house property — typically where interest on a housing loan exceeds the rent received, or where a self-occupied property generates interest with no rental income. Payroll can factor this in, but only with the supporting interest certificate and, for let-out property, the rent details and municipal taxes paid.

The pattern to watch for is asymmetric declaration: the employee declares the interest but not the rental income. Ask for both sides. Also note that current rules cap how much house property loss can be set off against salary in a year; confirm the present position before configuring your payroll rules.

Rent Claims, Landlord PAN, and the Fraud Patterns Everyone Sees

Landlord PAN

Where annual rent crosses a threshold set by the tax department, the employee is required to furnish the landlord's PAN, along with the landlord's name and address. Below that threshold, PAN is not required. Do not publish the threshold figure from memory — look it up each year and put the current number in your checklist.

The operational problems are predictable. Landlords refuse to share PAN. Employees supply a PAN that fails a basic format check. Employees supply the PAN of a relative rather than the actual owner. Or an employee whose rent sits just under the threshold declares an amount suspiciously close to the line.

Handle it with a rule, not a negotiation. If PAN is required for the amount claimed and PAN is not provided, the claim is limited to what can be supported without it, and the employee is told this in the rejection reason. Where the landlord genuinely refuses, current practice in many organisations is to accept a declaration from the landlord stating they do not hold a PAN, along with their address — check whether that route is still valid before relying on it.

Rent receipts that stand up

A receipt that is worth verifying contains the landlord's name and address, the tenant's name, the property address, the period covered, the amount, the mode of payment, and the landlord's signature. Receipts that cover a full year in a single line, written on the same day in the same pen, with a revenue stamp casually stuck on, are technically receipts and practically evidence of nothing.

The stronger standard, and the one increasingly used, is to pair receipts with a rent agreement and a payment trail. A bank transfer to the landlord each month is the cleanest evidence in this entire category. Encourage it in your April communication, well before anyone is scrambling in January: employees who pay rent by transfer have a painless proof season.

Rent paid to family members

Paying rent to a parent, spouse or sibling is not automatically illegitimate. A person can genuinely rent a portion of a property owned by a parent and genuinely pay for it. What makes these claims risky is that they are also the easiest claims to fabricate, and tax authorities know it.

Set a consistent internal standard for family rent claims and apply it to everyone:

• The landlord must actually own the property, and ownership evidence should be on file.
• A rent agreement must exist.
• Payment must be traceable through a bank transfer, not cash.
• The employee cannot be a co-owner of the property they claim to rent.
• The claim must be plausible relative to the property and the locality.

Employees will point out that you are asking more of family claims than of third-party claims. You are, and the reason is defensible: family claims lack the natural arm's-length check that a stranger landlord provides. Write the reason into your policy so reviewers are not arguing it case by case.

The patterns payroll teams actually see

• The round-number year. Twelve identical monthly receipts totalling a suspiciously round figure, declared at exactly the level that maximises the exemption.
• The threshold hugger. Rent declared just below the level at which landlord PAN becomes mandatory.
• The phantom period. Receipts for months the employee was demonstrably living elsewhere, in company accommodation, or on an overseas assignment.
• The duplicate landlord. The same landlord name and PAN appearing across unrelated employees who live in different cities.
• The self-rental. Rent claimed on a property the employee owns, sometimes the very property for which they are also claiming home loan interest as self-occupied.
• The spouse split. The same rent claimed in full by two spouses working at two different companies.
• The late conversion. An employee who declared nothing in April suddenly producing a full year of rent receipts in January, generated in one sitting.

Verifying without playing tax officer

Your job is to apply a reasonable, documented standard consistently. It is not to run an investigation, demand explanations of someone's family arrangements, or make accusations you cannot support. Three principles keep this balanced:

1. Objective criteria only. Rejections should cite a missing document, a date mismatch, a name mismatch or a format failure — never a suspicion.
2. Same standard for everyone. If you require a payment trail for family rent, you require it from the intern and from the CFO. Selective rigour is the fastest way to turn a process issue into a grievance.
3. Escalate rather than adjudicate. Where something looks fabricated, the reviewer's action is to escalate to a named owner in finance or HR, not to confront the employee. The organisation decides how to handle suspected falsification; a reviewer does not.

And say the quiet part to employees in writing, once, without drama: payroll's acceptance is not a tax authority's acceptance. The individual remains responsible for what they claim in their own return, and documents may be asked for years later. That single line does more to discourage inflated claims than any verification process.

Perquisites and Reimbursements Are Not Declarations

A meaningful share of proof-season confusion comes from employees mixing up three different things.

Declarations are the employee's own investments and expenses that reduce taxable income. The employee spends their own money and claims a benefit.

Reimbursements are the employer paying the employee back for something, against bills, under a company policy. Fuel and driver reimbursement, telephone and internet, books and periodicals, and similar components sit here. The bills go to payroll, but they are governed by company policy and by rules about what can be paid tax-free, not by the investment declaration. They usually have their own submission cycle and their own cut-offs.

Perquisites are benefits the employer provides that are themselves taxable in the employee's hands — company accommodation, a company car available for personal use, interest-free or concessional loans, employer-funded club memberships, and stock-based benefits at the relevant trigger. These increase taxable income rather than reduce it, and their valuation follows prescribed rules that payroll applies; the employee does not declare them.

Practical consequences:

• Keep reimbursement claims on a separate form and a separate schedule from the investment declaration. Mixing them means fuel bills land in the proof queue and rent receipts land in the reimbursement queue.
• Tell employees plainly that submitting bills for a reimbursement component is not the same as claiming a deduction.
• Make sure perquisite values are loaded into the annual projection early, not discovered at recompute. An employee in company accommodation who learns in February that a perquisite value has been added to their income all year will be, reasonably, upset.
• Where an employee has both a rent allowance component and company-provided accommodation for different parts of the year, handle the switchover explicitly. This is a classic source of double benefit and of angry corrections.

The Verification Playbook

Decide your posture before the window opens

There are two coherent postures and one incoherent one.

Full verification means every submitted document is opened and checked. It is defensible, predictable, and expensive. It is the right choice for small headcounts, for organisations with a low risk appetite, and for any category with a history of problems.

Risk-based verification means low-risk items are auto-accepted against system-visible data, mid-risk items get a documentary check, and high-risk items get a full check. It is the right choice at scale, provided the rules are written down.

The incoherent posture is unstructured sampling — checking whatever a reviewer happens to open, deeply on a Monday and shallowly on a Thursday. It produces inconsistency without saving meaningful effort and is indefensible if challenged.

A workable risk-based split:

Set a value threshold above which anything, in any category, moves to full check. Pick the number based on your salary bands and write it into the policy.

The escalation ladder

Make it four clear steps so no reviewer has to invent a response.

1. Reviewer accepts. Criteria met. Status set to accepted with the accepted amount recorded.
2. Reviewer queries. Something is missing or inconsistent but likely fixable. A rejection reason code is issued with a resubmission deadline. This is the most common outcome and should be treated as routine, not as a failure.
3. Reviewer reduces. Proof supports less than was declared. The accepted amount is recorded at the supported level, the difference is noted with a reason, and the employee is told the specific figure that will flow into the recompute.
4. Reviewer escalates. Possible falsification, a sensitive category, a senior employee's claim requiring independent review, or any case where the reviewer is genuinely unsure. Escalation goes to a single named owner. Reviewers should never be penalised for escalating.

A rejection reason taxonomy

Free-text rejection notes are the enemy of a calm season. They are inconsistent between reviewers, they generate helpdesk tickets because employees cannot tell what to do next, and they make it impossible to analyse where your process is failing. Use codes, each with a fixed employee-facing sentence and a fixed required action.

At the end of the season, count the codes. If PERIOD-MISMATCH dominates, your checklist is not clear about which year's documents you want. If DOC-MISSING dominates, your communication plan failed. The taxonomy turns a pile of complaints into a list of fixes for next year.

Turnaround SLAs

Publish them and hold to them.

• First review of a submission: within five working days of upload during the window.
• Query resolution after a resubmission: within three working days.
• Resubmission window for the employee after a query: seven calendar days, or until the hard cut-off, whichever comes first.
• Final status published to every employee: at least one full week before the first recomputed payroll runs.

That last SLA is the one that protects you. An employee who knows their final accepted figure a week before the payslip can ask questions calmly. An employee who learns it from the payslip cannot.

Write the policy down

A one-page internal verification policy, approved by finance and HR and shared with reviewers, should state:

• Which categories are auto-accepted, light-checked, fully checked and senior-reviewed
• The value threshold that escalates any item to full check
• The specific acceptance criteria for each category
• The rejection code list and the employee-facing wording for each
• The escalation owner by name and role
• The resubmission policy and the number of rounds allowed
• The position on post-cut-off submissions
• Who may override a reviewer decision, and how the override is recorded

The point is not bureaucracy. The point is that when an employee asks "why was mine rejected when my colleague's was accepted," you can answer with a document instead of an argument.

The Communication Plan

Most proof-season pain is a communication failure wearing a tax costume. Three emails, one FAQ page and a staffed helpdesk prevent the majority of it.

Email one: the advance notice

Sent two to three weeks before the proof window opens. Its job is to give people time to request documents that take time to arrive.

Cover: - The exact open and close dates of the proof window, in bold - The full category checklist, split by regime, so employees only read what applies to them - Which documents typically take weeks to obtain — lender certificates, insurer statements, school fee breakdowns, landlord PAN — with an instruction to request them now - A plain statement of what happens to unsupported declarations, and that the adjustment lands in the final months - Where to upload, and the fact that partial uploads are welcome and encouraged - Who to contact, and the response time they can expect

Email two: the window is open

Sent on the day the window opens, then repeated as a reminder to non-submitters only.

Cover: - A direct link to the upload portal - A short "top rejection reasons last year" list with one line each on how to avoid them — this is the single highest-value paragraph in the entire sequence - The resubmission policy: one query round, seven days to respond - A reminder that anyone who has no claims should still confirm that, so payroll can close their record - An explicit note that submitting the wrong year's document is the most common failure

Segment the reminders. An employee who submitted everything on day two and keeps receiving reminders will stop reading your emails entirely, and you need them to read the third one.

Email three: the recompute notice

Sent after verification closes, before the recomputed payroll runs. This is the email that prevents the February surge, and it should be personalised, not generic.

Cover: - The employee's declared total and their accepted total, side by side - The reason codes for any reduction, in plain language - The revised monthly deduction for each of the remaining months, stated as a number - A one-line explanation of why the change is concentrated: the year's tax is fixed, only the months left to collect it have shrunk - A clear statement that anything payroll could not process can still be claimed when the employee files their own return, with a link to the official site - The escalation route and its deadline, for genuine errors

If your system can only send a generic version of this message, send the generic version and then publish individual figures in the self-service portal on the same day. The figure is what people want; the paragraph is what stops them panicking.

The employee FAQ page

Build it once, keep it live all year, and link it from every email. It should answer, in the employee's own words:

• What a declaration is and why the amount affects monthly take-home
• What happens if I declare and then do not invest
• What happens if I invest but miss the proof window
• Which documents count for rent, housing loan, insurance, tuition and retirement savings
• Why my colleague's claim was accepted and mine was not
• Whether I can change my regime, and by when internally
• What the year-end statement shows and how it relates to my own return
• How to read the deduction line on my payslip

Write it in short sentences. Avoid section numbers and legal phrasing; employees do not find them reassuring. Add a line at the top and bottom directing anyone with a genuine tax planning question to the income tax department's site or their own advisor.

The helpdesk plan

• Open a dedicated channel for the season — a ticket queue or a single alias, not individual reviewers' inboxes.
• Publish response times and meet them. Two working days is achievable if the FAQ is good.
• Staff for the two spikes: the last three days of the window, and the two days after the recompute notice.
• Maintain a canned-response library keyed to your rejection codes.
• Log every question by category. Next year's FAQ writes itself.

Heading off "why is my take-home lower this month"

The surge is caused by surprise, not by the deduction. Four things reduce it:

1. Show the projection all year. If employees can see their projected annual tax and current accepted deductions in the portal every month, February is a continuation rather than an event.
2. Send the personalised notice before the payslip. Always.
3. Give the reason in one sentence. "Your accepted proofs were lower than your declaration, so the remaining tax for the year is being collected across the final payslips." That sentence answers ninety percent of tickets.
4. Have a hardship position. Decide in advance whether you will do anything for severe cases and what the limits are. Whatever you decide, apply it consistently and do not invent it at the counter in February.

Handling the Edge Cases

Mid-year joiners

Onboarding should capture the regime choice, a fresh declaration for the remainder of the year, and prior employer income and tax details. Compute on the whole year's income, not just your portion, wherever the employee discloses it. If they do not, record the non-disclosure, compute on what you have, and put the warning in writing.

Also set the proof expectation at onboarding, not in December. Someone who joins in November needs to know within their first week that a proof window closes in January.

Leavers

When someone exits mid-year, their full-and-final settlement is the last chance to correct the year's withholding. Ask for proofs at exit, even if the proof window has not opened yet, because you will not get them afterwards. Issue the salary tax statement for the period you employed them promptly, and tell them clearly that the new employer will need it.

The common failure is settling someone in September on the strength of an April declaration nobody ever verified. Build a proof check into the exit checklist.

Employees on long leave

Someone on extended parental, medical or sabbatical leave will miss your emails. Identify them in advance from your leave records and contact them through a personal email or phone, with a longer response window. Treat this as an accessibility requirement, not a courtesy. Also confirm how their reduced or nil salary months affect the projection, because the recompute mechanics differ when there is little or no remaining salary to deduct from.

Employees who never submit

Some proportion of your workforce will submit nothing despite three emails. Handle it mechanically:

• Send a final individual notice stating that no proofs were received and specifying what the recompute will assume.
• Run the recompute with zero accepted for the unsupported categories.
• Record the notice in the employee's file.
• Tell them explicitly that they may still claim eligible deductions when filing their own return.

Do not make exceptions after the fact for people who simply ignored the process, because the exception becomes the precedent and next year half the population waits for it.

Declarations that exceed what proofs support

This is the normal case, not the exception. People declare aspirationally in April. The correct response is to accept the supported amount, record the difference with a reason code, communicate the revised figure, and recompute. No moral judgement is required. What matters is that the gap is communicated before the payslip, in numbers.

Where the gap is very large, flag it to the employee individually rather than in a batch email. A person whose take-home is about to move significantly deserves a conversation.

Regime switch requests

Requests to switch regimes cluster in January, once employees realise their proofs are thin. Your internal policy, published in April, should state the last date payroll will process a switch and what happens after it. Whatever the law permits an individual to do at filing time is a separate matter that the employee handles in their own return, and you should say so in the same breath so people do not think the door is permanently closed.

Be particularly careful with employees who want to switch after the recompute has run. Re-running payroll for individuals at that stage creates reconciliation problems that outlast the season.

Corrections after the window closes

Distinguish three cases and treat them differently:

• Payroll error. You mis-keyed an amount, lost an upload, or applied the wrong regime. Fix it, whenever it is discovered, and apologise.
• Employee error inside the process. They uploaded the wrong file but responded to your query. Resolve within the resubmission round.
• Employee late submission outside the process. They missed everything. Do not reopen. Point them to their own return.

Publish those three cases in your FAQ so employees can see which one they are in.

What Breaks on Spreadsheets, and What a Portal Changes

The failure modes of email-and-spreadsheet proof season

• Attachments are not a database. Four hundred employees times eight categories is thousands of files arriving in an inbox with subject lines like "proofs" and "Re: Re: Fwd: docs". Nobody can tell what is missing without opening everything.
• Version confusion. An employee sends a corrected receipt in a new email. Two reviewers, one working from each version, reach different conclusions.
• No status visibility. Employees cannot tell whether their file was received, so they email again. Every re-ask becomes a ticket.
• Manual recompute. Someone types accepted amounts into a spreadsheet, which feeds another spreadsheet, which feeds the payroll input. A single transposed figure creates a wrong deduction that is discovered after the bank file has gone out.
• No audit trail. Six months later, nobody can say who accepted a claim, when, or on what basis. If an authority or an internal auditor asks, you are reconstructing from memory.
• Security exposure. Medical certificates, PAN details and bank statements sitting in personal mailboxes and shared drives is a data protection problem regardless of whether anyone has complained yet.
• Knowledge concentration. The whole process lives in the head of one experienced person, and when they are on leave in January, everything stops.

What a self-service declaration and proof portal actually changes

• Structured capture. Declarations are collected per category with validation at entry, so amounts are numeric, periods are dated, and regime selection filters the form.
• Employee-side uploads with instant status. The employee sees pending, submitted, under review, query raised, accepted or reduced — per line item. Status visibility alone removes a large fraction of helpdesk volume.
• Reviewer queues. Work is assigned, not fished out of an inbox. Reviewers see only their queue, and a supervisor sees the backlog by category.
• Rule-driven auto-accept. Items payroll can already see are confirmed from system data with no employee effort.
• Coded rejections with templated messaging. Reviewers click a code; the employee receives clear wording and a resubmission link.
• Automatic recompute. Accepted amounts flow straight into the tax engine. The revised monthly deduction is calculated and published without anyone retyping anything.
• Complete audit trail. Who submitted what, when, who reviewed it, what code was applied, and what was overridden, all timestamped.
• Controlled document access. Sensitive categories restricted to named reviewers, with access logs.
• Reporting that lets you manage the season. Submission rate by department, pending queue by reviewer, rejection codes by frequency, and a list of employees facing the biggest recompute impact — the last one being your individual-outreach list.

None of this makes tax decisions for you. It removes the clerical failure modes that cause most of the pain, and it makes the process explainable when someone asks.

A Worked Example — Illustrative Numbers Only

Everything below is illustrative. The rate used is a made-up flat percentage chosen only to make the arithmetic readable. It is not a real tax rate, there are no slabs, surcharge, cess, rebates or standard deductions applied, and no real limits are used. The purpose is to show the shape of what happens, not to compute anyone's tax.

Setup

• Illustrative annual salary income: 12,00,000
• Declared deductions in April: 2,00,000
• Assumed flat tax rate used purely for arithmetic: 20 percent

Step one: withholding based on the declaration

Income after declared deductions: 12,00,000 − 2,00,000 = 10,00,000 Annual tax at the assumed flat rate: 10,00,000 × 20 percent = 2,00,000 Monthly deduction across twelve months: 2,00,000 ÷ 12 ≈ 16,667

The employee sees roughly 16,667 deducted each month from April onwards and plans their spending around the resulting take-home.

Step two: proofs fall short

In January, verification concludes. Of the 2,00,000 declared, proofs support only 80,000. The employee's rent receipts lacked landlord PAN for part of the year, and an insurance premium they intended to pay was never paid.

Revised income after accepted deductions: 12,00,000 − 80,000 = 11,20,000 Revised annual tax at the same assumed rate: 11,20,000 × 20 percent = 2,24,000

Step three: the recompute lands on the months that remain

Already deducted across nine months (April to December): 16,667 × 9 ≈ 1,50,000 Balance to collect: 2,24,000 − 1,50,000 = 74,000 Months remaining: three (January, February, March) Revised monthly deduction: 74,000 ÷ 3 ≈ 24,667

What the employee experiences

The annual tax rose by 24,000 — an increase of twelve percent on the year's tax. The monthly deduction rose from about 16,667 to about 24,667, an increase of roughly forty-eight percent in the final payslips. The employee's reasonable reaction is "my salary was cut," and no amount of arithmetic delivered after the fact will feel like an explanation.

The same gap, caught earlier

Suppose the mid-year revision window in October had caught the unpaid insurance premium, and the shortfall had been reduced to 1,20,000 at that point. The balance would have been spread over six months rather than three, roughly halving the monthly increase. Nothing about the total tax changes. Only the concentration changes — and concentration is what people actually feel.

The lesson in one line

You cannot reduce the tax. You can only control when the gap is discovered and whether the employee heard about it before the payslip did.

Frequently Asked Questions

Can an employee declare something in April that they have not yet invested in?

Yes. The declaration is a forward-looking estimate of what the employee expects to do during the financial year, and that is exactly what it is meant to be. Payroll withholds on the basis of the estimate. The obligation the employee takes on is to actually make the investment and to produce proof before the employer's verification window closes. If they do not, the benefit is reversed and the tax is collected in the remaining months. Employees should declare what they realistically intend to do, not the maximum they can imagine doing.

What if an employee genuinely invests but misses the employer's proof window?

The employer will not be able to reflect the deduction in its computation or in the year-end salary tax statement, because it verified nothing. The employee is not, however, permanently out of luck. They can claim eligible deductions when filing their own income tax return and seek a refund of the excess tax deducted. Payroll should say this clearly rather than leave employees believing the money is gone, while being equally clear that reopening the window for one person is not an option. Refer employees to the income tax department's site or their advisor for how to claim in their return.

Can payroll accept proofs that arrive after the internal cut-off?

That is a policy decision, not a legal one, and the sensible answer is no for late submissions and yes for payroll's own errors. If you accept late submissions from anyone who asks, your cut-off ceases to exist and next year's submissions will all arrive late. Publish the cut-off in April, repeat it in the proof-window emails, and state the exception clearly: mistakes made by payroll get fixed whenever they are found; missed deadlines by employees do not reopen the window.

How should payroll handle an employee who refuses to disclose previous employer income?

Record the refusal in writing, compute tax on the salary you are paying, and warn the employee in writing that their total tax for the year is likely to be under-deducted because their combined income sits higher than what your computation reflects. They will face the balance, and possibly interest, when they file. Do not pressure the employee and do not quietly guess at the missing figure. Documenting the position protects both sides.

Is rent paid to a parent acceptable?

It can be, when the arrangement is real. The parent must actually own the property, an agreement should exist, payment should be traceable through a bank transfer rather than cash, and the employee should not be a co-owner of the property they claim to be renting. The parent also has to treat the rent as their income. Apply the same standard to every family rent claim in the organisation and write the standard into your verification policy so reviewers are consistent and employees cannot argue that they were singled out.

Can an employee change their tax regime in the middle of the year?

Internally, that depends on the policy you publish, and the usual approach is to allow changes up to a stated cut-off and to stop processing them after that. Separately, the rules governing what an individual may do when filing their own return are set by the income tax department and have changed over time, including the treatment of the default regime when an employee says nothing. Confirm the current position before advising anyone, tell employees your internal cut-off in April, and direct regime questions to the official site or a tax advisor rather than answering them from payroll.

Should every proof be checked, or is sampling acceptable?

Both are defensible if they are systematic. What is not defensible is ad-hoc checking that varies by reviewer and by day. If you sample, define tiers in writing: which categories are auto-accepted from your own system data, which get a light check, which always get a full check, and what value threshold escalates anything into full check regardless of category. Rent, housing loan, previous employer income and house property loss belong in full check for almost every organisation, because they carry the largest amounts and the most common errors.

How can payroll reduce the February and March spike in complaints?

Move the information earlier. Publish all season dates in April. Run a genuine mid-year revision window so gaps surface in October rather than January. Show employees their projected annual tax and accepted deductions in a self-service portal every month instead of once at the end. Send a personalised notice with declared versus accepted amounts and the revised monthly deduction at least a week before the recomputed payroll runs. The complaints are about surprise far more than they are about money.

What documents should employees be told to collect first?

The ones that depend on somebody else. Lender interest certificates, insurer premium statements, school fee breakdowns by head, retirement account contribution statements and landlord PAN all involve a third party and can take weeks. Employees who request them the day your window opens will be chasing them the day it closes. Everything the employee can produce themselves — receipts, bank statements, agreements — can wait.

Running a Season You Do Not Dread

The recurring theme across every part of this cycle is that the tax rules are not what makes proof season hard. The hard parts are operational and entirely within your control: dates published early enough for third parties to respond, a regime choice captured cleanly, a category checklist employees can actually follow, a written verification standard that produces the same answer for every employee, coded rejections instead of free-text notes, SLAs you meet, and a personalised recompute notice that reaches people before their payslip does.

Get those seven things right and February stops being an event. The tax collected is the same; the surprise is gone. Get them wrong and you will spend six weeks explaining arithmetic to people who are, understandably, upset, while reconstructing decisions from an inbox.

If your team is still running the investment declaration cycle across a shared drive, a mailbox and a spreadsheet that only one person fully understands, that is the piece worth fixing before next April rather than next January. CozyHR handles the operational layer of this end to end: regime-aware declaration forms, employee self-service uploads with per-item status tracking, reviewer queues with coded rejection reasons, restricted access for sensitive documents, a complete audit trail, and automatic recompute that pushes revised monthly TDS into payroll without anyone retyping a figure. If you want to see what your own proof season would look like with the clerical failure modes removed, take CozyHR for a walkthrough with your actual category list and headcount before the next declaration window opens.

A final reminder, because it matters more than anything else in this article: tax rates, deduction limits, thresholds, regime parameters and statutory dates change. Nothing here is tax advice. Verify every current figure with the income tax department's official resources or a qualified tax advisor before you configure payroll or publish guidance to your employees.