What happens when an error on your certificate of origin is challenged at destination

Every write-up of the certificate of origin covers the same ground: what it is, and which type you need. Almost none of them cover the moment that actually costs money. The goods have already left India, and your buyer's customs has just told them the certificate does not support the lower duty it was supposed to.

What the error actually looks like#

It is rarely a forged document. It is usually one of three ordinary things.

A field that does not match the rest of the set. The description, the HS code or the quantity on the certificate reads differently from the invoice or the packing list. This is the same reconciliation problem that runs through the whole document set. The certificate is one more document that has to agree with the others, and nothing checks that it does before it is submitted.

A certificate on the wrong format. Trade agreements get amended: a new protocol, a revised template, a changed list of data fields. The old format keeps circulating because someone is still working from a saved copy or a link a colleague sent last year. A certificate correctly filled in on a superseded format can be rejected on that ground alone.

An origin claim the goods don't actually meet. The certificate says the goods qualify under a specific trade agreement, and they don't. The value-addition threshold was assumed rather than calculated, or the product had its own stricter rule that nobody checked. How origin is decided, and where exporters usually get it wrong covers that half; this article is about what happens once the wrong claim has already been made and someone downstream has noticed.

Preferential or non-preferential decides which failure you're in#

A preferential certificate supports a claim to a lower duty rate under a specific trade agreement, and it is what most of the errors above affect. A non-preferential certificate simply states where the goods came from, for customs clearance, a trade remedy, or a buyer's own compliance requirement, and carries no duty benefit to lose. DGFT's own platform draws this line in those terms: a preferential certificate is issued under a free trade, regional or preferential trade agreement to obtain a tariff concession in the importing country, while a non-preferential one is issued for clearance and compliance purposes with no such benefit attached.

Sending the wrong type, or a preferential certificate under the wrong agreement, produces the same outcome as an error inside a correct one: the concession is not available.

What happens at the destination#

The importing country's customs does not need proof of fraud to act. A doubt is enough: a mismatch against the other documents, an unfamiliar format, or a reasonable suspicion that the origin criterion was not actually met.

The preferential rate is refused and the standard duty applies, at least provisionally, while the question is resolved. India runs the identical machinery for the reverse case, where an importer into India claims a preferential rate: the Customs (Administration of Rules of Origin under Trade Agreements) Rules, 2020, known as CAROTAR. It sets out exactly this sequence. On a doubt about a certificate's genuineness, or about whether the origin criterion is actually met, the claim is checked before it is accepted, and the goods may be cleared provisionally, or held, while that happens.

A verification query goes back to whoever issued the certificate. Under CAROTAR, India's own customs sends that query to a single designated point, the Director of International Customs at the CBIC, and the same circular states that where a claim is ultimately denied, the certificate is forwarded on for "onward communication to the exporting country, where required." That is the same channel running in reverse when your buyer's country is the one asking. The query lands with the authority in India that issued your certificate, not with you directly, though your exporting agency will in practice come straight back to you for the underlying paperwork.

How that query travels is getting faster to check, at least for the document itself. DGFT's Trade Connect ePlatform now carries a Certificate Verification API alongside the application system. The document itself can now be checked quickly, by its file number, certificate number and date, returning its status and a link to the certified PDF, without a written request through diplomatic channels. That settles whether the document is genuine quickly. It does not settle whether the origin claim on it is correct. That still depends on the calculation behind it, and a query on that point takes as long as it takes someone in India to produce the working papers.

If nothing satisfactory comes back, the duty stays at the standard rate. This is not unique to India's trade partners: it is how USMCA's own origin chapter writes it, for instance — preferential treatment is denied if the claim cannot be substantiated, if the certificate is defective and not corrected within the window given, or if nobody responds to the query at all. Other agreements use similar structures, with their own windows and wording, so check the one your buyer is actually claiming under.

The bill lands on your buyer. The cost still comes back to you. The importer pays the difference, and while the goods themselves are rarely returned over a paperwork question, a hold runs up charges in several places at once if the consignment is stopped rather than cleared provisionally. Either way, a buyer who quoted a price assuming the concession and did not get it is a commercial problem for you, whatever the customs paperwork says.

Before you promise the benefit, and once it's held#

Prevention is the cheap version of all of this. Apply through the current platform and the current format rather than a saved template — a certificate on a superseded format fails for a reason that has nothing to do with your goods. Read the certificate against the invoice and the packing list before it is submitted, the same way you would any other document in the set. And confirm the origin claim against the specific agreement's own rule for your product, not the general summary, before it goes on the certificate at all.

Recourse once it's held is narrower, and speed matters. A format or transcription defect is usually correctable within whatever window the agreement allows. Get the corrected certificate back to the issuing authority immediately, because that window is short and does not wait for a convenient moment. A genuine origin problem is a different conversation: keep the bills of materials, the input invoices and the value-addition working that actually support the claim, because a certificate with nothing behind it answers no query at all.