# Polish Company Registry Scraper (KRS) (`deriverge/polish-company-check`) Actor

\[$2.00 / 1K] Bulk Polish company lookup by NIP or KRS number. Queries the Ministry of Finance VAT white list, the KRS court register and EU VIES. Returns legal name, address, VAT status, published bank accounts, invoice account verification and KRS insolvency. Unmatched rows are free.

- **URL**: https://apify.com/deriverge/polish-company-check.md
- **Developed by:** [deriverge s.r.o.](https://apify.com/deriverge) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 company records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Polish Company Checker

### What does Polish Company Checker do?

**Polish Company Checker** verifies Polish companies in bulk against three official sources at once: the Ministry of Finance VAT white list, the National Court Register (KRS) and EU VIES. Give it a list of NIP or KRS numbers and for each one you get back the name, VAT status, the bank accounts the company has published with the tax office, the KRS status including insolvency, liquidation or restructuring, and an independent VIES confirmation.

### Why the white list matters

Since 2020, a payment above 15,000 PLN to a bank account that is **not** on the supplier's white list entry is not tax-deductible, and the buyer becomes jointly liable for the supplier's VAT. Accountants check this by hand, invoice by invoice. This actor does it in bulk: add the account number from the invoice to the row and the output says whether it is on the white list as of today, together with the request identifier the Ministry issues, which is the proof you keep for an audit.

| Source | The question only it answers |
|---|---|
| **VAT white list** | Is it an active VAT payer, since when, was it removed, and which accounts did it publish? |
| **KRS** | Does the legal entity exist, and is it in insolvency, liquidation or restructuring? |
| **EU VIES** | Does the EU confirm the VAT number is valid for cross-border trade? |

### Fair billing

You pay only for companies that resolve. NIPs that fail the checksum are caught locally and never generate a request. Sources that return no answer are not billed. A run that resolves nothing costs nothing.

### Sole proprietors are people

The white list also covers natural persons running a business under their own name. When the entry belongs to a natural person, **the name and address are withheld by design**. You still learn the VAT status. Sections of the KRS extract that list board members and shareholders are never read at all.

### Input

```json
{
  "companies": [
    "5260250995",
    "0000028860",
    { "nip": "7740001454", "bankAccount": "17103015080000000503131100", "reference": "invoice-1187" }
  ],
  "includeKrs": true,
  "includeVies": true
}
```

Strings and objects can be mixed freely. Ten digits with a valid NIP checksum are read as a NIP, any other ten digits as a KRS number; VAT numbers with the PL prefix work as well.

### Output

One row per submitted company:

```json
{
  "input": "5260250995",
  "matched": true,
  "entityType": "legal_entity",
  "nip": "5260250995",
  "krs": "0000010681",
  "name": "ORANGE POLSKA SPÓŁKA AKCYJNA",
  "vatStatus": "Czynny",
  "vatActive": true,
  "vatRegisteredOn": "1996-01-01",
  "publishedAccounts": ["17103015080000000503131100", "71103015080000000503131098"],
  "accountOnWhiteList": true,
  "companyActive": true,
  "krsProceedings": [],
  "vatValidVies": true,
  "whiteListRequestId": "iu9tM-98e2fkb",
  "riskFlags": []
}
```

Every value carries provenance: which register said it, at which URL, and when. If a source was down, the affected fields are `null` and the provenance row says why, never silently guessed.

### Watch a list for changes

Checking a supplier once is useful. Checking the same list every morning and reading only what changed is what keeps you out of trouble. Give the run a watch name (or save it as a task and schedule it) and every later run compares its results with the previous one: a company that turned inactive, a new risk flag, a VAT registration cancelled, a published account that disappeared. The differences are stored in the `CHANGES` record of the run, ready for an integration or an email. The comparison itself is free.

### Pricing

| Event | Price |
|---|---|
| Run fee, a tenth of a cent per run that resolves at least one company | $0.001 |
| Company resolved | $0.004 |
| Each additional source that returned an answer (KRS, VIES, account check) | $0.001 |
| Company not found | **free** |

### Frequently asked questions

**What does an unmatched row cost?** Nothing. Rows that fail the checksum or that no register knows are returned with an explanation and are never charged.

**Can I check an invoice account?** Yes. Add `bankAccount` to the row and the output says whether the account is on the white list today, with the Ministry's request identifier as proof.

**What if I only have a KRS number?** The actor reads the KRS extract first, takes the NIP from it, and continues with the white list and VIES.

**Where does the data come from?** The Ministry of Finance white list service, the Ministry of Justice KRS open API and EU VIES. All official, all free of charge, every value with its source and timestamp.

This is the Polish sibling of our Czech and Slovak, Romanian, Estonian, Lithuanian, Latvian and Bulgarian company checkers. They share the same validation engine and the same billing rule: unmatched rows are free.

# Actor input Schema

## `companies` (type: `array`):

One entry per company: a NIP (5260250995), a VAT number (PL5260250995), a KRS number (0000010681), or an object with nip or krs, an optional bankAccount from the invoice to verify against the white list, and an optional reference returned unchanged. Typos that fail the NIP checksum are reported and never charged.

## `includeKrs` (type: `boolean`):

Fetch the current KRS extract for every company that has a KRS number: legal form, seat, registration and removal dates, and section 6 with insolvency, liquidation and restructuring.

## `includeVies` (type: `boolean`):

Cross-check every company against the EU VIES system as a second, independent source. A disagreement between the registers is reported as a risk flag.

## `watchKey` (type: `string`):

Give the run a name such as "suppliers" and schedule it. Every later run with the same name compares its results with the previous one and stores the differences (status changes, new risk flags, removed accounts) in the CHANGES record. Comparison is free. Runs from a saved task are compared automatically even without a name.

## Actor input object example

```json
{
  "companies": [
    "5260250995",
    {
      "nip": "7740001454",
      "bankAccount": "17103015080000000503131100",
      "reference": "supplier-42"
    }
  ],
  "includeKrs": true,
  "includeVies": true
}
```

# Actor output Schema

## `companies` (type: `string`):

One row per submitted company, with VAT white list status, published accounts, KRS status and risk flags.

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

How many entities were resolved, how many were not found and therefore not charged, and how many carry a risk flag.

# 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 = {
    "companies": [
        "5260250995",
        {
            "nip": "7740001454",
            "bankAccount": "17103015080000000503131100",
            "reference": "supplier-42"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("deriverge/polish-company-check").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 = { "companies": [
        "5260250995",
        {
            "nip": "7740001454",
            "bankAccount": "17103015080000000503131100",
            "reference": "supplier-42",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("deriverge/polish-company-check").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 '{
  "companies": [
    "5260250995",
    {
      "nip": "7740001454",
      "bankAccount": "17103015080000000503131100",
      "reference": "supplier-42"
    }
  ]
}' |
apify call deriverge/polish-company-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,deriverge/polish-company-check"
        }
    }
}

```

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/2dhiL5boi4GlAcL3H/builds/pGbIBxHJam8B3YV72/openapi.json