A subsidy is not a "receive-then-pay" scheme; it is a "pay-then-get-back" scheme. Even after you receive the grant decision, the cash is not wired in right away. Most subsidies are, in principle, paid "by reimbursement (in arrears)": the business first pays the vendor the costs with its own funds, completes the project, and only after passing the performance report and inspection is the subsidy-rate share paid in. In other words, the first question a buyer should ask is not "can we place the order because a subsidy will come out," but "with which funds do we bridge the several months until payout." This article explains, from a neutral position that helps the buyer's decision-making, cash flow premised on arrears payment and the design of payment terms for system development.
1. Conclusion: a subsidy is "pay, then get back" — advance first, payout later
Lay out the flow of a subsidy's funds in chronological order, and it looks like this.
① 交付申請 … まだお金は動かない
② 交付決定 … 「採択」通知。ここでもまだ入金はない
③ 事業実施 … ★ここでベンダーへ支払う（自己資金で立替）
④ 事業実績報告 … 支払った証憑を提出
⑤ 確定検査・確定 … 補助対象額が確定
⑥ 補助金交付（入金）… ★ここで初めて補助率分が振り込まれる
The important point is that there is a time lag between ③, where cash goes out, and ⑥, where cash comes back. The official flow of the Digitalization & AI Adoption Subsidy 2026 (formerly IT Introduction Subsidy) also runs in the order "grant decision → project-implementation period → performance report → subsidy grant," with the subsidy grant placed last.
Seen in concrete amounts, the gap between the advance and the return becomes even clearer. The Normal Frame of the Digitalization & AI Adoption Subsidy has a subsidy rate of, in principle, up to 1/2 (up to 2/3 if the wage requirements are met), and the amount cap is a maximum of ¥4.5M.
| Item | Amount (e.g., a ¥4.5M pre-tax tool, 1/2 subsidy rate) |
|---|---|
| Total payment to the vendor (tax included) | ¥4.5M + ¥450K consumption tax = ¥4.95M |
| Cash to advance (at the point of ③) | ¥4.95M (prepare the full amount first) |
| Subsidy returned later (at the point of ⑥) | ¥4.5M pre-tax × 1/2 = ¥2.25M |
| Consumption tax (ineligible, self-funded) | ¥450K |
| Final self-funded amount | ¥4.95M − ¥2.25M = ¥2.7M |
If you think "at a 1/2 subsidy rate, half will do," your funding plan collapses. What becomes half is the final burden; the cash you prepare first is the total (tax included). And what comes back is months away.
2. Why it's paid in arrears — the subsidy grant flow and three pitfalls
Subsidies are paid in arrears because, as a scheme funded by tax revenue, the grant is made only after confirming from actual results "whether the expense was really used." From this structure arise three pitfalls that bear directly on cash flow.
2-1. Ordering before the grant decision is "ineligible" (jumping the gun)
In many subsidies, expenses contracted, ordered, or paid before the grant decision become ineligible. "It looks like we'll be adopted, so let's start development early" is a classic accident that can turn entirely self-funded. In the official flow, too, ordering and contracting are placed after the grant decision. It is safe to write the grant-decision date into the development contract as a condition and align the start with the schedule.
2-2. Consumption tax is ineligible
As in the previous section's example, a subsidy generally applies the subsidy rate to the pre-tax expense. You need to include the consumption-tax portion as a self-funded amount that does not come back in your funding plan.
2-3. The time lag until payout
From the grant decision to the payout, the project-implementation period, performance report, and confirmation inspection intervene, so a time lag on the order of months arises. The larger the subsidy, the longer this period tends to be. Always confirm the exact period in each round's solicitation guidelines and project schedule. Organizing how money moves at each stage of the flow gives the following.
| Stage | Cash movement | What the buyer does |
|---|---|---|
| Grant application to grant decision | No movement | Firm up estimate and requirements |
| Project implementation | Goes out (advance) | Pay the vendor / prepare the funds |
| Performance report to confirmation | No movement | Submit evidence (estimate, contract, invoice, transfer record, deliverables) |
| Subsidy grant | Comes back | Confirm the payout |
This structure is the same as the "surface the invisible costs first" thinking covered in cost design for legacy renewal: the key is to map the timing at which cash moves in advance.
3. Four funding options to fill the "gap until payout"
With which funds do you fill the gap from advance to payout? There are four main options.
| Option | Overview | Suited case | Caveat |
|---|---|---|---|
| Own funds | Advance with cash on hand | Ample working capital on hand | Funds are tied up during the advance |
| Bridge financing | Temporarily fill until payout with a loan | The advance exceeds cash on hand | Interest and guarantee fees arise. Early consultation is essential |
| Provisional payment | Receive part of the subsidy ahead of completion | Large-scale, where the grant regulations allow | Allowed or not depending on the scheme. Always confirm in the solicitation guidelines |
| Payment-term design | Lower the advance peak via vendor-side splitting/leveling | Development cost is large | Requires the vendor's agreement |
3-1. Bridge financing
Bridge financing is a loan that temporarily fills the period from subsidy adoption to payout. Financial institutions — starting with the government-affiliated Japan Finance Corporation — handle working capital and equipment funds for SMEs and small businesses. The key is timing: consult your banking partner right after the adoption notice arrives and firm up your funding plan for the project-implementation period, and you can withstand even a delayed payout.
3-2. Provisional payment
Provisional payment is a mechanism to receive part of the subsidy ahead of time, without waiting for project completion. However, this is available only where each subsidy's grant regulations allow it. Because whether it is allowed and its conditions differ by scheme, fiscal year, and frame, do not assume "it should be usable" — always confirm in that round's solicitation guidelines. The safe stance is to build your funding plan on the premise that you cannot use it, and to have it be a relief if you can.
4. "Payment design" for system development — protect cash flow with the estimate and contract
The fourth option, "payment-term design," is an approach that lowers the advance peak through the contract design between buyer and vendor. This is the part where system development leaves the most room for ingenuity.
4-1. Splitting into deposit / interim / on-delivery payments (milestone payments)
Rather than prepaying the development cost in a lump sum, splitting it into a deposit, interim payment, and on-delivery payment keeps the advance of ③ from concentrating at once. By paying per milestone, you can bring the curve of outflows closer to the subsidy's payout timing. In the development work I take on, I also accommodate split deposits and milestone payments, and I sometimes receive consultations on combining them with an arrears-paid subsidy to flatten the peaks of cash flow.
4-2. Leveling cloud usage fees (subscriptions)
In the Normal Frame of the Digitalization & AI Adoption Subsidy, in addition to software purchase costs, cloud usage fees (up to 2 years) can also be eligible. Because cloud usage fees arise monthly, unlike a lump-sum license fee, the advance peak is kept low — that is the advantage. Design on a SaaS premise and you can shrink the initial advance burden itself. That said, whether it is eligible and the cash flow until payout are separate problems; the buyer keeps holding the monthly payments.
4-3. Write the "grant-decision date" into the contract
To avoid the jumping-the-gun described in 2-1, include in the contract a clause to the effect that "the grant decision is a condition precedent," or set the start date to on or after the grant-decision date. This is both a design to protect eligibility and a practical way for both parties to share the scheme schedule.
5. A checklist of "cash-flow landmines" a buyer should clear in advance
Payment design gets stronger the more you build it on the premise that accidents happen. In developing a payment platform I achieved zero double-charges in production, and the crux was to "design evidence and consistency for money-moving flows on the premise that they will fail." Subsidy cash flow follows the same philosophy — clear the following before ordering.
- Have you avoided contracting, ordering, or paying before the grant decision (jumping the gun = ineligibility risk)
- Have you built the self-funded portion of consumption tax and ineligible expenses into the funding plan
- Do you grasp the advance amount (tax-included total) and the returned amount (pre-tax × subsidy rate) separately
- On the premise of the time lag until payout, do you have bridge funds lined up
- Is it designed to retain the evidence needed for the performance report (estimate, contract, invoice, transfer record, deliverables)
- Have you confirmed whether provisional payment is allowed in the solicitation guidelines, rather than assuming
- Do you have working-capital headroom so the project doesn't stall even if the payout is delayed
Pass this check at the design stage, and you avoid the worst case of "adopted, but the money doesn't flow." A subsidy is a scheme that pushes a business forward; it is not a scheme that guarantees cash flow.
6. Conclusion
Subsidies are paid in arrears (reimbursement). That is exactly why the order of decisions puts "how do we bridge the way to payout" ahead of "will a subsidy come out." The advance is the total (tax included), the return is pre-tax × subsidy rate, and there is a time lag of several months in between — map these three points first, and combine bridge financing, provisional payment, and payment-term design to flatten the peaks of cash flow. That is the foundation for keeping a DX investment from stalling.
Also, the author is not an IT-introduction-support vendor and does not act as a subsidy-application agent. This article is a neutral explanation to support the buyer's decision-making. Always confirm the scheme details, the latest subsidy rates, caps, schedules, eligible expenses, and whether provisional payment is allowed in the official solicitation guidelines. On that basis, if you have technical and practical questions — how to run development on an arrears premise, how to design payment terms, or how to compress the advance with SaaS — I can help as a free DX diagnosis.