+91 9828123489
HomeIncome TaxTAN Registration

TAN Registration in Chhattisgarh

Tax Deduction Account Number, commonly called TAN, is a ten-character alphanumeric number issued by the Income Tax Department to persons responsible for deducting tax at source or collecting tax at source. It is used in TDS/TCS statements, challans, certificates, and correspondence. Vakilkaro assists companies, LLPs, partnership firms, proprietorships, trusts, societies, employers, and other deductors with TAN registration, correction, portal onboarding, and the first steps of TDS return filing.

cut-out photo

Get free consultation

Talk to a qualified professional today.
+91
or reach us directly
Quick answer

TAN registration is the process of obtaining a Tax Deduction and Collection Account Number from the Income Tax Department. Every person required to deduct TDS or collect TCS generally needs TAN unless a specific transaction is permitted to be reported through PAN-based challan-cum-statements. TAN identifies the deductor, links tax deposits with quarterly statements, and enables issuance of Form 16 or Form 16A to deductees. It is different from PAN and must be quoted accurately in prescribed TDS/TCS documents. From 1 April 2026, the Income Tax Act, 2025 applies to income and compliance events falling in Tax Year 2026-27 onward. However, matters relating to FY 2025-26 and AY 2026-27 continue under the Income Tax Act, 1961. Businesses should therefore identify the date of the payment, deduction, filing period, or notice before selecting the applicable provision. The practical filing workflow on the e-filing portal may support both legal frameworks during the transition, but the governing section depends on the relevant year and event.

TAN Registration Online in India — Apply for Tax Deduction Account Number with Vakilkaro

Who Is Required to Obtain TAN?

Any person responsible for deducting or collecting tax under applicable provisions should evaluate TAN registration before the first deduction becomes due. The responsibility can arise from salary payments, contractor bills, professional fees, rent, commission, interest, purchase transactions, e-commerce arrangements, benefits or perquisites, and other specified payments. The obligation depends on status, payment nature, threshold, and statutory provision.

  • Private limited, public limited, one person, and Section 8 companies.
  • Limited liability partnerships and partnership firms.
  • Proprietorships and individuals liable to deduct tax in business or professional transactions.
  • Trusts, societies, NGOs, educational institutions, hospitals, and associations.
  • Government offices, local authorities, cooperative societies, and other bodies.
  • Employers deducting tax from salary.
  • Persons required to collect tax at source under applicable provisions.

A newly incorporated company may receive TAN as part of an integrated incorporation process, but the allotment should still be verified before use. A business should not assume that GST registration, PAN, company registration, or LLP registration automatically completes TDS onboarding.

Transactions Where Separate TAN May Not Be Required

Certain one-time transactions are reported through PAN-based challan-cum-statements, and the deductor may not need a separate TAN solely for that transaction. Common examples under the applicable framework include specified property purchases, rent payments by certain individuals or HUFs, and contractual or professional payments covered by special challan-cum-statement provisions. The exception is transaction-specific and should not be extended to ordinary recurring business deductions.

Where a person also deducts tax under general provisions—for example, a business paying salary, contractor charges, rent, or professional fees—a TAN can still be necessary. Applying the exception incorrectly may result in an invalid challan, inability to file the quarterly statement, and late-filing consequences.

Documents and Information Required for TAN Registration

The name, date of formation, status, and address should match PAN and constitutional records. Differences caused by abbreviations, old addresses, punctuation, or conversion of a firm into an LLP can delay processing or create future mismatches on the e-filing and TRACES systems.

Form 49B for TAN Application

Form 49B is used to apply for allotment of TAN. The form captures the applicant’s category, branch or division details, address, responsible person, and contact information. Each field should reflect the legal entity responsible for deduction, not merely the consultant, employee, payroll vendor, or branch submitting the form.

Single TAN or multiple TANs

An organisation may have centralised or decentralised TDS administration. Separate TANs can exist for branches or divisions where permitted and operationally justified, but unnecessary duplication creates reconciliation problems. Before applying, the business should search existing records, examine old TDS certificates and challans, and confirm whether a TAN has already been allotted. Duplicate TANs should not be used interchangeably.

Step-by-Step TAN Registration Process

  • Confirm that the applicant has a TAN obligation and that no transaction-specific exception applies.
  • Search existing records to prevent a duplicate application.
  • Collect PAN, legal name, status, address, and responsible-person information.
  • Prepare Form 49B through the authorised online application channel or prescribed offline route.
  • Verify each field against PAN and entity-registration records.
  • Pay the applicable processing fee and generate the acknowledgement.
  • Complete signature or document submission requirements according to the chosen mode.
  • Track the application using the acknowledgement number.
  • Verify the allotted TAN through the Income Tax Department’s Know TAN service.
  • Register the TAN on the e-filing portal and complete TRACES onboarding before filing or certificate issuance.

The processing timeline depends on successful validation and document acceptance. Applications containing inconsistent names, addresses, status codes, or responsible-person details may be placed on hold or rejected.

What to Do After TAN Is Allotted

TAN allotment is the beginning of TDS administration, not the end. The deductor should map the TAN in accounting and payroll software, register on the e-filing portal, complete TRACES registration, create authorised-user controls, and establish a calendar for deduction, deposit, quarterly statements, correction statements, and certificate issuance.

  • Use the correct TAN on Challan ITNS 281 or the applicable integrated payment module.
  • Reconcile challan details with the relevant quarter and deduction section.
  • File the correct statement—such as salary, resident non-salary, non-resident, or TCS statement.
  • Download and issue TDS certificates after statement processing.
  • Review defaults, short deduction, interest, and unmatched challans on TRACES.
  • Maintain deductee PAN validation and lower-deduction certificate records.

Vakilkaro can connect TAN registration with TDS return filing so the entity’s first deduction cycle is set up correctly rather than waiting for a default notice.

TAN Correction and Changes

A TAN correction request is used when allotted data such as name, address, contact details, branch information, or responsible person needs updating. The correction should be supported by current legal records. A change in authorised employee does not always require changing the legal deductor identity, while conversion, merger, demerger, or restructuring may require a more detailed review.

Where multiple TANs have been obtained accidentally, the deductor should identify the TAN carrying valid historical statements and seek cancellation or surrender of the duplicate through the prescribed process. Filing some quarters under one TAN and other quarters under another can fragment deductee credit and make correction expensive.

Difference Between TAN, PAN, GSTIN and CIN

These identifiers are connected but not substitutes. PAN identifies the taxpayer, TAN identifies the deductor/collector function, GSTIN identifies the registered person under GST, and CIN or LLPIN identifies the legal entity under corporate law. The names and addresses across registrations should be kept consistent to reduce KYC and portal validation issues.

Penalty and Consequences of TAN Non-Compliance

Failure to apply for TAN, quote it correctly, deposit deducted tax, file statements, or issue certificates can attract separate consequences. Quoting an incorrect TAN may cause challan mismatch and deny deductees timely credit. Late TDS statements can attract a daily fee subject to statutory limits, while inaccurate statements, non-deduction, short deduction, and delayed deposit can lead to interest, penalty, prosecution in serious cases, and disallowance of related expenditure.

The risk is not limited to the deductor. Employees, vendors, landlords, consultants, and other deductees may see missing credit in Form 26AS or AIS and may raise disputes. A reliable TAN and TDS workflow protects both sides.

Benefits of Applying Through Vakilkaro

Vakilkaro checks the applicant’s legal status, existing TAN records, PAN data, and intended deduction activity before filing. The service includes Form 49B preparation, application tracking, allotment verification, correction guidance, and optional setup for e-filing and TDS return compliance.

For a new company or LLP, TAN registration can be aligned with payroll, professional-fee payments, rent, contractor payments, GST registration, and company ITR filing. This integrated approach prevents the common situation in which tax is deducted but deposited or reported under an incorrect identifier.

TAN Registration for Different Types of Applicants

A company typically requires TAN because it may deduct tax from salary, rent, professional fees, contractor payments, commission, interest, or other specified payments. Even when a newly incorporated company receives TAN through an integrated incorporation form, the finance team should verify the allotment letter, map the number in payroll and accounting software, and complete e-filing and TRACES registration before the first quarterly statement.

An LLP or partnership firm may have no employees but can still require TAN for rent, professional charges, contractor bills, interest, or partner-related payments covered by the law. The responsible-person details should be maintained carefully because partners and designated partners may change while the legal deductor continues.

A proprietor is not a separate legal person from the individual, but the proprietorship may have a distinct TAN for deduction activities. The trade name, proprietor’s PAN, business address, and deductor category should be entered consistently. Using the individual’s personal PAN in a general TDS statement where TAN is required can prevent valid filing.

Trusts, societies, NGOs, educational institutions, and hospitals often make salary, rent, professional, security, housekeeping, construction, and event-related payments. Their exemption or charitable status does not automatically remove TDS obligations. TAN registration should be integrated with trust or NGO tax filing and the institution’s accounting controls.

Government offices and large organisations may operate through several drawing and disbursing officers. Before applying for additional TANs, the organisation should define which office will deduct, deposit, file, issue certificates, and answer defaults. A decentralised structure without a written responsibility matrix frequently produces duplicate filings and unmatched challans.

Operational Setup After TAN Registration

The first post-allotment task is to create a TDS responsibility calendar. It should list the earlier-of-credit-or-payment rule, monthly deposit dates, quarterly statement dates, certificate dates, year-end salary reconciliation, lower-deduction certificate tracking, and periodic default review. The calendar should name both a preparer and reviewer so compliance does not depend on one employee.

Vendor onboarding should capture PAN, legal name, residential status, entity type, GST details, bank account, and declaration or certificate relevant to withholding. A vendor should not be assigned a tax section solely from its business name. The nature of each payment and contract must be considered. Similarly, employee payroll should reconcile declarations, proofs, previous-employer salary, and regime selection.

Accounting software should block or flag payments where PAN is absent, the threshold is crossed, or the section has not been selected. The challan should be generated from a reviewed deduction summary, not from an approximate amount. After payment, the challan identification details should be stored in a central register and matched to the return before quarter close.

Access control is also important. TAN login, TRACES account, digital signature, and registered contact details should remain under organisational control when an employee or consultant changes. The organisation should not discover at filing time that OTPs are going to an unavailable phone number or that historical statements are accessible only to a former service provider.

Why TAN Data Consistency Matters

  • TAN is connected to multiple systems: the tax-payment module, TDS statements, TRACES, certificates, Form 26AS, AIS, payroll, accounts payable, and income-tax assessment. A small spelling difference in the deductor name may not always block filing, but repeated differences in PAN, TAN, address, responsible person, and entity status can complicate KYC, correction, and portal registration.

When an entity changes its registered office, authorised signatory, constitution, or name, the update plan should cover PAN, TAN, GST, MCA or registrar records, bank KYC, payroll, invoices, and contractual documents. Updating one system while leaving all others unchanged creates contradictory evidence. Vakilkaro maps the dependent registrations and advises whether correction or a fresh registration is legally appropriate.

Historical compliance should be reviewed before surrendering a TAN. Open defaults, unissued certificates, pending corrections, and unmatched challans may still need the old TAN. Once the correct history is secured and responsibilities are transferred, a duplicate or obsolete number can be addressed through the prescribed route.

Practical TAN Registration Checklist

  • Confirm the payment types that create TDS or TCS responsibility.
  • Check whether a transaction-specific PAN-based exception applies.
  • Search for an existing TAN before submitting Form 49B.
  • Match legal name, status, date, PAN, and address with source records.
  • Identify the correct responsible person and branch structure.
  • Retain the application acknowledgement and payment receipt.
  • Track allotment and verify TAN through the official search facility.
  • Register the TAN on the e-filing portal and TRACES.
  • Configure payroll and accounting software with the verified number.
  • Create a deduction, deposit, return, and certificate calendar.
  • Validate deductee PAN and residency before the first payment.
  • Review portal defaults after every quarterly statement.
Questions, answered

Frequently asked questions

TAN is a ten-character Tax Deduction and Collection Account Number issued by the Income Tax Department to persons responsible for deducting TDS or collecting TCS.

Yes. PAN identifies the taxpayer, whereas TAN identifies the person in the role of tax deductor or collector. Both may be required for the same entity.

A person required to deduct TDS or collect TCS generally needs TAN unless a specific PAN-based transaction mechanism applies.

An employee does not need TAN merely because tax is deducted from salary. The employer, as deductor, uses TAN.

A proprietor liable to deduct tax may obtain TAN in the deductor capacity. The application should use the correct proprietorship and responsible-person details.

Specified property-purchase TDS is generally handled through a PAN-based challan-cum-statement, so TAN may not be needed solely for that transaction.

Separate TANs may exist for branches or divisions, but the structure should be deliberate. Duplicate or unnecessary TANs create reconciliation problems.

The Income Tax Department provides a Know TAN service. Old challans, TDS certificates, returns, and TRACES records should also be reviewed.

Form 49B is used for applying for TAN allotment.

A correction application can be filed through the authorised channel with supporting information and acknowledgement requirements.

A duplicate or no-longer-required TAN may be surrendered or cancelled through the prescribed process after checking historical filings and outstanding defaults.

TAN may be allotted through integrated incorporation services, but the company should verify the number and complete e-filing/TRACES registration.

It is quoted in TDS/TCS statements, challans, certificates, and relevant correspondence.

The payment may not match the correct deductor account or statement. A challan correction or other remedial process may be required.

Yes, where general TDS provisions apply. Obtaining TAN early allows correct deposit and statement filing.

TAN does not ordinarily require periodic renewal, but its details should be updated and it should be surrendered if duplicated or legally unnecessary.

TRACES is the system used for TDS administration, statement processing, certificates, defaults, and related services.

Yes. TAN registration can be followed by recurring TDS return filing, correction statements, and compliance support.

Common information includes PAN, legal name, status, address, contact details, responsible person, and entity-registration records.

Timing depends on application validation and document processing. Correct matching details help avoid delays.

Most steps can be completed online through the relevant government portal, authorised application channel, digital signature, and electronic verification. Physical or bank documentation may still be required depending on the service, applicant, transaction, or correction route. Vakilkaro provides a service-specific checklist before filing.

The mismatch should be reconciled rather than overwritten without explanation. Source records, PAN or TAN data, tax statements, challans, agreements, and earlier filings are compared. Depending on the issue, a correction request, revised filing, deductor update, or written response may be required.

No. Early preparation allows time for document collection, PAN validation, treaty or tax review, challan correction, and client approval. Last-day filing increases the risk of portal congestion, incomplete evidence, wrong payment details, and missed verification.

No. A form or return may be one part of a broader process involving tax payment, certificate issuance, bank approval, TRACES processing, assessment, accounting, GST, audit, or legal response. The related actions should be identified and tracked separately.

The work follows a document checklist, preparer review, reconciliation, and final verification. Material figures are matched with source documents and portal records. The client receives acknowledgements and a summary of any continuing action, such as certificate generation, correction, or notice tracking.

Many filings have a correction, revision, withdrawal, or rectification mechanism, but the available route and deadline vary. The earlier acknowledgement, processing status, tax payment, and any pending notice must be reviewed before selecting the remedy.

Digital-signature requirements depend on the taxpayer, form, and filing mode. Companies and certain other filers commonly use DSC, while individuals may have electronic-verification options. The signature should be registered and tested before the due date.

Keep the filed form or return, acknowledgement, computation, tax challan, source documents, correspondence, and evidence relied upon. Records should remain accessible for assessment, audit, correction, and future-year consistency, not merely until the portal shows successful submission.

Yes. The work can be coordinated with TAN registration, TDS return filing, ITR filing online, foreign-remittance compliance, company or business tax filing, and income tax notice response where the facts are connected.

The portal records data but does not decide every legal or factual issue for the user. Eligibility, tax character, correct section, supporting evidence, reconciliation, and remedy selection require judgement. Professional review reduces technically successful but substantively incorrect filing.

Share the applicant or taxpayer profile, relevant year or period, earlier acknowledgements, portal communications, tax payments, source documents, and a brief explanation of the transaction or error. Complete initial information helps identify the correct filing route and prevents repeated document requests.

Yes. Missing identity details, challans, agreements, statements, certificates, or supporting computations can delay preparation, trigger validation errors, or weaken the filing. Where a document is genuinely unavailable, the alternative evidence and risk should be discussed before submission.

Successful upload proves submission, but processing, verification, certificate generation, bank approval, correction review, or departmental response may still remain. The acknowledgement should be checked and any post-filing action should be placed on a compliance calendar.

A remedy may be available for an incorrect challan, assessment year, TAN, minor head, or allocation, depending on the payment and processing stage. The bank receipt, challan status, filed statement, and portal record must be examined before attempting correction.

Yes. The completion summary can identify follow-up work such as tax deposit, e-verification, certificate issuance, bank submission, correction statement, response tracking, or next-quarter compliance. This prevents the client from treating one acknowledgement as the end of the entire process.

Current filing and historical cleanup can be coordinated, but they are usually separated into clear work streams. This prevents unresolved old defaults from delaying the current due date while still creating a plan for corrections, demands, or missing documents.

The organisation should recover portal access, registered contact details, digital signatures, acknowledgements, working files, and payment records. Authorised-person information may need updating. Compliance access should belong to the organisation rather than remain dependent on one employee or consultant.

Only records relevant to the assignment should be collected and shared through controlled channels. Access should be limited to the responsible team, and final files should be organised so the client can retain its own complete compliance record.

Yes. Acceptance or processing does not prevent later verification or assessment where permitted by law. The taxpayer should retain the legal basis, reconciliation, documents, and computation so the position can be explained consistently if a question arises.

A defensible filing matches legal eligibility, books, bank records, tax statements, supporting documents, and portal data. It explains material judgements, uses the correct period and identifier, contains accurate tax payment details, and preserves acknowledgements and working papers.

Clear scanned records can be used for review where originals are not required for submission. Names, dates, amounts, signatures, registration numbers, and challan details must remain legible. The client should preserve original records for verification, audit, or departmental proceedings.

Branch-wise data should be consolidated under the correct legal entity, PAN, TAN, and filing responsibility. Separate registrations or statements should be used only where legally and operationally appropriate. A central reconciliation helps prevent duplication and omitted transactions.

Accounting exports are useful, but they should be reviewed for mapping, duplicates, journal entries, residential status, tax sections, and year-end provisions. Software data is a starting point, not conclusive evidence that the legal treatment is correct.

The error message, validation file, browser record, and submission status are checked first. The team distinguishes a technical portal issue from a data or eligibility error, makes the required correction, and preserves screenshots or acknowledgements where the deadline is relevant.

Yes. The final review checks identity, period, form, material figures, tax payment, supporting documents, verification method, and internal consistency. The submission proceeds only after unresolved issues and assumptions have been communicated to the client.

Ready when you are

Ready to get started with tan registration?

One free call. A real expert. A clear quote, no surprises.

₹999+ govt feeGet free quote