To digitize a paper workflow in a Japanese business, start with one complete process rather than a company-wide program, and write down what the paper is actually doing before replacing it. Paper forms, hanko and faxes often carry information a new application does not capture: who checks an exception, why a signature is needed, which supplier can only use the old channel, which record the tax accountant relies on. Map that, decide what must be kept, then choose the simplest tool that does the job and measure whether the work got faster.

Japan is known for bullet trains and precision manufacturing, yet a lot of everyday business still runs on paper, seals and fax. That contrast is often described as a paradox. From inside a small company it looks less mysterious: the analog process works, the people running it know its exceptions, and replacing it carries risk nobody has been asked to own.

Why do Japanese businesses still run on paper?

The technology is not the obstacle. Cloud accounting, e-contracts, internet fax and workflow tools are widely available in Japanese, from Japanese vendors.

The reasons are practical. A hanko on a form shows who approved it and that they took responsibility, and that meaning matters inside the company and to trading partners. Some customers and suppliers still send orders by fax. Older staff and owners are comfortable with processes they have run for decades. Tax and record-keeping rules have changed several times in a few years, so some owners keep paper because they are unsure what the digital version must look like. And in many companies nobody has the time or authority to redesign a process that still, more or less, works.

Government pressure has shifted things. Many administrative procedures dropped hanko requirements from 2020 onwards, the qualified invoice system (インボイス制度) began in October 2023, and since January 2024 invoices and receipts received as data must be stored as data under the electronic bookkeeping law. Those changes gave many businesses a reason to act, but also a way to digitize badly: scanning paper into folders without changing how the work flows.

What does the paper process know that the software does not?

Before replacing a paper process, look closely at it. The form is usually the least interesting part. What matters is the behavior around it.

Exceptions. The order form has a handwritten note in the margin for one customer’s delivery rule. Nobody wrote that rule anywhere else.
Approvals. A manager’s seal is required above a certain amount. Is that a company rule, a bank requirement or habit?
Evidence. The stamped original is filed because the tax accountant (税理士) or an auditor asks for it. What do they actually need?
Relationships. A long-standing supplier only uses fax. Moving them abruptly could cost goodwill that matters more than the saved time.
Recovery. When a sheet goes missing, someone knows who to call. That knowledge is part of the process.

A new application that ignores these details will be worked around. Staff will keep the old paper as a backup, write the exceptions in a private notebook, or approve things by phone, and the business ends up running two processes.

How do you digitize one workflow properly?

Choose one process with a clear start and end

Customer onboarding, purchase approval, order intake, expense claims and monthly reporting are good candidates. A vague goal to “go paperless” is not. Pick the process that causes the most retyping, delay or errors today.

Map it as it really runs

Follow real cases, not the manual. Record who supplies the information, who checks and approves it, which record is treated as the final truth, where the same data is typed again, and what happens when something is missing or wrong. Include the fax, LINE messages and phone calls.

Separate legal requirements from habit

For every seal, signature and stored original, ask whether it is required by law, by a contract or customer, or by company habit. Your tax accountant can confirm record-keeping needs, and the Japan SaaS compliance guide explains how to scope record obligations across your systems. Keep what is required. Question the rest.

Choose the simplest tool that fits

Many workflows need nothing exotic. Common choices in Japanese SMEs include:

Approvals: ジョブカンワークフロー, kintone, Garoon, or forms with approval steps in Google Workspace or Microsoft 365.
Invoices and receipts: freee or Money Forward, which also store records to the electronic bookkeeping rules. See freee vs Money Forward.
Contracts: CloudSign or GMO Sign in place of printed, stamped copies.
Incoming fax: internet fax or a multifunction printer that forwards faxes as PDF, as described in the guide to moving off fax.

Video: 申告・納税と一緒に日々の業務もデジタル化しませんか？（令和８年１月修正） from the National Tax Agency (国税庁動画チャンネル), in Japanese.

Build an exception path

Some seals, originals and paper-only partners cannot change immediately. Record those constraints rather than pretending they are gone. A temporary manual step is legitimate when it has an owner, a reason and a date to review it.

How do you know it worked?

Do not count paper forms eliminated. Measure elapsed time from start to finish, how often the same data is entered twice, how much correction work there is, and how many cases still need one experienced person’s private knowledge. A new interface that leaves those numbers unchanged is decoration. A modest workflow that reduces them is real progress.

After the first month, review actual cases with the staff who handled them. Look for work that escaped into email, private spreadsheets or verbal approvals. Those escapes show where the new process is unclear or where a real requirement was missed. Fix the workflow before adding automation. A stable manual checkpoint is better than an automated mistake that spreads through every connected system.

Questions for the first workflow review

Which record is treated as the final truth today?
Where is the same information typed again?
Which approval is legally or commercially necessary, and which is habit?
What evidence would show that the new process is faster or safer?
How can staff keep working if the chosen service is unavailable?

Is Japan’s slow pace just resistance to change?

Not entirely. Many Japanese companies are deliberate because a failed change is costly to relationships and reputation. That caution protects some things worth protecting. The weakness is that caution can hide real fragility: a business with a modern public face running on processes only a few people understand.

The companies that make progress rarely do it with a dramatic transformation program. They digitize one complete process so it works better for the people operating it, then repeat that on the next one. Digital transformation becomes credible when a process actually works better, not when a dashboard exists.

If you want help choosing which process to start with and mapping what it really depends on, a Diagnostics review covers that. For a wider view of why these projects go wrong, see why DX projects in Japan fail before the software arrives.

Further reading: how to move a Japanese business off fax · digital literacy is part of running the business · training staff to replace legacy systems