# EU Supplier & Invoice Check (IBAN, VAT, sanctions, Peppol) (`factline/eu-supplier-invoice-check`) Actor

Check a supplier before paying its invoice: company registers, sanctions and PEP on company, directors and parents, VAT match, IBAN validity and country, Polish whitelist accounts, sender email, Peppol. One verdict: pass, review or hold.

- **URL**: https://apify.com/factline/eu-supplier-invoice-check.md
- **Developed by:** [Matthew Sammels](https://apify.com/factline) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $150.00 / 1,000 invoice checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## EU Supplier & Invoice Check

Check a supplier before you pay its invoice. One row per invoice with a verdict (`pass`, `review` or `hold`), the reasons, and the official source of every part.

### What it checks

- **The supplier** in official company registers: UK Companies House, Ireland CRO, France SIRENE/RNE, Norway, Finland, Czechia, Slovakia, Estonia, Poland, plus GLEIF worldwide. Active or dissolved, number, address, incorporation date.
- **Sanctions and PEP** on the company, its directors and owners (UK, France, Norway) and its parent companies (GLEIF), against the EU, UN, UK and US OFAC lists.
- **VAT number** in the EU VIES service, matched to the registered company name.
- **IBAN**: valid checksum and length, and whether the bank account is in the same country as the company. For Polish suppliers: whether the account is registered to that company on the Polish VAT whitelist (paying another account has tax consequences in Poland).
- **Sender email**: domain exists and receives mail, throwaway domains, look-alike typo domains, and a mismatch with the supplier's website.
- **Dutch bankruptcy** (Centraal Insolventieregister) when you add the KvK number.
- **Peppol e-invoicing**: whether the supplier is on Peppol and which documents it receives.

### Input

A list of invoices as JSON. Each invoice: `name` (or `id`, a company number) and `country`, plus what is on the invoice: `vat`, `iban`, `email`; optional `domain` and `kvk`. Send at least `iban` or `vat`.

```json
[
  { "id": "7740001454", "country": "PL", "vat": "PL7740001454", "iban": "PL62102010260000190206882106" },
  { "name": "Colruyt Group", "country": "BE", "vat": "BE0400378485" }
]
```

### Verdicts

- `pass`: supplier found and active, payment details consistent, nothing flagged.
- `review`: something needs a human look before paying, for example an IBAN abroad, an account not on the Polish whitelist, a VAT number registered to another name, a new website or a sender email that does not match.
- `hold`: do not pay yet. A possible sanctions match on the company, a director, an owner or a parent company, or an invalid IBAN.

### Limits

This checks the supplier and the invoice details against official records. It cannot confirm who holds a bank account: use your bank's payee name check (Verification of Payee) before the first payment. Sanctions results are possible matches for a human to confirm; this is a screening aid, not legal advice.

Powered by [Factline](https://factline.dev). Also available as an API (`/v1/invoice/check`) and MCP tool (`supplier_invoice_check`) for AI agents.

### For AI agents

Agents can run this Actor through the Apify MCP server, or pay with USDC on Base through Apify's x402 support without an Apify account.

# Actor input Schema

## `invoices` (type: `array`):

One object per invoice. Fields: name (supplier company name) or id (company number: LEI, UK company number, SIREN, Polish NIP...), country (2 letters), and from the invoice: vat, iban, email (sender), optional domain (supplier website) and kvk (Dutch KvK number, adds a bankruptcy check). Send at least iban or vat.

## Actor input object example

```json
{
  "invoices": [
    {
      "id": "7740001454",
      "country": "PL",
      "vat": "PL7740001454",
      "iban": "PL62102010260000190206882106"
    },
    {
      "name": "Colruyt Group",
      "country": "BE",
      "vat": "BE0400378485"
    }
  ]
}
```

# Actor output Schema

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

All results as JSON (one item per invoice).

## `overview` (type: `string`):

Supplier, verdict, summary, flags.

# 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 = {
    "invoices": [
        {
            "id": "7740001454",
            "country": "PL",
            "vat": "PL7740001454",
            "iban": "PL62102010260000190206882106"
        },
        {
            "name": "Colruyt Group",
            "country": "BE",
            "vat": "BE0400378485"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("factline/eu-supplier-invoice-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 = { "invoices": [
        {
            "id": "7740001454",
            "country": "PL",
            "vat": "PL7740001454",
            "iban": "PL62102010260000190206882106",
        },
        {
            "name": "Colruyt Group",
            "country": "BE",
            "vat": "BE0400378485",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("factline/eu-supplier-invoice-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 '{
  "invoices": [
    {
      "id": "7740001454",
      "country": "PL",
      "vat": "PL7740001454",
      "iban": "PL62102010260000190206882106"
    },
    {
      "name": "Colruyt Group",
      "country": "BE",
      "vat": "BE0400378485"
    }
  ]
}' |
apify call factline/eu-supplier-invoice-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,factline/eu-supplier-invoice-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/VpeIYvnOh3nDqu83b/builds/jkxbetZ9PV8Yz2xjp/openapi.json