3.4 Fixed Business Expressions and Email Formulae (頭語, 結語, クッション言葉)

3.4 Fixed Business Expressions and Email Formulae (頭語, 結語, クッション言葉)

Quick Answer: Japanese business email is a templated genre: 頭語 (opening), 季節の挨拶 (seasonal greeting), クッション言葉 (cushion), body, 結び (closing), 結語 (closing greeting). Mismatching the pair (拝啓 without 敬具) or the season (師走 in May) is an instant BJT error.

頭語 (Opening Greeting) and 結語 (Closing Greeting)

These come as fixed pairs:

Trap: 拝啓 must be paired with 敬具. Writing 拝啓 and closing with 早々 is a mismatch. 前略 exists to skip the seasonal greeting — appropriate for in-house or urgent mail, never for a first-time customer contact. 返信用の頭語: when you reply to a formal email that opened with 拝啓, open with 拝復 (haifuku) and close with 敬具. When the sender used 謹啓, a reply in kind (謹啓 → 敬白/拝具) shows you have registered the elevated register; downgrading to 拝復 is not strictly wrong but signals a slight drop in politeness.

季節の挨拶 — Seasonal Openings

Generic opening line used year-round when you are unsure of the season:

貴社におかれましては益々ご清栄のこととお慶び申し上げます。

Seasonal couplet patterns (paired with month):

Trap: greeting must match month. A May email opening 師走の候 is a visible BJT error. When in doubt, use the generic 貴社におかれましては…

ときの挨拶 variants and formality ranking. The seasonal suffix is not free variation: ～の候 is the most formal and is standard in written business letters; ～の折（おり） is slightly less formal and common in email; ～のみぎり is the least formal of the three and tends to appear in in-house or semi-formal email, not in customer-facing letters. A BJT trap is to mix them within one mail (新緑の候、…若葉のみぎり…) — choose one suffix and keep it consistent. When in doubt, use the generic 貴社におかれましては…

宛名 — Addressing

The hard rule: 様 for an individual, 御中 for a department or organization. Never combine 御中 with a personal name (山田 御中 is wrong) and never write 御中 様 (double suffix). The canonical address order is 会社名 → 部署名 → 役職 → 名前 → 様/殿; skipping a level is acceptable, but reversing the order (名前 before 役職, 部署 after 名前) is a visible BJT error. 連名 (multiple recipients): when two co-recipients share one line, write 〇〇様・〇〇様 with a middle dot, or stack them on separate lines; do not collapse them as 〇〇・〇〇様 (a single 様 cannot cover two names). The 〇〇様方 (様方) pattern is used when addressing mail to a person care of another household or company (e.g., 〇〇株式会社 〇〇 様方 〇〇 様) — rare in modern business email, but it still appears in formal paper correspondence and in BJT items testing address syntax.

CC / BCC Japanese convention

In Japanese business email, the abbreviations CC: 〇〇、BCC: 〇〇 are written in romaji as in English, but the surrounding line often carries a Japanese note: 「CC: 〇〇部 〇〇（参考）」or 「CC: 関係者各位」. In formal business letters (not email), there is no CC/BCC field; instead the 写 (うつし) line lists recipients who receive a carbon copy, e.g., 「写: 〇〇部長、〇〇部長」. A BJT trap is to import the English "CC:" tag into a 添え状-style formal letter — use 「写」in letters and 「CC」only in email.

件名 — Subject Line

A Japanese 件名 should be concise and front-load the action/purpose. Common templates:

• 【ご請求書】〇〇月分のお支払いについて
• 【ご相談】〇〇の件、ご回答のお願い
• 【ご案内】新商品〇〇のご紹介
• 【お詫び】〇月〇日納品遅延につきまして
• 【ご報告】〇〇プロジェクト完了のご報告

Trap: a blank, vague (「お世話になっております」 only), or overly long 件名 is a BJT-listed email error. The bracketed tag at the front signals the mail's function.

クッション言葉 — Cushion Words

Softeners placed before a request, refusal, or interruption:

Trap: a request without a cushion is not automatically ungrammatical, but it sounds abrupt and is graded as impolite in BJT email tasks.

添付ファイル — Attachment Conventions

When the mail carries an attachment, the body must say so explicitly. Standard phrasings:

• 添付ファイルにてお送りいたします。 (I am sending this by attachment.)
• 添付資料をご参照ください。 (Please refer to the attached materials.)
• 別紙記入の上、ご返送ください。 (Please fill in the attached form and return it.)
• 添付ファイルにて〇〇の資料を同封いたしますので、ご査収ください。

Trap: sending an attachment without any in-body mention is a BJT error — the recipient may miss it, and the convention requires explicit 添付 reference. When requesting a return, 「別紙」+「ご返送」is the fixed collocation; 「添付ファイルをご返送ください」is slightly less natural because 返送 implies a separate paper sheet.

依頼・断り・謝罪 — Requests, Refusals, Apologies

依頼 (requests):

• ご対応いただけますと幸いです。 (It would be appreciated if you could…)
• お手数ですが、〇〇をお願いいたします。 (Sorry to trouble you, but please…)
• 何卒よろしくお願い申し上げます。 (Please kindly…)
• 誠に恐縮ですが、ご検討のほどお願い申し上げます。

断り (refusals):

• お気持ちはありがたいのですが、今回は見送らせていただきます。
• 残念ながら〇〇のため、辞退させていただきます。
• 現状ではお引き受けいたしかねます。
• せっかくのお話ですが、今回はご期待に沿えず申し訳ございません。

謝罪 (apologies):

• 申し訳ございません。
• 大変申し訳ございません。
• 心よりお詫び申し上げます。
• 深くお詫び申し上げます。
• ご迷惑をおかけしましたこと、お詫び申し上げます。

報告と結び — Reporting and Closing Formulae

報告 (reporting):

• おかげさまで無事に終了いたしました。
• 〇〇の件、ご報告申し上げます。
• ご指定の期日通りに完了いたしました。

結び (closing formulae):

• 引き続き、何卒よろしくお願い申し上げます。
• 今後とも変わらぬご愛顧を賜りますようお願い申し上げます。
• まずは略儀ながら、書中にてお礼申し上げます。 (Used when skipping the full ceremonial close — for example, when you have already met or spoken and a full letter formula would be excessive.)
• 末筆ではございますが、〇〇様のますますのご活躍をお祈り申し上げます。 (Added after a formulaic close to insert a personal well-wish; 末筆ながら is the contracted form and is equally acceptable.)
• まずは略儀ながら書中にてご挨拶申し上げます。 (Used when sending a greeting-only letter and skipping the full ceremony — typical for 年賀状 follow-ups and brief notifications.)

内外線 — External vs Internal Mail

External mail (外部向け) carries the full stack: 頭語 (拝啓/謹啓) → 季節の挨拶 → 宛名 (〇〇様) → body → 結び → 結語 (敬具). Internal mail (社内向け) is typically lighter: 前略 (or no 頭語 at all) → 〇〇様 / 〇〇部長 only → body → 早々, or no 結語. Using 拝啓+敬具 for an in-house note to a close colleague is over-formal and is graded as register mismatch in BJT; using 前略 for an external customer email is under-formal and equally wrong. The BJT-listed rule of thumb: 外部 = 拝啓+敬具 with 季節の挨拶; 社内 = 前略+早々 or 〇〇様 only.

The Seven Common BJT Email Errors

1. Mismatched 頭語 / 結語 — 拝啓 without 敬具; 前略 with 敬具; 謹啓 with 早々.
2. 様 / 御中 mismatch — 御中 after a personal name; 様 after a department alone; the double suffix 御中 様.
3. 季節の挨拶 out of season — 師走の候 in May; 早春の候 in November; mixing 候 / 折 / みぎり within one mail.
4. Over-formal vs under-formal register — using 前略 for a first-time customer email, or 〇〇くん in an external email; using full 拝啓+敬具 for an in-house one-liner.
5. 件名 blank or vague — only 「お世話になっております」 as a subject; or no subject at all.
6. Reply 頭語 mismatch — replying to a 拝啓 email with 早々 (under-formal) or replying to a 謹啓 email without matching the elevated register; failing to use 拝復 in a formal reply.
7. 添付ファイル / 連名 / 様方 errors — sending an attachment with no in-body mention; writing 〇〇・〇〇様 (single 様 covering two names) instead of 〇〇様・〇〇様; misusing 様方 in modern business email.

A well-formed BJT email stacks the parts in order: 頭語 → 季節の挨拶 → 宛名 (above the body) → クッション言葉 → 依頼/報告/謝罪 body → 結び → 結語. Learning the stack is faster than memorizing each formula in isolation.