No Single Person Approves a 10 Million Yen Spend: Committee Ringi

A 30-million-yen machining center lands on the desk of one plant manager at a precision parts maker in Shizuoka, about 280 staff, supplying automotive OEMs. He stamps the requisition alone. Three weeks later the invoice arrives, the asset is booked, and the machine is on the floor. Then, at a board meeting, two directors ask a quiet question. Why did none of us see this before it was committed? The answer is uncomfortable. The approval rules said any single executive could clear a purchase of that size, trusting one person to carry a decision that should have belonged to the board.

This is the concentration-of-authority problem, and it is one of the most expensive governance gaps a manufacturer can carry. A single signature on a large capital expenditure or major contract concentrates risk in one person, fails the segregation-of-duties test J-SOX internal controls expect, and leaves no record of why the decision was sound. The fix is older than any ERP. It is committee ringi (internal approval proposals), where a quorum of approvers must sign off before the spend moves. The hard part has never been the principle. The hard part has been running it on paper.

Why One-Signature Large Spend Fails the Controls Test

A large capital purchase is not a routine approval. It commits cash, changes the balance sheet, and often locks the company into a vendor relationship for years. When that decision rests on a single person, three things break at once.

First, segregation of duties collapses. J-SOX internal controls, and any credible internal-control framework, expect the person who requests, the person who approves, and the person who records to be distinct. For material spend they expect the approval itself to be shared, so no single individual can move a large sum unchallenged. One signature fails that test by design.

Second, the evidence dissolves. A stamped requisition slip proves a stamp was applied. It does not prove the approver read the quote, checked the budget, compared alternatives, or understood the total cost of ownership. Six months on, when an auditor asks why this machine and not a cheaper one, the paper cannot answer. The rationale lives in the head of the one person who stamped, if it lives anywhere.

Third, paper committee ringi is slow and hard to tally. When the rule is that three of five directors must agree, paper turns that into a scavenger hunt. Forms travel between offices, signatures collect on different days, one director is on a train, another is at a customer site, and nobody knows whether the quorum has been reached until someone counts the stamps. Decisions that should take two days take two weeks, or they degrade back to a single signature because that is the only way to get them to move at all.

This last point is the cruelest one. The committee rule exists on paper. In practice, the friction of running it pushes people back toward the very concentration of authority the rule was written to stop.

What Committee Ringi Actually Needs to Work

A committee approval is more than collecting several signatures. Done right, it has three parts that must hold together.

The first is a quorum threshold. The rule is not that everyone must agree, which would let one absent director block everything. The rule is that a defined number out of a defined group must agree, say three of five executives, or two of three department heads. The request passes when the threshold is met, and fails or stalls when it is not. This is the difference between consensus theater and a real governance gate.

The second is parallel review. A quorum only works if the approvers can review at the same time rather than in a serial chain. If the five directors must sign one after another, the form still travels, and the slowest person sets the pace. Parallel review means each approver sees the full request, the quotes, and the justification at once, and signs off independently. The threshold is tallied as the approvals come in, not at the end of a paper trail.

The third, and the one most teams forget, is a frozen snapshot of what was actually approved. When three directors sign off on a 30-million-yen machine, what exactly did they approve? The vendor, the model, the price, the delivery date, the payment terms. If any of those can change after the signatures, the approval is meaningless. A credible committee ringi freezes the exact content of the request at the moment of approval, so the audit trail shows not only who agreed but what they agreed to. That snapshot is the evidence J-SOX reviewers actually want to see.

How a Core Business System Runs Committee Ringi

This is where a core business system earns its keep on large spend. The workflow engine handles exactly this shape of approval, with no developer needed to configure it.

For a capital expenditure above the threshold you set, the routing rule sends the request to a defined group of approvers. The system is set to require a quorum, meaning N approvers out of M must sign off to pass. You decide the numbers. Three of five executives for spend above 10 million yen. Two of three for a smaller tier. The threshold and the group travel with the rule, not with whoever is in the office.

The review runs in parallel. Every approver in the group sees the request at the same time, with the quotes attached, the budget context visible, and the justification in one place. Each signs off independently. As the approvals arrive, the system tallies them against the threshold. The moment the quorum is met, the request passes. When it is clear the quorum cannot be met, it stalls for review. Nobody has to chase anyone, and nobody has to count stamps.

Crucially, the system freezes a snapshot of what was approved. The vendor, the amount, the terms, the attachments at the moment of approval are captured as the record of the decision. If anything changes afterward, there is a new request and a new approval, not a quiet edit to a form someone signed. That frozen snapshot is the audit trail, and for a company preparing for a J-SOX review it is the difference between asserting that a decision was governed and proving it.

Because the approval lives in the same core business system as the rest of the ERP, the audit trail is complete from the start. You can see who proposed the spend, who reviewed it, who approved it, when each step happened, and what content was on the table. A paper requisition slip cannot defend any of that. A forwarded email chain cannot either. The system writes the evidence as the work happens.

A Scenario: The Precision Parts Maker in Shizuoka

Return to the precision parts maker, 280 staff, a head office in Tokyo and a plant in Shizuoka, supplying automotive and industrial-machinery OEMs. Today, a new machining center request starts on a paper ringi form. The plant manager proposes it. Because the amount, around 30 million yen, crosses the board-level threshold, the rule says three of five directors must agree. In practice, the form sits in a tray until someone walks it to the executive floor, one director stamps it, it goes into a briefcase for a week while another travels, and by the time the third signature arrives nobody remembers which quote was the basis. When the auditors ask, months later, the team spends days reconstructing who approved what and on what terms.

Now imagine the same request in the core business system. The plant manager files it from Shizuoka, attaching the vendor quotes, the expected payback, and the budget line it will draw from. The workflow engine sees the amount, recognizes it crosses the board-level threshold, and routes it in parallel to the five directors. Each director reviews the identical request from wherever they are, on the evening of the same day. Three sign off. The system tallies the quorum, the request passes, and a frozen snapshot of the exact content, vendor, model, price, terms, is locked as the record. Total elapsed time drops from roughly two weeks to a day or two.

The governance gain is the larger half of the story. No single person moved the spend. The segregation of duties is visible by design. And when the auditors arrive, the approval exports in minutes, with every name, timestamp, and the exact approved content attached. The dread of review season shrinks, because the evidence was captured when the decision was made.

Why This Matters for Japanese Manufacturers Now

Three forces make this urgent in 2025 and 2026.

The compliance bar is rising. J-SOX internal controls and broader internal-control reviews expect segregation of duties and documented, shared approval for material spend. A single-signature rule on a 30-million-yen purchase is exactly the gap a reviewer will flag. The qualified-invoice system and the broader push for searchable, tamper-resistant digital records raise the cost of paper evidence further.

The talent shortage compounds the risk. According to the 2025 Communications White Paper, 48.7 percent of Japanese companies cite the talent shortage as the top barrier to digital transformation. When experienced executives retire, the tacit knowledge of why a large purchase was sound retires with them. A frozen snapshot with names and rationale preserves that knowledge in a form a successor or an auditor can read.

Finally, there is the speed argument that often gets overlooked. Companies fear that committee ringi will slow decisions. The opposite is true when it is run in a system. Parallel review with a quorum threshold is faster than a serial paper chain, because it removes the bottleneck of one traveling form. Industry research on the Asahi Drinks case shows ringi decision time cut by 7 days and roughly 4,000 hours of administrative work eliminated. The committee does not slow governance. Paper slows governance.

Common Questions, Answered Honestly

Does committee ringi mean every large decision takes longer?

No. The delay in large-spend approval almost never comes from the number of approvers. It comes from the serial paper chain, where a form waits on one desk, then travels, then waits on the next. Parallel review removes that chain. Each approver acts at the same time, and the quorum is tallied live. In practice, committee ringi in a system is faster than a single-signature paper flow, because nothing is waiting to be walked between offices.

What happens if the request changes after the first approvals?

The frozen snapshot handles this. Once the quorum is met, the approved content, vendor, amount, terms, attachments, is locked as the record. If the vendor raises the price or the terms shift, that is a new request, not an edit to one already signed. The original approval and the change are both in the audit trail. Nothing is silently overwritten.

Can we set different quorum rules for different spend tiers?

Yes, and this is where the threshold routing earns its keep. You might require two of three department heads for spend between 5 and 10 million yen, and three of five executives above 10 million yen. The threshold and the approver group live on the rule, so the right governance gate applies automatically based on the amount. One rule set, applied consistently, every time.

Is this a substitute for our board's own governance process?

No. The system provides the evidence and enforces the approval gate you configure. Your board, your audit firm, and your internal-control team still own the governance framework and the conclusions. The ERP supports the process by capturing who agreed to what and when. It does not certify the judgment behind the decision.

Key Takeaway

A 10 million yen purchase resting on one signature is a governance accident waiting for an auditor to find it. Committee ringi, with a quorum threshold, parallel review, and a frozen snapshot of what was approved, turns large spend from a concentration-of-authority risk into a controlled, fast, auditable decision. The principle is old. Running it without paper is what makes it finally work.

Get Started With Kikan System

If your large capital expenditure still rests on a single stamp, look at Kikan System. The approval workflows module runs committee ringi with configurable quorum thresholds, parallel review, and a frozen snapshot of exactly what was approved, inside one core business system built for the Japan market. You can start on the free plan with up to 2 users, no credit card required. Begin at → Start free.