Business Japanese email: structure, set phrases and a template you can reuse

Here is the thing nobody tells learners early enough: a Japanese business email is not composition, it is assembly. Roughly the first four lines and the last two are fixed formulas that every writer in every industry uses in the same order, and only the middle is yours. That is enormously good news. Once you have the skeleton and about fifteen set phrases, you can write a competent, unremarkable, entirely appropriate email — and unremarkable is exactly the goal. This guide gives you the structure line by line, the phrases with readings, the title rules that trip up foreigners, and two complete worked examples you can adapt today.

1. Why the openings and closings are formulas, not writing

English business email rewards a little personality: a warm opener, a distinctive sign-off, some variation to show you are a human being. Japanese business email rewards the opposite. The conventional phrases function as a handshake — they signal that you know the protocol and that the relationship is being handled correctly. Deviating from them does not read as creative; it reads as either careless or oddly familiar.

Consider いつもお世話になっております (いつも おせわに なっております). Translated literally it means something like "you are always taking care of me", which sounds strange and rather intimate in English. In practice it means precisely nothing beyond "this is a business email between people who have dealt with each other before". No Japanese reader parses it semantically, any more than an English reader parses "Dear". Its function is positional: it goes on the line after the address block, and its absence is conspicuous.

This is liberating for a learner. You do not need to invent language for the hardest, most face-sensitive parts of the message. You need to memorise them, place them correctly, and spend your actual Japanese ability on the two or three sentences in the middle that carry information. The register these formulas live in is 敬語 (けいご) — if the honorific system itself is still hazy, read the keigo basics guide alongside this one, because every phrase below is an application of the humble and honorific patterns it explains.

2. The skeleton, line by line

A standard external business email has seven parts, in this order, with a blank line between each block:

1. 件名 (けんめい) — the subject line. Written before anything else and treated as functional, not conversational. More on conventions in section 8.
2. 宛名 (あてな) — the address block. Company, then department, then name plus 様, each on its own line: 株式会社さくら商事 / 営業部 / 田中太郎様 (かぶしきがいしゃ さくらしょうじ / えいぎょうぶ / たなか たろう さま). Write the company name in full — 株式会社 is not abbreviated to (株) in the address block of an email you care about.
3. 挨拶 (あいさつ) — the greeting formula. いつもお世話になっております for an existing contact; 初めてご連絡いたします (はじめて ごれんらく いたします) for a first approach.
4. 名乗り (なのり) — self-identification. Company + の + your name + です/と申します: 株式会社ミライの山田と申します (かぶしきがいしゃ ミライの やまだと もうします). と申します is the humble form and is standard on first contact; です is fine once you correspond regularly. Note the の — you belong to the company, so the company comes first.
5. 用件 (ようけん) — the purpose statement. One sentence stating why you are writing, before any detail: 〜の件でご連絡いたしました (〜のけんで ごれんらく いたしました). Japanese business readers expect the topic up front; burying it three paragraphs down is a genuine discourtesy.
6. 本文 (ほんぶん) — the body. Short paragraphs, generous line breaks, and bulleted specifics for dates, quantities and deadlines. Japanese business email is typically hard-wrapped at a comfortable line length rather than left to flow, and lists are set off with ・ or 記 blocks.
7. 結び (むすび) and 署名 (しょめい) — the closing and signature. Almost always よろしくお願いいたします or the more formal 何卒よろしくお願い申し上げます, followed by a signature block with company, department, name, address, phone and email, usually fenced off with a line of dashes.

Two formatting habits mark out a careless email immediately. First, no blank lines: a Japanese business email that arrives as one dense block looks aggressive, because whitespace between blocks is part of the convention. Second, missing the address block entirely and starting with the greeting — that is acceptable in a fast internal thread, never in external correspondence.

3. The set phrases worth memorising

These are the load-bearing phrases. Learn them as single units, the way you learned いただきます — do not try to parse every morpheme before you use them.

Notice how many of these are humble forms: いたします (from する), 申し上げます (from 言う), いただく (from もらう), ございます (from ある). That is the engine of the whole register — you lower your own actions to raise the reader. Every one of them is drawn from the small set of irregular humble and honorific verbs, which is why learning that set pays for itself so quickly.

4. Titles: 様, さん, 御中, 各位, and the 殿 trap

Getting the honorific title wrong is the most visible error you can make, because it is in the first line and it is aimed directly at the reader.

• 様 (さま) — the standard written title for an individual outside your organisation. 田中太郎様, or 田中様 once the relationship is established. Use it in the address block of essentially every external email.
• さん — for colleagues inside your own company, in internal email and speech. Using さん to an external client in writing reads as too casual; using 様 to the person at the next desk reads as sarcastic.
• 御中 (おんちゅう) — for an organisation when you are not naming an individual: 株式会社さくら商事 御中, or 営業部 御中. The critical rule: 御中 and 様 never appear together. ×株式会社さくら商事御中 田中様 is wrong. Once you name a person, the company line simply takes no title: 株式会社さくら商事 / 営業部 / 田中様.
• 各位 (かくい) — "to all concerned", for a group: 関係者各位 (かんけいしゃ かくい), 社員各位 (しゃいん かくい). 各位 is already honorific, so ×各位様 is a doubled title and wrong. (You will nonetheless see お客様各位 widely used in practice; it is established enough to be safe, but it is the exception, not a licence to stack titles generally.)
• Job titles are titles. 部長 (ぶちょう), 課長 (かちょう) and 社長 (しゃちょう) carry respect by themselves, so 田中部長 is correct and ×田中部長様 is a doubled title. If you want 様, restructure: 営業部 部長 田中様.
• 殿 (どの) — historically used downward, from an organisation to an individual, and it survives mainly on formal internal documents and official notices. Addressed to a client or a superior in ordinary email it lands as either stiff and archaic or faintly condescending. As a learner, simply never use it; 様 covers every case where you might have been tempted.

5. Worked example 1 — making a request

Yamada, at a company called ミライ, is asking Tanaka at さくら商事 for a written quotation. Each line below gives the Japanese and its English gloss.

• 件名:【お見積りのお願い】ウェブサイト制作について(株式会社ミライ 山田) — "[Request for quotation] Regarding website production (Mirai Inc., Yamada)"
• 株式会社さくら商事 — the recipient's company, on its own line
• 営業部 田中太郎様 — "Sales Department, Mr Taro Tanaka"
• いつもお世話になっております。 — the fixed greeting
• 株式会社ミライの山田と申します。 — "This is Yamada of Mirai Inc."
• 早速ですが、先日ご相談いたしましたウェブサイト制作の件で、お見積書をご送付いただきたくご連絡いたしました。(せんじつ ごそうだん いたしました ウェブサイト せいさくの けんで、おみつもりしょを ごそうふ いただきたく ごれんらく いたしました) — "To come straight to the point: I am writing to ask you to send a quotation for the website production we discussed the other day."
• つきましては、下記の内容でご検討いただけますでしょうか。(つきましては、かきの ないようで ごけんとう いただけますでしょうか) — "Accordingly, could you consider it on the terms below?"
• ・ページ数:10ページ程度(ページすう:10ページ ていど) — "Number of pages: around 10"
• ・希望納期:10月末(きぼう のうき:10がつまつ) — "Desired delivery: end of October"
• ・お見積書のご提出期限:8月20日(おみつもりしょの ごていしゅつ きげん) — "Quotation due by 20 August"
• お忙しいところ恐れ入りますが、ご検討のほどよろしくお願いいたします。(おいそがしい ところ おそれいりますが、ごけんとうの ほど よろしく おねがい いたします) — "I am sorry to trouble you when you are busy; I would be grateful for your consideration."
• 署名: 株式会社ミライ 営業部 / 山田 花子(やまだ はなこ)/ TEL: 03-0000-0000 / Email: [email protected] — the signature block, fenced above and below with a line of dashes

Three things to notice. The purpose appears in the first body sentence, not the last. 下記 (かき, "the following") formally introduces the bulleted specifics, and its partner 上記 (じょうき, "the above") refers back to them later. And the request is wrapped in a cushion — お忙しいところ恐れ入りますが — placed immediately before the ask, which is where cushions go in Japanese: not at the start of the email, but against the imposition itself.

6. Worked example 2 — replying and acknowledging

Now Tanaka replies. Replies are shorter, keep the Re: subject line intact so the thread stays traceable, and follow the same skeleton with the greeting shortened.

• 件名: Re:【お見積りのお願い】ウェブサイト制作について — keep the original subject; do not invent a new one mid-thread
• 株式会社ミライ / 営業部 山田花子様 — the address block, same rules
• お世話になっております。株式会社さくら商事の田中です。 — "Thank you for your continued support. This is Tanaka of Sakura Shoji." (いつも may be dropped in a live thread; と申します becomes です once you are known to each other.)
• このたびはお問い合わせいただき、誠にありがとうございます。(このたびは おといあわせ いただき、まことに ありがとうございます) — "Thank you very much for your enquiry."
• お見積書の件、承知いたしました。(おみつもりしょの けん、しょうち いたしました) — "Regarding the quotation: understood."
• 8月18日までにご送付いたします。(8がつ 18にちまでに ごそうふ いたします) — "I will send it to you by 18 August." Note the humble いたします, and that a concrete date is given rather than 近日中に.
• ご不明な点がございましたら、お気軽にお申し付けください。(ごふめいな てんが ございましたら、おきがるに おもうしつけ ください) — "If anything is unclear, please do not hesitate to let me know."
• 取り急ぎ、ご連絡申し上げます。何卒よろしくお願い申し上げます。 — "A brief note for now. Thank you very much."

If the quotation were attached, the natural line would be: お見積書を添付いたしましたので、ご査収のほどよろしくお願いいたします。(おみつもりしょを てんぷ いたしましたので、ごさしゅうの ほど よろしく おねがい いたします) — "I have attached the quotation; please check it over." ご査収 specifically means "receive and inspect", so it belongs with attachments and nowhere else — attaching it to a message with no enclosure is a small but noticeable error.

7. Internal versus external: two different registers

Japanese draws a sharp line between うち (in-group: your own company) and そと (out-group: everyone else), and email register follows it exactly.

Internally, the greeting is お疲れ様です (おつかれさまです) rather than お世話になっております, colleagues take さん or their job title, the address block often collapses to a single line, and the cushioning phrases thin out considerably. 営業部の山田です。お疲れ様です。 is a perfectly complete opening to a colleague. Keigo is still present — you would not write in plain form to a 部長 — but it is lighter and faster.

Externally, two vocabulary pairs matter. Your own company is 弊社 (へいしゃ) — humble — or the neutral 当社 (とうしゃ). The recipient's company is 貴社 (きしゃ) in writing and 御社 (おんしゃ) in speech; that written/spoken split is a real convention and swapping them in an email is a small tell. So: 弊社の担当者がご説明いたします (へいしゃの たんとうしゃが ごせつめい いたします) — "our representative will explain".

The rule that most surprises learners: when writing to an outsider about your own boss, your boss becomes in-group and loses their honorific. You write 弊社の田中が伺います (へいしゃの たなかが うかがいます) — "Tanaka from our company will visit you" — dropping both the 部長 and the さん, and using the humble 伺う for his action even though he outranks you. Writing ×弊社の田中部長がいらっしゃいます to a client elevates your own side and is a genuine social error, not a stylistic quibble. Internally, the same sentence would of course be 田中部長がいらっしゃいます.

8. Mistakes that get noticed

• 了解しました upward. (りょうかいしました) It is fine between peers and common in casual work chat, but toward a client or a superior the expected forms are 承知いたしました or, in service contexts, かしこまりました. This is probably the single most-corrected phrase in Japanese new-employee training.
• Over-stacked keigo (二重敬語, にじゅうけいご). One honorific layer per verb. ×おっしゃられる should be おっしゃる; ×ご覧になられる should be ご覧になる; ×お伺いさせていただきます piles humble on humble and should simply be 伺います. More politeness is not more polite past the first layer — it reads as insecure.
• Overusing 〜させていただきます. The construction properly implies that you have the other party's permission and that you benefit. 参加させていただきます ("I will attend, with your kind permission") is fine; sprinkling it on every verb in the email is a well-known tic that native readers notice.
• Doubled titles: ×各位様, ×田中部長様, ×株式会社〇〇御中 田中様. Covered in section 4, and worth a final check before you press send, because they sit in line one.
• Subject-line failures. An empty subject, a bare お世話になっております as the subject, or something as vague as ご連絡. Japanese business inboxes are triaged from the subject line, so name the matter and add your company and name in brackets: 【ご確認のお願い】8月納品分の数量について(株式会社ミライ 山田). Bracket prefixes such as 【ご依頼】【ご確認】【重要】 are conventional and helpful.
• 殿 to a client, or ご苦労様です to a superior. Both are downward-facing expressions. Use 様 and お疲れ様です respectively.
• すみません where 申し訳ございません belongs. (もうしわけございません) すみません is conversational; a written apology to a client for a real error needs the full form, often as 大変申し訳ございません.
• Vague dates. 近日中に or なるべく早く in a business email invites a follow-up asking what that means. Give the date: 8月18日までに.

9. How this fits into keigo study and exam preparation

Business email is the most concentrated, most practical application of keigo there is, which makes it an unusually efficient way to study the honorific system. The phrases in section 3 are not decorative extras — they are the humble and honorific verb forms in their highest-frequency real-world habitat. Learn the keigo irregular pairs first as vocabulary, then meet them again here doing a job, and both halves stick better than either alone.

For exams, this material maps far more directly onto the JPT than onto the JLPT. The JPT is a 990-point test across 200 questions — 100 listening, 100 reading — with no pass or fail, and its reading half leans heavily on workplace documents: emails, notices, memos, forms. Questions built around exactly the phrases above are routine. If a Japanese-speaking job is your goal, work through the JPT test guide for the format, then the JPT module, whose 5,862 words are banded by target score. The JPT 600 list is the usual starting band for business-functional vocabulary, with the JPT 800 and JPT 900 lists covering the more formal written register that documents like these are built from.

A practical way to build the habit: keep a personal template file with the skeleton from section 2 and three or four variants of the middle — a request, an acknowledgement, an apology, a scheduling message — and fill in rather than compose. Add each new phrase you meet in real correspondence to your review deck as a whole chunk, phrase on one side and situation on the other, and run the unfamiliar readings back through a flashcard session until they are automatic; 査収, 恐縮 and 何卒 are words you will almost never meet in conversation but read constantly in email. Within a few weeks the openings and closings become automatic, and your attention goes where it belongs — the two or three sentences in the middle that actually say something.