Your headquarters has been running SAP or Microsoft Dynamics for ten years. Your Tokyo subsidiary opened two years ago. And yet, every month-end close, your financial controller spends three days manually reconciling Japanese data with the European consolidation. This is not a skills problem — it is an architecture problem.
Japan imposes four constraints that consistently catch European IT directors off guard: a Qualified Invoice System (QIS) that came into force in October 2023 — the functional equivalent of European e-invoicing; a dual consumption tax rate of 10% and 8% (reduced rate for food) with progressive deductibility rules for unregistered suppliers; an April-to-March fiscal year that is incompatible by default with most Western ERP configurations; and a local software market dominated by five Japanese vendors virtually unknown outside Japan. This guide is written for the CIO or CFO of a European mid-market company managing or planning a Japanese operation.
1. The Japanese ERP Market: 2026 Overview
1.1 Five Local Vendors You Need to Know
The Japanese SME ERP market is structured around five local players that appear in no European Gartner Magic Quadrant:
Yayoi is the historic leader for SME and micro-business accounting with approximately 3.4 million users (AQ Partners, accounting software Japan guide). Long desktop-anchored, it has migrated to its cloud ecosystem “Yayoi Online”. Yayoi is certified as a Peppol service provider by the Japanese Digital Agency. Its primary target: sole traders, micro-businesses, and very small SMEs.
TKC Corp. is a distinctive player: an ERP vendor embedded within a network of licensed accounting firms (TKC member firms). Its FX4 Cloud solution is widely deployed among Japanese SMEs that work with a TKC accountant. Regulatory compliance (QIS, consumption tax, payroll) is updated centrally for all clients simultaneously — a decisive advantage during legislative changes. Its limitation: limited openness to group integrations.
PCA Corp. targets SMEs with up to 300 ERP users, offering an accounting-payroll-HR-procurement suite. Distributed through a trusted reseller network, it represents a credible alternative to Yayoi for organisations that need proper purchasing and sales modules.
Obic serves Japanese mid-market companies with its modular Obic7 suite. Its client base includes many mid-size companies listed on the Tokyo Stock Exchange (TSE). Documentation and interfaces are almost exclusively in Japanese.
Freee is the cloud success story of the decade. Founded in 2012, the company reports 621,000 paying customers as of 30 September 2025, including 245,000 businesses, with an ARR of ¥35.5 billion (Freee Factbook, October 2025). Its preferred target: startups, entrepreneurs, and service-sector SMEs. Its API-first architecture makes it integrable, but its modules remain focused on accounting and HR — it does not cover complex manufacturing or supply chain workflows.
1.2 International ERPs and the Cloud Growth Story
The Japanese cloud ERP market is valued at approximately USD 5.4 billion in 2026 and is expected to reach USD 15 billion by 2034, at an estimated CAGR of 15.8% (DataM Intelligence, Japan Cloud ERP Market). SAP holds approximately 24.5% of the ERP market share in Japan, ahead of Oracle (~19.8%) and Microsoft (~14.6%), according to industry estimates (Spherical Insights, Japan ERP Software Market).
International ERPs are present primarily in large Japanese enterprises (>1,000 employees) and in local subsidiaries of multinational groups. Adoption among Japanese SMEs remains limited, held back by insufficiently localised interfaces, high deployment costs, and the absence of local accounting partners within their ecosystems.
2. Mandatory Regulatory and Tax Requirements
2.1 Qualified Invoice System (October 2023): Concrete Impact on Your ERP
The Qualified Invoice System (QIS, Tekikaku Seikyûsho Seido in Japanese) came into force on 1 October 2023. It represents the most significant change to Japan’s consumption tax regime since the introduction of JCT in 1989.
The principle: only issuers registered with Japan’s National Tax Agency (NTA) can issue qualified invoices that allow their customers to deduct consumption tax in full. Each issuer receives a unique number in the format T + 13 digits (T-number), verifiable on the official NTA portal (invoice-kohyo.nta.go.jp). Approximately 4.8 million businesses were registered by end-2024 (invoicedataextraction.com, Japan QIS Guide).
Direct impact on your ERP: every supplier invoice must now display the issuer’s T-number, and your ERP must store that number, validate it against the NTA database, and associate it with each purchase line eligible for tax deductibility. An ERP not configured for QIS will automatically generate JCT deductibility errors.
The transition period: for purchases from suppliers not registered under QIS, deductibility follows a phased schedule (invoicedataextraction.com, Japan QIS Guide):
| Period | Deductibility Rate |
|---|---|
| October 2023 – September 2026 | 80% |
| October 2026 – September 2028 | 70% |
| October 2028 – September 2030 | 50% |
| October 2030 – September 2031 | 30% |
| From October 2031 | 0% |
For a B2B subsidiary with many small unregistered independent suppliers (freelancers, sole traders), this exposure becomes financially significant from October 2026.
2.2 Japanese Consumption Tax (JCT): Dual Rate in Your ERP
Japan’s consumption tax (JCT) applies at two rates since 2019: 10% standard rate, and 8% reduced rate applicable to food items (excluding alcohol and restaurant meals) and newspaper subscriptions with more than two issues per week. Your ERP must handle both tax codes simultaneously on mixed invoices.
Unlike European VAT, JCT is a partially recoverable cascade-style tax. Importers pay JCT at Japan Customs and can recover it through their semi-annual or monthly JCT declaration (depending on annual turnover).
2.3 Japan’s Fiscal Calendar: April-to-March Year-End and Its Implications
The vast majority of Japanese businesses, and the entire Japanese government, close their fiscal year on 31 March (Mailmate, Japan’s Fiscal Year). For a subsidiary of a European group whose headquarters closes on 31 December, this creates two concrete challenges.
First challenge: a three-month offset for interim consolidation. IFRS standards tolerate a maximum three-month gap between closing dates of consolidated entities — which is exactly at the limit for a December-March group. Second challenge: the need to produce a “shadow” set of accounts as at 31 December for group reporting purposes, with extrapolation or confirmation of the subsidiary’s data.
The good news: Japanese company law allows foreign-owned subsidiaries to freely choose their accounting year-end, including a December-to-December year aligned with headquarters. Check with your local tax advisor whether this option is viable for your structure — it simplifies ERP consolidation considerably.
2.4 Peppol, E-Invoicing, and the 2027 Horizon
Japan’s Digital Agency has been the Peppol authority for Japan since September 2021. The adopted format is JP PINT (Japanese Peppol International). B2B e-invoicing via Peppol is not yet mandatory, but it is actively promoted, and a B2B mandate is expected around 1 January 2027 according to industry projections (Group Serès, E-invoicing in Japan).
The main local ERPs (Yayoi, Freee, TKC) are certified Peppol service providers by the Digital Agency (Digital Agency Japan, Peppol Certified Service Providers). For international ERPs, verify the existence of a certified JP PINT connector before starting any project.
2.5 Digital Hanko and Electronic Archiving (EBPA)
The hanko — the physical corporate seal affixed to contracts and invoices — is still used by over 90% of Japanese businesses. The Digital Agency is pushing dematerialisation via e-seal (electronic seal), with the goal of reducing by 90% the administrative procedures requiring a physical hanko.
For your ERP, this transition is an opportunity: internal approval workflows (purchase orders, invoice validation) can now be dematerialised via electronic signature. Confirm with your local partners that dematerialised workflows comply with Japanese law.
Furthermore, the Electronic Book Preservation Act (EBPA, reformed in January 2022, mandatory since January 2024) requires digital archiving of electronically received data with searchability, tamper-evidence, and timestamping requirements. Your ERP or document management system must be configured to meet these obligations.
3. Choosing Between Local and International ERP: Decision Criteria
3.1 When a Local Japanese ERP Makes Sense
For a subsidiary with fewer than 150 ERP users, primarily local workflows, and no real-time consolidation requirement with the group, a local ERP is the more pragmatic choice. The case is compelling:
- Native compliance: QIS, JCT, Japanese payroll, and EBPA are handled natively and updated automatically with each regulatory change.
- Japanese interface: kanji, kana, date formats (Reiwa era), and banking formats (Zengin) are built in.
- Accounting partner network: TKC and Yayoi are deeply integrated into Japan’s accountant ecosystem.
- Cost: 3 to 5 times cheaper to deploy than an international ERP with a Japan localisation module.
3.2 When a Japan-Certified International ERP Makes Sense
For a subsidiary with more than 200 ERP users, integrated into a group supply chain, or with IFRS consolidation requirements, an international ERP with certified Japan localisation is the recommended path:
- Group IT consistency: a single platform across headquarters and subsidiary reduces integration costs and accelerates consolidation.
- Advanced modules: WMS, treasury, integrated CRM, and analytical reporting available on the same platform.
- SOX compliance and internal controls: audit trail and segregation of duties requirements that local ERPs do not fully cover.
3.3 The Two-Tier Approach for Japan
Many European mid-market companies with Japanese operations adopt a two-tier architecture: the international ERP (SAP, Oracle, D365) for group functions (finance, consolidation, strategic procurement), and a local ERP (TKC, PCA, or Freee) for day-to-day local operations with monthly synchronisation. This approach controls costs while guaranteeing local compliance.
| Criterion | Local ERP (Freee / TKC / PCA) | Certified International ERP | Two-Tier |
|---|---|---|---|
| Target subsidiary | <150 users, local operations | >200 users, group integration | 100–300 users, rapid growth |
| QIS/JCT compliance | Native | Certified module required | Local ERP for compliance |
| Japanese interface | Native | Varies by vendor | Local ERP for operations |
| IFRS consolidation | Limited | Native | Monthly export to group IS |
| Deployment timeline | 3–6 months | 9–18 months | 5–10 months |
| Indicative budget | ¥3–15M | ¥50–300M | ¥15–50M |
4. International ERPs Certified for Japan
4.1 SAP S/4HANA Japan: Localisation and Partners
SAP is the most established international vendor in Japan, with approximately 24.5% of the ERP market according to industry estimates. S/4HANA includes a Japan localisation covering JCT (dual rate, QIS, T-number), Japanese bank book format (Zengin), payroll via SAP SuccessFactors or HCM Japan, and EBPA archiving.
The leading SAP-certified partners in Japan are NTT Data — SAP Platinum Partner worldwide with over 20,000 SAP professionals in 40 countries (ERPResearch, NTT DATA SAP partner) — and Fujitsu, an SAP partner for over 40 years with more than 3,500 SAP specialists globally (Fujitsu, SAP global partnership). Accenture Japan and NEC complete the ecosystem. For a European group already on SAP, extending to Japan through one of these partners is the most coherent path.
4.2 Oracle Cloud ERP Japan
Oracle NetSuite and Oracle Fusion Cloud ERP include Japan localisation modules. NetSuite Japan covers JCT, QIS, payroll via partner, and Zengin banking formats. Its main advantage for European groups already on NetSuite: a single global tenant with the Japan module activated, with no additional local infrastructure. Data residency is not mandated for foreign subsidiaries in Japan (unlike China), which simplifies SaaS deployment.
4.3 Microsoft Dynamics 365 Japan
Dynamics 365 Finance and Business Central include official Japan localisations: dual-rate JCT, QIS, Japanese invoice format, and J-GAAP accounting statements. One point of caution: native hanko support in D365 approval workflows often requires customisation through Power Automate. For groups already on Microsoft 365 and the Power Platform ecosystem, Business Central Japan is a natural extension.
4.4 NetSuite OneWorld Japan: Option for NetSuite Groups
For a mid-market company already on Oracle NetSuite at headquarters, activating the Japan OneWorld module is the simplest route. The localisation covers QIS, JCT, Zengin formats, and J-GAAP financial statements. With no data residency constraint, SaaS deployment is fast (4 to 9 months depending on payroll module complexity).
5. Key Implementation Watchpoints
5.1 Language and Dual Entry: Kanji Required on Invoices
Japanese invoices must display the names of both parties in Japanese (kanji or kana). Most Western ERPs store third-party records only in Latin characters. Plan for a separate “Japanese name” field in your vendor/customer master data, and configure invoice print templates to use this field for the Japanese market. This point is consistently underestimated during initial ERP configuration.
5.2 Consolidated Reporting for European Headquarters: Year-End Offset
If your headquarters closes on 31 December and your Japanese subsidiary closes on 31 March, you are technically producing two offset sets of accounts. This offset is legally acceptable under IFRS, but it requires producing an interim set of accounts as at 31 December for consolidation purposes. Include this scenario in your ERP requirements specification from day one, and test it explicitly during user acceptance testing.
5.3 Leave and Working Hours Management (Labour Standards Act)
Japanese employment law is strict: a minimum of 10 days of paid leave after six months’ service, and detailed tracking of overtime hours (karoshi — death from overwork — has been legally regulated since 2018). Your ERP HR module must be specifically configured for Japanese labour law, with automatic alerts on overtime thresholds.
6. Recommendations by Subsidiary Profile
| Subsidiary Profile | ERP Recommendation |
|---|---|
| Commercial, <50 staff, purely local operations | Freee or TKC + monthly accounting export to headquarters |
| Manufacturing/distribution, 50–200 staff | PCA or Obic + data hub integration with group ERP |
| Shared services centre or entity >200 users | SAP S/4HANA Japan (NTT Data / Fujitsu) or D365 Finance Japan |
| Group already on NetSuite globally | Activate Japan OneWorld module |
| High-growth subsidiary (scale-up) | Freee in phase 1, migration to SAP Business One Japan in phase 2 |
To go further in managing ERP for your Asian subsidiaries, read our guide to ERP in China: Golden Tax, PIPL and subsidiary integration and our guide to ERP in Australia and New Zealand: STP2, Peppol ANBP, and local vendors. To evaluate your options on a common framework, download our 100-point ERP evaluation grid — 30 criteria across 5 dimensions, designed to compare three vendors side by side.
