# Supplier onboarding

> Check a supplier's registered entity, status and officers before you issue the first purchase order.

Canonical: https://corpoapi.com/solutions/supplier-onboarding

## Verify before you pay

A new supplier is a new counterparty. Before the first purchase order, you want to know that the entity exists, that it is active, and that the bank details you were sent belong to the company you think you are paying. The register settles the first two, and the identifier you capture settles which entity the rest of the record belongs to.

## What to capture per supplier

A supplier master record is only as good as the identifiers in it. Capture these from the register:

- Legal name, as the register writes it
- Company number, the exact key for every future re-check
- Registered address and legal form
- Status, so a supplier that later dissolves can be flagged
- Officer records for the sign-off file

## A worked example

Once a supplier is in your master, checking it is one call. This request is the same shape for a vendor list you run on a schedule:

```bash
curl -X POST https://api.corpoapi.com/v1/verify/batch \
  -H "Authorization: Bearer ck_live_..." \
  -d '{"items": [{"jurisdiction": "se", "company_number": "5560129206"}]}'
```

A batch returns a result for each item, and the same company is billed at most once per day, so re-running the whole list the next morning does not multiply the bill. The first 100 starter calls are free, and the starter allowance applies across the whole batch.

## Across borders

Supplier panels span many countries and many registers. One API and one schema mean the vendor check does not need a new integration per country, and the coverage page lists each register with the fields it returns.

## Verify before you pay

Confirm the entity exists and is active, capture its identifiers for the vendor master, and pull the register's officer records for the sign-off file.

- Entity and status check
- Identifiers for your vendor master
- Officer records for the sign-off file

## One check for a global vendor list

Suppliers come from many countries and many registers. One API and one schema mean your vendor onboarding does not need a new integration per country.

- Many registers, one schema
- Batch-friendly for vendor lists
- Provenance for procurement records

## FAQ

### Can I check a long supplier list?

Yes. Batch verify runs up to 100 items per call, and the starter allowance applies across the batch.

### Do you cover suppliers outside the EU and US?

Yes. Coverage spans Europe, the Americas and Asia-Pacific, and the coverage page lists every register with the fields it returns.

### Does this check bank details?

No. It confirms the registered entity and its identifiers. Matching bank details to the entity is a separate check, and the company number you capture here is what makes that possible.