Document recognition is a control question before it is a procedural one. Who accepted the document, under what authority, and on what legal basis — these are the facts that determine whether a shareholder can enforce rights or a buyer can rely on a title. The sources that answer these questions are not uniform across jurisdictions. This page maps what they show, what they do not show, and where the evidentiary chain ends.
The angle here is control: which entity or authority holds the power to validate or reject a document, and what the official record shows about that decision. Procedural rights and legal remedies are addressed separately. This page addresses only what can be established from official sources.
What the sources showThe legal basis for recognition — treaty, domestic statute, or bilateral agreement — is traceable through official legislative databases and treaty registries. Verified against public sources as of 2026-09-15. What the sources do not showAdministrative discretion exercised at the point of submission. No register records whether a specific official accepted or rejected a document in a given transaction. Condition of accessTreaty texts and domestic statutes are generally public. Apostille registers vary by jurisdiction: some are searchable online, others require a written request to the competent authority. Where the chain endsRecognition of a specific document instance — as distinct from the legal framework governing recognition — is not recorded in any centralised public register. The ceiling of what the sources allow is stated before any engagement.The legal framework governing document recognition
Document recognition operates on three distinct legal layers. Each layer has its own sources, and each has its own ceiling.
The first layer is the treaty framework. The 1961 Hague Apostille Convention establishes the baseline for public documents between contracting states. The HCCH e-APP register lists competent authorities by jurisdiction and, where a state has implemented the electronic apostille programme, allows verification of individual apostille certificates by number. This is the most reliable public source for confirming that a specific apostille was issued. Where a state has not implemented e-APP, verification requires direct contact with the issuing authority.
The second layer is bilateral and multilateral agreements. Many jurisdictions maintain separate treaties on legal assistance, mutual recognition of judgments, and consular legalisation. These treaties are registered with the United Nations Treaty Collection or the relevant regional body. The treaty text is public; the administrative practice under the treaty is not.
The third layer is domestic law. Each jurisdiction defines, by statute or regulation, which foreign documents it will accept, in what form, and with what authentication. These statutes are traceable through official legislative databases. Amendments are not always consolidated promptly, and the operative version at a given date requires verification.
Control, in this context, means the competent authority: the body designated by law to issue, authenticate, or verify a document. That designation is traceable. The exercise of discretion by an individual official at a specific submission is not.
What the Apostille register shows — and what it does not
The HCCH Apostille Section publishes a list of contracting states and their designated competent authorities. As of the date of this page, over 120 states are party to the 1961 Convention. The list is updated by the Permanent Bureau and is the authoritative source for determining whether a given state is a contracting party.
For states participating in the e-APP programme, the register allows verification of individual apostille certificates. The verification confirms: issuing authority, date of issue, document type (in general terms), and certificate number. It does not confirm the content of the underlying document, the identity of the signatory, or the legal effect of the document in the receiving jurisdiction.
For states not participating in e-APP, no centralised verification exists. Authentication follows the legalisation chain: notarisation, competent authority certification, and consular legalisation. Each step is performed by a different body. The record of each step is held by that body, not by a central register.
The gap between treaty membership and operational verification is material for cross-border transactions. A document may be formally apostilled by a contracting state and still be rejected by the receiving authority on grounds of domestic law. That rejection is not recorded in any public register.
| Layer | Source | What it shows | What it does not show |
|---|---|---|---|
| Treaty membership | HCCH Apostille Section | Whether a state is a contracting party | Whether a specific document was accepted |
| Competent authority | HCCH authority list | Which body is designated to issue apostilles | How that body exercises discretion |
| Individual certificate (e-APP states) | HCCH e-APP register | Issuing authority, date, document type | Document content, legal effect in receiving state |
| Individual certificate (non-e-APP states) | Issuing authority directly | Confirmation on request | Not available through public register |
| Domestic recognition rules | National legislative database | Statutory conditions for acceptance | Administrative practice, case-by-case decisions |
| Bilateral treaties | UN Treaty Collection / regional registries | Treaty text and parties | Implementation practice |
Control: who decides, and what the record shows
The control question in document recognition is not abstract. For a shareholder verifying a corporate structure across multiple jurisdictions, the operative question is: which authority in each jurisdiction has the power to accept or reject the documents that establish ownership, directorship, or encumbrance?
That authority is designated by law. The designation is traceable. The following categories of competent authority appear across the 35 jurisdictions covered by this analytical framework:
- Notarial bodies — designated by domestic notarial law to authenticate signatures and certify copies. The notarial register is public in most jurisdictions; individual acts are not.
- State or regional registries — designated to receive and file corporate documents. The filed document is the record. Whether the registry accepted or rejected a submission at a specific date is recorded in the registry's own files, not in a public database.
- Apostille-issuing authorities — designated by each contracting state under the 1961 Convention. The HCCH list names the authority; the e-APP register (where available) records individual certificates.
- Consular posts — designated to perform legalisation for non-Apostille chains. Consular records are not public.
- Judicial or administrative bodies — in some jurisdictions, recognition of foreign judgments or administrative acts requires a separate court or administrative procedure. The outcome of that procedure is recorded in the court or administrative register, which may or may not be publicly searchable.
For each jurisdiction in a cross-border verification, the analytical task is to identify the designated authority, confirm the applicable legal basis, and establish what the public record shows about the document in question. Where the public record is silent — because the authority does not maintain a searchable register, or because the relevant act predates digitisation — the ceiling is stated explicitly.
Where the sources disagree
Discrepancies between sources are themselves evidentiary. The following categories of disagreement arise in document recognition analysis:
Treaty list versus domestic statute. A jurisdiction may be listed as a contracting party to the Apostille Convention while its domestic law imposes additional requirements not reflected in the treaty. The treaty text and the domestic statute are both public; the operative rule at a given date requires reconciliation.
Registry record versus filed document. A corporate registry may show a document as filed and accepted. The document itself, when retrieved, may contain terms that conflict with the registry's index entry. The filed document controls; the index entry is a summary.
Apostille certificate versus underlying document date. An apostille certifies the authenticity of the signature or seal on the underlying document, not the currency of the information in that document. A document authenticated in 2019 and apostilled in 2024 reflects the state of affairs at the time of the underlying document, not at the time of authentication. This discrepancy is not flagged by the apostille register.
Bilateral treaty versus Apostille Convention. Some jurisdictions maintain bilateral legal assistance treaties that operate in parallel with or in place of the Apostille Convention for certain document types. Where both instruments apply, the applicable instrument for a specific document type requires legal analysis, not only source retrieval.
Where sources disagree, the disagreement is reported as a finding, not resolved by inference.
The limit of what the sources allow
The ceiling of what the sources allow is stated before any engagement. This section states it in full.
What can be established from official sources:
- Whether a jurisdiction is party to the Apostille Convention, and which authority is designated to issue apostilles.
- The text of applicable bilateral or multilateral treaties, as registered with the relevant treaty body.
- The domestic statutory framework governing recognition of foreign documents, as published in the official legislative database.
- For e-APP states: whether a specific apostille certificate was issued, by which authority, and on what date.
- The filed record in a corporate or land registry, where the registry is publicly accessible.
What cannot be established from official sources:
- Whether a specific document was accepted or rejected by a receiving authority in a specific transaction.
- The administrative practice of a competent authority — how it exercises discretion, what informal requirements it applies, how long it takes in practice.
- The content or legal effect of a document that has not been retrieved and reviewed.
- Whether a document that was valid at the time of authentication remains valid at the time of reliance.
- The outcome of any recognition procedure that is not recorded in a publicly searchable register.
The analytical report maps the first category. It names the ceiling explicitly for each jurisdiction covered. It does not infer, estimate, or extrapolate beyond what the sources show.
Cross-border coverage: 35 jurisdictions
Document recognition analysis across 35 jurisdictions requires a layered source map. Not all jurisdictions maintain the same categories of public record. The following framework applies:
Apostille Convention states (majority of the 35): The HCCH authority list and, where applicable, the e-APP register are the primary sources. Domestic legislative databases provide the statutory framework. Where the domestic language is not English, the operative text requires translation and verification.
Non-Apostille states (minority of the 35): The legalisation chain applies. The competent authority for each step is identified from the domestic legal framework and from the relevant consular post's published requirements. Consular requirements are published on official government websites and are subject to change without notice.
Jurisdictions with bilateral legal assistance treaties: The UN Treaty Collection and regional treaty registries are the primary sources for treaty text. Implementation practice is not recorded in a public register.
Jurisdictions with domestic recognition statutes: The official legislative database is the primary source. Consolidation of amendments varies; the operative version at a specific date requires verification against the official gazette or equivalent.
The analytical report for a cross-border transaction identifies, for each jurisdiction, which layer applies, which sources were consulted, what those sources show, and where the evidentiary chain ends.
FAQ
What does an apostille confirm, and what does it not confirm?
An apostille, issued under the 1961 Hague Convention, confirms the authenticity of the signature, seal, or stamp on the underlying document. It confirms the capacity in which the person signing the document acted. It does not confirm the accuracy of the content of the document, the legal effect of the document in the receiving jurisdiction, or the current validity of the information the document contains. The HCCH e-APP register, where available, allows verification that a specific apostille certificate was issued. It does not record whether the document was accepted by the receiving authority.
Can a document be apostilled and still be rejected?
Yes. An apostille satisfies the authentication requirement under the 1961 Convention for contracting states. It does not override domestic requirements in the receiving jurisdiction that go beyond authentication — for example, requirements for certified translation, notarial certification of the translation, or specific form requirements for the document type. Rejection by a receiving authority is not recorded in any public register. The analytical report identifies the domestic requirements applicable in each jurisdiction; it does not predict administrative outcomes.
What is the difference between legalisation and apostille?
Apostille is the simplified authentication procedure available between contracting states to the 1961 Hague Convention. Legalisation is the full authentication chain — typically notarisation, certification by the competent domestic authority, and consular certification by the receiving state's consular post — required where the apostille procedure does not apply. The applicable procedure depends on whether both the issuing and receiving states are contracting parties to the Convention, and whether any bilateral treaty modifies the default rule.
What sources are used to verify the legal framework in a specific jurisdiction?
The primary sources are: the HCCH Apostille Section (treaty membership and competent authority lists), the UN Treaty Collection (bilateral and multilateral treaty texts), the official legislative database of the jurisdiction in question (domestic statutes and regulations), and, where applicable, the official gazette for recent amendments. For e-APP states, the HCCH e-APP register is used for individual certificate verification. No secondary or aggregated source is used as a substitute for the primary official source.
How is a discrepancy between sources handled?
A discrepancy between sources — for example, between the treaty text and the domestic statute, or between the registry index and the filed document — is reported as a finding. The report identifies which source controls for the specific legal question, explains the basis for that determination, and states the discrepancy explicitly. Discrepancies are not resolved by inference or by preference for the more favourable source.
Sources
- HCCH Apostille Section — https://www.hcch.net/en/instruments/conventions/specialised-sections/apostille — extracted 2026-09-15
- HCCH e-APP Register — https://www.hcch.net/en/instruments/conventions/specialised-sections/apostille/eapp — extracted 2026-09-15
- United Nations Treaty Collection — https://treaties.un.org — extracted 2026-09-15
- Official national legislative databases — consulted per jurisdiction; URLs vary by state — extracted 2026-09-15
Request this report
Disclaimer: This report is a factual compilation from official registers and public sources. It is provided for informational purposes only, does not constitute legal advice, and contains no legal qualification of the facts established. VLO Law Firm assumes no liability for actions taken or not taken based on this material. For advice regarding your particular situation, please contact info@vlolawfirm.com.
Author: Elena Moretti — Partner, Continental Europe, VLO Law Firm