AD Code Re-Mapping After Bank or Port Change: Exporter Checklist
By Ravi Sisodia · Reviewed by CA Divyanshu Sengar · Updated 5 October 2026
Finin2min 2-Minute Summary
Changing the exporter bank, branch or customs port is not a cosmetic profile edit. The exporter should confirm the bank account used for export proceeds, the AD code linked to the relevant customs location, the IEC/ICEGATE profile and the acknowledgement generated after the change. A successful shipping-bill filing is not proof that the banking linkage is correct for later realisation or export-incentive processing.
Practical position
Start with a port-wise register showing port code, old AD code, new AD code, bank branch, effective date and the first shipping bill expected to use the new mapping. Obtain the bank letter/certificate in the format required by the customs location or ICEGATE process and keep the IEC details consistent. Where the business has multiple ports, do not assume a change made for one customs location automatically propagates to every other location. Before the first shipment after a change, verify the exporter profile, bank account and port mapping on the system actually used for filing.
Issue-specific control
Separate three events in the control file: a bank-account change, an AD-code change and addition of a customs location. They may occur together, but each can have a different effective point. For the first shipment after remapping, nominate one owner to verify the ICEGATE filing acknowledgement and one owner to verify the later bank-realisation trail; that two-stage check catches profile changes that appear successful at filing but fail downstream.
Worked example
An exporter moves its collection account from Bank A to Bank B while continuing exports from Nhava Sheva and adding Mundra. The safe sequence is to preserve the old mapping, obtain Bank B evidence, map the new AD code for each relevant port, and test the first shipping bill. The team also checks whether e-BRC realisation will flow to the expected bank record. If Mundra is newly added, its mapping is treated as a new-port setup rather than a side effect of the Nhava Sheva change.
Documents and action checklist
- Bank certificate/letter supporting the AD code and account
- IEC and ICEGATE profile identifiers
- Port code and location-specific mapping acknowledgement
- First shipping bill filed after the change
- Bank realisation/e-BRC trail for the first affected shipment
- Internal register showing old and new mapping with effective date
Frequently asked questions
Does one AD-code change cover every customs port?
Not necessarily. Treat port mapping as location-specific unless the official process confirms otherwise.
Should the old mapping be deleted immediately?
Preserve evidence of the old mapping and effective date. Historical shipments may still need to be reconciled against it.
What is the best post-change control?
Test the first shipment end to end: shipping bill, bank linkage, realisation record and any export-benefit data.
Official sources
Reader note
Use this AD Code Re-Mapping After Bank or Port Change: Exporter Checklist guide with the current official instrument and the records for the actual event date. Where facts, jurisdiction or legal status differ, re-test the conclusion before acting.
Disclaimer
Educational and professional reference only; confirm the current law, rates and the facts of your case before relying on this page.