BOE
Bill of Entry Amendment on ICEGATE: Amend, Delete or Supplement
The BE Amendment webform message type by message type. When to file A, D or S, the amend codes under each, the segments and tabs you actually fill, and why a container can only be deleted and re-added.
By Aaryan Kakani · · 11 min read
What is a Bill of Entry amendment and when does it become necessary?
A Bill of Entry amendment is a correction to a Bill of Entry that has already been presented to Customs. The enabling provision is Section 149 of the Customs Act 1962 , under which the proper officer may, in his discretion, authorise the amendment of a document after it has been presented at the custom house (CBIC consolidated Customs Act 1962 text, 30 March 2022).
The single most important thing to understand is that Section 149 has two very different halves. Before clearance, amendment is a matter of officer discretion. You make your case and the officer decides. After the goods have been cleared for home consumption or deposited in a warehouse, the door narrows sharply: the amendment may be authorised only on the basis of documentary evidence which was in existence at the time the goods were cleared or deposited . You cannot manufacture the proof afterwards. A revised invoice issued next month will not save an amendment that needed the original invoice.
The Finance Act 2021 added provisos allowing amendments to be done electronically through the customs automated system on the basis of risk-based selection criteria, and allowing the Board to specify amendments that the importer, exporter or agent may carry out themselves on the common portal. The ICEGATE BE Amendment webform is the practical expression of that machinery.
Typical triggers for a BE amendment
- Wrong quantity. The packing list and the declared quantity diverge, usually after a physical examination.
- Wrong invoice value. A supplier credit note, a freight or insurance element mis-stated, or a currency entered against the wrong invoice line.
- Wrong IGM linkage. The BE is tagged to the wrong Import General Manifest, line number or MAWB.
- Missing supporting document. A certificate of origin, a licence or a test report that was never uploaded to e-Sanchit.
- Wrong item description. A description that does not match the goods, which in turn puts the classification in doubt.
What is the difference between message type A, D and S?
The BE Amendment webform opens with a Message Type dropdown offering exactly three values (A (Amendment) , S (Supplement) and D (Deletion)) per the User Manual BE Amendment using Webform v1.03, 25 March 2025 . Everything else on the form is downstream of that one choice. Get it wrong and the amend code you actually need will simply not be in the list.
CBIC itself treats these as three separate procedures rather than three flavours of one. It has published three separately dated video tutorials (BE Amendment) Amend (11 September 2024), BE Amendment (Delete (14 November 2024) and BE Amendment) Supplement (19 December 2024). If the three were interchangeable there would be one video.
| Message type | What it does | Codes available | Worked example | Officer approval |
|---|---|---|---|---|
| A. Amendment | Changes the value of a field that already exists on the filed BE | 5. BE details, IGM details, Invoice details, Item details, Amendment of MAWB for prior BE IGM | Invoice value keyed as USD 8,500 when the commercial invoice says USD 8,050 | Yes. Section 149 discretion of the proper officer |
| D. Deletion | Removes an entry that should never have been on the BE | 5. Delete Container details, Delete IGM details, Delete Invoice details, Delete Item details, Delete Supporting documents | A second invoice line captured twice, or a container that belongs to a different consignment | Yes. And expect closer scrutiny, since deletion reduces what was declared |
| S. Supplement | Adds information that was never on the BE in the first place | 6. Add Container details, Add IGM details, Add Invoice details, Add Item details, Add Supporting documents, Add Declaration Statement | Certificate of origin uploaded to e-Sanchit after filing and now needs to be attached to the BE | Yes. Though document-only supplements are usually the least contentious |
Two asymmetries in that code list are worth committing to memory, because both of them cause real filing failures.
| Subject | Under A | Under D | Under S |
|---|---|---|---|
| BE details | Yes | . | . |
| IGM details | Yes | Yes | Yes |
| Invoice details | Yes | Yes | Yes |
| Item details | Yes | Yes | Yes |
| Container details | No | Yes | Yes |
| Supporting documents | . | Yes | Yes |
| MAWB for prior BE IGM | Yes. Only here | . | . |
| Declaration Statement | . | . | Yes. Only here |
How do you reach the BE Amendment webform on ICEGATE?
The literal path, once you have an ICEGATE registration, is short. Log in with your ICEGATE ID and password, selecting User Type = 'ICEGATE User' . Then, from the dashboard:
Menu path
Services widget > Electronic Filling >> Webforms > BE Amendment
Source: BE Amendment webform manual v1.03. The double chevron and the spelling "Filling" are ICEGATE's own. Searching the portal for "Filing" will not match the menu label.
There is a host quirk that wastes an enormous amount of time and makes people believe the guidance pages are dead. The apex domain icegate.gov.in serves an empty Angular shell for /guidelines/* URLs and then 302-redirects to the homepage. Use www.icegate.gov.in instead. Even there, the guidance page is a pdf.js viewer wrapper: the actual document lives in the ?file= query parameter, pointing at /sites/default/files/YYYY-MM/*.pdf . If you want the manual itself rather than a viewer, pull that parameter out and open the PDF directly.
The authority for everything in this guide is User Manual BE Amendment using Webform, version 1.03, dated 25 March 2025 , a 30-page document. Check the version number before you rely on a copy someone has emailed you. The form has changed across revisions, and an older manual will show codes that no longer match the dropdown.
Which segments and tabs do you have to fill in the BE Amendment form?
Below the header block, the form is organised into three segments, each with its own tab strip. You do not have to touch every segment (only the ones your chosen amend code reaches) but you should know the whole tree, because a single amendment often ripples across two segments.
| Segment | Tabs, in order | What typically changes here |
|---|---|---|
| Invoice details | Invoice details → Supplier details → Seller and Broker Details → Invoice rates and Commercial details → Third Party details → Supporting Document | Invoice number and date, currency, assessable value, freight and insurance elements, supplier identity |
| Item details ("List of Items") | Item details → Product and Notification Details → Price details → Manufacture details → Supporting Document | Description, quantity, unit price, notification benefit claimed, country of manufacture |
| Single Window | Production details → Control details → Constituent details → Declaration Statements | Participating Government Agency data. Composition, controls, and the declaration statements added under message type S |
Mandatory fields carry an asterisk and highlight in red when left blank on save. In practice the same handful gets missed over and over, usually because they sit in the header block above the segments and people scroll straight past them to the data they came to change.
| Field most often left blank | Where to get it |
|---|---|
| BE number | The filed Bill of Entry / ICEGATE enquiry |
| BE date | The filed Bill of Entry. Must match exactly, not the assessment date |
| Custom House Code | Port code on the BE, not your registered office location |
| Request Letter number | Your own letter to the Custom House requesting the amendment |
| Request date | Date on that request letter |
| User job date | Your internal job reference date for the filing |
| Reason for Amendment | Free text. Write it out properly, see below |
Input fields carry hover tooltips describing the expected content, which is the fastest way to settle a formatting question without leaving the form.
Why can container details only be deleted and re-added, never amended?
This is the structural quirk that catches most first-time filers. Container details appear as Add Container details under message type S and Delete Container details under message type D. There is no container option under message type A at all. Whatever the design reason, the operational consequence is fixed: a container number cannot be edited in place. It has to be removed and re-entered.
Correcting a container number: the two-step sequence
- 1 Record the correct data before you touch anything Copy the existing container entry in full (number, seal, size, type) and write out the corrected version alongside it. Once the delete goes through, the old record is no longer on screen to copy from.
- 2 File message type D with Delete Container details Reason for amendment should say plainly that the container is being deleted only so that the corrected number can be added, and should name the corrected number. This prevents the officer reading the deletion as a reduction in declared cargo.
- 3 File message type S with Add Container details Enter the corrected container. Cross-reference the Tracking ID of the deletion filing in the reason text so the two halves are visibly one transaction.
- 4 Verify the BE reads correctly end to end Confirm the container count on the amended BE matches the IGM and the carrier documents. A delete that succeeds and an add that fails leaves the BE short a container.
Generalise the lesson beyond containers. Before you assume any correction is a straight edit, check whether the field is actually offered under message type A . If it is not, you are looking at a delete-plus-add pair, and you should plan it as a pair from the outset. Same session, same evidence bundle, cross-referenced reasons.
How do you attach supporting documents and get past DSC validation?
There are two routes to getting a supporting document onto a BE amendment, and the manual supports both. The difference matters when things go wrong.
| Route | How it works | When to use it |
|---|---|---|
| Upload on e-Sanchit first (preferred) | Go to e-Sanchit from the Services widget, upload the PDF, receive the IRN and DRN, then quote both on the amendment form | Always, when you have time. You see the upload succeed before you commit to the amendment |
| In-form attach | Fill the document particulars, click Attach, click Save. The file is forwarded to e-Sanchit; IRN and DRN are generated and auto-filled into the Image Reference Number and Document Reference Number fields | When you are already mid-form and the document is small, clean and already signed |
On the in-form route, whether the IRN and DRN come back automatically depends on the file. If the PDF is already digitally signed , the reference numbers return automatically on Save. If it is not, use the webform's own Sign file option before saving.
Worked example: fitting a scanned invoice pack under the cap
You have a 12-page scanned commercial invoice pack to attach to an amendment. Scanned at 300 dpi colour, each page is about 0.42 MB.
- 12 pages × 0.42 MB = 5.04 MB. The single combined PDF.
- 5.04 MB − 1.5 MB = 3.54 MB over the cap. It will be rejected outright.
- Pages that fit in one file at this scan quality: 1.5 MB ÷ 0.42 MB = 3.57 , so 3 pages per file (round down. Never up).
- Files needed: 12 ÷ 3 = 4 files , each 3 × 0.42 = 1.26 MB . Headroom per file: 1.5 − 1.26 = 0.24 MB .
- Better alternative: re-scan at 200 dpi greyscale, which typically lands near 0.11 MB per page. Then 12 × 0.11 = 1.32 MB. One file, under the cap, with 1.5 − 1.32 = 0.18 MB to spare, and one IRN instead of four.
The lesson: fix the scan settings before you split the file. Splitting multiplies the IRNs you have to track and quote; re-scanning does not.
The other family of errors is field-level rather than document-level. The form validates each input against its expected type and length, and reports a Field Type Error when the two do not agree.
| Error class | Typical cause | Fix |
|---|---|---|
| Numeric field error | Letters, commas or a currency symbol pasted into a numbers-only field | Strip formatting; paste values as plain digits with a decimal point only |
| Character field error | Digits or special characters in an alphabetic-only field | Remove punctuation carried over from a spreadsheet or a PDF copy-paste |
| Date field error | Date typed in a format the field does not accept, or a future date where a past one is required | Use the date picker rather than typing; check the hover tooltip for the expected format |
| Field length mismatch | Value longer or shorter than the field allows. Common with codes that need leading zeros | Restore leading zeros that a spreadsheet stripped; truncate trailing whitespace |
What is the difference between a ticket reference number and a Tracking ID?
This distinction is responsible for more false comfort than anything else in the BE amendment flow, so it is worth stating bluntly: a ticket reference number is not proof that you filed anything. Only a Tracking ID is.
| Identifier | Issued when | What it proves | Needs DSC |
|---|---|---|---|
| Ticket reference number | On Save as Draft. The popup reads "Form has been saved as draft." with the number (the manual's worked example is 26809) | That a draft exists on ICEGATE and can be reopened. Nothing has been submitted to Customs | No |
| Tracking ID | On successful submission, after DSC validation succeeds | That the amendment request has actually been filed and can be followed up | Yes |
Saved drafts are retrievable from the Drafts widget > Filing Draft link, where each draft carries Rename and Delete buttons. Rename them to something you will recognise a week later. The BE number and the amend code beats "Draft 3".
For long forms on a poor connection, the webform supports an offline mode. Use the download icon in the browser address bar, then Install , to get the desktop web-app. You can fill the form offline, use Export File to save the work as JSON, and re-import it later with Choose File > Open . Two things stay online-only: uploading documents, and submitting. Offline mode is a data-entry convenience, not a filing channel.
| Filing method | Best suited to | Signature requirement |
|---|---|---|
| Webform (online) | One-off amendments, occasional filers, anyone who wants field-level validation as they type | DSC validated at submit |
| Webform (offline desktop app) | Long forms, unreliable connectivity, drafting away from the office | DSC still required. You must come online to submit |
| Flat file | Established system-to-system filers already on the legacy format | Per the applicable message specification |
| JSON schema (CACHI01) | Volume filers integrating their own systems. See the BE/SB Open API advisory dated 18 November 2025 | digSign object mandatory; an unsigned JSON is invalid |
If you are heading down the integration route, the advisory for BE/SB filing using the JSON-based schema sits alongside the CACHI01 schema , which requires three top-level objects. HeaderField , master and digSign . Build the signing step into your pipeline from day one; retrofitting it is the usual cause of a stalled integration.
BE amendment pre-filing checklist
Before you open the form
- Identify which of A , D or S covers the field you need to change. Amend, delete or add.
- Confirm the specific amend code actually exists under that message type. Containers and declaration statements are the known traps.
- Have the header data ready: BE number, BE date, Custom House Code, Request Letter number, Request date and User job date.
- Draft the reason for amendment in full, using the long free-text allowance. What changed, which document proves it, and when that document came into existence.
- Upload the evidence to e-Sanchit first and note the IRN and DRN before you start the amendment form.
- Check every PDF is under 1.5 MB and is genuinely a PDF. Re-scan at lower dpi rather than splitting where you can.
- Plug in the DSC and confirm it reads before you start filling, because validation only bites at submit.
- For containers, plan the delete plus re-add pair as one session with both sets of data written down first.
While filing and afterwards
- Save a draft and note the ticket reference number. But remember it proves nothing was filed.
- Submit, and record the Tracking ID against the BE in your own register. That is the filing evidence.
- Re-read the amended BE end to end and confirm counts and values reconcile to the IGM and the commercial documents.
- Check whether the same correction needs to flow onward. To IDPMS on the import payment side, or to your GST records if the assessable value or IGST changed.
- File the request letter, the evidence bundle and the Tracking ID together, so the Section 149 story is reconstructible if questioned later.
Update history
- First published.