e-BRC (Electronic Bank Realisation Certificate) Textile Export Reconciliation

A Karur home-textile exporter’s finance controller opens the November 2026 export ledger with 43 open shipping bills against three US retail customers and two European buyers. The largest single shipment — 32,000 bed linen sets valued at $850,000 FOB against a US big-box order shipped on 22 October 2026 — has just been credited to the AD bank (HDFC Bank illustrative) with a SWIFT MT-103 for $845,000, a $5,000 short-realisation the buyer’s remittance advice attributes to a chargeback for a quality claim on 3,200 sets from the previous quarter. The banker’s e-BRC drops into the DGFT portal 48 hours later showing realised value $845,000, INR credited ₹7.03 crore at the bank’s TT-buying rate of ₹83.15, and realisation date 6 November 2026. The shipping bill declared FOB at ₹7.06 crore at the CBIC-notified customs exchange rate of ₹83.05 for the second half of October 2026. Two different INR values, one shipment, one buyer, one shipping bill — and every downstream reconciliation cascade (RoDTEP claim, RoSCTL claim, EPCG EO credit, buyer AR write-off, FEMA aging) depends on the controller mapping all four documents cleanly to the same underlying export event. This is e-BRC electronic bank realisation certificate textile export reconciliation at the pace that a Karur, Panipat, or Tiruppur exporter runs — and the article that follows walks through the statute, the illustrative worked example, and the platform discipline that closes the loop.

Quick reference

The reconciliation in one paragraph

The e-BRC is a DGFT-hosted electronic Bank Realisation Certificate uploaded by the Authorised Dealer bank against a shipping bill after export proceeds are received in India. FEMA Master Direction on Export of Goods and Services (RBI MD-16/2015-16 as updated) requires that proceeds be realised and repatriated within 9 months from the date of export. The AD bank monitors this through EDPMS — every shipping bill auto-populates from ICEGATE and must be linked to an inward remittance IRM before the 9-month mark. The e-BRC captures the realised value in the invoice foreign currency, the INR credited at the AD bank’s TT-buying rate, and the realisation date. Textile exporters must reconcile four documents for every shipment: (1) the shipping bill (FOB in foreign currency at the CBIC customs exchange rate for the fortnight); (2) the export invoice (typically identical to SB FOB); (3) the SWIFT MT-103 credit advice (which may be short-realised for buyer deductions); and (4) the e-BRC (which validates INR credit and gates every DGFT scheme). RoDTEP (Appendix 4R for DTA, 4RE for AA/EOU/SEZ), RoSCTL for garments and made-ups, EPCG export obligation credit, and Advance Authorisation input-output norm closure all depend on the e-BRC being present, correctly linked, and inside the FEMA window.

What the e-BRC reconciliation looks like in India

Karur is the epicentre of India’s home-textile export industry — bed linen, kitchen linen, curtains, cushion covers, made-ups for US and European retail chains, and OEM production for global brands. The regional cluster runs on export-weighted revenue: a specialist tier-2 Karur home-textile exporter typically sells 60 to 80 percent of production to overseas buyers on 60- or 90-day open-account terms, with the balance to domestic retail. Panipat runs the same shape for winter home furnishings and utility textiles; Tiruppur runs it for knitwear apparel; Ludhiana for winter woollens; Solapur for jacquards. Illustrative principals operating at this shape include specialist tier-2 firms such as Welspun India (home textiles market leader), Indo Count Industries (bed linen), Himatsingka Seide (bedding and home fashion), Trident Ltd (bath and bed linen), and Pearl Global Industries (apparel exports); and tier-1 vertically integrated firms such as Vardhman Textiles, Arvind Ltd, KPR Mill, and Aditya Birla Fashion and Retail (Pantaloons, Allen Solly, Van Heusen). Regional cluster geography matters because AD bank branches and the correspondent banks (US and European buyers’ side) vary by cluster, and the SWIFT routing patterns that feed EDPMS depend on the AD bank’s nostro network.

The reconciliation base case is the single-shipment single-buyer credit — the buyer remits the exact invoice value, the AD bank credits, the e-BRC issues, and the RoDTEP scrip drops within days. The stress cases that a Karur controller sees in practice: a US retail buyer remits a consolidated payment across five shipping bills spread over three weeks (the AD bank must split-tag the IRM to five SBs on EDPMS); a European buyer deducts a small commission or freight adjustment (short-realisation must be routed to buyer AR); a chargeback for a quality claim on a prior shipment lands as a deduction against a current shipment’s remittance (short-realisation is genuine but must not be treated as a bad-debt write-off in the current SB); a buyer files bankruptcy or delays past 9 months (XOS reporting triggers, extension or write-off decision required). Each stress case cascades into the same downstream question — can the exporter still claim RoDTEP, RoSCTL, and EPCG EO credit on this shipping bill, and if so, at what value.

The regulatory overlay — FEMA, EDPMS, e-BRC, and the scheme downstream

The FEMA Master Direction on Export of Goods and Services sets the 9-month realisation window measured from the date of export. Sub-provisions cover extension by AD bank (up to a specified cumulative limit), extension by RBI (beyond AD bank’s limit), self-write-off (permitted up to a specified percentage of the previous year’s export turnover for exporters with a satisfactory track record), and AD-bank-approved write-off (beyond self-write-off, subject to genuine buyer default and documented recovery effort). The 9-month clock is a hard-edged aging surface — the AD bank must include every SB not linked to an IRM by day 270 in the XOS statement that goes to the RBI half-yearly, and once XOS-reported, the corresponding RoDTEP or RoSCTL claim can be held up at the DGFT until the realisation resolves.

EDPMS is the operational portal. Every shipping bill filed at ICEGATE auto-flows into EDPMS in the AD bank’s dashboard. When a SWIFT MT-103 credit lands in the AD bank’s nostro account with the exporter as beneficiary, the bank generates an IRM (Inward Remittance Message) that must be linked to a shipping bill on EDPMS. The linkage carries the foreign currency amount, the value date, the buyer reference, and any short-realisation. Once linked, the AD bank uploads the e-BRC to the DGFT portal against the shipping bill — the e-BRC carries SB number, IEC, buyer, invoice value in foreign currency, realised value in foreign currency, INR credit at the bank’s TT-buying rate on the realisation date, and the realisation date itself. The exporter downloads the e-BRC from the DGFT e-BRC portal against IEC and SB number.

Downstream, the e-BRC gates every DGFT scheme. RoDTEP claim (DGFT Notification 10/2025-26 dated 24 and 26 May 2025 — Appendix 4R w.e.f. 1 May 2025 for DTA exports, Appendix 4RE w.e.f. 1 June 2025 for Advance Authorisation, EOU, and SEZ exports, both valid till 31 March 2026) is computed on the FOB value in foreign currency at the customs exchange rate on shipping bill date, and the scrip issues only when the e-BRC is present against the SB. RoSCTL (garments, made-ups, Chapters 61, 62, 63) works the same way — scrip issuance is gated on e-BRC. EPCG (Foreign Trade Policy 2023 Chapter 5) demands 6× duty saved as export obligation over 6 years from authorisation issue; every EPCG-flagged shipping bill’s e-BRC contributes to the block-year EO fulfilment, and shortfall triggers customs duty foregone plus 15 percent interest per annum from original clearance date. Advance Authorisation input-output norm closure and legacy MEIS and SEIS scrip claims (discontinued for most products but still reconcilable for closure) all follow the same gating pattern.

A worked example — a Karur home-textile shipment to US retail

Illustrative — the following figures represent the operating pattern of a representative Karur home-textile export shipment of the scale that a specialist tier-2 firm operates. Public disclosures do not reveal individual shipping bill and e-BRC values; cross-verify against your own export ledger before action.

A Karur home-textile exporter with approximately ₹200 crore turnover ships 32,000 bed linen sets to a US big-box retailer on 22 October 2026. The commercial invoice is USD 850,000 FOB (₹2,656 per set at USD 26.56 per set FOB). The shipping bill filed at Chennai Port on 22 October 2026 carries FOB USD 850,000 and, at the CBIC-notified customs exchange rate for the second half of October 2026 of ₹83.05 per USD, declares FOB INR ₹7,05,92,500 (approximately ₹7.06 crore). The shipping bill scheme flag is RoDTEP Appendix 4R (DTA export — the exporter is not operating under Advance Authorisation, EOU, or SEZ for this SKU); RoSCTL yes (made-up bed linen under Chapter 63); no EPCG authorisation attached (the digital printing line was cleared without EPCG in an earlier year). The FEMA realisation clock starts on 22 October 2026 and expires on 22 July 2027 — 9 months forward.

The buyer’s payment terms are 30 days from bill of lading date. On 6 November 2026 — approximately 15 days after export, ahead of the 30-day term — the buyer initiates a SWIFT MT-103 wire for USD 845,000 from its US bank (correspondent bank in New York) routing through the AD bank’s US nostro account and landing in the AD bank’s (HDFC Bank illustrative) Chennai branch nostro. The remittance advice attached to the MT-103 references invoice number and shipping bill number, and notes a USD 5,000 chargeback against a quality claim on a prior shipment.

The AD bank generates the IRM on EDPMS for USD 845,000 with the buyer name, links it to the correct shipping bill number, and notes the USD 5,000 short-realisation with the chargeback reference. On 6 November 2026, the AD bank converts USD 845,000 at its TT-buying rate for that date of ₹83.15 per USD (fractionally higher than the customs exchange rate of ₹83.05 because the customs rate is a fortnight-average CBIC notification and the bank rate is a real-time TT-buying quote). The INR credit is ₹7,02,61,750 (approximately ₹7.03 crore). Bank charges — SWIFT fee, correspondent bank fee, and a nostro charge — deduct approximately ₹4,200 from the credit, leaving net INR ₹7,02,57,550 in the exporter’s current account.

The AD bank uploads the e-BRC to the DGFT server on 7 November 2026: SB number 22102026/CHN/XXXXX, IEC, invoice value USD 850,000, realised value USD 845,000, INR credited ₹7,02,61,750, bank rate ₹83.15, realisation date 6 November 2026. The exporter downloads the e-BRC from the DGFT portal on 8 November 2026 and files it in the export register.

The reconciliation pack for this single shipment surfaces the following entries:

The reconciliation closes cleanly. RoDTEP and RoSCTL claims are filed on RFD-01 (or the DGFT-specific claim flow) with the shipping bill and e-BRC as attached evidence, and the e-scrips drop in the DGFT ledger within the DGFT processing cycle. The USD 5,000 short-realisation sits in buyer AR as a chargeback dispute — the exporter’s commercial team pursues the buyer for chargeback substantiation (proving the prior quality claim was invalid, or accepting the deduction as commercial adjustment) and either recovers the amount in a future remittance or writes it off after a defined recovery cycle.

Now consider a failure mode. Change the buyer’s payment behaviour — the US retailer’s treasury pauses payment for a supply-chain dispute unrelated to this shipment, and the SWIFT MT-103 does not land until 15 August 2027, nine months and three weeks after the shipping bill date. The FEMA 9-month realisation window expired on 22 July 2027. The AD bank includes the shipping bill in the XOS statement submitted to the RBI for the half-year ending 30 September 2027. The realisation on 15 August 2027 was inside the AD bank’s typical extension authority, and the AD bank retroactively grants a short extension based on the buyer’s supply-chain letter — the shipping bill is closed off the XOS after the extension is regularised. However, the RoDTEP claim that was pending release at the DGFT was held up during the XOS period, and once the extension is regularised and the e-BRC issues on 16 August 2027, the RoDTEP e-scrip releases with a 6-week delay against the normal cycle. The exporter’s working capital cost for the delay is the interest on the delayed scrip realisation — a real cost that the platform tracks against the shipping bill.

Common reconciliation breakages

Five recurring breakages surface across Karur, Panipat, Tiruppur, and Ludhiana exporters running e-BRC reconciliation at scale.

• Consolidated remittance across multiple shipping bills. A US retail buyer often nets multiple invoice batches into a single weekly remittance. The IRM on EDPMS lands as one lump sum, and the AD bank must split-tag the IRM across the correct set of shipping bills. If the exporter does not supply an accurate remittance-to-SB mapping to the AD bank quickly, the bank may auto-tag by FIFO — which frequently mis-links payments to older SBs that were already reconciled elsewhere, corrupting the aging on subsequent SBs.

• Short-realisation misclassified as write-off. SWIFT short-realisations arise from buyer chargebacks, freight adjustments, commission deductions, or quality claims. The exporter must route the short-realisation to buyer AR as a dispute or a commercial adjustment, not treat it as a bad-debt write-off. A misclassified write-off shows up as a FEMA compliance issue because the AD bank’s write-off approval requires documented recovery effort — a self-generated write-off without evidence is a red flag at RBI inspection.

• Customs exchange rate vs bank TT-buying rate confusion in scheme claim compute. RoDTEP and RoSCTL claims are computed on FOB in INR at the customs exchange rate on shipping bill date, not at the AD bank’s realisation-date rate. Exporters that use the bank rate for scheme compute either under-claim or over-claim by the rate differential, and the DGFT reconciliation flags the mismatch when the e-scrip actually issues.

• e-BRC missing against a claimed shipping bill. RoDTEP and RoSCTL claims filed before the AD bank uploads the e-BRC sit in queue at the DGFT. The exporter must sequence — SB filed at ICEGATE, SWIFT credit received, IRM linked on EDPMS, e-BRC uploaded to DGFT, then scheme claim filed. Any out-of-sequence claim burns processing cycles and delays scrip issuance.

• EPCG EO fulfilment under-counted because of unmapped e-BRCs. For EPCG-flagged shipping bills, the block-year EO tally depends on every e-BRC being tagged to the EPCG authorisation reference. Exporters that run multiple EPCG authorisations across product lines commonly mis-tag e-BRCs to the wrong authorisation, leaving one authorisation over-fulfilled and another under-fulfilled. At the 6-year block-end, the under-fulfilled authorisation triggers the customs duty foregone plus 15 percent interest penalty — a large contingent liability that the platform must surface early.

How a reconciliation platform handles this

A purpose-built textile export reconciliation platform ingests the shipping bill register from ICEGATE, the SWIFT MT-103 feed from the AD bank, the EDPMS export ledger, and the e-BRC download from the DGFT portal, and produces a per-shipping-bill closure view that chains FOB in foreign currency at customs rate, SWIFT credit in foreign currency at bank rate, IRM linkage on EDPMS, and e-BRC upload against the DGFT record. The platform runs the FEMA 9-month realisation clock against every open SB and surfaces exposure at 180, 240, and 270 days from shipping date, so the exporter can chase buyers and coordinate with the AD bank before the XOS half-year cycle picks up any un-reconciled SB. It classifies every short-realisation into chargeback dispute, freight adjustment, commission deduction, or write-off candidate and routes each to the correct downstream owner. It gates every RoDTEP (Appendix 4R for DTA, 4RE for AA/EOU/SEZ) and RoSCTL claim only when the SB-e-BRC pair is complete and inside the FEMA window, computing claim value on FOB at customs rate and not confusing it with bank rate. For EPCG authorisations, the platform tallies every EPCG-flagged SB’s e-BRC realisation against the block-year EO and flags shortfall risk with enough lead time for corrective shipments before the 6-year block-end. Match rate improvement of 51 to 88 percent on the SB-to-e-BRC-to-EDPMS chain, combined with ISO 27001:2022 posture and DPDP Act 2023 aligned data handling, is what makes the platform infrastructure for an export-heavy textile principal rather than a spreadsheet substitute.

Cross-cluster bridges and where to read next

The e-BRC discipline in this article closes the export-realisation loop for the entire textile cluster. For the incentive scheme side, the RoDTEP claim reconciliation walkthrough at RoDTEP claim reconciliation textile India, the appendix-specific detail at RoDTEP Appendix 4R DTA textile claim and RoDTEP Appendix 4RE AA/EOU/SEZ textile claim, and the garment-specific rebate at RoSCTL claim reconciliation garment and made-ups India all sit downstream of clean e-BRC data. For the capital-goods obligation surface, EPCG export promotion capital goods textile reconciliation walks through the 6-year EO block against e-BRCs. For the legacy scheme closure, MEIS legacy claim reconciliation textile export and SEIS textile services export reconciliation explain the discontinued-scheme close-out that still requires e-BRC evidence. Upstream, the job-work chain that produced the exported garment or made-up is covered in multi-hop job-work reconciliation textile India, the movement documentation in Rule 55 delivery challan for textile job-work movement, and the quarterly filing surface in ITC-04 quarterly return textile job-work reconciliation. The inverted-duty refund cycle that runs parallel to export incentives is at Rule 89(5) inverted-duty refund textile India, with monthly filing mechanics at RFD-01 monthly filing textile inverted-duty refund. The commercial pillar for the entire cluster is Textile reconciliation software India; the broader authority is reconciliation software India.

The five FAQs below address the operational questions Indian textile export controllers ask most often when implementing structured e-BRC reconciliation.

Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 6 July 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024