
Free TISAX audit checklist in Word and PDF: assessment levels, labels, VDA ISA areas and the evidence to prepare, plus an Excel self-assessment tracker.
What J-SOX is, how it differs from US SOX, and a checklist of J-SOX requirements from scoping to the internal control report.


Content writer, trio.so
J-SOX is the nickname for Japan's internal control reporting system under the Financial Instruments and Exchange Act (FIEA). It requires listed companies to assess their internal control over financial reporting (ICFR) every year, file an internal control report with their annual securities report, and have an independent auditor audit that assessment. The rules apply to fiscal years beginning on or after 1 April 2008, and the current version of the standards, revised in April 2023, applies from fiscal years beginning on or after 1 April 2024.
Get the J-SOX checklist: every requirement area from scoping to the internal control report, with a tracker for controls, evidence and deficiencies.
J-SOX stands for "Japanese Sarbanes-Oxley". The statute does not use that name. It calls the system the internal control reporting system (内部統制報告制度), and the nickname comes from the big accounting firms. The framework is set by the Business Accounting Council, an advisory body to Japan's Financial Services Agency (FSA), in its Standards and Practice Standards for Management Assessment and Audit concerning Internal Control Over Financial Reporting. The council set the first version in 2007, revised it in 2011, and published a major revision on 7 April 2023.
The framework defines internal control as a process, carried out by everyone in the organization, that gives reasonable assurance on four objectives:
It has six basic components: control environment, risk assessment and response, control activities, information and communication, monitoring, and response to IT. The system itself is about financial reporting only.
What changed in the 2023 revision, in short:
Source: the FSA's 7 April 2023 release and its English weekly review. The FSA publishes the 2023 standards only in Japanese. English labels in this post are our own, aligned with the FSA's English translations of the earlier versions, which the FSA offers for reference only.
| Point | J-SOX (Japan) | US SOX Section 404 |
|---|---|---|
| Approach | Top-down and risk-based: company-level controls first, then processes. | Also top-down and risk-based. |
| Auditor's role | Audits management's assessment. There is no direct reporting by the auditor on control effectiveness. | The auditor gives its own opinion on the effectiveness of internal control over financial reporting. |
| Who audits | The same auditor (firm and engagement partners) as the financial statement audit. | An integrated audit by the same firm. |
| Audit report | In principle combined with the financial statement audit report. | Can be combined or separate. |
| Deficiency classes | Two: deficiency and material deficiency. | Three: deficiency, significant deficiency and material weakness. |
| Objectives and components | 4 objectives (adds safeguarding of assets) and 6 components (adds response to IT). | COSO 2013 uses 3 objectives and 5 components. |
| Small companies | No size exemption. Newly listed companies skip the auditor's audit for the first 3 years but still file the management report. | Non-accelerated filers are exempt from the auditor attestation, but management's report is still required. |
The US column rests on the SEC's rules and general knowledge, not the Japanese sources, so confirm US details with a US advisor.
If you are a Japanese subsidiary of a listed parent, the group's scope decision usually determines whether your site is in scope. Ask group finance or internal audit before you build anything.
Management assesses company-level controls first, then process-level controls in light of the result. In principle company-level controls are assessed for all locations, except immaterial ones.
The IT component has two parts: responding to the IT environment, and using and controlling IT through IT general controls and IT application controls. The standards give four examples of IT general controls:
Access and system security. Write an access management policy for the systems used in financial reporting. The standards name internal and external access management as part of system security. Typical controls that support these items, not J-SOX requirements: grant, change and remove access on approval, review access rights periodically, restrict privileged access and log its use, and secure the devices that reach financial systems. If a company device used for financial work is lost, lock it, wipe it if the company owns it, and record what you did.
Development, maintenance and change. The standards name control over data migration to a new system and user training. Typical controls that support these items, not J-SOX requirements: approve, test and document changes before they go live, and control which software and versions run on finance devices.
Operations and backup. The standards name backup for fast recovery, and analysis and resolution of incidents. Typical controls that support these items, not J-SOX requirements: schedule and monitor the batch jobs and interfaces that feed the general ledger, and keep an up-to-date list of the systems in use and the devices that run financial software.
Outsourcing. List outsourced work that is part of significant processes and keep it in scope. Manage outsourcing contracts. Either test samples of the provider's output, or use the provider's service organization controls report (JICPA Assurance Practice Guideline 3402, the Japanese standard comparable to ISAE 3402 and SOC 1). In practice, check the period the report covers against your fiscal year, and run the controls it expects you to run yourself.
What J-SOX does not say. The 2023 standards contain no password rules, patch deadlines, encryption requirements, device or backup frequency settings. J-SOX expects controls over system access and security. The specific settings are your company's choice, and many companies draw on frameworks such as ISO 27001 or NIST for them. If someone tells you "J-SOX requires MFA" or "J-SOX requires 90-day passwords", ask for the source.
On the device side, controls such as screen lock, disk encryption and current OS versions support the access and security items, and trio.so exports compliance evidence for the devices it manages. That covers device basics only. The internal control report is management's own assessment, and no tool makes a company J-SOX compliant.
IT application controls are the checks built into financial applications, and they can be manual too. The standards give input completeness, accuracy and validity, correcting and reprocessing errors, master data maintenance, and authentication with limits on what each user can do. In practice:
The financial closing and reporting process, from general ledger to financial statements, consolidation entries and disclosure preparation, is assessed company-wide, like company-level controls. Process-level controls cover the business processes in scope.
Most companies prepare three documents per significant process. The standards present them as samples, to be prepared as needed. Companies do not have to use these formats and can use documents they already have. The Japanese practitioner nickname "three-piece set" (三点セット) is not a term in the standards.
| Document | FSA English name | What it shows |
|---|---|---|
| Flow chart | Business process flowchart (sample) | The steps of a process, who does what, and the systems involved. |
| Process description | Business process description (sample) | A written narrative of the same process. |
| Risk control matrix (RCM) | Relationship between risks and controls (sample) | Each risk, the control that addresses it and the assertion it supports. |
The Practice Standards also list what to keep as records: policies and procedures, the status of each company-level item, an outline of each significant process including system flows, application controls and a list of systems in use, the risks and controls, test evidence, and deficiencies and fixes. Keep J-SOX records for about as long as the annual securities report is open to public inspection (5 years). The Practice Standards use that as the reference point. The retention period is the company's own call.
The report. The internal control report has five sections: (1) the basic framework of ICFR; (2) scope, assessment date and procedures; (3) the assessment result; (4) additional notes; (5) special notes. Management typically concludes one of three things: ICFR is effective; it is effective except that some procedures could not be performed (with reasons); or a material deficiency exists, so ICFR is not effective (with details). The 2023 revision added two requirements: explain why the scope was set as it was, and, if a material deficiency was reported the year before, state its remediation status in the additional notes.
The audit. The auditor audits management's assessment. The ICFR audit report is in principle combined with the financial statement audit report. If the report discloses a material deficiency, the auditor's report states its effect on the financial statement audit.
Timeline. Management assesses ICFR as of the fiscal year-end. The annual securities report is due within 3 months of year-end, and the internal control report is filed together with it. For a March year-end company, that means the end of June. The revised standards first applied to fiscal years beginning on or after 1 April 2024, so the first reports under them covered the year ending March 2025.
Penalties. Filing an internal control report with a false statement on a material matter, or not filing one, carries up to 5 years' imprisonment and/or a fine of up to JPY 5 million for individuals, and a fine of up to JPY 500 million for the company (FIEA Articles 197-2 and 207).
Get the J-SOX checklist: every requirement area from scoping to the internal control report, with a tracker for controls, evidence and deficiencies.
Related reading: types of compliance, SOX compliance and IT compliance.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.





Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.
Related
The related industry news, interviews, technologies, and resources.

Free TISAX audit checklist in Word and PDF: assessment levels, labels, VDA ISA areas and the evidence to prepare, plus an Excel self-assessment tracker.

Learn how you can improve your resource allocation strategy & download the IT Resource Allocation Template to optimize your IT resource management.

Free IT audit checklist template in Excel, PDF and Word: 66 checks in 8 areas, an audit questionnaire, a findings tracker and a filled-in example.

Free IT contingency plan template in Word and Excel, with a filled-in example: BIA with MTD, RTO and RPO, call tree, recovery steps and test forms.

Free SDLC policy template with security work for every phase, release gates, a checklist, sign-off form, framework mapping and an Excel tracker.

Free NIS2 checklist in Excel, PDF and Word: check who is in scope, work through the ten Article 21 measures, supplier security and 24h/72h reporting.

Learn how to create a comprehensive Request for Information (RFI) template tailored for IT admins.

A server hardening checklist template for Windows and Linux with verification commands, plus a free Excel tracker, Word checklist and policy template.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients