Budget Setting and Changes: Approve So Spending Stays Governed

A finance clerk at a precision parts maker in Shizuoka, about 280 staff and supplying automotive OEMs, is closing the books for the third quarter. The factory maintenance budget was set at 40 million yen for the quarter. Actual spend lands at 53 million. Nobody raised a flag when an extra 6 million yen of tooling was committed in October, or when a 4 million yen rush order was added in November, or earlier this month when a 3 million yen budget revision quietly moved money from training into maintenance to cover the gap. The variance report now reads like a postmortem. The cash is gone, the executive who should have approved the revision was never asked, and the only thing left is to explain it in the management meeting.

This is what ungoverned budget changes look like in a company that runs budgets on spreadsheets. The budget is set once a year, then revised by whoever has the spreadsheet open, with no approval and no record. Overruns surface only at month-end close, far too late to act. This post is about a different model: a budget-setting and budget-change approval workflow inside a core business system, where every revision, from the initial annual budget down to a single mid-quarter reallocation, is routed, approved, and frozen as an audit record before it takes effect.

The Problem With Budgets That Anyone Can Edit

A budget is supposed to be a commitment. In practice, in most mid-size companies, it is a spreadsheet that anyone in finance can overwrite. Three things go wrong, and they compound.

First, the initial budget is set without a visible approval. Someone drafts the annual numbers, a manager glances at them, and they become the working budget. There is no record of who agreed to what, no snapshot of the approved version, and no audit trail. When a J-SOX reviewer asks who approved the maintenance budget increase last year, the answer is a shrug.

Second, mid-year revisions happen invisibly. A department head asks finance to move 2 million yen from supplies into overtime. The clerk edits the cell. The change takes effect instantly. No approver sees it. No threshold rule routes it. If the reallocation crosses an authority boundary that should have escalated to an executive, nobody notices, because the spreadsheet has no concept of authority. Roughly 40 percent of companies that adopt a workflow tool stall at merely electronifying a paper form, and budget control is a classic place where that stall shows up.

Third, overruns are discovered, not prevented. The budget and the actual spend live in separate systems that do not talk, so the comparison only happens when a person sits down at month-end and reconciles the two. By then the quarter is over.

An ERP changes the timing. It moves the budget checkpoint from month-end backwards to the moment a person asks to set or change a budget figure. That single shift is the difference between governing spending and documenting it.

What a Budget-Change Approval Workflow Actually Does

This is not about typing numbers into a nicer spreadsheet. A real budget approval workflow inside a core business system handles the full lifecycle of a budget figure. Reading the actual workflow engine, here is what is genuinely built and live today, and where the honesty line sits. Being precise about that line matters more than overselling.

Every budget is set through an approval, not around one

The first job of the workflow is to make the initial budget an approved object, not a draft someone happened to save. When finance proposes the annual maintenance budget, the figure does not become the working budget the moment it is typed. It enters an approval route, configurable so that a budget under a threshold is approved by the department head, while a larger budget escalates to the executive who owns that cost center. The routing is dynamic, tied to the role rather than to a named person, so a reorganization never breaks the chain.

This is conditional threshold routing, and it is live today. A 40 million yen maintenance line routes to the right approver based on the amount, automatically. The requester does not choose the approver. The amount and the role do. There is no way for a 60 million yen budget to be set with only a section chief sign-off, because the ERP never sends it there.

Every revision is a governed change, with a frozen snapshot

The second job is the one most companies skip entirely. Once a budget is set, it is not set in stone. Real operations need revisions. A machine breaks, a rush order is required, a project accelerates. The question is not whether revisions happen but whether they are governed.

In the workflow, a budget change is its own request type, with its own form and its own approval route. The requester proposes moving 3 million yen from training into maintenance. The system captures what is changing: the old figure, the new figure, the reason, and the requester. It routes the revision along the configured approval path, escalating by amount if the revision crosses a threshold. When the approver decides, the system freezes a snapshot of precisely what was approved, by whom, and when. That snapshot is the audit trail a J-SOX reviewer asks for. The budget did not silently drift from 40 million to 53 million. It moved through a series of approved, recorded, traceable revisions.

This is the same frozen-snapshot mechanism that governs capital expenditure and master-data changes. A governed record is one where you can answer who changed what, when, and with whose authority.

Visibility into where every budget request is stuck

Because every budget setting and change moves through the same workflow layer, you can see the state of every request in real time. A revision proposed last week that is still sitting in a manager queue is visible as a bottleneck, not hidden in an inbox. Watchers can follow a high-value budget request without being approvers. When a manager travels, safe delegation lets a named substitute approve, with mandatory re-approval for high-risk items on return. Approvals no longer freeze because someone is on a Shinkansen.

These are the same workflow capabilities that govern ringi (internal approval proposals), expense reimbursement, and purchase orders. The budget is simply another request type routed through the same engine, which is why a core business system that already owns the workflow beats a standalone budgeting tool bolted on the side.

The Honest Boundary: Approval Is Live, the Live-Spend Gate Is Coming

This is the part where precision matters. The budget-setting and budget-change approval workflow is built and live today. You can configure the approval routes, run revisions through them, freeze the snapshots, and produce the audit trail. That control is real and available now.

What is on the roadmap, not built, is the fully integrated budget-overrun gate that reads live committed spend from the ERP and writes the approved budget figure back to the budget line automatically on approval. Today the approval produces a fully-audited approval record, and the budget figure itself is updated in the normal flow. The automatic writeback, and the live comparison of actual spend against the approved budget that would block an over-budget request at submission, is what the roadmap closes.

Stating that boundary plainly is how trust stays intact. The approval control you switch on today is the one that stops a 53 million yen quarter from being a surprise at month-end. The live spend-overrun gate is the next layer, catching an over-budget purchase request before it is committed. The first is here now. The second is coming.

A Scenario: The Shizuoka Precision Parts Maker

Return to the maker in Shizuoka. Before the budget approval workflow, the maintenance budget drifted from 40 million to 53 million over a quarter with no approval and no record. In the governed flow, the same quarter looks different.

The annual 40 million yen maintenance budget is proposed in finance, routed to the executive who owns the cost center, approved, and frozen as version one. In October, the site manager needs an extra 6 million yen for tooling. He files a budget revision request, naming the source account, the destination, the amount, and the reason. Because the revision crosses a threshold, the system routes it past the department head to the executive, who approves. The system freezes a snapshot: revision one, plus 6 million, approved by the executive, timestamp recorded.

In November, the rush order adds another 4 million. Another revision, another approval, another snapshot. In December, the clerk who once would have silently moved 3 million from training into maintenance now files that as a revision request, because there is no untracked cell to edit anymore. Every figure is either the original approved version or a named, approved revision.

At month-end close, the variance report is no longer a postmortem. The finance team can show the chain of approved revisions that moved the maintenance line from 40 million to 53 million, each with its approver and timestamp. The surprise is gone because the governance happened in real time.

Why Budget Governance Matters Beyond Saving Time

The benefit is not only a shorter month-end, though the hours are real. Budget governance is where internal control and operational discipline meet. A company that cannot produce the approval record for a budget revision cannot defend its spending decisions to an auditor. Japan's electronic bookkeeping rules and the rising bar on J-SOX both push toward records that are searchable, tamper-evident, and traceable to a named approver. When every budget revision is a frozen snapshot inside the workflow, those records build themselves.

There is also a labor-shortage angle specific to Japan. According to the 2025 Communications White Paper, 48.7 percent of Japanese companies cite the talent shortage as the top barrier to digital transformation. The back-office team that once reconciled budgets by hand is shrinking, and the work that depended on a veteran clerk remembering why a figure changed has to move into a system that records the reason automatically. Finally, there is decision quality. An executive who sees a revision alongside the running total of approved changes to the same budget line makes a better-informed call than one who sees it in isolation. Visibility turns a rubber stamp into a real decision.

Common Questions, Answered Honestly

Can the approval thresholds match our existing authority regulations?

Yes, and they should. The thresholds are configurable, so the breakpoints in your ringi authority rules map directly into the routing logic. The point is not to invent new policy but to enforce the one already written. A common first step is to transcribe the current authority table into the routing rules verbatim, then refine from there.

What happens when a budget revision is approved?

The approved figure becomes the new working budget for that line, and the system freezes a snapshot of the revision: the old figure, the new figure, the approver, and the timestamp. The honest qualifier is that automatic writeback of the approved budget into the live budget ledger, with no manual step, is on the roadmap. Today the approval produces the audit record, and the budget figure is updated in the normal flow.

Does the system stop an over-budget purchase automatically?

Not yet. The budget-change approval workflow is built and live, so every revision to the budget is governed and traceable. The fully integrated budget-overrun gate that reads live committed spend and blocks an over-budget purchase request at submission is on the roadmap. Today the prevention comes from the approval control on the budget itself and on the purchase order, both routed through the same engine.

Does this survive when managers are out of the office?

Yes. The workflow supports safe delegation, so a traveling manager can delegate approval authority to a named substitute, with mandatory re-approval for high-risk items on return. The audit trail records exactly who stood in for whom.

Key Takeaway

Ungoverned budgets are not a spreadsheet problem. They are a governance problem. An ERP with a budget-setting and budget-change approval workflow turns every budget figure, from the annual plan down to a single reallocation, into an approved, recorded, traceable object. The approval control is live today. The live spend-overrun gate is coming. Together they move the budget checkpoint from a month-end postmortem to a real-time control.

Get Started With Kikan System

If your budgets drift through the year with no approval record, look at Kikan System. The workflow engine routes every budget setting and budget change by authority threshold, freezes a snapshot of each approved revision, and produces the audit trail an internal-control reviewer asks for. The budget-change approval control is live today, with the live spend-overrun gate and automatic budget writeback on the roadmap. Start on the free plan with up to 2 users, no credit card required. Begin at /#get-started.