RBI & Banking
10 Common EDPMS Errors and How to Resolve Them
Shipping bill not reflecting, purpose code mismatch, amount discrepancy, aggregator payments, write-off limits. Solutions for each.
By Aaryan Kakani · · 13 min read
What Is EDPMS?
EDPMS (the Export Data Processing and Monitoring System) is the RBI's centralised platform for tracking every export transaction from the moment goods leave India to the moment the payment is realised and the Bank Realisation Certificate (BRC) is closed. Launched to replace the older XOS (Export Outstanding Statement) system, EDPMS gives the RBI real-time visibility into whether exporters are bringing foreign exchange back into the country within the prescribed timelines.
As an exporter, you do not log into EDPMS directly. Your Authorised Dealer (AD) bank is the intermediary. It reports your shipping bills, matches inward remittances, and closes entries on your behalf. But the data quality depends entirely on what you provide to the bank. If the shipping bill number is wrong, the purpose code is mismatched, or the payment amount does not tally, the EDPMS entry stays open. And open entries, once they age past the RBI's prescribed deadlines, trigger compliance flags that can cascade into caution listing, blocked incentive claims, and show-cause notices.
How EDPMS Works: The Four-Step Cycle
Understanding the EDPMS lifecycle helps you see exactly where each error occurs and why. Every export transaction follows the same four steps:
| Step | What happens | Who does it |
|---|---|---|
| 1. Shipping bill filed | Customs processes the shipping bill and the EGM (Export General Manifest) is filed by the shipping line or airline. This data flows from ICEGATE to EDPMS automatically. | Customs / Shipping line |
| 2. EDPMS entry created | The RBI system creates an open entry against the shipping bill number with the FOB value, port code, and date of shipment. | RBI (automatic) |
| 3. Bank receipt matching | When the buyer's payment arrives, the AD bank matches the inward remittance to the corresponding EDPMS entry using the shipping bill number and purpose code. | AD bank |
| 4. BRC closure | Once the full FOB value is matched, the AD bank issues an eBRC (electronic Bank Realisation Certificate) and the EDPMS entry is marked as closed. | AD bank |
Errors can creep in at any of these four steps. The shipping bill might not flow from ICEGATE to EDPMS. The bank might tag the receipt with the wrong purpose code. The amounts might not match due to exchange rate differences. Understanding where the breakdown occurs is the first step to resolving it.
Shipping Bill Not Reflecting in EDPMS
This is the most fundamental EDPMS error: your goods have shipped, the buyer has paid, but when your AD bank tries to match the receipt, the shipping bill simply does not exist in EDPMS. No entry, no match, no BRC.
The root cause is almost always a missing Export General Manifest (EGM). The EDPMS entry is created only after the EGM is filed by the shipping line or airline with customs. If the EGM is delayed, filed with errors, or the vessel/flight details do not match, the data never reaches EDPMS. In some cases, the customs port itself has a backlog in transmitting data to ICEGATE.
How to resolve it
- Check the EGM status on ICEGATE within 7 days of shipment. If the EGM has not been filed, contact your CHA (Customs House Agent) or freight forwarder immediately.
- For sea shipments, verify that the shipping line has filed the EGM with the correct vessel name, voyage number, and port code. Mismatched details prevent the data flow.
- If the EGM is filed but EDPMS still does not show the entry after 15 days, raise a query through your AD bank to the RBI regional office, referencing the shipping bill number and EGM filing date.
- For shipments through smaller ports or ICDs (Inland Container Depots), allow additional processing time. Data transmission from these locations is frequently delayed by 2. 4 weeks.
Purpose Code Mismatch
Every inward remittance must be tagged with a purpose code that tells the RBI what the payment is for. For goods exports, the three codes you will encounter most are:
| Code | Description | When to use |
|---|---|---|
| P0102 | Realisation of export bills (goods) | Payment received after shipment against a specific shipping bill |
| P0108 | Receipts against export of goods (services component) | Often misused for goods. Should only be for service-linked receipts against goods exports |
| P1007 | Advance payment against export orders | Payment received before shipment, against a confirmed export order or proforma invoice |
The most common mistake is tagging a goods export receipt as P0108 instead of P0102 . This happens because the buyer's bank or the correspondent bank picks a generic code during the SWIFT transfer, and your AD bank does not always correct it. When the purpose code is wrong, EDPMS cannot link the receipt to the shipping bill, and the entry stays open.
How to resolve it
- Submit a purpose code amendment request to your AD bank with the original shipping bill, the remittance advice, and a letter specifying the correct code. Refer to our purpose code change guide for the exact process.
- Include the correct purpose code in your proforma invoice and wire transfer instructions to the buyer. This prevents the error at source.
- Verify the purpose code on every bank credit advice within 48 hours of receipt. Catching it early means the amendment is simple; catching it after 9 months means it is an escalation.
Amount Mismatch Between Shipping Bill and Bank Receipt
The FOB (Free on Board) value on your shipping bill must match the amount your AD bank credits to your account. When there is a difference (even a few dollars) EDPMS flags the entry as a partial match or rejects the matching altogether.
Mismatches happen for several legitimate reasons: the buyer deducts bank charges from the payment, a trade discount is applied after shipment, the actual shipped quantity differs slightly from the invoiced quantity, or the buyer pays a rounded amount. In each case, the EDPMS entry cannot close until the difference is explained and documented.
How to resolve it
- If bank charges were deducted, provide your AD bank with a debit note from the buyer's bank showing the charges. The bank can then close the entry with the net amount.
- For trade discounts, submit a credit note to the buyer and provide a copy to your AD bank. The bank adjusts the EDPMS entry to match the reduced amount.
- If the difference is within the RBI's permissible variation (typically 5% or the AD bank's internal threshold), apply for a write-off of the shortfall amount through your AD bank.
- Never instruct the buyer to "pay OUR charges" (BEN charges) without confirming the exact net amount that will arrive. SHA (shared charges) often causes unpredictable deductions.
Multiple Receipts Against a Single Shipping Bill
Many buyers pay in instalments. An advance before shipment, a partial payment on delivery, and the balance 30 or 60 days later. Each payment creates a separate inward remittance that needs to be matched against the same shipping bill in EDPMS. If your AD bank does not know which remittances map to which shipping bill, the matching fails.
This is especially common with large orders where the buyer splits payments across multiple invoices or payment cycles. Each partial receipt must be explicitly linked to the shipping bill number. Without a clear mapping instruction from you, the AD bank may match the receipt against the wrong shipping bill or leave it unmatched entirely.
How to resolve it
- Provide your AD bank with a written "matching instruction" for every inward remittance, specifying the shipping bill number, the amount to be matched, and whether it is a partial or full payment.
- Maintain a shipment-wise payment tracker that shows the FOB value, amounts received to date, and the outstanding balance. Share this with your AD bank quarterly.
- Ask the buyer to include the shipping bill number or your invoice number in the SWIFT payment reference field. This helps your AD bank identify the correct mapping even without a separate instruction.
E-Commerce Aggregator Payments (Amazon, Payoneer, Stripe)
E-commerce exporters selling through Amazon Global, eBay, or Etsy face a unique EDPMS challenge: payments arrive as pooled remittances from the aggregator (Amazon or Payoneer), not from the individual buyer. A single wire transfer from Payoneer might cover 15 different shipping bills across 3 countries. The AD bank receives one lump sum and has no way to automatically match it against individual EDPMS entries.
The problem is compounded because aggregator payouts often include deductions for marketplace fees, return adjustments, and currency conversion charges. The net amount credited to your bank account rarely matches the sum of FOB values on your shipping bills.
How to resolve it
- Download the detailed payout report from the marketplace (Amazon Seller Central, Payoneer transaction report) and prepare a mapping sheet that links each order to its shipping bill number and the pro-rated share of the payout.
- Submit this mapping sheet to your AD bank with each pooled remittance. Most banks now accept a standard Excel format for bulk EDPMS matching.
- For marketplace fee deductions, provide the marketplace invoice showing the fees charged. The AD bank can then adjust the matching amount or process a write-off for the fee component.
- Consider using a bank that specialises in e-commerce exports. Several AD banks have dedicated e-commerce trade desks that understand pooled payouts.
Advance Payment Matching Issues
When a buyer sends an advance payment before shipment, the AD bank creates a separate advance entry in EDPMS under purpose code P1007 . This advance entry must eventually be matched to a shipping bill once the goods are shipped. If you do not ship within one year of receiving the advance, or if you do not provide the shipping bill details to the bank for matching, the advance entry stays open and ages into a compliance issue.
A common variant of this error: the buyer sends an advance, you ship the goods, but the AD bank creates a new EDPMS entry against the shipping bill and matches a fresh receipt against it. Leaving the original advance entry orphaned. Now you have one closed entry and one permanently open advance entry, even though the commercial transaction is complete.
How to resolve it
- Inform your AD bank on the day the advance arrives, with the buyer's purchase order and expected shipment date. Confirm the bank has created the advance entry under P1007.
- After shipping, immediately provide the shipping bill number to the bank with a specific instruction to match it against the existing advance entry. Not to create a new EDPMS entry.
- If you cannot ship within one year, apply for an extension through the AD bank or refund the advance to the buyer. Document either action to close the EDPMS advance entry.
Write-Off for Unrealised Exports
When a buyer defaults, disputes, or goes bankrupt and you cannot collect the export proceeds, the EDPMS entry remains open. Without a formal write-off, the RBI treats it as non-repatriation. Even if the commercial reality is that the money is irrecoverable.
The RBI prescribes specific write-off limits. AD banks can approve write-offs on their own up to 5% of total export proceeds for the financial year. For amounts between 5% and 10%, the AD bank requires RBI approval. Beyond 10%, you must apply directly to the RBI regional office with a detailed case file including correspondence with the buyer, legal notices, and an auditor's certificate.
How to resolve it
- Start the write-off process at the 6-month mark if the buyer is unresponsive. Do not wait for the 9-month deadline to pass.
- Gather supporting documents: email correspondence, legal demand notices, buyer insolvency records (if available), and a certificate from your statutory auditor confirming the amount is irrecoverable.
- Track your cumulative write-off percentage against total exports for the year. If you are approaching the 5% threshold, loop in the RBI early through your AD bank.
EDPMS Caution Listing: Triggers and Removal
The RBI maintains a "caution list" of exporters with a significant number of open or overdue EDPMS entries. Being placed on this list has serious operational consequences: your IEC may be flagged, new export incentive applications (RoDTEP, duty drawback, MEIS/SEIS) are held up, and some banks may refuse to open new Letters of Credit or process new export bills.
Caution listing is triggered when open EDPMS entries exceed a certain threshold. Typically when a significant proportion of your entries are overdue past 9 months. The RBI shares this caution list with DGFT (Directorate General of Foreign Trade), which can then hold up IEC renewals and new trade licences.
| Impact area | What happens |
|---|---|
| Export incentives | RoDTEP, duty drawback, and SEIS claims are held up until all overdue entries are closed |
| IEC status | DGFT may flag or suspend your IEC, blocking new export shipments |
| Bank facilities | AD banks may decline new packing credit, post-shipment finance, or LCs |
| Customs clearance | Some customs ports add additional scrutiny to shipments from caution-listed IECs |
| Reputation | The caution list is shared across all AD banks. Switching banks does not help |
How to get removed from the caution list
- Close all overdue EDPMS entries. Either by matching receipts, processing write-offs, or obtaining RBI extensions.
- Submit a closure confirmation request through your AD bank, with a list of all previously open entries and their current status (closed, written off, or extended).
- The AD bank reports the closure to the RBI. Removal from the caution list typically takes 30. 60 days after all entries are resolved.
- Prevent recurrence by setting up a monthly EDPMS review process. Do not let entries age past 6 months without action.
Currency Conversion Discrepancies
The shipping bill records the FOB value in the invoice currency (usually USD), while the bank receipt is converted to INR at the prevailing exchange rate on the date of credit. EDPMS compares values in foreign currency, but discrepancies arise when the buyer pays in a different currency than invoiced (e.g., paying in EUR for a USD invoice), or when the exchange rate used by the correspondent bank differs from the RBI reference rate.
Another common scenario: the buyer's bank converts USD to the buyer's local currency and back to USD at slightly different rates during the SWIFT transfer, resulting in a net receipt that is