# DGFT Scraps Physical Challan Requirement for EODC from August 2026 *Advance Authorisation and EPCG holders can now submit duty payments electronically via ICEGATE integration* - Canonical: https://eximlabh.io/newsletter/dgft-scraps-physical-challan-requirement-for-eodc-from-august-2026 - Markdown: https://eximlabh.io/newsletter/dgft-scraps-physical-challan-requirement-for-eodc-from-august-2026.md - Published: 2026-09-08T00:00:00.000Z - Tag: DGFT - Author: EximLabh AI ## DGFT Scraps Physical Challan Requirement for EODC: What Advance Authorisation & EPCG Holders Must Do Now DGFT has removed one of the most tedious steps in the EODC process. From 1 August 2026, exporters closing Advance Authorisation and EPCG obligations no longer need to attach physical duty-payment challans. Customs payment data now flows directly from ICEGATE into DGFT's system. ## What actually changed Per the PIB release dated 10 August 2026, DGFT has eliminated the requirement for physical challan submission on voluntary duty payments made on or after 1 August 2026 in EODC applications under both AA and EPCG. This change is built on an API integration between DGFT and ICEGATE. Licence-wise Customs duty-payment records now move electronically into DGFT's EODC processing system. In practice: - Exporters can check authenticated payment records on the DGFT Customer Portal before filing. - Regional Authorities pull the same data from the DGFT Back Office, eliminating manual challan verification on both sides. - No physical TR-6 challan copy needs to be uploaded or couriered for payments after the cutoff. This complements two other digitisation moves. Trade Notice No. 02/2026-27 established an online module for Post Export EPCG duty credit scrips, also built on ICEGATE data exchange. Additionally, DGFT cleared 59% of pending AA cases and 54% of pending EPCG cases during a special drive in March 2026. The challan change arrives during this high-volume closure push, making file-level accuracy critical. ## Where this matters in practice The old process required exporters to generate a TR-6 challan from Customs after paying duty on shortfall or default in export obligation, then upload it manually as part of the closure file. That manual step is now gone for post-1 August payments. However, "gone" does not mean "no verification needed." The system now depends entirely on correct mapping between the Customs payment record and the specific authorisation number. If that mapping fails, whether through a data entry error at the bank, a wrong licence reference at payment time, or a lag in ICEGATE transmission, the EODC application can be flagged or rejected. ## The reconciliation exporters need to do now Before filing any EODC application dated on or after 1 August 2026, complete this check: - Log into the DGFT Customer Portal and retrieve the voluntary duty payment record against each authorisation number. - Confirm the payment is correctly attributed to that specific AA or EPCG licence, not unmapped or linked to a different file. - Cross-check the amount against your internal export obligation tracker. Discrepancies are the most common rejection trigger during transitions like this. - For Post-Export EPCG duty credit scrip cases, treat these separately since Trade Notice No. 02/2026-27 governs a distinct online module. - Keep a saved copy or screenshot of the portal-verified payment as your own evidence trail until the new process stabilises. One unresolved point: whether payments made before 1 August 2026 still require the legacy physical-challan-upload route, or whether there is a transition window for applications already in the pipeline. Wait for DGFT's formal notification or the relevant Trade Notice number before proceeding. ## Trade context: why this matters at scale | Destination | FY 2025 exports (₹ crore) | | --- | ---: | | US | 770,252 | | AE | 329,685 | | CN | 172,509 | | NL | 153,824 | | GB | 118,783 | | SG | 105,223 | | DE | 101,931 | | BD | 93,467 | A large share of this export volume runs through duty-exemption schemes like AA and EPCG. Every shipment eventually needs an EODC to close the file. Given the backlog DGFT cleared in March 2026, a digital duty-payment link that avoids manual challan mismatches should speed up closures. But that speed only helps if your underlying data mapping is clean first. ## What to do this week - Pull licence-wise voluntary duty payment records from the DGFT Customer Portal for any EODC application you plan to file dated on or after 1 August 2026. - Verify each payment is correctly mapped to the right authorisation number before submission. - Reconcile your internal export obligation tracker against the ICEGATE-sourced data on the portal. - Separate Post-Export EPCG duty credit scrip files from standard EODC applications, since they use a different online module. - For any payment made before 1 August 2026, confirm with your Regional Authority whether the old physical-challan-upload requirement still applies. **Keywords:** DGFT, EODC, Advance Authorisation, EPCG, ICEGATE, export obligation discharge certificate, TR-6 challan, Foreign Trade Policy 2023 --- Source: The EximLabh Brief. Citation-backed trade notes, not legal advice.