The Renewal Was Budgeted Last Autumn.
Your Price Increase Was Not.

▶ 60-Second Slide Summary Prefer the 8-slide version of this article? Tap to read in 60 seconds. View slides →

Quick Answers

When should a SaaS vendor tell a Japanese customer about a price increase for an April renewal?

Before the customer builds its budget for the next fiscal year. For a company whose year starts on 1 April, that work generally runs from the preceding autumn into the winter, so a written notice in the autumn — and no later than the end of the calendar year — gives the new price a chance to be inside the number that gets approved. A notice in February or March usually arrives after the budget is fixed.

Is there a legal notice period for price increases in Japan?

Not a general one that sets a date for B2B software subscriptions. The three months many vendors give is business practice. The notice period that binds you is the one in your own contract or terms of service, so read that clause first.

TL;DR

Most Japanese enterprise customers run an April-to-March fiscal year, and the budget that pays for your April renewal was generally built in the autumn and fixed over the winter — at last year's price. An increase that arrives in February or March does not adjust that budget. It needs a new internal approval, which takes time, requires a written justification and invites a comparison with alternatives. Send the notice before the budget is drafted: in the autumn, and by the end of the calendar year at the latest. Write it in Japanese, as a document the person drafting the approval can attach — new price, effective date, reason, the conditions under which the current price holds, and the multi-year or annual prepayment options. The three-month notice period is practice, not law; your contract's notice clause is what binds you.

Key Takeaways

• The renewal was budgeted months ago. For an April renewal, the money was requested in the autumn and approved over the winter, at the price your customer knew at the time.
• An increase is a new approval, not an edit. Anything above the approved amount goes back through ringi, with a reason, a new sign-off and often a question about alternatives.
• Three months is a habit, not a statute. No general rule fixes a notice period for B2B subscription price increases. Your contract or terms of service set it.
• Send it before the budget is drafted. Autumn for an April-start customer, and the end of the calendar year at the latest. For other fiscal years, count back from their start date.
• Write for the ringi, not the inbox. A Japanese written notice with the price, date, reason and options is something the champion can attach. A pricing-page link is not.

The Email That Went Out in February

The pattern is familiar enough to describe without naming anyone. A Japanese enterprise customer has been on an annual subscription since its first April. The user department likes the product, the contract renewed quietly last year, and nobody on the vendor side thinks of the account as a risk. In the global pricing cycle the increase is decided in January, the customer-success team sends a well-written English notice in February, and the April renewal date is treated as the natural moment for the new price to start.

The reply is courteous and noncommittal. The champion needs to confirm internally. Two weeks later they ask whether the old price could apply for one more year. Then the renewal date passes with a purchase order that has not arrived, and someone in their procurement team asks, for the first time since the original deal, whether there are comparable products.

From headquarters it looks like a customer pushing back on price. From inside the customer it looks like something else: a vendor asking for money that nobody had budgeted, at the one point in the year when there is no easy way to find it.

Why February Is Too Late

Most large Japanese companies run a fiscal year from 1 April to 31 March. It is not universal, but it is the default to plan against: the Tokyo Stock Exchange's own tally of results announcements for the year ended March 2025 covered 2,231 domestic listed companies with a March year-end. Group subsidiaries usually align with their parent, and Japan's national and local governments also run their fiscal year from April to March.

The budget for a year that starts in April is generally built in the preceding autumn and settled over the winter. Departments submit their requests, the requests are consolidated and cut, and by January or February the number for the coming year is largely fixed. We covered the sales side of this calendar in why deals slip to March in Japan. Renewals follow the same logic, and they are more exposed to it, because a renewal is the item nobody expects to discuss.

So the line for your product in next year's budget was written in the autumn, by someone who assumed the price would be what it was. By the time your February notice arrives, the question is no longer whether the new price is fair. It is where the difference comes from.

An Increase Is a New Approval, Not an Edit

Japanese companies approve spending through a written internal proposal, the ringi (稟議), which collects the sign-off of each person with authority over the purchase. The renewal was approved for a stated amount. A higher amount is not a correction to that document; it is a new decision, and it has to be justified to people who were not in the original evaluation.

The questions that come back are predictable. Why is the price going up? What changed in the service? Is the increase in line with the market? Were alternatives considered? None of these are hostile. They are the questions an approver is expected to ask before signing for money outside the budget, and the champion has to answer them in writing — in Japanese, usually with nothing from you except an English email and a link to a pricing page.

The last question is the expensive one. A renewal that goes back through approval with an unplanned increase is exactly the kind of item that procurement is asked to compare. You were never in a competitive process during the year. You are in one now, and it started because of the timing of your notice rather than the size of your increase.

Three Months Is a Habit, Not a Law

Many vendors give Japanese customers three months' notice of a price change, and many buyers expect roughly that. It is worth being precise about what it is: a business practice. There is no general Japanese rule that sets a notice period for price increases on business-to-business software subscriptions. The notice period that actually binds you is the one in your own agreement or terms of service — read that clause before you plan anything, because it may require more notice than the habit does, or a specific form.

You may also hear that Japan tightened the rules on pricing between companies. The Subcontract Act was amended and renamed, and since 1 January 2026 it has been in force under a new name, 中小受託取引適正化法 (the Toriteki Act, per the Japan Fair Trade Commission). Among other changes, it prohibits a commissioning business from deciding the price unilaterally without responding to a request to consult. That rule protects the smaller business that receives manufacturing, repair, content-creation or service work from the company that commissions it. It is generally not the relationship in which a foreign SaaS vendor sells a subscription to a Japanese customer, so it does not set your notice period or limit your increase. If your arrangement includes development work the customer has commissioned from you, ask counsel how it applies.

When to Send It

The goal is simple to state: the new price should be known before the customer drafts its budget request, so that the number that gets approved already contains it. For a customer with an April start, that points to the autumn, and to the end of the calendar year as the latest point at which a written notice still has a realistic chance of being included.

In practice that means deciding Japanese price changes on a different clock from the rest of the world. If your global pricing review happens in January, it is already too late for the April renewals of that year; either decide the Japan increase in the summer, or apply it from the following renewal and say so. For customers on a different fiscal year, count back from their start date in the same way — the renewal date matters less than the date their budget is drafted.

What the Notice Has to Contain

A notice that works in Japan answers, on one page, every question the approver will ask. At minimum:

• The new price, per unit and in total for the customer's current configuration, with a clear statement of whether consumption tax is included.
• The effective date, stated as a date and tied to the renewal it applies to.
• The reason, in concrete terms: what has changed in cost, capacity or the service itself. A short, factual reason is easier to put into a ringi than a general reference to market conditions.
• The conditions under which the current price holds — for example, a renewal signed before a given date, or an existing multi-year term.
• The options: a multi-year commitment, annual prepayment, or a different plan, each with its price, so the customer can choose a path that fits the budget it has.
• What happens if nothing is agreed by the effective date, and who to contact.

Write It for the Person Who Drafts the Ringi

Your champion is rarely the person who approves the increase, and often not the person who writes the proposal either. The reader who matters is whoever has to explain the new number to people who have never seen your product. Give that person a document they can attach, not an email they have to translate.

That means a formal notice in Japanese, issued as a PDF in your company's name and dated, rather than a message from a support mailbox. It means the reason written in terms an approver in finance or general affairs can accept. And it means sending it to the contract holder of record as well as the day-to-day contact, because a notice that reached only the user department may not reach the budget at all.

The same notice written in English for headquarters is fine to send alongside. It is not a substitute. An increase that the champion has to translate, justify and defend alone is the one most likely to end up in a comparison.

Increases That Are Easier to Approve

The size of an increase matters less in Japan than its shape. An approver who can see that the customer has a choice, and that one of the choices fits the budget already approved, has something to sign. An approver who is handed a single new number has only a question.

Structures that tend to travel well through an approval process:

• A price lock for a longer term. A two- or three-year renewal at a price close to the current one gives the customer certainty and gives you the commitment. It also turns the conversation from "why is this going up" into "which term do we want".
• Annual prepayment. Many Japanese companies already pay annually. A clear difference between the annual and the monthly price gives finance a reason to prefer the option that suits both sides.
• A phased increase. Part of the change this year and the rest at the next renewal, with both figures stated now, so the second step can be written into next year's budget rather than discovered in February.
• New pricing for additional volume only. Keeping existing seats or usage at the current price and applying the new price to anything added keeps the renewal itself inside the approved amount.

None of these are concessions for their own sake. They are ways of giving the champion a version of the renewal that can be approved inside the budget they have, while the full price is placed where it belongs: in the next budget, with notice.

Signs the Notice Has Not Reached the Budget

A notice can be delivered without being absorbed. The early signals are small and easy to read as routine questions:

• The champion asks for the notice again, or asks whether there is a Japanese version.
• You are asked for a formal quotation (見積書) for the renewal well before the renewal date.
• You are asked when the new price starts, although the date is in the notice — which often means the date has to be written into a proposal.
• Someone new appears in the thread, from procurement, finance or general affairs.
• The question "could the current price apply for one more year" arrives in January or later.

Each of these is an invitation to help, not a sign of trouble. Answer with the document the person needs — in Japanese, with the figures they will copy into their proposal — and ask directly when their budget for the coming year is decided. Most champions will tell you, and the answer gives you the date to plan the next increase against.

The Calendar, Worked Backwards

For an April renewal with a customer on an April-to-March year, a workable sequence looks like this:

• Summer: decide the Japan price change, check the notice clause in each contract, and prepare the Japanese notice and the options.
• Early autumn: tell the champion informally that a change is coming and roughly when, so it can be flagged in the budget request.
• Autumn, and no later than the end of the calendar year: send the formal written notice to the contract holder and the champion.
• January to February: confirm the renewal terms and the option chosen, and answer any follow-up questions from their approval process.
• April: the renewal starts at the price that was in the budget.

If you are already past the window for this year, the honest options are to hold the current price until the next renewal, or to phase the increase so that the part arriving this April is small enough to fit within the customer's discretion — and to say clearly, now, what the full price will be from the renewal after that.

Frequently Asked Questions