How to Politely Decline a Business Proposal in Japanese

This guide is for a sender who needs to decline a proposal or request; it is not a guide to guessing whether a recipient's tentative reply means rejection. Before choosing polite Japanese, confirm that the sender has authority to make the decision, whether the decline is based on current timing or is final for this proposal, and what future contact should remain open. Once a final decision has been made, do not replace it with 検討します or another expression that makes the outcome look unresolved. A reason should appear only when it is real and shareable—do not invent budget limits, resource constraints, priorities, or an internal review. Declining one proposal also does not automatically end an account, contract, transaction, or broader relationship. Employment matters and declines with contractual, financial, legal, service, or major strategic consequences require human review rather than an automatic message.

Plain-language answer

State only the decision you have authority to make. Distinguish a timing-based decline from a final decline, give a reason only when it is verified, and use a closing that matches whether unrelated contact may continue, changed conditions may reopen the proposal, or similar outreach should stop.

This is a decision guide, not a message that fits every recipient unchanged.

Why context matters

A sender who can decide may decline; a sender without authority should state only the role boundary and must not invent forwarding, internal review, or another person's action.

今回はお受けできません limits the decline to current timing or conditions, while 本件についてはお受けしないことにいたしました states a completed decision for this proposal.

Cold outreach, an internal request, an existing vendor or partner, and an existing customer require different relationship framing.

The closing can invite unrelated contact, allow reconsideration only if conditions change, or ask that similar outreach stop. These meanings should not be mixed.

A decline of the current proposal does not by itself end an account, transaction, contract, or ongoing relationship.

This guide does not cover: Interpreting another party's intent, making decisions outside the sender's authority, employment decisions, legal or contractual conclusions, and automatic wording for financial, service, public, or major strategic consequences are outside this guide.

What to check first

01
Confirm whether the sender can decide, can only recommend, can only state a role boundary, or has unclear authority.
02
Identify whether the proposal came from cold outreach, an existing vendor or partner, an existing customer, or an internal colleague.
03
Distinguish a timing-based decline from a final decision on this proposal.
04
Use a reason only when it is real, accurate, and shareable.
05
Choose the intended future-contact boundary: unrelated contact may continue, reopen only if conditions change, or no further similar outreach.
06
For an existing customer, vendor, or partner, check whether the relationship is standard or strategically important.
07
Identify any contractual, financial, service, legal, public, reputational, or employment consequence before using an example.

Authority comes before politeness

If the decision is outside your authority, do not send a decline on behalf of another person or promise that a department, manager, or reviewer will act. State only your role boundary and obtain human guidance on the next step.

Decision framework

Choose the decision statement and the future-contact closing separately. A polite sentence is still inaccurate if it overstates authority, finality, reasons, or the future relationship.

The sender lacks confirmed decision authority

Approach: Do not issue a decline. State only that the decision is outside the sender's authority and obtain human review.

Why: Polite wording cannot authorize a decision or promise another person's action.

Timing or present conditions do not work

Approach: Use a timing-bounded decline such as 今回はお受けできません.

Why: The wording should not turn a current constraint into a permanent refusal.

A final decision has been made for this proposal

Approach: State the completed decision directly and do not use 検討します or 見送る方向で進めています.

Why: An unresolved expression would misrepresent a decision that is already final.

An existing customer, vendor, or partner is involved

Approach: Limit the statement to this proposal and preserve only the future-contact boundary the sender actually selected.

Why: Declining one proposal does not automatically end or guarantee the broader relationship.

Future contact depends on changed conditions

Approach: Invite reconsideration only if the relevant conditions change.

Why: A conditional reopening should not look like a general invitation for repeated proposals.

A major strategic final decline or high-risk consequence is involved

Approach: Suppress ordinary examples and review the authority, full history, consequence, and next action with a human.

Why: The relationship, employment, contract, payment, service, legal, or public impact cannot be resolved as a wording preference.

Example messages

Copy the language only after checking that its stated conditions match the real situation.

Cold outreach: timing-based decline

Use when: The sender has authority, the current timing or conditions do not work, no reason should be stated, and no high-risk consequence applies.
Channel: Business email
Strength: Clear but limited to the present circumstances

ご提案いただきありがとうございます。今回はお受けできません。

Meaning and impression: Thank the sender and decline under the current circumstances without inventing a reason.

Why this wording: 今回は keeps the scope narrower than a final rejection of all future proposals.

Avoid when: Do not use it for a final decision, outside your authority, or when employment, contractual, financial, service, legal, or public consequences apply.

Cold outreach: final decline

Use when: The sender has authority, the decision is final for this proposal, a real reason can be shared, and no high-risk consequence applies.
Channel: Business email
Strength: Polite and final for this matter

ご提案いただきありがとうございます。［共有できる実際の理由］のため、本件についてはお受けしないことにいたしました。

Meaning and impression: State a completed decision about this proposal and include only a verified reason.

Why this wording: 本件について limits finality to the proposal instead of claiming the broader relationship is over.

Avoid when: Do not use a placeholder for an invented budget, resource, priority, or internal-review reason.

Existing relationship: timing-based decline

Use when: A standard existing customer, vendor, partner, supplier, contractor, or client relationship remains, and current timing does not work.
Channel: Business email or an established email thread
Strength: Relationship-aware and timing-bounded

平素よりお世話になっております。今回はお受けできません。

Meaning and impression: Acknowledge the established relationship and decline only under the current circumstances.

Why this wording: The sentence does not invent a reason or state that the account, contract, or transaction is ending.

Avoid when: Do not use it for a major strategic final decline or as a guarantee that the broader relationship will continue unchanged.

Internal request: final decline

Use when: The sender can decide for their own role, the decision is final for this internal request, and no high-risk or employment issue applies.
Channel: Internal email or established work chat
Strength: Direct and neutral

提案ありがとうございます。今回は引き受けないことにしました。

Meaning and impression: Thank the colleague and state the completed decision without inventing an internal process or reason.

Why this wording: The wording is less ceremonial than an external letter while keeping the decision clear.

Avoid when: Do not use it for hiring, dismissal, discipline, performance, or another employment-related matter.

Reopen only if conditions change

Use when: The selected future-contact boundary permits another proposal only after relevant conditions change.
Channel: Business email
Strength: Conditional and bounded

前提条件が変わる場合は、その際に改めてご相談ください。

Meaning and impression: Allow reconsideration only if the underlying conditions change.

Why this wording: The closing avoids an open invitation for immediate or repeated resubmission.

Avoid when: Do not use it when the sender wants similar outreach to stop or when no genuine changed condition could reopen the matter.

Ask that similar outreach stop

Use when: The selected future-contact boundary is no further similar proposals or requests.
Channel: Business email
Strength: Clear boundary

今後、同様のご提案に関するご連絡はお控えください。

Meaning and impression: Ask the sender not to make further similar proposals without making a statement about unrelated contact.

Why this wording: The sentence does not accidentally invite another version of the same proposal.

Avoid when: Do not use it when normal similar outreach should remain open or when an existing strategic relationship requires review.

Expressions to avoid—or use carefully

検討します／見送る方向で進めています

Why it can be a problem: It can make a completed decline look unresolved.

Problem conditions: It is misleading after the sender has made a final decision.

When it may work: Use tentative wording only when the decision is genuinely still pending and the sender has authority to describe that process.

Safer alternative: State the final decision for this proposal when that is the verified outcome.

Example: 本件についてはお受けしないことにいたしました。

予算の都合で／リソース不足のため／社内で検討した結果

Why it can be a problem: A plausible explanation can still be false.

Problem conditions: It is unsafe when the structured facts do not establish that exact reason or process.

When it may work: Use a short reason only when it is real, accurate, and shareable.

Safer alternative: Omit the reason clause or use the verified reason.

担当部署へ共有します／責任者へ転送します／改めて回答します

Why it can be a problem: It promises routing or future action outside the sender's established authority.

Problem conditions: It is unsafe when the sender cannot verify who will act and what they agreed to do.

When it may work: Use it only when the action and authority are confirmed.

Safer alternative: State only the sender's role boundary and obtain human guidance.

また別の件で相談しようと思います

Why it can be a problem: It can invite future contact that the sender did not intend.

Problem conditions: It conflicts with a no-further-similar-outreach boundary.

When it may work: Use a future-facing closing only when that exact contact boundary was selected.

Safer alternative: Choose a closing that matches unrelated contact, changed conditions, or no further similar outreach.

An automatic decline for an employment-related matter

Why it can be a problem: Hiring, dismissal, discipline, performance, and other employment decisions can involve procedure, rights, and significant personal impact.

Problem conditions: Ordinary reference messages are suppressed for employment-related risk.

When it may work: Only after the responsible HR or management owner and any necessary specialist confirm the process and wording.

Safer alternative: Send the decision, authority, procedure, and relevant clause for human review.

Cultural context without stereotypes

A direct decline is not automatically rude, and a vague decline is not automatically considerate. Accuracy about authority and finality matters more than adding ceremonial language.

External business email may use more framing than established work chat, but the actual relationship and earlier thread should guide the level of formality.

Do not assume that every Japanese recipient expects an indirect rejection. Some teams prefer a short, explicit decision that saves further follow-up.

When future contact is unclear, confirm the intended boundary instead of adding a conventional invitation that the sender does not mean.

When human review is recommended

Ask for review of the uncertain decision or high-risk clause—not necessarily a complete rewrite of every sentence.

The sender cannot confirm authority to make the decline.Review the decision owner and next step. The automatic output should be limited to a role-bounded authority statement, not a decline or forwarding promise.
The matter involves employment, hiring, dismissal, discipline, performance, or another employment-related decision.Have the responsible HR or management owner verify the procedure, authority, facts, and exact decision language, with specialist advice where needed.
A contract, payment, refund, pricing, termination, service continuity, legal right, regulation, liability, or formal notice is involved.Review the full relevant clause, factual basis, authority, and operational consequence rather than only the polite ending.
A final decline affects a major or strategically important existing customer, vendor, partner, supplier, or contractor.Review the relationship history, decision authority, commercial consequence, and complete follow-up plan.
The decline may create a material public commitment or reputational consequence.Confirm what is actually public, who may speak, and which exact statement needs approval; do not infer public visibility from private correspondence.

Check the context before drafting

Identify which authority, relationship, decision-stage, reason, future-contact, and risk questions affect your situation. The current check does not analyze or rewrite the text of your message.

Open Message Context Check