Japan renewal dates that miss the customer's budget year

Published Sep 26, 2026 Updated Oct 17, 2026

A renewal reminder fires ninety days out, right on schedule, for an account your team considers healthy. Then it stalls, the same way it stalled last year, and the year before that with a different account in the same industry.

Nobody in Japan says the product isn’t working. The renewal is simply not on anyone’s approved list of spend for the year it happens to fall in.

Renewal dates set from the signature date ignore a calendar that already exists

Most CS platforms date the renewal from the day the contract was signed. Sign in September, renew the following September. It is a clean rule, and it has nothing to do with when the customer’s fiscal year runs.

Most large Japanese companies run an April to March fiscal year. Of companies listed on the Tokyo Stock Exchange’s Prime Market, 68% close their books in March, 13% in December, and 5% in February (Nomura Securities Investment Information Department, published March 2023, based on TSE Prime company filings).

Budgets for the year starting in April are typically built the preceding January and February.

A contract signed in September renews the following September, so the renewal has to be in the budget built that January or February, four to five months after go-live.

But the 90-day reminder, counted from the signature date, fires in June. By the time the vendor raises the renewal, the budget that has to pay for it was locked four months earlier.

The first purchase is often funded mid-year from a contingency or a department’s discretionary pool. Four or five months in, with little evidence of value yet, few champions will put the renewal into next year’s budget unprompted.

”They’re already using it” is not the argument that gets a renewal approved

HQ tends to assume a renewal carries less friction than a new deal. The evaluation is done, the product is in use, the account is satisfied. Surely the approval is lighter.

In many Japanese organisations, what determines whether spend clears easily is not satisfaction. It is whether that spend has a line in the current year’s budget table.

If it does, renewal is signing off a row that was already planned. If it does not, someone has to open a new approval for supplementary or reallocated budget, at the same weight as a new purchase, regardless of how long the product has been running.

Occasionally it is heavier, because the champion now has to explain why something already in use needs a fresh approval at all.

Two equally satisfied accounts can carry completely different renewal risk

Take two customers on the same product, equally satisfied, same usage. One signed in April, so its 90-day reminder fires in January, exactly when next year’s budget is being assembled. The other signed in September, so its reminder fires in June, after that year’s budget has closed.

A CS health score will not tell these two accounts apart. Both show the same usage and the same sentiment.

But one renewal needs no new approval and the other does, and the difference has nothing to do with the account manager or the product.

When a regional dashboard shows the September cohort renewing worse than the April cohort, the read is usually “Japan satisfaction is soft.” What is actually different is where the renewal date happens to fall on a fiscal calendar nobody built the CS motion around.

Two fixes that do not work

Moving the reminder from 90 days to 120 days does not solve this.

For a September renewal, 120 days out is May, still well after the January and February budget window. The earlier warning only tells you sooner that the account has no budget line, not how to get one created outside the planning cycle.

Multi-year contracts were also considered and set aside. The first term still has to land inside some fiscal year’s budget at signing, and Japanese buyers, especially early in a vendor relationship, are often reluctant to commit multiple years before they have seen a full cycle of value.

When multi-year deals do get signed, the renewal conversation usually still carries a price step-up, which reopens the same fiscal-year mismatch at a larger number.

Two moves, used together.

1. Put next year’s fee into the first purchase approval as a planned amount. When the September purchase goes through the customer’s internal approval, ask the champion to include next fiscal year’s annual fee as a planned figure.

When next year’s budget is built in January and February, the champion is no longer asking for a new line from zero. To support that, the vendor hands the champion a one-page summary of actual usage by December.

The evidence is thin four or five months in. That is exactly why the vendor should prepare it rather than wait for the customer to.

2. End the first contract term at the customer’s fiscal year end. A September signature becomes a seven-month first term running to the following March, prorated, with the twelve-month cycle starting from there. Every subsequent renewal then falls in April, and its 90-day conversation lands in January, inside the customer’s budget window.

Move 2 on its own still leaves the first renewal to be budgeted four or five months after go-live, which is the problem described above. Move 1 carries the first renewal; move 2 puts every renewal after it on the customer’s budget calendar.

Where that renegotiation is not available, the minimum fix is a field. Record the customer’s fiscal year end in the CRM as a property separate from the contract date, and start the renewal conversation counting back from the customer’s budget planning window (roughly January and February for an April start), not from the contract’s own anniversary.

It costs one field and one changed habit, and it tells the Japan team, months earlier, whether this renewal has anywhere to go.

The wider approach to designing revenue processes around the buyer’s calendar rather than the seller’s is in Japan Market GTM and Messaging.

If the renewal conversation starts after the customer’s budget is fixed, the renewal needs a fresh approval no matter how satisfied the account is. Carry the first renewal in the first purchase approval, and align every renewal after it to the customer’s fiscal year end. The reference point is the customer’s fiscal year, not the signature date.

This week, pull every account with an upcoming renewal and compare two dates: the day your renewal conversation starts (renewal date minus 90 days) and the month the customer locks the budget for the fiscal year that renewal falls in (around February for an April start).

Every account whose conversation starts after that month is a renewal your Japan team will likely have to re-argue from budget zero. Where the customer’s fiscal year end is not in the CRM, fill that in first.

Common mistakes

Reading a soft renewal rate in one signature cohort as a satisfaction problem. Check whether the renewal conversation started after the customer’s budget was locked before concluding anything about the account.

Moving the reminder earlier without moving the renewal date. An earlier warning about a bad landing spot is still a bad landing spot.

Assuming multi-year contracts solve this. They defer the mismatch to a bigger renewal with a price increase attached, and Japanese buyers new to a vendor relationship often will not sign multi-year in the first place.

Treating the fiscal year end as something only finance needs to know. It belongs in the CRM, next to the renewal date, as the field that tells you whether this renewal has a budget line to land on.

The same fiscal-year mismatch shows up on the marketing side in Adapt the Japan campaign, keep the global pipeline wiring. That note is about campaign timing; this one is about renewal timing.

Other notes on the same problem are collected under Japan market entry.