Trade Policy
eBRC & FEMA 2026: What Changes for Banks and Exporters from 1 October 2026
If you are an Indian exporter, what will actually be different when your bank processes export transactions after 1 October 2026? FEMA 2026 shifts banks from “submit when asked” to “maintain clean, reconcilable transaction data” — and eBRC becomes the output of that system, not just a certificate.
What actually changes for your bank and your export transaction after 1 October 2026?
If you are an Indian exporter, what will actually be different when your bank processes and monitors your export transactions after 1 October 2026? The new FEMA (Export and Import of Goods and Services) Regulations, 2026 (Notification No. FEMA 23(R)/2026-RB dated 13 January 2026, RBI Press Release 16 Jan 2026) come into force on 1 October 2026, in supersession of the 2015 Regulations (Notification No. FEMA 23(R)/2015-RB). They are principle-based, unified for goods, services and software, and intended to promote ease of doing business for small exporters while empowering Authorised Dealers to provide quicker service.
The central shift for you as an exporter is from “submit documents when the bank asks” to “maintain clean, continuously reconcilable transaction data that the bank can verify.” The regulation requires it; bank behaviour will follow.
The old position → new position → what the bank has to do → what you will experience
| Regulatory change | Old position (2015 + circulars) | New position (2026, from 1 Oct 2026) | What the AD bank must do | What you as exporter will experience |
|---|---|---|---|---|
| Declaration | EDF for goods at Customs; SOFTEX for software via STPI/SEZ; no single form for services | Single unified Export Declaration Form (EDF) for goods, services and software. Goods: EDF at time of export (deemed submitted as part of shipping bill at EDI port). Services: EDF within 30 days from end of month of invoice (single EDF may cover a month); services other than software may file EDF on or before receipt of payment, with AD extension power. | Defined “specified authority” for EDF; services EDF reported in EDPMS within 5 working days of receipt | Software is now a service — no SOFTEX; one EDF workflow for goods and services; AD can extend EDF submission on reasonableness |
| Realisation period | 9 months generally, extended to 12, then to 15 months via 14 Nov 2025 amendment, then reverted to 9 months for interim 5 Jun–30 Sep 2026 via First Amendment 2026 | 9 months from shipment (goods) / invoice (services) / sale from warehouse; 12 months where export is invoiced/settled in INR (Sept 2026 amendment cut the Jan-2026 15/18-month text; Regulation 5) | Put in place systems to monitor and follow up on realisation within period; may extend period on exporter request if satisfied | Clean 9-month window (12 for INR) from 1 Oct 2026; earlier shipments keep their old bucket (see transitional note below) |
| Beyond one year outstanding | Caution-listing framework for unrealised exports | If proceeds remain outstanding beyond one year from due date/extended period without valid extension/write-off, further exports permitted only against full advance or irrevocable LC (EY summary of 2026 Regulations) | Must flag and enforce — will be more cautious with exceptions | A large outstanding may block the next open-account shipment |
| Reduction / write-off | Detailed categories, percentage caps, limited AD powers | AD may allow reduction in realisation on exporter request if satisfied; up to ₹10 lakh per shipping bill/invoice (goods) or invoice (services) may be closed on exporter declaration alone (Regulations 4 & 6) | Be more comfortable with small-value declared adjustments; still needs declaration and record | Small shortfalls (e.g., bank charges) can be closed on declaration without a file at RBI |
| EDPMS / reporting | EDPMS/IDPMS existed but fragmented across circulars; no uniform 5-day upload norm | All transactions must be reported in FETERS and EDPMS; AD must upload documents in EDPMS/IDPMS within 5 working days of receipt (KPMG comparison table) | More automated, more timely uploads; active monitoring obligation | Your bank’s EDPMS view will be fresher; mismatches surface faster |
| Set-off and third party | Complex, restricted | Set-off of export receivables vs import payables vs same overseas buyer/supplier or group/associate within realisation period; third-party receipts/payments allowed with AD approval (Regulations 7 & 8) | Verify genuineness, approve where satisfied, ensure EDPMS reporting | A single remittance covering multiple invoices, or a third-party payer, becomes explainable if documented for the bank |
What the law says vs what banks will likely do
The left three columns are what the regulation and directions actually require (RBI Notifications FEMA 23(R)/2026-RB, A.P. (DIR Series) Circular No. 20 dated 16 Jan 2026). The right two columns are likely operational behaviour — banks becoming more data-driven, proactive and exception-sensitive — based on the monitoring obligation in Regulation 5(2) and the 5-day EDPMS upload duty, not a direct quote from the regulation. Treat them as inferences to prepare for, not as guaranteed bank SOPs.
Is October 2026 a shift from “submit when asked” to “keep reconcilable data”?
Yes — that is the thesis to track against the law. The old world was document-submission on demand. The new world, via the monitoring duty in Regulation 5(2) and the 5-day upload in the directions, requires banks to maintain systems to monitor and follow up continuously. Your side of that is transaction-level reconciliation: the bank will be more comfortable with a clean chain and more likely to ask for an explanation where the chain breaks.
- More automated: EDPMS entries, IRMs and eBRCs are system-linked; status is visible to the bank without manual chase.
- More data-driven: EDF, shipping bill, invoice, IRM, eBRC, FETERS form one data set — consistency matters.
- More proactive: banks must follow up on outstanding entries within the period, not just at year-end.
- More comfortable with clean/reconciled: a matched IRM→eBRC→EDPMS chain closes without friction.
- More cautious with exceptions: partials, third-party receipts, buyer mismatches need a documented reason to close.
eBRC is increasingly the output of a reconciliation system — not just a certificate
Is eBRC increasingly becoming an output of an integrated export-data and reconciliation system rather than simply a certificate? Under the evolving DGFT–RBI–GSTN loop, yes. Banks upload Inward Remittance Messages (IRMs) to DGFT; you self-certify eBRCs on the DGFT portal by mapping IRMs to shipping bills/invoices; the DGFT eBRC is the proof that closes the loop for incentives and for FEMA realisation. Since 13 January 2026 (DGFT Public Notice 42/2025-26 amending Appendix 2U), every eBRC carries GSTIN, GST Invoice Number and GST Invoice Date, with QR validation on dgft.gov.in — linking GST returns, Customs and DGFT in one invoice-level loop.
- IRM: bank-generated notice of receipt of foreign exchange — sent electronically to DGFT; you cannot edit it, only map it.
- eBRC: your self-certification on DGFT (Services → eBRC → Generate e-BRC) that links an IRM to a shipping bill/invoice and purpose code — stored in DGFT repository, visible to banks/RAs.
- EDPMS: RBI’s central ledger where the AD files the EDF/shipping bill/invoice entry and later closes it against the IRM/eBRC realisation — now with a 5-day upload duty for the bank.
- DGFT–GSTN link: the GST invoice data in the eBRC lets authorities cross-check realisation vs zero-rated claim at invoice level — eBRC is now a GST-linked compliance instrument (Chartered Online, 22 Jan 2026).
DGFT Trade Notice 33/2023-24 piloted enhanced eBRC self-certification, and 12/2024-25 introduced bulk upload and API integration for IRM retrieval and eBRC generation. The direction is clear: IRMs flow automatically, you map them accurately, the system validates.
The real-world exporter experience — what happens when the data does not match?
An exporter receives $98,000 against a $100,000 invoice. Today, the question is not simply whether the money arrived. The bank also needs to understand what happened to the $2,000 difference — before it can update EDPMS and before you can generate a clean eBRC.
| Scenario | What the bank needs to verify | What you should do |
|---|---|---|
| Invoice $100,000 — payment $98,000 (short) | Whether the $2,000 is bank charges, forex difference, discount/commission, or short realisation — needs a reason to allow reduction under Regulation 6 | Provide bank advice showing charges, credit note, or discount agreement; if ≤₹10 lakh per invoice, a declaration may suffice |
| One remittance covers multiple invoices | Which IRM maps to which shipping bill/invoice for EDPMS closure and eBRC generation | Give the split — IRM X covers Invoice A $40,000 + Invoice B $60,000 — so the bank can allocate and you can generate two eBRCs |
| One invoice receives multiple payments | Partial realisations against the same shipping bill/invoice — each IRM must be mapped | Generate eBRCs incrementally as IRMs arrive; keep a running balance per invoice |
| Partial payment, balance outstanding | Whether the balance is still due within the 9-month window (12 for INR) or needs extension/reduction | Monitor the outstanding in EDPMS; seek AD extension before expiry if the buyer will still pay |
| Bank charges / forex difference | Deduction amount and reason — is it a handling fee or a commercial discount? | Provide the debit advice; if it is an agreed discount, keep the buyer’s acceptance |
| Payment from a third party (not the invoiced buyer) | Genuineness of third-party receipt and link to the export — allowed with AD approval under Regulation 8 | Provide buyer’s authorisation for third-party payment and the AD’s approval record |
| Buyer name ≠ remitter name | Whether the remitter is a group/associate company — needs link evidence | Provide group structure proof or buyer confirmation that the associate paid |
| Payment comes through another bank | Which AD holds the EDPMS entry vs which AD received the remittance — needs inter-bank coordination | Inform both ADs; the EDPMS-holding AD closes on the IRM from the other bank once verified |
| Proceeds remain outstanding | Whether the entry is within period, extended, or needs to be treated as unrealised — triggers the “further exports only on advance/LC” rule after one year beyond due date | Reconcile monthly; do not let entries age without an extension or reduction request |
| You change AD bank | New AD must take over EDPMS outstanding from the old AD — needs transfer of records | Intimate both banks; ensure EDF/EDPMS data migrates cleanly before the next shipment |
| Bank records and your records don’t match | Data consistency between bank’s EDPMS, DGFT eBRC repository and your books — shipping bill number, invoice number, GST fields | Audit the chain: Invoice → Export declaration (EDF) → Buyer → Shipment → IRM → eBRC → Outstanding balance — and fix the source (GSTIN, invoice number/date) before certifying |
SMEs vs large exporters — who is better prepared?
Who is better prepared for this new world — a large exporter with an ERP and integrated banking data, or an SME managing exports across Excel, accounting software, email, multiple consultants and multiple banks? Today, the large exporter is — by accident of systems, not by regulation.
A large exporter already maintains the practical chain in one place: Invoice → Export declaration (EDF) → Buyer → Shipment (shipping bill) → Bank remittance (IRM) → Realisation → eBRC → Outstanding balance. When the bank asks why an IRM for $30,000 matches three invoices, the answer is a report. An SME that keeps invoices in accounting software, shipping bills in CHA emails, IRMs in bank PDFs and eBRCs on the DGFT portal must stitch the same chain manually — and that stitching is exactly what banks will be checking more proactively from October 2026.
- Transaction-level reconciliation matters more because the bank must close EDPMS at the invoice/shipping bill level, not just on aggregate turnover.
- Invoice-level GSTIN/Invoice No/Date in every eBRC since 13 Jan 2026 means a typo in the invoice number is now a reconciliation break that blocks both eBRC and incentive claims.
- Outstanding export entries that remain open beyond one year from the due date have a direct consequence — further open-account exports are restricted — so SMEs cannot let small balances age in a spreadsheet.
- Having the chain cleanly connected — same IEC, same GSTIN, same invoice date across books, eBR C and bank — reduces friction with the bank and makes extensions or reductions easier to justify.
What should exporters do before 1 October 2026?
- Audit all pending EDPMS entries for your IEC — download the outstanding list from your AD bank and match it to your books.
- Generate eBRCs for every past IRM not yet linked to a shipping bill/invoice on dgft.gov.in (Services → eBRC → IRM/ORM Repository → Generate e-BRC); use bulk upload for volume and API where available (Trade Notice 12/2024-25).
- Transition SOFTEX to EDF — from 1 Oct 2026 software is a service; services EDF is within 30 days from month-end of invoice (single EDF may cover a month), and AD must upload to EDPMS within 5 working days.
- Reconcile GSTIN, GST Invoice Number and Date in your ERP with what banks will put in eBRCs — the revised Appendix 2U is mandatory since 13 Jan 2026 (Public Notice 42/2025-26).
- Verify RBI purpose codes (e.g., P0802, P0803, P0807 for IT/ITES) against SAC codes and DGFT purpose mapping before the next eBRC — mismatches block generation.
- Prepare explanations for unresolved mismatches — bank charges, forex differences, third-party payers, buyer-name variations — with evidence so the AD can allow reduction or approve the third-party receipt under Regulations 6 and 8.
- Check bank/IRM records for outstanding receivables beyond one year from the due date — seek AD extension before expiry where the buyer will still pay, or plan for advance/LC for further exports to that buyer.
Treat this as an inference, not a guarantee
Banks are required to monitor and follow up (Regulation 5(2)) and to upload within 5 days — how each bank operationally staffs that monitoring (automation, follow-up emails, documentation requests) is inferred from those duties. Do not present any bank’s future SOP as fact; verify with your AD closer to October 2026.
The bottom line — what fundamentally changes from 1 October 2026?
From 1 October 2026, export compliance in India moves from filing separate declarations for goods, services and software to a single EDF + EDPMS trail for all exports, with the bank as the continuous monitor, not the periodic checker. The AD is empowered to allow extensions, reductions and closures without approaching RBI, but it is also obliged to keep the trail reconcilable. For you as an exporter, the change is not a new form — it is a discipline: every invoice has an export declaration, every remittance has an IRM, every IRM has a mapped eBRC, and every outstanding has a clock. Keep that chain clean and the new regime is ease of doing business; let it fragment across systems and every exception becomes a conversation with your bank.
Keep reading
Documents banks check before paying
Invoice, B/L, packing list, COO — fields that stop payment.
Read documents guide →Pre-shipment papers that feed eBRC
Get the upstream set right so reconciliation matches.
Read pre-shipment docs →9 or 12 months? The 15/18-month myth
Why the Jan-2026 figures no longer apply, and when INR exports get 12 months.
Read the realisation guide →Service EDF in 30 days
Monthly single-EDF filing, DTA/SEZ/STPI routing, pay-on-receipt option.
Read the EDF guide →Close old EDPMS entries
4-bucket cleanup playbook plus the Rs 10 lakh per-entry declaration relief.
Read the cleanup playbook →FEMA 2026 questions on a live transaction?
Talk to trad — extensions, EDF filing and EDPMS cleanup for Indian exporters.
Contact us →Frequently asked questions
What changes for exporters from 1 October 2026?
FEMA (Export and Import of Goods and Services) Regulations, 2026 (FEMA 23(R)/2026-RB dated 13 Jan 2026) come into force 1 Oct 2026, superseding the 2015 Regulations. Exports get a unified Export Declaration Form (EDF) for goods and services, 9 months realisation (12 months for INR-invoiced/settled exports — the Jan-2026 15/18-month text was cut by the Sept 2026 amendment before go-live), stricter AD bank monitoring via EDPMS/IDPMS/FETERS, and tighter eBRC GST linkage (GSTIN/Invoice No/Date since 13 Jan 2026).
How will banks behave differently under the new FEMA regulations?
Banks must put in place systems to monitor and follow up on export realisation and are empowered to allow extensions, reductions and closures without RBI reference. Expect more automated EDPMS monitoring, data-driven checks, proactive follow-ups on outstanding entries, and greater comfort with clean/reconciled transactions — and more questions when invoice, shipping bill, IRM and eBRC data do not match.
Will banks ask for more documentation after October 2026?
Not necessarily more paper, but more precise data. The regulation empowers AD banks to satisfy themselves of genuineness and to close entries on exporter declarations for small values (up to ₹10 lakh per shipping bill/invoice). For exceptions — partial payments, third-party remittances, buyer mismatches — banks will need a clear explanation and evidence to update EDPMS and justify the entry closure or reduction.
What happens to outstanding export payments?
Every export creates an EDPMS entry (EDF + shipping bill/invoice) that must be closed by matching it to an IRM/eBRC realisation within the period (9 months, or 12 for INR). If export proceeds remain outstanding beyond one year from the due date/extended period without valid extension/write-off, further exports are permitted only against full advance or irrevocable LC. Outstanding entries are actively flagged to AD banks for follow-up.
How will the new rules affect SME exporters?
An SME juggling Excel, accounting software, email and multiple banks/brokers will feel the shift most. A large exporter with ERP and integrated bank data already maintains the chain Invoice → Export declaration → Shipment → IRM → eBRC → Outstanding balance in one place. SMEs will need the same discipline — reconciling invoices, shipping bills, IRMs and eBRCs continuously — or face more bank queries on mismatches.
What happens when export and payment data do not match?
The bank must verify and explain the difference before closing EDPMS: e.g., $98,000 received against a $100,000 invoice — where is the $2,000 difference? Bank charges, forex loss, discount, short-shipment or partial realisation each needs a documented reason for the bank to allow reduction and close the entry. Without it, the entry stays outstanding and may block future exports on open terms.
What should exporters do now the rules are live?
Audit all pending EDPMS entries, generate eBRCs for past IRMs not yet linked, transition SOFTEX to EDF, verify RBI purpose codes vs SAC codes, ensure GST invoice data matches eBRC data, and reconcile bank/IRM records with your books. Clean the chain now that banks have switched to active monitoring from 1 Oct 2026.