Supplier onboarding

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.

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

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:

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.

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.