Why Your Bank AD Code Is Not Reflecting on ICEGATE Portal After Approval (Complete 2026 Guide)

Key Takeaways

• Bank approval and final ICEGATE registration status are not necessarily the same.

• ICEGATE displays different statuses for system verification and Customs approval.

• Incorrect PAN, IEC, account number, IFSC or AD Code mapping can prevent successful verification.

• ICEGATE introduced API-based bank verification through its advisory dated 1 October 2026.

• Applicants should check the existing request before submitting a fresh application.

• AD Code registration and Refund/Incentive bank account registration are separate functions.

Introduction

An Authorised Dealer (AD) Code is an important banking detail for businesses involved in international trade. Exporters generally need to register their bank’s AD Code and associated account details on ICEGATE to complete relevant Customs procedures.

However, a common problem occurs when the bank confirms that the AD Code has been approved, but the details are still not visible on the ICEGATE portal.

This can create difficulties when exporters are preparing shipping bills or trying to complete other export-related formalities.

The important point is that approval or confirmation by the bank does not automatically establish that the registration has completed every verification stage on ICEGATE.

Why Is Your Bank AD Code Not Reflecting on ICEGATE?

1. Customs approval is still pending

An application may have passed initial system checks but still be awaiting approval at the selected Customs port.

ICEGATE’s AD Code registration advisory identifies separate statuses, including System Pending, System Rejected, Custom Port Pending, Custom Port Approved and Custom Port Rejected.

The bank account is reflected on the dashboard once the request reaches Custom Port Approved status under the earlier workflow. Always check the actual status rather than relying only on the bank’s confirmation.

2. PAN and IEC details do not match

ICEGATE’s updated 2026 verification process checks whether the PAN, IEC and bank account details are consistent across the relevant records.

Common issues include:

• PAN not correctly linked with the bank account.

• IEC not updated in the bank’s records.

• PAN and IEC mapped to different customer profiles.

• Difference in the entity name across records.

3. Incorrect bank account number or IFSC

Even a small mistake in the account number or IFSC can result in unsuccessful verification.

The IFSC must correspond to the branch maintaining the account. The account must also be active and operational.

4. Incorrect AD Code or bank branch mapping

The AD Code must be valid, issued by the concerned bank and mapped to the relevant account and authorised foreign-exchange branch.

Selecting an incorrect branch or using an AD Code that is not mapped properly can prevent successful verification.

5. Bank KYC or customer records are outdated

The bank’s customer master records and KYC details must be complete and updated.

Dormant, inactive, frozen, restricted or closed accounts may fail the verification process.

6. ICEGATE or bank server issues

ICEGATE’s 1 October 2026 advisory confirms that verification depends on the availability of the concerned bank’s systems.

Maintenance, network disruption or temporary service unavailability may interrupt the process. In such cases, users should retry after some time and check the existing application status before filing another request.

Important 2026 Update: ICEGATE Introduces API-Based Bank Verification

ICEGATE issued an advisory dated 1 October 2026 introducing electronic verification of AD Code and Incentive bank account details through secure API-based services with participating banks.

Under this process:

• Bank verification results are generated using responses received from the concerned bank.

• For API-integrated banks, users do not need to select a document type or upload supporting documents with the corresponding IRN.

• The AD Code can be entered to retrieve bank and branch details through the portal.

• Verification failures must be corrected with the concerned bank wherever the problem originates in bank records.

This is an important change for exporters because document requirements and verification steps may differ depending on whether the bank is integrated with ICEGATE.

How to Check Your AD Code Registration Status on ICEGATE

Follow these steps:

1. Visit the official ICEGATE portal and log in using your registered credentials.

2. Open Financial Services.

3. Select Bank Account Management.

4. Open Authorised Dealer (AD) Code Registration.

5. Check the registered bank account and Customs location.

6. Review the application status and open the relevant request to view error details, wherever available.

The dashboard helps identify whether the request is pending, rejected or approved.

What Should You Do If Your AD Code Is Approved but Not Visible?

Follow this practical resolution process:

Step 1: Check the exact status. Confirm whether the request shows Custom Port Approved or is still pending at another stage.

Step 2: Verify bank details. Cross-check the account number, IFSC, AD Code, bank name and branch.

Step 3: Confirm PAN and IEC mapping. Ask your bank to verify that the entity’s PAN and IEC are correctly linked to the same customer profile.

Step 4: Check the bank integration status. Refer to ICEGATE’s active and inactive bank list for ADC and INC integration.

Step 5: Contact the bank. Request correction of any mismatch in its customer master records or AD Code mapping.

Step 6: Contact ICEGATE Helpdesk. If bank-side details are correct but the portal still does not reflect the registration, raise a support request with the application reference and relevant screenshots.

ICEGATE Helpdesk:

• Phone: 1800-3010-1000

• Email: icegatehelpdesk@icegate.gov.in

AD Code Registration vs Refund/Incentive Bank Account

These are separate account categories on ICEGATE:

• Foreign Remittance Account (AD Code): Used to declare the bank details associated with foreign remittances.

• Refund/Incentive Account: Used for receiving eligible Customs refunds and export incentives.

Do not assume that approval of one account automatically completes registration of the other.

Featured Snippet: Why Is an Approved AD Code Not Reflecting on ICEGATE?

An approved AD Code may not reflect on ICEGATE because final portal verification is incomplete, bank records do not match PAN or IEC details, the account or IFSC is incorrect, or the bank’s verification system is temporarily unavailable. Check the registration dashboard, confirm the bank details and contact the bank or ICEGATE Helpdesk for resolution.

FAQs

1. Why is my AD Code not showing on ICEGATE after bank approval?

Bank approval may not mean that ICEGATE verification and registration are complete. Check the application status and confirm the bank and Customs-side records.

2. How many days does AD Code approval take on ICEGATE?

Processing depends on verification requirements and the selected workflow. ICEGATE’s FAQ mentions 7–10 working days for a Custom Pending status. This is guidance, not a guaranteed timeline.

3. Can PAN and IEC mismatch affect AD Code registration?

Yes. ICEGATE’s October 2026 advisory specifically identifies PAN–IEC mismatch and different customer ID mapping as reasons for verification failure.

4. Do I need to upload documents for AD Code registration in 2026?

For banks integrated with ICEGATE’s API-based verification, document type selection and supporting document upload with IRN are not required. Requirements may differ for other banks.

5. Is AD Code registration required separately at every Customs port?

The registration dashboard and applicable Customs instructions should be checked for the current process. Do not assume that an older port-wise procedure still applies to every new registration.

6. What should I do if my AD Code request is rejected?

Open the application status, check the error code and rejection reason, correct the underlying bank or application details and follow the applicable resubmission or modification process.

Conclusion

If your bank AD Code is approved but not reflecting on ICEGATE, the issue may be related to pending portal processing, incorrect bank details, PAN–IEC mapping or unsuccessful electronic verification.

The October 2026 API-based verification advisory makes it especially important to ensure that your bank records are accurate and updated before submitting an application.

Always check the actual ICEGATE dashboard status, coordinate with your bank and avoid submitting duplicate requests without understanding the reason for the delay.

Need Assistance With AD Code Registration on ICEGATE?

A V International provides professional import-export consultancy and regulatory compliance support to exporters, manufacturers and businesses across India.

Our services include:

• Bank AD Code registration assistance.

• ICEGATE registration and bank account mapping.

• AD Code modification and documentation support.

• Refund and incentive bank account registration guidance.

• DGFT licensing and export-import compliance.

• Customs and shipping bill-related consultancy.

Connect with A V International for professional assistance with AD Code registration and ICEGATE-related issues.

Written By

Akash Bhangare

Having more than 10 years of experience in EPR Compliance, Legal Metrology, DGFT Regulations and Import Export Consulting Services in India.

Associated with A V International, a company with over 35 years of expertise in Environmental Compliance, EPR Registrations, Licensing and Regulatory Approvals.