What Is Export Payment Reconciliation in Tally?

Export payment reconciliation in Tally is the process of matching your recorded export sales invoices against the actual INR amount credited by the bank. It accounts for forex fluctuations, bank charges, and compliance documents like the electronic Bank Realisation Certificate (e-BRC) and the Foreign Inward Remittance Certificate (FIRC).

After a foreign client pays a USD invoice, the INR credited to your bank account almost never equals the INR value booked at the time of invoicing. Reconciliation is what closes that gap in your books.

Here's how it plays out. A Bengaluru software exporter raises an invoice for $3,000 at a booked rate of ₹82.50/USD, which is ₹2,47,500. The bank credits ₹2,49,600 because the rate on settlement day is ₹83.20/USD. Reconciliation records that ₹2,100 difference and ties the bank credit back to the original invoice.

Why Export Payment Reconciliation Matters?

Export payment reconciliation matters because the amount credited to your bank account when an international client pays an export invoice rarely matches the exact invoice value, and each mismatch has a specific cause that must be recorded separately in Tally. The causes are bank charges, exchange rate differences, agreed deductions or discounts, and partial payments.

If these differences aren't recorded correctly, Tally's bank reconciliation will show unexplained mismatches. These flag during CA audits and can delay FEMA compliance submissions.

What Documents Do You Need Before You Start Reconciling in Tally?

The <a href="https://www.skydo.com/blog/export-documents-attestation">documents</a> you need before reconciling export payments in Tally fall into two categories. For bank reconciliation, you need updated Tally books, the official bank statement, and the previous reconciliation or opening BRS. For GST reconciliation (GSTR-1, GSTR-3B, or GSTR-2B), you need your sales and purchase data from the books of accounts, GST portal returns or JSON files, and credit and debit notes.

For GST Reconciliation (GSTR-1, GSTR-3B, or GSTR-2B)

How Export Reconciliation Works in Tally? A Step-by-Step Guide

Export reconciliation in Tally works by matching recorded export sales invoices, zero-rated GST data, shipping bills, port codes, and <a href="https://www.skydo.com/blog/export-realisation-guide">bank realisations</a> (e-BRC/FIRC) against GST portal data and bank records. The goal is to confirm zero-rated or Letter of Undertaking (LUT) compliance and close every open invoice in the books. You do it in four steps: record and verify the export invoices, review the GSTR-1 export data, export the return file for portal matching, and reconcile the bank realisation.

Step 1: Record and Verify Export Invoices

Exports are <a href="https://www.skydo.com/blog/export-of-services-under-gst">zero-rated supplies under GST</a>. No tax is charged on the transaction, but exporters can claim input tax credit on purchases made for export production.

If your business has filed a Letter of Undertaking (LUT), it can export without paying IGST. This must be reflected in the voucher type selection.

Step 2: Access and Review the GSTR-1 Export Data (Table 6A)

Step 3: Export the Return File for Portal Matching

Step 4: Reconcile Bank Realization (e-BRC / FIRC)

What You Need for Complete Export Payment Reconciliation in Tally

How Does Skydo Help Receive International Payments?

Traditional SWIFT wires come with heavy paperwork, unpredictable bank charges, and delayed documentation, and all of these directly slow down Tally reconciliation. <a href="https://www.skydo.com/">Skydo</a> helps Indian exporters receive international payments by acting as a <a href="https://www.skydo.com/blog/cross-border-payments">cross-border payment processing layer</a> that removes those three problems.

The core problem Skydo solves is cost you can't predict. Banks and services like PayPal charge up to 8% in hidden fees. Skydo charges a flat $19 under $2,000 and a flat $29 from $2,000 to $10,000, and 0.3% over $10,000. That makes the credited INR amount predictable before the payment even arrives, which removes one of the biggest variables in export reconciliation.

large_Proforma invoice vs quoation

medium_Proforma invoice vs quoation

small_Proforma invoice vs quoation

thumbnail_Proforma invoice vs quoation

Proforma invoice vs quoation

What Is Export Payment Reconciliation in Oracle NetSuite?

Export payment reconciliation in Oracle NetSuite is the process of matching international payment transactions recorded in your bank or payment gateway against the corresponding entries in your NetSuite general ledger (GL), so that your financial statements reflect accurate, verified balances.

For Indian exporters, the process confirms that every <a href="https://www.skydo.com/blog/export-realisation-guide">inward foreign remittance</a> received against an export invoice is correctly recorded, accounted for in the right currency, and supported by the required compliance documentation, such as a Foreign Inward Remittance Certificate (FIRC).

Here is an example. A Bengaluru-based software exporter raises an invoice for $5,000, and the client pays via SWIFT. After correspondent bank deductions, the amount credited to the bank is $4,963. Reconciliation in NetSuite is how the exporter traces, matches, and books that $4,963 against the original $5,000 invoice, and accounts for the $37 gap.

Export payment reconciliation matters because the amount an international client pays rarely equals the amount credited to your bank account, and every gap must be identified, explained, and correctly booked in NetSuite. The gaps come from four sources: bank charges, exchange rate differences, agreed deductions or discounts, and partial payments.

For Indian exporters, unreconciled export payments also create downstream compliance risk. Pending FIRC documentation, unmatched shipping bills, and open EDPMS entries can all result in regulatory scrutiny.

What Documents Do You Need Before You Start Reconciling in Oracle NetSuite?

Before you start reconciling in Oracle NetSuite, you need four things: an official bank or credit card statement, importable bank data files, prior reconciliation records, and <a href="https://www.skydo.com/blog/export-documents-attestation">supporting source documentation</a> such as trial balances, vendor bills, customer invoices, and payment receipts.

How Export Reconciliation Works in Oracle NetSuite? A Step-by-Step Guide

Export reconciliation in Oracle NetSuite works through the Bank Feeds or Advanced Bank Reconciliation modules, matching external bank or gateway transactions against your internal GL records in six steps. You export data from your financial institution, import the file, run automated matching rules, manually match what remains, review and submit, and then complete the Reconcile Statement screen.

Step 1: Export Data from Your Financial Institution

Step 4: Manually Match Remaining Transactions

Step 6: Complete the Reconcile Statement Screen

The $37 gap is posted as a bank charge expense. The exchange rate difference between the invoice date and the credit date is posted as a realised forex gain or loss. The reconciliation is complete only when all three figures (invoice amount, bank receipt, and booked INR amount) are accounted for and the NetSuite difference reads zero.

Here is how the three approaches to reconciling <a href="https://www.skydo.com/blog/cross-border-payments">cross-border payments</a> compare.

Gaps in NetSuite reconciliation start upstream, with unpredictable bank charges, missing remittance data, and delayed documentation. <a href="https://www.skydo.com/">Skydo</a> helps Indian exporters receive international payments cleanly by acting as a cross-border payment processing layer that eliminates all three.

Tax on Foreign Income: What Indian Freelancers Need to Know (2025)

large_Tax on Foreign Income: What Indian Freelancers Need to Know (2025)

medium_Tax on Foreign Income: What Indian Freelancers Need to Know (2025)

small_Tax on Foreign Income: What Indian Freelancers Need to Know (2025)

thumbnail_Tax on Foreign Income: What Indian Freelancers Need to Know (2025)

What Is Export Payment Reconciliation in Microsoft Dynamics?

Export payment reconciliation in Microsoft Dynamics is the process of matching the foreign currency payments you receive from international clients against the corresponding export invoices recorded in your ERP. It confirms that every inward remittance is accounted for in the correct amount, currency, and period.

For Indian exporters, the need is practical. When a foreign buyer pays a USD invoice via SWIFT wire, the amount that hits your Indian bank account in INR rarely equals the invoiced value. Reconciliation inside Dynamics is the step that explains and closes that gap officially in your books.

Take a Pune-based IT services firm that raises a USD 10,000 invoice. By the time the payment clears, the bank credits the INR equivalent of USD 9,940 after deducting SWIFT charges and applying its own conversion rate. Reconciliation in Dynamics records both the expected USD 10,000 and the actual net receipt, posts the difference correctly, and closes the customer ledger entry.

Export payment reconciliation matters because the amount credited to your bank account for an international invoice almost never matches the original invoice value, and every gap must be explained and documented in your books. The gap comes from intermediary bank charges, exchange rate differences, agreed deductions, or partial payments. Leaving it unreconciled affects <a href="https://www.skydo.com/blog/fira-gst-refund-saas-exporters-india">GST refund claims</a>, FEMA reporting timelines, and the validity of your Foreign Inward Remittance Certificate (FIRC)/BIRC as proof of inward remittance.

The credited amount can differ from the invoice for 4 reasons:

Export payments in Dynamics often show a mismatch because your bank deducted SWIFT charges before crediting, so reconcile net receipt against gross invoice separately.

For Indian exporters, unreconciled export payments carry compliance consequences beyond accounting accuracy. Mismatches affect GST refund claims, because export invoices must be matched to realized payments. They also affect FEMA reporting timelines and the validity of your FIRC/BIRC as proof of inward remittance.

An unreconciled open entry in Dynamics, even a small INR difference from a SWIFT deduction, keeps the customer ledger entry open. That distorts your Accounts Receivable (AR) aging reports and makes it harder to demonstrate full <a href="https://www.skydo.com/blog/export-realisation-guide">export realization</a> to your bank or auditor.

What Documents Do You Need Before You Start Reconciling in Microsoft Dynamics?

Before you start reconciling in Microsoft Dynamics, gather the official bank statement, an electronic bank statement file (if you are using Advanced Bank Reconciliation), undeposited receipts or cashier reports, the prior reconciliation report, and an outstanding checks and deposits list. You also need two pieces of system data: the last reconciled date and ending balance, and confirmation that all transaction batches are fully posted.

For SWIFT receipts, request your bank's MT940 or CAMT.053 file format. It imports directly into Dynamics Advanced Bank Reconciliation and auto-maps transaction references, reducing manual matching time significantly.

Two pieces of system data need to be in place before you start:

How Export Reconciliation Works in Microsoft Dynamics? A Step-by-Step Guide

Export reconciliation in Microsoft Dynamics works in 4 phases: configuring the data export setup, running the ledger or bank statement export, pulling bank statement entities via the Data Management workspace, and reviewing and finalizing the reconciliation audit trail.

Phase 1: Configuring the Data Export Setup

Phase 2: Exporting Reconciliation and Ledger Files

Phase 3: Exporting Bank Statement Entities via Data Management Workspace

Use this phase when you are doing bank-to-ERP reconciliation via spreadsheet models. You can pull bank statement header and line entities directly from Dynamics.

Phase 4: Reviewing and Finalizing the Reconciliation Audit Trail

Once extracted, the data is reviewed externally or matched back in Dynamics for validation via the Account Reconciliation Workspace.

SWIFT deductions, hidden intermediary charges, and delayed bank feeds all originate at the payment receipt stage, and they are what produce the mismatches you reconcile in Dynamics. <a href="https://www.skydo.com/">Skydo</a> helps Indian exporters receive international payments by acting as a cross-border payment processing layer that removes the heavy paperwork, unpredictable bank charges, and delayed documentation associated with traditional SWIFT wires.

Skydo declares its fee upfront, before you transact, so the amount credited to your account is exactly what you expect to see when you open Dynamics. The fee depends on the amount received:

There are no hidden deductions, no mid-chain surprises, and no open entries to chase.

large_Gig economy in India

medium_Gig economy in India

small_Gig economy in India

thumbnail_Gig economy in India

Gig economy in India

What Is EDPMS and Why Do Open Entries Matter?

EDPMS (Export Data Processing and Monitoring System) is an RBI-mandated digital platform that tracks every export transaction from the moment a Shipping Bill is filed at Customs through to realization of payment in your Indian bank account. Open entries matter because an entry stays open, and so does your compliance obligation, until the remittance is matched to its Shipping Bill and the electronic Bank Realisation Certificate (eBRC) is issued.

At its core,<a href="https://www.skydo.com/blog/understanding-edpms-full-form-and-its-essential-role-in-export-management">EDPMS</a> links the inward remittance from your foreign buyer to the specific Shipping Bill filed at Customs. Once the AD bank confirms that match in EDPMS, the data is transmitted to the DGFT portal, which then generates the eBRC.

Say a Bengaluru textile exporter ships goods worth $5,000 to a buyer in Germany. The moment Customs processes the Shipping Bill, an EDPMS entry is created. Until the $5,000 arrives, the Authorised Dealer (AD) bank matches it to that Shipping Bill, and the eBRC is issued, the entry stays open.

Why Do EDPMS Entries Stay Open or Pending?

EDPMS entries stay open or pending for these reasons: delayed or partial payment from the overseas buyer, mismatched invoice values between the Shipping Bill and the remittance received, purpose code errors on the inward remittance that stop the bank's system from auto-matching it to the export, missing or delayed eBRC submission, multiple Shipping Bills being settled against a single remittance (which requires manual linking), and no one internally owning the reconciliation.

Receiving export proceeds does not auto-close an EDPMS entry. The remittance must be matched, and the AD bank must update or close the entry after completing its genuineness check. Money arriving does not mean the entry has closed.

Even after the money has arrived, a purpose code error is often what keeps an entry open.

Ownership is the last gap. Finance teams often assume the bank or the CA is tracking open entries, and the bank assumes you are on top of it. The result is that nobody is, and entries accumulate silently.

Most exporters only discover an entry is stuck when the bank flags it during a routine review, or when an EPCG or RoDTEP claim gets blocked because of the open entry. Unresolved entries compound quietly, so by the time a bank formally raises the issue, you can be looking at months or years of backlog rather than one clean fix.

Timing adds pressure. Entries open within the prescribed period (currently 9 months from the shipment date for most exports) are treated as in-process. Beyond that, the AD bank is required to follow up and may report the entry as overdue. Extended non-realization risks flagging to the RBI caution list, which can block future export transactions and deny export incentives.

What Happens to Open EDPMS Entries When You Switch AD Banks?

When you switch AD banks, your open EDPMS entries do not automatically migrate, close, or transfer. They stay linked to the original Shipping Bill and the AD code registered at the time of export, so opening an account at a new bank gives that bank no visibility into or responsibility for them.

The new AD bank has to be formally registered as the Authorised Dealer for those open Shipping Bill entries before it can act on them. Until that handoff happens, the entries remain the responsibility of the outgoing bank, even if your account there is dormant or closed.

The outgoing and incoming banks must coordinate. The incoming bank picks up responsibility for the open Shipping Bill entries, and a formal internal communication between the banks triggers that handoff, so your word alone is not enough.

This creates a specific risk mid-transition. If you close your old bank account before the open entries have been formally transferred, the new AD bank may refuse to accept responsibility, leaving those entries orphaned in the system and potentially FEMA-flagged.

How Do You Transfer Open EDPMS Entries to Your New AD Bank?

To transfer open EDPMS entries to your new AD bank, you audit every open entry on ICEGATE, obtain a No Objection Certificate (NOC) from the outgoing bank, submit Shipping Bill-wise details to the new bank, confirm the new bank acknowledges responsibility within its own system, and verify on ICEGATE that the entries now reflect the new bank. The steps run in this order.

What Documents Do You Need When Switching AD Banks for EDPMS?

Switching AD banks for EDPMS involves eight documents: the NOC from the outgoing bank, a Shipping Bill-wise list of open EDPMS entries, a copy of each open Shipping Bill, the invoice for each, the IRM or Foreign Inward Remittance Certificate (FIRC) for payments already received but unmatched, an eBRC status confirmation, a written transfer letter from you to both banks, and the AD code registration documents for the new bank. The table shows who needs each one.

What Are the FEMA Compliance Risks During a Bank Switch?

The FEMA compliance risks of an AD bank switch are orphaned entries (entries with no AD bank formally responsible for them), entries reported as overdue because the transition gap pushed them past the prescribed realization period, and potential caution listing if entries stay unresolved for an extended period.

The prescribed period for realization of export proceeds is currently 9 months from the date of shipment for most exports. If a bank-switch transition delays matching or closure and pushes an entry past that window, the AD bank is required to report it as overdue, even if the delay was administrative.

The scenario most likely to result in FEMA non-compliance is a premature account closure. If you close the old account before the entries are formally transferred, no AD bank is responsible for following up on those entries with RBI. The risk comes from that gap. The switch itself is not a FEMA violation, and the violation happens when no AD bank is formally responsible for an open entry.

Prior to October 2026, the RBI maintained a "caution list" for exporters with unrealized payments exceeding 2 years. Under the new FEMA 2026 regulations, this has been replaced by a revised compliance framework. Now, if your export proceeds remain unrealized beyond 1 year, your AD bank may restrict you to exporting only against 100% advance payments or irrevocable Letters of Credit.

Whether you are dealing with a legacy caution list flag or the new 2026 restrictions, persistent open entries even from an administrative bank-switch gap will trigger these consequences:

What Did FEMA Export Regulations 2026 Change for Open EDPMS Entries?

The FEMA Export and Import Regulations 2026, effective 1 October 2026, made three changes relevant to open EDPMS entries, including during a bank transition. They replaced the earlier caution listing mechanism with a revised compliance framework, extended the small-value self-declaration route for closing entries at or below ₹10 lakh, and changed the EDPMS timelines for realizing export proceeds and closing entries.

Entries that were already overdue under the old framework but fall within the new 2026 timeline parameters may have a different compliance status after October 2026. Confirm this with the new AD bank before assuming an entry is flagged.

FEMA 2026 did not eliminate compliance obligations for old open entries. It changed the framework that governs them, so every open entry needs to be reviewed against the new rules, including those created before October 2026.

How Does Skydo Help Exporters Managing an AD Bank Switch?

One of the most time-consuming tasks in an AD bank switch is gathering proof of every inward remittance, meaning FIRC or eBRC-equivalent documentation, to present to the incoming bank for each open Shipping Bill. <a href="https://www.skydo.com/">Skydo</a> is built to take that chase off your plate.

large_Vostro Accounts 

medium_Vostro Accounts 

small_Vostro Accounts 

thumbnail_Vostro Accounts 

Vostro Accounts 

What Are Export Documents Required for Audit?

Export documents required for audit are the set of records an Indian exporter must maintain and present when a regulatory authority (customs, GST, income tax, or RBI/FEMA) examines their export transactions for compliance.

These documents are your evidence that you declared goods or services correctly, charged the right taxes or claimed the right exemptions, received payment in foreign exchange, and met RBI reporting requirements.

Take a Pune-based software exporter invoicing a US client $5,000. If any of the four regulatory frameworks audits that transaction, the exporter must produce the <a href="https://www.skydo.com/blog/what-is-export-invoice">export invoice</a>, a Letter of Undertaking (LUT) under GST, bank remittance records, and a Foreign Inward Remittance Certificate (FIRC) or Bank Inward Remittance Certificate (BIRC). One document is not enough. The full chain is what an auditor asks for.

Which Types of Audits Can an Indian Exporter Face?

An Indian exporter can face four distinct types of audits: a Customs Audit, a GST Audit, an Income Tax Audit and a FEMA/RBI Compliance Review. Each is conducted by a different authority, checks different documents and has its own trigger, so you need to keep the right paperwork for all four.

What Documents Are Required for a Customs Audit?

A customs audit requires you to produce documents showing that the shipment details, declared value and nature of goods match what was actually exported. The core set is the shipping bill, commercial invoice, packing list, Bill of Lading or Airway Bill, and ARE-1 form, and the Customs Audit Regulations, 2018 require you to preserve them for a minimum of 5 years from the date of export.

Missing even one document from this chain can trigger penalties during a customs audit. A shipping bill that does not reconcile with the commercial invoice is one example.

What Documents Do You Need for a GST Audit as an Exporter?

For a GST audit, you need records that prove your exports were made under the <a href="https://www.skydo.com/blog/export-of-services-under-gst">correct GST treatment</a>, either zero-rated with a LUT/Bond or with IGST paid and subsequently refunded. The core documents are your GSTR-1 and GSTR-3B returns, the LUT or Export Bond, export invoices, refund claim records (Form RFD-01) and, for service exporters, a FIRC/BIRC. GST records must be maintained for 6 years from the due date of the annual return for the relevant year.

Which Documents Are Needed for an Income Tax Audit?

An income tax audit for an exporter requires financial records that verify total receipts, allowable deductions and foreign income, filed in the prescribed forms under Section 44AB of the Income Tax Act. The core documents are audited financial statements, Form 3CA/3CB and Form 3CD, books of accounts, foreign remittance records and, if applicable, TDS/TCS records. Books of accounts must be maintained for 8 years from the end of the relevant assessment year.

Section 44AB requires a tax audit if your total gross receipts exceed ₹1 crore in a financial year for business, or ₹50 lakh for professional services. The threshold applies to total receipts, not just export income, so all receipts count toward it. Service exporters should not assume their foreign income is exempt from tax audit scrutiny.

What Proof of Payment Documents Are Required for FEMA Compliance?

For FEMA compliance, you need documents that prove foreign exchange was received in India within the prescribed time period and reported correctly to the authorised dealer bank. The primary proof of payment documents are the FIRC or BIRC, the bank remittance advice or SWIFT confirmation, the purpose code declaration and EDPMS closure proof, and they should be preserved for at least 5 years.

The 5-year retention matters because customs auditors, under the 2018 Regulations, can request payment evidence alongside shipment records.

If you receive international payments through <a href="https://www.skydo.com/">Skydo</a>, a FIRC/BIRC is automatically issued per transaction and stored digitally, so you don't need to chase your bank before an audit.

Pre-Audit Export Document Checklist for Indian Exporters

A pre-audit export document checklist for Indian exporters covers 10 categories of records that must be complete, correctly dated and immediately accessible before an auditor arrives: shipping bills, commercial invoices, packing lists, Bill of Lading or Airway Bill, LUT or Export Bond, GSTR-1 and GSTR-3B returns, FIRC/BIRC, EDPMS closure records, audited financial statements with Form 3CA/3CB and 3CD, and purpose code records.

Run through this list at least 30 days before a scheduled audit or year-end. Gaps in any one category can delay your response to an auditor's notice.

How Does Skydo Help You Stay Audit-Ready for Export Payments?

The payment side of an audit comes down to one question: can you produce a proper FIRC or BIRC for every transaction? FEMA auditors require one per transaction, and a bank statement alone does not satisfy them. Waiting on a bank RM to dig those certificates out right before an audit is the problem Skydo is built to remove.

<a href="https://www.skydo.com/">Skydo</a> helps Indian exporters stay audit-ready for payment-related compliance by automatically generating and storing FIRC/BIRC certificates for every international payment received. Every inward remittance processed through Skydo comes with an auto-generated FIRC/BIRC, issued per transaction and available digitally at any time.

Setup takes 10–15 minutes. Virtual accounts are available in USD, EUR, GBP, SGD, AUD and CAD, all free of cost.

What Is EDPMS and What Does an Open EDPMS Entry Mean?

The Export Data Processing and Monitoring System (EDPMS) is the RBI's online platform, launched in March 2014, that tracks every export from India and monitors whether payment for it has been received within the allowed time. An open EDPMS entry means that payment has not yet been confirmed and matched to the export.

Two documents drive the <a href="https://www.skydo.com/blog/understanding-edpms-full-form-and-its-essential-role-in-export-management">lifecycle of an EDPMS entry</a>. The shipping bill (for goods) or SOFTEX form (for services) opens the entry, and your AD bank closes it once it confirms that payment has been received and matched.

Say a Mumbai exporter ships goods and the shipping bill is filed at customs. An entry opens in EDPMS immediately. Until the exporter's bank confirms that the inward remittance matches that shipping bill, the regulator considers the export unfinished business.

Why Is Your EDPMS Entry Still Open After Payment?

The most common reason an EDPMS entry stays open after payment is that no one connected the inward remittance to the specific shipping bill: the money arrived, but the bank was never told which bill it settles. Other causes include a short payment, a wrong purpose code, one remittance covering several shipping bills, a payment that has not arrived, an export advance with no completed export, a missing or delayed eBRC (Bank Realisation Certificate), and nobody owning the reconciliation. Money reaching your account does not close the entry on its own, because the bank must match the remittance to the specific shipping bill using your instructions and documents.

Before calling your AD bank, run through these five questions:

How Does EDPMS Closure Actually Work, Who Does What?

EDPMS closure works through four stages: reconciliation, root-cause correction, eBRC alignment, and a formal closure request to the AD bank. The bank must sign off directly, so you cannot close an entry unilaterally.

Your role is to supply the correct reference details and documentation: the right documents, a written remittance mapping, and the eBRC. The AD bank's role is to perform the actual match and mark the entry closed in the system. The bank can't close anything until it has what you supply, so closure is not a bank-only action.

Automating the match speeds up closures and unlocks any linked export benefits. The cleaner and better-referenced the incoming payment documentation, the fewer entries get stuck.

How to Close a Stuck EDPMS Entry: Three Distinct Routes

There are three distinct routes to close a stuck EDPMS entry: standard realisation, the ₹10 lakh self-declaration route, and the write-off route. There is no single closure process, so the right path depends on the entry value, whether payment was received, and whether the export actually happened.

Route 1: Standard Realisation (the Ordinary Route)

The bank marks the entry closed once it has confirmed that the export value has been realised and matched. You need these documents:

The typical timeline after proper document submission is 1–3 working days.

Route 2: ₹10 Lakh Self-Declaration (for Small-Value Entries)

Route 3: Write-Off (Where Realisation Is Not Possible)

Where no export was made and refunding an advance is not possible, or where the outstanding amount cannot be recovered, the bank may, on your request, allow the entry to be written off under applicable RBI guidelines.

What Happens If Your EDPMS Entry Stays Open Too Long?

If your EDPMS entry stays open past the 9-month realisation deadline (15 months for project exports), your name can be added to the RBI caution list, which blocks future export credit and banking relationships. The consequences compound over time rather than arriving at a single cutoff.

The practical risk is not one open entry. Unresolved entries accumulate quietly, and by the time the bank raises the issue formally, a finance team can be looking at months or years of backlog rather than one clean fix.

An exporter on the caution list may also find EPCG claims, RoDTEP benefits, or export credit lines affected while entries remain unresolved.

Under the Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026 (effective 1 October 2026), the caution listing framework has been updated. Check the latest RBI FEMA Export-Import Regulations for the revised compliance framework replacing the earlier caution-listing mechanism.

How to Check Your EDPMS Pending List and Entry Status

You have two practical ways to check your EDPMS pending list and entry status: use the ICEGATE portal, or request a statement directly from your AD bank.

Most businesses do not find out an entry is stuck until the bank flags it during a routine review, or a claim gets blocked. Requesting a periodic statement from your AD bank is the simplest way to stay ahead.

Entries show as pending on the list for these reasons:

Does Skydo Help Close EDPMS Entries Faster?

The manual documentation burden is the primary cause of stuck EDPMS entries, and it gets heavier when payment arrives through a non-bank channel or payment aggregator, because your AD bank may not automatically know which shipping bill the remittance settles. Yes, <a href="https://www.skydo.com/">Skydo</a> helps Indian exporters and businesses receiving international payments reduce that burden.

Pricing is flat and predictable for transactions up to $10,000, and a percentage above that. There are no monthly fees, and you pay only when you transact.

Proforma Invoice: Meaning, Format And Template

large_Proforma Invoice: Meaning, Format And Template

medium_Proforma Invoice: Meaning, Format And Template

small_Proforma Invoice: Meaning, Format And Template

thumbnail_Proforma Invoice: Meaning, Format And Template

What Is EDPMS and Why Does It Matter for Exporters?

EDPMS (<a href="https://www.skydo.com/blog/understanding-edpms-full-form-and-its-essential-role-in-export-management">Export Data Processing and Monitoring System</a>) is RBI's centralised system for tracking export declarations and ensuring that foreign exchange from exports is repatriated to India within the stipulated timeline. For you as an exporter, it is the live record that links every export shipment or service declaration to its corresponding inward payment.

Until that link is made, the entry stays open and you remain in a compliance grey zone.

Here is how it plays out. A Bengaluru-based software exporter invoices a US client for $5,000. The moment the payment is received by their Authorised Dealer (AD) bank and matched to the export declaration, the EDPMS entry is marked closed, confirming the foreign exchange has been repatriated.

EDPMS closure is the process by which your AD bank marks an open export entry as settled after confirming that the export proceeds have been received and credited. The entry stays open until an inward remittance is matched against it.

The export declaration comes first. It is a shipping bill for goods or an Export Declaration Form (EDF) for services, and it appears in EDPMS as an open entry. When proceeds are realised, the AD bank reports the realisation in EDPMS and, per RBI's directive (A.P. DIR Series Circular No. 04, dated September 15, 2017), updates the system on an as-and-when-realised basis.

Before crediting your account, the AD bank must satisfy itself about the genuineness of the transaction. It then updates or closes the EDPMS entry accordingly.

The complete transaction trail the AD bank relies on for closure runs in this order:

A closed EDPMS entry is also the trigger for Electronic Bank Realisation Certificate (eBRC) generation. From the effective date in the eBRC circular, AD banks generate eBRCs directly from EDPMS data for consistency.

If your export documents go to a bank other than the one originally declared, EDPMS supports AD transfer requests. Ask your bank how transfers are handled in practice. For service exports, the <a href="https://www.skydo.com/blog/softex-form-guide-indian-exporters">SOFTEX form guide</a> is a useful companion to the EDF process described here.

Does a Payment Platform Affect Your EDPMS Closure?

No, using a payment platform does not block or delay EDPMS closure, provided the platform routes the funds correctly to your Indian AD bank and issues the right documentation. What matters to the AD bank is that the inward remittance arrives, that it carries the correct purpose code matching the original export entry, and that a Foreign Inward Remittance Certificate (FIRC) or FIRA is available as remittance evidence.

EDPMS closure is triggered at the AD bank level, when an inward remittance is matched to an open export entry. A <a href="https://www.skydo.com/blog/eefc-account-vs-payment-platforms">payment platform</a> is simply the channel the foreign currency travels through before it reaches the AD bank. It does not sit inside the EDPMS system itself.

A platform that is RBI-authorised, meaning it holds a PA-CB licence or operates as an authorised payment aggregator, routes funds through the banking system in an EDPMS-compatible way. The remittance reaches the AD bank just as a direct SWIFT would, but via the platform's banking partner.

The risk comes from incomplete documentation. Closure fails in two situations:

In either case, the AD bank cannot close the EDPMS entry. Many exporters believe that if a platform receives the USD first, EDPMS closure cannot happen. In reality, closure is triggered by the AD bank crediting your account, not by who holds the funds in transit.

How Do Platform Payments Flow to Your AD Bank for EDPMS Closure?

When you use a platform, your client pays the platform in foreign currency, the platform receives the funds in its nodal/pooling account, and it routes the equivalent amount to your Indian AD bank account. Your AD bank receives the inward remittance, matches it to the open EDPMS export entry, and the entry is closed.

Only your AD bank can close the EDPMS entry, after it receives and matches the inward remittance. The platform does not close it.

Platform-Routed Payment vs. Direct SWIFT: What Changes for EDPMS?

The core compliance outcome is identical for both routes: the EDPMS entry is closed and the eBRC is generated, provided documentation is complete. The practical difference is convenience and speed. Platforms that settle in T+1 or T+2 and issue FIRC/FIRA automatically reduce your manual burden significantly compared to traditional SWIFT.

The table below compares the two routes across four dimensions: who initiates EDPMS closure, what documentation is issued, typical closure timeline, and manual steps required from you.

There is one risk specific to platforms. If a platform settles in INR without providing a FIRC or FIRA, your AD bank may not have sufficient documentation to close the EDPMS entry. Confirm your platform issues FIRC/FIRA per transaction before onboarding.

When you evaluate a platform for EDPMS compatibility, look at four factors:

Exporters choosing a platform need one that issues a free FIRC per transaction and routes with the correct purpose code. <a href="https://www.skydo.com/">Skydo</a> does both, with setup in 15 minutes.

How Does the EDF Mandate from October 2026 Affect EDPMS Closure via Platforms?

Growing Global

Staying Compliant blogs