TDS, TCS and Other Statutory Requirements

Introduction and context

Tax Deducted at Source (TDS) and Tax Collected at Source (TCS) are compliance mechanisms under India’s Income-tax Act, 1961. They require a payer or specified seller to collect or deduct tax at the time prescribed by law and deposit it with the Central Government. The person responsible must also report the transaction, issue prescribed certificates and preserve evidence.

Tally.ERP 9 can automate much of the accounting and compliance workflow, but it is not a substitute for statutory interpretation. Correct results depend on the assessment year, nature of payment, deductee or buyer status, threshold limits, PAN validity, applicable rate, timing rule and changes introduced by legislation or departmental notifications. A professional accountant must therefore distinguish between:

• the legal obligation;
• the accounting entry;
• the software configuration; and
• the return, payment and documentation obligation.

This distinction is especially important because Tally.ERP 9 is a legacy product. Its statutory capabilities, reports and return formats may not reflect every later amendment, portal requirement or procedural change. Final compliance should be validated against current law and the relevant government portal.

Learning objectives

After studying this chapter, the learner should be able to:

1. explain the legal and accounting logic of TDS and TCS;
2. determine the relevant transaction, threshold, rate and timing considerations;
3. configure TDS and TCS features in Tally.ERP 9;
4. record deductions, collections, reversals, exemptions and adjustments;
5. reconcile ledgers with challans, certificates and returns;
6. evaluate compliance risks arising from incorrect master data or outdated software; and
7. design a controlled monthly and quarterly compliance process.

1. Conceptual foundations

1.1 TDS

TDS shifts part of the tax-collection responsibility from the recipient of income to the payer. A payer deducts tax from an eligible payment and pays the net amount to the recipient. The deducted amount is a liability of the payer until deposited with the Government.

A simplified accounting relationship is:

The formula is an accounting identity, not a universal legal formula. It applies where deduction is required and the amount is represented before TDS. The rate and base must be determined under the applicable provision. GST, reimbursements, surcharges, cess and other components may require separate legal analysis.

Example: If a contract bill is ₹100,000 and the applicable TDS is ₹1,000, the entry normally recognises expense of ₹100,000, credits the supplier with ₹99,000 and credits TDS payable with ₹1,000. This example assumes that the entire bill is subject to deduction and ignores GST and other statutory complications.

1.2 TCS

TCS is generally collected by a seller or specified person from a buyer or other counterparty in transactions covered by the relevant provision. The collected amount is added to the amount recoverable from the buyer, unless the transaction documentation and law prescribe another treatment.

A simplified relationship is:

This is applicable only where TCS is legally chargeable and the stated base is correct. It does not mean that every sale attracts TCS. The nature of goods or transaction, buyer category, threshold, declaration, PAN status and special provisions must be examined.

1.3 TDS and TCS compared

2. Legal decision framework

A reliable compliance decision should proceed through the following sequence.

Step 1: Identify the legal provision

Classify the payment or receipt: for example, contract, professional service, rent, commission, interest, purchase or sale of specified goods, or another notified category. Similar accounting descriptions can have different legal consequences.

Step 2: Identify the parties

Determine whether the counterparty is an individual, company, firm, government body, non-resident or another specified person. PAN status and declarations may affect the rate or obligation. The accounting ledger should contain the correct tax registration and identification details.

Step 3: Test threshold and exceptions

Many provisions operate only after a transaction-level or aggregate threshold is crossed. Thresholds can differ by section and may change through annual legislation. Exemptions may arise from a declaration, certificate, lower or nil deduction order, specified status, nature of payment or statutory exclusion.

An exemption is not the same as deleting a tax ledger. It must be supported by evidence and applied only to the relevant period and transaction.

Step 4: Determine the rate and base

The applicable rate may depend on the section, residential status, PAN availability, surcharge, cess, special rate and effective date. The base may be gross payment, specified component, amount exceeding a threshold or another statutory amount. A rate stored in Tally is an implementation parameter, not proof that the rate is legally correct.

Step 5: Determine the timing

The law may prescribe deduction at credit, payment, receipt or another event, whichever occurs earlier or as otherwise specified. Tally entries must therefore be dated to reflect the legal event, not merely the date on which the invoice is entered.

Step 6: Deposit, report and certify

After deduction or collection, the entity must deposit the amount within the prescribed time, file the appropriate statement and issue the applicable certificate. A correct journal entry without payment and reporting is incomplete compliance.

3. Configuration in Tally.ERP 9

The exact menu names differ by release, localisation and statutory patch. The following is a conceptual configuration sequence; users should confirm the screen labels in their installed release.

3.1 Company-level settings

Enable TDS under statutory or taxation features and enter the organisation’s deductor details, including TAN and relevant registration information. Select the correct financial year and configure the company’s books to match the statutory reporting period.

For TCS, enable the TCS feature where the business is legally liable to collect. Enter the required collector details and verify the company’s address and identification particulars.

Important controls include:

• correct company jurisdiction and financial year;
• valid TAN, PAN and registration data;
• appropriate accounting method and voucher numbering;
• activation of the relevant statutory feature;
• backup before changing tax configuration; and
• confirmation that the latest statutory patch is installed.

3.2 Ledger masters

Create or amend ledgers systematically.

Expense or purchase ledgers. Classify them according to the nature of payment. A single ledger called “Professional and Contract Expenses” may be convenient but can produce incorrect section mapping.

Party ledgers. Record the supplier or buyer’s legal name, address, PAN, party type and other required particulars. A missing or invalid PAN can cause a higher deduction or collection consequence under applicable law.

TDS ledgers. Create liability ledgers for relevant TDS categories or sections. The ledger should be configured as a statutory liability and mapped to the appropriate tax section.

TCS ledgers. Create collection ledgers with the correct nature of goods or transaction and applicable rate parameters.

Bank and challan ledgers. The bank ledger records payment; statutory liability ledgers record the amount due to the Government. Do not post tax payments directly as expenses unless the entry reflects a legally supportable treatment.

3.3 Nature of payment and tax-rate masters

Tally.ERP 9 typically uses nature-of-payment or tax-category masters to connect a transaction with a section, threshold and rate. These masters must be reviewed whenever a Finance Act, circular, notification or judicial interpretation changes the law.

A sound master-data register should record:

3.4 TCS configuration

For TCS, configure the appropriate stock item, sales ledger, party ledger and TCS category. The software must know whether the item or transaction falls within the statutory category. TCS should not be activated merely because a customer is a dealer or because the invoice is large.

Where Tally cannot represent a complex rule, the accountant should use a controlled manual adjustment supported by a tax computation sheet rather than forcing an inaccurate automated configuration.

4. Transaction processing

4.1 TDS on a purchase or expense voucher

A typical process is:

1. enter the supplier invoice with the correct date;
2. select the expense or purchase ledger mapped to the relevant nature of payment;
3. select the supplier ledger containing PAN and party details;
4. allow Tally to calculate TDS, or enter a controlled adjustment where necessary;
5. verify the gross amount, deduction base, rate and threshold treatment;
6. save the voucher and review the resulting TDS liability; and
7. reconcile the supplier balance with the remittance advice.

The accounting result should normally show the gross expense, net supplier payable and TDS payable separately. This preserves auditability.

4.2 TDS journal approach

A journal may be appropriate where the deduction is recognised separately from the original invoice or where an adjustment is required. The entry should identify the source voucher and explain the reason. Unreferenced journal entries are a major audit risk because they obscure the point at which the statutory obligation arose.

4.3 TCS on sales

A typical process is:

1. identify whether the sale is legally within a TCS category;
2. verify the buyer’s status, PAN and any declaration or exemption;
3. select the applicable stock and sales ledgers;
4. calculate TCS on the legally relevant base;
5. add the collection to the receivable where required;
6. print or issue an invoice showing the collection distinctly; and
7. reconcile the TCS ledger to the sales register and return data.

4.4 Exemptions, lower deduction and nil deduction

Exemptions may be transaction-specific, party-specific, period-specific or document-specific. The accounting system should retain a reference to the supporting certificate or declaration.

A control register should include:

• certificate or declaration number;
• issuing authority or responsible person;
• applicable section;
• authorised limit, if any;
• validity dates;
• parties and transactions covered; and
• reviewer and approval date.

When an exemption expires, the master must be updated immediately. A common failure is continuing nil deduction after the certificate has ceased to apply.

5. Adjustments and special accounting situations

5.1 Credit notes and cancellations

If an invoice is cancelled before the statutory event or if a credit note changes the taxable base, the TDS or TCS consequence must be considered separately from the commercial adjustment. A credit note does not automatically reverse a statutory liability in every case.

5.2 Advances

An advance may trigger TDS or TCS where the relevant provision uses payment or receipt as the trigger. The accountant should not assume that tax waits until the final invoice. The voucher should identify the advance and later settlement clearly.

5.3 Year-end provisions

A provision credited to a supplier or expense account may create a TDS issue depending on the statutory rule and facts. If the provision is reversed and rebooked, the entity must preserve the audit trail showing the original credit, deduction and reversal.

5.4 Reimbursement and GST components

Whether reimbursement or GST is included in the deduction base depends on the applicable law, contractual structure, invoice presentation and prevailing guidance. Tally cannot determine this from the word “reimbursement” alone. The tax working paper should state the legal basis for inclusion or exclusion.

5.5 Wrong deduction and correction

If the wrong rate or section is used, do not silently overwrite the original voucher. Pass a dated correction or adjustment entry, document the reason, reconcile the revised liability and assess whether a correction statement or communication is necessary.

6. Challans, certificates and returns

6.1 Challan process

Before generating a challan, reconcile the liability ledger with transaction reports. The reconciliation should cover:

• opening balance;
• current-period deductions or collections;
• reversals and corrections;
• payments already made;
• interest or other statutory amounts; and
• closing balance.

The accounting equation is:

This identity assumes that interest, fees and penalties are separately identified if they are included in the reconciliation. It is a control equation, not a substitute for the legally prescribed challan calculation.

A challan payment entry should debit the relevant statutory liability and credit bank. Interest or late fee should be recorded separately where appropriate so that management can distinguish tax from cost of non-compliance.

6.2 Certificates

TDS certificates, such as Form 16 or Form 16A where applicable, and TCS certificates must be generated or downloaded in the prescribed format and within the prescribed time. The certificate should agree with the filed statement and the recipient’s tax credit information.

The accountant should verify name, PAN, amount, tax deducted or collected, period and challan details. A certificate generated from an unreconciled ledger can communicate incorrect information even if the voucher totals appear reasonable.

6.3 Statements and returns

Periodic statements require transaction-level accuracy. Before filing, reconcile:

1. Tally transaction reports;
2. challan data and bank confirmation;
3. PAN and party master data;
4. certificates or lower-deduction records;
5. correction statements; and
6. portal validation results.

A return utility or portal may reject records because of format, validation or identification errors. Tally’s report should therefore be treated as a source for review, not as conclusive evidence of successful filing.

7. Worked application

Illustrative example: professional fee with TDS

A company records a professional fee invoice of ₹80,000. Assume, solely for illustration, that the applicable law requires TDS at 10%, that the entire amount is subject to deduction, that no surcharge or cess applies, and that the statutory event occurs in the current period.

The accounting entry is:

When the consultant is paid:

When TDS is deposited:

The calculation assumes a simple case. In practice, the accountant must test the relevant section, threshold, payment or credit trigger, PAN status, GST treatment, certificate and current rate before posting.

8. Illustrative case study: Meridian Components Ltd.

Background

Meridian Components Ltd. uses Tally.ERP 9 for purchase, sales and statutory accounting. During a quarterly review, the finance manager finds that TDS payable in Tally is ₹486,000, while challans deposited total ₹450,000. The supplier register also contains duplicate PAN records, and a nil-deduction certificate for one consultant expired during the quarter.

Problem

The apparent difference of ₹36,000 may represent unpaid tax, a timing difference, a reversal not reflected in the return, or a master-data error. The expired certificate creates a risk of short deduction. Duplicate PANs may cause statement rejection or incorrect tax credit.

Analysis

The team extracts the TDS payable report by section and month, then matches each item to the purchase register. It identifies:

• ₹20,000 relating to a correctly recorded deduction whose challan was paid after the reporting cut-off;
• ₹10,000 reversed through a journal entry without a linked source voucher; and
• ₹6,000 relating to fees recorded after the consultant’s nil-deduction certificate expired.

The balance therefore cannot be treated as one homogeneous error.

Approach and solution

The company:

1. confirms the ₹20,000 timing difference with bank evidence;
2. investigates and documents the ₹10,000 reversal, correcting the voucher linkage;
3. recalculates the ₹6,000 deduction under the current applicable rule;
4. updates the consultant master and certificate register;
5. validates PAN data and removes duplicate records only after preserving the audit trail;
6. pays or adjusts the resulting liability according to professional advice; and
7. performs a return and certificate impact assessment.

Outcome

The company obtains a reconciled liability schedule, corrects the master data, identifies a possible short deduction before assessment and establishes a monthly review. The major improvement is not merely the corrected amount; it is the linkage between legal evidence, accounting records, payment and reporting.

Learning points

• A ledger balance is not automatically a compliance balance.
• Timing differences must be evidenced, not assumed.
• Exemption documents require expiry controls.
• Manual journals need source-voucher references.
• PAN and master-data quality directly affect statutory reporting.

9. Compliance risks and governance

9.1 Common risks

Wrong classification: Similar descriptions may belong to different statutory sections.

Outdated rates: A rate configured in an old release may remain active after a legal change.

Threshold failure: Aggregation across branches, invoices or months may be missed.

Invalid PAN: Incorrect or missing PAN may cause higher deduction or reporting mismatch.

Timing failure: Tax may be deducted late even though the invoice was entered on time.

Unreconciled challans: Payment may be made but not matched to the correct liability or statement.

Unauthorised overrides: Users may disable TDS or alter rates without review.

Incomplete evidence: Certificates, declarations and approvals may not be retained.

9.2 Internal control framework

A post-graduate accounting function should implement segregation of duties:

• procurement identifies the transaction;
• accounts payable records it;
• the tax reviewer validates section and rate;
• treasury deposits the liability; and
• a compliance reviewer reconciles the return and certificate.

Useful controls include maker-checker approval, locked tax masters, monthly exception reports, access logs, version-controlled backups and a statutory calendar. The reviewer should sample both transactions where tax was deducted and transactions where tax was not deducted.

9.3 Ethical and professional responsibilities

Avoiding TDS or TCS through artificial splitting, misclassification, backdating, suppression of invoices or misuse of exemptions is not legitimate tax planning. Chartered accountants and finance professionals must maintain objectivity, document judgement and communicate uncertainty to management. Where law is unclear, the working paper should state the interpretation, evidence, materiality and escalation decision.

10. Version-specific limitations and contemporary practice

Tally.ERP 9 may support statutory configuration and reports, but limitations can arise from:

• an old statutory patch;
• changes in income-tax forms or portal schemas;
• new transaction categories not mapped in the software;
• inability to model complex threshold aggregation;
• incomplete integration with electronic filing systems;
• incorrect customisation of tax masters; and
• differences between book dates and legally relevant event dates.

Accordingly, an organisation should maintain a release register showing the installed version, statutory patch, date tested and responsible reviewer. Before each financial year, it should compare the software configuration with current law, official utilities, portal validations and professional guidance.

Technology can improve compliance through API-enabled reconciliation, PAN validation, exception analytics and workflow approvals. AI may assist in classifying transactions or identifying unusual rates, but it should not make unsupervised legal decisions. An AI-generated classification must be reviewed against the statute, facts and effective date. Confidential taxpayer data should also be protected under the organisation’s privacy and information-security policies.

Best-practice operating cycle

A practical operating cycle is:

1. maintain current legal-rate and section tables;
2. capture complete supplier and buyer master data;
3. classify every relevant transaction at entry;
4. review exemptions before posting;
5. run monthly TDS/TCS exception reports;
6. reconcile liability ledgers to source registers;
7. prepare and approve challans;
8. match bank payments to challans;
9. validate return data before submission;
10. issue certificates only after reconciliation; and
11. archive vouchers, declarations, certificates, challans, filings and correction evidence.

Chapter Summary

TDS and TCS combine legal classification, accounting recognition, payment, reporting and documentation. TDS normally reduces the amount payable to a recipient and creates a liability in the payer’s books; TCS generally increases the amount recoverable from the buyer and creates a liability of the collector. Tally.ERP 9 can support configuration, voucher processing, ledger reporting and reconciliation, but the software does not determine the law.

Effective compliance requires correct section selection, party identification, threshold testing, rate and base determination, timing analysis, exemption control and reconciliation. Challans, certificates and returns are integral parts of the process. Credit notes, advances, year-end provisions, reimbursements and GST components require fact-specific analysis. The principal risks are outdated configuration, wrong master data, unlinked adjustments, invalid exemptions and failure to reconcile books with portal records. A controlled workflow, current statutory patch, maker-checker review and documented professional judgement are essential.

Key Terms

TDS: Tax deducted by a person responsible for making a specified payment.

TCS: Tax collected by a seller or other specified person on covered transactions.

Deductor: Person responsible for deducting tax at source.

Collector: Person responsible for collecting tax at source.

Deductee: Recipient from whose payment TDS is deducted.

TAN: Tax Deduction and Collection Account Number used for specified tax reporting.

PAN: Permanent Account Number used for taxpayer identification.

Nature of payment: Statutory classification connecting a transaction with a TDS provision.

Threshold: Statutory amount or condition beyond which deduction or collection applies.

Exemption: Legal basis for non-deduction or non-collection in specified circumstances.

Lower-deduction certificate: Authority permitting deduction at a lower or nil rate, subject to its terms.

Challan: Prescribed instrument or electronic payment record for depositing tax.

TDS payable: Liability representing tax deducted but not yet deposited.

TCS payable: Liability representing tax collected but not yet deposited.

Tax base: Amount on which the statutory rate is applied.

Statutory patch: Software update intended to reflect legal or filing changes.

Correction statement: Revised statutory statement filed to correct reported data.

Reconciliation: Comparison of books, payment evidence, certificates and return records.

Maker-checker control: Separation between transaction preparation and review or approval.

Review Questions

Short Answer Questions

1. Distinguish between TDS and TCS from the perspective of the responsible person and accounting effect.
2. Why must PAN and party master data be validated before statutory reporting?
3. What is the purpose of a nature-of-payment master in Tally.ERP 9?
4. Why is a nil-deduction certificate not equivalent to permanently disabling TDS?
5. Identify two limitations of relying solely on Tally.ERP 9 for statutory compliance.

Long Answer Questions

1. Explain the complete TDS lifecycle from transaction classification to certificate issuance and return reconciliation.
2. Describe how TDS and TCS should be configured and controlled in Tally.ERP 9.
3. Discuss the treatment and compliance risks associated with advances, credit notes, year-end provisions and reimbursements.
4. Explain the role of challan reconciliation in preventing statutory reporting errors.
5. Evaluate the governance, ethical and version-control responsibilities of a professional accountant using legacy accounting software.

Analytical / Application Questions

1. A company’s TDS ledger exceeds challan payments, but management believes all tax has been deposited. Design a reconciliation procedure that distinguishes timing differences, reversals, short payments and reporting errors.
2. A supplier’s lower-deduction certificate expires midway through a quarter. Explain the accounting, master-data, documentation and return actions required.
3. A TCS transaction is correctly classified commercially but the software applies an outdated rate. Analyse the risks and propose a controlled correction process.

Multiple Choice Questions with Answers

Question 1

Which statement best describes TDS?

A. Tax added to every sales invoice

B. Tax deducted by the payer from a specified payment

C. Tax paid only by the recipient after assessment

D. A voluntary advance payment unrelated to a transaction

Correct Answer: B. Tax deducted by the payer from a specified payment

Question 2

What is the usual accounting effect of TDS on an eligible supplier invoice?

A. The supplier payable is increased by the TDS amount

B. The expense is eliminated

C. The supplier payable is reduced and a TDS liability is created

D. The bank is credited for the TDS amount immediately

Correct Answer: C. The supplier payable is reduced and a TDS liability is created

Question 3

Which item is most important when mapping a transaction to a TDS category in Tally.ERP 9?

A. The colour of the voucher screen

B. The legal nature of the payment

C. The supplier’s preferred invoice format

D. The number of inventory godowns

Correct Answer: B. The legal nature of the payment

Question 4

A nil-deduction certificate should generally be treated as:

A. Permanent permission for all future transactions

B. Evidence that no PAN is required

C. A document subject to its terms, scope and validity period

D. A replacement for filing statutory statements

Correct Answer: C. A document subject to its terms, scope and validity period

Question 5

If professional fees of ₹80,000 are subject to an illustrative TDS rate of 10%, what is the TDS?

A. ₹800

B. ₹8,000

C. ₹72,000

D. ₹88,000

Correct Answer: B. ₹8,000

Question 6

Which entry normally records deposit of TDS already deducted?

A. Debit bank and credit TDS payable

B. Debit expense and credit supplier

C. Debit TDS payable and credit bank

D. Debit sales and credit bank

Correct Answer: C. Debit TDS payable and credit bank

Question 7

What is the primary purpose of challan reconciliation?

A. To replace the purchase register

B. To match statutory liabilities with deposits and evidence

C. To calculate inventory valuation

D. To remove all manual review

Correct Answer: B. To match statutory liabilities with deposits and evidence

Question 8

Which is a significant risk of using an outdated Tally.ERP 9 statutory configuration?

A. Automatic correction of every legal change

B. Application of obsolete rates or return formats

C. Elimination of the need for PAN

D. Prevention of all journal entries

Correct Answer: B. Application of obsolete rates or return formats

Question 9

In the illustrative Meridian case, which item represented a documentation and timing risk?

A. A certificate that expired during the quarter

B. A bank account with no transactions

C. A stock item with a reorder level

D. A sales invoice with a unique number

Correct Answer: A. A certificate that expired during the quarter

Question 10

Which control best supports reliable statutory compliance?

A. Allowing users to change tax rates without approval

B. Deleting original vouchers after correction

C. Maker-checker review with reconciliation to challans and returns

D. Using one generic expense ledger for every payment

Correct Answer: C. Maker-checker review with reconciliation to challans and returns