End-User Certificates and Pledges (Seiyakusho) in Japanese Export Control | A Beginner's Guide to the Required Documents, Timing, and How to Fill Them Out [2026 Edition]

Hello, this is Hamamoto from TIMEWELL. An overseas customer asks you to "send an end-user certificate so we can obtain the export license." Or, the other way around, your own company prepares an export license application and finds an unfamiliar item on the list of required attachments: a "pledge of the consignee and end user" (juyousha-tou no seiyakusho / 需要者等の誓約書). People who have just started working in export control ask me about these two situations all the time.

What makes this document tricky is that it goes by many names depending on the context: the pledge (seiyakusho), the pledge of the consignee and end user, the End-Use Certificate (saishuu youto seiyakusho / 最終用途誓約書), the end-user certificate, or the End-User Certificate — EUC for short. The names differ, but they all point to roughly the same thing: a document in which the party that will actually use the exported goods or technology commits in writing to who will use them, where, and for what purpose. In this article, I will walk first-timers through the topic step by step — how the formal names map to the common ones, which forms exist, when to obtain the document, and what to watch out for when it is filled in. If you are not sure whether your company's export control framework is in decent shape to begin with, we offer a free export-control readiness check — feel free to run through it as you read.

What Are the Pledge and the End-User Certificate? Sorting Out the Names First

Let me start with some traffic control on terminology. If you stumble here, everything that follows becomes fuzzy.

When you apply to the Ministry of Economy, Trade and Industry (METI) for an export license, one of the attachments you submit is the "pledge of the consignee and end user" (juyousha-tou no seiyakusho). The "consignee and end user" (juyousha) means the party that will actually use the exported goods or the provided technology. The title printed on the form itself is "End-Use Certificate" (saishuu youto seiyakusho)[^1]. A helpful way to keep these straight: "pledge of the consignee and end user" describes the document's role in the application, while "End-Use Certificate" is the title of the document itself.

The end-user certificate, on the other hand, is the international common name. The end user is the party that ultimately uses the goods or technology, and the end use is the purpose it is put to. In the world of export control, most countries require a similar document, and these are collectively called End-User Certificates, or EUCs. Japan's pledge of the consignee and end user is a member of this family. In email exchanges with overseas business partners, it will most often appear as an "EUC" or an "End-Use Statement."

If you are dealing with a non-Japanese counterparty, this mapping between names is more than trivia. When a customer in Japan asks you for an "EUC," they mean the same document that their license application checklist calls the pledge of the consignee and end user. And when a Japanese exporter asks its overseas buyer for a "seiyakusho," what lands in the buyer's inbox will look, to them, like an ordinary End-Use Statement. Knowing that all of these labels resolve to one document saves a great deal of back-and-forth.

There is one more document that beginners easily confuse with the pledge: the classification report, often called a non-applicability certificate (gaihi hantei-sho / hi-gaitou shoumeisho). That document shows the result of the exporter's own determination of whether the goods or technology fall under the control lists — a completely different role from the pledge. The classification report is a document in which the exporter explains "what this item is"; the pledge is a document in which the user promises "what this item will be used for." That distinction is worth memorizing. We cover the classification report in detail in our guide to classification reports and non-applicability certificates, and reading the two together should give you the full picture.

Why Is This Document Required? Start from FEFTA and the Export License System

Why does the counterparty have to go as far as signing a pledge in the first place? The background lies in the mechanics of Japan's basic export control statute, the Foreign Exchange and Foreign Trade Act (FEFTA, gaitamehou / 外為法)[^2].

When goods are exported from Japan or technology is provided overseas, a license from the Minister of Economy, Trade and Industry may be required depending on what is involved. The legal basis is Article 48 of FEFTA for the export of goods and Article 25 for the provision of technology[^2]. Which goods and technologies are covered is spelled out in detail in cabinet orders such as the Export Trade Control Order[^3].

The important point here is that the license review looks at more than just the "what." The review evaluates, as a set, what is being transferred, to whom, and for what use. Take the same machine tool: selling it to a small factory that machines parts for civilian products and selling it to an organization suspected of missile development carry entirely different risks. The document that substantiates the "to whom" and the "for what" is precisely the pledge of the consignee and end user. Beyond the paperwork logic, the pledge also creates a contract-like commitment between the exporter and the end user — no unauthorized resale, no use outside the promised purpose.

Verifying the end use and the end user matters even for goods that do not fall under the control lists. Under the catch-all controls — formally, the Complementary Export Controls — goods and technologies that are not listed can still require a license if there is a risk of their being used for weapons of mass destruction or similar ends[^4]. And the two inputs for judging whether such a risk exists are exactly end-use verification and end-user verification. METI publishes materials to support that judgment, including the "Clearly Evident Guidelines" (akiraka guideline) and the Foreign End User List[^5]. Note that the Complementary Export Controls were revised with effect from October 9, 2025[^6], so the fine details of the requirements are in motion. For any actual determination, always check METI's latest public notices and Q&A. For the overall structure of the catch-all controls, see our plain-language guide to the three requirements of the catch-all controls.

One caution I want to put on the table early: the pledge is not a magic wand. METI's own completion instructions state explicitly that even where a pledge has been submitted, a license may still be denied based on an individual assessment from the standpoint of maintaining international peace and security[^1]. The pledge is not a ticket that guarantees approval; it is one piece of evidence considered in the review. Keeping that distance in mind from the outset will keep your expectations realistic in day-to-day practice.

The Pledge Forms Are Prescribed: Form 2 Versus Form 3

So what does the actual document look like? The pledges used in Japanese export license applications follow forms prescribed by METI's Submission Documents Circular, and the forms can be downloaded from the official website[^7]. This is not a document you draft from scratch. This point is misunderstood surprisingly often — I hear of cases where a company creates its own template in Word, sends it to the counterparty, and later has to have it redone. METI itself states plainly that a pledge not prepared in accordance with the completion examples may need to be replaced[^1].

Which form to use depends on whether the end user has been identified. Here is the breakdown[^1]:

Situation	Form to use	English version	Notes to the pledge
End user has been identified	Form 2 (End-Use Certificate)	FORM 2	Appendix 3-1
End user has not been identified (e.g., resale via a trading company)	Form 3 (End-Use Certificate)	FORM 3	Appendix 3-2
Sensitive items such as carbon fiber, certain chemicals, and artificial graphite	Item-specific dedicated forms such as Form 2 (2-17) and Form 4	Available	Appendix 3-2-1 etc., depending on the item
Transactions providing design or manufacturing technology related to weapons of mass destruction	Form 2 with all additional pledge clauses included	FORM 2	Appendix 3-1

In practice, you often know the trading company you are selling to, but the onward resale destination is not yet fixed. That is when Form 3 comes in. Form 3 includes a field for listing anticipated resale destinations where they can reasonably be foreseen — METI gives the example of replacement-part stock for goods exported in the past[^1]. Conversely, if the end user is clearly identified, use Form 2. For items of particular concern for diversion to nuclear or chemical weapons — carbon fiber, chemicals at specified concentrations, artificial graphite — dedicated forms are provided[^1].

Why does it matter so much that you use the prescribed form rather than your own wording? Because the pledge is reviewed as part of a license application, and the reviewer needs to see the specific commitments the form is designed to capture — the identity of the end user, the concrete end use, and the re-export consent clause — expressed in the prescribed structure. A home-made template that omits or rephrases any of these invites a replacement request, and a replacement request means another multi-week round trip to the counterparty for a fresh signature. Using the official form the first time is by far the cheaper path.

A quick note on language. METI's forms come in Japanese and English versions, and the website of CISTEC (Center for Information on Security Trade Control, a general incorporated foundation that provides export control information) also carries Chinese-language versions of the pledge together with completion instructions[^8]. Sending a Japanese form to a contact in the destination country will get you nowhere, so knowing that English and Chinese versions exist will speed up your work considerably.

Timing and Completion: Getting Ahead of the Common Stumbling Blocks

Now that you know what the document is, let us get into the practical questions — when, who, and how.

Timing first. Because the pledge is an attachment to the export license application, it needs to be in hand before you apply[^9]. And remember, this document is written not by your company but by the other side. You send the form to the overseas buyer or end user, they route it through their internal approvals, obtain a signature at the representative level, and mail the original back to Japan. It is not unusual for that round trip alone to take several weeks. In my experience, the realistic approach is to start the pledge process at the same time as contract negotiations. If you wait until the contract is signed and then bring up the pledge, the counterparty says "nobody told us about this" and your shipping schedule collapses. Tell them at the quotation or contract stage that a pledge will be required for the license application. That one step prevents the majority of trouble.

Next, the key points on completion, taken from METI's completion instructions[^1]. The signatory must be a representative of the consignee or end user, or a person delegated by that representative. Where a delegated person signs, a copy of the document evidencing the delegation must be attached. The supplier field — effectively the addressee — shows the name of the Japanese exporter. In the intended-use field, the counterparty is expected to be as specific as possible: what will ultimately be manufactured using the goods, and in which process and how the goods will be used. One-word answers like "industrial use" or "research use" will not pass. Submission is one original and one copy each; after the contents are checked, the original is returned[^1]. The core substance of the pledge concerns re-export: if the exported goods are to be re-exported to a third country or resold, the end user must obtain the Japanese exporter's prior written consent[^1].

Here is where practice gets genuinely hard: confirming whether the counterparty really is a trustworthy end user. Paper is only paper — if the organization signing it is dubious, the signature means nothing. Checking against the Foreign End User List, looking into past violations, probing links to military-related organizations: there is a lot to investigate, and doing it by hand for every transaction is a serious burden. As an aside, the single most common thing I hear when advising in this area is: "We know how to check — we just cannot keep up with the volume." Our export control AI agent TRAFEED is a tool that supports this kind of end-user concern screening and preliminary classification work. Drawing on a knowledge graph of more than 200 million records, including academic papers, patents, and researcher information, it visualizes the concern level of a counterparty in five seconds. Its AI assessments run at over 95% accuracy (based on a joint demonstration with Okayama University using roughly 30,000 past review records; in-house figures) — but the principle stands: the final classification decision and the go/no-go call on a transaction rest with your company's export control officer. The tool exists to speed up the preparation, nothing more. For the thinking behind end-user verification itself, see our article on end-user screening and customer due diligence.

Collecting the Pledge Is Not the End of the Story

Finally, let us talk about what happens after you collect the pledge. Many explainers skip this part, but in practice this is where the real work begins.

The pledge's effect does have an exit. According to METI's completion instructions, the prior-consent obligation under the pledge lapses when the exported goods have been consumed, when the provided technology has entered the public domain, when the item no longer meets the controlled specifications, or when a regulatory amendment renders it non-controlled[^1]. Put the other way around: until one of those things happens, the pledge remains alive. If the exporter learns that the exported goods have been resold to someone other than the original end user, METI provides a form for reporting and sharing that information with the ministry[^1]. The system assumes you keep paying attention to where the transaction goes after export — it is not sell-and-forget, file-and-forget.

That is exactly why I recommend treating the pledge not as a one-off piece of paperwork but as a component of your company's export control framework. Classification, end-use and end-user verification, obtaining the pledge, post-export follow-up: decide who handles each step of that chain, and in what order. A company that has this sequence written down — even roughly — handles a request for an EUC from a customer, or a pledge requirement on its own application, as routine work rather than a fire drill. A company that has not tends to rediscover the whole process from scratch every time a shipment comes up, with the schedule risk that entails. METI's introductory Security Trade Control Guidance[^10] is a good, free starting point for building that framework, and CISTEC's FAQ[^11] has accumulated answers to the finer questions of daily practice. The details of the system shift with each amendment, so even for the material covered in this article, always verify against METI's latest public notices and forms when you actually apply[^12].

At bottom, both the pledge and the end-user certificate exist for one purpose: making sure that what your company sold does not turn into a weapon somewhere you never intended. The document names and form numbers can simply be memorized — but the counterparty vetting and continuous management that sit behind them cannot be run as a side job. If you would like to discuss concretely where your company should start, please book a consultation. Let a single pledge form be your entry point into putting the whole of your export control house in order.

References

[^1]: Completion Instructions for the Pledge of the Consignee and End User — METI Security Export Control — accessed July 2026 [^2]: Foreign Exchange and Foreign Trade Act (Act No. 228 of 1949) — e-Gov Legal Database — accessed July 2026 [^3]: Export Trade Control Order (Cabinet Order No. 378 of 1949) — e-Gov Legal Database — accessed July 2026 [^4]: Complementary Export Controls (Catch-All Controls) — METI — accessed July 2026 [^5]: Q&A on the Foreign End User List, Examples of Goods of High Concern, and the "Clearly Evident Guidelines" — METI — accessed July 2026 [^6]: Revision of the Complementary Export Controls (effective October 9, 2025) — METI Trade and Economic Security Bureau — October 2025 [^7]: Forms Attached to the Submission Documents Circular — METI — accessed July 2026 [^8]: License Application Procedures (including Chinese-language pledges) — CISTEC (Center for Information on Security Trade Control) — accessed July 2026 [^9]: Documents and Notes for Export License, Service Transaction License, and Specified Recording Media Export License Applications — METI — accessed July 2026 [^10]: Security Trade Control Guidance (Introductory Edition), Version 3.0 — METI — March 2026 [^11]: FAQ on Export Control — CISTEC (Center for Information on Security Trade Control) — accessed July 2026 [^12]: Application Flow (For First-Time Exporters) — METI — accessed July 2026