Introducing AI-Powered 26AS TDS Reconciliation in Cointab

We’re excited to introduce 26AS TDS Reconciliation in Cointab.

Finance and tax teams can now reconcile the TDS recorded in their books of account with the TDS reported in Form 26AS.

Users only need to upload their TDS ledger or Books file along with the Form 26AS TXT file downloaded from the Income Tax Portal. Cointab uses AI to map party names with 26AS deductor names and applies multiple reconciliation mechanisms to match the underlying transactions.

The results are presented as:

• Fully matched
• Partially matched
• Unmatched
• Skipped

This helps teams identify TDS recorded in the books but not reported in Form 26AS, TDS appearing in Form 26AS but missing from the books, and differences in the amounts reported by deductors.

---

Why 26AS TDS reconciliation is important

Businesses record TDS receivable in their books when customers or other parties deduct tax from payments.

The deductor is also expected to report the deduction against the business’s TAN. Once reported, the TDS appears in Form 26AS.

Finance and tax teams therefore need to compare:

• TDS recorded in the Books or ledger
• TDS reported by deductors in Form 26AS

This reconciliation helps identify situations where:

• TDS has been recorded in the Books but is not appearing in Form 26AS
• TDS appears in Form 26AS but has not been recorded in the Books
• The TDS amount in the Books differs from the amount reported in Form 26AS
• TDS has been reported under an unexpected deductor name
• Multiple transactions need to be considered together
• Entries have been recorded or reported in different periods
• Further follow-up with the deductor may be required

Without a structured reconciliation process, teams often compare these records manually using Excel sheets, formulas, party-wise summaries, and repeated searches across both datasets.

---

Why 26AS reconciliation is difficult

There are two major challenges when reconciling TDS recorded in the Books with Form 26AS.

Party names may be different

The party name maintained in the accounting records may not exactly match the deductor name appearing in Form 26AS.

For example, a party may appear in the Books as:

ABC Technologies Pvt Ltd – Chennai

The same entity may appear in Form 26AS as:

ABC TECHNOLOGIES PRIVATE LIMITED

Differences may arise because of:

• Abbreviations such as Pvt Ltd and Private Limited
• Branch or location names
• Internal customer or property codes
• Legal entity suffixes
• Punctuation and spacing
• Spelling variations
• Additional descriptive text
• Differences between the business name and legal name

Traditional exact-name matching may treat these as different parties even though they refer to the same entity.

Form 26AS does not contain invoice numbers

Most reconciliations use a common identifier such as:

• Invoice number
• Document number
• Payment reference
• Transaction ID
• Receipt number
• Accounting reference

However, Form 26AS typically does not contain the invoice number against which the TDS was deducted.

The available information mainly includes details such as:

• Name of deductor
• Transaction or deduction date
• TDS amount
• Deductor identification information

This makes it difficult to directly establish a one-to-one relationship between every Book transaction and every 26AS transaction.

A single Book entry may correspond with multiple entries in Form 26AS. Similarly, several Book entries may collectively correspond with one or more deductions reported by the same deductor.

---

Upload the Books file and Form 26AS statement

To start the reconciliation, users can select 26AS TDS reconciliation from the list of ready-made reconciliations in Cointab.

Users then select or create:

• Tax account or entity name
• Financial year or reconciliation period

The reconciliation contains two sides:

Books or ledger

Users can upload the TDS ledger or Books file maintained in their accounting system.

Supported file formats include:

• CSV
• XLS
• XLSX

26AS statement

Users can download Form 26AS as a TXT file from the Income Tax Portal and upload it directly to Cointab.

Cointab formats the TXT file and prepares the relevant transaction and deductor details for reconciliation.

---

Configure the relevant Books fields

After uploading the Books file, users select the fields required for reconciliation.

These include:

• Party or ledger name
• Transaction date
• TDS amount

Users can preview the uploaded data and confirm that the correct columns have been selected.

Where required, users can also prepare the Books data by:

• Selecting the correct header row
• Filtering the records to be included
• Creating a derived column
• Adjusting the fields used for reconciliation

This allows Cointab to work with Books files generated from different accounting systems and ERP platforms.

---

Review the formatted 26AS statement

After the Form 26AS TXT file is uploaded, Cointab formats the statement and displays a preview.

Users can review details such as:

• Assessee name
• TAN
• Financial year
• Assessment year
• File creation date
• Deductor details
• TDS transactions

This allows the user to confirm that the correct Form 26AS file has been uploaded for the selected entity and financial year before proceeding.

---

AI matches Book parties with 26AS deductors

Cointab uses AI to map party names in the Books with deductor names appearing in Form 26AS.

The system analyses the available names and suggests the most likely corresponding deductor for each Book party.

This helps identify matches even when the names contain:

• Different legal suffixes
• Abbreviated words
• Branch or location references
• Internal codes
• Additional text
• Different punctuation
• Minor spelling differences
• Formatting variations

Each suggested mapping is assigned a confidence level.

---

Review mappings by confidence level

Cointab classifies party mappings into different confidence levels so users can focus their review on uncertain cases.

High confidence

High-confidence mappings represent parties where Cointab has identified a strong relationship between the Book party name and the 26AS deductor name.

These mappings are automatically suggested and can be quickly reviewed by the user.

Medium confidence

Medium-confidence mappings may require a closer review before the reconciliation is run.

The user can verify whether the suggested deductor represents the same entity as the party maintained in the Books.

Needs review

Where Cointab is unable to identify a sufficiently reliable deductor, the party is marked as Needs review.

The user can:

• Search for the correct deductor
• Select the appropriate deductor manually
• Change an incorrect suggestion
• Leave the party unmapped where no corresponding deductor exists

Users can filter the mapping screen to review:

• All mappings
• High-confidence mappings
• Medium-confidence mappings
• Mappings that need review

This allows Cointab to automate confident mappings while keeping users in control of uncertain cases.

---

Multiple mechanisms are used to reconcile transactions

After party mapping is completed, Cointab applies multiple reconciliation mechanisms to compare the TDS recorded in the Books with the TDS reported in Form 26AS.

Because invoice numbers are not available in Form 26AS, the reconciliation does not depend on a single common transaction identifier.

Cointab evaluates the available information across both datasets, including:

• Mapped party and deductor
• Transaction dates
• TDS amounts
• Individual transactions
• Groups of transactions
• One-to-one relationships
• One-to-many relationships
• Many-to-one relationships
• Aggregated amounts at the deductor level

This helps reconcile cases where the same TDS amount has been recorded differently across the Books and Form 26AS.

For example:

• One Book transaction may correspond with multiple 26AS transactions
• Multiple Book transactions may correspond with one 26AS amount
• Several transactions on both sides may collectively reconcile
• Transactions may have different dates but belong to the same deductor-level amount
• Part of the Book amount may be reported while the remaining amount is still open

Cointab groups the relevant transactions and presents both the total and the underlying line items for review.

---

Fully matched transactions

The Fully matched section contains Book and 26AS transactions where the corresponding TDS amounts have been reconciled.

For each matched group, users can review:

• Book transaction date
• Book party or deductor name
• Book TDS amount
• 26AS transaction date
• 26AS deductor name
• 26AS TDS amount
• Difference between both sides

Where multiple transactions form part of the match, Cointab displays them as a grouped result.

Users can expand the group to review all the transactions included from the Books and Form 26AS.

This helps retain complete transaction-level visibility even where the reconciliation requires one-to-many, many-to-one, or grouped matching.

---

Partially matched transactions

The Partially matched section contains transactions where a relationship has been identified between the Books and Form 26AS, but the total TDS amounts do not completely agree.

For example:

• TDS of ₹35,719 may be recorded in the Books
• TDS of ₹38,134 may be reported in Form 26AS
• The remaining difference of ₹2,415 requires investigation

A partial match may arise because:

• Only part of the TDS has been reported in Form 26AS
• The deductor has reported an additional amount
• Some Book transactions are missing from the 26AS statement
• Some 26AS transactions are missing from the Books
• Transactions have been reported in different periods
• An incorrect amount has been recorded or reported
• Further transaction grouping is required

Cointab displays the underlying Book and 26AS transactions together so that users can understand how the difference has been calculated.

Users can also use the manual match option where additional business context is available.

---

Unmatched transactions

The Unmatched section separately presents open transactions from the Books and Form 26AS.

Unmatched in Books or ledger

These are transactions recorded in the Books but not found in the Form 26AS statement.

Such transactions may indicate that:

• The deductor has not yet reported the TDS
• The deductor reported the TDS under a different period
• The party has been mapped incorrectly
• The TDS amount was recorded incorrectly
• The transaction requires follow-up with the deductor

Unmatched in the 26AS statement

These are transactions appearing in Form 26AS but not found in the Books or ledger.

Such transactions may indicate that:

• The accounting entry is missing
• The TDS was recorded under a different ledger
• The party or deductor mapping needs to be reviewed
• The transaction relates to a different accounting period
• The amount requires further investigation

Cointab displays the unmatched transactions from both sides next to each other, making it easier for users to investigate the open items.

---

Review the reconciliation summary

The reconciliation report provides a summary of the results across both sides.

Users can review:

• Total Books or ledger amount
• Total Form 26AS amount
• Difference between both sides
• Fully matched amount and transaction count
• Partially matched amount and transaction count
• Unmatched amount and transaction count
• Skipped transactions

The summary also displays the percentage of transactions classified under each result.

Users can select a result category and directly review the corresponding transaction details.

This provides a high-level view for reviewers while retaining complete drill-down visibility for finance and tax teams.

---

Manually review and close remaining transactions

Some transactions may require business knowledge that cannot be determined from the available data alone.

For example:

• A party changed its legal name
• One deductor represents multiple internal customer ledgers
• TDS was reported in a later quarter
• An accounting adjustment was posted separately
• Several deductions belong to a consolidated entry
• A transaction was recorded under an unexpected ledger

Users can review the open transactions and use Cointab’s manual matching functionality to close transactions after applying their judgement.

This ensures that automated reconciliation handles the clear cases while finance users retain control over exceptions.

---

Download the reconciliation report

After completing the review, users can download the detailed reconciliation report.

The report can be used for:

• Internal finance review
• Tax reconciliation working papers
• Follow-up with deductors
• Accounting adjustments
• Audit support
• Period-end closing
• Management reporting

Instead of maintaining separate Excel sheets for party mapping, transaction matching, grouped calculations, and unmatched items, users can manage the complete reconciliation through one structured workflow.

---

Benefits of 26AS TDS reconciliation in Cointab

Reduce manual party mapping

AI identifies likely relationships between Book party names and Form 26AS deductor names, even when the names are not written in the same format.

Reconcile without invoice numbers

Cointab applies multiple matching mechanisms using the information available in the Books and Form 26AS instead of depending on invoice numbers.

Handle grouped transactions

The system can evaluate one-to-one, one-to-many, many-to-one, and grouped transaction relationships.

Identify missing TDS credits

Transactions recorded in the Books but not found in Form 26AS are clearly presented for investigation and follow-up.

Find entries missing from the Books

TDS reported in Form 26AS but not recorded in the Books is separately displayed for review.

Focus users on uncertain mappings

Confidence-based party mapping allows users to concentrate on the cases that need human review instead of checking every party manually.

Review differences at the deductor level

Fully matched and partially matched transactions are grouped by the mapped party or deductor while retaining the underlying transaction details.

Create a repeatable process

The same reconciliation can be reused when an updated Books file or refreshed Form 26AS statement becomes available.

---

Complete 26AS reconciliation faster

Cointab helps finance and tax teams replace manual party-wise comparisons, Excel formulas, and repeated transaction searches with a structured reconciliation process.

Users can:

1. Upload the TDS ledger or Books file.
2. Upload the Form 26AS TXT file.
3. Select the relevant Book fields.
4. Review the formatted 26AS statement.
5. Review AI-generated party mappings.
6. Run the reconciliation.
7. Investigate fully matched, partially matched, and unmatched transactions.
8. Download the reconciliation report.

The 26AS TDS Reconciliation feature is now live in Cointab.

Start free:

https://www.cointab.net/