EDPMS vs IDPMS: RBI's Export and Import Monitoring Systems Explained

If you export IT or services from India, EDPMS is the RBI system that decides whether your export is marked as paid or left flagged as outstanding. Get it wrong and future export paperwork, and even GST refunds, can stall. Get it right and you rarely notice it exists.

Here is the short answer. EDPMS (Export Data Processing and Monitoring System) tracks whether export earnings actually come back to India. IDPMS (Import Data Processing and Monitoring System) tracks whether import payments are backed by real goods coming in. Same design, opposite directions. As a services exporter you live almost entirely in EDPMS, usually entering it through your SOFTEX filing rather than a shipping bill.

Both are Reserve Bank of India (RBI) platforms that operate under FEMA, the Foreign Exchange Management Act. Both match a customs record to a bank remittance so nothing slips through, which is why getting paid on time and reported correctly is a compliance step, not just a cash-flow one. It ties directly into the realisation and repatriation of export proceeds rules.

The table below sets the two systems side by side, with the detail underneath.

EDPMS, the Export Data Processing and Monitoring System, is an RBI platform that records every export from India and follows it until the payment is received and reported. It is the central scoreboard for export realisation.

The entry is created at the point of export. For goods, that is the Shipping Bill from Customs. For software and services, it is the SOFTEX form, which is why the softex vs shipping bill choice matters to exporters. Your bank, an Authorised Dealer (AD bank), then updates the entry when your foreign payment arrives and is matched to it.

An export that is shipped or filed but not marked as paid shows up as an outstanding entry, which is a compliance flag against your business. That flag is what most exporters are trying to avoid, often without realising the system behind it. For a full walkthrough, see the EDPMS compliance guide for exporters.

IDPMS, the Import Data Processing and Monitoring System, is the mirror image. It records imports into India and follows them until the payment abroad is matched to genuine goods arriving.

Here the customs record is the Bill of Entry, generated when goods clear Customs. Your AD bank links it to the outward remittance you send the supplier, so every payment leaving the country is backed by a real import.

The purpose is the reverse of EDPMS. Instead of checking that money comes in, IDPMS checks that money going out is genuine, which stops foreign exchange leaving India against fake or non-existent shipments.

Example: A Pune hardware firm pays a Taiwanese supplier $40,000 for components. When the goods clear Customs, the Bill of Entry enters IDPMS, and the bank ties it to that outward payment. Until the two match, the remittance stays open, the same way an unrealised export sits open in EDPMS.

The two systems share one design and split on direction. Reading them as a pair makes each easier to remember.

• EDPMS answers the RBI's export question: did the foreign currency for this shipment or SOFTEX actually come back to India, on time?
• IDPMS answers the RBI's import question: did real goods arrive in India for this payment we sent abroad?
• Both link a customs document to a bank remittance, so the money trail and the goods trail always have to match.
• Which applies to you depends on trade direction: sell abroad and you are in EDPMS, buy from abroad and IDPMS applies to those purchases.

For a pure services exporter with no imports, IDPMS is background knowledge and EDPMS is the system you actually deal with.

The systems are not just record-keepers. They enforce deadlines, and a missed one creates real friction with your bank.

For EDPMS, export proceeds must be realised and repatriated within 9 months of the shipment or export. This period reverted to 9 months for exports made on or after 5 June 2026, having been temporarily longer, so confirm the rule for your specific shipment date. The RBI can grant extensions on valid grounds, and once proceeds are realised the record also supports your bank realisation certificate explained.

For IDPMS, you must submit evidence of import, chiefly the Bill of Entry, to your AD bank within the prescribed window after paying, so the outward remittance can be closed against real goods.

Example: A Bengaluru software firm files a SOFTEX in July and invoices a US client $30,000. Under the 9-month rule, that payment needs to reach India and be reported against the SOFTEX entry by the following April.

If it is realised in September and correctly matched, EDPMS closes the entry quietly. If the client pays but the receipt is never linked to the entry, EDPMS still shows it outstanding, even though the money arrived.

For most IT and services exporters, EDPMS is a background process that only becomes visible when something breaks. Keeping it clean comes down to a few habits.

• File your SOFTEX or export declartion form correctly, so the entry is created accurately from the start rather than needing corrections later.
• Realise proceeds within the window, and make sure the inward remittance is reported against the right export entry, not left floating.
• Apply the correct purpose code to each receipt, since a wrong code can leave the entry unmatched. The RBI purpose code for inward remittance guide explains how to pick it, and most software work falls under purpose code P0802.
• Give your bank the payment proof it needs, chiefly the FIRA, so old entries are matched and closed rather than sitting open. Knowing how FIRC works with Vostro payments helps when the money arrives via a partner bank.

An outstanding EDPMS entry can hold up future export documentation and related processes, including GST refunds that follow the export of services under GST rules, so it pays to keep the record current.

The hard part of EDPMS is rarely the rule. It is the paperwork that proves you followed it: money arriving on time, against the right entry, with the right purpose code and proper documentation. Missing pieces are what leave entries outstanding.

Xflow's platform is built for the receiving side of exactly this problem:

• Faster realisation: payments settle to your Indian bank account, typically the next business day, so proceeds arrive well inside the 9-month window instead of drifting through slow correspondent banking.
• Correct documentation: the eFIRA and payment advice are auto-issued, giving your AD bank what it needs to match and close the EDPMS entry.
• Right purpose codes: the correct purpose code is applied to each receipt, reducing the unmatched entries that trigger outstanding flags.

Xflow holds final RBI PA-CB authorisation for both exports and imports, as of February 2026, so it sits properly inside the FEMA framework that EDPMS and IDPMS enforce. See how receiving accounts handle the inward leg.

EDPMS and IDPMS are the same monitoring idea pointed in opposite directions.

• EDPMS watches export money coming back to India, and every Indian exporter must keep it clean by realising proceeds on time and reporting them correctly.
• IDPMS watches import payments going out, and it applies only when you buy from abroad.

Treat EDPMS as a discipline rather than a hurdle. Get paid on time, with clean documentation and the right purpose code, and the system stays quiet.