Latvian Company Checker

What does Latvian Company Checker do?

Latvian Company Checker verifies Latvian companies in bulk against five official state registers at once. Give it a list of registration numbers and for each one you get back the legal name, address, legal form and status from the Register of Enterprises, the VAT registration with the tax authority's own risk marker, and three things a plain lookup never shows: insolvency proceedings, liquidation, and links to sanctions lists.

The combination is the point. Each register answers a question the others cannot:

Source	The question only it answers
Register of Enterprises	Does the company exist, and was it removed from the register?
VAT payer register	Is it a VAT payer, since when, was it excluded, and does the tax authority flag it as a risk under Section 139(2) of the VAT Act?
Insolvency register	Is it, or was it, in insolvency proceedings, and how did they end?
Liquidation register	Is it being wound up right now?
Sanctions register	Is the company linked to a sanctions listing such as OFAC SDN, directly or through its owners?
EU VIES	Does the EU confirm the VAT number is valid for cross-border trade?

A supplier can look perfectly registered while it has been in liquidation for two weeks, or while its beneficial owner sits on a sanctions list. This actor puts all of that on one row.

Fair billing

You pay only for companies that resolve. Checksum failures are caught locally and never generate a request. Registers that could not be read are not billed as joins. A run that resolves nothing costs nothing.

Sole traders and farms are people

The register also lists sole traders (IK, IND) and family farms (ZEM) under the names of the people who run them. When the entity is a natural person, the name and address are withheld by design. You still learn that the number exists, its status and its VAT registration. The sanctions register contains personal data too; this actor reads from it only the link to the company (which list, which program, since when, in which role) and never the person.

Typos never reach the register

Modern 11-digit registration numbers carry a checksum digit. Every number is validated locally first; a number that fails is reported as a typo, costs nothing, and never generates a download. Older 9-digit numbers have no checksum and are passed through to the register.

Input

{
  "companies": [
    "40003100234",
    { "code": "41203017621", "reference": "supplier-42" }
  ],
  "includeVies": true
}

Strings and objects can be mixed freely. VAT numbers with the LV prefix work as well. The optional reference is returned unchanged so you can join results back to your own system.

Output

One row per submitted company:

{
  "input": "41203017621",
  "matched": true,
  "entityType": "legal_entity",
  "code": "41203017621",
  "name": "Akciju sabiedrība \"L.V.K.\"",
  "legalForm": "Akciju sabiedrība",
  "companyActive": true,
  "vatNumber": "LV41203017621",
  "vatActive": true,
  "vatRiskFlag139": false,
  "vatValidVies": true,
  "insolvencyProceedings": [],
  "liquidations": [],
  "sanctionsLinks": [
    { "list": "OFAC SDN", "program": "GLOMAG", "since": "2019-12-09", "role": "Beneficial owner" }
  ],
  "riskFlags": [
    "SANCTIONS LINK: listed on OFAC SDN (GLOMAG) since 2019-12-09 through its beneficial owner. Do not pay before a compliance review."
  ]
}

Every value carries provenance: which register said it, at which URL, and when. If a register could not be read, 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 (VAT register, risk registers, VIES)	$0.001
Company not found	free

Speed

The Register of Enterprises publishes its data only as a 128 MB daily file with no per-company lookup. The actor therefore keeps a daily snapshot of all five registers and checks your list against it in seconds. If the snapshot is older than 36 hours, the run downloads the registers directly, which takes a few minutes; the output says which of the two happened.

Frequently asked questions

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

What does the Section 139(2) flag mean? The State Revenue Service marks VAT payers it considers a risk under Section 139(2) of the VAT Act. It is the closest Latvian equivalent to an unreliable payer status, and it is exactly the kind of thing to know before you pay an invoice with VAT.

How fresh is the data? The snapshot is rebuilt every day from files the registers publish daily. Each row states the snapshot time.

Where does the data come from? The Register of Enterprises (register, liquidations, sanctions), the State Revenue Service (VAT payers) and the national open data portal (insolvency), all published under open licences, plus EU VIES.

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