EDPMS (Export Data Processing and Monitoring System) is the Reserve Bank of India's system for tracking outstanding export bills. When a shipping bill's proceeds aren't realized and reported within the prescribed period, the entry stays open in EDPMS - and gets flagged to your AD (Authorized Dealer) bank, and eventually to the RBI caution list, which can block your ability to export until it's resolved.
If your finance team has ever been asked by the bank to "explain your EDPMS position," this guide walks through what that means and how closure actually works.
What is EDPMS, exactly?
EDPMS is RBI's centralized platform, operated through AD banks, that monitors every export transaction from shipping bill to final payment realization. Every time you export goods, the shipping bill is uploaded to EDPMS, and the entry stays "open" until your AD bank confirms the payment has been received and matched against that bill.
The system exists so RBI can track that export proceeds are actually coming back into India, in line with FEMA (Foreign Exchange Management Act) requirements - it's a compliance and forex-monitoring tool, not a punitive one by design. Entries only become a problem when they sit open too long.
Why do EDPMS entries stay open?
In practice, entries go unresolved for a handful of recurring reasons:
- Delayed or partial payment from the overseas buyer
- Mismatched invoice values between the shipping bill and the actual remittance received
- Purpose code errors on the inward remittance, so the bank's system can't auto-match it to the export
- Missing or delayed eBRC (Bank Realization Certificate) submission
- Multiple shipping bills settled against a single remittance, which needs manual linking
- No one owning the reconciliation - the finance team assumes the bank or CA is tracking it, and no one is
Most businesses don't find out an entry is stuck until the bank flags it during a routine review, or an EPCG/RoDTEP claim gets stuck behind it.
What happens if EDPMS entries stay open too long?
There's a compounding timeline, not a single cutoff:
| Time open | What typically happens |
|---|---|
| Within RBI's prescribed period (currently 9 months from shipment for most exports) | Normal - treated as in-process |
| Beyond the prescribed period | AD bank is required to follow up and may report the entry as overdue |
| Extended non-realization | Entry risks being flagged to the RBI caution list |
| On the caution list | Future export transactions can face additional scrutiny or be blocked until the entry is resolved |
The risk isn't the individual entry - it's that unresolved entries quietly accumulate, and by the time a bank raises it formally, a finance team can be looking at months or years of backlog rather than one clean fix.
How EDPMS closure actually works
Closing an entry means proving, to the AD bank's satisfaction, that the export proceeds have been correctly received and matched. The process generally runs through four stages:
- Reconciliation - Pull every open EDPMS entry from the AD bank and match it against actual remittances received, invoice by invoice.
- Root-cause correction - Fix whatever is blocking the match: correct purpose codes, link split remittances to the right shipping bills, chase any genuinely unpaid invoices, or get missing documentation from the buyer's bank.
- eBRC alignment - Ensure a valid eBRC exists for each resolved entry, since AD banks use it as proof of realization.
- Formal closure request to the AD bank - Submit the reconciliation with supporting documents and request the bank close the entry in EDPMS. This step needs the AD bank's direct sign-off; it can't be done unilaterally.
Steps 1–3 are where most of the actual work - and most of the delay - happens. A bank won't close an entry on a general assurance; it wants a matched, documented trail for each one.
A real example
One pharmaceutical exporter came to thefintrado with three years of unresolved EDPMS entries and a looming caution-list risk. The issue wasn't unpaid invoices - it was purpose-code mismatches and unlinked partial remittances that had never been reconciled. After auditing every outstanding bill against the AD bank's records and correcting the mismatches, full closure was completed inside six weeks, with the caution-list risk removed and a clean record going into the client's next banking review.
That timeline is typical once the backlog is properly mapped - the delay is almost always in the reconciliation, not the bank's process itself.
Three things to check this week
If you haven't reviewed your EDPMS register recently, start here:
- Any shipping bills open beyond 9 months - pull the list from your AD bank directly; don't rely on memory.
- Purpose codes matching the actual transaction - a mismatched code is the single most common reason an otherwise-paid entry stays open.
- Your AD bank's latest EDPMS reconciliation report - most banks will share this on request; if you've never seen one, that's a signal.
Facing a backlog of pending EDPMS entries? Book a free 20-minute compliance review - no obligation, confidential, response within one business day.
thefintrado provides end-to-end EXIM compliance advisory for Indian exporters, importers, and enterprises, including EDPMS & IDPMS closure, eBRC issuance, DGFT licensing, and RBI coordination.
Common questions
Quick answers
- What's the difference between EDPMS and IDPMS?
- EDPMS tracks export bills and proceeds; IDPMS (Import Data Processing and Monitoring System) does the equivalent for import remittances. They're companion systems - an export-heavy business deals mainly with EDPMS, an import-heavy one with IDPMS, and many businesses handle both.
- How long does EDPMS closure typically take?
- It depends on the size of the backlog and how many entries have genuine documentation gaps versus simple mismatches. A handful of purpose-code corrections can close in days; a multi-year backlog typically takes weeks, not months, once it's properly resourced.
- Can I close EDPMS entries myself without an advisor?
- Yes, for straightforward cases - it's your AD bank's process, not a third-party gate. Advisory help tends to matter most at volume, or when entries have sat long enough that the documentation trail needs to be reconstructed.
