Try it
Trade Intelligence Guides

Export Refund Stuck? How EGM, SB005, IGST Refund, Drawback and RoDTEP Are Connected

Reviewed by: Stavyx Trade Intelligence Team Last reviewed: October 2026

The cargo has left.

The Shipping Bill shows export.

But the money or export benefit has not arrived.

This is where export teams often begin checking five portals and calling four people without knowing which record actually failed.

The better approach is to identify which downstream process is stuck and trace it back to the transaction field that controls it.

The short answer

An export refund or incentive can remain pending because the underlying electronic records do not reconcile.

Common examples include:

  • EGM not filed
  • Gateway EGM unavailable
  • invoice number mismatch
  • Shipping Bill details mismatch
  • GSTIN mismatch
  • drawback claim pending in scroll processing
  • RoDTEP claim / e-scrip not progressing
  • incentive bank-account issue
  • post-export amendment not yet reprocessed

Start with the status / error code.

Then fix the source record or process that owns that error.

Why is the money stuck?
  1. Shipping Bill
    Export declaration
  2. LEO
    Export permitted
  3. EGM
    Departure recorded
  4. Validation
    Where the downstream checks run
  • IGST refund
    Held if EGM or invoice data will not validate
  • Duty Drawback
    Held pending scroll generation
  • RoDTEP / e-scrip
    Held if the Shipping Bill declaration is wrong

On an error: find the exact code, find the source record, assign an owner, correct it, then re-check the downstream status.

First separate the three problems

Exporters often say:

“My refund is stuck.”

But they may mean completely different things.

1. IGST refund

Linked to GST/customs validation and Shipping Bill data.

2. Duty Drawback

A customs incentive / drawback processing flow.

3. RoDTEP / RoSCTL

An export-incentive claim that flows through Shipping Bill declarations and the ICEGATE e-scrip system.

Do not troubleshoot one as though it were another.

Why EGM matters after cargo has already left

ICEGATE's IGST refund guidance explicitly requires EGM information in the validation chain.

Common error responses include:

If the carrier has not correctly filed / integrated the EGM, the exporter may see a refund problem even though the cargo physically exported.

That is why post-shipment tracking matters.

What is SB005 error?

ICEGATE identifies SB005 as:

Invalid invoice number

For the exporter, the useful question is not the code itself.

It is:

Which invoice reference differs between the GST data and the Shipping Bill / customs record?

Check the exact characters.

Typical causes can include:

Do not create a new invoice simply to clear the validation.

Correct the wrong system record through the permitted process.

A simple SB005 example

Commercial invoice:

INV/2026/148

Shipping Bill:

INV/2026/148

GST filing:

INV-2026-148

To a person, these may look “the same”.

To an electronic validation, they may not be the same reference.

The team needs to identify exactly where the invalid reference sits and use the correct amendment route.

This is a classic example of a low-value-looking data difference becoming a high-friction operational problem.

Other common IGST validation codes

ICEGATE guidance lists:

CodeMeaning
SB000Successfully validated
SB001Invalid Shipping Bill details
SB002EGM not filed
SB003GSTIN mismatch
SB004Record already received / validated
SB005Invalid invoice number
SB006Gateway EGM not available

ICEGATE also explains that once invoice validations in a Shipping Bill are completed, a scroll is generated and processed for disbursement.

The important operational idea is:

The refund is an output. The validation chain is the input.

Fix the failed validation first.

Why “pending for scroll generation” matters

A scroll is part of the downstream processing chain for eligible refunds / benefits.

If your status is pending for scroll generation, the first task is to understand:

Do not assume “scroll pending” always means Customs is simply slow.

Sometimes the transaction is waiting because a preceding record is incomplete.

Duty Drawback: what can hold it up?

Drawback processing can be affected by issues such as:

Chennai Customs, for example, issued a 2025 facility circular specifically addressing cases where drawback could not be credited due to wrong account number or invalid IFSC.

The lesson is broader:

Customs may have processed the export correctly, but the payment leg can still fail.

Always separate:

eligibility / processing status from payment-credit status.

RoDTEP: Shipping Bill declaration matters

RoDTEP is not something to think about only after export.

The claim originates from the Shipping Bill / export declaration workflow and is later handled through the e-scrip system.

For operations teams, check:

A missing or incorrect source declaration can be much harder to solve after export than before filing.

Example: one shipment, three downstream problems

An exporter has one Shipping Bill.

After shipment:

IGST refund

Status: SB005

Drawback

Status: pending

RoDTEP

Benefit not visible

Do not treat this as “one customs problem”.

Build a simple control table:

ProcessStatusLikely next check
IGST refundSB005invoice reference in GST vs Shipping Bill
DrawbackpendingEGM / query / scroll / bank credit status
RoDTEPnot visibleShipping Bill claim / eligibility / e-scrip processing

The underlying Shipping Bill connects them.

But each outcome has its own processing chain.

A 10-minute exporter troubleshooting sequence

1. Confirm Shipping Bill status

Is the correct Shipping Bill visible?

2. Confirm LEO and EGM

Has post-export movement been correctly integrated?

3. Read the exact error

Do not troubleshoot from “refund pending”.

Use the actual code/status.

4. Compare the source fields

Invoice number, Shipping Bill, GSTIN, port code, amounts and other relevant references.

5. Identify the owner

- exporter GST team
- CHA
- shipping line
- Customs
- bank-account maintenance
- ICEGATE / DGFT helpdesk depending on the issue

6. Recheck after correction

Do not assume amendment automatically means reprocessing is complete.

Where transaction intelligence helps

Most refund problems are not solved by another definition of “IGST refund”.

They are solved by answering:

What failed?
Which records disagree?
Who owns the correction?
Has the correction propagated downstream?

That is a transaction-control problem.

The same exporter may otherwise have:

and still not receive the expected outcome because those records did not reconcile electronically.

What does SB005 mean?

ICEGATE identifies SB005 as invalid invoice number in the IGST refund validation process.

What is SB002?

SB002 means EGM not filed. ICEGATE advises exporters to approach the shipping line/airline/carrier.

What is SB006?

SB006 means Gateway EGM is not available.

Why is my IGST refund not sanctioned after filing GST returns?

ICEGATE notes that refund may not process if validations fail at GSTN or Customs, including invoice, GSTIN or EGM-related errors.

Why is drawback pending?

Possible causes vary. Check Shipping Bill/EGM integration, customs query status, scroll status and bank account / credit details.

How does RoDTEP relate to the Shipping Bill?

The claim is connected to export declaration / Shipping Bill processing and later to ICEGATE e-scrip functionality.

This guide is educational. Refund and incentive rules, eligibility and portal procedures can change. Check current ICEGATE/CBIC instructions and your live Shipping Bill status.

This guide is educational and does not replace examination of the specific credit, applicable ICC rules, international standard banking practice, contractual requirements or professional advice relevant to a particular transaction.