trio.so
Templates

J-SOX Compliance Requirements: What It Is and a Checklist

What J-SOX is, how it differs from US SOX, and a checklist of J-SOX requirements from scoping to the internal control report.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

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.

What is J-SOX?

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:

  1. effectiveness and efficiency of operations;
  2. reliability of reporting (the 2023 wording; it used to say "financial reporting");
  3. compliance with laws and regulations relevant to business activities;
  4. safeguarding of assets.

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:

  • Risk assessment must consider fraud risk.
  • The IT component stresses controls over outsourced IT and information system security, with cyber risk, cloud and remote access named.
  • It gives examples of controls against management override, including override by process owners and not only top management.
  • Scoping indicators such as "about two-thirds of sales" and the three accounts of sales, receivables and inventory stay as examples, but must not be applied mechanically.
  • The internal control report must explain why the scope was set as it was.

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.

J-SOX vs US SOX

PointJ-SOX (Japan)US SOX Section 404
ApproachTop-down and risk-based: company-level controls first, then processes.Also top-down and risk-based.
Auditor's roleAudits 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 auditsThe same auditor (firm and engagement partners) as the financial statement audit.An integrated audit by the same firm.
Audit reportIn principle combined with the financial statement audit report.Can be combined or separate.
Deficiency classesTwo: deficiency and material deficiency.Three: deficiency, significant deficiency and material weakness.
Objectives and components4 objectives (adds safeguarding of assets) and 6 components (adds response to IT).COSO 2013 uses 3 objectives and 5 components.
Small companiesNo 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.

Who J-SOX applies to

  • Listed companies. Under FIEA Article 24-4-4, companies that must file an annual securities report and have securities listed on an exchange must assess ICFR every fiscal year and file an internal control report together with the annual securities report. Other annual report filers may file one voluntarily.
  • The whole group. The assessment covers the corporate group and the company. Subsidiaries and overseas sites can become part of the scope as significant locations.
  • Auditor attestation. A listed company's report must be audited by a CPA or audit firm with no special interest in the company (FIEA Article 193-2).
  • Newly listed companies. The auditor's audit is not required for filings made until 3 years after the company first became a listed issuer. The management report is still filed. The relief is not available if share capital was JPY 10 billion or more, or total liabilities JPY 100 billion or more, in the fiscal year before listing.
  • No small-company exemption. We found no general size threshold that removes the management report for a listed company.

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.

Scoping and planning

  1. Confirm the company must file an internal control report and whether the new-listing auditor relief applies.
  2. Set the fiscal year-end as the assessment date. Plan the timeline so the report can be filed with the annual securities report within 3 months of year-end.
  3. Choose significant locations using a risk-based indicator such as consolidated sales. "About two-thirds of sales" is an example in the Practice Standards, not a rule. Record why you chose the indicator and the percentage.
  4. At significant locations, include the processes that lead to the accounts most closely tied to the business. Sales, receivables and inventory are the usual example, but do not apply them mechanically.
  5. Add high-risk processes individually: risky transactions, significant estimates and management forecasts, and non-routine transactions.
  6. Review locations and processes that have been out of scope for a long time and decide whether to bring them in.
  7. If a material deficiency turns up outside your scope, bring that location or process into scope at least for the period in which it was found.
  8. Discuss the scope with the external auditor at the planning stage and again when circumstances change. Scope is management's decision, and the auditor stays independent.
  9. Identify the IT systems that support in-scope processes (ERP, accounting, consolidation, banking) and the devices and users that reach them.

Company-level controls

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.

  • Cover all six components: control environment, risk assessment and response, control activities, information and communication, monitoring, and response to IT.
  • Use the example assessment items in the Practice Standards (Exhibit 1) as a starting list and document how each is designed and operating.
  • Include fraud risk in the risk assessment.
  • Put controls in place against management override at company level and in processes, and consider override by process owners.
  • Give the board, audit and supervisory board members, and internal audit clear roles. Internal audit should be able to report to the board and the audit and supervisory board.
  • Set an IT policy that responds to your IT environment, including cloud, remote access and cyber risk.
  • Protect company assets (objective 4), including the IT equipment used for financial work.

IT general controls (ITGC)

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:

  1. system development and maintenance;
  2. system operation and management;
  3. system security, including internal and external access management;
  4. management of contracts for outsourced work.

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.

Application controls

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:

  • Check that input is complete, accurate and valid (edit checks, matching, approvals).
  • Correct and reprocess errors and exceptions in a controlled way.
  • Control master data changes: customers, vendors, prices, bank details.
  • Authenticate users in the application and limit what each can do, with segregation of duties.
  • Do not over-rely on automated controls. Watch for electronic records that can change without leaving a trace.

Financial closing and process-level controls

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.

  • Assess the closing process across the company.
  • Map each in-scope process from start to recording.
  • Identify the risks of misstatement in each process and the key controls that reduce them, against the financial statement assertions: existence, completeness, rights and obligations, valuation, period allocation and presentation.
  • Test the design and the operation of key controls.
  • Reassess controls that changed during the year.

The three documents: flow chart, process description and risk control matrix

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.

DocumentFSA English nameWhat it shows
Flow chartBusiness process flowchart (sample)The steps of a process, who does what, and the systems involved.
Process descriptionBusiness 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.

Testing, deficiencies and remediation

  • Assess design and operation. For each key control, check that it is designed well and that it ran as designed. The assessment date is the fiscal year-end.
  • Reuse of testing. For company-level items and IT general controls that were effective last year and have not changed in design, management may record that fact and reuse last year's operating test results, so testing can happen once every few years. Use careful judgment. The standards say not to apply a fixed number of years mechanically.
  • Two classes of deficiency. J-SOX has deficiencies and material deficiencies. (In English you also see "material weakness" for the Japanese term.) A material deficiency is one with a high likelihood of causing a misstatement above a set amount, or a qualitatively material misstatement. Judge both quantitative and qualitative materiality, in principle at consolidated level.
  • Example materiality. The Practice Standards give about 5% of consolidated pre-tax income as an example level for judging a material deficiency. It is an example of materiality, not a scoping threshold.
  • Fix before year-end. If a material deficiency is remediated by the year-end assessment date, management can conclude that ICFR is effective. Fixes made after year-end are described in the report's additional notes.
  • Track everything. Keep a record of each deficiency, who owns the fix, the evidence it was fixed and when it was retested.

The internal control report and timeline

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).

J-SOX compliance checklist (summary)

  1. Scope and planning: confirm filing duty, set the assessment date, choose significant locations and processes with a recorded rationale, add high-risk processes, review long-excluded areas, discuss scope with the auditor.
  2. Company-level controls: assess all six components, document design and operation, cover fraud risk and management override, define board and internal audit roles.
  3. IT general controls: access policy and reviews, privileged access, secure devices, remote access, change control, data migration, backup and restore, incident handling, outsourcing and service organization reports.
  4. Application controls: input checks, error handling, master data, user authentication and segregation of duties.
  5. Financial closing: company-wide closing controls, journal entry review, estimates.
  6. Process controls: map each process, identify risks and key controls, test design and operation.
  7. Documents: flow chart, process description and risk control matrix per significant process (or your equivalent), plus records of scope and testing.
  8. Deficiencies: evaluate, fix before year-end where possible, retest and track.
  9. Report and timeline: draft the report with the scope rationale and remediation status, agree timing with the auditor, file with the annual securities report.

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.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

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.

14-day free trial. No credit card required.

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.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

J-SOX compliance means a listed company in Japan assesses its internal control over financial reporting each year, files an internal control report with its annual securities report, and has an independent auditor audit that assessment.

It is short for "Japanese Sarbanes-Oxley". The official name is the internal control reporting system under the Financial Instruments and Exchange Act.

It is the independent audit of management's assessment of internal control over financial reporting. The same auditor that audits the financial statements does it, and the audit report is in principle combined with the financial statement audit report.

In J-SOX the auditor audits management's assessment and does not give a separate opinion on control effectiveness. J-SOX also has two deficiency classes instead of three, adds safeguarding of assets as an objective, and has no size exemption for listed companies.

Scope the assessment, assess company-level and process-level controls including IT controls, document the process and controls, evaluate and fix deficiencies, and file the internal control report with the annual securities report, together with the auditor's report.

Related

From the blog

The related industry news, interviews, technologies, and resources.