Japanese Calendar and Scheduling Localization:
Eras, Holidays, and the Week That Starts on the Wrong Day

TL;DR

Key Takeaways

• Default to 西暦, support 和暦 where it is required — everyday scheduling can use 2026年, but government, contract, tax, and finance contexts still expect 令和 (Reiwa). Never hard-code only one.
• The Japanese week starts on Sunday — with Sunday traditionally in red and Saturday in blue. A Monday-start grid with no weekend coloring reads as foreign at a glance.
• Japan has 16 national holidays plus 振替休日 — a holiday on a Sunday creates a substitute holiday on the next working day. Mark holidays in the picker and respect them in business-day logic.
• 営業日 (business-day) logic must exclude weekends and holidays — delivery, settlement, and SLA estimates that count holidays as working days are wrong in Japan.
• The fiscal year (年度) starts in April for most organizations — date ranges, reporting periods, and "this year" framing read differently when the year pivots on April 1, not January 1.

和暦 vs 西暦: Where Each Era System Is Expected

Japan runs two parallel year systems. The Western calendar year — 西暦 (seireki) — is 2026. The Japanese era year — 和暦 (wareki) — is currently 令和 (Reiwa), and 2026 is 令和8年. Both are in daily use, and the mistake most foreign software makes is assuming it must pick exactly one. The right answer is context-dependent, and getting it wrong in either direction creates friction.

For general scheduling, booking, and most consumer or B2B SaaS interfaces, 西暦 is the safe default. Japanese users are entirely comfortable reading and entering 2026年 for appointments, deadlines, and calendar events. Forcing 和暦 into a casual booking flow would feel oddly formal, the way a Western app insisting on Roman numerals for years would feel to an English user.

But 和暦 is not optional everywhere. Government forms, official documents, contracts, tax filings (確定申告), insurance, and many financial products still expect — and sometimes legally require — the era format. A FinTech product that only accepts 西暦 on a form that maps to an official filing will force users to convert in their heads, and a healthcare or insurance product that displays a policy date only in 西暦 may mismatch the paper documents the user is holding. The failure mode is hard-coding a single system. The localized approach is to default to 西暦 for everyday UI while supporting 和暦 input and display anywhere the product touches official, legal, or government-adjacent workflows — ideally showing both, e.g. 2026年（令和8年）, in those contexts.

One more era subtlety: era boundaries do not align with calendar years. 令和 began partway through 2019, so the first year of an era (元年) and the transition between eras can produce edge cases in date math and historical records. Software that supports 和暦 must handle 元年 (the "year one" of an era is written 元年, not 1年) and must not assume a clean one-era-per-decade mapping.

The Week That Starts on the Wrong Day

Open almost any Japanese wall calendar, pocket diary, or printed schedule and the week starts on Sunday (日). This is the dominant convention in Japan, and it carries a visual grammar that goes with it: Sunday is printed in red, Saturday in blue, and the two together read instantly as the weekend. Public holidays are also marked in red, sharing the visual language of "non-working day."

Many calendar and date-picker components inherit their week-start from the developer's locale or a library default — often Monday (the ISO standard) or a US-style Sunday-start without the coloring. A Monday-start grid is not wrong in the abstract, but to a Japanese user scanning a familiar shape, it is subtly off: the columns are shifted, the weekend is not where the eye expects it, and weekends and holidays are not visually distinguished from working days. The user has to recount the grid instead of recognizing it.

The weekday abbreviations themselves are single kanji: 月火水木金土日 (Monday through Sunday). Japanese calendar headers use these one-character forms, not romanized "Mon/Tue" or full words. A date picker that shows "Mon Tue Wed" in a Japanese interface is an immediate tell that the calendar was not localized — only the surrounding chrome was.

Public Holidays and 振替休日

Japan has 16 national public holidays spread across the year, from 元日 (New Year's Day, January 1) through 天皇誕生日 (the Emperor's Birthday) and the cluster of holidays in late April and early May known as ゴールデンウィーク (Golden Week). On these days, most offices, banks, and government services are closed — which means any software that schedules, books, ships, or settles needs to know about them.

There is an additional rule that trips up holiday logic written for other countries: the substitute holiday (振替休日). When a national holiday falls on a Sunday, the following working day becomes a holiday in its place. So a naïve holiday list that only contains the fixed dates will be wrong in any year where a holiday lands on a Sunday — it will miss the substitute day entirely, marking a closed day as open.

Practically, this means loading and maintaining an up-to-date Japanese holiday calendar rather than hard-coding dates. Holiday dates can shift — some are defined by rules like "the third Monday of a month" (ハッピーマンデー), and the government occasionally adds one-off holidays for special events. A product serving Japan should treat the holiday calendar as data that is refreshed annually, mark holidays visually in date pickers (typically in the same red as Sundays), and exclude them from any business-day calculation.

午前/午後, the 24-Hour Clock, and 曜日

Time display in Japan accommodates two formats, and the right choice depends on the surface. The 24-hour clock is common and unambiguous — 14:00 is widely understood and standard in transport timetables, business systems, and official schedules. The 12-hour format uses 午前 (AM, literally "before noon") and 午後 (PM, "after noon"), placed before the time: 午後2時, not 2時午後. A literal port of an English "2:00 PM" layout that puts the meridiem after the time, or that uses "AM/PM" in Latin letters, reads as untranslated.

Dates in running text and UI commonly attach the weekday in parentheses with the single-kanji form: 2026年6月11日（木） — year, month, day, then the weekday 木 (Thursday) in parentheses. This 「（曜日）」 convention is pervasive in Japanese scheduling contexts, and including it makes dates feel correctly formatted. Omitting the weekday, or spelling it out in English, are both small signals that the date format was not localized.

営業日: Business-Day Logic and the Fiscal Year

Estimates phrased as "within 3 business days" appear constantly in Japanese commerce, support, and finance — and the Japanese term is 営業日 (eigyōbi, business day). The user reading 「3営業日以内」 expects the count to exclude weekends and national holidays. Software that counts calendar days, or that counts weekends and holidays as business days, produces estimates that are simply wrong: a "3 business day" delivery promised over Golden Week will arrive far later than the date the system displayed.

Correct 営業日 logic requires the same holiday calendar described above, combined with weekend exclusion. It also needs to handle the substitute-holiday rule so that a 振替休日 is not counted as a working day. This is not cosmetic — for shipping windows, settlement dates, SLA commitments, and support response times, the business-day count is a promise the product is making to the user.

The other date concept that reshapes Japanese scheduling is the fiscal year, 年度 (nendo). For most Japanese organizations — companies, schools, and government — the 年度 commonly starts on April 1 and ends March 31 of the following year. This is distinct from the calendar year (年). When a Japanese user sees a reporting period, an annual plan, or a "this year" filter, their mental model may pivot on April, not January. The school year, the hiring cycle (新卒採用), budget cycles, and many subscription and reporting flows all align to 年度. A dashboard or scheduling tool that only offers January-to-December ranges, with no concept of 年度, forces Japanese business users to do mental arithmetic on every annual figure.

The localized approach is to offer 年度-based ranges as a first-class option wherever annual periods appear — a "2026年度" range that runs April 2026 to March 2027 — alongside the calendar year, and to label them clearly so users know which boundary they are looking at.

Scheduling and Booking Copy: 予約 and 日程調整

Beyond the mechanics of the calendar grid, the words around scheduling carry their own conventions. The core noun is 予約 (yoyaku, reservation/booking), used for appointments, restaurant tables, and meeting slots alike. The act of finding a mutually convenient time — the back-and-forth that English calls "scheduling" — is 日程調整 (nittei chōsei), and it is a distinct, recognized concept in Japanese business culture, often involving proposing several candidate times (候補日) for the other party to choose from.

Booking copy should use these established terms rather than literal translations. A button labeled with a calque of "Book now" can land awkwardly; 「予約する」 is the natural form. A flow that proposes times should frame them as 候補 (candidates) and use 日程調整 framing rather than a literal rendering of "let's find a time." And because Japanese business communication leans toward politeness in transactional moments, confirmation and reminder copy reads better in plain-polite (です/ます) form — 「ご予約ありがとうございます」 — than in a clipped, command-style register.

Calendar and Scheduling Localization Checklist

Four Before/After Scheduling Examples

Example 1: Date Display in a Confirmation

Example 2: Calendar Header Row

Example 3: Business-Day Estimate

Example 4: Annual Reporting Range

Frequently Asked Questions