ICEGATE now verifies AD Code and incentive bank accounts directly with banks through API; no document upload for API-integrated banks
ICEGATE has integrated with participating banks to verify AD Code and incentive bank account details electronically. For API-integrated banks, the user need not select a document type or upload a document with IRN. The advisory of 1 October 2026 lists what must match across ICEGATE, DGFT and bank records, and the common reasons a verification fails.
Key facts
- Published
- 1 October 2026
- Section
- Customs
- What it is
- New facility
- In force
- ICEGATE advisory dated 1 October 2026
- Who it affects
- Exporters and importers registering or modifying AD Code and incentive bank accounts on ICEGATE, customs brokers, authorised dealer banks
In 30 seconds
- The advisory is dated 1 October 2026 and covers AD Code (ADC) and Incentive (INC) bank account registration on ICEGATE.
- Verification results are system-generated from the bank’s response; ICEGATE does not alter or override them.
- For API-integrated banks, no document type need be selected and no document or IRN need be uploaded.
- Entity name, PAN, IEC, account number, IFSC and AD Code must be the same in ICEGATE, DGFT and bank records.
- In incentive account registration, an “All” option lets the user select every applicable customs location in one action.
- If verification fails, re-check the entries and approach the bank to correct its records.
हिंदी में सार
ICEGATE ने 1 अक्टूबर 2026 की advisory में बताया है कि AD Code और incentive बैंक खाते का सत्यापन अब बैंकों से सीधे API के ज़रिये होगा। API से जुड़े बैंकों के लिए दस्तावेज़ का प्रकार चुनने या दस्तावेज़ और IRN अपलोड करने की ज़रूरत नहीं है। नाम, PAN, IEC, खाता संख्या, IFSC और AD Code — ICEGATE, DGFT और बैंक, तीनों के रिकॉर्ड में एक जैसे होने चाहिए; सत्यापन विफल हो तो बैंक से रिकॉर्ड ठीक कराएँ।
What has changed
ICEGATE has integrated with participating banks to verify AD Code (ADC) and Incentive (INC) bank account details electronically, through secure API-based services. The advisory dated 1 October 2026 says the verification result shown on ICEGATE is system-generated, based on the response received from the bank concerned.
For banks integrated through API, the user is not required to select a document type or upload any document with its IRN.
What the user must get right
| Item | What the advisory requires |
|---|---|
| Bank account number | Correct, and of an active and operative account |
| PAN | Correctly linked with the bank account and matching the bank’s records |
| IEC | Updated with the bank and mapped to the same customer / entity profile as the PAN and the account |
| IFSC | Of the branch that maintains the account |
| AD Code (for ADC registration) | Valid, issued by the bank concerned, and mapped to the relevant account / authorised branch |
| Consistency | Entity name, PAN, IEC, account number, IFSC and AD Code must be consistent across ICEGATE, DGFT and bank records |
| KYC | KYC and customer master records complete and up to date; the account must not be dormant, inactive, frozen, restricted or closed |
| Branch | Where applicable, select the correct account-maintaining branch and use the AD Code of the authorised foreign-exchange branch |
Changes on the screens
- AD Code registration: on entering the AD Code and clicking “get details”, the system shows the name of the bank and the branch name. If several branches are linked to the same AD Code, the branch names appear in a dropdown.
- Incentive account registration: the Custom Port Location dropdown now has an “All” option, so that all applicable customs locations can be selected in a single action.
Why verification fails
- Incorrect account number or IFSC.
- Invalid or unmapped AD Code.
- PAN / IEC mismatch, or PAN and IEC mapped to different Customer IDs.
- Outdated KYC or customer master data.
- Inactive, dormant, frozen, restricted or closed account; wrong branch selected; or inconsistency among ICEGATE, DGFT and bank records.
If it fails, or the bank’s system is down
Users should re-check the particulars entered on ICEGATE and approach the bank to correct or update its records. ICEGATE only exchanges the request and the response; it does not change the outcome communicated by the bank.
Verification depends on the bank’s systems being available. In case of maintenance, network disruption or temporary unavailability, retry after some time. Where processing continues beyond the browser session, check the application status before submitting a fresh request.
What exporters should do
Update and validate your records with the bank before starting an ADC or INC registration or modification request on ICEGATE. The advisory adds that supporting-document requirements for accounts verified online are being streamlined, and that the ADC and INC workflows are being enhanced for better field validation and branch identification.
Questions and answers
Do I still have to upload a bank document for AD Code registration on ICEGATE?
Not where the bank is API-integrated. The advisory says that for API-integrated banks, selection of the document type and uploading of any document with the corresponding IRN are not required from the user.
Why did my AD Code or incentive account verification fail?
The advisory lists the common reasons: incorrect account number or IFSC, invalid or unmapped AD Code, PAN/IEC mismatch, PAN and IEC mapped to different Customer IDs, outdated KYC, an inactive or frozen account, wrong branch selection, or inconsistency among ICEGATE, DGFT and bank records.
Can ICEGATE override a failed verification?
No. ICEGATE facilitates the exchange of verification requests and responses and does not alter or override the outcome communicated by the bank. The correction has to be made in the bank’s records.
What if the bank’s system is not responding?
Retry after some time. If processing continues beyond the browser session, check the application status before submitting a fresh request.
Published 1 October 2026. Updated 5 October 2026. This report is for general information and is not professional advice. Read the source document before acting on it.