Skip to main content
This guide is outdated and will be removed on 1 November 2026. The up-to-date Slovakia reference is on the Slovakia country page.

Start here

This guide contains public integration notes for Slovakia. Use it for identifier formats, search behavior, and country-specific caveats. The live source of truth for coverage, pricing, data sources, documents, legal forms, roles, and status values is the pricing page.

Slovakia coverage, pricing, and sources

Open the current catalog for supported datapoints, documents, sources, identifiers, and availability.
Country details below are preserved as integration notes. If a table or example conflicts with the live pricing page, use the pricing page as the source of truth and contact support.

Data Sources

Slovakia uses four official sources. For a given entity, company data comes from the RPO, financial statements come from the RÚZ, the Trade Register Extract comes from the ORSR, and beneficial ownership comes from the commercial register’s beneficial-owner records.
  • RPO (Register právnických osôb, podnikateľov a orgánov verejnej moci). The Register of Legal Entities, Entrepreneurs and Public Authorities. This is the structured data source for company data for all entity types (commercial companies, sole entrepreneurs, non-profits, public entities), available at rpo.statistics.sk. Provides company name, legal form, status, registered address, share capital, activity descriptions, statutory bodies (legal representatives), stakeholders (shareholders, other key persons), and statistical codes.
  • RÚZ (Register účtovných závierok). The Register of Financial Statements, available at registeruz.sk. Source of the Financial Statements documents.
  • ORSR (Obchodný Register Slovenskej Republiky). The Commercial Register of the Slovak Republic, maintained by the Ministry of Justice. Used for Trade Register Extract (PDF) retrieval from orsr.sk. It is not a structured data source for company attributes.
  • KÚV (Konečný užívateľ výhod). Beneficial-owner records filed into the commercial register. They are not published on the register website or in the Trade Register Extract, so they are obtained as an official certificate of facts issued by the registration court. Source of the Ultimate Beneficial Owners datapoint and the Beneficial Ownership Certificate document.
The RPO aggregates data from multiple source registers (Commercial Register, Trade Licenses Register, etc.) and provides a unified view of legal entities in Slovakia. The ORSR specifically covers commercial companies registered in the court registry system.

Modes

Slovakia serves company, legalRepresentatives, otherKeyPersons, and shareholders in two modes: The activity-code inference and the dissolved-company fallback described below apply to verification mode only.

Company Identifiers

Query Identifiers

Slovakia uses a single primary identifier for all entity types:
ICO is always 8 digits. Leading zeros are significant and must be preserved. For example, 00151742 is a valid ICO — do not strip leading zeros.
Entities without an ICO. A small number of register entities (for example attorneys, branches of foreign undertakings, and state enterprises) have no ICO. Search returns them with an id in the form RPO-<number>. Use that id as returned for company requests. Their response has no identifiers.ico.

Identifiers in API Response

Once you retrieve company data, the identifiers object contains:
Slovakia does not return VAT numbers in the company profile response. Eligible companies can also return an EUID alongside their ICO.

European Unique Identifier (EUID)

Eligible s.r.o. and a.s. companies confirmed in the Commercial Register can return company.identifiers.euid in the format SKORSR. followed by their 8-digit IČO. It is available in prefill and verification when the register confirms the company’s current identity and legal form. EUID is a response identifier, not a search key. GLEIF is the supplementary data source for this identifier. company.identifiers.lei is optional. It is returned when the IČO (ico) matches exactly one LEI through a GLEIF registration or validation reference. The Legal Entity Identifier has 20 uppercase alphanumeric characters, ending in two check digits. Coverage varies by entity. An absent lei does not prove that the company has no LEI. Lapsed, retired or merged LEIs may be returned; annulled LEIs are excluded.

Search Capabilities

Search Performance: Use ICO-based searches for best performance and exact matching. See the Speed section of the pricing page for current search latency.

Active companies only

The register itself excludes companies that are no longer active when you search with activeOnly=true.

Quirks & Gotchas

Company Status

Company status is mapped deterministically from RPO legal status codes (codelist CL010108). No AI inference is involved in status determination.

Status Code Mapping

Status priority logic: (1) If a termination date exists, the company is always mapped to Closed regardless of the status code. (2) Otherwise, the current status code determines the status. (3) If no status information is available, the system defaults to Active.
Slovakia uses the official codelist CL000056 containing 90+ legal forms. The mapping from these codes to standardized forms and ISO 20275 (ELF) codes is deterministic. In verification mode, when the codelist mapping gives no ISO 20275 code, one may be added by lookup, and a form mapped to “Other” may receive a more specific standardized category. Forms shown with -- in the tables below can therefore still carry an ISO 20275 code in the API response.
ISO 20275 (ELF) codes are only assigned for legal forms that have registered LEI entities in the GLEIF database. Most Slovak legal forms do not have ELF codes assigned in the current GLEIF list (v1.6).

Key Business Forms

Sole Proprietorships

Cooperatives

Non-Profit Organizations

Public Law Entities

Branch Offices

European Forms

Financial Institutions

The full CL000056 codelist (90+ legal forms) is available at MetaIS. Our system maps every code to provide English translations, standardized categories, and ISO 20275 codes where the codelist allows.
Legal representatives are extracted from two RPO data arrays, combined and deduplicated: The classification of a role as legal representative is fully deterministic — based on codelist codes, not AI inference.

Complete Statutory Body Role List (CL010113 — 58 roles)

These are stakeholders with signing authority, extracted from the stakeholders array:
Legal representatives include both individuals and corporate entities. Role translations are standardized deterministically based on the official codelist CL010113. All statutory body entries are current records only — historical records (with validTo set) are filtered out.

Other Key Persons

Other key persons are extracted from the RPO stakeholders array using codelist CL010109. These include supervisory board members, administrators, founders, and other roles that are neither legal representatives nor shareholders.

Complete Other Key Persons Role Mapping (CL010109 — 40 codes)

Codes 4-23 (marked “historical”) are executive roles that can appear in stakeholders when they represent former/historical positions rather than current statutory authority. These same codes in CL010113 represent current legal representatives. Mapping source: CL010109.

Shareholders

Shareholders are extracted from the RPO stakeholders array using codelist CL010109 (7 shareholder codes). Both individual and corporate shareholders are supported.

Shareholder Codes (CL010109)

Ownership Data

For s.r.o. (Limited Liability Companies), ownership data is calculated from RPO deposit records by matching stakeholders to deposits by name: Example (company with 3 shareholders, 7,500 EUR total equity):
Ownership percentages and capital amounts are only available for s.r.o. (Limited Liability Companies). Shareholders of other company forms (for example v.o.s. partners or the sole shareholder of an a.s.) are still returned when the register discloses them, without these amounts. Deposit-to-stakeholder matching uses normalized names (lowercase, academic titles removed). Currency is read from the currency.code field. Only current deposits (where validTo is null) are used.

Activity Code Mapping

The RPO publishes its main activity in statisticalCodes.mainActivity and current trade descriptions separately. The source code and wording are preserved under NACE_SK with isMainActivity: true in both modes. The actual code-list stamp CL010579 identifies NACE Rev. 2.1. Those assignments are formatted as NACE classes and formally mapped to ISIC, retaining the main flag. Unknown or missing stamps remain native; dates and code shape do not establish the edition. Verification mode can additionally infer activities from the current trade descriptions. Declared source assignments win over inferred duplicates and keep their main marker. The original descriptions are preserved in activityDescription.

Ultimate Beneficial Owners

Beneficial ownership is held separately from public RPO company data. A local partner obtains the certificate concerning the commercial register’s beneficial ownership records. Request ultimateBeneficialOwners in verification mode for structured data, or order ultimateBeneficialOwnersCertificate from availableDocuments for the source PDF. Delivery is asynchronous and can take several business days. Follow the existing request through webhooks or polling; do not submit repeated orders while it is pending. If the certificate cannot be obtained, the request reports an error rather than a successful empty result.

Data Availability Matrix

Legend: Yes = Available | No = Not Available | Limited = Conditionally Available | Manual = Delivered manually

Documents by Company Type

Entities without ORSR registration, such as most sole entrepreneurs and non-profits, have no trade register extract. Financial statements may still be available if the entity has filed reports in the Register účtovných závierok (RÚZ).
Trade Register Extract requires ORSR registration. The extract is listed for every company, but it can only be retrieved for entities registered in the commercial register (ORSR). Retrieval fails for entities that are not registered there, such as most sole entrepreneurs and non-profits.
Financial statements: Filed reports are obtained from RÚZ. Availability depends on the entity and reporting year; it does not require the customer to provide eIDAS credentials.

Example API Responses

All examples use placeholder data. Query: POST /v2/company with { "id": "<id>", "countryCode": "SK", "dataPoints": ["company", "legalRepresentatives"] }
Note: Closed companies have active: false. Shareholders and other key persons may not be available for dissolved companies, as the RPO entity endpoint may return empty arrays.
Note: Companies under insolvency proceedings have active: false with detailed status including insolvencyStartDate and additionalInfo describing the specific proceeding type.
Documents are returned when "dataPoints": ["availableDocuments"] is requested.