Recommended Free Tools
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To fix a Form 3CA, 3CB or 3CD error before submission, first confirm the assessment year and the correct form regime, then regenerate the file in the latest Income Tax Department utility. An INVALID JSON message usually calls for importing or resuming the draft in that latest utility and downloading fresh JSON; INVALID METADATA usually means that identity, year, filing-type, form-code or CA-membership details do not agree between the utility, JSON and portal.
The workflow below is for reports that have not yet been accepted and verified. Portal labels, utility versions and signing components can change, so use the current year-specific instructions and the latest download from the Income Tax Department’s Income Tax Forms downloads page.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat should I check before fixing any error?
Check the tax year and form path before changing data. A technically valid JSON can still be rejected if it belongs to the wrong year, filing type or form code.
Confirm the year regime
The Department’s current FAQ says that financial year 2025–26, corresponding to assessment year (AY) 2026–27, continues to use Forms 3CA, 3CB and 3CD under the Income-tax Act, 1961. It says that Tax Year 2026–27 uses the unified Form 26 under the Income-tax Act, 2025. Form 26 is not an alternative name for 3CA, 3CB or 3CD; do not use a legacy utility or form for a year that has moved to the new regime.
Popular on Amazon
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
The same FAQ stated 30 September 2026 as the tax-audit-report deadline for AY 2026–27. That date has passed as of 13 November 2026, so treat it as historical rather than as an upcoming deadline. The FAQ also states 30 September 2027 for Tax Year 2026–27 under the new regime. Check the portal for any extension, late-filing direction or year-specific notice before submitting.
Choose the correct legacy form combination
| Form combination | Use it when | What the CA submits |
|---|---|---|
| 3CA-3CD | The assessee’s accounts are required to be audited under another law. | Form 3CA together with the particulars in Form 3CD. |
| 3CB-3CD | The accounts are not required to be audited under another law. | Form 3CB together with the particulars in Form 3CD. |
These distinctions are set out in the Department’s Form 3CB-3CD guidance and the Form 3CA-3CD user manual. The form combination must match the code selected on the portal and in the offline utility.
Record the current draft before replacing it
Keep a copy of the old JSON, the utility data file if the utility provides one, screenshots of the error, and any transaction or draft reference. Do not overwrite your only copy. These records help you identify what changed and give the CA and taxpayer a common reference if the assignment has to be restarted.
How do I fix the “INVALID JSON” error?
Use the latest applicable utility, bring the old draft into it, review every panel, and generate a new JSON. The Department’s FAQ explicitly says: “Please ensure that you are using latest utility available under ‘Downloads’ tab in the e-Filing Portal.”
- Open the Department’s Downloads page. Download the utility listed for the relevant year and form combination from the official Income Tax Forms downloads page. Do not assume that a utility downloaded for a previous assessment year remains valid.
- Install or start the new utility. Use the release and operating-system instructions supplied with that download. A generic JSON-repair program or paid software is not required by the Department’s remedy.
- Import the old JSON or resume the draft. If the utility offers an import function, import the JSON that produced the error. If the draft was saved in the portal workflow or utility, use the current utility’s resume/open-draft option instead. If the file cannot be imported, start a new draft in the current utility and re-enter the data from the signed working papers.
- Confirm every panel. Review taxpayer identification, assessment year, original or revised filing type, form combination, CA details, dates, amounts, schedules and all applicable clauses. An import can carry forward values that were accepted by an older version but are no longer valid for the current schema.
- Save and validate in the current utility. Use its own validation controls. Correct any field-level messages before proceeding; do not edit the JSON text manually unless the Department’s current instructions specifically tell you to.
- Generate fresh JSON. Download a new JSON from the current utility, note its file name and creation time, and upload that new file rather than the old one.
If the error message identifies particular clauses, apply the clause-specific step below only after confirming that the current utility still presents the same problem. The Department’s detailed clarification is from January 2022, and its screens may not match the current release.
Also popular on Amazon
What does “INVALID METADATA” mean, and how do I correct it?
“INVALID METADATA” generally indicates that the identifying metadata in the utility or JSON does not match the filing choices made on the portal. Compare the values character by character, correct the source data, regenerate JSON and upload it again.
The Department’s FAQ says: “Please ensure that below details should be correct in the Utility/JSON for which form is being submitted.” Check these five items in both places:
- Taxpayer PAN: Confirm that the PAN in the utility and JSON is the PAN of the taxpayer whose account is being used. Watch for transposed characters, spaces or a draft belonging to another taxpayer.
- Assessment year: The AY selected in the portal must be the same AY encoded in the file. Do not substitute a financial year label for an assessment-year value, and do not use an AY-2026–27 file in a Tax Year 2026–27 Form 26 workflow.
- Original or revised filing type: Select the same filing type in the portal and utility. If the report is revised, ensure that the revision option and any required reference to the earlier report are completed according to the current utility’s prompts.
- Form code: Match 3CA-3CD with 3CA-3CD and 3CB-3CD with 3CB-3CD. Choosing one combination on the portal while generating the other in the utility creates a metadata mismatch even when the underlying accounts and clauses are correct.
- CA membership number: Verify the membership number of the signing CA in the utility/JSON against the CA assigned on the portal. A draft prepared by one CA cannot be uploaded under a different assigned CA without correcting the assignment and regenerating the file.
After correcting any mismatch, save the draft, run the current utility’s validation, generate a new JSON and upload only that new file. Rechecking the portal selection after generation is worthwhile because changing a portal choice after the file was created can recreate the same error.
Should I re-enter clauses 11, 18, 20, 21, 26 and 34?
Possibly, but treat this as legacy troubleshooting rather than a universal rule. The Department’s January 2022 clarification says that, when generating JSON, data in clauses 11, 18, 20, 21, 26 and 34 should be re-entered. It does not establish that every current utility requires those clauses to be retyped.
- First install the latest utility and try the import or resume process.
- Check whether the current utility flags one or more of those clauses or produces an error that corresponds to the clarification.
- Open the affected clause, clear the carried-forward value if the utility instructs you to, and re-enter it from the approved working papers and books.
- Save the clause, validate the entire form, and generate a new JSON. Never copy a value merely to silence an error; reconcile it to the underlying records.
Keep the 2022 Department clarification on Forms 3CA-3CD and 3CB-3CD as a reference, but follow the current utility’s labels and validation messages if they differ.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Also popular on Amazon
What is the correct taxpayer–CA handoff before submission?
The taxpayer and CA have different portal actions. Keeping those handoffs separate prevents a corrected JSON from being sent through the wrong account.
- Taxpayer assigns the CA. The taxpayer’s registered e-Filing account selects the assessment year, form type and filing type, then assigns the report to the CA using the portal’s current assignment flow.
- CA accepts the assignment. The CA signs in with the registered account, accepts the assignment and prepares the report in the offline utility. The CA should confirm that the utility’s PAN, AY, filing type, form code and membership number match the assignment before generating JSON.
- CA uploads and signs. The CA uploads the generated JSON from the assigned account and submits it with a valid Digital Signature Certificate (DSC), following the current signing prompt.
- Taxpayer accepts and verifies. After the CA’s submission, the taxpayer reviews the report in the taxpayer account, accepts it and completes the required verification. Save the acknowledgement and transaction references after each successful stage.
If the CA rejects the assignment, the taxpayer—not the CA—must make a new assignment. Reassigning a rejected assignment is an assignment step; it is not the same thing as revising a report that has already been accepted and verified.
What should I check if the JSON is correct but upload or signing still fails?
Separate file errors from account and signing prerequisites. A valid JSON cannot be submitted if the account, assignment or DSC setup is incomplete.
Account and assignment checks
- Both taxpayer and CA should have registered e-Filing accounts with the required profile details.
- Confirm that the PAN statuses are active and that the taxpayer is using the correct PAN account.
- Verify that the assignment is visible to the intended CA and that the CA has accepted it.
- Ensure that the selected assessment year, filing type and form code are the same on the assignment and in the utility-generated file.
DSC and local signing checks
- Use a valid, active DSC belonging to the signing CA and registered as required on the portal.
- If the current portal instructions require a token, token driver, emSigner or emBridge component, install or update those components from the official instructions and restart the signing process.
- Check that the token is connected, the correct certificate is selected and its validity has not expired.
- Review the CA profile, email address and mobile number if the portal requires contact details for verification or signing.
The Department’s older clarification lists these setup checks as possible causes when upload or signing does not complete. Because components and browser requirements change, use the current portal’s help and download instructions rather than relying on an old installer or an unofficial fix.
Free tools Windows power users keep installed
One-click scans. No signup required.
How can I distinguish a JSON-generation problem from a metadata problem?
Use the error text to choose the shortest check sequence instead of changing unrelated data.
Also popular on Amazon
| Error type | Most likely issue | First action | Next action |
|---|---|---|---|
| INVALID JSON | The file was created by an old utility, is incomplete, or does not conform to the current schema. | Download the latest applicable utility. | Import or resume the draft, confirm all panels and generate fresh JSON. |
| INVALID METADATA | Identity or filing selections do not agree between the file and portal. | Compare PAN, AY, original/revised type, form code and CA membership number. | Correct the mismatch in the utility and portal, then regenerate JSON. |
| Upload or verification failure after correction | Account, assignment, DSC or signing-component issue. | Check registered accounts, active PAN status, assignment and DSC. | Follow current emSigner/emBridge, token and profile instructions. |
Do not infer a cause from an error message that is not covered by the Department’s guidance. Capture the exact current message and consult the portal’s current help material or a qualified Indian tax professional if the issue persists.
What should I do after a successful upload?
Confirm completion at each stage rather than assuming that a successful file upload means the report is filed. The CA should confirm that the portal accepted the JSON and DSC submission; the taxpayer should then accept and verify the report. Download or record the acknowledgement, transaction ID and any assignment reference shown by the portal.
Keep the final JSON, utility output, signed working papers and acknowledgement together with the report’s preparation records. If a later notice refers to the report, these references allow the taxpayer and CA to identify exactly which submission was accepted.
Can an already accepted and verified report be corrected through this workflow?
No supported post-verification correction process is established by the user manuals covered here. The workflow in this article is for correcting a report before the taxpayer accepts and verifies it. Rejecting or reassigning a CA assignment is not automatically a method for revising a filed report.
If the report has already been accepted and verified, stop before creating a duplicate submission. Check the current official instructions for the relevant year and obtain advice from a qualified Indian tax professional on whether a revised report, portal response or other statutory route is available.
Also popular on Amazon
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Final pre-submission checklist
- Year confirmed: AY 2026–27 legacy forms or the applicable Tax Year/Form 26 regime.
- Correct combination selected: 3CA-3CD where another law requires an audit, otherwise 3CB-3CD.
- Latest applicable utility downloaded from the Department’s Downloads page.
- Old JSON imported or draft resumed in that utility, with every panel reviewed.
- PAN, assessment year, original/revised type, form code and CA membership number agree in the utility, JSON and portal.
- Any clause-specific re-entry was performed only where the current utility indicates it is needed, with values reconciled to working papers.
- Taxpayer assignment and CA acceptance are complete.
- Registered accounts, active PAN statuses, profile details and valid active DSCs are ready.
- Required token drivers, emSigner or emBridge components are current where the portal calls for them.
- Fresh JSON generated after every correction; old JSON is not reused.
- CA upload and DSC submission completed, followed by taxpayer acceptance and verification.
- Acknowledgement, transaction and assignment references saved.
For the Department’s original troubleshooting language and form instructions, consult the official FAQ for Forms 3CA-3CD and 3CB-3CD, the January 2022 clarification, and the current Income Tax Forms information page. Portal guidance is procedural information, not individualized tax advice.
Frequently Asked Questions
Can I upload the same JSON again after an INVALID JSON message?
Usually no. Keep the rejected file for your records, but import or resume its data in the latest applicable utility, validate the draft and generate a new JSON before trying again. A file name change alone does not update the schema or metadata.
Is Form 26 the revised name for Form 3CD?
No. The Department describes Form 26 as part of the unified regime for Tax Year 2026–27 under the Income-tax Act, 2025. For FY 2025–26 (AY 2026–27), the Department says the 3CA, 3CB and 3CD forms under the 1961 Act continue to apply.
Can the taxpayer edit figures inside a CA-prepared tax-audit JSON?
The CA prepares and signs the report in the utility, while the taxpayer accepts and verifies it on the portal. The taxpayer should send corrections to the CA rather than alter the generated JSON, because an out-of-band edit can invalidate the file or the professional’s signing responsibility.
What if the portal shows a different error after I fix the metadata?
Record the exact new message and stop making unrelated changes. Reconfirm the assignment, account status and DSC prerequisites, then use the current portal help for that specific message or seek qualified professional advice; the remedies for INVALID JSON and INVALID METADATA do not cover every portal error.
