Handling Mixed 8 Percent and 10 Percent Tax Rate Invoices in Your Core Business System

It is the last Friday of the month. Your finance lead opens the invoice run for a major catering client and stops cold. One invoice, three line types, two different tax rates, and a junior clerk who applied a flat 10 percent to everything the night before. By the time the error surfaces, the customer has already received the wrong figure, the tax account does not match the journal, and the monthly close slides another two days to the right.

For Japanese businesses that sell both food and eating-out services, this is not a rare edge case. It is the default shape of every invoice. The reduced 8 percent rate on food and beverages sits alongside the standard 10 percent rate on eating out, and a single bill can carry both at once. A core business system that treats tax as a flat invoice-level switch cannot keep up. This guide explains what changes when each invoice line carries its own tax setting, why it matters for the Japanese market, and what to look for in an ERP that gets this right out of the box.

The Problem (what it costs now)

Most legacy core business systems, and many spreadsheet-based workflows, apply a single tax rate per document. You pick 10 percent or 8 percent at the top of the invoice, and that rate cascades down to every line. For a company that sells only one type of taxable good, that works. For a bento supplier who also runs eat-in catering, it breaks down on the very first mixed invoice.

The cost shows up in four places.

First, miscoding. A clerk sets the whole invoice to 10 percent, the takeout bento lines that should be 8 percent get overcharged, and the customer either disputes the bill or quietly absorbs an inflated figure that erodes trust. Reverse the error, set the whole invoice to 8 percent, and the eat-in catering lines are underbilled, which means under-reported consumption tax and exposure later.

Second, reconciliation pain. When the tax rate on the invoice does not match the tax posting in the general ledger, the monthly close stalls while someone manually splits the figures and re-enters the journal. For many Japanese small and midsize businesses, the monthly close already takes one to two weeks, and mixed-rate errors add days on top of that.

Third, audit risk. Under the qualified-invoice system that started in October 2023, the tax shown on a qualified invoice has to line up with what you report. A pattern of miscoded mixed invoices is exactly the kind of discrepancy that creates friction during a tax review, even when the intent was honest.

Fourth, lost time on corrections. When an invoice goes out wrong, the fix is a credit note. If the core business system does not handle credit notes cleanly, staff resort to manual journal entries or external spreadsheets, which fragments the audit trail and makes the correction harder to trace.

None of this is a problem the business owner signed up to solve. It is a structural mismatch between how the tax rules work and how the old core business system was built.

What Changes

The shift is simple to describe and hard to live without once you have it. Instead of one tax rate per invoice, the ERP holds separate tax settings, one at 10 percent standard and one at 8 percent reduced, and each invoice line carries its own tax setting. The per-line tax then rolls up correctly into the document total, the journal, and the tax accounts.

In a double-entry core business system built this way, every sales invoice and every purchase bill generates its own journal entries automatically. Each tax rate is a configured record with a name, a percentage, and two linked accounts: a sales tax account, treated as a liability for the tax you collect, and a purchase tax account, treated as an asset for the tax you paid. A line coded to the 8 percent setting lands in the reduced-rate liability account; a line coded to the 10 percent setting lands in the standard liability account. The split is structural, not a manual calculation.

This setup also makes credit notes first-class. A corrected invoice produces a proper credit note that reverses the original journal, line by line, at the original tax rates. There is no spreadsheet workaround and no broken audit trail. Invoice types are explicit in the system, so a credit note is never confused with a regular invoice in the period close.

Because the tax settings are configurable master data, you do not need a developer to add a rate or change an account. Each company sets up its rates once, and every product, every invoice line, and every business partner record can reference the correct setting. This is the fit-to-standard principle in practice: the system adapts to the tax rules through configuration, not custom code.

A Real-World Scenario

Consider a bento and catering supplier based in Nagoya, with about 70 staff. Two revenue lines run side by side. The first is takeout bento boxes and retail food products, sold at the reduced 8 percent consumption tax rate because food and beverages qualify for the reduced rate. Eat-in and event catering services are sold at the standard 10 percent rate, because eating out is treated as a standard-rated service regardless of what is on the plate.

A single corporate client often buys both in the same billing cycle: five hundred takeout bento boxes for a staff lunch, plus a full seated catering setup for a product launch. The invoice has to show the bento lines at 8 percent and the catering lines at 10 percent, with each tax subtotal correct, the document total correct, and the qualified-invoice registration number of the supplier printed on the document.

Before the company moved to a per-line tax model, the monthly invoice run was a recurring fire drill. A finance clerk would set the whole invoice to 10 percent to be safe, the takeout lines would be over-taxed, and the tax account balances would not reconcile against the sales by category report. Fixing it meant manual splits in a spreadsheet, manual journal entries, and a credit process that lived outside the core business system. The monthly close routinely ran 10 business days, with two consumed entirely by mixed-rate corrections.

After configuring two tax settings, one at 10 percent and one at 8 percent, and assigning the correct setting at the product and invoice-line level, the same invoice takes a different path. Each line carries its own rate, the document total and tax split calculate themselves, and the journal posts to the correct liability accounts automatically. A correction becomes a proper credit note that reverses the original entries at the original rates. The close drops from 10 days toward a handful, and the finance team stops dreading the catering client.

The point is not that the software does the tax accountant's job. It does not. The point is that the data is structured correctly from the moment the line is entered, so the accountant, the auditor, and the period close all work from the same clean figures.

Why This Matters for Japan

Mixed-rate invoicing is not a niche scenario in Japan. It is the daily reality for any business that touches food retail and food service, and for many that bundle taxable services with reduced-rate goods. The consumption tax regime has two headline rates, 10 percent standard and 8 percent reduced on food and beverages, and the food-versus-eating-out rule is precise: food and drinks sold for takeaway qualify for 8 percent, while eating out, meaning food and drink provided for consumption on the premises as part of a service, is taxed at 10 percent.

The qualified-invoice system layers on top of this. Since October 2023, a registered business issues a qualified invoice that carries its registration number, and the buyer uses that document to support their input tax credit. The transitional input tax credit schedule was revised by the 2026 tax reform, so the old shorthand of a straight drop to zero no longer holds. According to the National Tax Agency, the schedule now runs 80 percent deductible through September 2026, then 70 percent from October 2026 to September 2028, then stepping down to 50 percent, then 30 percent, and reaching 0 percent from October 2031. Businesses need figures that hold up across that entire runway.

This is also why the surrounding detail matters. A modern ERP stores the supplier's qualified-invoice registration number and corporate number on the business partner record, and prints the company's own registration number on outgoing invoices. It captures the tax treatment per line, so a later review can reconstruct exactly which lines were reduced-rate and which were standard. It ties every invoice and bill to a closing run, which locks a clean set of figures for the period. None of this replaces the final tax return, which remains the tax accountant's domain. It gives the accountant a set of books that is internally consistent from day one, instead of a pile of corrections to unwind.

The broader market pressure compounds the urgency. The 2025 legacy cliff pushed many on-prem ERP platforms, Windows Server 2012 R2, and older database engines past their end of security support. METI has framed the 2025 IT legacy problem around roughly 12 trillion yen of potential economic impact. Businesses that renew now are not just chasing a tax feature. They are rebuilding the foundation so that rules like the revised input tax credit schedule fit inside the system instead of being managed in a side spreadsheet.

Is This Right for Your Business?

Not every company needs per-line mixed-rate invoicing today. If you sell a single category of goods at a single tax rate, a simpler setup will carry you. But the question to ask is whether that will still be true in two years.

Per-line tax settings become essential when food or beverages sit alongside taxable services, when products and labor share a single invoice, or when customers buy from you in more than one tax category. The same applies if the monthly close regularly slips past a week on reconciliation work, if the finance team keeps a parallel spreadsheet to split tax correctly, or if the company has grown through acquisition or succession and inherited a core business system that was never built for two rates.

For Japanese small and midsize businesses facing the labor shortage and the succession problem, the value of an auditable, transferable core business system is rising fast. A buyer, an investor, or a successor does not want to inherit a pile of manual workarounds. They want a system where the tax split is configured once, coded correctly on every line, and rolled up into a clean period close.

The right test is simple. Ask your vendor to show you a single invoice with one line at 8 percent and another at 10 percent, posted to the correct liability accounts, corrected by a proper credit note, and tied to a closed period. If they cannot show that in a live demo, the system is not built for the rules you actually operate under.

Frequently Asked Questions

Does the system file my consumption tax return for me?

No, and it should not claim to. The ERP structures the data correctly, codes every line to the right tax setting, and rolls the figures up into clean period totals. Your tax accountant or tax return preparer handles the final tax return and any government filing using those figures. The value is in trustworthy books, not in automated submission.

How does the food-versus-eating-out rule work in practice?

Food and beverages sold for takeaway qualify for the 8 percent reduced rate. Eating out, meaning food and drink served for consumption on your premises as part of a service, is taxed at the standard 10 percent rate. A mixed invoice simply carries the 8 percent setting on the takeaway lines and the 10 percent setting on the eat-in lines, and each line lands in the correct liability account.

What happens if an invoice goes out with the wrong rate?

You issue a credit note. In a double-entry core business system built for this, the credit note reverses the original journal line by line at the original tax rates, and a corrected invoice replaces it. The audit trail stays intact, and the period figures stay reconciled.

Can we add or change a tax rate without a developer?

Yes. Tax settings are configurable master data. You define each rate with its percentage, its sales tax account as a liability, and its purchase tax account as an asset. Adding a rate or re-pointing an account is a configuration change, not a code change.

Stop Dreading the Mixed-Rate Invoice Run

Kikan System is built for the Japanese tax rules you actually work under, with configurable 8 percent and 10 percent tax settings, per-line tax on every invoice, automatic double-entry journals, proper credit notes, and a clean period close. The same core business system carries your qualified-invoice registration number, stores your business partners' registration numbers, and ties every document to a locked closing run. See it for yourself with up to 2 users, no credit card required.

(-> Start free)(/#get-started)

For more on choosing and renewing a core business system in Japan, read our cloud ERP selection guide and our walkthrough of the 2025 cliff and core business system renewal.