Registering a Telecommunications Business in Japan: When Your SaaS Is Legally a Carrier

Japan’s Telecommunications Business Act reaches further than most foreign software companies expect, and the companies it catches are rarely the ones that think of themselves as telecom. Messaging apps, voice-over-IP, some cloud and platform services: if a product carries or intermediates other people’s communications as a business, it can be a telecommunications carrier under Japanese law, with the registration or notification duty that follows.

The good news is that for most of these companies the administrative step is light, a one-day electronic notification rather than a heavy licence. The trap is not the procedure; it is failing to realise the procedure applies to you at all, and discovering it during a compliance review or a partner’s due diligence rather than at market entry.

What follows is how the Act classifies businesses, the registration-versus-notification split, what the 2023 amendment added, and how to tell whether you are in scope. The governing law is the Telecommunications Business Act (電気通信事業法), owned by the Ministry of Internal Affairs and Communications (総務省, MIC).

The classification trap: are you even a telecommunications carrier?

The first question is not which procedure you file; it is whether the Act applies to you, and that turns on a definition broader than most companies assume.

A telecommunications carrier under the Act is, in substance, anyone who provides a telecommunications service to others as a business, who carries or intermediates other people’s communications. That framing catches a range of businesses that do not describe themselves as telecom: messaging and chat services, voice-over-IP, some communication-carrying cloud services, ISPs and MVNOs.

What generally falls outside is a service that does not carry others’ communications, or that a company operates purely for its own use. Pure software, where the product does not transmit other people’s communications, usually is not caught. But the boundary sits in a place that surprises people, and because being in scope brings real duties, the classification is worth settling deliberately at the planning stage rather than assumed away because a product feels like software rather than telecom.

Registration versus notification

For a business that is a telecommunications carrier, the Act splits into two tiers, and the split is about the scale and nature of the facilities involved, not the size of the company.

Route	Legal basis	Who it applies to	Period	Fee	Annual volume
Registration	Art. 9	facility-based carriers above a scale threshold, or spanning prefectures	15 days	none	very few
Notification	Art. 16(1)	all other telecommunications carriers	1 day	none	~1,643
Intermediary-business notification	Art. 73-2 (2023)	businesses that intermediate others’ services	up to 3 weeks	none	~16,339

Registration under Article 9 is for facility-based carriers whose own transmission facilities exceed a scale set by ordinance or span multiple prefectures, the large infrastructure operators. It runs on a 15-day period, and the volume is tiny, a handful a year, because few entrants build at that scale.

Notification under Article 16 covers every other telecommunications carrier. It runs on a one-day period, carries no fee and is filed electronically. This is the route almost every foreign software and service company takes: light, fast, and easy to overlook precisely because it is so light.

The practical point is that the heavy-sounding word “registration” applies to very few companies. Most entrants who are in scope simply notify, and the real work is the classification that determines whether they must, not the filing itself.

What the 2023 amendment added

The 2023 reform of the Act was aimed at large platforms and intermediaries, and it added two things a foreign web or platform business should check against its own service.

The intermediary-business notification under Article 73-2 requires businesses that intermediate, broker or act as agent for others’ telecommunications services to notify. This is a newer and higher-volume category, about 16,000 filings a year, running on up to a three-week period, and it reaches resellers and intermediaries that the older registration-and-notification framework did not squarely address.

The external-transmission rules require certain telecommunications services to disclose when they send information from a user’s device to outside parties. This is Japan’s counterpart to the international debate over cookies and third-party tracking, and it is a live compliance item for web services, platforms and apps that reach Japanese users, independent of whether the company also has to notify as a carrier.

Neither of these is exotic, and both are the kind of obligation that a foreign digital service can be subject to without ever having thought of itself as operating in Japanese telecom law.

The gap between published and actual

The telecom notifications are among the faster procedures a market entrant meets, but the standard qualification on published periods still applies.

A standard processing period (標準処理期間) is set under Article 6 of the Administrative Procedure Act. That article obliges an agency to publish the period once it has set one, but setting it is only a best-efforts duty, and there is no statutory obligation to actually meet it, and the clock generally excludes time while a filing sits with the applicant for correction. Where completion data is systematically published the gap can run large: every pesticide re-evaluation concluded to date has taken 3.5 to 4.0 years against a published period of one year, from that ministry’s own records, set out in our guide to registering a pesticide in Japan. A one-day telecom notification will not show a multiple like that, and in this area the published periods are broadly realistic. The lesson that does carry across is to confirm your classification early, because the schedule risk here is not the filing time, it is discovering the obligation late.

Where this becomes a public affairs question

The registration and notification mechanics are compliance work, and telecom regulatory counsel handle them well. The public affairs questions arrive when the rules themselves are moving, and in Japanese telecom and digital policy they move often.

Platform regulation, the scope of the external-transmission rules, data and content governance, and the treatment of new service categories are all under active development, through MIC councils and the wider digital-policy machinery. A company introducing a service model that Japan has not yet classified, or that sits awkwardly across the line between software and telecom, may find that the binding question is not how it notifies but how its category is defined, and that definition is set through policy before it hardens into a rule. As everywhere in this regime, shaping a classification while it is open is far easier than contesting it once settled.

If that is your situation, get in touch.

How to plan it

• Settle your classification first. Whether the Act applies to you is the decision that matters; the filing is secondary. Confirm it deliberately rather than assuming a software product is out of scope.
• Expect notification, not registration. Almost all foreign software and service entrants notify under Article 16; registration is for large facility-based carriers.
• Check the 2023 additions against your service. The intermediary-business notification and the external-transmission rules catch platforms and web services that predate them in their own thinking.
• Map the overlap with the Radio Act. If your service uses its own wireless equipment, you may face both frameworks; see our guide to radio type approval.
• Engage on classification if your model is genuinely new. How a novel service category is defined is a policy question, and the time to shape it is before the rule sets.

Why this matters for public affairs in Japan

Telecommunications registration looks like a compliance formality, and for a clearly-in-scope carrier it largely is. But the Act sits on top of a fast-moving digital-policy agenda, platform rules, data governance, external-transmission disclosure, the classification of new service types, and the definitions that decide who is caught are being written and rewritten. For a company whose Japanese business depends on how its service is classified, the notification is downstream of a policy question that can be reopened. Knowing which is which, and engaging while the definition is still open, is what separates a one-day formality from a market-access risk.

Gemini Group advises foreign and Japanese technology companies on market entry, digital and telecom policy, and public affairs strategy in Japan, including where a classification question is really a policy question. Contact us to discuss your Japan strategy.

Further reading: our guide to radio type approval covers the adjacent spectrum regime, the market-entry regulatory checklist maps which institutions apply to your sector, and our Digital Agency overview covers the wider digital-governance machinery.