# Japan Supplier & Invoice Change Monitor (`japan_signal_lab/japan-supplier-compliance-watchlist`) Actor

Monitor known Japanese suppliers for official corporate-registry and qualified-invoice changes—built for procurement, supplier risk, KYB, accounts payable, and CRM.

- **URL**: https://apify.com/japan\_signal\_lab/japan-supplier-compliance-watchlist.md
- **Developed by:** [Japan Signal Lab](https://apify.com/japan_signal_lab) (community)
- **Categories:** AI
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 watchlist company monitoreds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Japan Supplier Compliance Watchlist

Monitor a known Japanese supplier watchlist by **exact 13-digit corporate number**. This Actor checks the newest public daily difference files from Japan's National Tax Agency (NTA) and emits only matching change events.

### What it checks

- Corporate Number Publication Site daily differences — name, address, status, and other registered-publication changes.
- Qualified Invoice Issuer Publication Site daily differences — invoice-issuer registration changes.

Every result includes official source URLs, published dates, file identifiers, source freshness, and attribution.

### Best for

- Procurement teams monitoring named Japanese suppliers
- Supplier-risk, KYB, compliance, and M\&A workflows
- Supply-chain and B2B data systems that need machine-readable Japanese official events

### Input

Provide `corporateNumbers`: an array of exact 13-digit Japanese corporate numbers. A watchlist of up to 10,000 companies is supported.

```json
{
  "corporateNumbers": ["1010001008916", "1010001034714"],
  "includeCorporateRegistry": true,
  "includeQualifiedInvoiceIssuer": true
}
```

### Output

Each change event contains the matched corporate number, company name where supplied, event source, official source URL, official published date, file number, source freshness, and a machine-readable English summary. A `SUMMARY` record contains the run-level source counts and limitations.

### Pricing

The main charge is **$0.01 per monitored company** ($10 per 1,000 companies). Tiny synthetic start/result events may appear separately. Platform usage costs are included by the developer.

### Important limits

- This is a change-event monitor, **not a current legal-status or compliance determination**.
- Invoice records are restricted to official corporate-entity rows (`kind=2`); individual businesses are excluded.
- No result means no exact match in the selected retained daily-difference files.
- The Actor uses official batch/difference files, not a scraped Japanese company directory.

### Data sources and attribution

- National Tax Agency Corporate Number Publication Site: https://www.houjin-bangou.nta.go.jp/download/sabun/index.html
- National Tax Agency Qualified Invoice Issuer Publication Site: https://www.invoice-kohyo.nta.go.jp/download/sabun

Output retains source attribution and links. Use is subject to the official source terms.

# Actor input Schema

## `companyNumbers` (type: `array`):

One known 13-digit Japanese corporate number per item. Spaces and hyphens are accepted and removed before exact matching.

## `corporateSourceDate` (type: `string`):

Use YYYY-MM-DD for one retained NTA corporate-number file. Leave blank for its newest file.

## `invoiceSourceDate` (type: `string`):

Use YYYY-MM-DD for one retained NTA qualified-invoice CSV file. Leave blank for its newest file.

## `includeCorporateRegistry` (type: `boolean`):

Includes official corporate-number publication changes such as name, address, closure, or merger events.

## `includeQualifiedInvoiceIssuer` (type: `boolean`):

Includes corporate-entity (kind=2) issuer registration, public-information, expiration, cancellation, and deletion events.

## Actor input object example

```json
{
  "companyNumbers": [
    "1010001034714",
    "1010001008916"
  ],
  "includeCorporateRegistry": true,
  "includeQualifiedInvoiceIssuer": true
}
```

# Actor output Schema

## `results` (type: `string`):

Exact-watchlist matches from the selected official NTA daily difference files.

## `summary` (type: `string`):

Source provenance, row counts, matched event counts, and product limitations.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companyNumbers": [
        "1010001034714",
        "1010001008916"
    ],
    "corporateSourceDate": "",
    "invoiceSourceDate": "",
    "includeCorporateRegistry": true,
    "includeQualifiedInvoiceIssuer": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("japan_signal_lab/japan-supplier-compliance-watchlist").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "companyNumbers": [
        "1010001034714",
        "1010001008916",
    ],
    "corporateSourceDate": "",
    "invoiceSourceDate": "",
    "includeCorporateRegistry": True,
    "includeQualifiedInvoiceIssuer": True,
}

# Run the Actor and wait for it to finish
run = client.actor("japan_signal_lab/japan-supplier-compliance-watchlist").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "companyNumbers": [
    "1010001034714",
    "1010001008916"
  ],
  "corporateSourceDate": "",
  "invoiceSourceDate": "",
  "includeCorporateRegistry": true,
  "includeQualifiedInvoiceIssuer": true
}' |
apify call japan_signal_lab/japan-supplier-compliance-watchlist --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,japan_signal_lab/japan-supplier-compliance-watchlist"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ltme3XJ5qVjTdgdO6/builds/rfd8DSJWqsdkP60Y8/openapi.json