Workflow / Ringi Approval System: Cost Guide (2026)

A workflow / electronic approval (ringi) system digitizes the drafting, routing, approval, and storage of internal requests, centrally recording "who approved what, and when." It replaces paper approval documents, hanko-stamped routing slips, and email-attached requests, aiming to eliminate stalled approvals and lost paperwork. In recent years many cloud-based workflow SaaS products have appeared, and off-the-shelf services starting at just a few hundred yen per user per month now cover the request-and-approval workload of many small and mid-sized businesses. Because of this, before considering development costs at all, the starting point should be checking whether an off-the-shelf service can already handle your approval flow.

- Request form builder: create diverse form types—ringi, expense claims, leave requests, purchase requests—with no-code tools
- Approval route configuration: multi-stage approvals, conditional branching, delegated approval, and escalation based on amount or department
- Notifications and reminders: pending-approval notices, dunning for stalled items, and deadline alerts
- Audit trail / logs: tamper-resistant history of who approved or returned each item and when
- Core / accounting system integration: pass approved data to accounting, procurement, or HR systems
- Mobile approval: submit and approve from a smartphone (for staff on the road or on-site)

Workflow systems are also generally built using one of three approaches. Standard ringi, expense, and leave requests are often fully covered by off-the-shelf SaaS, and the need for customization or custom development grows as unique approval logic or tight integration with core systems is required.

These figures are general benchmarks only, and actual costs vary considerably depending on requirements. For a broader look at how system development costs are structured, see Understanding System Development Costs. Per-user SaaS pricing accumulates as the number of users grows, so a company-wide rollout requires estimating by headcount.

For many small and mid-sized businesses, simply configuring the standard request forms (ringi, expenses, leave, purchasing) in an off-the-shelf workflow SaaS is enough. On the other hand, when unique requirements are essential—approval routes that branch in complex ways by amount or counterparty, or approvals that must be linked with inventory and order data in a core system—customizing the SaaS or custom development enters the picture. If you are also considering digitizing the ordering process itself, review Order Management System Development Costs alongside this.

When considering a workflow system, compliance with internal controls and Japan's e-book storage law also becomes a point to address. Approval records for ringi and expense claims serve as evidence for later verifying the validity of spending, so being able to preserve "who approved it" in a tamper-resistant form is important. In particular, for requests involving expenses, invoicing, and payments, you must meet the e-book storage law's electronic-transaction data storage requirements (such as searchability by date, amount, and counterparty). Most off-the-shelf SaaS include audit logs and e-book storage law support as standard, but with custom development the storage requirements must be built into the system spec, so confirm the scope of coverage at the estimate stage.

- Complexity of approval routes: the more multi-stage branching and conditional approvals by amount, department, or counterparty, the greater the design effort
- Number of form types: the more request types you digitize, the more form-building and testing effort is required
- Number of users: per-user SaaS pricing rises in proportion to headcount
- Integration with existing systems: API integration with accounting, HR, or core systems is a major driver of additional development
- Mobile and multi-site support: approval requirements from the field or on the road widen the scope of design
- Audit and control requirements: the rigor of internal-control reporting and e-book storage law compliance changes the effort involved

A good way to proceed is to first take stock of your current request-and-approval flows and start by reducing the "approval stages you truly need." Simply moving paper routing into a system as-is does not solve the root problem of stalled approvals. On that basis, estimate how far an off-the-shelf workflow SaaS can realize your flow, and make only the requirements it still cannot meet the target for customization or custom development—this yields the best cost-effectiveness. If you want to organize your whole internal information-sharing foundation, Intranet Portal Development Costs is helpful, and for choosing a vendor in general, see A Guide to Ordering System Development.

Workflow / electronic approval system development costs can start from just a few hundred yen per user per month when using an off-the-shelf SaaS as-is, while requiring unique approval logic or tight integration with a core system can push initial costs into the millions of yen. The best-balanced approach is to first review the approval flow itself and reduce stages, then target only the requirements an off-the-shelf SaaS cannot meet for customization or custom development. Because costs vary greatly by requirements, we recommend comparing quotes from multiple vendors before deciding.