Stop Waiting for the President's Stamp: Go Paperless on Ringi

A 30-million-yen investment proposal sits in a tan folder on the fourth floor of a precision parts maker in Shizuoka. The plant manager has reviewed it. The finance lead has checked the numbers. The only thing between this decision and a signed contract is one physical stamp, held by the president, who is on a factory tour in Kyushu until Thursday. So the folder waits. The vendor waits. The machine delivery slot waits. And the company loses a week it can never recover.

This is the everyday reality of paper ringi (internal approval proposals) in Japan. The hanko stamp is not a quaint tradition at the edge of the workflow. It is the workflow, the literal physical object every decision must pass through, and when the person who holds it is out of the office, every decision stops. In an era of remote work, hybrid teams, and global supply chains, a process that cannot move when a single executive travels is quietly bleeding the company money.

The good news is that a modern core business system, the ERP at the center of the company, removes the hanko stamp from ringi without removing the accountability it was meant to provide. In fact, it provides far more accountability, because every approval leaves a tamper-evident record a paper folder never could.

Why the Hanko Stamp Is the Real Blocker

Talk to anyone running a mid-size manufacturer in Japan and the complaint is the same. It is not the software that slows decisions. It is the stamp. According to research compiled by the Startup Notebook (Sogyo Techo), more than 90 percent of Japanese companies still use the hanko stamp in some form, yet only about 20 percent are actively eliminating it. The gap between intention and action is where decisions go to die.

The cost of that gap shows up in three places. First, cycle time. A paper ringi travels desk to desk, and at each desk it waits. An atled survey found that 31.4 percent of companies still ran ringi on paper even at the peak of the pandemic, when offices were closed and stamps were unreachable. Second, loss. Folders get buried. A request urgent on Monday is invisible by Wednesday because it slid behind newer ones. Third, and most damaging, there is no tamper-proof record. A stamped page tells you only that a stamp touched it, not what was on the page when it did, who reviewed it first, or whether the amount was changed after approval.

When companies do break free, the payoff is dramatic. The Asahi Drinks case shortened ringi decision time by 7 days and eliminated roughly 4,000 hours of administrative work. That is an entire department of labor recovered, simply by removing paper from a process that never needed to be on paper.

What Electronic Ringi Actually Replaces

Going paperless on ringi is not scanning a form and emailing it. A real electronic approval module inside a core business system replaces the three things the hanko stamp was doing and does each one better.

A decision that travels instead of waiting

The first thing the stamp does is force physical presence. The president must be in the building. The department head must be at the desk. Electronic ringi removes that constraint. A request, once submitted, lands in the right approval queue automatically, routed to the role or position rather than the person sitting in a chair. The president can approve from a tablet on a Shinkansen. A department head can clear the queue from home in the evening. The decision moves at the speed of reading, not the speed of a paper folder walking across a building.

The routing survives reorganizations. When a department is split or a role moves, the approval still finds the right person because it follows the position, not a name typed into a paper route sheet years ago.

Safe delegation when an executive is away

The second thing the stamp does is concentrate authority in one pair of hands, a single point of failure the moment those hands are unavailable. A well-built approval system solves this with delegation. An executive traveling can delegate their authority to a trusted deputy for a defined window. The request still moves. The decision still gets made.

The honest part is what happens with risky items. For high-value or high-risk requests, the system does not let delegation rubber-stamp everything. It can require mandatory re-approval by the original authority on return, or committee sign-off where a quorum of approvers must agree. So delegation buys speed on the routine and protects integrity on the consequential, a balance a paper folder cannot do at all.

A frozen snapshot of exactly what was approved

The third thing the stamp does is attest. The person pressed the stamp, therefore the person approved. But attest to what? On paper the answer is murky. The amount could have been edited. The attached quotation could have been swapped. The conditions could have been altered after the stamp dried.

A core business system replaces that fragile attestation with a frozen snapshot. When an approval is recorded, the system captures exactly what was on the request at that moment: the amount, terms, attachments, conditions. That snapshot cannot be retroactively edited. For any company under J-SOX or internal-control requirements, this is the audit evidence auditors want. You can prove, months later, that the approved amount was the amount paid, and that the person who approved it was authorized to do so. No paper slip, however carefully filed, gives you that.

The Scenario: A Precision Parts Maker Stuck Waiting

Consider a precision parts manufacturer in Shizuoka, about 280 staff, supplying automotive and industrial-machinery OEMs. Their ringi process is a textbook of paper-bound decision-making. A proposal for a new machining center, worth 30 million yen, begins as a typed form printed at the plant. It travels by internal mail to the head office in Tokyo, where it waits for the plant manager, then the finance director, then the president. If the president is traveling for customer visits and trade shows, the folder sits. A decision that should take two days takes two weeks. The vendor's price holds for only ten days, and the machine's delivery slot is booked by a competitor.

In the paperless flow, the same proposal is filed once, electronically, from the plant. The system routes it automatically to the plant manager, then the finance director, then the president, each step visible on a dashboard showing exactly where the request is and who it is waiting on. The president, on the road, opens it on his tablet, reviews the frozen snapshot of the amount and attached quotation, and approves. If he delegates authority while overseas, the deputy clears routine items and the genuinely large ones either wait for re-approval or go to a committee quorum. The whole journey, from filing to final decision, happens in days instead of weeks, every step recorded with a timestamp and an identity.

The Honest Boundary: What Is Built and What Is Not

Being direct about the boundary matters more than overselling. The electronic approval engine, role-based routing, safe delegation with mandatory re-approval, the committee quorum, and the frozen snapshot are all built and working today. These are the capabilities that kill the hanko stamp and the paper folder.

What is on the roadmap, not built yet, is the automatic writeback of an approved ringi into every downstream record. Today, when a capital expenditure ringi is approved, the approval is recorded and the snapshot is frozen, but the system does not yet auto-create the purchase order or fixed-asset record from that approval. For two cases, expense reimbursement and leave applications, that auto-writeback is already built. For everything else, the connection from approval to downstream ERP record is a planned next step. So when a vendor promises one approval magically updates every ledger, ask which two it actually does. Honesty here is the safeguard.

This is also why the workflow module can be deployed standalone first. A manufacturer does not need to rip out current systems to kill the hanko stamp. They can run electronic ringi on its own, prove the cycle-time savings on their highest-value decisions, and then connect the approval to the rest of the core business system once the team is fluent. That standalone-first path is the fastest route to ROI.

Beyond the Stamp: Why This Matters Now

Removing the hanko stamp from ringi is not only about saving a week per decision, though the week is real. It is about making the company operable in a world that no longer revolves around a single office and desk.

The labor shortage is the quiet pressure behind this. The 2025 White Paper on Information and Communications found that 48.7 percent of companies cite the labor shortage as the top barrier to digitalization, paradoxical until you see that paper processes magnify the shortage. Paper demands physical presence, the one thing a shrinking workforce cannot guarantee. A ringi system that requires physical presence cannot flex when a key person is out sick, on parental leave, or simply no longer with the company. An electronic ringi system, with delegation and role-based routing, absorbs that absence gracefully. The decision still moves.

There is also the generational angle. Younger managers expect to work the way they work in every other part of their lives. Telling a talented new hire that their first task is to walk a paper folder between three floors to collect stamps is a fast way to lose them. A core business system that runs approvals the modern way is a retention tool as much as an efficiency tool.

Finally, there is the governance angle. J-SOX, internal-control reviews, and the tightening of evidence requirements push companies toward records that are tamper-evident and traceable. A frozen snapshot of what was approved, by whom, and when is exactly that record. A stamped paper folder is not. Moving to electronic ringi builds the governance layer the company will need for the next decade.

Common Questions, Answered Honestly

Is removing the hanko stamp even legal for formal approvals?

Yes. Local law does not require a physical stamp for internal company approvals. The hanko is a convention, not a legal mandate, for internal ringi. Electronic approval, with a verifiable identity and a timestamp, carries the same internal weight and is far easier to audit. The legal hanko requirements that do exist apply to specific external filings, not to an internal decision to approve a purchase or a price change.

What happens if the approver genuinely cannot be reached?

This is exactly what delegation is for. The approver delegates authority for a defined window, the deputy clears the routine items, and the high-risk items either wait for re-approval or go to a committee. The decision does not stall for a week because one person is on a plane. This is the single biggest operational win of going paperless.

How is this different from just emailing a PDF?

A PDF in an email is still a paper process, just digitized. It has none of the safeguards. You cannot prove who opened it, freeze the content at the moment of approval, enforce a routing order, or produce an audit trail beyond a sent-mail folder. About 40 percent of workflow adopters, per SIOS research from 2025, are stuck at this stage, the electronified paper ringi, where they scanned the form but kept all the old problems. A real approval module inside a core business system is categorically different: the approval, routing, snapshot, and audit trail are one connected thing.

Does this force us to change our existing approval rules?

No. The system is configured to match your existing authority matrix. If your rules say purchases over 1 million yen need a department head and purchases over 5 million yen need an executive, those thresholds are encoded as routing conditions. The paperless version enforces your rules more consistently than paper, because a paper route sheet relies on someone remembering to walk it to the right desk. The system never forgets.

Key Takeaway

The hanko stamp is not protecting your decisions. It is blocking them. Every day a ringi folder waits for a physical stamp is a day of lost cycle time, lost vendor pricing, and lost opportunity. A core business system removes the stamp, adds a tamper-evident record of exactly what was approved, and lets decisions travel with your people instead of trapping them at a desk. The ERP that runs your company should run your approvals too. The technology to do this is built and working today. The only question is how much longer the company can afford to wait.

Get Started With Kikan System

If your decisions sit in folders waiting for a stamp that is on a train somewhere else, look at Kikan System. The approval workflows module runs electronic ringi with role-based routing, safe delegation, committee quorum, and a frozen snapshot of every approved decision, all out of the box. You can start on the free plan with up to 2 users, no credit card required, and prove the cycle-time win on your highest-value decisions first. Begin at /#get-started, or compare plans at /#pricing.