Nine times out of ten, a stuck RoDTEP or drawback claim is not a DGFT problem. It is an eBRC problem sitting quietly at the AD bank. Here are the four mismatches we see most often.
1. Shipping bill number mismatch
The eBRC quotes a shipping bill that is one digit off, or references a cancelled bill. DGFT rejects silently. Fix: bank raises a correction against the correct bill number and re-transmits.
2. Realised value differs from invoice value
The AD bank has applied bank charges before crediting, so the realised value on the eBRC is lower than the invoice. DGFT sees a short realisation and blocks the claim. Fix: reconcile bank charges separately and get the bank to reissue at gross realisation.
3. Wrong purpose code
The IRM was tagged with a services purpose code when the underlying shipment was goods. The eBRC issues under the services code, and the DGFT scheme does not recognise it. Fix: purpose-code correction at the AD bank, followed by fresh eBRC issuance.
4. Multiple eBRCs against one shipping bill
Partial remittances have generated multiple eBRCs, none of which cover the full shipping bill value. DGFT waits for a consolidated position. Fix: reconcile all part-remittances and issue a consolidated eBRC.
The right sequence
Do not raise a DGFT ticket first. It will get closed with "contact your AD bank." Start at the bank, reconcile the bill, get the corrected eBRC transmitted, then re-file the incentive claim. The saved time is usually three to four weeks per file.
Common questions
Quick answers
- Who corrects an eBRC, the AD bank or DGFT?
- The AD bank issues and cancels eBRCs. DGFT only consumes them. Any correction has to originate at the AD-bank trade desk, be re-transmitted, and then reflected in the DGFT portal before an incentive claim can be re-filed.
- How long does an eBRC correction usually take?
- Once the AD bank agrees on the exact fields to change, the technical correction takes three to seven working days. Most delay is in the reconciliation upstream, not the bank action itself.
