Skip to content

TDS Receivables: Why TDS Reconciliation Is a Blind Spot for Accounts Receivable Teams

Learn how TDS receivables arise, the challenges of TDS reconciliation, and how integrated AR solutions help improve matching and TDS recovery.

Kumar Karpe, co-founder and CEO of KapittxKumar KarpePublished 3 August 2026Updated 4 August 20267 min read
Tax & Compliance

TDS Receivables: Why TDS Reconciliation Is a Blind Spot for Accounts Receivable Teams

Understanding TDS Receivables

India is one of a handful countries of the world, which has a Tax Deducted at Source (TDS) on domestic commercial transactions. TDS, by definition, is a tax deducted by the payer on behalf of the recipient, and the recipient can then claim credit for it in their tax filings.

TDS is typically applicable on Service transactions, since the presumption is that there is a high profit margin, which the government needs to collect the tax on time and not wait until the end of the quarter.

How the TDS Receivables Process Works

TDS receivablesHow the TDS Receivables Process Works
  1. 01Supplier ASupplier A provides services to Customer B worth Rs 100 plus GST 18% = Rs 118 invoice value.
  2. 02Customer BCustomer B pays the invoice as per the Payment Terms.
  3. 03Customer BCustomer B deducts (say) 10% of the basic value (Rs 100), i.e. Rs 10, from the overall payment of Rs 118.
  4. 04Supplier ASupplier A records the short payment as a TDS Receivable in their books.
  5. 05Customer BCustomer B deposits the Rs 10 with the Government Treasury by the 7th of the following month.
  6. 06Customer BCustomer B files a quarterly return giving the date of transaction, base amount on which TDS was deducted, TDS deducted and TDS deposited.
  7. 07Income-tax departmentWhen all returns are filed by the deadline, the Income-tax department compiles the data in Form 26AS, available to Supplier A.
  8. 08Supplier ASupplier A downloads Form 26AS, which includes deposits from Customer B and many more, and tries to reconcile it with the TDS Receivable in their books.
  9. 09ClosedIdeally, if all details are mentioned correctly, the deposit in Form 26AS should match the expected TDS Receivable, and the process can be closed.
  • Supplier A has provided services to Customer B worth Rs 100 plus GST 18% o Rs 118 invoice value.
  • Customer B then pays the invoice as per the Payment Terms.
  • Customer B deducts (say) 10%of the basic value (Rs 100 i.e. Rs 10) from the overall payment of Rs 118.
  • Supplier A records the short payment as a TDS Receivable in their books
  • Customer B, then deposits the Rs 10 with the Government Treasury by the 7th of following month.
  • Customer B then files a quarterly return giving a breakdown of the TDS deducted and deposited by them. In this, they are supposed to mention date of transaction, base amount on which TDS was deducted, the actual TDS deducted and the TDS deposited
  • When all returns are filed by the deadline, the Income-tax department compiles the data in a format called Form 26AS, which is available to each deductee i.e. the Supplier A in our case
  • Our Supplier A, will download the Form 26AS, which will include deposits from Customers B, and many more and try to reconcile the TDS Receivable in their books (see Step 4) with the Form 26AS entries
  • Ideally, if all the details are mentioned correctly, the deposit in Form 26AS should match the expected TDS Receivable and the process can be closed.

Challenges in TDS Reconciliation

Why TDS reconciliation breaksForm 26AS does not have a provision for Invoice Numbers, so lookup reconciliation based on a unique reference will not work.

TDS Receivable in your books

Form 26AS

  • Mismatch in transaction valueThe customer deducts TDS on the total invoice value; you expect it on the base value
  • Mismatch in TDS ratesYour system expects 2%; the customer deducted 10%
  • Timing differencesPayment received in July, reported in August, and worse if it spills across Financial Years
  • Accrual v/s payment dateTDS may be deposited in the month the payment was accrued, not when it was paid
  • Wrong PAN number reportedThe TDS credit accrues to some other party
  • Clubbing of invoicesMultiple invoices reported as one single transaction in the TDS return
  • Splitting of invoicesOne invoice, multiple entries in Form 26AS
  • Lower TDS ratesThe customer ignores your lower TDS rate certificate and deducts at standard rates
  • Customer defaulting on TDS depositsShort paid citing TDS, but not deposited with Government
  • Customer not filed TDS returnTDS deposited on time, but without the quarterly return there is no way to claim the credit

Real-time reconciliation, integrated with AR Collections, so that

  • Mismatches are identified in time
  • Only Exceptions are communicated to the Customer
  • TDS Recovery communication is tracked and made part of routine Collections, with added Urgency for filing deadlines

TDS Receivable is an outcome of Accounts Receivable. TDS Form 26AS reconciliation cannot be a part-time activity, as it can mean a real hit to the bottom-line.

  • Form 26AS does not have a provision for Invoice Numbers, therefore, the Lookup reconciliation based on a unique reference will not work
  • Mismatch in Transaction value: Customer deducts TDS on total invoice value whereas, you are expecting TDS on base value
  • Mismatch in TDS rates: Your system shows that TDS is supposed to be deducted at 2%, whereas Customer has actually deducted at 10%
  • Timing Differences: Your system shows payment received in July, while Customer may have reported the transaction in August. Worse, if this spills across Financial Years
  • Accrual v/s Payment date: Customer may have deposited the TDS in the month in which they accrued the payment and not when they paid. Again, leading to a wild goose chase to match the TDS
  • Wrong PAN number reported: Customer may have deducted and deposited the TDS, but has made an error in his TDS return by mentioning the wrong PAN number. In this case, the TDS Credit will accrue to some other party
  • Clubbing of invoices: Many Customers tend to club multiple invoices in their system and report it as one single transaction in their TDS return. This makes the matching a very difficult tax
  • Splitting of invoices: Some Customers record a single invoice as multiple transactions in their ERPs due to internal Cost allocations. In these cases, there could be multiple entries in Form 26AS for a single invoice. The reverse of clubbing invoices, and equally painful to identify the breakup
  • Lower TDS rates: If you have obtained lower TDS rate Certificate from Income tax department for certain transactions, yet the Customer ignores the certificate rates and continues to deduct at standard rates.
  • Customer defaulting on TDS deposits: Customer has short paid you, citing TDS deduction, but has not deposited the amount with Government. This is an offence under Income Tax law, but lack of a robust timely reconciliation, means you detect this anomaly quite late to take effective action
  • Customer not filed TDS return: Even though they may have deposited the TDS on time, if they don’t file the quarterly return, there is no way you can the credit for the TDS deducted.


Organizational Challenges of TDS Reconciliation

Many large organizations have separate departments handling routine AR Collections and TDS Reconciliation. Typically, TDS is with the Taxation department, since it is felt that it is a regulatory compliance matter.

However, the problem with this approach is that TDS Receivable is an outcome of Accounts Receivable. Tax departments may not have the bandwidth nor the relationships with Customers like AR Collection teams have.

All this results in significant delays by the time a mismatch is identified, triaged and sent to the customer for resolution.

These delays could cost the organization, potential write offs, if Customers refuse to resolve mismatches of previous Financial Years citing book closures.

Need for Real-Time TDS Reconciliation

From the above, it is clear that TDS Form 26AS cannot be a part-time activity, as it can mean a real hit to the bottom-line. Every Rupee of TDS not sighted in Form 26AS is a direct hit to revenue as you may have to write off the amount.

Organisations need to invest in real-time reconciliation solutions, which are integrated with AR Collections systems, so that:

  • Mismatches are identified in time
  • Only Exceptions are communicated to the Customer
  • TDS Recovery communication is tracked and made part of routine Collections with added Urgency for filing deadlines

The Payback of Integrated AR and TDS Reconciliation platforms

Unlike Standalone Reconciliation Solutions, Integrated AR and TDS Reconciliation solutions will be much more effective in reducing manual effort with 80% match rate. Collections teams can focus on exception cases with clear reasons like Timing Difference, Rate mismatch etc, and can proactively resolve them with Customer Collaboration.

Typical ROI for such platforms is achieved in less than one quarter.

Frequently asked questions

What is a TDS Receivable in accounts receivable?

A TDS Receivable is the portion of an invoice a customer withholds and deposits with the government on the supplier's behalf, instead of paying it directly. When a customer deducts TDS from an invoice, say, withholding Rs 10 from a Rs 118 invoice, the supplier records that withheld amount as a TDS Receivable, expecting to later claim it as credit once it appears in Form 26AS.

Why is Form 26AS difficult to reconcile with TDS Receivables?

Form 26AS doesn't carry invoice numbers, so a simple lookup match against the supplier's books isn't possible. Reconciliation instead depends on matching transaction value, TDS rate, timing, and other details, any one of which can create a mismatch even when the deduction itself was correct.

What are the most common causes of TDS mismatches?

Customers deducting TDS on the total invoice value instead of the base value, incorrect TDS rates being applied, timing differences between when a payment was received versus reported, accrual-date versus payment-date deposits, wrong PAN numbers on the customer's TDS return, and invoices being clubbed together or split apart differently than in the supplier's own records.

What happens if a customer deducts TDS but never deposits it with the government?

The customer has short-paid the supplier citing TDS, but hasn't actually deposited it with the government, this is an offence under Income Tax law. Without a robust, timely reconciliation process, this kind of default is typically detected too late for the supplier to take effective action.

Why doesn't filing a TDS deposit guarantee the supplier gets credit?

Even if a customer deposits the TDS on time, the supplier cannot claim credit unless the customer also files the corresponding quarterly TDS return. Without that return, there is no way for the supplier to get credit for the TDS that was deducted.

Should the AR team or the Tax/Compliance team own TDS reconciliation?

TDS Receivable is an outcome of the Accounts Receivable process, so AR Collections teams are better positioned to own it than Tax departments. Tax teams typically don't have the bandwidth or the customer relationships that Collections teams already have, and splitting ownership between departments causes significant delays in identifying, triaging, and resolving mismatches with customers.

What's the financial risk of delayed TDS reconciliation?

Every rupee of TDS not sighted in Form 26AS is a direct hit to revenue, since it may have to be written off. These delays can cost the organization, especially if customers refuse to resolve mismatches from previous financial years citing book closures.

What results can integrated AR and TDS reconciliation platforms deliver?

Compared to standalone reconciliation tools, integrated AR and TDS reconciliation platforms are more effective at reducing manual effort, with an 80% match rate. This lets collections teams focus on exception cases with clear reasons like timing differences or rate mismatches, resolving them proactively with the customer. Typical ROI for such platforms is achieved in less than one quarter.

Get the next post in your inbox

Monthly notes on AR, cash application, and finance automation. No filler.