From Trip Request to Settlement in One Flow: No Lost Receipts

Picture a sales engineer in Nagoya who needs to visit three clients in Fukuoka next week. Today, she fills out a paper travel request, her manager stamps it, and it lands in a filing cabinet. She flies down, pays for hotels, trains, and client dinners out of pocket or a cash advance, and collects a sleeve of paper receipts. Back at the office, she hunts for each slip, retypes the amounts into a settlement form, chases her manager for a second signature, and hands the pile to finance. A receipt goes missing. The settlement stalls. Three weeks later, nobody can find the original request that set the budget, so nobody is sure the spend was even approved in advance.

That fragmented chain is the everyday reality of business travel in most Japanese companies. The trip itself is one event, but the paperwork around it is four disconnected stages that never talk to each other. Receipts get lost, settlements get missed, and the audit trail is whatever survived in a drawer. The fix is not another standalone travel-booking tool. The fix is one connected flow, inside your core business system, where the request, the budget check, the approval, and the post-trip settlement all live as stages of a single record.

Why a Trip Splinters Into Four Broken Pieces

A business trip is deceptively complex. It is not a single expense. It is a pre-trip request that sets a budget, a budget check that confirms the spend fits, an approval that authorizes the trip, and a post-trip settlement that reconciles what was actually spent against what was approved. Each of those stages has its own form, its own approver, and its own paper trail.

The moment those stages live in different places, the trip fractures. The request sits in a filing cabinet. The budget check happens in someone's head or a spreadsheet that nobody updates. The approval is a hanko stamp on a slip that travels around the office. The settlement is a separate form with receipts stapled to it. None of these stages can see the others, so the whole thing depends on people remembering to connect them. People forget. Receipts fade or vanish. Settlements drift weeks past the trip.

The numbers tell the story. A 2024 TOKIUM survey found that 90.4 percent of employees still submit paper receipts, and only 7.0 percent of expense claims are electronic. That means the overwhelming majority of trip settlements are still built on paper slips that can be lost, smudged, or left in a wallet for a month. The processing cost is just as stark. Benchmark data from Rakuraku Seisan shows expense handling dropping from roughly three hours to thirty minutes when the flow is digitized. The gap between the paper present and the connected future is enormous, and a core business system is what closes it.

The Answer: One Connected Flow With a Dynamic Form Per Stage

The core idea is simple. A business trip is not four forms. It is one record that moves through four stages, each with the right form for that stage. When the trip request and the trip settlement are linked, the budget approved before departure is the same budget reconciled after return, and nothing falls through the cracks.

This is what a core business system does that a stack of standalone tools cannot. The workflow engine lets you define one trip record that carries a dynamic form for each stage. The pre-trip request form captures destination, purpose, dates, estimated costs, and the project or client the trip serves. The settlement form captures actual receipts, actual amounts, and the variance against the approved estimate. Because the two forms are stages of the same record, the settlement always knows what was originally approved. You cannot lose the budget because the budget is part of the trip.

The dynamic form is what makes this work without a developer. Each stage shows only the fields that stage needs. The request stage asks for estimates. The settlement stage asks for actuals and receipts. The fields are not hardcoded. They are configured per stage, so a domestic day trip and a week-long overseas visit can use the same connected flow with different visible fields. One trip type, one flow, forms that adapt to the moment.

A Single Approval That Covers Both Halves

Here is where most travel tools fail. They handle the request or they handle the settlement, rarely both, and almost never as one approval. The result is a trip where the manager approves the plan, forgets about it, and then has to approve a settlement weeks later with no memory of what was agreed.

In a connected flow inside your ERP, the approval is unified. The manager sees the original request and the settlement side by side, with the variance highlighted. Did the engineer spend more on hotels than planned? The system shows the gap against the approved estimate, not a number floating in isolation. The manager approves the settlement with full context, or sends it back for clarification, and the entire history of who approved what and when is attached to the trip record as an audit trail.

That audit trail is the part that matters for internal control. A frozen snapshot of exactly what was approved, by whom, and at which stage, is what a paper slip in a drawer can never provide. When the request and the settlement share one record, the trail is complete by construction. You do not assemble it after the fact. You build it as the trip moves.

When the Expense Posts Automatically

The settlement is approved. Now what? In the old paper world, finance retypes the amounts into the ledger, matches the receipt to the line, and prays the tax rate is right. In a core business system, the approved settlement posts the expense automatically.

This is one of the two places where automatic writeback to the ledger is genuinely built, not on a roadmap. When a trip settlement is approved, the system creates the expense reimbursement record and the accounting entry follows the rules you already configured. The pre-tax amount lands in the right expense account, the input consumption tax is captured per rate, and accounts payable is credited for the amount owed to the traveler. The approved expense posts automatically, with the trip record as the reference. No retyping, no separate spreadsheet, no second system.

Being honest about the boundary matters here. Automatic writeback is built for expense reimbursement and for leave applications. That covers the vast majority of trip settlements, because the cost of a business trip is an expense reimbursement. Other writebacks, like purchase orders or vendor bills, are on the roadmap, not built today. But for the trip flow specifically, the one that matters in this post, the approved expense posts to the books automatically. That is a real, implemented capability.

A Scenario: The Sales Team on the Tokaido Corridor

Imagine a precision parts maker in Shizuoka, about 280 staff, supplying automotive OEMs across the Tokaido corridor. Their sales engineers travel constantly between clients in Nagoya, Tokyo, and sometimes Hiroshima. Before their core business system, each engineer filed a paper travel request, carried receipts across a week of travel, and dumped a settlement folder on finance at month-end. Receipts went missing. Settlements slipped past the accounting close. Nobody could prove the spend matched an approved budget.

In the connected flow, the engineer files a travel request from her laptop on Monday. The dynamic form captures the three client visits, the estimated train fare, two hotel nights, and the client dinner, all tagged to the relevant projects. The request routes to her manager, who approves on Tuesday. The budget for the trip is now part of the record.

She travels. On the train home Friday, she opens the same trip record and moves it to the settlement stage. The settlement form appears, showing only the fields for actuals and receipts. She enters each amount against the matching line, and because the form is configured for that stage, nothing that does not belong in a settlement shows up. When a hotel came in higher than the estimate, the variance is visible the moment she lines it up against the approved request. Her manager approves the settlement with the original request and the actuals side by side. The moment approval lands, the expense reimbursement posts automatically. Travel lands in travel, meals in meals, and the input consumption tax is captured per rate. At month-end, finance is not retyping slips. The trip already posted.

Why This Matters Beyond the Receipt

The benefit is not only that receipts stop getting lost, though they do. The deeper win is that the trip becomes one auditable object instead of four orphaned pieces of paper. Every approved trip carries its request, its budget, its receipts, its approvals, and its posted entry in a single record. That is the internal-control story that matters for J-SOX and for any review.

There is also the labor-shortage angle. Japan's 2025 white paper on communications flagged that 48.7 percent of companies cite the labor shortage as the top barrier to digitalization. The irony is that the paper trip flow is exactly the kind of low-value manual work that absorbs scarce back-office hours. Connecting the flow frees the finance team to do analysis instead of data entry. That is how digitalization answers the labor shortage instead of being blocked by it.

Finally, there is cycle time. When the request and the settlement are one record, and the approved expense posts automatically, the time from trip-end to posted entry collapses. Finance stops chasing engineers for slips. Engineers stop dreading the settlement folder. The month-end close gets shorter because the travel spend is already in the books, not arriving in a stack on the last Friday.

Common Questions, Answered Honestly

Does the settlement have to match the request exactly?

No, and it should not, because real travel rarely matches estimates. The point of connecting them is that the variance is visible and explainable. If a hotel cost more, the manager sees the original estimate and the actual side by side and approves with context. What the system prevents is a settlement with no approved request behind it at all, which is how unapproved spend slips through.

What happens if a manager is traveling when a settlement lands?

The approval does not freeze. The workflow engine supports safe delegation, so a traveling manager can hand approvals to a delegate without losing control. For high-risk items, the system can require the original manager to re-approve on return. The trip settlement keeps moving instead of stalling for a week.

Is the automatic expense posting real or a roadmap promise?

Real, for expense reimbursement. Trip settlements are expense reimbursements, so the approved settlement posts the expense and the accounting entry automatically. The honest boundary is that other writebacks, such as purchase orders or vendor master updates, are on the roadmap. For the trip flow in this post, the auto-posting is built and working.

Can we set different rules for different trip types?

Yes, and the dynamic form is what makes it possible. A domestic day trip and an overseas week can use the same connected flow with different visible fields per stage. One flow, forms that adapt, one set of rules applied consistently.

Key Takeaway

A business trip is one event. Stop treating it as four disconnected forms. When the request, the budget check, the approval, and the settlement live as stages of a single record inside your ERP, receipts stop getting lost, settlements stop getting missed, and the approved expense posts automatically. The trip becomes one auditable object instead of a pile of paper.

Get Started With Kikan System

If your travel settlements still live across paper and email, look at Kikan System. The workflow engine runs the trip as one connected flow, with a dynamic form for each stage, a unified approval, a full audit trail, and automatic posting of the approved expense to the ledger. You can start on the free plan with up to 2 users, no credit card required. Begin at /#get-started.