The IT Introduction Subsidy 2026, explained for buyers — categories, subsidy rates, eligibility, and the 'not eligible' cases

Let me start with the conclusion. In 2026, what everyone calls the "IT Introduction Subsidy" was renamed the "Digitalization & AI Introduction Subsidy 2026," but the program's skeleton has not changed. It rests on the premise that you adopt an IT tool pre-registered with the secretariat, by way of a registered "IT introduction support vendor." That is why full-scratch development, built from the ground up to fit your operations exactly, is in principle not eligible. It is a powerful program for greatly compressing the upfront cost of adopting an off-the-shelf SaaS or package, but a buyer who wants custom development is better off choosing a different path than forcing a fit — the result will be cheaper, faster, and better. This article is not a set of application techniques; it is a map that lets a buyer decide, in the shortest time, whether their investment even rides on this program at all.

1. First, the premise: the name changed to the "Digitalization & AI Introduction Subsidy 2026"

From FY2026, the program's brand name changed to the "Digitalization & AI Introduction Subsidy 2026" (formal name: the SME Digitalization & AI Introduction Support Project Subsidy). The top of the official site itself clearly states "formerly: IT Introduction Subsidy."

In search engines and internal conversations it will keep being called the "IT Introduction Subsidy," but when you, as a buyer, check the primary source, always look at the official site under the new name (it-shien.smrj.go.jp). Taking the "2024 figures" from an old blog post or an agency's sales deck at face value is the single most common accident with programs like this. Subsidy rates, caps, category names, and schedules change every fiscal year.

2. The program's structure: three players and the "registered-tool premise"

The key to understanding this subsidy, before any figures, is its structure: who buys and sells what. There are three players.

According to the official program overview, the eligible IT tools are limited to "those that have undergone the secretariat's prior review and are published (registered) on the subsidy website," and the applicant is required to "apply in partnership with a registered IT introduction support vendor" (except for the multi-party collaboration category).

In other words, the flow of money looks like this.

[発注者]
   │ ①登録された支援事業者とパートナーを組む
   ▼
[IT導入支援事業者] ──② 登録済みITツールを提案・共同で交付申請
   │
   ▼
[事務局] ──③ 審査 → 交付決定
   │
   ▼
[発注者] ──④ 交付決定「後」に導入・支払い → ⑤実績報告 → ⑥補助金入金

There is one most-important point for the buyer to grasp here: "eligibility is limited to off-the-shelf tools registered in advance." This single point is the whole reason "full-scratch is not eligible," which we cover below.

3. The 2026 application categories, the standard category's subsidy rate, and the schedule

3.1 The five application categories

The application categories you can confirm on the 2026 official site are these five.

1. Standard category
2. Invoice category (invoice-support type)
3. Invoice category (electronic-transaction type)
4. Security-measures promotion category
5. Multi-party collaboration digitalization & AI introduction category

If you want to digitize accounting, ordering, and payments, the Invoice category; if it's a security investment, the Security-measures promotion category — the categories split by "the nature of the tool you want to adopt." First, work out which category your purpose falls under.

3.2 The standard category's subsidy rate and caps

The standard category, which buyers use most, has the following terms according to the official page (a summary of the 2026 wording).

• Eligible costs: software purchase costs, cloud usage fees (up to two years), options (feature extensions, data integration, security), and services (adoption consulting, configuration, training, and maintenance support).
• Higher subsidy rate under the wage-increase requirement: the page states that up to 2/3 applies if you demonstrate conditions such as employing, for three or more months between October 2024 (Reiwa 6) and September 2025 (Reiwa 7), workers below the FY2025 (Reiwa 7)-revised regional minimum wage who make up 30% or more of all employees.

The figures are revised each fiscal year. Before applying, always re-confirm the subsidy rate, caps, and requirements in the latest call-for-applications guidelines (standard category). The tables in this article are only an entry point for your judgment.

3.3 The schedule (the axis buyers must work backward from)

The official schedule publishes the following for 2026 (common to the standard, invoice, and security categories).

The dates for the 2nd deadline onward are unpublished as of this writing. The one thing a buyer must never get wrong here is: "do not order, contract, or pay before the grant-decision date." Build your schedule — adoption, acceptance, performance reporting — by working backward from the grant decision. "I wanted to start early, so I signed the contract first" is a textbook accident that voids eligibility.

4. The heart of it: is your order "eligible" or "not eligible"?

This is the most important chapter for buyers. From the program's structure, let's clearly separate the cases that tend to be eligible from those that are, in principle, not.

4.1 Cases that tend to be eligible (= where this program is strong)

• You want to adopt an off-the-shelf SaaS / package for accounting, ordering, payments, inventory, and the like
• You want to bring in registered business software that supports the invoice system and electronic transactions
• You want to adopt a registered service for security measures
• You want support that also covers the accompanying cloud usage fees (up to two years) and configuration/training costs

In short, it's the type of investment where you "bring a product that already exists in the world into your company for the first time." Here the 1/2–2/3 subsidy rate bites, and the upfront-cost hurdle actually drops.

4.2 Cases that, in principle, tend to be "not eligible"

4.3 Why "full-scratch development" is, in principle, not eligible

The reason is simple and lies in the program's very design. This subsidy is a mechanism that makes eligible only the tools the secretariat has reviewed in advance and registered/published like a model number. A registered tool is, so to speak, a standardized product, premised on "many SMEs being able to adopt the same product."

By contrast, full-scratch development, designed from scratch to fit your distribution flow, forms, and approval workflow, is by definition "exclusive to one company" and can never be a pre-registered off-the-shelf tool. So no matter how excellent your bespoke system is, it in principle does not ride on this program's standard category. This is not a flaw in the program — it is simply that the program is designed for a different purpose.

If you consult a vendor on the premise that "a subsidy should be available, so let's do custom development," the conversation breaks down right here. First, separate "will an off-the-shelf tool suffice, or do you need custom development?" This way of separating the two is laid out in detail in how to choose among SaaS adoption, packaged purchase, full-scratch, and in-house vs. outsourcing.

5. If you need full-scratch: three alternative routes

"Our operations are special; an off-the-shelf SaaS won't run them. We absolutely need custom development" — in fact, this is normal in legacy-industry DX. In that case there are three realistic options.

5.1 Route A: Consider a different subsidy

For custom-development- or capital-investment-leaning investment, other programs become candidates, such as the Monozukuri subsidy (the Monozukuri, Commerce, and Service Productivity Improvement Promotion Project) or, for small businesses, the Sustainability subsidy. However, their purpose, eligible costs, caps, and schedules are entirely different from the IT Introduction Subsidy, and whether custom development is eligible also varies by round and by type. Always confirm the eligible costs in each program's latest call-for-applications guidelines. In this article, prioritizing accuracy, I deliberately refrain from asserting the specific amounts or subsidy rates of other programs.

5.2 Route B: Self-funding + phased ordering (MVP → expansion)

Rather than binding your business to the subsidy's schedule of deadlines, grant decisions, and performance reports, it is often more rational for custom development to build small with your own funds, validate, and expand the investment step by step as you observe the effect. Don't order all the features up front; ship an MVP of the core operations first, and expand only after you've confirmed the field can use it. This "phased adoption" mindset is explained with real examples in a technology-selection framework for legacy-industry DX.

5.3 Route C: Reconsider whether a registered SaaS could substitute in the first place

Before you commit to custom development, doubt once more whether "an off-the-shelf tool truly won't suffice." Trying to satisfy every request from the field tends to lead to custom development, but it is not rare that, if you standardize the business side a little, it fits onto a registered SaaS. If it does, you can use the subsidy, and the product side even handles maintenance. Putting custom development last as a last resort pays off in both cost and maintenance.

5.4 Comparing the three routes

6. Five pitfalls buyers easily step into

1. Working backward from "subsidy first": if you pick a tool by working backward from the amount available, you'll grab something that doesn't fit your operations. Think in the order purpose → tool → (the subsidy that happens to be usable).
2. The support vendor's interests: a registered support vendor is in the position of recommending the tools it handles. That's not a bad thing, but buyers should hold the perspective of comparing multiple vendors and tools.
3. Jumping the gun before the grant decision: as noted above, this is in principle ineligible. However urgent, wait for the decision.
4. Underrating the post-award obligations: after the grant, you're required to file performance and outcome reports and to operate for a set period, and there's a clawback risk if you don't meet the requirements. It's not "receive it and you're done."
5. The cloud-fee period: the standard category covers cloud usage fees for up to two years as a rule of thumb. Estimate your running costs on the premise that year three onward is out of pocket.

7. A buyer's decision checklist

□ 導入したいのは「既製の登録ツール」か、それとも「自社専用の独自開発」か
□ 独自開発なら → この制度は原則対象外。ルートA/B/Cで再設計したか
□ 既製ツールなら → どの枠（通常/インボイス/セキュリティ/複数者連携）に当たるか
□ 補助率・上限・対象経費を「最新の公募要領」で自分で確認したか
□ 交付決定日を起点に、発注・導入・実績報告を逆算できているか
□ 補助金ありきでなく、業務目的から選んでいるか
□ 交付後の報告義務・返還リスク・3年目以降のランニングを織り込んだか

Just running this check in the first 30 minutes largely prevents textbook accidents like "I want custom development but the subsidy talk doesn't line up" or "I signed the contract first and became ineligible."

The author is not a registered IT introduction support vendor and does not file subsidy applications on your behalf. This article is a neutral explanation meant to support buyers' decision-making. Always confirm the program's details and the latest subsidy rates, caps, schedules, and eligible costs in the official call-for-applications guidelines.

On that basis, I can advise on the technology-selection and phased-ordering design behind "will an off-the-shelf tool suffice, or do you need custom development?" and "if custom, what should you build and in what order?" — grounded in hands-on experience with generative-AI-accelerated development. Not as subsidy-application support, but as a free DX assessment / technical consultation, I'll join you at the entrance to your investment decision.