Paperless Expense Reimbursement in Your Core Business System

It is the last Friday of the month. Tanaka from sales walks back to the Osaka office carrying a clear folder stuffed with train tickets, taxi receipts, and a crumpled dinner bill from a client visit three weeks ago. The finance lead counts the slips, frowns at a faded thermal printout she can barely read, and types the amounts, tax rates, and vendor names into a spreadsheet by hand. Then she emails a manager for approval, waits, prints a payment list, and keys the journal entries into the accounting software. Multiply that by sixty staff, every month, and the cost is staggering.

This scene is still the norm in Japan. A 2023 TOKIUM survey of office workers found that about 90 percent still submit expenses by physically bringing paper receipts to the office. The same research series reported that only around 7 percent of companies have fully digitized their expense process. The gap between wanting digital transformation and actually running it is enormous. The good news is that a modern core business system closes that gap without bolting on yet another standalone tool.

Why Paper Expenses Quietly Bleed Money

Expense reimbursement looks small on a per-claim basis. It is anything but small in aggregate. Every paper receipt that reaches the office triggers a chain of manual work: data entry, rate lookup, duplicate checking, approval chasing, filing, and re-entry into the books. Each step is a chance for a typo, a lost slip, or a missed input-tax credit.

The cost shows up in three places. First, staff time. Finance teams spend days at month-end reconciling paper rather than analyzing numbers. Second, lost deductions. When a consumption-tax receipt disappears or fades, the input credit on that 10 percent or 8 percent purchase simply vanishes. Third, audit risk. A box of receipts in a cabinet is hard to defend in a review. None of these costs appear as a line item, which is exactly why they persist for so long.

The deeper problem is fragmentation. Receipts live in wallets. Approvals live in email. Amounts live in spreadsheets. The ledger lives somewhere else entirely. A core business system fixes this by collapsing all of those steps into one connected flow, where the claim, the approval, the receipt image, and the accounting entry are never more than a click apart.

What a Built-In Expense Module Actually Does

This is not about scanning a receipt and hoping for the best. A real expense module inside a core business system handles the whole lifecycle. Reading the actual expense code, here is what is genuinely built and not a roadmap promise.

One claim, many lines, fully structured

An employee files a single reimbursement that holds as many lines as they need. Each line carries the expense category, the transaction date, an optional vendor name, a free-text description, and a pre-tax amount. A line can also carry its own tax breakdown, so a single claim might mix meals taxed at 10 percent with transport taxed at a reduced rate, all in one submission. Lines can be tagged to a project, so a sales trip to a specific client lands its cost against the right project ledger.

Critically, the totals are never trusted from the screen. The system recomputes the subtotal, the aggregated tax by rate, and the grand total on the server every time. An employee cannot hand-edit the total and create a rounding gap between the claim and the books.

Receipts attached where they belong, with rules

Every line can hold receipt attachments. When a claim is created, the files move from temporary upload storage to permanent paths inside the same transaction, so a half-uploaded claim never leaves receipts stranded. The system then serves secure, time-limited links to view those images. There is no shared drive, no email attachment, no folder naming convention to remember.

The interesting part is the rules engine. Each expense category can be configured with its own receipt policy. A category can require a receipt for every amount, or only above a threshold you set, say 1,000 yen. On submit, the system checks every line against its category rule. A 3,000-yen taxi line without an attached receipt is blocked before it ever reaches a manager, with a clear message naming the line and the category. This is the single biggest reason digitized expense systems cut month-end work: bad claims never start the approval journey.

Approvals that travel with the claim

A claim is not an island. The moment it is submitted, the expense module hands it to a configurable approval workflow. The claim binds to a defined approval route, and the status flows through draft, submitted, changes-requested, and approved. A manager can send a claim back for revision, and the employee can edit and resubmit without retyping the whole thing.

Because the approval lives inside the same system, the history is complete. You can see who approved what and when, all attached to the original claim. For companies thinking about internal control, this is the audit trail that a paper approval slip simply cannot provide.

The Step That Most Tools Leave Out: Automatic Journal Entries

Here is where a core business system separates itself from a receipt-scanning app. When an expense reimbursement is approved, the system writes the accounting entry for you. It credits accounts payable for the full amount owed to the employee. It debits the expense account of each line for its pre-tax amount, so travel lands in travel, meals in meals, supplies in supplies. It debits the input consumption-tax account for each distinct tax rate, aggregated across lines. The entry posts the moment approval completes, with the claim number as reference. The result is a balanced, posted entry.

Later, when finance marks the approved claim as paid, a second entry fires automatically. The act of paying the employee generates a payment journal entry that debits accounts payable and credits cash or bank. So from approval to cash out the door, both legs of the transaction are booked automatically, in the correct accounts, with the tax in the right place.

This is the third of the three sources that auto-post in the system. Sales invoices and purchase bills do it on their own. Expense reimbursements do it the moment they are approved, with the payment entry following at pay. Everything else, like inventory adjustments or manufacturing costs, is a manual journal entry today. Being honest about that boundary matters more than overselling.

A Scenario: The Precision Parts Maker in Higashi-Osaka

Consider a precision parts manufacturer in Higashi-Osaka, about seventy staff, supplying components to industrial equipment makers across Kansai. Their sales engineers travel constantly between clients in Osaka, Kyoto, and Nagoya. Before their core business system, each engineer accumulated a month of receipts and dumped them on the accounting team in a folder.

In the new flow, an engineer files a claim from a phone the evening of the trip. The Shinkansen ticket is attached to a transport line. The client dinner receipt is attached to a meals line, tagged to the project for that customer. Both lines carry their own 10 percent consumption tax. The claim lands in the manager's approval queue the same night. The manager approves during the morning commute.

At month-end, the accounting lead selects the approved claims and marks them paid in a single bulk action. The system refuses to pay any claim that is not fully approved, and it refuses to pay anything twice. The expense, tax, and accounts-payable entries already posted to the ledger when each claim was approved, and the moment payment is recorded, the cash-out entry follows. The 800,000 yen the company used to spend in scattered travel and entertainment now reconciles in minutes instead of days, and every yen of input consumption tax is captured because the receipts are attached before submission, not hunted for later.

Why This Matters Beyond Saving Time

The benefit is not only hours saved, though the hours are real. A 2025 DesigNet survey found that 75.6 percent of Japanese companies are already working to digitize paper data, and that nearly half rank paperless promotion as their top digital-transformation priority. Expense reimbursement is one of the highest-friction paper processes a company runs, which makes it one of the fastest ways to show tangible progress on that transformation goal.

There is also a compliance angle. Japan's electronic bookkeeping preservation rules and the qualified-invoice system both push companies toward keeping digital records that are searchable and tamper-resistant. When receipts are attached to lines, and lines roll up into posted journal entries with claim references, the records an auditor wants are already in place. You are not retrofitting compliance onto a paper process. You built the compliant process from the start.

Finally, there is succession planning. Many Japanese small and mid-size manufacturers carry decades of tribal knowledge in the head of one veteran accounting person. When that person retires, the paper system retires with them. A core business system captures the workflow, the rules, and the history so the next generation inherits a process, not a puzzle.

Frequently Asked Questions

Is switching from our current spreadsheet going to lose our history?

No, and you should insist on migrating open and recent claims before go-live. The expense module in Kikan System supports drafts, submitted claims, and paid claims as distinct states, so you can import historical claims at their correct status. What you should not expect is automatic migration of receipts sitting in email inboxes or desk drawers, which is a one-time cleanup project worth doing once so you never do it again.

How do we know the accounting entries are correct?

Because they follow double-entry by construction. Each approved claim produces a balanced entry: the sum of the expense debits plus the tax debits equals the accounts-payable credit. You can open any journal entry and trace it back to the exact claim and line. If an expense category is missing its expense account mapping, the system skips that line with a warning rather than silently posting to the wrong account. Transparency here is the safeguard.

Can we set different rules for different cost types?

Yes, and this is where the per-category receipt policy earns its keep. Entertainment might require a receipt for every yen. Local transport might require one only above 1,000 yen. The threshold and the always-required flag live on the expense category, so the policy travels with the cost type, not with whoever happens to be filing. One rule, applied consistently, every time.

What about consumption tax on mixed-rate expenses?

A single claim can hold lines taxed at different rates, and the journal entry handles each rate as its own debit to the input consumption-tax account. So a claim with a 10 percent meal and a reduced-rate transport cost posts two separate tax lines, aggregated correctly. Nothing is blended or approximated.

Key Takeaway

Paperless expense reimbursement is not a scanning app. It is the connection between a receipt, an approval, and a journal entry, all inside one core business system. When those three live together, month-end gets shorter, input tax stops leaking, and the audit trail builds itself.

Get Started With Kikan System

If you are tired of clearing folders at month-end, look at Kikan System. The expense reimbursement module files claims, enforces receipt rules by category, runs approvals, and posts both the expense and the payment journal entries automatically. You can start on the free plan with up to 2 users, no credit card required. Begin at /#get-started, or compare plans at /#pricing.