Approve Subcontracting Before Cost and Quality Drift

A production planner at a precision parts maker in Shizuoka, about 280 staff and supplying automotive OEMs, is staring at a spike in orders it cannot cut in-house. Two of its veteran machinists retired this year and were not replaced. A heat-treatment process that used to run on the night shift now sits idle because nobody is left to run the furnace. The planner emails a long-trusted subcontractor, asks for a quote, and within a day the work is on the way. Nobody in purchasing saw the request. Nobody in quality checked whether the subcontractor still holds the certification the automotive customer demands. Nobody in finance confirmed the unit price against the budget for outsourced processing. The invoice arrives two months later at 3.8 million yen, and the customer rejects the first batch for a surface defect traced back to the subcontractor's tooling.

That is subcontracting without a governed approval. It is not fraud. It is what happens when outsourcing decisions live in email and a planner's personal contact list, with no approval gate between the request and the order. Cost drifts because the unit price is never checked. Quality drifts because the certification and the process audit are never confirmed. Capacity decisions stay untracked because the company has no single list of which processes were outsourced, to whom, and at what cost. Outsourcing quietly becomes an uncontrolled spend channel. This post is about how a core business system closes that gap with a subcontracting approval workflow, where a subcontract order routes through cost and quality sign-off before it is ever placed.

Why Subcontracting Slips Past the Approval Rules

Outsourcing sits in an awkward corner of purchasing. It is not a standard material buy, so it does not always enter the purchase-order flow. It is not a capital expenditure, so it does not always enter the ringi (internal approval proposals) chain. And because it is often urgent, a line down or a deadline missed, the planner is rewarded for speed rather than for governance. The result is that subcontracting grows into a parallel purchasing channel that the authority regulations never touch.

The cost side drifts first. A subcontractor's unit price creeps up over the years and nobody rechecks it against the budget line for outsourced processing. A rush job carries a premium that was never quoted, just accepted. Two subcontractors do overlapping work because nobody realized the other team had already outsourced the same process last month. None of these are large on their own. Aggregated across a year, for a maker spending hundreds of millions of yen on outsourced processing, the drift is material.

The quality side drifts in parallel. A subcontractor that was qualified three years ago may have let a certification lapse, or quietly moved the work to a different site with a different machine. When the customer audit comes, the maker cannot produce a clean record of which subcontractor was approved, for which process, and when that approval was last reviewed. The automotive customer's rejection in the opening scenario is not a freak event. It is the predictable endpoint of ungoverned outsourcing.

The 2025 Communications White Paper found that 48.7 percent of Japanese companies cite the talent shortage as the top barrier to digital transformation. The same shortage is exactly why subcontracting volume is rising. When skilled machinists retire and cannot be replaced, the work does not disappear, it goes to a subcontractor. More outsourcing is the rational response. The problem is doing more outsourcing without more governance. That is the gap a core business system closes.

An Approval Workflow Built for the Subcontract Order

The engine that closes this gap lives inside the workflow layer of a modern ERP. It is the same system that already owns the ledger, the purchase orders, and the inventory. Reading the actual approval code, here is what is genuinely built today versus what is on the roadmap. Honesty about that line matters more than overselling.

One subcontract request, routed to cost and quality

When a planner files a subcontract request, the system does not dump it into a generic inbox. It routes the request along a defined approval path built specifically for outsourcing. The path can require sign-off from purchasing on the cost, and from quality on the certification and process. Both have to clear before the order proceeds.

This is conditional routing, and it is built and live today. A small subcontract order for a non-critical process might need only the requester's own manager. A larger order, or one for a customer-certified process, can be configured to require purchasing and quality in parallel. The planner does not choose the approvers. The request type and the amount do. There is no way for a 3.8 million yen order for a certified process to sail through on a single manager's nod, because the system never sends it there.

This matters because it makes the subcontracting rules self-enforcing. The policy that says quality must sign off on any outsourced process becomes the rule that actually decides where the request goes. The logic survives reorganizations too, because approvals route to the role (quality lead for certified processes) rather than to a named person. When someone changes seats, the flow keeps working.

The quality gate that catches certification drift

The second piece is the one most companies do not have at all. A subcontract request can be configured so that quality must confirm the subcontractor's certification is current and covers the specific process before the order proceeds. This is the difference between catching a lapsed certification at request time and discovering it during a customer rejection a month later.

Because the approval lives inside the same core business system, the history is complete. You can see, for any outsourced job, who confirmed the cost, who confirmed the quality, and when. For companies facing a J-SOX or internal-control review, that record is exactly what the auditor asks for. A spreadsheet of subcontractors in someone's desk drawer is not an audit trail. A timestamped approval chain inside the ERP is.

Where the honesty line sits

Here is the boundary, stated plainly. The subcontracting approval workflow, with conditional routing, parallel cost and quality sign-off, role-based approvers, and the frozen audit snapshot of what was approved, is built and running today. What is on the roadmap is the automatic creation of the subcontract purchase order on approval. Today, an approved subcontract request produces a clean, fully-audited approval record, and the subcontract purchase order itself is created from that record in the normal flow. The removal of that last manual step, automatic subcontract-PO creation the moment approval completes, is what the roadmap closes.

We say this directly because the temptation in this market is to imply the whole loop is automated when it is not. The control you actually need, the approval gate that stops cost and quality drift before the order is placed, is live. The writeback to the purchase order record is coming. Stating that boundary is how trust stays intact.

A Scenario: The Shizuoka Precision Parts Maker

Return to the maker in Shizuoka. Before the approval workflow, the heat-treatment job would have gone out on a single email. The planner files the subcontract request into the system instead. He enters the subcontractor, the process, the volume, and the estimated 3.8 million yen, and he tags the request to the outsourced-processing budget line.

Two things happen before any human approves. First, the request type and the amount trigger the routing rule, so the request lands in the parallel queues of purchasing and quality, not in a single manager's inbox. Second, the cost is visible against the budget line for outsourced processing, and the quality lead sees the specific process and the subcontractor on one screen.

The purchasing lead checks the unit price against the agreed rate card and notices the subcontractor has quietly added a 15 percent premium for the rush. She pushes back, the planner negotiates it down, and the revised amount is approved with the negotiation noted in the record. The quality lead checks the certification, sees it is current, and signs off. Both clear. The subcontract purchase order is then created from the approved record. The customer audit three months later produces a clean trail: who approved, for which process, at what unit price, on what date.

Multiply that across a year. The maker outsources a growing share of its processing because of the retirements it cannot backfill. Without the gate, that volume drifts in cost and quality. With the gate, each request carries its own evidence. The prevented customer rejection alone, one returned batch is often worth several million yen in scrap and rework, pays for the change many times over. The cost drift that never happened because purchasing rechecked the unit price is the larger figure that resists clean accounting.

Why Outsourcing Governance Matters More Now

Three forces make this gate urgent in 2026.

First, the labor shortage is forcing more subcontracting whether companies govern it or not. The 48.7 percent figure from the 2025 Communications White Paper is not abstract for a manufacturer. It is the reason the furnace sits idle on the night shift, and the rational response is to outsource more. The governance gap is that the approval rules written for in-house work were never extended to outsourced work.

Second, the compliance bar keeps rising. The qualified-invoice system demands searchable digital records of every transaction, and J-SOX and internal-control audits expect a clear approval trail and segregation of duties. When a subcontract order can leave on an email with no record, the company cannot defend its own outsourcing. A core business system with the approval gate builds the compliant record from the start.

Third, the customer audits are getting stricter, not lighter. Automotive and industrial OEMs increasingly require their suppliers to prove governance over their own subcontractors. A maker that can produce, in seconds, the approval record for every outsourced job passes that audit. A maker that reaches for a desk drawer does not.

Why This Belongs in One Core Business System

The deeper argument for governing subcontracting inside a core business system, rather than in a standalone procurement tool, is connection. A standalone tool can route an approval, but it cannot, on its own, read the budget line for outsourced processing, hold the inventory record the subcontracted work feeds back into, or post the cost to the right account. That connection is what turns an approval flow into real control.

An ERP that already owns the ledger, the purchase orders, the inventory, and the workflow engine is a better home for this gate than yet another point solution. The subcontract request, the cost check, the quality check, and the downstream purchase order all live in one place. Finance stops being the team that reports cost overruns a month late and becomes the team whose rules prevented the overruns from forming.

The adoption path is pragmatic too. The workflow engine can be deployed standalone first, with no dependency on the rest of the records. A manufacturer can prove the ROI on subcontracting approval alone, then connect it to the full core business system as the team gets fluent.

Common Questions, Answered Honestly

Does approving a subcontract request automatically create the purchase order?

Not yet, and we will be direct. The subcontracting approval workflow, with conditional routing and parallel cost and quality sign-off, is built and running. Automatic creation of the subcontract purchase order on approval is on the roadmap. Today an approved request produces a clean, fully-audited approval record, and the subcontract purchase order is created from that record in the normal flow. The control you need at request time is live. The writeback is coming.

Can the routing match our existing subcontracting rules?

Yes, and it should. The routing is configurable, so the rules you already wrote in your authority regulations map directly into the flow. If your policy says quality must sign off on any certified process and purchasing must sign off above a set amount, the system enforces exactly that. The point is not to invent new policy but to run the one you already have.

What if the subcontractor's certification has lapsed?

That is precisely what the quality gate catches. The quality lead sees the subcontractor and the process on the approval screen and is expected to confirm the certification before signing off. A lapsed certification stops the order at request time rather than surfacing as a customer rejection later. The audit trail records who confirmed and when.

Does this work if our managers travel often?

Yes. The workflow layer supports safe delegation, so a traveling manager can delegate approval to a named substitute, with mandatory re-approval for high-risk items on return. A subcontract request does not stall for a week waiting for someone to fly back, and the audit trail records exactly who stood in for whom. This removes one of the most common reasons staff route around the official process.

Key Takeaway

Ungoverned subcontracting is not malicious. It is what happens when outsourcing decisions live in email and the approval rules were never extended to outsourced work. A core business system with a subcontracting approval workflow moves the cost and quality checks to the moment of request. The request type and amount decide who approves. Quality confirms the certification. Purchasing checks the cost. Orders that used to drift quietly now stop at the gate, and the company finally has one governed channel for the outsourcing the labor shortage is forcing it to do more of.

Get Started With Kikan System

If subcontract orders keep leaving without a cost or quality check, look at Kikan System. The workflow engine routes every subcontract request through parallel cost and quality sign-off before the order proceeds, so the gate runs at request time instead of at a customer rejection. The subcontracting approval workflow is live today, with automatic subcontract-PO creation on the roadmap. You can start on the free plan with up to 2 users, no credit card required. Begin at /#get-started.