What to Do When GST Portal Shows ‘Invoice Already Filed

You are uploading your GSTR-1 JSON file, and the GST portal throws back a message: Invoice Already Filed. No explanation. No next step. Just an error that stops your filing cold.

This is one of the most misunderstood errors in GST compliance, and it trips up businesses of all sizes, from small traders to large enterprises filing hundreds of invoices monthly. The good news: it is almost always fixable without contacting your CA or raising a grievance ticket.

This guide walks you through exactly what this error means, why it happens, and the precise steps to resolve it.

What Does “Invoice Already Filed” Actually Mean?

The GST portal tracks every invoice by its unique document number, financial year, and GSTIN combination. When you try to upload an invoice that matches a record already present in the portal’s database, it flags it as a duplicate and throws this error.

The critical thing to understand here is that the portal does not care whether you intended to file that invoice or whether it was filed correctly. If the document number exists in the system under your GSTIN for that return period, the system blocks the new entry.

This can happen even if you never manually submitted that invoice, because third-party integrations, earlier JSON uploads, or auto-populated data from your e-invoicing system may have already pushed it through.

Common Reasons This Error Appears

The error does not always mean you made a mistake. Here are the situations that most commonly trigger it.

An earlier partial upload went through.

You may have uploaded a JSON file previously and assumed it failed. In many cases, some invoices from that file were successfully ingested by the portal even though the upload showed an error. Those invoices now exist in the system.

E-invoice auto-population.

If you are on the e-invoicing system (applicable for businesses above the threshold turnover), your IRN-generated invoices are automatically pushed to the GSTR-1 portal. When you try to file the same invoice again via JSON upload or manual entry, the portal flags it.

Accounting software double-export.

Tally Prime and other accounting tools sometimes export the same invoice across two JSON files when a user re-exports without checking the date range. Both files get uploaded, and the second one fails on the overlapping invoices.

Amendment filed for original invoice.

Once an invoice is amended in a previous return period, the original document number remains in the system. Trying to file it again as a fresh invoice triggers this error.

Invoice filed under a different section by mistake.

An invoice may have been filed under B2CS instead of B2B, or vice versa. The invoice number is still “in the system,” causing this conflict.

How to Confirm Which Invoice Is Causing the Error?

Before you fix anything, confirm exactly which invoice the portal is rejecting.

Open the error report that the portal generates after a failed JSON upload. It is available under Returns Dashboard > GSTR-1 > Error Report. The file lists each rejected invoice with its document number and the specific error code.

Cross-reference those document numbers against your GSTR-1 dashboard under the relevant section (B2B, B2CS, CDNR, etc.). If you can see the invoice already sitting in the portal with the correct details, you do not need to do anything further for that specific invoice. It is already filed.

Step-by-Step: How to Fix the Error

Step 1 — Check If the Invoice Is Already Correctly Filed

Log in to the GST portal. Go to Services > Returns > GSTR-1. Select the relevant return period. Open each section (B2B, B2CS, etc.) and search for the invoice number. If the invoice is there with correct values (GSTIN, taxable amount, tax amount, HSN), it has already been filed and you do not need to re-upload it.

Remove that invoice from your JSON file in Tally (or your accounting software) and re-upload the cleaned file.

Step 2 — If the Invoice Is Incorrectly Filed

If the invoice exists in the portal but with wrong values, you cannot overwrite it by re-uploading. You must amend it. AmendmenWhat to Do When GST Portal Shows ‘Invoice Already Filedts in GSTR-1 are done in the next return period under the amendment tables (B2BA for B2B, B2CSA for B2CS, CDNRA for credit notes).

Do not try to delete and re-upload in the same period. The portal does not support deletion of already-accepted invoices within the same GSTR-1 period.

Step 3 — If the Invoice Was Filed Under the Wrong Section

This is a two-step correction. First, raise a credit note or amendment in the current/next period to nullify the incorrectly filed entry. Second, add the invoice under the correct section. This ensures the net effect is correct without leaving phantom entries on the portal.

Step 4 — Clean Your Export in Tally Prime

If the error is caused by a double-export from Tally, go to Gateway of Tally > Display More Reports > Statutory Reports > GST Reports > GSTR-1. Check the filing status of the relevant vouchers. Vouchers already exported will show a different status. Exclude them from your next export by adjusting the filter or marking them as filed.

Quick Reference: Error Scenarios and Fixes

What Not to Do?

Raising a grievance ticket as the first step wastes time. The GST helpdesk will ask you to verify the invoice status yourself before they intervene. Start with the portal checks described above.

Do not delete the invoice from your accounting software thinking it will remove it from the portal. Your accounting records and the portal are separate. Deleting in Tally does not delete from the GST portal.

Do not file a nil GSTR-1 for the period and assume the error will disappear. Nil returns do not clear invoice-level conflicts.

Do not ignore the error and submit without resolving it. The portal may allow submission with errors in some cases, but those invoices will not count as validly filed and can cause ITC issues for your buyer.

How to Prevent This from Happening Again?

The simplest prevention is a pre-upload reconciliation habit. Before every GSTR-1 filing, compare your software’s invoice list against what is already sitting on the portal dashboard. This takes ten minutes and eliminates most duplicate filing issues.

If you use e-invoicing, ensure your accounting software is configured to pull the auto-population data from the portal before generating the JSON file. Tally Prime has a built-in option to import auto-populated data from GSTR-1; use it.

Also maintain a monthly filing log with the invoice ranges covered in each JSON upload. When you know exactly which document numbers were in each file, tracking down duplicates becomes straightforward.

Frequently Asked Questions

Q1. Will my buyer lose ITC because of this error?

If the invoice was already successfully filed (and is visible on the portal with correct values), your buyer will receive it in their GSTR-2B. The error only affects the new upload attempt, not the already-filed record. However, if the invoice has wrong values, the ITC your buyer claims may not match what you filed, which can cause a mismatch during reconciliation.

Q2. Can I amend an invoice in the same GSTR-1 period?

No. Amendments are only possible in the subsequent return period. Once an invoice is accepted by the portal in a given period, it cannot be modified within that same period’s GSTR-1 return.

Q3. The portal shows the invoice but with a different GSTIN. What do I do?

This means the invoice was filed under the wrong supplier GSTIN (possibly a data entry error). You will need to raise a credit note for the incorrectly filed invoice and file a fresh invoice with the correct GSTIN. Contact your CA if the GSTIN belongs to a different registered entity.

Q4. I filed the invoice under B2CS but it should be B2B. Is it recoverable?

Yes, it is recoverable but requires an amendment cycle. You need to amend the B2CS entry to reduce the value, and then file the correct invoice under B2B in the next period. The net tax liability remains the same, but the invoice trail becomes accurate.

Q5. Tally shows the invoice as “not filed” but the portal shows it as filed. Why?

This usually happens when a manual upload was done directly on the portal (not via Tally’s export), or when someone else in your organization uploaded the JSON without marking the invoices in Tally. Reconcile your portal data with Tally by using the GSTR-1 import function in Tally to pull the portal’s filed status.

Q6. Will this error attract a penalty?

The error itself does not attract a penalty. It is a portal validation check, not a compliance violation. However, if the error causes you to miss the GSTR-1 deadline, late filing fees will apply regardless of the reason.

Q7. What if the error persists even after I remove the invoice from the JSON?

Re-generate the JSON file completely rather than editing the existing one. Sometimes a corrupted JSON carries metadata from the original upload that confuses the portal. In Tally, delete the exported JSON and generate a fresh one after making your corrections.

Final Word

The “Invoice Already Filed” error is the GST portal’s way of protecting the integrity of your return data. It is not a penalty; it is a guard rail. Once you understand that the invoice is likely sitting correctly in the system already, the resolution path becomes clear: verify, clean your upload file, and proceed.

For most businesses, this error is resolved within 15 minutes once you know where to look.