Home 26AS TDS Reconciliation Why is a transaction partially matched or unmatched and how do I fix it?

Why is a transaction partially matched or unmatched and how do I fix it?

Last updated on Sep 08, 2026

Short Answer: Partial/unmatched items occur when amounts, identifiers, or party names differ; check column mappings, party mappings and the 'Match basis' e.g., Reference ID + Amount, fix source data and re-run reconciliation.

Answer

PreRequisites

  1. Have run reconciliation and can access Partially matched / Unmatched tabs.

  2. Access to source Books and 26AS files for corrections.

Steps

  1. Open the 'Partially matched' or 'Unmatched' tab to locate affected transactions.
    List of problem transactions appears for review.

  2. Click the transaction row and review 'Matched transaction details' to see 'Match basis' and the 'Difference'.
    You can identify which field caused the mismatch identifier, amount, or party.

  3. If amounts differ, verify and correct the 'TDS amount' mapping in 'Configure file - Books' or correct the source file.
    Amount values align after correction.

  4. If parties do not match, open 'Party mapping' and correct the '26AS deductor' selection for the Books party.
    Party mapping updated; re-run reconciliation.

  5. Re-run the reconciliation to confirm the fixes moved transactions to Fully matched.
    Previously partial/unmatched rows move to Fully matched if resolved.

Troubleshooting

  1. Small decimal differences appear, e.g., -0.03.
    LikelyCause: Rounding or precision differences between source files.
    Action: Check source files for rounding; adjust precision in Books or correct values in source files; re-run reconciliation.

  2. Reference ID missing for a row.
    LikelyCause: Identifier column not present or not mapped.
    Action: Map the identifier column in 'Configure file - Books' if available, or use party mapping to match by party and amount.