Core Business System Tax Settings Master: Separating Output and Input Tax

It is the last Friday of the quarter and your accounting team is still in the office. The consumption-tax return is due. Somewhere in the general ledger sits one enormous miscellaneous tax account, holding every yen of output tax you charged customers and every yen of input tax you paid vendors, all dumped together. Before anyone can file, the numbers must be sorted by hand, line by line, into what you collected and what you spent. Hours vanish. Confidence does not survive the process.

This scene plays out in thousands of Japanese companies every reporting period. The qualified-invoice system has made it harder, because the credit you can claim on purchases now depends on a sliding scale, not a single flat rate. A core business system that separates output tax from input tax at the moment of entry removes the manual re-sort entirely. The structural separation is what produces a clean return.

The Problem: What It Costs Now

When all tax lands in one account, you pay for it in three ways.

First, there is the labor. A finance staffer must comb through the ledger, identify which lines are sales-tax collected and which are purchase-tax paid, and rebuild two totals that the system should already know. For a mid-size distributor running a few thousand invoices a quarter, this re-sort can consume days of skilled time every period.

Second, there is the risk of error. Manual sorting invites mistakes. A single misclassified line shifts your taxable base, and under the consumption-tax regime the penalty for getting it wrong lands on you. Errors discovered late mean amended filings and tense conversations with your tax accountant.

Third, there is the visibility gap. With one merged account, management cannot see the real tax burden by product line or by vendor category until the manual work is done. Decisions about pricing, vendor terms, and cash timing wait on a report that exists only after the close. For many Japanese small and mid-size enterprises, the monthly close still takes one to two weeks or more. A merged tax account is a leading reason why.

What Changes

A double-entry core business system treats consumption tax as what it legally is: two distinct balances. Output tax, the tax you collect on sales, is a liability. You owe it to the tax office. Input tax, the tax you pay on purchases, is an asset. You recover it as a credit. Mixing them in one account is not just untidy, it misstates both sides of the balance sheet.

The structural fix lives in the tax settings master. Each tax rate is configured as its own record, carrying four things: a name, a rate as a percentage (decimals preserved, so 10.00 or 8.00 are exact), a sales-tax liability account, and a purchase-tax asset account. The moment an invoice line or a product carries that tax setting, the system knows where the resulting tax belongs.

The enforcement happens at write time, not at report time. The chart of accounts in a fit-to-standard ERP lets each company define its own accounts with subtypes, and the core business system will not let you link a sales-tax setting to anything other than a liability account, nor a purchase-tax setting to anything other than an asset account. The guardrail is structural. The configuration itself is rejected if the subtypes are wrong.

Then the journal entries take over. Every sales invoice auto-generates its own journal entries, with the output tax landing in the linked liability account. Every purchase bill auto-generates its own entries, with the input tax landing in the linked asset account. Entry-type validation runs on each one. Credit notes, treated as their own invoice type, post the reversal the same way. Nobody sorts anything by hand, because the sorting was decided when the tax setting was created.

Multi-rate is native, not bolted on. Because each rate is its own tax-setting record, a company running the standard 10 percent rate and the reduced 8 percent rate on food and beverages simply configures two settings. A product or invoice line points to whichever applies. The journal entries follow the linked accounts for that specific rate, so a reduced-rate transaction never contaminates a standard-rate total.

How the Linked Accounts Work Together

Picture the two accounts as a matched pair behind every rate. When a sales invoice goes out at the standard rate, the output tax flows into the linked sales-tax liability account, the bucket you owe the tax office. When a purchase bill arrives at the same rate, the input tax flows into the linked purchase-tax asset account, the bucket you will recover as a credit. Because both accounts are pinned to the rate at configuration time, a glance at the pair tells you the net position for that rate without touching a source document. The separation travels with the transaction, not with whoever runs the report.

A Real-World Scenario

Consider an electronics distributor in Tokyo with roughly 120 staff. The company buys components from domestic and overseas partners, assembles small product lines, and sells to retailers across Japan. Its volume is healthy. Its tax accounting was not.

For years, the company recorded every consumption-tax amount into a single general tax account. Output and input sat together, undifferentiated. At the end of each quarter, the accounting lead exported the ledger into a spreadsheet and spent close to a full week sorting lines by direction and by rate, rebuilding the totals the tax accountant needed for the return. When the qualified-invoice system arrived and the transitional input-tax credit schedule began phasing down, the spreadsheet grew new columns for deductible ratios, and the re-sort grew longer.

After moving to a core business system with separated output and input tax settings, the change was immediate. The standard 10 percent rate became one tax setting, linked to a sales-tax liability account and a purchase-tax asset account. The reduced 8 percent rate became a second setting, with its own linked accounts. Every sales invoice posted its output tax to the liability side automatically. Every purchase bill posted its input tax to the asset side automatically.

The quarter-end re-sort vanished. The accounting lead pulled two account balances instead of sorting 2 thousand lines. The monthly close dropped from nearly two weeks to a matter of days, and the tax accountant received clean, separated figures on the first request rather than the fifth. The time recovered went back into reconciling vendor statements, the work that actually protects cash.

Why This Matters for Japan

Japan consumption tax is built on this exact split. The amount you remit is your output tax minus your input tax credit, subject to the rules in force. The qualified-invoice system, which began in October 2023, sharpens the input side. Under the transitional measures revised by the 2026 tax reform, the deductible ratio of input tax on purchases steps down over time: 80 percent through September 2026, then 70 percent from October 2026 through September 2028, then lower thresholds until full deduction requires a qualified invoice from October 2031. The old shorthand of a straight 80-to-0 decline by 2029 is out of date.

A core business system that holds output and input in separate, subtype-enforced accounts gives your tax accountant exactly the structure these rules assume. The qualified-invoice registration numbers, yours and each business partner's, are stored on the company and partner records and printed on the invoices. The system structures the data for the credit calculation and the filing, even though it does not file for you. That line is important. The ERP does not submit returns to a government portal and does not perform certified electronic-bookkeeping storage. Your tax accountant owns those steps. What the core business system removes is the manual wreckage that used to feed them.

There is also a timing reason that matters in Japan specifically. The monthly close for many companies still stretches long because the underlying data is unstructured. When tax posts to the right account on day one, the close compresses. Days instead of weeks is the realistic target, and it starts with getting the tax master right at configuration time.

Is This Right for Your Business?

This matters most when you have volume and variety. If your company issues and receives enough invoices that a manual sort is a real cost, separated tax settings pay for themselves in the first close. If you operate across both the standard and reduced rates, the multi-rate structure is not optional, it is the only way to keep the two bases honest.

It matters less if you are very small and file on a simplified basis, though even there the structure costs nothing to have and pays off as you grow. It matters more if you face J-SOX internal controls or an external audit, because auditable tax accounts with a clean trail of journal entries answer questions before they are asked.

The real test is the close. If your finance team is still rebuilding tax totals from a merged account at period end, the problem is the account structure, not the team. A core business system that enforces the separation at write time fixes the root cause.

Frequently Asked Questions

Does the system file my consumption tax return automatically?

No, and it should not. The core business system structures output and input tax into the right accounts and hands your tax accountant clean figures. Filing and certified electronic-bookkeeping storage remain the accountant's responsibility. The value is the separation, not a submission button.

How does the system handle the 10 percent standard rate and the 8 percent reduced rate together?

Each rate is its own tax-setting record, linked to its own sales-tax liability account and purchase-tax asset account. A product or invoice line points to whichever rate applies, and the journal entries post to the correct accounts for that rate. The two bases never contaminate each other.

Can I configure my own chart of accounts, or am I locked to a fixed list?

Each company configures its own accounts with subtypes. The system enforces at write time that a sales-tax account is a liability subtype and a purchase-tax account is an asset subtype, with guardrails that prevent the one misconfiguration that breaks the close. You define the accounts to match how your business is structured.

Will separating output and input tax really shorten my monthly close?

Yes, when the underlying data is unstructured it is the manual re-sort that consumes days every period. When tax posts to the correct liability or asset account on day one, the close compresses to reading two balances instead of rebuilding them. Kikan System enforces that separation at write time, and you can test it free with up to 2 users and no credit card.

Key Takeaway

The cleanest consumption-tax return is the one nobody had to assemble by hand. When output tax lives in a liability account and input tax lives in an asset account from the first entry onward, the return becomes a reading exercise, not a reconstruction project. That structural separation is the difference between a core business system and a ledger that happens to hold tax numbers.

See the Separation in Action

Kikan System enforces output and input tax separation at write time, with multi-rate support, a subtype-validated chart of accounts, and journal entries that post to the right accounts automatically. Start with up to 2 users, no credit card required, and run a close the way it should work.

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

Related reading