Translation, notary, apostille

Where was it issued, and where will it be used?

Pair hint (checked 2026-10-15)

• Origin: PARTY_IN_FORCE (EIF 1981-10-15)
• Destination: PARTY_IN_FORCE (EIF 1965-01-24)
• Apostille: LIKELY_YES_PUBLIC_DOCUMENTS
• Legalisation: USUALLY_REPLACED_BY_APOSTILLE
• RON offer: off (DO_NOT_ASSUME)
• Confidence: medium

• Both countries are Apostille parties in force for public documents in scope.
• Apostille does not confirm the truth of the document contents.
• Foreign recognition is never promised.

Translation checklist

Verdict: REVIEW_REQUIRED — Same language still may require a certified/sworn form — confirm with the recipient.

Translator pack (free)

Attach or name the source file before translation

Keep unchanged in the translation:

• Full legal names exactly as on the source
• Dates in the source calendar form
• Official titles, seals, and registry numbers
• Place names and authority names

• Origin US → destination GB.
• Document family: civil_status.
• Translation checklist: REVIEW_REQUIRED — Same language still may require a certified/sworn form — confirm with the recipient.
• Do not machine-translate seals, signatures, or proper names without a human check.
• A certificate of translation is only used where the destination allows self-certification; otherwise use a sworn/certified translator route.

Auto-translate of seals and proper names is forbidden without a human check. Certificate of translation: only where the destination allows self-certification.

Notarisation instruction

1. Confirm whether the receiving authority needs a notarial act on the original, on a copy, or on a translation.
2. Use a notary (or equivalent authorised officer) competent in the place of signing or issuance.
3. Keep the original and the notarial certificate together for the next formality step.

• Remote online notarisation (RON) is not assumed to be recognised abroad.
• Destination recognition of RON: DO_NOT_ASSUME — offer stays off until confirmed.
• Partner notaries are optional and only after you have seen the official path.

Apostille or consular legalisation

Likely apostille path for public documents in scope (confirm competent authority and recipient rules)

Official fee: GAP. Processing time: GAP.

1. Open the HCCH competent authorities list for the country of origin.
2. Confirm the document type is a public document (or has been notarised into one) before requesting an apostille.
3. If apostille does not apply, ask the destination embassy/consulate of the origin country for the current legalisation chain.
4. Do not treat an apostille as proof that the contents of the document are true.

HCCH competent authorities · Convention status table

• Apostille applicable hint: LIKELY_YES_PUBLIC_DOCUMENTS
• Legalisation chain hint: USUALLY_REPLACED_BY_APOSTILLE
• Confidence: medium
• Official fee and processing time stay GAP until a dated official schedule is attached.
• The receiving authority may still add its own requirements.

Sequence control

Mark what you have already done. Usual order: original → notary → translation → apostille/legalisation.

• Original document(suggested next)
• Notarisation (if required)
• Translation (if required)
• Apostille or legalisation

Cost estimate

• Official fees: GAP_until_sourced
• Third-party: GAP_until_sourced
• Partner quote: only_after_user_opts_in

No invented prices. Partner quotes only after an explicit opt-in; DIY official path stays free information.

Optional partner path

You can finish everything yourself via the official links above. A partner is never required. Passport scans and sensitive uploads stay blocked until a dedicated architecture and consent exist (blocked_until_separate_architecture_and_consent).