xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Finance & Accounting/TDS & TCS: the withholding compliance cycle
CONCEPT · Last reviewed

TDS & TCS: the withholding compliance cycle

When you pay a contractor, book a rent bill, or sell above a section's threshold, income-tax law can require your company to hold back tax (TDS) or collect it (TCS) and pass it to the government. xMatix connects posting-time withholding, monthly challan actions, quarterly-return computation and certificates through the withholding register. Review each transition and its evidence; shared source data reduces re-keying but does not eliminate the need for reconciliation or access controls.

Read the challan

TDS challan form with all values visible and sections for period, amounts, deposit and CIN evidence
A withholding challan separates statutory period and section identity, deposited amounts, and bank or CIN evidence; status does not currently make the generic form immutable.UI captured
  1. 1

    Period & Code identifies the withholding nature, year, month, payment code and statutory section.

  2. 2

    Branch, major head and minor head complete the government payment classification.

  3. 3

    Tax Amount is separated from interest and fee components so the deposit remains explainable.

  4. 4

    Interest, late-deduction interest and fees preserve why the total exceeds the underlying tax.

  5. 5

    Deposit date, bank and CIN or challan serial fields retain payment evidence; restrict generic edits after posting because status alone is not a technical lock.

The challan form separates statutory classification from money and payment proof. Period year and month, nature, section code, payment code and major/minor heads say which obligation is being deposited. Tax amount is shown separately from interest, late-deduction interest and fees so reviewers can explain why the total differs from the underlying withholding. The values in the picture are invented sample data.

The Deposit & CIN section closes the loop from liability to evidence. Due date explains timeliness, deposit date proves when cash moved, bank GL account provides the book side and BSR code, challan serial or CIN fields provide the government acknowledgement. Before marking the challan paid, reconcile its tax amount to the undeposited register, its total to the bank posting and its statutory codes to the period's obligation.

The challan actions never change a deposited challan's amounts, but saving the record does not freeze a Deposited or Verified challan. A user with edit permission can change its fields, including amounts or status. Restrict edit access after deposit and audit any such change.

One-time setup

  • Provision the statutory catalog. On the TDS Sections screen, Provision Statutory Catalog loads the FY 2026-27 sections with their rates, thresholds and deduction points as data that you can edit. The button runs from a section, so tick a row on the list (or create a starter row first). Re-running it restores the shipped values on the catalog rows. Every field, how the row for a document is chosen, and how thresholds work are in TDS sections.
  • Record the company's TAN on the company account; every challan, return and certificate quotes it.
  • Classify your parties. On each vendor and customer: the PAN (without a valid one, the law forces deduction at the penal higher rate, and the return reports it with the corresponding remarks code), the deductee type (individual, company, firm…) which selects the rate on dual-rate sections, optionally a default TDS section that pre-tags new bill lines (a section you pick on the line always wins), and a TDS applicable switch for genuinely exempt parties.
  • Record lower/nil-deduction certificates. A certificate from the assessing officer is captured with its number, section, certified rate, amount limit and validity. It is applied automatically while it is Active, within its dates, and its remaining limit covers the whole transaction. Consumption is tracked, and a certificate stops applying on its own once its limit is used up or its validity ends. Certificate rows carry the proper remarks code on the return. See Lower deduction certificates.

Day to day — it happens at posting

  • Vendor bills and payments deduct at whichever point the section prescribes — bill, payment, or the earlier of the two — and never twice. The vendor's payable is reduced, so you naturally pay the net.
  • Customer invoices collect TCS on top: the receivable is increased by the collected amount, and a receipt against an invoice can trigger collection for sections that collect at payment time. Reversing an invoice reverses its collection cleanly.
  • Thresholds are assessed per party and section across the financial year. The year-to-date total counts only amounts already deducted. Documents that stayed below the thresholds are not added up, so check vendors with many small bills (see TDS sections).
  • Every event lands in the TDS Transactions register — party, PAN, section, rate, amount, and later the challan and certificate references. How rows are written, change status and are corrected is in TDS transactions. The TDS Summary screen in the Tax Center reports over this register; TCS Summary is built from invoices and their lines.

Salary TDS is computed by payroll and deposits through its own statutory challans alongside PF and ESI; its quarterly return is part of the same return pipeline below.

Monthly — deposit challans

The month's challans are drafted from the register — by the scheduled compliance job, or for a single deduction by Allocate to Next Challan on the reconciliation page — one per payment code and per major head. Company deductees and others deposit under different heads, so one code can correctly produce two challans. Drafting again is safe: late-posted bills top up the existing draft, and nothing is allocated twice.

After paying at the bank, enter the deposit date and the bank's CIN (BSR code and challan serial; the deposit date is the tender date) and select Deposit Challan. It computes both statutory interest legs — late deduction and late deposit — as of the deposit date, posts the deposit from your bank account and marks every covered deduction deposited. The quarterly return cannot validate a challan without its CIN.

Checking the CIN against the portal's Challan Status Inquiry file and recording bank or portal corrections have their own actions, Verify Against CSI and Correct Challan, but the shipped challan screen cannot pass them the file or the correction reference they need. The step-by-step procedure, the interest rules, every field and the manual alternatives are in TDS challans.

The challan record itself is not locked after deposit: anyone with edit permission can still change its amounts or status. Restrict edit access to deposited challans and audit any change; do not rely on the status alone as a technical lock.

Quarterly — the returns

The quarter's return headers (the vendor-TDS, TCS and salary forms) are drafted for you — by the scheduled compliance job or manually — and each moves through Draft → Computed → Validated → Filed. The step-by-step procedure, every field and the full pre-file checklist are in TDS returns.

  1. Compute assembles every deduction of the quarter and maps each to its depositing challan. Recompute freely until filing; it always rebuilds from the live register.
  2. Validate runs the pre-file checklist early, so problems surface on your side: missing or invalid PANs, department-rejected PANs (these block filing), deductions not yet deposited, incomplete CINs, challan over-use or short deposit, and missing certificate numbers on lower-deduction rows.
  3. Export renders the computed return as the caret-delimited e-return statement text that the government's return-preparation and validation utilities accept — the last step before uploading on the portal.
  4. Mark Filed records the portal acknowledgment and date; a late filing's fee is computed so the cost is on record. A filed return is locked — corrections go through Create Correction, which drafts a linked correction statement you compute, validate and file the same way.

PAN hygiene is part of the pipeline: run the department's bulk PAN verification and import the results — every party gets stamped Verified, Invalid or Name mismatch, and validation uses those stamps (rejected PANs block; never-verified ones warn).

After filing — certificates

On a filed return, Generate Certificates builds the certificate register: one numbered certificate per deductee — the non-salary TDS certificate for the vendor return, the TCS certificate for the collection return, and the salary certificate rows for the salary return — and stamps the certificate number back onto every underlying deduction, so the ledger, the certificate and the deductee's own statement all cite the same reference. Mark certificates Issued as you hand them over; issued certificates lock the register. xMatix keeps the register only, so the certificate documents themselves come from the government's TDS portal. See TDS certificates.

The scheduled front half

The Provision TDS/TCS compliance job runs the routine's front half unattended for every deductor company: it drafts the month's deposit challans and ensures the quarter's return headers exist. It is existence-checked and idempotent — your team reviews, pays and files.

Statutory rates, thresholds and due dates come from the provisioned catalog and the return logic, and change with the law — confirm current rules with your tax advisor.