Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
You have known Form 26AS as the single annual tax credit statement for a decade — TDS, TCS, advance tax, refunds, and high-value transactions all in one document keyed to your PAN. Now your ERP release notes and your CA are talking about Form 168, and it is not obvious what is the same, what has changed, and whether the process you built around Form 26AS still works. The confusion is not in your head — the transition genuinely runs two statements side by side for at least three financial years, and the scope of the two statements is not identical.
Form 26AS is the annual tax credit statement under Section 285BB of the Income Tax Act 1961 read with Rule 114-I. Form 168 is the annual TDS and TCS statement under Section 393 of the Income Tax Act 2025, effective 1 April 2026 for Tax Year 2025-26 onwards. Three things change at the switchover — the scope narrows (high-value transactions move out to AIS), the labelling changes (payment code 1001-1092 in place of section code 194x, Tax Year in place of Assessment Year), and the portal splits (Form 26AS stays on TRACES for old-era corrections, Form 168 lives on the e-filing portal). Everything else — the PAN-level keying, the quarterly update cadence, the reconciliation workflow against the TDS receivable ledger — carries forward substantially unchanged.
A dual-mode reconciliation posture from April 2026 through March 2029. An equivalency table between old section codes and new payment codes for the receivable ledger. Era flag on every TDS receivable entry (FY 2025-26 or earlier vs FY 2026-27 onwards). Separate pulls of Form 26AS (from TRACES for pre-cutover entries and late corrections) and Form 168 (from the e-filing portal for new-era entries), reconciled to the same PAN-level receivable ledger with double-count prevention via the era flag.
A PAN-level TDS receivable ledger reconciled to the correct statement for each era, no double-counting between Form 26AS and Form 168 pulls, a clean AIS check that runs separately for high-value transaction disclosure in the ITR, and a working paper trail that lets a statutory auditor see which statement supports each material TDS receivable balance across the three-year cross-era window.
You searched for the difference between Form 26AS and Form 168. Perhaps a note in your ITR portal mentioned Form 168 in passing. Perhaps your ERP release notes flagged a switch. Perhaps your CA sent a one-liner about the April 2026 cutover and you realised you did not know what was actually changing.
The confusion is normal. Both statements exist. Both are keyed to your PAN. Both aggregate TDS credits from every deductor who paid you. Yet from 1 April 2026, they are not the same statement — the scope narrows, the labelling changes, and the portal splits. This guide walks through what actually differs, in plain terms, before you touch a reconciliation run.
The quick answer
Form 168 is Form 26AS renamed, re-scoped, and moved under the Income Tax Act 2025. The renaming is straightforward — Tax Credit Statement becomes Annual TDS-TCS Statement. The re-scoping is the substantive change — high-value transactions like large cash deposits, property purchases above Rs 30 lakh, and mutual-fund investments above Rs 10 lakh in a financial year move out of the combined view and into a separate Annual Information Statement (AIS). The move is administrative — Form 26AS was downloaded from TRACES; Form 168 is downloaded from the Income Tax e-filing portal at incometax.gov.in. Both statements coexist through March 2029 because the six-year correction window on FY 2025-26 returns keeps legacy Form 26AS operationally live until then.
Everything else — the PAN keying, the 3-to-7-working-day update lag after challan processing, the 7-to-10-working-day lag after quarterly return processing, the correction-return escalation path if a credit is missing — carries forward substantially unchanged.
The five specific differences that matter to a finance team
Not every difference matters equally. A small mid-market finance team preparing its first Q1 FY 2026-27 reconciliation in July 2026 needs to internalise these five before the rest.
Difference 1 — Legal basis and effective date
Form 26AS is issued under Section 285BB of the Income Tax Act 1961 read with Rule 114-I of the Income-tax Rules 1962. Form 168 is issued under Section 393 of the Income Tax Act 2025 (Chapter XX). The pivot is 1 April 2026 — every deduction made from that date is reported into Form 168; every deduction on or before 31 March 2026 remains in Form 26AS.
The date that matters is the date of deduction, not the date the certificate is downloaded. A March 2026 invoice with TDS under Section 194J stays in the Form 26AS view even when the Form 16A certificate arrives in June 2026. Only the April 2026 onwards deductions flow to Form 168.
Difference 2 — Scope: TDS and TCS only, versus TDS-TCS-plus-high-value-transactions
This is the substantive change. Form 26AS in its late-life form (from FY 2020-21 onwards) had absorbed the Statement of Financial Transactions data reported by banks, sub-registrars, mutual funds, and companies under Section 285BA — so a single Form 26AS view showed TDS, TCS, advance tax, self-assessment tax, refunds, and also the deductee’s high-value transactions like a Rs 12 lakh mutual-fund purchase or a Rs 65 lakh property registration.
Form 168 unbundles this. Under Section 393, Form 168 covers only TDS and TCS credits — leaner, single-purpose, and easier to reconcile against the TDS receivable ledger. The high-value transaction data moves to the Annual Information Statement (AIS) and its taxpayer-facing summary (the Taxpayer Information Summary, or TIS). For an SME controller preparing the ITR, this splits one download into two workflows — TDS reconciliation against Form 168, and ITR disclosure completeness against AIS.
If your process was pulling Form 26AS once and cross-checking both TDS credits and undisclosed high-value income in a single pass, you need two passes now.
Difference 3 — Payment code in place of section code
Every entry in Form 26AS today carries a section code — 194C for contractor payments, 194J for professional fees, 194I for rent, 194Q for purchase of goods, 194O for e-commerce operator payments, and so on. Every entry in Form 168 carries a numeric payment code drawn from the 1001-to-1092 range under Sections 392 to 394 of the Income Tax Act 2025.
For a receivable ledger, the equivalency matters. Section 194J maps to payment code 1027 under Section 393(1) Sl. 6(iii).D(b). Section 194Q at 0.1 per cent maps to payment code 1031. Section 194O at 1 per cent maps to payment code 1011. Section 194C splits across payment codes 1001 and 1002 depending on the deductee type. This is the equivalency table your reconciliation configuration needs before the first cross-era run — and it is documented in depth in the cross-era TDS reconciliation guide and captured for desk-side reference in the Form 141/168/131/26 Reference Card.
Difference 4 — Tax Year in place of Assessment Year
Form 26AS labels the period as an Assessment Year (AY 2026-27, AY 2025-26). Form 168 labels the period as a Tax Year (Tax Year 2025-26, Tax Year 2026-27). Tax Year 2025-26 corresponds to what was previously called Assessment Year 2026-27.
The one-year offset is the source of a specific reconciliation trap — a controller who filters an ERP report by AY 2026-27 and then filters a Form 168 pull by Tax Year 2026-27 is looking at two different periods. The convention change is small on paper and material in a reconciliation queue. Every reconciliation system built for Form 26AS needs an AY-to-TY mapping rule before it can ingest Form 168 records.
Difference 5 — Portal split: TRACES for legacy, e-filing for new
Form 26AS is downloaded from the TRACES portal at tdscpc.gov.in. Form 168 is downloaded from the Income Tax e-filing portal at incometax.gov.in. Correction statements for FY 2025-26 and earlier returns continue to be filed on TRACES; correction statements for FY 2026-27 onwards are filed through the updated e-filing portal workflow.
Between April 2026 and March 2029, a finance team runs a two-portal workflow — TRACES for legacy Form 26AS pulls and old-era corrections, e-filing portal for Form 168 pulls, Form 131 certificate downloads, and new-era corrections. The workflow itself is not complicated once the split is understood, but a team that assumes everything moved to the e-filing portal will spend a fortnight looking for a Q2 FY 2025-26 correction path that does not exist there.
The one to escalate first — the cross-era correction window
Of these five differences, the one that carries the highest financial risk is the cross-era window itself. FY 2025-26 corrections can be filed until 31 March 2029 under the six-year limitation of Section 200 of the Income Tax Act 1961. That is a three-year overlap window during which a PAN mismatch, an amount error, or a wrong section code in an FY 2025-26 return can still be fixed on TRACES — after which the correction is permanently barred.
An illustrative Rs 2,00,000 professional fee invoice from March 2026 with a Rs 20,000 TDS at Section 194J that got booked against the wrong PAN in the deductor’s Q4 FY 2025-26 return is a live problem for the deductee’s ITR until 31 March 2029. The correction path is TRACES, not the e-filing portal. The reference statement is Form 26AS, not Form 168. If your team assumes everything is Form 168 territory after April 2026, this Rs 20,000 credit stays lost.
The same time-bar logic applies with even more urgency to earlier years. FY 2018-19 through FY 2022-23 correction windows closed on 31 March 2026 under the same Section 200 limitation — a five-year block of TDS data that became permanently uncorrectable at the same moment the switchover happened. That deadline is treated in depth in the TDS correction statement March 2026 deadline guide.
When manual dual-portal checking outgrows itself
A finance manager at a Rs 200 crore SME with 30-40 vendors deducting TDS each quarter can run the two-portal workflow manually for a year or two. Pull Form 26AS from TRACES, pull Form 168 from the e-filing portal, load both into an Excel workbook keyed by PAN and quarter, mark each receivable as old-era or new-era, and reconcile against the TDS receivable ledger. The volume is manageable; the discipline is what matters.
At a Rs 800 crore manufacturer with 200-plus deductor relationships, the same two-portal workflow becomes a full-time role for one analyst across the closing week of every quarter. The equivalency table between old section codes and new payment codes has to be maintained, the AY-to-TY mapping has to be applied on every pull, the era flag has to be set correctly on every receivable entry, and the AIS pull has to run as a separate workflow for ITR-completeness cross-check. This is the volume threshold at which structured TDS reconciliation software that ingests both statements natively, applies the equivalency table automatically, and flags era-boundary mismatches for review starts to pay back the licence cost in analyst hours saved.
The wider design of the two-statement, two-portal reconciliation workflow — how it sits inside the monthly close cadence, how it hands off from the bank window to the TDS window, how the auditor working paper trail is maintained across the cross-era window — is treated as a sequence in the reconciliation playbook for monthly close.
Go deeper
For the underlying technical treatment of each statement and the transition mechanics:
- Form 168 — the new TDS statement in detail — full schema, payment code structure, e-filing portal workflow, and the specific reconciliation configuration change for Tax Year 2025-26.
- Cross-era TDS reconciliation — old section codes to new payment codes — the failure modes that emerge during the three-year overlap window and the equivalency table between Sections 194C, 194J, 194I, 194Q, 194O and payment codes 1001-1092.
- Form 26AS — what it is and how it works — the legacy statement in detail, including Parts A through F and why Form 26AS remains operationally live through March 2029.
- Form 131 — the quarterly deductor certificate replacing Form 16A — the certificate that pairs with Form 168, its 15-day issuance window, and the Rs 100-per-day late-issuance penalty.
- Form 141 — the unified challan-cum-statement replacing 26QB, 26QC, 26QD, and 26QE — the parallel simplification on the individual-and-HUF specified-payment side, covering property, rent, contractor, and virtual digital asset TDS.
- Form 141/168/131/26 Reference Card — the one-page desk reference for the four new-era forms, their legacy predecessors, and the effective dates.
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Section 285BB, Income-tax Act 1961 read with Rule 114-I of the Income-tax Rules 1962 — The Principal Director General of Income-tax (Systems) or the Director General of Income-tax (Systems) shall upload in the registered account of the assessee an annual information statement in Form 26AS containing information relating to tax deducted or collected at source, specified financial transactions, payment of taxes, demand and refund, pending proceedings, and completed proceedings. This is the statutory anchor for Form 26AS as it operates for FY 2025-26 and earlier assessment years, and continues to be the correction-filing basis until the six-year correction window under Section 200 closes on 31 March 2029 for FY 2025-26 entries.
- ▸ Section 393, Income-tax Act 2025 (Chapter XX) — The Income-tax Act 2025 introduces a unified annual TDS and TCS statement under Section 393 in the form and manner prescribed, effective from 1 April 2026 for Tax Year 2025-26 and onwards. The new statement, notified as Form 168, carries every entry with a four-digit payment code drawn from the Section 392 to 394 schedule (1001 to 1092 range) in place of the legacy section code (194C, 194J, 194I and so on) that appeared in Form 26AS.
- ▸ Section 285BA, Income-tax Act 1961 — Statement of Financial Transactions — Reporting entities including banks, mutual funds, sub-registrars, and companies issuing shares must file an annual Statement of Financial Transactions covering high-value transactions such as cash deposits or withdrawals above the specified thresholds, immovable property transactions above Rs 30 lakh, credit-card payments above the specified threshold, and mutual-fund or bond investments above Rs 10 lakh in a financial year. This SFT feed is what populates the high-value transactions block that appeared in the composite Form 26AS view and, from Tax Year 2025-26 onwards, is presented separately in the Annual Information Statement rather than in Form 168.
- ▸ Section 200, Income-tax Act 1961 — Correction Window for TDS Returns — A deductor may file a correction statement to rectify a TDS return within six years from the end of the financial year in which the original return was filed. This limitation is what fixes the last date for correcting FY 2025-26 TDS returns as 31 March 2029, and it is why Form 26AS in its legacy form (with old section codes) must remain accessible on the TRACES portal alongside Form 168 for at least three financial years after the 1 April 2026 switchover — cross-era matching is a compliance requirement, not a convenience.
- ▸ Section 139AA, Income-tax Act 1961 — PAN as Universal Identifier — The Permanent Account Number remains the universal identifier for every tax credit statement in the Indian tax system. Both Form 26AS and Form 168 are keyed to PAN, and every entry — TDS, TCS, advance tax, self-assessment tax, refund — must reference the deductee PAN correctly for the credit to be claimable in the income tax return. A PAN mismatch in a Q4 FY 2025-26 return that surfaces after 1 April 2026 still corrects to Form 26AS (old era), not Form 168, because the underlying deduction was made under the 1961 Act.