Japan Supplier & KYB Change Monitor

Check known Japanese suppliers for official company closures, mergers, name changes and address changes. Built for procurement, KYB and CRM teams that already have Japanese corporate numbers.

See the evidence before connecting your supplier list: keep the prefilled demo, click Start, then open Dataset to inspect one official registry-closure event. No file upload or NTA API application ID is needed. The historical demo costs $0.0152 at current PPE prices; it is not a free run.

Try the 1-company demo

Example: what you will see

This is an actual historical record, rechecked on 2026-09-15, not a claim about a company's present creditworthiness.

Corporate number	Company	Official event	Effective date	Publication
1010001008916	旭化成パックス株式会社	Registry record closed (21)	2026-08-17	NTA, 2026-08-25

Every result includes the original process code, source sequence number, published address, official file identity and retrieval time. Download the Dataset as CSV, Excel or JSON, or consume it through the API.

Problem

A supplier's registry record can change between formal reviews. Procurement and compliance teams need to know which records to revisit; CRM teams need to know which entries to refresh.

What you get

An exact-match feed of official NTA changes for your own list of 1–10,000 corporate numbers. Paste a corporate-number column directly from Excel, CSV or a text list, or keep using the API-compatible list input. Choose a 1-, 7- or 30-calendar-day window. Identical events repeated across daily files are returned once; distinct history rows in the same file are preserved.

This is registry-change monitoring for a known list. Company-name discovery, static company databases, credit scores and legal pass/fail decisions are outside its scope.

Who it is for

• Procurement and supplier-risk teams reviewing existing Japanese vendors.
• KYB and compliance teams maintaining known counterparties.
• CRM, ERP and master-data teams routing company-record updates.

Quick start: no setup changes needed

1. Open the demo input. Keep the sample number, 1-day period and historical end date. No advanced settings are needed.
2. Click Start. Expected PPE charge: $0.0152 for one company and one event. Apify account credits may cover it; check your available credit before running.
3. When the run succeeds, open Dataset. Expect one closed event, official process code 21, with publication date 2026-08-25. Open Run summary to check coverage and charges.

The same demo input is ready to copy for the API:

{
  "companyNumbersText": "1010001008916",
  "lookbackDays": "1",
  "sourceDate": "2026-08-25"
}

This small historical demo reads one official daily file. Its date is pinned so you can reproduce the example; it is not live monitoring. NTA files have a rolling retention period, so a retained-date demo needs refreshing when its source expires.

The result tells you which existing record to review, not whether to terminate a supplier. In this example, workflowHint.queue is supplier_status_review; the original NTA event and source remain the evidence. Selected fields from the sample result:

{
  "companyNumber": "1010001008916",
  "name": "旭化成パックス株式会社",
  "eventType": "closed",
  "processCode": "21",
  "changeDate": "2026-08-17",
  "workflowHint": {
    "queue": "supplier_status_review",
    "label": "Review the supplier or KYB record status"
  },
  "source": {
    "publishedDate": "2026-08-25",
    "fileNo": 27873,
    "archiveName": "diff_20260825.zip"
  }
}

The complete Dataset row also retains the published address, source URL, attribution, retrieval timestamp and other original registry fields.

Release check on 2026-09-08: the official diff_20260825.zip archive (file 27873) still contained the documented change in 2,222 source rows. Local end-to-end checks completed the 1-/7-/30-day windows in 544 ms / 1,487 ms / 5,630 ms respectively; the 7- and 30-day summaries recorded unavailable publication dates rather than treating them as no-change days. These observed timings are release evidence, not a Cloud performance guarantee.

Rechecked on 2026-09-15 after simplifying the input: the same archive still returned exactly one matching event, and every sample-output field matched the current parser, including workflowHint (527 ms for the local one-file check).

How to monitor Japanese suppliers for closures and address changes

1. Replace the demo number in the paste box with a corporate-number column from your supplier, KYB or CRM export. Omit the header and company names. Leave the optional advanced list empty.
2. Clear sourceDate and select lookbackDays: "30" for your first audit.
3. Review the Dataset's official event, effective date and source evidence in your existing workflow.
4. Switch to lookbackDays: "1" for a daily task. Use 7 days to catch up after a short pause.

Setting	What to enter
Company numbers	Replace the sample with one known 13-digit-number column from Excel/CSV/text (new lines, comma, tab, semicolon accepted). Spaces and hyphens are accepted. No fuzzy name matching.
Audit period	1 day for the demo/daily monitoring; 7 days for catch-up; 30 days for an initial audit.
Audit end date	Clear for the newest available file. A specified non-publication day resolves to the preceding available file.

Already using the list input or a saved task? The companyNumbers array still works through the API and under Advanced — existing API/list input. Saved inputs are not overwritten by this update. Both fields are combined: remove any old demo number from the advanced list before pasting your own companies, or clear the paste box to use only the list. API requests without lookbackDays still use 30 days; the demo prefills do not inject a company or historical date into API requests.

A zero-match run with your own list can be valid. Open Run summary to see COMPLETE, PARTIAL, or FAILED, the processed/duplicate input count, fetched or failed files, dates without publications and the PPE event-charge estimate. PARTIAL states whether unavailable source files or a maximum run-cost limit reduced coverage. Do not interpret a failed source as "no changes."

Each result also includes a non-decisional workflowHint for an existing supplier/KYB/CRM queue, based only on the official NTA process code. It helps route a name or address refresh, status review, or successor-entity review; it is not legal, credit, sanctions, or supplier-termination advice.

Why this data is hard to collect manually

The official source is a set of Japanese XML archives published on business days. A manual workflow must select the right dates, process archives, interpret official codes and match a watchlist while retaining evidence. This Actor handles that repeatable work and keeps the original facts accessible.

Official source

National Tax Agency Corporate Number Publication Site — daily difference files.

Each result attributes the NTA publication and includes publishedDate, fileNo, archiveName and retrievedAt. Use is subject to the NTA terms. The Actor uses public downloads and does not require an NTA Web API application ID. It does not verify NTA's OpenPGP signatures.

Pricing example

Example	Calculation	Price
Demo: 1 company, 1 change	$0.005 + $0.00020 + $0.010	$0.0152
Audit: 100 companies, 5 changes	$0.005 + $0.020 + $0.050	$0.075
Audit: 1,000 companies, no matches	$0.005 + $0.200	$0.205

Companies are charged once per run, regardless of the lookback window. Each unique matching event costs $0.010. The Pricing tab is the current authority; platform usage is currently included. A low maximum run-cost limit may yield an explicitly partial result.

After the demo: use your list for a 30-day audit, then set up daily monitoring for ongoing record maintenance.

Release check for the live demo

Before a release, run npm run verify:quick-start. It checks that the documented demo event still exists in its exact official source archive. The check reads the public NTA file directly and does not start an Actor run or create PPE charges.