Japan Corporate Events Monitor — M&A, Shareholder & Board Changes (EDINET)

What just happened at that Japanese listed company?

Japanese listed companies must file an extraordinary report (臨時報告書, rinji hokokusho — the Japanese equivalent of a U.S. 8-K) with the Financial Services Agency whenever a material corporate event happens: an M&A decision, a change of major shareholders or parent company, a change of representative directors, shareholders-meeting resolutions, or an event with significant impact on financial results.

Those filings are public on EDINET, but they are in Japanese and buried in XBRL. This actor turns them into a daily, machine-readable feed of which company disclosed what kind of event, when — as clean English structured JSON. No Japanese reading required.

A key trick: in EDINET's XBRL, the element ID that carries the report body identifies the event type by itself. So classification is exact, not guessed from free text.

What you get (one record per filing)

{
  "docId": "S100YST3",
  "submittedAt": "2026-07-29 09:12",
  "filingType": "extraordinary_report",
  "companyNameJa": "株式会社ニチリョク",
  "companyNameEn": "Nichiryoku Co.,Ltd.",
  "secCode": "7578",
  "edinetCode": "E03304",
  "eventCategories": ["business_transfer"],
  "hasMnaEvent": true,
  "events": [
    {
      "category": "business_transfer",
      "categoryEn": "Business transfer or acquisition decision (M&A)",
      "isMnaRelated": true,
      "titleJa": "事業の譲渡又は譲受けの決定",
      "eventDate": "2026-05-26",
      "bodyJa": "２【報告内容】１．当該事業譲渡先の名称、住所、代表者の氏名…",
      "element": "DecisionOnTransferOrAcquisitionOfBusinessTextBlock"
    }
  ],
  "reasonJa": "当社は、2026年５月26日開催の取締役会において…",
  "ordinanceItems": ["8-2"],
  "source": "EDINET"
}

• eventCategories / hasMnaEvent — machine-readable event classification, derived from the XBRL element, not from text guessing.
• companyNameEn — the company's official English name as registered in EDINET (not machine-translated).
• eventDate — best-effort first date found in the report body (board decision date, meeting date, …).
• bodyJa / reasonJa — the original Japanese text, kept for full detail (feed it to your LLM for translation or summaries).
• ordinanceItems — the legal item under Cabinet Office Ordinance Art. 19(2) that triggered the filing (e.g. 9-2 = shareholders-meeting resolutions).

Event categories

Category	Meaning
merger, share_exchange, share_transfer, company_split, business_transfer, subsidiary_acquisition	M&A decisions (hasMnaEvent: true)
reverse_stock_split	Meeting called for a reverse stock split (often the step before a squeeze-out / delisting)
major_shareholder_change	Change in major shareholders
parent_or_subsidiary_change	Change in parent company or specified subsidiaries
representative_director_change	Change of representative directors (top management)
auditor_change	Change of independent auditors
agm_resolution	Shareholders-meeting resolutions, incl. voting results
stock_option_issuance	Stock option issuance not subject to registration
significant_financial_event	Impairments, debt waivers, special losses, etc.
financial_covenants, uncollectible_receivables	Debt covenant / receivable-risk disclosures
other	Anything else — still labeled with a readable English name derived from the XBRL element

Who it's for

• Investors & analysts watching Japanese equities for corporate events without reading Japanese.
• M&A / special-situations researchers — filter with categories for M&A decisions only.
• Newsletter writers & AI agent builders who want Japanese 8-K-style events as a normalized JSON stream.

Pairs well with our Japan Activist & 5% Filings Tracker: that one tells you who is accumulating shares; this one tells you what the company itself just disclosed. For the U.S. market, see our SEC Insider Trades Tracker (Form 4).

Input

Field	Default	Notes
dateFrom	5 days ago	First disclosure date (JST), YYYY-MM-DD.
dateTo	dateFrom / today	Last disclosure date (JST).
categories	[] (all)	Keep only filings containing these event categories.
includeCorrections	false	Also scan correction reports (doc type 190).
secCode	—	Optional stock code filter (e.g. 7203 for Toyota).
maxFilings	40	Cap the run for a cheap sample (0 = no limit).
delayMs	500	Politeness delay between EDINET requests.
edinetApiKey	—	Your EDINET API v2 key (free from the FSA). Falls back to EDINET_API_KEY env var.

Volume guide: roughly 15–50 corporate extraordinary reports per business day, spiking to 150+ in late June (AGM season voting results).

Getting an EDINET API key

The key is free. Register at the EDINET site (Financial Services Agency) → API section → issue a subscription key. This actor calls only the official documented API (documents.json and document download), never scrapes the web UI.

Notes & limitations

• Investment-trust filings ("臨時報告書（内国特定有価証券）" — fund accounting-period notices) are excluded on purpose; this actor is about corporate events.
• Report bodies are free-form Japanese; classification comes from the XBRL element and is exact, while eventDate is best-effort. The original text is always included.
• Data source: EDINET (FSA). Usage follows EDINET's terms (API access permitted; high-volume hammering is not — hence the built-in delay).

FAQ

What is a rinji hokokusho (臨時報告書)? Japan's equivalent of a U.S. 8-K: an extraordinary report that listed companies must file with the FSA when a material event happens — an M&A decision, a change of major shareholders or representative directors, AGM resolutions, or a significant financial event. This actor turns those filings into English structured JSON.

How do I monitor Japanese M&A announcements in English? Set categories to the M&A set (merger, share_exchange, share_transfer, company_split, business_transfer, subsidiary_acquisition) — or just filter records where hasMnaEvent is true.

How reliable is the event classification? Exact, not guessed: in EDINET's XBRL the element ID that carries the report body identifies the event type by itself. The original Japanese text is always included for detail.

How many filings should I expect? Roughly 15–50 corporate extraordinary reports per business day, spiking to 150+ in late June (AGM season voting results).

Run locally

npm install
EDINET_API_KEY=your_key node src/main.js

Local input can be placed in storage/key_value_stores/default/INPUT.json.