For finance and compliance teams

Error-free bank paperwork, straight from the trade record

Every bank document comes from the transaction, bank details come from your masters, and IDPMS and EDPMS matching is built in, so you can send each request with confidence.

Start a free workspace Book a demo

Start a free workspace with up to 10 records, free for 60 days. No card needed.

The view for founders and CFOs is on For founders and CFOs.

Every bank document, generated from the trade record

Stop copying last month's letter and changing the invoice number. On FxLayer, every standard letter, declaration and RBI form is generated from the record it belongs to, one at a time or in bulk as PDF. Each document checks its required fields before it prints, so every figure matches the record.

  • Bank request letters and declarations print on your letterhead, using the platform's designs or your own uploaded letterhead.
  • HDFC, ICICI, Axis and other bank formats are laid over the standard letter, so it carries the particulars and undertakings your bank asks for.
  • Form A1 (import remittance application) and Form A2 keep the RBI layout, as the bank expects.

Bank details filled from your masters, never retyped

Typing the same supplier's bank details twice a month is how errors start. FxLayer fills party and bank details from your party and bank masters into every document, so they're entered once and never retyped. Every create, update and letter is logged in the audit trail.

IDPMS and EDPMS matching built in

  • IDPMS to Bill of Entry: each outward remittance is matched to the Bill of Entry it settles, across banks, and the Import Outstanding Statement is built from open entries. What is IDPMS?
  • EDPMS to Shipping Bill: each receipt is linked to its Shipping Bill and invoice, and the Export Outstanding Statement is built from open bills. What is EDPMS?
  • When the bank's list doesn't match your books (Growth and above): upload your AD bank's outstanding list (CSV or Excel). Every row is matched to the register and sorted into close at bank, follow up, missing from register, or not at bank. Why an EDPMS entry stays open
  • Settlement letters, closure requests and the IDPMS closure declaration for a Bill of Entry up to ₹10 lakh come from the same record. The AD bank closes the entry.

More: EDPMS and IDPMS on one platform · the 2026 export and import regulations

Shipping Bills tracked to BRC and duty drawback

  • 9-month realisation countdown: each Shipping Bill gets its due date from the rule in force on its date. From 1 October 2026 that's 9 months, or 12 if invoiced or settled in INR. An AD-bank extension date replaces it when recorded. Confirm with your AD bank or CA. Export realisation timelines
  • 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 full advance or an LC.
  • Extension letter in advance: generate the export realisation extension letter ahead of time rather than at the last moment, so you can send it to the bank whenever you need to.
  • BRC tracking: advance, post-shipment and pending amounts and eBRC cover for every Shipping Bill, from shipped to closed, with an "eBRC due" alert. eBRC and FIRC
  • Duty drawback by HS code: the platform finds the notified drawback and RoDTEP rate for each Shipping Bill line by HS code (and drawback item). You confirm the declared rate, and the platform checks the expected amount, flags anything not claimed or at a different rate, and tracks the claim to credit. You file the claim on ICEGATE as usual.

Merchanting trade declarations without copied references

Both legs of a merchanting trade sit on one record, with their payments, receipts, AD banks and margin. The gap between the legs is counted down (6 months for trades begun on or after 1 October 2025). The merchant trade declaration, the bank request letters and the closure request come from the trade itself, on your letterhead. Form A2 for the import leg stays in the RBI layout. Merchanting trade transactions

Services exports: the monthly EDF that replaces SOFTEX

SOFTEX ended on 1 October 2026. The EDF now goes to the specified authority within 30 days of the end of the invoice month, and one EDF can cover the whole month. FxLayer prepares it from your service invoices as a PDF and a CSV for your AD bank, and tracks the 30-day timing. Confirm the authority and timing for your case with your AD bank or CA. Monthly EDF for services

See every module on Solutions and compare plans on Pricing.

FAQ

Each outward remittance is linked to the Bill of Entry it settles, across all your banks, within the contract due date, the credit days or 180 days by default. Open entries form the Import Outstanding Statement, and the settlement or closure letter comes from the same record.
On the Growth plan and above, upload your AD bank's outstanding list as CSV or Excel. FxLayer matches each row to your register and sorts it into close at bank, follow up, missing from register, or not at bank, so you know exactly which entries to chase or close.
No. The platform looks up the notified rate by HS code and drawback item and shows it on the Shipping Bill. You type the declared rate, and the platform checks the expected amount and tracks the claim until it's credited. The claim itself is filed on ICEGATE.
Yes. Generate it in advance from the Shipping Bill rather than at the last moment, and send it to your AD bank whenever you need to. It's for export realisation on Shipping Bills; there's no import or merchanting extension letter.
Yes, SOFTEX ended on 1 October 2026 and services exporters now file a monthly EDF. FxLayer prepares it from your service invoices as a PDF and a CSV for your AD bank, and one EDF can cover the whole month. Confirm the details with your AD bank or CA.