IGST on Imports: Claiming ITC and Matching BOE in GSTR-2B

The customs broker filed the bill of entry on time, the duty challan was paid the same afternoon and the container reached the plant two days later. Three months on, the indirect tax manager is still carrying ₹8.4 lakh of IGST as "pending credit", because the bill of entry never appeared in the company's GSTR-2B. The broker had keyed the GSTIN of the group's Gujarat branch instead of the Maharashtra unit that imported and paid.

IGST paid at customs is one of the largest credits an importer claims, and one of the least watched, because it arrives through a feed from ICEGATE rather than from a supplier who can be chased. A short set of checks on each bill of entry, run between duty payment and the monthly return, catches wrong GSTINs, late reference dates and value amendments while they are still cheap to fix.

• What this guide covers: how IGST on imports becomes input tax credit, how bill of entry data flows from ICEGATE to GSTR-2B and the Invoice Management System, the reference date that sets the month, and how mismatches are corrected.
• What it adds: a matching query, a timestamped GSTIN error, a worked import posted in rupees beside a US entry in dollars, and a month-end checklist.

Where IGST on an import comes from and why it is a credit, not cost

IGST on imported goods is collected by customs on the bill of entry, alongside basic customs duty, and the importer can usually take it as input tax credit. The customs duties are cost; the IGST is a receivable from the moment it is paid until it appears in the credit ledger.

The first proviso to Section 5(1) of the IGST Act, 2017 provides that integrated tax on goods imported into India is levied and collected under Section 3 of the Customs Tariff Act, 1975, on the value determined under that Act, when customs duties are levied under Section 12 of the Customs Act, 1962. The bill of entry therefore carries the IGST line, and the duty challan pays it.

IGST paid on an Indian bill of entry is credited, not capitalised: Rule 36(1)(d) of the CGST Rules accepts the bill of entry as the credit document, and Ind AS 2 paragraph 11 excludes recoverable taxes from inventory cost, so the ERP should post 100% of eligible IGST to a receivable account.

On the credit side, Rule 36(1)(d) of the CGST Rules, 2017 lists a bill of entry, or a similar document prescribed under the Customs Act, for the assessment of integrated tax on imports, as a document on which credit may be taken. Section 16(2) of the CGST Act then sets the general conditions, which map to import records like this:

• Document held: the bill of entry naming the importer's GSTIN, kept with the import file.
• Goods received: the goods receipt note at the importing plant or warehouse after out of charge.
• Tax paid: the duty payment record from ICEGATE showing the IGST line settled.
• Return filed: the GSTR-3B in which the credit is claimed.

How the duty stack itself is computed, from assessable value through basic customs duty and Social Welfare Surcharge to IGST, is covered in our guide to Indian import landed cost. This article starts after the duty is paid and follows the IGST until it is claimed. Our older page on ICEGATE bill of entry and shipping bill reconciliation covers the customs-side ERP integration; this one stays on the GST side of the same document. Related import and tax guides are collected in the Logistics and Supply Chain hub.

From ICEGATE to GSTR-2B: how a bill of entry reaches the credit ledger

Bill of entry data reaches the GST portal from ICEGATE, not from any supplier filing, so the importer cannot ask a counterparty to upload it. What the importer controls is the accuracy of the bill of entry itself and the follow-up when a record does not arrive.

The GSTN's FAQ on GSTR-2B says the statement contains import of goods information from the ICEGATE system, available from the August 2020 GSTR-2B onwards, and warns that some imports, such as courier imports, may not be available. Records come in two sections: IMPG for bills of entry covering imports from overseas and IMPGSEZ for bills of entry covering goods received from a Special Economic Zone unit.

• Generation date: the FAQ states that GSTR-2B is generated for each month on the 14th day of the following month.
• Import cut-off: the same FAQ says the statement includes import data received within the 13th of the following month.
• Amendments: changes to value or GSTIN on an overseas bill of entry appear in an amendment section, IMPGA, which shows the difference between amended and original amounts.
• Invoice Management System: a GSTN advisory dated 30 October 2025 added an Import of Goods section to IMS from the October 2025 period, where bills of entry, including SEZ ones, can be acted on individually.
• Default action: the advisory says a bill of entry with no action is deemed accepted, and the portal builds the draft GSTR-2B on the 14th from the actions taken.

The flow below shows where each step sits, from the broker's filing to the credit in GSTR-3B. The import line in GSTR-3B's eligible credit table is populated from GSTR-2B, so a bill of entry missing from GSTR-2B usually means credit missing from the return unless someone adds it deliberately and keeps the evidence.

The ICEGATE reference date and the month a credit becomes visible

The month in which a bill of entry appears in GSTR-2B depends on its ICEGATE reference date, not the bill of entry date. For month-end cut-off, the controller should expect an import cleared in the last days of a month to land in the next month's statement.

The GSTR-2B FAQ defines the reference date as the out of charge date, the duty payment date or the amendment date, whichever is later. A bill of entry filed on 27 October with duty paid on 29 October and out of charge given on 3 November therefore carries a 3 November reference date. The FAQ also notes that details usually take some time after the reference date to reach the portal from ICEGATE.

The GSTR-2B period for an Indian import is set by the ICEGATE reference date, defined by the GSTN as the latest of out of charge, duty payment and amendment dates; an October bill of entry cleared on 3 November surfaces in the November statement generated on 14 December, one month later.

Practitioners differ on whether credit may be taken in the bill of entry's own month when the record appears later, because Rule 36(4), which ties credit to GSTR-2B, is written for invoices and debit notes reported by suppliers. Most finance teams avoid the argument by claiming in the month the record appears and keeping the receivable open until then. Whichever policy you choose, write it down and apply it to every bill of entry.

Record owners for import credit, from the broker to the tax manager

Import credit crosses four teams: the customs broker who files, logistics who tracks clearance, accounts who pay the duty and the indirect tax team who claim it. Each record needs one owner, and the GSTIN on the bill of entry needs a check by someone other than the person who keyed it.

The GSTIN check is the control that matters most. A group with several registrations under one PAN can have a bill of entry filed under any of them, and the broker usually works from a template. Give the broker a fixed mapping from each ship-to plant to its GSTIN, and have import logistics confirm the GSTIN on the checklist copy before the bill of entry is submitted, not after the duty is paid.

Six reasons a paid bill of entry is missing or wrong in GSTR-2B

Almost every gap between duty paid and credit visible traces back to one of six causes, and each has its own fix. Classify the cause before chasing anyone, because the route for a wrong GSTIN is customs, while the route for a late record is the portal.

• Reference date in the next month: clearance happened after month-end. No fix is needed; keep the receivable open and look for the record in the following statement.
• Record delayed on the portal: the GSTN FAQ says to use Services, then User Services, then Search BoE if data is not available after five days, and to press Query ICEGATE when the search finds nothing; the query status appears after about 30 minutes.
• Wrong GSTIN on the bill of entry: the credit sits with another registration. The fix is an amendment through customs, covered in the next section.
• Value or duty reassessed: a later assessment changes the IGST; the IMPGA section shows the difference, which may increase or reduce the credit.
• Courier or special clearance: the FAQ warns that some imports, such as courier imports, may not be available. Keep the bill of entry and payment proof and record the policy for claiming such items.
• Goods into a customs warehouse: IGST is paid when goods are cleared from the warehouse for home consumption, so the credit follows the ex-bond bill of entry rather than the into-bond one; our bonded warehouse comparison explains the two filings.

-- Match open import IGST receivables in the ERP to GSTR-2B / IMS import records
-- downloaded for every GSTIN in the group (sections IMPG, IMPGSEZ, IMPGA)
SELECT r.boe_no,
       r.port_code,
       r.boe_date,
       r.gstin              AS gstin_expected,
       g.gstin              AS gstin_on_portal,
       r.igst_paid,
       g.igst               AS igst_on_portal,
       g.ref_date,
       CASE
         WHEN g.boe_no IS NULL AND CURRENT_DATE - r.ooc_date <= 5 THEN 'WAIT'
         WHEN g.boe_no IS NULL                                       THEN 'SEARCH_BOE_THEN_QUERY_ICEGATE'
         WHEN g.gstin <> r.gstin                                     THEN 'WRONG_GSTIN_AMEND_BOE'
         WHEN ABS(g.igst - r.igst_paid) > 1                           THEN 'VALUE_DIFF_CHECK_IMPGA'
         ELSE 'MATCHED_READY_TO_CLAIM'
       END AS action
FROM   erp_import_igst_receivable r
LEFT JOIN portal_import_records g
       ON  g.port_code = r.port_code
       AND g.boe_no    = r.boe_no
       AND g.boe_date  = r.boe_date
WHERE  r.status = 'OPEN'
ORDER  BY r.boe_date;

-- Key: port code + bill of entry number + bill of entry date (a number alone can repeat across ports)
-- Tolerance: Rs 1 for rounding; any larger IGST difference is investigated, never absorbed
-- r.ooc_date: the later of out of charge and duty payment dates, a proxy for the reference date

Run the query weekly, not just at month-end. A wrong GSTIN found in the first week after clearance can be fixed while the broker still has the file open and the documentary evidence is easy to assemble; one found at the annual return stage turns into a much longer conversation with customs.

Correcting a wrong GSTIN or value through amendment and IMPGA

A bill of entry with the wrong GSTIN is corrected at customs, not on the GST portal. Section 149 of the Customs Act, 1962 lets the proper officer authorise amendment of a document after it is presented, and after clearance only on documentary evidence that existed when the goods were cleared.

That proviso is why evidence quality matters. A purchase order, commercial invoice and bill of lading naming the correct importing unit, together with its GST registration, are the documents that existed at clearance. A letter written afterwards explaining the mistake is not. Once the amendment is processed, the GSTR-2B FAQ says an ITC reversal entry for the incorrect GSTIN appears as the first entry in the IMPGA section, and the corrected record flows to the right registration.

A bill of entry filed under the wrong GSTIN is corrected through Section 149 of the Customs Act, 1962 using documents that existed at clearance; after amendment, GSTR-2B shows an ITC reversal for the wrong GSTIN in the IMPGA section, and the full IGST, ₹8,39,160 in this example, moves to the correct registration.

The trace below shows the error from the opening of this article. Times, numbers and amounts are illustrative.

1. 27 Oct, 16:05: the broker files bill of entry 4471209 at Nhava Sheva for the Maharashtra plant but keys the GSTIN of the Gujarat branch, state code 24 instead of 27.
2. 29 Oct, 11:20: accounts pay duty including IGST of ₹8,39,160 through the ICEGATE e-payment gateway; the ERP posts the IGST to the Maharashtra receivable account.
3. 3 Nov, 18:45: out of charge is granted; the reference date becomes 3 November and the record flows, unseen, to the Gujarat branch's IMS and GSTR-2B.
4. 14 Dec, 09:00: the Maharashtra draft GSTR-2B for November has no matching record. The weekly query was not running, so nobody looks until the January close.
5. 22 Jan, 15:30: the tax team finds the record in the Gujarat statement, assembles the purchase order, invoice and bill of lading naming the Maharashtra plant, and asks the broker to apply for amendment. Run weekly, the matching query would have flagged WRONG_GSTIN_AMEND_BOE on 10 November.

A worked import from duty challan to GSTR-3B, with a US contrast

The same consignment produces a cost and a credit in India, and only a cost in the United States. India's IGST on imports is recoverable through GSTR-3B; the US has no federal value-added tax on imports, so its column has no credit line to reconcile.

The example uses an illustrative assessable value of ₹42,00,000, basic customs duty at 10%, Social Welfare Surcharge at 10% of that duty and IGST at 18%. Rates depend on the tariff item and any exemption notification, so treat them as placeholders. The US column assumes an entered value of $50,000 and an illustrative duty rate of 4%; processing and harbour fees are covered in our MPF and HMF calculation guide.

The receivable balance at each month-end should equal the IGST on bills of entry paid but not yet visible in GSTR-2B, listed bill by bill. Any item older than two statements is either a wrong GSTIN, a courier clearance or a portal delay, and the matching query says which. For how the customs duties flow into unit cost, see our guide to capitalising landed cost into inventory.

Automated matching rules and the judgement calls left to the tax team

Matching bills of entry to portal records, ageing the receivable and flagging GSTIN or value gaps are rules a script should run every week. Choosing the claim month for a disputed item, deciding whether to claim a courier import that never appears, and approving an amendment request are decisions for the tax manager.

Keep any extraction tool out of the claim path. A model that reads a bill of entry image can speed up a manual reconciliation, but the value claimed must come from the portal record or the ICEGATE copy, because those are what an officer will compare against GSTR-3B.

Month-end import credit checklist for logistics finance controllers

Close each month with a bill-by-bill list of open IGST receivables, each tagged with its cause and next action, and claim only what the GSTR-2B or IMS record supports. A single unexplained balance is the warning sign, whatever its size.

If you are choosing tax, customs or ERP tools to automate these checks, ask each vendor to show the GSTIN mismatch case end to end, from the bill of entry to the IMPGA reversal. Weighted evaluation criteria built from these checks can go straight into a tender through our RFP service.