Canada joined the Hague Apostille Convention in 2024. The useful question now is which competent authority handles your document and what the Ukrainian recipient expects next.
The 2024 Hague Apostille change simplified the international authentication framework, but it did not make every Canadian document follow the same competent-authority route.
Old pre-2024 instructions can send clients through unnecessary or obsolete steps. Even under the apostille system, the source document, issuing jurisdiction and Ukrainian recipient still determine the practical route.
Read this section for the underlying reasoning and operational detail. Where a rule can change, use the dated source trail rather than treating the article as permanent authority.
The Hague Apostille Convention entered into force for Canada on 11 January 2024. That replaced the older authentication/legalization route for documents covered by the Convention, but it did not create one universal counter for every Canadian document.
Ontario Official Documents Services is a competent authority for documents within Ontario’s competence, including eligible Ontario public documents and Ontario-notarized documents. Global Affairs Canada remains a competent authority for federal documents and other applicable routes described in its current guidance.
People often begin by asking “Where do I get an apostille?” before confirming what document the Ukrainian notary, bank, registry or other recipient actually needs. That reverses the workflow. First identify the receiving requirement; then determine how the Canadian document must be signed or issued; then choose the competent apostille authority.
Apostille also does not replace translation, nor does it guarantee that a Ukrainian institution will accept the substance or wording of the underlying document. Those are separate questions.
For powers of attorney and similar Canada-to-Ukraine documents, align the Ukraine-side wording before notarization, then map the apostille and translation route. This reduces the risk of paying twice for a document that was formally authenticated but substantively unusable.
These links support the change-sensitive or institutional points in this publication. Check the competent source again when you are about to execute a real file.
Send the real situation. We’ll map the operational route and separate what is stable from what needs current verification.