Tax advisory
TDS Compliance for Startups and MSMEs: From Payment Review to Certificate
A Tax Year 2026-27 TDS operating workflow for Indian startups and MSMEs, covering applicability, deduction triggers, deposit, statements, certificates, corrections, and ledger reconciliation.
9 min read
Short answer
For each payment in Tax Year 2026-27, first identify the payer, payee status and residence, exact payment nature, applicable row of section 392 or 393 of the Income-tax Act, 2025, tax-year aggregate, threshold, rate, and any valid declaration or lower/no-deduction certificate. For many section 393 payments, deduction occurs at the earlier of credit to the payee or payment; a suspense-account credit can also count. After deduction, deposit under the applicable Rule 218 path, report it in the correct statement, reconcile the processed result, and issue the correct certificate. Do not use one TDS rate, threshold, form, or date across salaries, resident vendors, non-residents, and special transactions. One controlled ledger should connect invoice or payroll evidence, deduction, challan, statement line, correction, certificate, and deductee credit.
An unpaid invoice can already create the deduction event
Decide applicability before calculating an amount
| Payment stream | Primary legal route | Facts that control the decision | Do not assume |
|---|---|---|---|
| Salary and specified employment payments | Section 392 and the applicable salary computation rules | Employer status, employee income information, estimated taxable salary, relief and credits, payroll events, and current declarations | A vendor rate, invoice threshold, or non-salary statement form |
| Payment to a resident other than salary | The applicable row in section 393(1), and section 393(3) where relevant | Payer class, resident payee constitution, exact payment nature, single-payment and aggregate tests, earlier credit/payment event, PAN, declaration, and certificate | That every company payment deducts, or that every startup below one turnover figure is outside TDS |
| Payment to a non-resident or foreign company | Section 393(2), treaty and chargeability analysis, plus any valid section 395 or 400 process | Residence, beneficial and contractual recipient, income character, place and source facts, chargeable portion, treaty documents, rate components, and certificate | The resident-vendor threshold, rate, statement, or certificate path |
| Specified one-off transaction | The exact section 393 table row and the corresponding Rules form path | Transaction type, payer eligibility, property or asset facts, consideration, event date, counterparties, threshold and challan-cum-statement conditions | That a rare payment can wait for the quarterly close |
Section 393 contains payment-specific rows, thresholds, rates, payer conditions, and notes. Some tests apply to one payment; others apply to the tax-year aggregate. Some distinguish an individual or HUF payee from another person. A valid lower/no-deduction certificate under section 395, or a permitted declaration, changes action only within its scope, period, parties, payment category, and validity. Save the actual instrument and validate it; a vendor email claiming exemption is not enough.
Control the sequence from deduction to deductee credit
- 01
Approve the applicability decision
Before booking or payment, document the section and table row, payer and payee facts, aggregation, trigger, threshold, rate source, and exception. Route uncertain resident, non-resident, gross-up, related-party, software, reimbursement, property, VDA, or mixed-service facts for review.
- 02
Deduct on the controlling event
Use the event specified by the applicable provision. Where earlier credit or payment controls, a credit to the payee, suspense, or another account can trigger deduction before bank payment. Record gross amount, deduction date, rate basis, TDS, and net payable.
- 03
Deposit through the applicable Rule 218 route
Match the deductor class, deduction month, government or non-government route, challan or book adjustment, and any challan-cum-statement rule. Preserve payment status and challan identifiers. Do not treat bank debit alone as proof of a correctly credited deposit.
- 04
File the correct statement
For current new-Act periods, Form 138 covers specified salary reporting, Form 140 covers resident non-salary reporting, and Form 144 covers non-resident reporting; Form 141 is the common challan-cum-TDS statement for specified transactions. Confirm current instructions and period before filing.
- 05
Process exceptions and corrections
Review the acknowledgement and processed result. Resolve unmatched challans, invalid PAN or party data, section or rate errors, short deduction or deposit, and deductee-line mismatches. File a correction only against the correct original statement and within the applicable section 397 and Rules path.
- 06
Issue and reconcile the certificate
Use the certificate generated for the processed statement: Form 130 for salary, Form 131 for ordinary non-salary TDS, or Form 132 for specified challan-cum-statement transactions, as applicable. Confirm the certificate agrees to books, challan, statement, and recipient before closing the period.
Make the TDS ledger reconcile line by line
| Control total | Must agree to | Exception owner |
|---|---|---|
| Gross amount credited or paid | Contract or payroll, invoice or salary record, expense or asset ledger, vendor/employee subledger, and bank schedule | Accounts or payroll owner |
| Tax deducted and net amount | Applicability record, deduction date, statutory/certificate rate basis, TDS payable ledger, and net creditor balance | Tax reviewer |
| Tax deposited | TDS payable clearing, challan or book-adjustment evidence, bank, period, section/table row, and government credit status | Treasury and tax owner |
| Statement line | Correct deductor, deductee, PAN, amount, trigger date, section/table row, rate, deduction, deposit, and challan allocation | Statement preparer and independent reviewer |
| Certificate and deductee credit | Processed statement, generated certificate, recipient details, books, and any reported credit mismatch | Tax owner and recipient-contact owner |
Assign owners and preserve evidence without copying it everywhere
| Control | Owner | Evidence | Review trigger |
|---|---|---|---|
| Vendor and employee master | Procurement or HR, with finance review | Legal name, constitution, residence status, PAN/TAN status, contract, and validated certificate/declaration reference | New party, status change, expired certificate, or data mismatch |
| Payment classification | Accounts preparer; tax reviewer | Contract scope, invoice/payroll facts, ledger treatment, section/table-row decision, aggregation, and trigger date | New service, amended contract, one-off payment, non-resident, or threshold approach |
| Deposit and statement | Treasury and tax operations | TDS payable ledger, challan/book adjustment, statement file, validation, acknowledgement, and processed result | Short payment, unmatched challan, rejected file, or processing default |
| Certificate and correction | Tax operations; independent reviewer | Generated certificate, issue log, deductee complaint, correction basis, revised acknowledgement, and closure note | Wrong party/amount/section, missing credit, short deduction, or original-period error |
- Restrict edit rights for party masters, rate rules, challan allocation, and statement files.
- Use maker-checker approval for manual overrides, certificates, corrections, and period reopening.
- Keep original and corrected statement evidence; never overwrite the chronology.
- Track issue category, owner, status, deadline, and restricted repository reference in the shared queue.
Escalate before a wrong deduction becomes several wrong records
Failure or delay at deduction, deposit, statement, or certificate stage can create interest, fee, penalty, prosecution, expense-disallowance, cash, audit, and deductee-credit consequences under the applicable facts. These consequences do not all use the same base, period, defence, or remedy. Quantify each event separately and check current sections 424 to 427, 461 and 465, plus any other applicable provision, before recording exposure.
Sources and review
Published by ThynkBored. Published 16 July 2026. Content review completed 16 July 2026.
- Income-tax Act, 2025 as amended by Finance Act, 2026
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: Sections 392 and 393 payer, payment, threshold, rate, aggregation, credit/payment trigger, suspense-credit, resident, and non-resident TDS framework; Sections 395 and 397 certificate, TAN, deposit, statement, correction, and evidence duties; Sections 424 to 427, 461, and 465 consequence framework.
- Section 393: Tax to be deducted at source
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: Payment-specific table rows rather than a universal TDS threshold or rate; Earlier-of-credit-or-payment trigger and deemed credit through suspense or another account; Scope-limited declarations, exceptions, and gross-up rules.
- Notification No. 22/2026, G.S.R. 198(E): Income-tax Rules, 2026
Central Board of Direct Taxes. Accessed 16 July 2026.
Supports: Rule 218 deposit routes and Rule 219 statement framework; Notified Forms 130 to 132, 138, 140, 141, and 144 for the current certificate and statement sequence; Period, deductor, payment, correction, and evidence mechanics under the 2026 Rules.
- Form No. 138: Quarterly salary TDS statement
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: Form 138 is the Tax Year 2026-27 quarterly statement for specified salary and specified-senior-citizen deductions; Deductee, payment, deduction, deposit, and challan details required for salary reporting.
- Form No. 140: Quarterly resident non-salary TDS statement
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: Form 140 is the quarterly statement for payments other than salary to resident deductees; Statement reporting is separate from deduction and deposit evidence.
- Form No. 130: Salary TDS certificate
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: Form 130 is the certificate for specified salary and specified-senior-citizen TDS under the 2025 Act; Certificate generation follows the applicable deduction, deposit, and statement process.
- Form No. 131: Non-salary TDS certificate
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: Form 131 is the certificate for ordinary non-salary TDS reported through the applicable statement; Deductee credit depends on an accurate processed statement and matching certificate trail.
- Form No. 132: TDS certificate for specified transactions
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: Form 132 is the certificate for specified transactions using the current combined certificate path; Specified-transaction certificate work remains distinct from ordinary quarterly non-salary reporting.
This article is an educational Tax Year 2026-27 operating workflow, not a TDS opinion for a payment or a complete rate, threshold, due-date, treaty, gross-up, disallowance, interest, fee, penalty, or prosecution computation. Applicability depends on the current Act and Rules, payer class, payee constitution and residence, beneficial recipient, payment nature, contract, chargeability, tax-year aggregation, credit and payment dates, PAN/TAN, certificates, declarations, special provisions, treaty documents, government status, and later amendments or relief. Form names, utilities, portal validations, challans, and instructions can change. Verify the applicable statutory table row, current notified form, due date, certificate, correction window, and processed result before action. The composite example supplies no conclusion for a real invoice.
Name the payment and broken control before sharing records
Share only the payer category, Tax Year and quarter, resident or non-resident payee category, broad payment category, issue stage, status, and nearest deadline window. ThynkBored can help structure applicability, reconciliation, or correction questions for fact-specific review.
Use categories and status only. Do not send or upload PAN, TAN, Aadhaar, account numbers, credentials, passwords, OTPs, DSC details, invoices, contracts, payroll, ledgers, challans, statements, certificates, returns, bank records, identity files, or raw TDS workings through the form. Agree a secure handoff first if records require review.
Diagnose this issueQuestions owners ask
When should startups review TDS compliance?
Review before the first credit or payment for a new salary, vendor, resident, non-resident, rent, interest, property, asset, or special transaction; when a contract, party status, threshold aggregate, certificate, or rate basis changes; and before every deposit, statement, certificate, and correction close. For many section 393 payments, waiting for bank payment can be late because credit may be the earlier trigger.
What records are needed for TDS return readiness?
Keep the approved applicability record, contract and invoice or payroll evidence, payer/payee master and residence facts, PAN/TAN validation, threshold aggregation, credit/payment and deduction dates, rate or certificate basis, TDS ledger, challan or book adjustment, statement file and acknowledgement, processed result, correction trail, certificate, and deductee-credit exception log in a restricted record set.
Useful context for this decision
Follow the records, definitions, comparisons, and next actions connected to this page.