CBDT Sets New Tax-Data Verification Channel for Petroleum Ministry Under Income-tax Act, 2025
CBDT has designated DGIT (Systems), Delhi to provide specified Yes/No/Not Available tax-status flags to the Ministry of Petroleum & Natural Gas under section 258(1) of the Income-tax Act, 2025.

What changed
CBDT superseded an earlier Income-tax Act, 1961 information-sharing order and designated DGIT (Systems), Delhi as the specified authority for a structured data-verification arrangement with the Petroleum Ministry.
Why it matters
The order operationalises controlled inter-departmental verification under the new Income-tax Act, 2025 and is important for understanding how tax data may be shared for government programme administration without sending full return data.
Who is affected
Taxpayers whose PAN/Aadhaar data is queried by the Petroleum Ministry, CBDT systems teams, subsidy/program administrators and privacy/compliance functions.
Action required
Affected programme administrators should use only the authorised query fields and MoU process. Taxpayers should ensure PAN-Aadhaar linkage and return records are correct but should not interpret the order as a general public disclosure of tax-return data.
# CBDT Sets New Tax-Data Verification Channel for Petroleum Ministry Under Income-tax Act, 2025
Finin2min 2-minute summary
CBDT has designated DGIT (Systems), Delhi to provide specified Yes/No/Not Available tax-status flags to the Ministry of Petroleum & Natural Gas under section 258(1) of the Income-tax Act, 2025.
What changed
CBDT superseded an earlier Income-tax Act, 1961 information-sharing order and designated DGIT (Systems), Delhi as the specified authority for a structured data-verification arrangement with the Petroleum Ministry.
Why it matters
The order operationalises controlled inter-departmental verification under the new Income-tax Act, 2025 and is important for understanding how tax data may be shared for government programme administration without sending full return data.
Who is affected
Taxpayers whose PAN/Aadhaar data is queried by the Petroleum Ministry, CBDT systems teams, subsidy/program administrators and privacy/compliance functions.
Action / control point
Affected programme administrators should use only the authorised query fields and MoU process. Taxpayers should ensure PAN-Aadhaar linkage and return records are correct but should not interpret the order as a general public disclosure of tax-return data.
Key verified facts
- CBDT designated the Director General of Income Tax (Systems), Delhi as the specified authority for furnishing information to the Joint Secretary (Marketing), Ministry of Petroleum & Natural Gas.
- The order is issued under section 258(1) of the Income-tax Act, 2025 and refers to section 536(2)(j).
- The Petroleum Ministry will provide PAN and/or Aadhaar along with the relevant assessment year or tax year.
- The authorised response is structured as Yes/No/Not Available flags for specified queries rather than transfer of the complete underlying return.
- The order requires an MoU covering transfer mode, confidentiality, secure preservation, deletion/weeding and timelines.
Detailed Finin2min analysis
The most important feature is data minimisation. The order is designed around binary or limited-status responses, not a general sharing of return schedules, bank information or assessment files. That distinction matters for privacy, system design and public communication.
The move also illustrates how the Income-tax Act, 2025 is replacing legacy section references in administrative data-sharing arrangements. Compliance teams should therefore distinguish a superseding order from a substantive expansion of tax liability. The order changes the legal channel and authority for information exchange; it does not create a new head of income or tax rate.
PAN-Aadhaar linkage has a practical systems consequence because an Aadhaar number that cannot be mapped to PAN may produce a “not available” outcome. Individuals participating in relevant petroleum-sector schemes should keep identity linkage and filing status current to reduce false mismatches, while programme administrators should build exception handling instead of treating a missing flag as proof of ineligibility.
For government IT teams, the MoU becomes the control layer: it should define permissible fields, authentication, logs, retention, purpose limitation and breach handling. Auditable query trails are especially important where a tax-status flag influences eligibility for a subsidy or benefit.
Tax professionals should avoid overstating the order as a new surveillance power. It is an authorised information-sharing mechanism with specified parties and fields. Any decision adverse to a taxpayer should still be traceable to the governing programme rules and applicable principles of notice, correction and due process.
From an audit perspective, purpose limitation is central. A binary response designed for one government programme should not silently become a reusable risk score across unrelated programmes unless law authorises that use. The MoU and system logs should therefore make the requesting purpose and authorised recipient visible.
Taxpayers may also need a correction path because administrative databases can lag. A return filed under a different identifier state, an unlinked Aadhaar or a processing delay can generate a “not available” response even when the taxpayer has complied. Programme rules should avoid treating technical absence as conclusive non-compliance without an opportunity to cure.
For professionals advising affected individuals, the practical check is simple: verify PAN-Aadhaar linkage, filing acknowledgement, tax payment status and government-employment data before a benefit application is assessed. That reduces avoidable mismatch while preserving the principle that only the minimum authorised tax information should be shared.
What not to infer
The order does not make complete income-tax returns available to the Petroleum Ministry and does not, by itself, change a taxpayer’s substantive tax liability.
What to watch next
- Publication/execution of the MoU between DGIT (Systems) and MoP&NG
- Programme-specific use of the verified flags
- Any taxpayer correction or grievance mechanism
- Further section 258 information-sharing orders under the 2025 Act
Source and methodology
- Controlling source: Income Tax Department / CBDT — https://www.incometaxindia.gov.in/documents/d/guest/order-under-section-258-15-9-2026-pdf
- Source date: 2026-09-15
- Research cutoff: 2026-09-16 23:21 IST
Finin2min uses a primary-source-first hierarchy. Official regulator, government, court, exchange and company documents control operative facts where reasonably available. Reuters is used for live market data, source-based reporting and developments where a public primary document is not practically available. Competitor finance portals are discovery-only where stronger evidence can be closed.
Disclaimer
This material is for general information and education only. It is not investment, tax, legal, accounting or financial advice. Markets, regulations, litigation, tax positions and transaction terms can change after the stated research cutoff. Verify the latest controlling source and obtain appropriate professional advice before acting on a material decision.
View official source →
Educational and professional reference only — not financial, tax or legal advice. Confirm the current official position from the primary source before acting on any figure, rate, provision or deadline.