Group ERP vs Local Accounting Software for the Japan Entity: The Bridge Model That Works

The group ERP versus local accounting software question, for a Japan subsidiary, is the decision about where the entity's statutory ledger lives: inside the group's enterprise resource planning (ERP) system, configured for Japan, or in Japanese accounting software that feeds the group system each month. The answer determines who can maintain the books, how Japanese consumption tax and invoice rules are handled, where electronic records are stored, and how numbers reach the consolidation. For most subsidiaries of 5 to 50 people, the workable answer is a bridge model: Japanese software for the statutory books, a mapped trial balance into the group system, and a short list of controls that make the two reconcile. This guide covers what the Japan books must do, how the bridge works and is controlled, and when to bring Japan into the group ERP.

Key Takeaways

• The choice is about the statutory ledger, not the reporting. Headquarters gets group-format numbers either way. The real question is which system holds the books the Japanese tax return is built on, and who can maintain them.
• Japanese tax rules shape the ledger. Qualified invoices carry six required items, including the issuer's registration number, and the ledger must record transactions by consumption tax rate, at 10% or the reduced 8%.
• The bridge model keeps local work local. Japanese software handles tax codes, invoice data, and filing formats; a mapped trial balance carries the results into the group ERP each month.
• The mapping table is the control point. Headquarters should own the mapping from local accounts to the group chart of accounts, and every change to it should be approved and logged.
• Change the model on triggers, not instinct. Shared processes with other entities, real-time visibility needs, or growth past what a monthly upload can carry are the signals to bring Japan into the group ERP.

What the Japan Statutory Ledger Has to Do

A Japan subsidiary's ledger must support consumption tax by rate, qualified invoice data, electronic record retention, and Japanese tax filing.

Whatever system holds the books, the Japanese statutory ledger carries requirements that most group ERPs do not meet without configuration. Consumption tax applies at a standard 10% and a reduced 8%, with a national and a local portion inside each rate, as the National Tax Agency's consumption tax overview sets out. Since October 2023, input tax credits depend on the qualified invoice system (適格請求書等保存方式, tekikaku seikyusho to hozon hoshiki). According to the National Tax Agency's English invoice system instructions, revised in April 2026, a qualified invoice must show six items, from the issuer's name and registration number to the consumption tax amount by rate, and buyers must in principle retain both the qualified invoices and a ledger containing prescribed descriptions to claim the credit. Purchases from suppliers who are not registered issuers are, as a general rule, not eligible for the credit, with transitional relief that steps down through 2031.

Two further requirements sit outside the tax return itself. Electronic transaction data, such as invoices and receipts sent or received electronically, must be retained in electronic form under the Act on Retention of Ledgers through Electronic Methods (電子帳簿保存法, denshi chobo hozon ho). And the corporate tax return, due 2 months after the fiscal year-end, is prepared from the statutory books by a licensed zeirishi (税理士, certified tax accountant), who will usually work in Japanese software. The table below sets out how each requirement plays out in the two models.

Requirement	What the Japan books must do	Bridge model	Group ERP localised for Japan
Consumption tax by rate	Code every taxable transaction at 10% or 8%, with national and local portions	Built into Japanese software	Configure and test tax codes and the return worksheet
Qualified invoices issued	Show the six required items, including the registration number	Invoice templates provided by the software	Customise invoice output and test against the six items
Qualified invoices received	Record whether each supplier is a registered issuer	Supplier registration fields and checks in the software	Add supplier registration data and credit logic
Electronic records	Retain electronic transaction data in electronic form, searchable	Software or linked storage designed for Japanese rules	Confirm document storage meets the Japanese requirements
Corporate tax return	Produce statements and schedules the zeirishi files from	Zeirishi works directly in the software	Export to the zeirishi's tax software each year
Group reporting	Deliver results on the group chart of accounts	Mapped trial balance loaded monthly	Native, no upload needed
Payroll postings	Book salaries, social insurance, and withholding	Japanese payroll software posts journals locally	Interface from Japanese payroll software into the ERP
Maintenance	Keep up with Japanese rule changes	Software vendor updates	Group IT or the ERP partner updates the localisation

How the Bridge Model Works for a Japan Subsidiary

In the bridge model, Japanese software keeps the statutory books and a mapped trial balance carries results into the group ERP each month.

The bridge model separates two jobs that a single system would otherwise have to do at once. The statutory ledger runs on Japanese accounting software, such as freee, Money Forward, or Yayoi, which the provider and the zeirishi use daily and which handles Japanese tax codes, invoice fields, and filing outputs as standard. At each month-end, the provider exports a trial balance, applies the mapping from local accounts to the group chart of accounts, and loads the result into the group ERP or consolidation tool. Any adjustments that exist only for group reporting are posted on the group side, so the statutory ledger stays clean for the tax return.

The model works because the Japan entity is small relative to the group. A subsidiary of 5 to 50 people generates a manageable number of transactions, its statutory year can match the group year, and its intercompany flows are usually limited to a few recurring charges. The monthly upload then carries everything headquarters needs to consolidate. A fuller view of how the subsidiary's books feed group reporting is in the group CFO's guide to Japan subsidiary finance, and a comparison of the software options themselves is in global versus domestic accounting software in Japan.

Controls That Make the Bridge Model Reliable

The bridge model is reliable when headquarters owns the mapping, reconciles each upload, and controls access to both the local and group systems.

A bridge between two systems introduces one new risk: the two sets of numbers can drift apart. Five controls keep them aligned.

• Mapping ownership. Headquarters owns the table that maps local accounts to the group chart of accounts. The provider proposes changes when new accounts are opened; headquarters approves them before the next upload.
• Upload reconciliation. Each month, total assets, total liabilities, and net income in the group ERP are compared with the local trial balance, and any difference is explained before the close is signed off.
• Unmapped account check. The upload template rejects or flags any local account without a mapping, so new accounts cannot reach the group system unclassified.
• System access. Headquarters holds administrator rights in the Japanese software as well as the ERP, and removes users when people leave the provider.
• Change log. Changes to mapping, tax codes, and posting rules are recorded with the date and approver, which also supports the group auditor's review.

Close speed is a useful health check for the whole arrangement. APQC benchmark data reported by CFO.com, drawn from about 2,300 organizations, put the median monthly close at 6.4 calendar days, with top-quartile companies at 4.8 days or less. A bridge that adds days to the group close, rather than fitting inside it, usually points to manual re-keying or an unstable mapping rather than to the model itself.

When to Bring the Japan Entity Into the Group ERP

Bring a Japan subsidiary into the group ERP when it shares processes with other entities, needs real-time data, or outgrows a monthly upload.

The bridge model is a stage, not a permanent answer. The signals that it is time to move are operational rather than size thresholds, and they usually arrive together.

Trigger	What it looks like	Why the bridge struggles
Shared procurement or billing	Japan buys or invoices through group-wide processes	Transactions start in the ERP and must be re-entered locally
Real-time visibility	Headquarters needs Japan data during the month, not after the close	A monthly upload cannot provide intra-month data
Transaction volume	Upload preparation and reconciliation become a significant monthly task	Manual effort and error risk grow with each upload
Inventory or project accounting	Japan holds stock or runs projects tracked in group modules	Subledgers in two systems are hard to keep aligned
Regional hub role	Japan begins serving other entities in the region	Intercompany volume and eliminations outgrow a trial balance feed
Group audit or SOX scope	Japan becomes in scope for detailed control testing	Controls must be evidenced in one auditable system

Moving to the ERP does not remove the Japanese requirements; it moves them into the group system. A Japan localisation should be tested against each row of the requirements table before go-live, including a full consumption tax return worksheet and a sample of qualified invoices. A practical safeguard is to keep the Japanese software running in parallel for the first fiscal year, so the zeirishi can prepare the return from familiar outputs. Statutory filing obligations are unchanged either way; the Japanese filing platforms are explained in Japan's digital tax filing platforms.

Why Digital Records Make the Choice Matter More

Japan is pushing invoices, ledgers, and returns toward end-to-end digital processing, which raises the cost of a ledger that cannot link them.

The National Tax Agency's 2025 report on digital transformation for tax administration describes a policy of "digital seamless" processing, in which invoices are exchanged digitally, including through the Peppol e-invoicing standard, and the resulting data flows into accounting software, journals, and the tax return without manual re-entry. The same report notes that the FY2025 tax reform revised the electronic records act to reduce penalty exposure where electronic transaction data are retained without modification and recorded through data linkage in the accounting software. For a Japan subsidiary, that direction favours a statutory ledger that connects natively to Japanese e-invoicing and bank data. In the bridge model, that is the local software's job; in the ERP model, it becomes a requirement for the localisation. Qualified invoice handling in local software is covered in the qualified invoice system and your accounting software.

Frequently Asked Questions

Can a Japan subsidiary keep its statutory books in the group ERP?

Yes, if the ERP is configured for Japanese consumption tax, qualified invoice data, electronic record retention, and the outputs the zeirishi needs for the corporate tax return. The configuration and its ongoing maintenance are the cost. Smaller subsidiaries usually keep the statutory books in Japanese software and send a mapped trial balance to the ERP instead.

Who should own the chart of accounts mapping?

Headquarters. The provider maintains the local chart of accounts and proposes mapping changes when accounts are added, but group finance approves each change before the next upload. Ownership at headquarters keeps the group numbers consistent across entities and gives the group auditor a single point of control to test.

Does the bridge model affect the Japanese tax return?

No. The tax return is prepared from the statutory books in the Japanese software, and the group-only adjustments are posted in the group system, so the return is unaffected. The model actually protects the return, because group reporting adjustments never enter the statutory ledger.

Working with AQ Partners. Our Tokyo team provides accounting software setup and monthly bookkeeping for foreign companies operating in Japan, including the chart of accounts mapping that feeds group reporting. Book a consultation to discuss your Japan systems setup.