Skip to main content
GET
Download bulk upload template
Download a pre-filled Excel (.xlsx) template with all required and optional column headers and two example rows. Use it as the starting point for a bulk upload. Column headers are matched to fields by name, so keep the header text unchanged.

One row per IRM-to-invoice mapping

A row is one IRM against one shipping bill, Softex or invoice. Either side may repeat:
  • One remittance settling several invoices. Repeat the IRM columns on one row per invoice, with a different SB Cum Invoice Number, Bill No and Mapped IRM Amount FCC on each. The mapped amounts for one IRM must add up to no more than the amount still available on it; the whole file is refused if they do not. The two example rows show this: IRMNUMBER123 maps 6,000 to shipping bill 1234567 and 4,000 to shipping bill 1234568, out of a 10,000 remittance.
  • Several remittances settling one invoice. One row per remittance, each carrying the same SB Cum Invoice Number. DGFT issues one eBRC per row, so the invoice ends up with one certificate per remittance.
Every row needs its own Serial No, from 1 upwards. The file is named ebrc-bulk-upload-template.xlsx and the sheet is named EBRC Bulk Upload.

Request example

Template columns

The template contains these 37 columns, in order. 19 are mandatory — a row missing any of them is rejected with a per-row error and nothing in the file is filed. Conditional means required when Is GST Avail is Y, and it must be left empty when it is N. Full formats and constraints for each field are in the Push IRM Request Fields annexure under the field of the same name.
The annexure documents the DGFT specification, which marks mappedORMAmountFCC and isThirdPartyExport as required. Our Excel validation treats both as optional and will accept a file without them. DGFT may still reject such a filing downstream, so populate them when they apply to your consignment.

Column and value formats

  • Header text is matched by name, case-insensitively and ignoring spaces and punctuation. SB Cum Invoice Number, sbcuminvoicenumber and Invoice Number all resolve to the same field, so a header your ERP exports in a different case still works. Column order does not matter; only the header text does. Unrecognised columns are ignored.
  • Dates are accepted as DD/MM/YYYY, DD-MM-YYYY, DDMMYYYY, YYYY-MM-DD, or a real Excel date cell, and are normalised to DGFT’s DDMMYYYY before filing. Ambiguous values are always read day-first: 01/02/2024 is 1 February, never 2 January. A well-formed but impossible date such as 31/02/2024 is rejected rather than filed.
  • Y/N columns (Is Vostro, Is Third Party Export, Is GST Avail) accept either case — y and Y both work. Anything else, including Yes and True, is rejected.
  • Numeric columns may arrive as numbers or as text; "10000" and 10000 are equivalent.
  • Fully blank rows are skipped, so trailing empty rows in the sheet are harmless.

Valid codes

Next steps

Authorizations

x-api-key
string
header
required

Response

200 - application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

Excel template file (.xlsx)

The response is of type file.