Japan Vendor Risk & Adverse Action Monitor avatar

Japan Vendor Risk & Adverse Action Monitor

Pricing

from $0.20 / 1,000 monitored companies

Go to Apify Store
Japan Vendor Risk & Adverse Action Monitor

Japan Vendor Risk & Adverse Action Monitor

Exact corporate-number monitoring for official Japan vendor adverse-action publications.

Pricing

from $0.20 / 1,000 monitored companies

Rating

0.0

(0)

Developer

Japan Signal Lab

Japan Signal Lab

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Monitor a known Japanese supplier, vendor, counterparty, or customer list for newly published official adverse-action events. Give this Actor the same 13-digit corporate-number watchlist used by a registry-change monitor. It returns only exact corporate-number matches—never a fuzzy name hit.

For: supplier risk, procurement, KYB/compliance, vendor master/CRM, and supply-chain risk teams managing Japanese counterparties.

Why this is a separate monitor

Japan Supplier & KYB Change Monitor answers: did the company record change? This Actor answers: did an in-scope regulator publish an adverse action for one of my known companies?

Use a 30-day initial audit, then schedule a 1-day run. A 7- or 30-day audit can repeat a historical match on later runs because this Actor deliberately does not retain a customer's watchlist or private alert state.

What it covers today

This is a narrow, source-backed MVP. It is not a complete Japan adverse-action, sanctions, legal, credit, insolvency, or adverse-media database. The public JFTC index rejected automated requests in this validation environment, so it is deliberately excluded rather than represented as coverage we cannot verify end to end.

SourceEvent scopeCorporate-number matchingPublication cadence
MLIT Negative Information SearchConstruction/public-works procurement suspensionsExact number displayed on the result and detail pageAs actions are published; Actor checks daily
Financial Services Agency (FSA)Financial-sector administrative actionsExact number displayed in the published action pageAs actions are published; Actor checks daily

MVP coverage is national within these authorities' published scopes, but it does not include every ministry, prefecture, municipality, license register, court, or private source. A source failure is recorded in SUMMARY; the Actor does not silently claim full coverage.

Input

{
"companyNumbers": ["7110001019278", "4120001077369", "3010001008699"],
"lookbackDays": 30
}
  • companyNumbers: 1–10,000 known Japanese 13-digit corporate numbers. Spaces and hyphens are normalized. Company names, aliases, and addresses are not matched.
  • lookbackDays: 1, 7, or 30. Use 1 for a daily schedule after a first audit.
  • sources: optional list of mlit_procurement and fsa_financial.

Output

{
"corporateNumber": "7110001019278",
"companyName": "中田建設株式会社",
"eventType": "procurement_suspension",
"authority": "北陸地方整備局",
"actionTitle": "指名停止",
"officialActionText": "工事請負契約に係る指名停止等の措置要領別表第2第15号に該当",
"actionDate": "2026-06-26",
"effectivePeriod": "令和8年6月26日~令和8年9月25日",
"sector": "Japan public-works procurement",
"severity": "medium",
"source": {
"sourceUrl": "https://www.mlit.go.jp/nega-inf/cgi-bin/search.cgi?jigyoubunya=shimeiteishi&EID=search&no=172",
"license": "PDL1.0"
},
"englishSummary": "Official MLIT procurement suspension. Review the linked Japanese source for the published grounds and period.",
"confidence": "official_exact_corporate_number"
}

Output storage

The named output Matched adverse-action events points to the adverse_actions Dataset and contains only exact matched events. The default Dataset contains one run_summary record per successful run (watchlist size, lookback, retrieval time, and match count). This lets scheduled health checks distinguish a successful zero-event sweep from a failed run without adding non-event records to the customer-facing event output.

severity is intentionally mechanical, not an AI judgment:

  • high: the official action title includes cancellation, revocation, abolition, or business suspension.
  • medium: the official action title includes a surcharge, procurement suspension, exclusion order, business-improvement order, or order.
  • not_assessed: no published action label maps to either rule.

Always review the official Japanese page. The Actor does not assert guilt, legal status beyond the publication, materiality to a relationship, or a compliance disposition.

Attribution and permitted use

Every output retains the official source URL, publication date, retrieval timestamp, authority, and an attribution string. The current authorities' site rules state that their content is usable under the Public Data License 1.0 (PDL1.0) unless otherwise marked, with source attribution and a clear indication that Japan Signal Lab processed it:

The Actor does not use gBizINFO REST API or data-download endpoints because those currently require an application and API token. It uses only the listed public official pages and checks sources sequentially with retry/backoff and response-size caps.

Pricing design (configure only after Cloud measurement)

PPE event names are fixed in code and must match the Apify Console exactly:

  • monitoring-run is charged once after input validation and before source processing.
  • monitored-corporate-number is charged before source processing.
  • adverse-action-event is charged immediately before each output row.
  • Do not configure apify-default-dataset-item; that would double-charge outputs.

Recommended pricing should be selected only after a successful Cloud Build and measured 1/100/1,000/10,000-company runs. The repository intentionally contains no live price or payment configuration.

Development

npm install
npm test
npm run build

For an audited live check, record the date, sources, lookback, exact test watchlist, source statuses, output count, and timing. Tests cover number normalization/deduplication plus MLIT and FSA parser fixtures.