B2B Software Consulting in Tokyo
Tokyo ledgers are specified by statute, not by preference: qualified invoice registration numbers since October 2023, and Electronic Books Preservation Act retention with non-alterability and date, amount and counterparty search since January 2024. ERPStack is remote-first and builds those rules into PostgreSQL schemas deployed to AWS ap-northeast-1.
Quick Answer
In short: a Tokyo ERP has to carry qualified invoice registration numbers, split 8% and 10% consumption tax, and retain electronic transactions under the Electronic Books Preservation Act. ERPStack builds it on PostgreSQL in AWS ap-northeast-1, four Availability Zones, with Osaka ap-northeast-3 for recovery and FISC-mapped access controls.
Regional Compliance
- Act on the Protection of Personal Information (APPI), PPC-supervised
- Electronic Books Preservation Act (電子帳簿保存法) — electronic transaction retention
- Qualified Invoice System (適格請求書等保存方式) — JCT input tax credit
- FISC Security Guidelines, 13th Edition (November 2025)
- ISMAP Cloud Service List for government procurement
- ISO 27001 and SOC 2 controls mapped onto FISC guideline references
Security & Compliance Architecture
Japanese law hands a Tokyo team something rare: a literal database specification. The Electronic Books Preservation Act names the search keys, the non-alterability requirement and the retention clock; ERPStack turns each clause into PostgreSQL structure.
Three search keys, plus range and combination
Electronic transaction records must be searchable by transaction date, amount and counterparty; by date or amount range; and by two or more keys at once, then exported on demand in an audit. ERPStack indexes those three PostgreSQL columns explicitly and ships the export as a REST API, so a Tokyo controller is never assembling evidence by hand.Non-alterability without buying a timestamp service
The Act accepts a timestamp before or immediately after exchange, a system that records or prevents correction and deletion, or documented procedures. ERPStack takes the third: an append-only PostgreSQL journal, an immutable audit trail and RBAC on the correction path, so a fix is a new row. Failed preservation puts a Tokyo filer’s blue-form status, and its loss carryforward, at risk.APPI after 17 July 2026
The amended Act on the Protection of Personal Information was promulgated on 17 July 2026 and gives Japan its first administrative surcharges: excluded below 1,000 affected individuals, multiplied by 1.5 for a repeat within 10 years, halved on voluntary self-report. Unlike GDPR, the amount tracks the gain, not turnover. Consent-based transfer abroad still obliges a Tokyo controller to name the destination regime, which is why ERPStack keeps the primary in AWS Tokyo.My Number, payroll and the sector auditors
The 12-digit Individual Number sits in its own schema behind RBAC with its own disposal job, because the My Number Act limits use to payroll, withholding and social insurance. Beside it sit welfare pension at 9.15% up to ¥650,000 monthly and the 720-hour annual overtime ceiling. Tokyo finance buyers audit against the FISC Security Guidelines, 13th Edition; government buyers procure from the ISMAP list; ERPStack maps both onto ISO 27001 and SOC 2 controls implemented at schema level.
Engineering Blueprint
Two dated statutes set the shape of a Tokyo ERP: the Qualified Invoice System (適格請求書等保存方式), live since 1 October 2023, and the Electronic Books Preservation Act (電子帳簿保存法), mandatory for electronic transactions since 1 January 2024. ERPStack builds that ledger in PostgreSQL with Drizzle ORM, Next.js and TypeScript, and deploys it to AWS ap-northeast-1 (Tokyo) across four Availability Zones, with the disaster-recovery replica in ap-northeast-3 (Osaka).
The invoice ledger Japanese tax law specifies
A qualified invoice carries the issuer registration number — T plus 13 digits — and consumption tax split by rate: 10% standard (7.8% national, 2.2% local) and 8% reduced (6.24%, 1.76%) on food, non-alcoholic drinks and newspapers. ERPStack puts the rate on the PostgreSQL line, not the header, so a Tokyo retail or logistics order of mixed goods emits one compliant document, and a sogo shosha uses multi-tenant architecture per legal entity because each files its own return. The transitional input credit for unregistered suppliers is a dated rule, not a constant: 80% until 30 September 2026, 50% until 30 September 2029, nil after. SAP S/4HANA and Oracle NetSuite localise this; a custom ERP earns its place around them.
// Drizzle ORM + PostgreSQL — Tokyo ERP qualified-invoice line
export const invoiceLine = pgTable('invoice_line', {
issuerRegNo: varchar('issuer_reg_no'), // T + 13 digits
taxRate: numeric('tax_rate'), // 10.00 | 8.00, per line
counterparty: varchar('counterparty').notNull(),
txnDate: date('txn_date').notNull(),
});JP PINT is the wire, PostgreSQL is the record
Japan’s Digital Agency has been the Peppol Authority since September 2021, and JP PINT reached Ver. 1.1.3 on 8 June 2026. ERPStack keeps Peppol at the edge — a REST and webhook boundary that maps JP PINT onto the internal PostgreSQL schema, validated with Zod — so a Tokyo finance team is never blocked by a specification bump. Terraform and GitHub Actions ship the stack; Sentry and OpenTelemetry Observability watch the exchange.
Migrating off the 2025 digital cliff
METI priced Japan’s legacy estate at up to 12 trillion yen a year after 2025, and its Legacy Systems Modernization Committee reported again on 28 May 2025. For Tokyo manufacturing groups running twenty-year-old cores, ERPStack uses the strangler fig migration pattern: a Next.js and React surface first, then an API read model in PostgreSQL, then module-by-module cutover. Technical debt retires without a big-bang go-live, and the cloud migration lands in ap-northeast-1 — or Microsoft Azure Japan East if the Tokyo group is already committed there.
Evaluate Your Stack
Take our interactive audit to see if your architecture is ready for operational scale.
Start Free AuditRegional Infrastructure
Infrastructure Region
Latency Metrics
Primary Datacenter
Success Stories in Tokyo
Artisan Manufacturing ERP
Supply chain and production system for artisan manufacturing
Read Case StudyTarget Industries in Tokyo
Frequently Asked Questions
No. Since 1 January 2024 electronic transaction data reaching a Tokyo entity — PDF invoices on email, cloud receipts, EDI messages — must be preserved as data under the Electronic Books Preservation Act. ERPStack stores them in PostgreSQL with the statutory index and an export API, because failed preservation puts blue-form status and loss carryforward at risk.
The rate belongs on the line, never the header. For Tokyo retail and logistics clients ERPStack stores the consumption tax rate per PostgreSQL line — 10% standard, or 8% reduced on food, non-alcoholic drinks and qualifying newspapers — then totals tax by rate on the qualified invoice, which is exactly what the document has to show.
Usually extend first. Bugyo and HUE already carry Japanese consumption tax logic, and OBC reported 820,000 cumulative registrations by August 2025. For most Tokyo manufacturing groups ERPStack builds a custom ERP layer for supply chain, quality and cost data and integrates back over REST, rather than ripping out a working ledger.
Legally often yes; commercially, rarely. APPI permits cross-border transfer on consent, but a Tokyo business must first tell data subjects about the destination country's protection regime. Regulated buyers citing the FISC Security Guidelines or the ISMAP list expect ap-northeast-1, so ERPStack defaults to AWS Tokyo and treats offshore hosting as the exception.
Three keys: transaction date, transaction amount and counterparty. A Tokyo system must also support range search on date or amount, combined search on two or more keys at once, and export on demand during a tax audit. ERPStack indexes those three columns in PostgreSQL and ships the audit export as a REST API.
Seven years from the day after the corporate tax return deadline, extending to ten years for any year in which a blue-form loss carryforward arose — nine years for years beginning before 1 April 2018. ERPStack partitions Tokyo ledgers by fiscal year in PostgreSQL and archives sealed partitions to AWS object storage.
Japan gained administrative monetary penalties for the first time. The bill passed the Diet on 10 July 2026 and was promulgated on 17 July 2026, after the PPC's triennial-review reform policy of 9 January 2026. Cases below 1,000 affected individuals are excluded; a repeat within 10 years carries a 1.5 multiplier. ERPStack plans Tokyo ERP rollouts for enforcement by 2028.
Promptly — PPC guidance points at roughly three to five days — with a full report within 30 days, or 60 days where the breach was likely committed for an unlawful purpose. ERPStack instruments Tokyo deployments with Sentry and an immutable audit trail in PostgreSQL, so the 30-day clock starts with evidence rather than guesswork.
If the Tokyo entity consolidates into a parent already running SAP S/4HANA, take the group template and build only the Japan-specific edges. If it does not, SAP S/4HANA is usually over-scaled inside the ¥3 billion to ¥100 billion band Fujitsu built GLOVIA One for in April 2026, and a custom ERP on PostgreSQL competes honestly there.