Export module

Export realisation and EDPMS: every Shipping Bill tracked to closure

Each Shipping Bill gets its realisation date from the rule in force on its date, is matched to the money that pays it, and is tracked to the eBRC and to closure in EDPMS by your AD bank.

No card needed.

Demo

See the Export realisation module run

One demo exporter and one Shipping Bill, from the export invoice under LUT to the eBRC: the lodgement letter signed and sent to the AD bank, the e-FIRA and the disposal instructions that link the money in EDPMS, the FX board, the eBRC file for DGFT, Duty Drawback and RoSCTL on the bill, and the EDPMS check against the bank's list.

How it runs

From the invoice to a closed EDPMS entry

Invoice and Shipping Bill

Make the export invoice in FxLayer or record your own; the Shipping Bill joins from ICEGATE data, its PDF or your ERP.

Money matched

Each receipt is matched to the Shipping Bills and invoices it pays, with part receipts, advances and bank charges handled.

eBRC

The eBRC is generated on DGFT from the bank's IRM: on the portal, in DGFT's bulk-upload file, or through DGFT's eBRC API.

Closed in EDPMS

The realisation or closure request goes to your AD bank, which reports the realisation and closes the entry.

The realisation clock

  • Nine months, twelve in rupees: for exports from 1 October 2026, twelve when invoiced or settled in rupees; older Shipping Bills keep the period of their own date. An extension your AD bank allows replaces the date once recorded.
  • Alerts: overdue bills, bills due soon and unrealised bills sit on your to-do list. A bill still unrealised a year past its due date is flagged, because further exports would need a full advance or a letter of credit.
  • Extension letter in advance: the realisation extension request is made from the Shipping Bill whenever you need it, not at the last moment.

EDPMS matching and closure

  • Scored suggestions: receipts matched to Shipping Bills by party, amount, currency and date, and more strongly when the bank's narration quotes your invoice.
  • Closure with variance: a short receipt is written off only within the lower of 5% or USD 1,000, with the declaration drafted when the rule allows it.
  • Export Outstanding Statement: built from the open bills, and on Growth and above the bank's outstanding list checked against your register line by line.
  • By API where the bank offers it: with ICICI, the closure list can go to the bank by API, on your own credentials.

eBRC, incentives and the Export desk

  • eBRC tracker: advance, after-shipment and pending amounts and the eBRC cover of every Shipping Bill, live from the records.
  • DGFT's eBRC API: on Growth and above with the Export or Services module, using your own credential from the DGFT portal; DGFT's bulk-upload file on every plan.
  • Export incentives: on Growth and above, the notified RoDTEP, Drawback and RoSCTL rates looked up by HS code; you confirm the declared rate and the claim is tracked to credit. The claim itself is filed on ICEGATE.
  • Certificates of origin: the type, agreement, number and date recorded on each Shipping Bill.
  • The Export desk: one page from invoiced to documents, money, eBRC, incentives and report, with what to do next.

Questions

For exports from 1 October 2026, nine months, or twelve if invoiced or settled in rupees. Older Shipping Bills keep the period on their date. Ask your AD bank before the due date if you need more time.
No. Your AD bank reports the realisation and closes the entry. FxLayer matches the money, prepares the request letter and shows the entry as closed once the bank has closed it.
On Growth and above, with DGFT's eBRC API and your own credential from the DGFT portal, FxLayer sends the request you approve and collects the eBRC number. On every plan it prepares DGFT's bulk-upload file for you to upload.
No. It shows the notified rate by HS code, checks the expected amount against the rate you declared and tracks the claim until it is credited. The claim is filed on ICEGATE.