Section 143(1) Income Tax Intimation: Meaning, Reasons, Response & 2026-27 Update
Quick Summary
- Section 143(1) intimation is an automated notice from the Income Tax Department's Centralised Processing Centre (CPC) issued after your ITR is processed. It is a routine processing communication, not a scrutiny notice.
- It applies to all categories of taxpayers, including individuals, Hindu Undivided Families (HUFs), partnership firms, Limited Liability Partnerships (LLPs), and companies that file income tax returns for years governed by the old law.
- The 2025 change widened the scope of summary processing so that certain inconsistencies based on information available with the department, including relevant prior return information, may also be considered during processing. This does not convert 143(1) into full scrutiny.
- Three possible outcomes are a tax demand, a refund, or no adjustment.
- If you receive a tax demand, you should respond promptly - either agree and pay, or disagree through the e-filing portal with the correct reason and supporting details.
- Ignoring a valid demand can lead to continuing outstanding tax demand, refund adjustment, and interest consequences where applicable.
- When paying a 143(1) demand, use Challan 280 with challan type 400 (Tax on Regular Assessment), not the Advance Tax code 100.
- If no intimation is issued within the statutory time limit, the return is generally treated as processed without adjustment in practical terms, though taxpayers should still verify status on the portal.
- Common mismatch triggers include TDS claimed that does not match Form 26AS or AIS-related information, unreported FD interest or dividend income, and deduction claims exceeding the limits under sections such as 80C or 80D.
- BUSY Accounting Software helps improve reconciliation discipline before ITR filing, thereby reducing avoidable mismatches during CPC processing.
What Is Section 143(1) of the Income-tax Act?
A Section 143(1) intimation is an automated communication issued by the Income Tax Department's Centralised Processing Centre (CPC) after it processes your income tax return (ITR). It is not a scrutiny notice . It is a system-generated comparison of what you declared in your ITR against what the department's records and system checks show.
The intimation contains three broad comparisons:
Column A: Income and tax figures as reported by you in your ITR
Column B: Income and tax figures as computed by CPC
Column C: The difference - resulting in a demand, refund, or no adjustment
The process is automated. CPC runs mathematical checks, cross-checks your data against available records such as Form 26AS, AIS, and TIS, and issues the intimation accordingly.
Important 2026-27 note: For tax years beginning before 1 April 2026, return processing continues under the earlier legal framework in practical terms, and Section 143(1) remains the relevant reference for those years. From 1 April 2026 onward, the new Income-tax Act, 2025 applies, and the comparable return-processing provision is Section 270(1). So readers should understand Section 143(1) mainly in the context of earlier years and pending matters under the old law.
Book A Demo
2026-27 Transition Update: Section 143(1) and the New Income-tax Act, 2025
This is the most important update from a 2026-27 perspective.
From 1 April 2026, the Income-tax Act, 2025, has officially come into force. However, the legal framework follows a dual-track approach during this transition. While the new Act governs all income earned from this date forward, returns and proceedings for earlier years continue to be administered under the Income-tax Act, 1961.
Consequently, Section 143(1) remains vital for taxpayers in 2026-27, particularly when addressing old intimations, responding to outstanding demands, or filing rectifications for prior assessment years.
- For earlier years and pending returns (under the 1961 Act): Section 143(1) remains the governing provision for processing and prima facie adjustments.
- For tax years beginning on or after 1 April 2026 (under the 2025 Act): Taxpayers must now refer to Section 270(1), which replaces the old processing mechanism for all new filings.
What Changed in 2025 for Section 143(1)?
This remains the most significant recent development in Section 143(1) for returns governed by the old law.
The 2025 change widened the scope of processing adjustment. Earlier, CPC could flag issues within your current ITR, such as arithmetic errors, internal inconsistencies, incorrect claims apparent from the return, or mismatches against tax credit and reported information for that year.
After the 2025 change, CPC can also consider certain inconsistencies apparent from information available with the department, including relevant prior return information, where such an adjustment still falls within the limited scope of summary processing.
Note: It does not indicate that CPC has unlimited power to do a full year-on-year investigation under Section 143(1). It remains a summary-processing mechanism, not a detailed scrutiny assessment.
What This Means in Practice
In practical terms, this may affect cases such as:
- a taxpayer who claimed a deduction, exemption, or carry forward figure in one year but reports inconsistent related figures in the next year
- a self-employed professional whose return disclosures materially change year on year without corresponding consistency in linked data
- a taxpayer who claimed housing loan related deductions in earlier years but reports related return data inconsistently in the current year
- changes in loss, deduction, or credit claims that do not align with prior return disclosures
- brought forward losses, depreciation, or tax credit figures that do not match the continuity expected from earlier filings
Who Receives a Section 143(1) Intimation?
Section 143(1) applies to all categories of taxpayers who file income tax returns for relevant years under the old law:
| Taxpayer Category | ITR Form | 143(1) Applicable? |
|---|---|---|
| Individual (salaried/other income) | ITR-1, ITR-2 | Yes |
| Individual (business/profession) | ITR-3, ITR-4 | Yes |
| Hindu Undivided Family (HUF) | ITR-2, ITR-3 | Yes |
| Partnership Firm | ITR-5 | Yes |
| LLP | ITR-5 | Yes |
| Company | ITR-6 | Yes |
| Trust / AOP / BOI | ITR-7 | Yes |
The intimation is delivered to the taxpayer's registered email address and is also available on the e-filing portal. An SMS may also be sent to the registered mobile number as an alert.
The PDF is usually password protected. For individuals, the password is your PAN in lowercase plus date of birth in DDMMYYYY format. For non-individuals, it is generally PAN in lowercase plus date of incorporation in DDMMYYYY format.
Example: PAN ABCDE1234F, DOB 15 August 1990 -> password is abcde1234f15081990
Filed vs Computed - Understanding Your Intimation
The intimation compares your filed return with the CPC computation across several line items:
| Comparison Item | What It Checks |
|---|---|
| Total income | Your declared income vs CPC recomputed income |
| Deductions (80C, 80D, 80G, etc.) | Claimed amount vs amount allowed as per law and records |
| Exempt income | Items you excluded vs items CPC treats differently |
| Loss set-off | Losses claimed vs eligibility based on return data |
| Gross tax liability | Tax computed on the income considered by CPC |
| TDS / TCS credit | TDS you claimed vs TDS reflected in available records |
| Advance tax / self-assessment tax | Payments you declared vs challan records |
| Interest | System-computed interest, where applicable |
| Late fee | Applicable fee, where relevant |
| Net tax payable or refundable | The final bottom-line difference |
Why You Receive Section 143(1) Intimations
A 143(1) intimation serves three purposes:
- confirms that your ITR has been processed by CPC
- communicates any arithmetic discrepancy, incorrect claim, or mismatch found during automated processing
- states whether a refund is due, additional tax is payable, or no change is needed
Receiving an intimation is not, by itself, a sign of wrongdoing or scrutiny. It is a standard part of return processing.
Common Reasons for 143(1) Mismatches
1. TDS / TCS Discrepancies
This is one of the most common triggers. The TDS you claimed in your ITR does not match the TDS reflected in Form 26AS or related records. This usually happens when:
- your employer or deductor quoted an incorrect PAN
- the deductor filed the TDS return late, so the credit is not yet reflected
- you changed jobs and TDS from multiple employers was not fully captured
- credit was claimed in the wrong assessment year
2. Undisclosed Income in AIS
AIS captures financial information reported by third parties such as banks, mutual funds, brokers, registrars, and other reporting entities. If your bank reported FD interest or your broker reported dividend or capital gains related information, and you did not include the taxable portion correctly in your ITR, CPC may recompute your income upward.
At the same time, taxpayers should not assume AIS is always perfectly accurate. AIS can sometimes contain duplicate entries, incomplete reporting, or entries that need clarification. So before accepting a mismatch, you should verify AIS against your actual records.
3. Deduction Claims Exceeding Limits
Claims under Section 80C, 80D, 80G , or similar provisions that exceed the permissible limit, are claimed under the wrong section, or do not match the taxpayer's eligibility can trigger a disallowance and recomputation.
4. Data Entry Errors
Manual filing mistakes - incorrect income figures, wrong challan details, wrong tax regime selection, incorrect residential status, typing errors, or transposition mistakes in tax payment entries - are often caught during automated processing.
5. Incorrect Tax Rate Application
Applying the wrong rate to special category income, using the wrong slab or rebate logic, or selecting the wrong residential status can lead to CPC computing tax differently from what was filed.
6. Late Filing Fees and Interest
If filing or payment defaults apply, CPC may automatically compute:
- applicable interest
- late filing fee
- net tax payable after considering delay and payment timing
AIS, TIS, and Form 26AS - The Three Documents CPC Uses
Taxpayers who receive a 143(1) mismatch are often confused by these three documents. Here is what each one contains and how it matters:
| Document | Full Name | What It Contains | When CPC Uses It |
|---|---|---|---|
| Form 26AS | Tax Credit Statement | TDS/TCS and certain tax payment entries linked to your PAN | To verify tax credit claims in your ITR |
| AIS | Annual Information Statement | Broader financial information reported by third parties, such as interest, dividends, securities transactions, and other reportable transactions | To verify income and information consistency |
| TIS | Taxpayer Information Summary | A simplified summary derived from AIS data | Used as a quick summary reference while comparing broad figures |
Which document to check for which mismatch:
- TDS discrepancy -> check Form 26AS -> verify deductor-wise credit entry
- Income gap such as interest, dividend, or other reported income -> check AIS -> identify unreported or mismatched entries
- General summary-level mismatch -> check TIS -> compare the consolidated figure used for filing review
All three should be reviewed before responding to a demand.
Worked Example - What a 143(1) Demand Looks Like
Scenario: Priya, a salaried individual in Mumbai, filed her ITR for AY 2025-26. She declared salary income , claimed deductions, and reported TDS credit based on the records she had available at the time of filing.
What CPC found:
- Priya's TDS broadly matched the available tax credit records.
- Priya's AIS showed additional FD interest from another bank account.
- Priya had reported one interest entry but missed the second one.
- Because that income was not included in the return, CPC recomputed her taxable income and tax liability.
Result:
Priya received a 143(1) intimation showing a tax demand.
She checked her AIS, identified the missed FD interest, and confirmed that the demand arose because that income had not been reported in her ITR. She then paid the demand using Challan 280 with Code 400.
This is a common real-world example of how a 143(1) demand arises: the return may appear correct to the taxpayer, but AIS may contain additional reportable income that was overlooked.
Possible Outcomes After Processing
Outcome 1: Refund
CPC's computation shows that you paid more tax than required - through excess TDS , advance tax, or self-assessment tax. The excess is issued as a refund, typically credited to your pre-validated bank account.
You usually do not need to take any action unless there is a bank account validation issue or refund failure.
Outcome 2: Tax Demand (Additional Tax Payable)
CPC's computation shows that more tax is payable than what you paid. In that case, you should review the intimation carefully and then either:
- agree with the demand and pay it
- disagree with the demand fully or partly through the portal
- file a rectification where the issue is due to an apparent mistake in processing
- revise the return, where legally permitted and where the mistake is in the original return itself rather than CPC processing
A valid demand should not be ignored. Unresolved demand can lead to continuing tax liability, future refund adjustment, and other follow-up consequences.
Outcome 3: No Demand, No Refund
CPC's computation matches your filed return, or no adjustment is required. The intimation simply confirms that your ITR has been processed without any payable or refundable difference.
The Time Limit Point - What If You Receive No Intimation?
The statutory time limit for issuing an intimation under Section 143(1) is 9 months from the end of the financial year (FY) in which you filed your return.
Example: If you filed your return in July 2025, that filing falls in FY 2025-26. The end of that financial year is 31 March 2026. Nine months from that date ends on 31 December 2026.
The Outcome: If no intimation is issued within this statutory time limit, your return is legally "deemed" to have been accepted as filed. In this case, the acknowledgement (ITR-V) you received upon filing serves as the final processing confirmation. However, taxpayers should always manually verify the 'Processed' status on the e-filing portal to ensure no notices were missed.
How to Respond to a Section 143(1) Intimation
Step 1: Review the intimation and identify whether the outcome is a demand, refund, or no adjustment.
Step 2: If there is a demand, compare the CPC computation with your ITR, Form 26AS, AIS, TIS, Form 16 or Form 16A , and challan records to determine whether the demand is correct, partly correct, or incorrect.
Step 3: Log in to the income tax e-filing portal and go to the section for responding to outstanding demand.
Step 4: Select the relevant assessment year and the 143(1) demand.
Step 5: Indicate your response:
Agree -> Pay the demand
Disagree fully -> Provide the reason and correct supporting details
Disagree partly -> Pay the agreed portion and contest the balance with the correct explanation
Step 6: If filing rectification for an apparent error:
- go to the rectification section on the portal
- choose the correct rectification request type
- submit the correction or the basis for reprocessing, as applicable
Important practical distinction
- If the issue is due to an error in your original return and the revision window is still open, a revised return may be the more appropriate route.
- If the issue is due to CPC's apparent processing error, rectification is usually the more appropriate remedy.
Time sensitivity
Where a proposed adjustment under Section 143(1)(a) is issued, the objection window is generally 30 days from the issue of the intimation. So, delay can reduce your procedural options.
How to Pay a 143(1) Tax Demand (Challan 280, Code 400)
When you agree with the 143(1) demand and want to pay it, using the correct challan and challan type is important. Using the wrong payment code can create reconciliation issues.
Correct Payment Route
| Step | Action |
|---|---|
| 1 | Go to the income tax portal and open e-Pay Tax |
| 2 | Select Challan 280 |
| 3 | Under "Type of Payment", select (400) Tax on Regular Assessment |
| 4 | Enter assessment year, PAN, and the demand amount |
| 5 | Complete payment through the available banking mode |
| 6 | Download the challan receipt and note the BSR Code, Challan Serial Number, and date |
| 7 | Return to the portal and update the payment reference in the relevant demand response flow, where required |
Why Code 400 and not Code 300?
Code 300 is generally used for self-assessment tax before or at the time of filing. Code 400 is used for a tax demand raised after processing or assessment. Using Code 400 helps ensure that the payment is mapped correctly against the outstanding demand.
Consequences of Ignoring a 143(1) Demand
Ignoring a valid 143(1) demand is one of the most common and avoidable mistakes taxpayers make. The consequences can escalate over time:
| Stage | What Happens |
|---|---|
| After demand remains unpaid | The amount continues as outstanding demand |
| Delay continues | Interest consequences may apply where legally applicable |
| Future refund arises | The demand may be adjusted against the refund |
| Continued non-resolution | Further follow-up or recovery action may follow in appropriate cases |
Practical point: even a small demand should be reviewed and addressed promptly. A minor unresolved mismatch can become a larger compliance issue later.
How to Download Your 143(1) Intimation from the Portal
If you did not receive the intimation by email, or cannot find it, follow these steps:
Step 1: Log in to the income tax portal using your PAN and password.
Step 2: Go to e-File -> Income Tax Returns -> View Filed Returns
Step 3: Select the relevant Assessment Year.
Step 4: Click View Details
Step 5: Under the processing status section, download the intimation order, if available.
Step 6: Open the downloaded PDF using the password:
Individuals: PAN in lowercase + date of birth in DDMMYYYY format
Example: PAN ABCDE1234F, DOB 15/08/1990 -> abcde1234f15081990
Non-individuals: PAN in lowercase + date of incorporation in DDMMYYYY format
If the option is not available, check your registered email inbox and spam folder. If the time limit has already passed, review the filing acknowledgement and consult your CA if confirmation is required.
Section 143(1) vs Section 143(2): Key Differences
When taxpayers receive a notice referencing "Section 143" but are unsure which sub-section applies, confusion is understandable. The difference is significant - 143(1) is routine processing, while 143(2) is a formal scrutiny selection.
| Feature | Section 143(1) Intimation | Section 143(2) Scrutiny Notice |
|---|---|---|
| Nature | Automated preliminary processing communication | Scrutiny notice requiring detailed review |
| Issued by | Centralized Processing Centre (CPC) | Jurisdictional Assessing Officer |
| Scope | Arithmetic errors, mismatch checks, incorrect claims apparent from records | Detailed examination of return, transactions, claims, and supporting documents |
| Time limit | Within the prescribed processing time limit | Separate statutory scrutiny notice timeline applies |
| Process | System-generated, generally without personal hearing at this stage | May require documents, written submissions, and hearings |
| Response | Usually limited unless a demand or adjustment is involved | Mandatory and more serious |
| Seriousness | Routine | More serious and detailed |
| Typical triggers | TDS mismatch, missed interest income, deduction mismatch | Case selected for scrutiny based on risk parameters or other reasons |
Bottom line: if you received a 143(1) intimation, it is a routine processing communication. If you receive a 143(2) notice, it is a scrutiny matter and should be handled carefully.
How BUSY Accounting Software Reduces 143(1) Mismatches
The most effective way to deal with a 143(1) intimation is to reduce the chance of mismatch before filing the return. Most 143(1) demands arise from discrepancies that are detectable and correctable earlier if records are properly maintained and reconciled.
| Common 143(1) Trigger | How Better Accounting Controls Help |
|---|---|
| TDS claimed not matching records | Reconciliation of TDS entries with available tax credit records reduces mismatch risk |
| Unreported income | Better bookkeeping and review processes help identify missing income entries before filing |
| Incorrect PAN or party-level tax data | Proper master data control reduces avoidable errors |
| Bank account mismatch for refund | Updated taxpayer and payment records reduce post-filing issues |
| Arithmetic and reporting errors | Structured accounting and tax computation workflows reduce manual mistakes |
| Multi-entity or multi-source tax tracking | Clear entity-wise and record-wise tracking reduces cross-claim confusion |
For businesses filing ITR-3, ITR-5, or ITR-6 with multiple income sources and multiple deductors, manual reconciliation significantly increases the chance of mismatch. Better accounting controls and pre-filing reconciliation can materially reduce avoidable 143(1) adjustments.
BUSY Accounting Software helps improve reconciliation discipline before ITR filing, thereby reducing avoidable mismatches during CPC processing
Where BUSY helps in practice
- cleaner ledger-wise income tracking so interest, commission, and other receipts are less likely to be missed
- stronger reconciliation discipline before return preparation
- better party-level and tax data control, reducing manual mismatches
- easier review of tax payments, books, and supporting schedules before filing
- better continuity of figures across years, especially for business taxpayers
BUSY does not eliminate the possibility of a mismatch in every case, but it can materially reduce avoidable 143(1) issues arising from weak bookkeeping, incomplete reconciliations, and poor data hygiene.
Explore All BUSY Calculators for Easy GST Compliance
Conclusion
Receiving a Section 143(1) intimation is a normal part of the ITR filing process, not a cause for panic. CPC processes returns and issues intimations to confirm processing and communicate any discrepancy it identifies. Many interventions result in no demand or in manageable adjustments.
BUSY helps improve accounting and reconciliation discipline before filing, which can help reduce the risk of 143(1) mismatches.
