1. The common assumption
A company receives a tender requirement: “commercial invoice, legalized.”
It notarises, secures foreign ministry authentication, and submits for embassy legalization.
2. Why it sometimes fails
Because “legalized” in the requirement may describe a chain the destination defines differently from the one in China.
Two failures recur:
The destination wanted commercial certification before legalization and the exporter went straight from the notary to the foreign ministry.
The destination wanted several documents legalized together and only one was submitted.
3. The Greek example
Some markets require that the invoice be legalized together with the certificate of origin.
Submitting the invoice alone returns the file.
4. The translation sequencing error
Translation must be part of the notarised document.
A translation added between the foreign ministry step and the embassy step is outside the certified bundle, and it is refused.
5. The amendment clause problem
Some destinations, Egypt among them, require that the contract not contain a clause stating the agreement must be notified to the embassy on amendment.
Legalization is refused until the clause is removed and the contract re-signed.
6. The consignee mismatch
Where the invoice is legalized and the certificate of origin is legalized separately, the two are compared.
Different buyer names in the two documents is a frequent ground for refusal.
7. A working approach
Ask the importer for the exact required wording, not a summary.
Ask which documents must be submitted together.
Confirm the language and the notarisation sequencing.
Build four weeks into the plan.
8. Closing view
Legalization failures are rarely failures of procedure. They are failures of specification.
The chain is standard. The destination’s version of it is not.
*This article is based on China’s consular authentication regulations, updated October 2026, and embassy practice.*