目錄
When you actually have to apologize in Japanese at work, 「申し訳ございません」 is usually not the hard part to remember. The difficult part is knowing what to say after it. You may realize you will not make it to a scheduled meeting on time, notice that the amount on a quotation you just sent is wrong, or only discover after sending an email that you forgot to attach the file altogether. All of these situations require an apology first, but from the recipient’s perspective, receiving nothing more than “I’m very sorry” still does not tell them what they should do next.
If you are going to be late, you need to say roughly what time you will arrive. If there is an error in a document, you need to make clear which version is the correct one. If the matter is still being checked, you should at least provide a time for your next update. In business Japanese, 「すみません」「申し訳ありません」「申し訳ございません」「お詫び申し上げます」 do differ in tone and appropriate context, but once they are placed into real workplace situations, how formal the apology sounds is only one part of the message. Whether the information that follows is complete often has a more direct impact on the communication as a whole.
How do you apologize in business Japanese? Explain the problem and the next step first
「すみません」「申し訳ありません」「申し訳ございません」 can all express an apology. The differences involve not only formality, but also your relationship with the other person, the impact of the incident, and the communication channel being used.
If you accidentally interrupt a coworker, 「すみません」 sounds natural. If a document contains an error, you are late, or work has been delayed, 「申し訳ありません」 is generally more appropriate in a business setting. When speaking to a customer, an external business partner, or about an incident with a larger impact, the more formal 「申し訳ございません」 is commonly used.
However, the apology formula itself does not solve the other person’s problem. The most practical approach is to combine the apology with information they can act on.
- Example: 申し訳ございません。到着が十五分ほど遅れる見込みです。
Kana: もうしわけございません。とうちゃくがじゅうごふんほどおくれるみこみです。
Translation: I am very sorry.
I expect to arrive about 15 minutes late.
In addition to apologizing, this immediately gives the length of the delay, allowing the other person to adjust their plans. - Example: 見積書の金額に誤りがございました。ご迷惑をおかけし、申し訳ございません。
Kana: みつもりしょのきんがくにあやまりがございました。ごめいわくをおかけし、もうしわけございません。
Translation: There was an error in the amount on the quotation.
I sincerely apologize for the inconvenience.
Identifying the specific error first and then acknowledging its impact makes the problem easier to understand than writing only 「申し訳ございません」. - Example: 再度ご確認いただくこととなり、お手数をおかけして申し訳ございません。
Kana: さいどごかくにんいただくこととなり、おてすうをおかけしてもうしわけございません。
Translation: I am sorry for the extra trouble of having to ask you to check it again.
「お手数をおかけする」 is suitable when your own mistake means the other person has to repeat a check, reply, or operation.
The basic order of a business apology in Japanese: apology, facts, action, and update time
There is no fixed template that must be copied every time you apologize at work, but the information that generally needs to be communicated can be divided into four parts: first acknowledge the impact, then explain the facts that have been confirmed, next state what is being done now, and finally provide the next update time or completion time.
In urgent situations, the apology and the key information can be placed in the same sentence. If you already know that you will be late, there is no need to write three lines of formalities first. Saying 「申し訳ございません。到着が十五分ほど遅れます」 directly is often more useful.
| Order | What needs to be communicated | Common expression | What the other person can understand |
| ① Apology | Acknowledge the impact | 申し訳ございません | The problem is being taken seriously |
| ② Facts | What happened | 添付資料が漏れておりました | The scope of the problem |
| ③ Action | What is being done now | 修正版を至急お送りします | The specific next action |
| ④ Update | When you will update them again | 十五時までにご連絡します | They do not need to chase you for progress |
Business Japanese apology step 1 | State the confirmed facts first, then add only the necessary reason
It is not that reasons should never be given. The point is to distinguish between a factual explanation and an excuse meant to defend yourself.
「電車が遅れていて、朝から道路も混んでいて……」 contains a lot of information, but most of it does not help the person who is waiting. What they really need to know first is how late you will be.
- Example: 申し訳ございません。電車の遅延により、到着が十分ほど遅れます。
Kana: もうしわけございません。でんしゃのちえんにより、とうちゃくがじゅっぷんほどおくれます。
Translation: I am very sorry.
Due to a train delay, I will arrive about 10 minutes late.
The reason is explained in one phrase, while the main information remains the length of the delay. - Example: 添付すべき資料が漏れておりました。申し訳ございません。
Kana: てんぷすべきしりょうがもれておりました。もうしわけございません。
Translation: The document that should have been attached was missing.
I apologize.
Saying exactly what was omitted makes the impact easier to understand than a vague statement such as 「メールに不備がありました」. - Example: 先ほど送付した資料に一部誤りがあることを確認いたしました。
Kana: さきほどそうふしたしりょうにいちぶあやまりがあることをかくにんいたしました。
Translation: We have confirmed that part of the document sent earlier contains an error.
If the cause has not yet been fully identified, you can first state the facts that are currently confirmed without rushing to speculate.
Business Japanese apology step 2 | Explain what is being done now
After a problem occurs, information such as “we are checking,” “we have resent it,” or “we are currently correcting it” communicates more than repeatedly apologizing.
- Example: 正しい資料を添付し、改めてお送りいたします。
Kana: ただしいしりょうをてんぷし、あらためておおくりいたします。
Translation: I will attach the correct document and send it again.
The other person can immediately understand that they do not need to correct the old file themselves. - Example: 現在、該当箇所を確認しております。
Kana: げんざい、がいとうかしょをかくにんしております。
Translation: We are currently checking the relevant section.
If the investigation is not finished, there is no need to give an unsupported conclusion in advance. - Example: 修正版を作成し、差し替えの準備を進めております。
Kana: しゅうせいばんをさくせいし、さしかえのじゅんびをすすめております。
Translation: We are preparing a corrected version and getting ready to replace the existing one.
This is suitable when corrective action has already begun but is not yet complete.
Business Japanese apology step 3 | Provide a completion time or the next update time
If 「確認します」 or 「対応します」 is given without a time, the other person still does not know when they will get an answer.
If you can confirm the completion time, state it directly. If you cannot yet guarantee completion, at least provide the time of the next progress update.
- Example: 修正版は本日十五時までにお送りいたします。
Kana: しゅうせいばんはほんじつじゅうごじまでにおおくりいたします。
Translation: I will send the corrected version by 3:00 p.m.
today.
When you can clearly commit to a completion time, state the deadline directly. - Example: 確認結果につきましては、本日十六時までに改めてご連絡いたします。
Kana: かくにんけっかにつきましては、ほんじつじゅうろくじまでにあらためてごれんらくいたします。
Translation: I will contact you again with the results of the review by 4:00 p.m.
today.
Even if the problem cannot yet be fully resolved, establish the time of the next update first. - Example: 現時点では復旧時刻を確定できないため、十三時に一度進捗をご報告いたします。
Kana: げんじてんではふっきゅうじこくをかくていできないため、じゅうさんじにいちどしんちょくをごほうこくいたします。
Translation: At this time, we cannot confirm the restoration time, so we will provide a progress update at 1:00 p.m.
If you are not certain, you do not need to force a completion time. Providing the next update point is enough.
The difference between 「すみません」「申し訳ございません」「お詫び申し上げます」: formality and appropriate situations
「すみません」「申し訳ございません」「お詫び申し上げます」 can all express an apology, but the differences are not simply a matter of ranking them from lighter to heavier. 「すみません」 is well suited to small mistakes spoken about on the spot. 「申し訳ございません」 is a very common direct apology in formal business communication. 「お詫び申し上げます」 has a more pronounced written and formal tone, and it is often used together with a clear statement of the incident being formally apologized for.
| Expression | Formality | Tone | Common recipients | Common situations | Spoken use | Email/written use | Suitable incidents |
| すみません | General | Everyday, direct | Coworkers, familiar work contacts | Minor on-the-spot mistakes, brief interruptions, slight delays | Very natural | Possible, but more formal wording is usually used in formal external emails | Forgetting a document, making someone wait briefly, interrupting a conversation, and other minor situations |
| 申し訳ございません | Formal, respectful | Clearly acknowledges an apology | Customers, supervisors, external partners | Business email, phone calls, meetings, customer support | Natural | Very common | Being late, delayed replies, document errors, insufficient checking, and other general to relatively formal business mistakes |
| お詫び申し上げます | Very formal | Strongly written, explicitly formal apology | Customers, consumers, partner companies, the general public | Formal email, notices, corporate statements | Less common in ordinary conversation | Very common in formal documents | Delivery delays, service outages, incorrect notices, and incidents requiring an official corporate apology |
▌Business use of 「すみません」: light apologies, interruptions, and waiting
「すみません」 does not become unusable once you enter a workplace. It is extremely common in everyday office conversation, especially for brief interruptions, minor mistakes, or things that can be corrected immediately.
- Example: すみません、資料を一枚取り忘れました。すぐ持ってきます。
Kana: すみません、しりょうをいちまいとりわすれました。すぐもってきます。
Translation: Sorry, I forgot one of the documents.
I’ll bring it right away.
The issue is minor and can be fixed immediately, so there is no need to deliberately escalate it to a very heavy apology. - Example: すみません、もう一度確認してもいいですか。
Kana: すみません、もういちどかくにんしてもいいですか。
Translation: Sorry, may I check that one more time?
This also carries the sense of interrupting the other person, so 「すみません」 can function as a conversational preface. - Example: すみません、お待たせしました。
Kana: すみません、おまたせしました。
Translation: Sorry to keep you waiting.
This is natural for a short wait or an ordinary workplace interaction.
▌Business use of 「申し訳ありません／ございません」: the standard formal apology
When a work mistake has already affected timing, content, or another person’s work, 「申し訳ありません」 is more appropriate in terms of formality than 「すみません」. When addressing customers or when a higher degree of politeness is needed, 「申し訳ございません」 is commonly used.
- Example: 回答が遅くなり、申し訳ありません。
Kana: かいとうがおそくなり、もうしわけありません。
Translation: I apologize for the delayed response.
This can be used in both ordinary business emails and formal internal communication. - Example: こちらの確認不足により、ご迷惑をおかけして申し訳ございません。
Kana: こちらのかくにんぶそくにより、ごめいわくをおかけしてもうしわけございません。
Translation: We apologize for the inconvenience caused by our insufficient checking.
If the cause has been confirmed, you can clearly acknowledge which part of the process went wrong. - Example: ご案内に誤りがあり、誠に申し訳ございませんでした。
Kana: ごあんないにあやまりがあり、まことにもうしわけございませんでした。
Translation: We sincerely apologize for the error in the information we provided.
「誠に」 increases the level of formality, but it does not need to be inserted into every ordinary email.
▌Business use of 「お詫び申し上げます」: formal written apologies in emails and public statements
「お詫び申し上げます」 is more formal and more strongly associated with written communication than the ordinary spoken 「申し訳ございません」. It is suitable for delivery delays, service outages, formal notices, and statements made on behalf of an organization.
- Example: このたびは納品が遅れましたこと、深くお詫び申し上げます。
Kana: このたびはのうひんがおくれましたこと、ふかくおわびもうしあげます。
Translation: We sincerely apologize for the delay in delivery.
This is suitable for formal external email and is not the kind of phrasing normally used in casual office conversation. - Example: サービスをご利用いただけない状況が続きましたことを、お詫び申し上げます。
Kana: さーびすをごりよういただけないじょうきょうがつづきましたことを、おわびもうしあげます。
Translation: We apologize that the service remained unavailable for an extended period.
Placing the affected incident directly before 「お詫び申し上げます」 is suitable for announcement-style writing. - Example: 多大なるご迷惑をおかけしましたこと、改めてお詫び申し上げます。
Kana: ただいなるごめいわくをおかけしましたこと、あらためておわびもうしあげます。
Translation: We once again sincerely apologize for the significant inconvenience caused.
This is a very strong apology and should be used for incidents with a corresponding level of impact. It is not suitable for repeatedly apologizing for a small mistake.
▌How do 「すみません」「申し訳ございません」「お詫び申し上げます」 differ when the same quotation contains an error?
Suppose the amount on a quotation you just sent is wrong. The incident itself does not change, but changing the apology phrase also changes the perceived distance between the speaker and the recipient. Saying 「すみません」 to a coworker you know well is not strange, but sending the same wording directly to a customer may feel too light. 「申し訳ございません」 is natural in an ordinary business correction email. If the error has a larger impact and requires an official company-level explanation, 「お詫び申し上げます」 is more appropriate than an everyday conversational expression.
- Example: すみません、先ほど送った見積書の金額が間違っていました。修正版を送ります。
Kana: すみません、さきほどおくったみつもりしょのきんがくがまちがっていました。しゅうせいばんをおくります。
Translation: Sorry, the amount on the quotation I sent earlier was wrong.
I’ll send a corrected version.
This sounds more like a direct explanation of a mistake between coworkers. The tone is natural and moves quickly to the solution. If the recipient is a new customer or the message is formal external correspondence, the level of formality would usually be raised. - Example: 先ほどお送りした見積書の金額に誤りがございました。ご迷惑をおかけし、誠に申し訳ございません。
Kana: さきほどおおくりしたみつもりしょのきんがくにあやまりがございました。ごめいわくをおかけし、まことにもうしわけございません。
Translation: There was an error in the amount on the quotation I sent earlier.
I sincerely apologize for the inconvenience.
「申し訳ございません」 is suitable when directly acknowledging a work mistake to a customer. It can be used both orally and in email, and it does not create as much distance as a formal public statement, making it one of the most common forms of business apology. - Example: このたびは、弊社よりお送りした見積書の金額に誤りがございましたこと、深くお詫び申し上げます。
Kana: このたびは、へいしゃよりおおくりしたみつもりしょのきんがくにあやまりがございましたこと、ふかくおわびもうしあげます。
Translation: We sincerely apologize for the error in the amount on the quotation sent by our company.
Once 「お詫び申し上げます」 is used, the sentence sounds more like a formal written statement and clearly identifies what is being apologized for. If coworkers are merely correcting a small numerical mistake, this level of wording can sound excessively heavy.
There is no need to think of the three expressions simply as 「すみません ＜ 申し訳ございません ＜ お詫び申し上げます」 and choose the most formal one every time. In actual work, you still need to consider the recipient, the communication channel, and the degree of impact. The same mistake will naturally be expressed differently when speaking to a nearby coworker, emailing a customer, or issuing an official public statement on behalf of a company.
The difference between 「ご迷惑」「お手数」「ご不便」「お待たせ」: how to choose in a business apology
「ご迷惑」「お手数」「ご不便」「お待たせ」 are all commonly used in business apologies, but they do not describe the same kind of burden. The difference becomes clearer if you ask, “What additional burden did this situation place on the other person?” If their work was affected, use 「ご迷惑」. If they have to do something again, use 「お手数」. If a service that should normally be available cannot be used, use 「ご不便」. If their waiting time has been extended, use 「お待たせ」.
| Expression | Main meaning | Focus of the apology | Common situations | Common collocation | Typical nuance |
| ご迷惑 | Causing trouble or disruption | The issue has already affected the other person’s work, plans, or interests | Delivery delays, document errors, system failures, communication mistakes | ご迷惑をおかけし、申し訳ございません | Broadest in scope; can also be used when there is no more precise type of burden to describe |
| お手数 | Causing extra effort | Because of your side, the other person must reconfirm, re-enter, resend, or repeat an operation | Re-entering data, logging in again, checking an attachment again, replying again | お手数をおかけして申し訳ございません | The focus is not on how serious the incident is, but on the fact that the other person has to do something again |
| ご不便 | Causing inconvenience in use or action | Something that should normally be usable or possible has been obstructed | System maintenance, website failure, equipment shutdown, service suspension | ご不便をおかけし、申し訳ございません | Common in service, facility, and system notices; more directly points to inconvenience in use than 「ご迷惑」 |
| お待たせ | Making someone wait | Something expected to be finished earlier is taking longer, increasing the waiting time | Delayed responses, customer support, in-person waiting, documents under review | お待たせして申し訳ございません | Directly acknowledges “we made you wait,” without describing every delay as 「ご迷惑」 |
▌「ご迷惑をおかけし」 | The incident has already affected the other person
- Example: 納品の遅れにより、ご迷惑をおかけして申し訳ございません。
Kana: のうひんのおくれにより、ごめいわくをおかけしてもうしわけございません。
Translation: We apologize for the inconvenience caused by the delivery delay.
Because the delay directly affects subsequent work, 「ご迷惑」 is used.
▌「お手数をおかけし」 | The other person has to do something again
- Example: 再度ご入力いただくこととなり、お手数をおかけして申し訳ございません。
Kana: さいどごにゅうりょくいただくこととなり、おてすうをおかけしてもうしわけございません。
Translation: We apologize for the extra trouble of asking you to enter the information again.
When the other person has to repeat an operation, 「お手数」 is more specific than the broader 「ご迷惑」.
▌「ご不便をおかけし」 | A service or facility cannot be used normally
- Example: システム障害により、ご不便をおかけしております。
Kana: しすてむしょうがいにより、ごふべんをおかけしております。
Translation: We apologize for the inconvenience currently caused by the system failure.
This is common in notices about websites, transportation, facilities, and service disruptions.
▌「お待たせし」 | The other person’s waiting time has been extended
- Example: ご回答までお待たせしてしまい、申し訳ございません。
Kana: ごかいとうまでおまたせしてしまい、もうしわけございません。
Translation: We apologize for keeping you waiting for our response.
When the problem is the waiting time itself, using 「お待たせする」 directly is more accurate than the abstract 「ご迷惑」.
▌How do 「ご迷惑」「お手数」「ご不便」「お待たせ」 differ in the same system outage?
Suppose a company’s online system experiences a problem, customers temporarily cannot complete an operation, customer support is working on it, and customers may need to log in again afterward. In this situation, all four expressions could appear in the communication, but each apology points to something different. 「ご迷惑」 refers to the overall incident having affected the customer. 「ご不便」 narrows the focus to the fact that the system cannot currently be used normally. 「お手数」 applies if the customer later has to perform an operation again. 「お待たせ」 applies when the handling time becomes long and the customer has been left waiting for information.
- Example: システム障害により、ご迷惑をおかけして申し訳ございません。
Kana: しすてむしょうがいにより、ごめいわくをおかけしてもうしわけございません。
Translation: We apologize for the trouble caused by the system failure.
「ご迷惑」 refers to the fact that the outage as a whole has affected the other person without limiting the burden to one particular type, making it suitable for apologizing for the overall incident. - Example: システム障害により、ご不便をおかけして申し訳ございません。
Kana: しすてむしょうがいにより、ごふべんをおかけしてもうしわけございません。
Translation: We apologize for the inconvenience caused by the system failure.
With 「ご不便」, the focus shifts to the fact that the system currently cannot be used normally. This is common in notices about websites, apps, equipment, and various service disruptions. - Example: 復旧後、再度ログインしていただく必要がございます。お手数をおかけして申し訳ございません。
Kana: ふっきゅうご、さいどろぐいんしていただくひつようがございます。おてすうをおかけしてもうしわけございません。
Translation: After service is restored, you will need to log in again.
We apologize for the extra trouble.
「お手数」 is used here because the problem requires the other person to log in again and perform an additional operation they would not otherwise have needed. - Example: 確認に時間を要しており、お待たせして申し訳ございません。
Kana: かくにんにじかんをようしており、おまたせしてもうしわけございません。
Translation: We apologize for keeping you waiting while the matter is being checked.
「お待たせ」 does not describe what effect the system itself is having. It acknowledges that the handling time has become longer and the customer has already been waiting.
More than one of these expressions may appear in the same system outage. For example, if the system cannot be used, you can first say 「ご不便をおかけしております」. If customers will then need to log in again after recovery, you can add 「お手数をおかけしますが、再度ログインをお願いいたします」. There is no need to force all four expressions into one email to make it sound more formal. Choose according to the burden that actually occurred.
Business Japanese apology use case ① | What to say when you are late or delayed for a meeting
The most important thing in a late-arrival notice is the new time information. If you know the reason, you can explain it briefly. If the reason is still being checked, there is no need to delay the message just to make it feel complete.
「遅刻します」 is grammatically correct, but when visiting someone outside your company, expressions such as 「到着が遅れます」 or 「○時ごろに伺います」 are often used because they focus directly on the arrival time the other person needs for scheduling.
- Example: 申し訳ございません。到着が十五分ほど遅れる見込みです。
Kana: もうしわけございません。とうちゃくがじゅうごふんほどおくれるみこみです。
Translation: I am very sorry.
I expect to arrive about 15 minutes late.
「見込みです」 indicates a current estimate and is suitable when traffic conditions may still change. - Example: ただいま向かっております。十時十分ごろに到着する予定です。
Kana: ただいまむかっております。じゅうじじゅっぷんごろにとうちゃくするよていです。
Translation: I am on my way now and expect to arrive at around 10:10.
The other person can immediately tell whether you are already on your way. - Example: 開始時刻に間に合わず、誠に申し訳ございません。十時十五分までには伺います。
Kana: かいしじこくにまにあわず、まことにもうしわけございません。じゅうじじゅうごふんまでにはうかがいます。
Translation: I sincerely apologize for not being able to make it by the start time.
I will arrive by 10:15.
Once it is certain that you will not arrive on time, there is no need to use vague wording. Acknowledge the impact directly and update the arrival time.
Business Japanese apology use case ② | What to say when an attachment is missing or a document contains an error
The biggest risk with a document error is that the other person may continue using the old version. In addition to apologizing, clearly explain which document has the problem, where the correct version is, and whether the old file should no longer be used.
- Example: 先ほどのメールに添付ファイルが漏れておりました。申し訳ございません。
Kana: さきほどのめーるにてんぷふぁいるがもれておりました。もうしわけございません。
Translation: The attachment was missing from the email I sent earlier.
I apologize.
Once the missing attachment has been confirmed, you can simply state it directly. - Example: 見積書の金額に誤りがございました。修正版を添付いたしますので、こちらをご確認ください。
Kana: みつもりしょのきんがくにあやまりがございました。しゅうせいばんをてんぷいたしますので、こちらをごかくにんください。
Translation: There was an error in the amount on the quotation.
I have attached the corrected version, so please check this file.
In addition to identifying the error, this clearly tells the recipient which version should be used from now on. - Example: 先ほどお送りしたファイルは破棄していただき、修正版をご使用くださいますようお願いいたします。
Kana: さきほどおおくりしたふぁいるははきしていただき、しゅうせいばんをごしようくださいますようおねがいいたします。
Translation: Please discard the file sent earlier and use the corrected version.
If the old file could cause further errors, the handling instructions need to be made explicit.
Business Japanese apology use case ③ | Customer support and system problems: what to say when the issue is not yet resolved
One of the most common problems in customer support is saying 「申し訳ございません。確認いたします」 and then giving no time information at all. The fact that the issue is not yet resolved does not mean you cannot reply. You can acknowledge the current situation and provide the next contact time.
- Example: 現在、原因を確認しております。ご不便をおかけし、申し訳ございません。
Kana: げんざい、げんいんをかくにんしております。ごふべんをおかけし、もうしわけございません。
Translation: We are currently checking the cause.
We apologize for the inconvenience.
If the cause has not yet been identified, communicate only confirmed information rather than speculating. - Example: 確認に時間を要しており、お待たせして申し訳ございません。
Kana: かくにんにじかんをようしており、おまたせしてもうしわけございません。
Translation: We apologize for keeping you waiting while the review is taking longer than expected.
This more directly states that your own checking process is taking time than 「確認にお時間をいただいており」. - Example: 本日十七時までに、確認状況を改めてご連絡いたします。
Kana: ほんじつじゅうしちじまでに、かくにんじょうきょうをあらためてごれんらくいたします。
Translation: We will contact you again with an update on the review status by 5:00 p.m.
today.
Even if the matter may not be completely resolved by then, you can still commit to reporting progress.
Can you explain the reason when apologizing in Japanese? The difference between 「理由」 and 「言い訳」
After a problem occurs at work, the cause usually needs to be explained. The issue is not whether you are “allowed to explain the reason,” but whether the reason helps the other person understand the current situation or merely reduces your own responsibility.
A more practical approach is to keep the facts that are relevant to resolving the issue. Delays in transportation, system failures, and configuration errors can all be mentioned, but there is no need to include a large amount of private detail or information that shifts responsibility elsewhere.
▌How to explain reasons in a business apology in Japanese | Keep only information relevant to the response
✅ システム障害により、一部の注文処理が遅れております。
Due to a system failure, some order processing is currently delayed.
This reason helps the other person understand the scope of the impact, so it is relevant.
▌What kinds of reasons sound like 「言い訳」? Details unrelated to the response can be shortened
△ 担当者が急に休みになり、引き継ぎもうまくできていなかったため……。
Because the person in charge suddenly took leave and the handover did not go smoothly…
If what the recipient really needs to know is when the corrected version will be provided, internal handover details usually do not need to appear in the first paragraph.
✅ ご回答が遅れており、申し訳ございません。本日十五時までに回答いたします。
We apologize for the delayed response. We will provide an answer by 3:00 p.m. today.
Do business apologies in Japanese need to mention 「再発防止」? Discuss preventive measures after the cause is known
For mistakes with a larger impact, formal apology emails often mention 「再発防止策」. However, if the cause has not yet been confirmed, writing 「今後このようなことがないよう徹底します」 too early can easily become nothing more than a stock phrase.
Once you know what caused the problem, it becomes appropriate to present a concrete improvement.
- Example: 再発防止のため、送信前の確認項目を追加いたします。
Kana: さいはつぼうしのため、そうしんまえのかくにんこうもくをついかいたします。
Translation: To prevent recurrence, we will add an additional pre-send check.
This measure directly relates to problems such as forgetting an attachment. - Example: 今後は二名で金額を確認する運用に変更いたします。
Kana: こんごはにめいできんがくをかくにんするうんようにへんこういたします。
Translation: Going forward, we will change the process so that two people check the amount.
This is more concrete than 「確認を徹底します」 and is easier to implement in practice. - Example: 原因を確認したうえで、必要な再発防止策をご報告いたします。
Kana: げんいんをかくにんしたうえで、ひつようなさいはつぼうしさくをごほうこくいたします。
Translation: After confirming the cause, we will report the necessary measures to prevent recurrence.
If the cause has not yet been identified, simply commit to the investigation and the follow-up report first.
How do you write a business apology email in Japanese? A document-correction template and complete structure
A correction email can be short as long as all necessary information is included.
Basic wording for a document error
Subject: 見積書訂正のお詫び
先ほどお送りした見積書の金額に誤りがございました。
ご迷惑をおかけし、誠に申し訳ございません。
修正版を本メールに添付しております。
お手数をおかけしますが、先ほどのファイルは破棄していただき、修正版をご確認くださいますようお願いいたします。
今後は送付前の確認手順を見直し、再発防止に努めます。
Kana: さきほどおおくりしたみつもりしょのきんがくにあやまりがございました。ごめいわくをおかけし、まことにもうしわけございません。しゅうせいばんをほんめーるにてんぷしております。おてすうをおかけしますが、さきほどのふぁいるははきしていただき、しゅうせいばんをごかくにんくださいますようおねがいいたします。こんごはそうふまえのかくにんてじゅんをみなおし、さいはつぼうしにつとめます。
Translation: There was an error in the amount on the quotation I sent earlier, and I sincerely apologize for the inconvenience.
The corrected version is attached to this email. I am sorry for the extra trouble, but please discard the previous file and review the corrected version. Going forward, we will review our pre-send checking procedure and work to prevent a recurrence.
There is no need to repeat 「申し訳ございません」 in every paragraph of this kind of email. Once the error, corrected version, and handling instructions are clear, one or two expressions of apology are enough.
Business apology examples from Japanese workplaces: lateness, document errors, and customer-service delays
▌Situation ① | You realize you will be late before visiting a customer
A：申し訳ございません。電車の遅延により、到着が十分ほど遅れる見込みです。十時十分ごろに伺います。
もうしわけございません。でんしゃのちえんにより、とうちゃくがじゅっぷんほどおくれるみこみです。じゅうじじゅっぷんごろにうかがいます。
I am very sorry. Due to a train delay, I expect to arrive about 10 minutes late. I will arrive at around 10:10.
B：承知しました。お気をつけてお越しください。
しょうちしました。おきをつけておこしください。
Understood. Please take care on your way here.
📌 Grammar Point: The apology, reason, and arrival time are all kept brief. The information the other person needs most is “around 10:10,” so there is no need to begin with a long explanation of the traffic situation.
▌Situation ② | You discover an error in an attachment you sent
A：先ほどお送りした資料に誤りがございました。申し訳ございません。修正版をすぐに再送いたします。
さきほどおおくりしたしりょうにあやまりがございました。もうしわけございません。しゅうせいばんをすぐにさいそういたします。
There was an error in the document I sent earlier. I apologize. I will resend the corrected version immediately.
B：承知しました。修正版を確認します。
しょうちしました。しゅうせいばんをかくにんします。
Understood. I will check the corrected version.
📌 Grammar Point: The first sentence identifies the error directly, and the second immediately gives the response. If the old file must no longer be used, you also need to tell the other person to discard it.
▌Situation ③ | Customer support has not yet identified the cause
A：現在も原因を確認しております。お待たせしており、申し訳ございません。本日十六時までに一度状況をご連絡いたします。
げんざいもげんいんをかくにんしております。おまたせしており、もうしわけございません。ほんじつじゅうろくじまでにいちどじょうきょうをごれんらくいたします。
We are still investigating the cause. We apologize for keeping you waiting. We will contact you with a status update by 4:00 p.m. today.
B：分かりました。ご連絡をお待ちしております。
わかりました。ごれんらくをおまちしております。
Understood. I will wait for your update.
📌 Grammar Point: Even when the issue is not yet resolved, you can provide the next update time. Saying “we will contact you with an update by 4:00 p.m.” makes it easier for the other person to plan than simply saying 「確認しております」.
Cultural Notes:
- Japanese 「すみません」 is used not only for apologies, but also to get someone’s attention, make a request, or express a mixture of apology and gratitude for another person’s help. It is not completely avoided in business settings; what matters is the weight of the situation.
- A higher level of formality does not mean one phrase solves the entire problem. If 「申し訳ございません」 is not followed by the current status and next action, the other person still has to ask again.
- 「お手数をおかけします」 and 「ご迷惑をおかけします」 are not completely interchangeable. The former more specifically means making the other person do extra work, while the latter covers broader effects on timing, decisions, and work.
How should Japanese 「申し訳ございません／お詫び申し上げます」 be understood alongside Korean 「죄송합니다／사과드립니다」?
Korean 「죄송합니다」 is one of the most common formal apology expressions in the workplace. It can be used on its own or after explaining a delay, mistake, or burden caused to the other person. The National Institute of Korean Language explains 「죄송하다」 as meaning to feel deeply sorry as if one had done something wrong, so the expression directly conveys the speaker’s regret about their own actions or the current situation.
「사과드립니다」 more directly performs the act of apologizing and is more common in formal notices, customer-service announcements, company correspondence, and public statements. Japanese 「申し訳ございません」 overlaps considerably with 「죄송합니다」 in ordinary workplace communication, while 「お詫び申し上げます」 is closer to the formal written 「사과드립니다」. However, the degree of formality is not completely fixed between the two pairs and still depends on the impact of the incident, surrounding modifiers, and the follow-up response.
◆ Similar expression ①: Korean 「죄송합니다」
「죄송합니다」 can express an apology directly and is also commonly used after forms such as 「-아／어서」 and 「-게 되어」 to explain a delay, mistake, or additional burden caused. In Japanese, it often corresponds to 「申し訳ありません」 or the more formal 「申し訳ございません」 depending on the level of formality.
- Example: 죄송합니다. 도착이 15분 정도 늦어질 것 같습니다.
Romanization: joe-song-ham-ni-da. do-chak-i sip-o-bun jeong-do neu-jeo-jil geot gat-seum-ni-da.
Translation: I am very sorry.
I expect to arrive about 15 minutes late.
This corresponds to the Japanese 「申し訳ございません。到着が十五分ほど遅れる見込みです」. Both first express an apology and then give a specific length of delay. 「것 같습니다」 and 「見込みです」 both preserve the sense that this is still an estimate. - Example: 자료에 오류가 있어 다시 확인을 부탁드리게 되어 죄송합니다.
Romanization: ja-ryo-e o-ryu-ga i-sseo da-si hwak-in-eul bu-tak-deu-ri-ge doe-eo joe-song-ham-ni-da.
Translation: I apologize for having to ask you to check again because there is an error in the document.
This corresponds to the Japanese 「資料に誤りがあり、再度ご確認をお願いすることとなり、申し訳ございません」. Korean uses 「다시 확인을 부탁드리게 되어」 to state directly that the other person must check again, while Japanese uses 「再度ご確認をお願いする」 to explain the added task. - Example: 답변이 늦어져 죄송합니다.
Romanization: dap-byeon-i neu-jeo-jyeo joe-song-ham-ni-da.
Translation: I apologize for the late reply.
This corresponds to the Japanese 「ご返信が遅くなり、申し訳ございません」. Delayed replies are a common workplace apology situation, and in both languages the speaker can apologize first and then continue with the content of the reply. There is not necessarily any need to switch to the more statement-like 「사과드립니다／お詫び申し上げます」.
◆ Similar expression ②: Korean 「사과드립니다」
「사과드립니다」 is formed by combining 「사과하다」 with the honorific verb 「드리다」 and sounds more like a formal act of apology than ordinary 「죄송합니다」. It is often used together with 「진심으로」「깊이」「다시 한번」 and frequently uses 「-ㄴ／은 점」 or 「-에 대해」 to clearly identify what is being apologized for.
- Example: 이번 일로 불편을 끼쳐 드린 점 진심으로 사과드립니다.
Romanization: i-beon il-lo bul-pyeon-eul kki-chyeo deu-rin jeom jin-si-meu-ro sa-gwa-deu-rim-ni-da.
Translation: We sincerely apologize for the inconvenience caused by this incident.
This corresponds to the Japanese 「このたびご不便をおかけしましたことを、心よりお詫び申し上げます」. Both clearly identify the inconvenience experienced by the other person and then make a formal apology on behalf of the speaker or organization. 「불편을 끼쳐 드리다」 is also an expression recognized by the National Institute of Korean Language. - Example: 잘못된 정보를 안내한 점 깊이 사과드립니다.
Romanization: jal-mot-doen jeong-bo-reul an-nae-han jeom gi-pi sa-gwa-deu-rim-ni-da.
Translation: We deeply apologize for providing incorrect information.
This corresponds to the Japanese 「誤った情報をご案内しましたことを、深くお詫び申し上げます」. This is not simply a personal, spontaneous apology. It formally acknowledges that incorrect information was provided, so both 「사과드립니다」 and 「お詫び申し上げます」 are more appropriate than an ordinary apology. - Example: 행사 취소 안내가 늦어진 점 진심으로 사과드립니다.
Romanization: haeng-sa chwi-so an-nae-ga neu-jeo-jin jeom jin-si-meu-ro sa-gwa-deu-rim-ni-da.
Translation: We sincerely apologize for the delay in notifying you of the event cancellation.
This corresponds to the Japanese 「イベント中止のご案内が遅くなりましたことを、心よりお詫び申し上げます」. Both are suitable for external notices issued by organizers or companies, and they are usually followed by information about refunds, rescheduling, contact details, or further arrangements.
◆ Core difference between Japanese and Korean workplace apologies:
「죄송합니다」 directly expresses that the speaker feels sorry and has a relatively broad range of use. It can be used for lateness, delayed replies, document errors, and temporary inconvenience. 「사과드립니다」 more explicitly performs the act of apologizing and is often used when responsibility must be acknowledged, when speaking on behalf of an organization, or when issuing a formal statement. Japanese 「申し訳ございません」 and 「お詫び申し上げます」 have a similar division of roles: the former is natural in ordinary work-related communication, while the latter appears more often in formal letters and public notices.
However, 「죄송합니다」 is not necessarily lighter than 「사과드립니다」. Expressions such as 「대단히 죄송합니다」 and 「진심으로 죄송합니다」 can convey a very strong apology. Conversely, if a company simply writes 「사과드립니다」 without explaining the impact, correction method, or follow-up measures, the formal wording alone is not enough to make the apology effective. When translating workplace apologies, besides choosing the corresponding expression, you also need to check whether the sentence explains what happened, how the other person was affected, and what will be done next.
After something goes wrong at work, an apology does not need to be overloaded. Repeating 「申し訳ございません」 throughout the same email does not solve an extra problem each time it appears. If you are late, provide the new arrival time. If you sent the wrong file, explain which one should be discarded and which one is the corrected version. Even if the cause has not yet been fully investigated, you can still give the current status and the time of the next update.
「すみません」 is suitable for lighter situations, 「申し訳ございません」 can be used for formal business mistakes, and 「お詫び申し上げます」 appears more often in formal emails and public explanations. Whether to explain the reason, how much detail to give, and whether to include preventive measures depends on how much has actually been confirmed at that point. There is no need to present an uncertain cause as a conclusion simply to appear responsible, nor does every case require the stock phrase 「今後徹底します」. Start by stating what is already known accurately, then make clear what is being done now and when the recipient will hear from you again. In actual work, that kind of apology is often more useful.
FAQs
Usually, you should include an apology, the confirmed facts, the current response, and the next update time or completion time.For a simple issue, there is no need to force the message into four full sections. For example, a lateness notice can simply say 「申し訳ございません。到着が十五分ほど遅れます」. The key is that the other person can immediately decide what to do next after reading it.
Yes. It is very common for small mistakes between coworkers, brief interruptions, in-person requests, and short waits.If the situation involves a customer, a delivery deadline, incorrect documents, or a more noticeable impact on work, 「申し訳ありません」 or 「申し訳ございません」 is usually more appropriate in terms of formality.
Both can be used for formal apologies. 「申し訳ございません」 is more respectful and is common with customers, supervisors, and external service users, while 「申し訳ありません」 can be used in ordinary business communication.A more serious incident does not automatically mean you should keep increasing the level of honorific language. The relationship between the parties and the overall writing style also matter.
「申し訳ございません」 is common in speech, phone calls, and email. 「お詫び申し上げます」 has a stronger written tone and higher level of formality, and it appears more often in formal emails, notices, and corporate statements.For an ordinary phone call about being late, 「申し訳ございません」 is generally more natural than 「お詫び申し上げます」.
「ご迷惑」 refers to broader trouble or impact, such as delays, errors, or failures.「お手数」 specifically refers to making the other person perform an additional task, such as checking again, re-entering information, or resubmitting something. If the same issue causes both kinds of impact, the two expressions may be used separately in different sentences.
It is commonly used for system failures, facility maintenance, service suspensions, transportation disruptions, and other situations where users cannot operate or act in the normal way.For example, 「システム障害により、ご不便をおかけしております」 is a typical use.
The highest priority is to communicate the apology and the new time information.You can say 「申し訳ございません。電車の遅延により、到着が十分ほど遅れます」. One sentence explaining the reason is enough; there is no need to describe the traffic situation in detail first.
Simply state the situation that has been confirmed so far. There is no need to guess.For example: 「現在、原因を確認しております。ご不便をおかけし、申し訳ございません。本日十五時までに改めて状況をご連絡いたします」. The cause can be explained later; first make the next update time clear.
Not necessarily. A minor one-off mistake may not require a formal explanation of recurrence-prevention measures.If an incident has a larger impact and improvement measures need to be explained, the measures should be specific and related to the cause. If the cause has not yet been identified, you can first say 「原因を確認したうえで、再発防止策をご報告いたします」.
It can appear in some customer-service expressions, but if you want to clearly acknowledge that your own checking process is taking time, 「確認に時間を要しており、お待たせして申し訳ございません」 is usually more direct.「お時間をいただく」 tends to focus on receiving time from the other person. When apologizing for a delay, it is often clearer to state directly that your side needs time and that the other person has been kept waiting.
It is not completely unnatural. 「お手間を取らせる」 can mean making someone go to extra trouble and can be used in an apology.However, in business email, when referring to extra actions such as reconfirming, filling something in again, or replying again, 「お手数をおかけし」 is extremely common and connects more naturally to a concrete work burden. If the focus is on taking up a large amount of the person’s time, 「お時間を取らせてしまい」 can be used.
Yes, but they should match the seriousness of the incident.「誠に申し訳ございません」「深くお詫び申し上げます」「心よりお詫び申し上げます」 all increase the weight of the apology. Using the strongest form for every minor mistake can make the wording feel disproportionate to the actual incident.
You should explain the facts that have been confirmed, but you do not need to speculate about responsibility when the information is still incomplete.If it has been confirmed that the problem resulted from insufficient checking on your side, you can acknowledge it directly. If the cause is still under investigation, first communicate the current impact, temporary response, and next update time. A formal explanation of responsibility can follow after the facts have been confirmed.
It is not a single JLPT grammar item. Basic expressions such as 「すみません」 and 「申し訳ありません」 are encountered relatively early, but using 「ご迷惑をおかけする」「お詫び申し上げる」, humble language, and different levels of formality across business situations requires a more complete understanding of Japanese honorific language.In actual workplaces, the focus is less on a single JLPT level and more on whether you can choose the appropriate expression based on the situation, the relationship between the parties, and the impact of the incident.