Decisions Don't Stall When Executives Travel: Safe Proxy Approval

The last week of April is the hardest week of the year to get a signature in Japan. Golden Week sits at the door, and the executives who sign the largest purchase proposals are already on planes or out of the office. A two-million-yen equipment order waits in a paper folder on an empty desk. The procurement lead calls the director's mobile. The director, on a family trip, asks a deputy to approve it over chat. The deputy types "ok." No one writes down who actually decided. Two weeks later, internal control asks for the approval record. There is nothing to show.

This scene repeats during obon in August and the year-end shutdown in December. Absence is the quiet killer of approval speed. When the only person who can sign is away, the chain of approvals freezes, or worse, it moves informally and leaves no trace. The cost is not only slow decisions. It is a genuine internal-control gap. A core business system, or ERP, solves this with a feature most companies assume is too complex to build: safe delegation that records the original approver on the chain of custody, plus mandatory re-approval for the risky items.

Why Absence Breaks Approval Chains

Japanese companies run a lot of their most important decisions through approval workflows (what is often called ringi, or internal approval proposals). The proposal moves up a defined chain, each link adds a stamp or a signature, and the final approver ratifies the decision. The chain works beautifully when everyone is at their desk. It collapses the moment a link is missing.

The breakdown shows up in three ways. First, the freeze. A proposal that needs a director's signature simply stops. Nothing escalates, nothing reroutes. The procurement team waits a week. A supplier waits a week. Second, the ad-hoc workaround. Someone messages a substitute on chat and asks them to say yes. The substitute agrees, but the agreement lives in a chat thread that no one archives and disappears when the history rolls over. Third, the control gap. When an auditor asks who approved a high-value purchase during Golden Week, the honest answer is often "nobody on the record." That answer fails a J-SOX review and a basic segregation-of-duties check.

The data confirms how common this is. Even during the height of remote work, 31.4 percent of companies still ran their approval proposals on paper, according to research from atled. Paper ringi cannot route around an absent approver. When the desk is empty, the paper sits. When the paper sits, the decision sits. For paper-based companies, absence routinely froze entire chains, and it still does today. An ERP breaks this pattern by routing around the empty desk instead of waiting for it.

What Safe Delegation Actually Means

The phrase "proxy approval" sounds dangerous to an internal-control person, and it should, if done naively. A naive proxy lets a substitute silently impersonate the real approver, so the record shows the director approved something when a deputy did. That is exactly the pattern internal control is designed to prevent.

Safe delegation is the opposite. It records both people on the chain of custody. The original approver is named as the intended approver. The delegate is named as the acting approver. The delegation window is recorded, and a reason can be captured. When the delegate approves, the record shows the decision was made by the delegate on behalf of the original approver, on a specific date, within that window. Nothing is impersonated. The chain of custody stays intact, and an auditor can reconstruct exactly who decided what and under what authority.

This matters because internal control in a modern ERP is not really about preventing substitutes from deciding. Substitutes have to decide, or the business stops. Internal control is about making every decision traceable. Safe delegation keeps the business moving and keeps the trail complete at the same time.

The Re-Approval Rule for High-Risk Items

Not every decision should be delegable, and this is where a serious core business system earns its place. Some items are too consequential to let a substitute ratify alone: a capital expenditure above a threshold, a vendor master change, a contract amendment, a write-off above a limit. For these, a single substitute's yes is not enough. The workflow engine handles this with a mandatory re-approval rule.

The rule works like this. For routine approvals, the delegate can approve in full and the decision is final. For high-risk items, flagged by amount threshold or by request type, the delegate can approve to keep the proposal moving, but the decision is not final until the original approver returns and re-approves. The substitute's approval acts as a provisional green light that unblocks the workflow, and the original approver's later ratification closes the loop. If the original approver disagrees, the proposal can be sent back. Nothing is silently overridden.

This is the difference between delegation and abandonment. With re-approval, the executive never loses authority over the big decisions. They simply allow the small ones to flow during their absence. For a J-SOX environment, this is the difference between a delegation policy that passes review and one that gets written up as a finding.

A Scenario: The Precision Parts Maker in Shizuoka

Picture a precision parts manufacturer in Shizuoka, about 280 staff, supplying automotive OEMs across the region. The company runs its largest decisions through approval proposals. A machining center above five million yen needs a director's signature. A vendor change needs legal and IT review in parallel. A price-list revision needs sales and finance sign-off. The approval rules are well defined on paper. The problem is the calendar.

During Golden Week, two of the four directors travel. During obon, a third is out. During the year-end shutdown, the approval desk is effectively closed for ten days. Before the company adopted a core business system, the procurement team had a standing rule: do not submit anything above one million yen after the second week of April, because it will not get signed until mid-May. That rule cost real money. A machine tool supplier offered a year-end discount expiring in late April. The proposal sat on an empty desk. The discount lapsed. The company paid list price in June.

In the new flow, the directors set up delegation before they leave. Each director names a delegate, with a start and end date for the delegation window. Routine approvals during that window flow to the delegate and close out. The chain of custody records the original approver, the delegate, and the delegation window on every decision. For high-risk items above threshold or on a restricted list, the delegate's approval is provisional. The original director re-approves on return, and only then does the proposal close.

The week before Golden Week, procurement submits the machining center proposal. The delegate (a general manager) gives provisional approval so the supplier holds the unit and the discount. The director returns on May 8 and re-approves the same morning. The proposal closes in days instead of weeks. The discount is held. The audit trail is complete. The director never lost final authority, and the business never stopped.

Where the Time Goes, and What You Get Back

The time savings are real, and documented. Asahi Drinks cut its ringi decision time by seven days and reclaimed roughly 4,000 hours by moving its approval proposals off paper. Much of that gain came from exactly this problem: proposals no longer wait for a specific person at a specific desk. When delegation is safe and built in, absence stops being a bottleneck.

The gain shows up in three places for a mid-size manufacturer. First, cycle time. Proposals that used to queue for a week or more during holiday periods now close in days, because the chain never breaks. Second, opportunity capture. Discounts, early-payment terms, and supplier allocations that used to expire during a director's absence now get locked in. Third, the control record. Every delegated decision carries the original approver, the delegate, the window, and (for high-risk items) the re-approval. The audit trail builds itself, with no extra clerical work.

Getting Delegation Right: Three Rules

Rolling out safe delegation is not just flipping a setting. It works when the policy around it is clear. Three rules matter.

Rule one: delegate the routine, re-approve the risky. Decide as a company which request types and which amount thresholds require re-approval on return. Capital expenditure above a limit. Vendor master changes. Contract amendments. Write-offs above a threshold. Everything else can be delegated outright. Write the list down and attach it to the workflow configuration, not to a memo that lives in someone's inbox.

Rule two: bound every delegation window. A delegate is named for a start and end date, not indefinitely. When the window closes, authority reverts automatically. This prevents the most common failure mode, a delegation set up for a one-week trip and forgotten for six months.

Rule three: keep the chain of custody visible. Anyone reviewing a closed proposal should see, in one place, who the intended approver was, who acted as delegate, when the delegation ran, and whether a re-approval followed. This is the record that satisfies an internal-control review and resolves disputes. When two people disagree about who decided what, the chain of custody settles it.

Common Questions, Answered Honestly

Can a delegate approve anything in the original approver's name?

No, and that is the point. Safe delegation never lets a substitute impersonate the original approver. The delegate approves as themselves, acting within a delegation window, and the record names both people. If your goal is to make it look like the director signed something they did not sign, that is exactly the behavior a proper core business system is built to prevent. The chain of custody stays honest.

What happens to proposals the delegate approved while the executive was away?

For routine items, the delegate's approval is final and the proposal closes. For high-risk items flagged by threshold or type, the delegate's approval is provisional. The proposal keeps moving, but it does not close until the original approver returns and re-approves. If the original approver disagrees, the proposal can be returned. The substitute never has the final word on the big decisions.

Does delegation weaken segregation of duties?

It does not, provided the delegate is not the same person who initiated or benefits from the request. The workflow engine routes based on role, position, and department, so the delegate is drawn from the same approval tier as the original approver. The segregation that existed before the trip still exists during it. What changes is only who sits in the chair, not where the chair sits in the chain.

What about executives who simply refuse to delegate?

This is a policy problem, not a technology problem. The system makes safe delegation easy, but it cannot force a culture of using it. The companies that get the most value treat pre-trip delegation setup as a standard step, like setting an out-of-office reply. Directors who delegate routinely see their proposals close on time. Directors who refuse see them queue for a week every holiday.

Where This Fits in the Bigger Picture

Safe delegation is one capability inside a broader workflow engine in the ERP. The same engine routes approvals to the role, position, or department so they survive reorganizations. It supports committee sign-off with a quorum for the largest spends. It enforces business-day deadlines so a proposal cannot sit forever. It lets stakeholders follow a request as watchers without being approvers. And it freezes a snapshot of exactly what was approved, which is the audit trail that holds up under J-SOX review. Delegation is the part that keeps all of that working when someone is on a plane.

If you want the full picture of how a mid-size manufacturer runs its entire approval surface, the pillar post walks through the complete catalog and the ROI behind each workflow.

For the foundation underneath delegation, two related posts are worth reading. The first covers how approval workflows are configured without code, where you set up the roles, thresholds, and re-approval rules that delegation relies on. The second covers the audit angle, which is why the chain of custody matters in the first place.

Key Takeaway

Absence is not an excuse to stop deciding, and it is not an excuse to decide off the record. Safe delegation lets a named substitute keep the routine work moving during Golden Week, obon, and the year-end shutdown, while mandatory re-approval keeps the original approver in control of the big decisions. The chain of custody records both people, every time. The business keeps moving, and the audit trail stays complete.

Get Started With Kikan System

If your approvals freeze every time a director travels, look at Kikan System. The workflow engine supports safe delegation with bounded windows, mandatory re-approval for high-risk items, and a chain of custody recording both the original approver and the delegate on every decision. You can start on the free plan with up to 2 users, no credit card required. Begin at → Start free.