Dual Tax Engine for ERP: Japan Consumption Tax and India GST in One Ledger

Two tax worlds, two sets of books, twice the reconciliation

If you run a group with a headquarters in Japan and an entity in India, you already know the tax pain. Your Japan company lives under consumption tax. Your India company lives under GST. Each regime has its own rates, its own invoice rules, and its own output-versus-input logic. And in most finance stacks, that means two disconnected systems doing the same job twice.

The Japan side carries a standard consumption tax rate of 10 percent, split into a 7.8 percent national portion and a 2.2 percent local portion, plus a reduced 8 percent rate on food and newspaper subscriptions. Since October 2023, the qualified invoice system gates your right to claim input tax, so every purchase invoice without a valid registration number quietly erodes your credit. On the India side, GST runs a standard 18 percent for most goods and services after the GST 2.0 consolidation that took effect in September 2025, with a 5 percent band for essentials and a higher band for sin goods.

Two countries. Two rate structures. Two reconciliation cycles. The CFO office ends up consolidating numbers that were never built to speak the same language.

What changes with a configurable tax engine

The fix is not a second tax module bolted onto your ERP. The fix is one configurable tax engine, applied per company, inside a single accounting core.

In a well-built ERP, a tax setting is a small master record. It carries a human-readable name, a rate expressed as a percentage from 0 to 100, and two account links. The first link points to the sales, or output, tax account. The second link points to the purchase, or input, tax account. At the moment you create the setting, the engine checks that the output account is a liability account and that the input account is an asset account. If you point output tax at an asset account by mistake, the write is rejected before it ever touches your books.

That single shape handles both regimes. A Japan company creates a setting named Consumption Tax 10 Percent with a 10 percent rate, a liability account for output sales tax, and an asset account for input purchase tax. An India company in the same group creates a setting named GST 18 Percent with an 18 percent rate, its own liability account for output GST, and its own asset account for input GST. Same engine, same fields, different numbers, fully isolated per company.

The engine also resolves where a tax rate comes from on each line. Priority runs from the most specific to the least specific. A product can carry its own tax setting. If it does not, the product's category is checked, and that check walks up the category tree to any parent. If neither the product nor the category specifies a rate, the company-level default applies. That product-to-category-to-company cascade means a GST-registered SKU in India picks up 18 percent automatically while a reduced-rate food SKU in Japan picks up 8 percent without anyone re-keying a number.

A real-world scenario for a Japan-plus-India group

Picture a group with its parent company in Tokyo and a wholly owned subsidiary in Bengaluru. The parent bills domestic customers 12 million yen a month for software implementation services. The subsidiary bills domestic customers 5 crore rupees a quarter for the same services delivered on the ground in India.

In the Japan company, the team configures a Consumption Tax 10 Percent setting. Output tax posts to a liability account called Provisional Consumption Tax Payable. Input tax posts to an asset account called Provisional Consumption Tax Receivable. When a 12 million yen invoice goes out, the engine splits it into 10,909,090 yen of revenue and 1,090,910 yen of output tax, and it credits the liability account in the same journal entry. Purchases follow the same logic in reverse, debiting the input tax asset account line by line.

In the India company, the team configures a GST 18 Percent setting. Output GST posts to a liability account called Output GST Payable. Input GST posts to an asset account called Input GST, or ITC, Receivable. A 5 crore rupee invoice splits into 4.237 crore rupees of revenue and 76.27 million rupees of output GST. Vendor bills feed the input side the same way, building the input tax credit balance that the India team will reconcile against their GST return.

None of this requires two products. It requires one engine, two tax settings, two sets of accounts, and the per-company isolation that keeps the Tokyo ledger and the Bengaluru ledger from ever contaminating each other. At month end, the group CFO reads both sets of output and input balances from the same chart of accounts framework, in the same report, and moves on.

Why this matters for Japan consumption tax and India GST

The qualified invoice system in Japan made output and input separation non-negotiable. You cannot claim input consumption tax credit on a purchase unless the supplier invoice carries a qualified-invoice registration number, and you cannot prove your output-versus-input position at year end if output tax and input tax are lumped into a single suspense account. A configurable engine forces the separation at the field level. Every tax setting has a distinct output account and a distinct input account from the moment it is created.

India GST demands the same discipline from the other direction. The input tax credit is the lifeblood of GST compliance, and the GST return reconciliation compares your input claim against what your suppliers reported. When input GST lands in a dedicated asset account on every bill journal entry, you have a clean, auditable balance to match against the tax authority's data.

One ledger per company. One tax engine shape. Two regulatory regimes handled without duplication.

Is this right for your business?

This approach fits groups that have at least two entities operating under different indirect-tax regimes, and a finance team tired of stitching together reconciliation spreadsheets. If your Japan entity and your India entity both transact enough volume that manual tax reclassification eats days at every close, a single configurable engine pays for itself in the first quarter.

It is also a fit for groups preparing to add a third jurisdiction. Because the engine is configurable rather than country-hardcoded, onboarding a Singapore entity with a 9 percent GST rate later is a matter of creating one more tax setting, not buying a localization package.

Frequently asked questions

Is this two separate tax engines running side by side?

No. It is one configurable tax engine applied per company. Each company creates its own tax settings with its own rates and its own output and input accounts. The engine shape is identical across companies, but the numbers and the accounts are isolated.

Does the system calculate the reduced 8 percent rate automatically?

The engine applies whatever rate you put in a tax setting, from 0 to 100. If you create a setting named Consumption Tax 8 Percent Reduced and attach it to the relevant products or categories, that rate resolves automatically on those lines. The standard-versus-reduced decision is yours to configure at the product or category level.

Can I see output tax and input tax as separate balances?

Yes. Because every tax setting links a distinct sales, or output, liability account and a distinct purchase, or input, asset account, your output tax and input tax always land in separate accounts and appear as separate balances in every report.

Key takeaway

You do not need a dual tax engine. You need one configurable tax engine, applied per company, that separates output and input tax at the field level. That is how a Japan-plus-India group runs consumption tax and GST in a single ERP without doubling its reconciliation workload.

Stop running two tax stacks

Kikan System ships a single configurable tax engine that handles Japan consumption tax and India GST in one ledger. Each company defines its own tax name, its own rate, and its own output and input accounts, and the engine validates the account types at write time so output tax never lands in an asset account. Sales journal entries post to your output tax liability account, and bill journal entries post to your input tax asset account, line by line. Start on the free plan for up to 2 users, no credit card required, at /#get-started.

If you want to go deeper, read how data isolation protects each company's books, see a multi-entity unification case study, or review the GST-ready ERP checklist for India. For Japan-specific depth, start with separating output and input tax settings and qualified invoice registration number management.