IGST refund stuck after export? Here's why — and how to fix it
Here's the second article — clean copy, ready to paste:
IGST refund stuck after export? Here's why — and how to fix it
You've shipped the goods, the buyer has paid, and you're waiting on an IGST refund that should have landed weeks ago. Your CA says the shipping bill is fine. Your bank says the payment came through. But the refund is nowhere.
This happens to experienced exporters more than it should — and the cause is almost never obvious, because the IGST refund system involves four separate government systems talking to each other. When one conversation breaks down, the whole chain stalls.
One important note before you read further: this article covers exporters who paid IGST on exports and are claiming a refund through the automated scroll process. If you export under a Letter of Undertaking (LUT) — where no IGST is paid upfront — your refund mechanism is different. You'd claim accumulated input tax credit through Form RFD-01 with your jurisdictional GST officer, not through ICEGATE. The checklist at the end of this article won't apply to you.
How the refund chain is supposed to work
When you export goods with IGST paid, the refund is meant to be automatic. You file your shipping bill on ICEGATE. You declare the same invoices in GSTR-1 under Table 6A. You report the exports as zero-rated supplies in Table 3.1(b) of your GSTR-3B and pay the IGST. GSTN then transmits that data to ICEGATE, which matches it against the shipping bill. If everything aligns, a Refund Scroll is generated and the money goes to your bank.
Four systems need to agree: ICEGATE, GSTN, your bank's PFMS registration, and the EGM filed by your shipping line. If any one of them has mismatched or missing data, the system doesn't just slow down — it stops, generates an error code, and waits for you to notice.
Under the GST Act, the statutory deadline for processing a refund is 60 days from the LEO date. In practice, clean refunds arrive within 2–4 weeks. If you're past 60 days and nothing has moved, something is genuinely stuck — not just delayed.
Where it breaks and why
The EGM wasn't filed — or was filed incorrectly
This is the single biggest cause of stuck refunds, and the frustrating part is it's not your mistake. The Export General Manifest is filed by your shipping line after your cargo physically leaves India. Until the EGM is filed and matched against your shipping bill on ICEGATE, the refund cannot be processed.
If your shipping bill shows LEO but your refund hasn't moved, check EGM status first. Go to Services → Enquiry → Public Enquiry 2.0 on ICEGATE. If it's missing, call your shipping line with the sailing date, container number, and shipping bill number. Most shipping lines file within 1–2 days of departure. If yours hasn't after a week, escalate in writing.
GSTR-3B and GSTR-1 both need to be right
Most exporters know to file their invoices in Table 6A of GSTR-1. What's less understood is that GSTN also checks Table 3.1(b) of your GSTR-3B, where exports need to be declared as zero-rated supplies. If GSTR-3B is incorrect or the figures don't reconcile with GSTR-1, GSTN won't transmit your data to ICEGATE — regardless of how clean your shipping bill is. If your refund shows no status at all, check both returns before assuming it's an ICEGATE problem.
Data mismatch between your GST return and your shipping bill
ICEGATE matches invoice data field by field — invoice number, invoice date, invoice value, IGST amount, port code, and GSTIN all need to be identical across both systems. A single character difference breaks the match.
Common mismatches: invoice numbers formatted differently across systems, wrong port code in GSTR-1, or a ₹1 rounding difference in IGST values. Check your refund status under Services → Refunds → Track Refund Status on ICEGATE. The error code tells you exactly which system has the problem.
The codes you're most likely to see:
SB000 means approved — money should arrive within days. SB001 means invoice details don't match between GSTR-1 and the shipping bill. SB002 or SB006 typically indicates the EGM hasn't been filed — check the advisory message alongside the code, since the exact mapping can vary. SB004 means duplicate invoice data was transmitted — usually harmless if the earlier record already validated. SB005 means a GSTIN mismatch. PFMS rejection means your bank account details on the GST portal don't match what's registered.
For SB001 and SB005, amend through Table 9A in GSTR-1 and wait for the next GSTN transmission cycle — typically 48–72 hours. For EGM errors, chase the shipping line. For PFMS failures, validate your bank account on both the GST portal and ICEGATE. Allow 3–5 days after updating for PFMS to confirm.
Your IEC is suspended
An IEC under suspension blocks IGST refunds completely, regardless of how clean everything else is. If your refund is stuck and the error codes don't explain it, log in to the DGFT portal and check your IEC status. A suspended IEC needs to be reinstated before any refund can process.
The EDPMS link that holds up your eBRC
Your IGST refund and your eBRC are separate but connected. The eBRC officially closes your shipping bill in EDPMS — RBI's system for tracking export proceeds. Until EDPMS shows the entry as closed, your export isn't considered fully compliant under FEMA, which affects future incentive claims and keeps your bank following up on realisation.
The chain runs like this: payment arrives from your overseas buyer → your AD bank receives an Inward Remittance Message (IRM) → the bank matches the IRM against your shipping bill in EDPMS → the bank generates your eBRC → EDPMS closes the entry.
Where this breaks: the IRM arrives but the bank doesn't map it to the right shipping bill — usually because the payment reference or AD code details don't align cleanly. The result is an open EDPMS entry and a delayed eBRC.
One deadline most exporters miss: the eBRC must be uploaded within 9 months of the export date for your refund claim to remain valid. If your bank is slow to reconcile and you're approaching that window, escalate immediately — don't wait for them to come to you.
Check your EDPMS status on ICEGATE under Public Enquiries → RBI-SB-EDPMS Enquiry. If the entry shows open despite payment clearing, give your bank the UTR number and SWIFT reference for the inward transfer and ask for manual mapping.
As of October 2025, RBI simplified this for smaller transactions: EDPMS entries up to ₹10 lakh per shipping bill can be closed on an exporter self-declaration, with quarterly consolidated declarations allowed for multiple bills. If you have a backlog of small-value open entries, ask your AD bank's trade finance desk to use this route.
When the automated system can't be fixed
Sometimes the mismatch between GSTN and ICEGATE is a system error on their end — not something you can correct through an amendment. In those cases, the automated scroll process simply won't work. The fallback is a manual refund application through Form RFD-01 filed with your jurisdictional GST officer, with the full supporting documentation: shipping bill, GSTR-1 and GSTR-3B filings, IGST payment proof, and eBRC.
Before treating any rejection as final, check that the refund order carries a Document Identification Number (DIN). Under CBIC Circular 14/2024, refund orders without a DIN are invalid. If you received a rejection letter without one, the order itself isn't legally enforceable — raise this with your jurisdictional officer before accepting the rejection.
If the helpdesk isn't resolving the issue, the next step is filing a grievance directly on the GST portal under Services → Refunds → Track Status → Raise Grievance. If that doesn't move things, escalate to your jurisdictional GST officer in writing with your shipping bill number, error code, and a timeline of the issue.
How slow payment documentation makes this worse
Every step in this chain depends on clean, timely payment documentation. When your overseas buyer sends USD or EUR, three things need to happen quickly: the FIRC gets issued, the IRM gets filed by your bank, and the EDPMS entry gets matched and closed. When these lag — which they routinely do with traditional banks — your eBRC is delayed, your EDPMS entry stays open, and your IGST refund claim sits in limbo even after customs has approved it.
This is where Winvesta's Global Collections Account makes a practical difference. When a payment arrives in your GCA account, the FIRC is generated instantly. Payment documentation is clean and linked to the correct invoice from the start. And because the records are structured for compliance, the reconciliation your bank needs to close the EDPMS entry is straightforward rather than a week of back-and-forth.
For exporters who are already managing the ICEGATE side well but keep hitting delays on payment realisation, this is usually where the remaining friction is.
[Open a free Winvesta GCA account →]
When your refund is stuck: go through this in order
Check EGM status on ICEGATE. If it's not filed, the shipping line is the first call — not your CA.
Check that Table 3.1(b) in your GSTR-3B reflects your exports as zero-rated supplies, not just Table 6A in GSTR-1.
Check your IGST refund error code under Services → Refunds → Track Refund Status. Read the advisory message alongside the code — the code alone can be ambiguous.
For data mismatch errors, amend through Table 9A in GSTR-1 and wait 48–72 hours for GSTN to retransmit.
Verify your IEC is active on the DGFT portal. A suspended IEC blocks refunds completely.
Confirm your bank account is PFMS-validated on the GST portal. Allow 3–5 days after updating.
Check EDPMS status on ICEGATE under Public Enquiries → RBI-SB-EDPMS Enquiry. If the entry is open despite payment clearing, give your bank the UTR and SWIFT reference and ask for manual mapping.
Watch the 9-month eBRC deadline from your export date. If you're approaching it and your bank hasn't reconciled, escalate immediately.
If the automated process is broken beyond amendment, file RFD-01 with your jurisdictional GST officer.
For unresolved issues, raise a grievance on the GST portal under Services → Refunds → Raise Grievance, then escalate to your jurisdictional officer in writing.
Disclaimer: The information provided in this blog is for general informational purposes only and does not constitute financial or legal advice. Winvesta makes no representations or warranties about the accuracy or suitability of the content and recommends consulting a professional before making any financial decisions.
Get paid globally. Keep more of it.
No FX markups. No GST. Funds in 1 day.
Table of Contents
Here's the second article — clean copy, ready to paste:
IGST refund stuck after export? Here's why — and how to fix it
You've shipped the goods, the buyer has paid, and you're waiting on an IGST refund that should have landed weeks ago. Your CA says the shipping bill is fine. Your bank says the payment came through. But the refund is nowhere.
This happens to experienced exporters more than it should — and the cause is almost never obvious, because the IGST refund system involves four separate government systems talking to each other. When one conversation breaks down, the whole chain stalls.
One important note before you read further: this article covers exporters who paid IGST on exports and are claiming a refund through the automated scroll process. If you export under a Letter of Undertaking (LUT) — where no IGST is paid upfront — your refund mechanism is different. You'd claim accumulated input tax credit through Form RFD-01 with your jurisdictional GST officer, not through ICEGATE. The checklist at the end of this article won't apply to you.
How the refund chain is supposed to work
When you export goods with IGST paid, the refund is meant to be automatic. You file your shipping bill on ICEGATE. You declare the same invoices in GSTR-1 under Table 6A. You report the exports as zero-rated supplies in Table 3.1(b) of your GSTR-3B and pay the IGST. GSTN then transmits that data to ICEGATE, which matches it against the shipping bill. If everything aligns, a Refund Scroll is generated and the money goes to your bank.
Four systems need to agree: ICEGATE, GSTN, your bank's PFMS registration, and the EGM filed by your shipping line. If any one of them has mismatched or missing data, the system doesn't just slow down — it stops, generates an error code, and waits for you to notice.
Under the GST Act, the statutory deadline for processing a refund is 60 days from the LEO date. In practice, clean refunds arrive within 2–4 weeks. If you're past 60 days and nothing has moved, something is genuinely stuck — not just delayed.
Where it breaks and why
The EGM wasn't filed — or was filed incorrectly
This is the single biggest cause of stuck refunds, and the frustrating part is it's not your mistake. The Export General Manifest is filed by your shipping line after your cargo physically leaves India. Until the EGM is filed and matched against your shipping bill on ICEGATE, the refund cannot be processed.
If your shipping bill shows LEO but your refund hasn't moved, check EGM status first. Go to Services → Enquiry → Public Enquiry 2.0 on ICEGATE. If it's missing, call your shipping line with the sailing date, container number, and shipping bill number. Most shipping lines file within 1–2 days of departure. If yours hasn't after a week, escalate in writing.
GSTR-3B and GSTR-1 both need to be right
Most exporters know to file their invoices in Table 6A of GSTR-1. What's less understood is that GSTN also checks Table 3.1(b) of your GSTR-3B, where exports need to be declared as zero-rated supplies. If GSTR-3B is incorrect or the figures don't reconcile with GSTR-1, GSTN won't transmit your data to ICEGATE — regardless of how clean your shipping bill is. If your refund shows no status at all, check both returns before assuming it's an ICEGATE problem.
Data mismatch between your GST return and your shipping bill
ICEGATE matches invoice data field by field — invoice number, invoice date, invoice value, IGST amount, port code, and GSTIN all need to be identical across both systems. A single character difference breaks the match.
Common mismatches: invoice numbers formatted differently across systems, wrong port code in GSTR-1, or a ₹1 rounding difference in IGST values. Check your refund status under Services → Refunds → Track Refund Status on ICEGATE. The error code tells you exactly which system has the problem.
The codes you're most likely to see:
SB000 means approved — money should arrive within days. SB001 means invoice details don't match between GSTR-1 and the shipping bill. SB002 or SB006 typically indicates the EGM hasn't been filed — check the advisory message alongside the code, since the exact mapping can vary. SB004 means duplicate invoice data was transmitted — usually harmless if the earlier record already validated. SB005 means a GSTIN mismatch. PFMS rejection means your bank account details on the GST portal don't match what's registered.
For SB001 and SB005, amend through Table 9A in GSTR-1 and wait for the next GSTN transmission cycle — typically 48–72 hours. For EGM errors, chase the shipping line. For PFMS failures, validate your bank account on both the GST portal and ICEGATE. Allow 3–5 days after updating for PFMS to confirm.
Your IEC is suspended
An IEC under suspension blocks IGST refunds completely, regardless of how clean everything else is. If your refund is stuck and the error codes don't explain it, log in to the DGFT portal and check your IEC status. A suspended IEC needs to be reinstated before any refund can process.
The EDPMS link that holds up your eBRC
Your IGST refund and your eBRC are separate but connected. The eBRC officially closes your shipping bill in EDPMS — RBI's system for tracking export proceeds. Until EDPMS shows the entry as closed, your export isn't considered fully compliant under FEMA, which affects future incentive claims and keeps your bank following up on realisation.
The chain runs like this: payment arrives from your overseas buyer → your AD bank receives an Inward Remittance Message (IRM) → the bank matches the IRM against your shipping bill in EDPMS → the bank generates your eBRC → EDPMS closes the entry.
Where this breaks: the IRM arrives but the bank doesn't map it to the right shipping bill — usually because the payment reference or AD code details don't align cleanly. The result is an open EDPMS entry and a delayed eBRC.
One deadline most exporters miss: the eBRC must be uploaded within 9 months of the export date for your refund claim to remain valid. If your bank is slow to reconcile and you're approaching that window, escalate immediately — don't wait for them to come to you.
Check your EDPMS status on ICEGATE under Public Enquiries → RBI-SB-EDPMS Enquiry. If the entry shows open despite payment clearing, give your bank the UTR number and SWIFT reference for the inward transfer and ask for manual mapping.
As of October 2025, RBI simplified this for smaller transactions: EDPMS entries up to ₹10 lakh per shipping bill can be closed on an exporter self-declaration, with quarterly consolidated declarations allowed for multiple bills. If you have a backlog of small-value open entries, ask your AD bank's trade finance desk to use this route.
When the automated system can't be fixed
Sometimes the mismatch between GSTN and ICEGATE is a system error on their end — not something you can correct through an amendment. In those cases, the automated scroll process simply won't work. The fallback is a manual refund application through Form RFD-01 filed with your jurisdictional GST officer, with the full supporting documentation: shipping bill, GSTR-1 and GSTR-3B filings, IGST payment proof, and eBRC.
Before treating any rejection as final, check that the refund order carries a Document Identification Number (DIN). Under CBIC Circular 14/2024, refund orders without a DIN are invalid. If you received a rejection letter without one, the order itself isn't legally enforceable — raise this with your jurisdictional officer before accepting the rejection.
If the helpdesk isn't resolving the issue, the next step is filing a grievance directly on the GST portal under Services → Refunds → Track Status → Raise Grievance. If that doesn't move things, escalate to your jurisdictional GST officer in writing with your shipping bill number, error code, and a timeline of the issue.
How slow payment documentation makes this worse
Every step in this chain depends on clean, timely payment documentation. When your overseas buyer sends USD or EUR, three things need to happen quickly: the FIRC gets issued, the IRM gets filed by your bank, and the EDPMS entry gets matched and closed. When these lag — which they routinely do with traditional banks — your eBRC is delayed, your EDPMS entry stays open, and your IGST refund claim sits in limbo even after customs has approved it.
This is where Winvesta's Global Collections Account makes a practical difference. When a payment arrives in your GCA account, the FIRC is generated instantly. Payment documentation is clean and linked to the correct invoice from the start. And because the records are structured for compliance, the reconciliation your bank needs to close the EDPMS entry is straightforward rather than a week of back-and-forth.
For exporters who are already managing the ICEGATE side well but keep hitting delays on payment realisation, this is usually where the remaining friction is.
[Open a free Winvesta GCA account →]
When your refund is stuck: go through this in order
Check EGM status on ICEGATE. If it's not filed, the shipping line is the first call — not your CA.
Check that Table 3.1(b) in your GSTR-3B reflects your exports as zero-rated supplies, not just Table 6A in GSTR-1.
Check your IGST refund error code under Services → Refunds → Track Refund Status. Read the advisory message alongside the code — the code alone can be ambiguous.
For data mismatch errors, amend through Table 9A in GSTR-1 and wait 48–72 hours for GSTN to retransmit.
Verify your IEC is active on the DGFT portal. A suspended IEC blocks refunds completely.
Confirm your bank account is PFMS-validated on the GST portal. Allow 3–5 days after updating.
Check EDPMS status on ICEGATE under Public Enquiries → RBI-SB-EDPMS Enquiry. If the entry is open despite payment clearing, give your bank the UTR and SWIFT reference and ask for manual mapping.
Watch the 9-month eBRC deadline from your export date. If you're approaching it and your bank hasn't reconciled, escalate immediately.
If the automated process is broken beyond amendment, file RFD-01 with your jurisdictional GST officer.
For unresolved issues, raise a grievance on the GST portal under Services → Refunds → Raise Grievance, then escalate to your jurisdictional officer in writing.
Disclaimer: The information provided in this blog is for general informational purposes only and does not constitute financial or legal advice. Winvesta makes no representations or warranties about the accuracy or suitability of the content and recommends consulting a professional before making any financial decisions.
Get paid globally. Keep more of it.
No FX markups. No GST. Funds in 1 day.