TDS Compliance

TDS compliance should stay connected from the underlying payment to the return.

TaxGraph supports businesses with recurring TDS compliance across the deduction, deposit, return and reconciliation process, with attention to the accounting and transaction information behind it.

Discuss your TDS requirement See where TDS differences arise

A filing acknowledgement confirms that a return was filed. It does not by itself show that the underlying deduction, deposit and accounting records are fully reconciled.

The return is one link in the chain

The return may be filed. The TDS trail may still contain unresolved items.

TDS is often managed as a quarterly event. The difficulty usually sits earlier than that — in whether the payment, the deduction, the deposit and the reported figure still refer to the same thing by the time the return is prepared.

  1. The accounting record and the return information do not fully agree

    What the books show as deducted and what the return reports are close, but not the same, and the difference has not been established.

  2. Deduction is identified after the transaction is already recorded

    The requirement is picked up during review rather than at the point of payment or booking, which turns a straightforward deduction into a correction.

  3. Deducted and deposited amounts need reconciliation

    The two are assumed to agree because both were done in the same period, rather than because they were compared.

  4. Challans exist, but the mapping needs review

    The deposits have been made. How they are allocated across deductees, periods and categories is less certain.

  5. Party or PAN information is incomplete or incorrect

    Master information gaps surface at the point of filing, when there is least time to go back to the party and resolve them.

  6. Differences from an earlier period continue into the next return

    An item that should have been closed is carried forward on the understanding that it will be dealt with later, and then is not.

  7. Corrections remain pending

    A correction is identified and agreed in principle, but nobody owns taking it through to completion.

  8. Accounting and TDS are handled separately

    Two processes work on the same underlying payments without reconciling to each other, so each looks complete on its own terms.

  9. Information reaches the TDS process too close to the compliance date

    There is time to file, but not enough time to question what is being filed.

  10. Management sees filing status, not open items

    The reporting confirms that the return went in. It does not show what remained unresolved behind it.

Not every business has all of these, and a difference is not the same thing as non-compliance. But where several appear together, TDS is usually being managed at the return rather than along the chain that leads to it.

Where differences arise

One TDS amount should be traceable through the whole compliance chain.

Each link below can be completed correctly on its own and still leave the chain broken. The useful question is not whether every step was done, but whether the same amount can be followed from the transaction through to the reported record — try it below.

HOLDS TO DEPOSIT, OPEN FROM THERE Follow-up required

Differences that commonly enter the chain:

  • Amount difference
  • Period difference
  • Challan mapping
  • Party information
  • Correction required
  • Information pending

Tracing helps identify where a difference has entered the chain. The appropriate TDS treatment depends on the underlying facts and the applicable requirements, and tracing does not by itself confirm complete statutory compliance.

What the service covers

TDS compliance support, scoped to what the business actually needs.

TDS requirements differ by the nature of the payments involved, the number of registrations, and how well the underlying records are maintained. What follows is the range of work this service covers.

Depending on the agreed scope, TDS Compliance support may include:

  1. TDS information review

    Review of the relevant payment, accounting and party information used for TDS compliance, so that what feeds the process has been looked at rather than simply passed through.

    This assumes the underlying accounting information exists. Producing or correcting the books themselves is separate unless specifically agreed.

  2. Deduction-related compliance support

    Support around identifying and processing the applicable TDS requirements for the transactions covered, based on the facts and information available within the agreed engagement.

    The correct treatment of any transaction depends on its underlying facts and the applicable requirements. Where information is incomplete or a position is genuinely uncertain, that is raised rather than assumed.

  3. Deposit and challan coordination

    Support around deposit-related information and the relevant challan records, so that what was deducted and what was deposited can be tied together rather than assumed to agree.

    TaxGraph does not fund, authorise or make tax payments on behalf of a business. Payment remains with the business.

  4. TDS returns

    Preparation of, and support for, the applicable recurring TDS returns within the agreed scope. Which returns and which registrations are covered is set in the engagement rather than assumed.

  5. Reconciliation

    Where included, reconciliation between the relevant accounting information, the TDS deduction records, the challan and deposit records, and the return information — and identification of the differences that need follow-up.

  6. Party and master information follow-up

    Identification of the party, PAN and master information issues that affect the agreed TDS compliance process, so they can be resolved with the party rather than discovered at the point of filing.

    Vendor onboarding and vendor master administration are separate functions and are not automatically included.

  7. Corrections and open items

    Tracking of, and support for, relevant return corrections, differences and unresolved items, so that open positions stay visible instead of being carried quietly into the next period.

  8. Coordination with the accounting function

    Working with the existing accountant or accounts team where TDS compliance depends on the underlying books. This is coordination, not a takeover of the accounting work.

Not every item above forms part of every engagement. What is included, which requirements are covered and how often the work runs are agreed before the engagement begins.

How the work runs

A recurring sequence that starts at the transaction, not the return.

Each stage exists to keep the next one connected to the one before it. Most recurring TDS difficulty comes from starting at the return and working backwards under time pressure.

  1. 01

    Payment / booking

    Start with the underlying business transaction or accounting entry that gives rise to the requirement.

  2. 02

    Review

    Identify the relevant TDS treatment based on the facts available and the scope agreed.

  3. 03

    Deduct

    Capture the applicable deduction information against the transaction it belongs to.

  4. 04

    Deposit

    Connect the deductions with the relevant tax deposit and challan information.

  5. 05

    Report

    Prepare the relevant TDS return information for the period covered.

  6. 06

    Reconcile

    Compare the accounting, deduction, deposit and return records against each other.

  7. 07

    Follow up

    Track corrections, information gaps and unresolved items through to a conclusion.

The last stage is the one most often missing. Without it, the same differences reappear in the next return and the process restarts from the same position.

Where this service fits

TDS Compliance may be relevant where a business

  • has recurring TDS obligations and needs ongoing compliance support
  • already has an accountant or finance team, but needs dedicated TDS support alongside them
  • wants deduction, deposit and return information kept connected rather than handled separately
  • sees the same challan, return or accounting differences returning period after period
  • needs clearer follow-up of corrections and unresolved TDS items
  • wants TaxGraph to coordinate with the existing accounting function rather than replace it
  • needs recurring TDS support under an agreed scope rather than ad-hoc help

It is a different requirement where a business

  • primarily needs payroll processing and salary administration rather than TDS compliance
  • primarily needs the underlying accounting records brought up to date
  • needs formal representation, appellate work or a specialist legal opinion
  • needs the business Income Tax return rather than recurring TDS compliance
  • is looking for statutory audit, assurance or certification

Not sure which of those describes the situation? Start with the situation and the appropriate scope can be identified from there.

Start with the situation

What is actually happening?

Scope and responsibilities

What is included depends on what is agreed.

TDS engagements vary by the nature and volume of the payments involved, the registrations covered, the state of the underlying records, and how much reconciliation and correction work is required. Scope is defined before the engagement begins rather than assumed from a service description.

The business remains responsible for making the tax payments themselves and for providing complete and accurate information in time for the work to be done properly. Which requirements, which registrations and what frequency are covered is set out in the engagement.

None of this is meant to narrow the service. It is meant to make the engagement predictable, so that what TaxGraph is responsible for and what the business is responsible for are clear from the start.

There are also limits that no adviser can remove:

  • TaxGraph cannot guarantee that no interest, late fee, disallowance, notice, default or correction will arise
  • reconciliation identifies differences; it does not determine the correct tax treatment on its own
  • the treatment of a transaction depends on its underlying facts and the applicable requirements
  • government system availability and authority processing are outside TaxGraph’s control

Scoped separately from the recurring engagement:

  • earlier-period differences, pending correction statements and unresolved historical matters, which usually need catch-up work before a recurring process runs cleanly — what is possible depends on the periods and records involved, what can be established from the available information, the current position on the relevant systems, and the applicable requirements at the time the work is done

Unless specifically included in the agreed scope, this service does not cover:

  • payroll processing, salary computation, employee and HR administration, attendance and leave records, and reimbursement or benefit administration
  • accounting and bookkeeping work on the underlying records
  • accounts payable processing, vendor onboarding and vendor master administration
  • the business Income Tax return and computation, which is a separate requirement
  • TCS or other withholding and collection requirements, which are scoped separately where relevant
  • formal litigation, appellate work, contentious representation or specialist legal opinions
  • non-resident and international tax positions, which may require separate specialist review
  • statutory audit, assurance or certification of any kind

Before you get in touch

Frequently asked questions

Start with the TDS requirement

Tell us what is happening with your TDS compliance.

Whether the issue is recurring deduction, deposit, return filing, reconciliation or an unresolved difference, start with the situation and TaxGraph can help define the appropriate scope.

If it is easier to talk it through first, a short introductory call is usually the quickest way to establish whether this is the right service.

Discuss your TDS requirement Book a 20-minute introductory call