Skip to main content
This annexure lists the complete field-level details for the Push IRM request payload.
Legend: Req Y = Required, N = Not required, O = Optional, O(M) = Optional but conditionally Mandatory

Message fields

Item fields (ebrcBulkGenDtos[])

IRM identification

These five fields are checked against the IRM we hold for the exporter, and a disagreement is reported in the warnings array of an accepted filing rather than refused: irmIfscCode, irmAdCode, irmDt, irmFCC and irmPurposeCode. DGFT compares the same five and answers ERR15, ERR16, ERR19, ERR20 and ERR22 on the status poll hours later, so the warning is the same finding, earlier. See Errors.
sbCumInvoiceNumber carries three different documents, and Direct Export has a stricter rule than the string(20) above.For a Direct Export, an invoice-style reference such as EX/25-26/028 or SB7654321 is rejected with 400 before the filing is sent to DGFT. The invoice reference belongs in billNo.
Direct export (uploadType 101)
Swapping these two is the most common cause of a rejected Direct Export filing. DGFT’s own error for it is ERR25“Invalid shipping bill number. It cannot be greater than 7 digit” — which would otherwise surface hours later on the status poll rather than at submission.
Only the request fields relevant to Push IRM are listed here. Response and status fields (e.g., dgftAckId, ackStatus) are documented on their respective pages.

Used by