Tax regime choice and monthly TDS on salary

Old versus new tax regime is a withholding input for salary payroll: which regime the employee is on for this year’s estimate, so monthly tax deducted at source (TDS) can be calculated. It is not the employee’s income-tax return, not the employer’s TDS return, and not legal or tax advice. This page does not publish current slabs, surcharge, or cess. Pending SME review; remains a draft.

Secondary blogs disagree about form names and section renumbering. Claims that Form 16 becomes Form 130, or that a familiar salary-withholding section is replaced by 392, are not treated as fact here. Official Income Tax Department materials or the gazette you are bound by are required for the period you are running. Dayzen payroll supports old and new regime in calculation; it does not file TDS. Calculation versus filing versus bank pay stays on the payroll calculation versus filing guide.

What monthly TDS on salary is

Monthly TDS is an estimate of tax on projected salary income (and other configured items you include), spread across remaining months, then withheld from this period’s net. The payslip line is that period’s withholding, not a final tax bill. The year still has to be trued up as income, declarations, and months remaining change.

Employees read the line as “tax I paid.” It is tax withheld by the employer under the process you actually run. Whether it matches the employee’s eventual liability depends on other income, other deductions, regime, and what was declared in time. Payroll cannot see a freelance invoice the employee never declared.

Dayzen payroll can compute TDS using the configured regime and components. It does not deposit tax with the government, does not file statements, and does not issue government certificates as a claimed product. The employee-facing certificate conversation — including why form nicknames must be verified officially — is on TDS certificates employers issue.

Regime as a stored fact, not a hallway preference

Hold the regime on the employee record payroll will read: old, new, or whatever statuses your reviewed process uses, with an effective period (typically a financial year). A chat “I am on new regime” that never hits the record will withhold as if last year’s choice still applied.

Who may change it, until when in the year, and whether a change is allowed more than once, are questions of current tax process — verify on official materials and your consultant. This article will not invent a deadline or a lock-in rule. Operationally, you still need a freeze: after a named date in the cycle, a late regime change is next month or an off-cycle exception, not a silent reopen of a locked run.

New joiners need a regime on day one of payroll, even if the declaration form is still moving. A default in the SOP (and a dated catch-up when the declaration arrives) is better than a blank that calculates as zero tax or as someone else’s template.

Exits need a last withholding that matches the employed period and the regime then in force. Do not leave a leaver on an estimated remaining-year spread as if they will still be on payroll in March.

Monthly estimate versus annual true-up (concept only)

A typical operating shape, not a statutory formula:

1. Project taxable salary income for the year from the current structure and expected months, plus configured extras you include.
2. Apply the regime’s configured treatment of deductions and exemptions you actually honour in payroll — without this page listing them as current law.
3. Compute estimated annual tax from configured tax tables you maintain from official sources — this article does not print those tables.
4. Subtract tax already withheld in prior periods of the year.
5. Spread the remainder across remaining pay periods (your spread method: equal months, or another written method).
6. Withhold this period’s amount, subject to your rounding rule.

True-up is what happens when any input in that list changes: increment, unpaid days, bonus, declaration of investment, regime correction, unpaid leave that reduced income. The next calculation should not pretend the old monthly amount is a contract. If you freeze declarations after a date, say so, so employees do not expect a same-month cut when they submit proofs on payday.

Arrears and one-off payments can spike a month. Write whether you withhold extra in that month, spread residual, or follow another reviewed method. Do not invent a relief section number here; if a relief or special computation applies, verify it on official materials and implement only what you have reviewed.

What you must not copy from the internet into the template

Do not paste current-year slab tables from a news card into an employee wiki and call them Dayzen policy. Slabs change; this project does not treat any blog grid as verified copy. The configuration in payroll should be maintained from official Income Tax sources for the assessment year you are in, by someone accountable, with a dated change log.

Do not publish surcharge or cess percentages in this article. Do not tell employees a round “new regime is always lower.” Regime comparison is individual. A payroll estimate is not a planning opinion.

Do not treat form-renumbering rumours as fact. If employees ask “is it still Form 16” or “did the section number change,” the honest operating answer is: we withhold as configured; the certificate and return names are whatever the Income Tax Department currently requires; we will not certify a blog’s renaming. Secondary sources disagree; gazette and ITD win.

Declarations and proofs as payroll inputs

Where the old regime (or any configured path) uses employee declarations, those declarations are inputs like LOP days: they must exist before freeze if they should affect this month. A spreadsheet in a CA’s inbox is not an input. Put the status on the record: declared, pending, rejected, or not applicable.

Proof collection later in the year is a true-up trigger, not a reason to reopen every past payslip. Write whether you recast remaining months only, or also correct prior months by adjustment. Recasting history without a named path rewrites every PDF the employee already downloaded.

New-regime employees may have a smaller set of payroll-side declarations. That is a configuration and education issue. It is not a reason to skip storing the regime itself.

Payslip and employee communication

Print TDS (or your chosen label) as a deduction line for the period. YTD tax withheld, if you print YTD, helps the employee see the year so far. It is still not the annual computation and not the certificate.

When someone asks “why did TDS jump,” answer with inputs: income change, unpaid days down, bonus, declaration change, months remaining, or a configuration correction — not with a slab lecture. When they ask “did you file my tax,” the answer is no: withholding is not the employee return and not the employer return unless those owners confirm they filed.

Self-service should show the regime on file if you choose to expose it, so the employee can spot a wrong flag before freeze. Wrong-regime withholding for half a year is an ugly true-up.

What finance still owns outside the HRMS

Deposits, return filing, traces, and certificates follow official due dates and portals you verify externally. The HRMS can supply calculated withholding and employee identity. It does not replace the filing owner. Growing teams blur the three and then blame the calculator when a statement is late.

If you outsource filing, still own regime and declaration freeze in-house. The vendor can withhold from a file. They cannot guess which regime you meant.

SME-gated items left open

Current slab tables, surcharge, cess, rebate mechanics, standard deduction amounts, which deductions exist in which regime, lock-in of regime choice, and any 2026 (or other year) form or section renumbering are out of scope. Verify on Income Tax Department materials and gazettes. This draft will not close those debates from secondary blogs.

---

Store the regime, estimate annual tax without printing slabs here, withhold a monthly share, true up when inputs change. Old versus new is a calculation flag. Filing is another job. Dayzen supports both regimes in payroll calculation; it does not file TDS. Form-name rumours need official confirmation. This article remains a draft pending SME review.

Train payroll to refuse “just use last year’s monthly TDS” when the structure or the regime changed. A stable line that ignores a new input is not conservatism; it is an estimate that will break at year-end and on the certificate the filing owner later prepares.

If an employee had tax withheld by a previous employer in the same year, that history is an input to this year’s estimate only when you have a reviewed process to capture it. This page will not name a government form for that capture. Until the input is on the record, this employer’s monthly estimate will not know about it. Put the catch-up in the SOP: what you collect, who types it, and that it true-ups remaining months rather than rewriting every past PDF by default.