Expense Report System Costs: SaaS vs. Custom Development

An expense report system centralizes and digitizes the process of submitting employee-paid expenses—transportation, entertainment, business travel—along with approval by managers and accounting staff, posting to the accounting system, and generating payment data for reimbursement. It replaces paper expense forms, receipts taped onto reports, and manual tallying in spreadsheets, aiming to reduce month-end accounting workload as well as missed submissions and duplicate claims. In recent years many cloud-based expense report SaaS products have appeared, and off-the-shelf services starting at just a few hundred yen per user per month now cover much of the expense-reporting workload for 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 reimbursement workflow. Custom development or customization only becomes necessary when a company needs unique expense-rule checks or tight integration with a project cost-management system.

- Transit IC card / corporate card integration: automatically import usage data from transit IC cards and corporate cards to reduce manual entry
- Smartphone OCR for receipts: automatically recognize amount, date, and merchant name simply by photographing a receipt with a phone
- Route search and automatic fare calculation: automatically calculate fares from origin and destination, preventing overlapping or fraudulent duplicate claims
- Approval workflow: multi-stage approval by managers and accounting, with automatic alerts for amounts over the limit or policy violations
- Accounting system integration: automatically post approved data to the correct account and pass it to accounting software
- E-book storage law (scanned-document retention) compliance: store photographed receipt images in a way that meets legal requirements so paper originals can be discarded

Expense report systems are also generally built using one of three approaches. Standard reimbursement and transportation-expense workflows are often fully covered by off-the-shelf SaaS, and the need for customization or custom development grows as unique expense rules or tight core-system integration are required.

These figures are general benchmarks only, and actual costs vary considerably depending on submission volume and the number of integrations. The thinking behind approval-flow design overlaps in many ways with the reconciliation and approval concepts covered in Invoice System Development Costs, which is worth reviewing alongside this guide to get a fuller sense of typical costs.

For most small and mid-sized businesses, combining an off-the-shelf expense report SaaS with smartphone OCR and corporate-card integration is sufficient. Digitizing the approval flow itself is covered in more depth in Workflow / Approval System Development Costs, which is worth reviewing alongside this guide if you are also evaluating an approval platform. On the other hand, companies that want to tally expenses together with project-level cost management, or that have industry-specific, complex reimbursement rules—such as automatic calculation of on-site allowances or per-diems—often find that standard SaaS features fall short, creating room to consider customization or custom development. Before moving to development, it is worth double-checking whether a higher-tier plan or add-on feature from an existing SaaS could meet the requirement, which is often the quickest way to avoid unnecessary development cost.

When considering an expense report system, compliance with the scanned-document retention rules under Japan's Electronic Books Preservation Act is an unavoidable topic. To store a smartphone photo of a receipt in place of the paper original, certain requirements must be met, such as applying a timestamp and recording any history of corrections or deletions. The relationship with Japan's qualified invoice system (Invoice System) is covered in detail in Operating Invoice Systems Under Japan's Invoice System; here, limiting the discussion to what affects development cost, building in automatic checks for whether a vendor is a registered qualified-invoice issuer, or automatically determining input tax credit eligibility by expense category, are elements whose scope should be clarified at the estimate stage.

With an off-the-shelf SaaS, operations can often begin within a few weeks of signing, focused mainly on building request forms and configuring approval routes. A customized SaaS / API-integration approach, including integration testing with the accounting system and migrating existing data, realistically takes one to three months, while custom development (core-integrated) typically runs six months to a year from requirements definition to go-live. Because expense reporting is used daily by every employee, running a pilot in one department before a company-wide rollout can substantially reduce usability complaints after launch.

- Submission volume and number of users: per-user SaaS pricing rises in proportion to headcount, and higher submission volume calls for more attention to processing capacity
- Required OCR accuracy: reading handwritten or overseas-issued receipts with high accuracy may require a higher-tier plan or individual tuning
- Number of transit IC card / corporate card integrations: more supported card issuers and transit operators increase integration design and testing effort
- Complexity of expense-rule checks: the more detailed the limits, eligible categories, and role-based rules, the more approval-logic development is required
- Scope of integration with accounting / cost-management systems: cost depends on how much posting to accounts or project codes is automated
- Rigor of e-book storage law compliance: cost depends on how much of the scanned-document retention requirements are automated within the system

A common mistake in expense report system projects is requesting a custom-development quote before checking what an off-the-shelf SaaS already covers, only to realize afterward that the off-the-shelf option would have been sufficient. The opposite also happens: a company selects an off-the-shelf SaaS, but its expense rules turn out to be unusual enough that manual checking is still required for every submission, leaving the process barely different from paper. Both pitfalls can be avoided by taking stock of your expense rules, approval routes, and required integrations before choosing a path, then concretely verifying whether an off-the-shelf service can meet them.

- Have you documented your current expense rules (limits, eligible categories, role-based rules)?
- Have you identified which transit IC card and corporate card issuers you need to integrate with?
- Have you defined your integration requirements with accounting and cost-management systems (accounts, project codes)?
- Have you clarified which types of receipts you want smartphone OCR to read, including handwritten or overseas-issued ones?
- Have you confirmed the scope of compliance needed for e-book storage law scanned-document retention?
- Have you decided which department will pilot the system, and for how long, before a company-wide rollout?
- Have you obtained quotes from multiple vendors and compared both initial and monthly/maintenance costs?

Expense report system development costs range widely by approach: an off-the-shelf SaaS can be started for around 300 yen per user a month, while custom development that integrates unique expense rules with a project cost-management system can exceed ten million yen. For most small and mid-sized businesses, the practical, cost-effective path is to first confirm whether an off-the-shelf service's smartphone OCR, IC card integration, and approval flow meet requirements, then scope development or customization only to the gaps that remain. Since costs vary by requirements, it is recommended to obtain and compare quotes from multiple vendors.