Compliance
Navigating Ukraine’s New “Kupina” Standard for Qualified Electronic Signatures
From September 1, Ukraine shifts to the “Kupina” cryptographic standard for qualified electronic signatures—learn what this means for individuals and businesses and how to stay compliant without disrupting operations.
By NomadicTax Research Team • 5-8 min read • August 31, 2026
## What is the “Kupina” Standard?
Ukraine’s State Tax Service is implementing a **new national cryptographic “Kupina” standard** starting **September 1, 2026**, for qualified electronic signatures (QES). The aim is to replace older algorithms with one that offers improved resilience against modern cyber threats, ensuring long-term protection of data. ([tax.gov.ua](https://www.tax.gov.ua/en/mass-media/news/1045106.html?utm_source=openai))
## Who Is Affected?
- **Providers of qualified electronic trust services**, including state authorities like the State Tax Service, are already able to issue certificates according to “Kupina” as of August 26. ([tax.gov.ua](https://www.tax.gov.ua/en/mass-media/news/1045106.html?utm_source=openai))
- **Individuals and businesses**: Current certificates remain valid until their expiration date. No immediate action is required by existing certificate holders. Systems supporting both old and new standards are interoperable to ease transition. ([tax.gov.ua](https://www.tax.gov.ua/en/mass-media/news/1045106.html?utm_source=openai))
## Why This Change Matters
- **Stronger security**: “Kupina” is designed to be robust against emerging threats that compromise older cryptographic methods.
- **Legal certainty**: Documents signed under the new standard retain full legal force; no retroactive invalidation is expected.
- **Administrative continuity**: Processes remain in place, and interoperability means minimal disturbance to current workflows.
## Actionable Advice
1. **Audit your current QES setup**: Check certificate expiry dates and readiness for future reissue under the new standard.
2. **Update software and systems**: Ensure that your digital signature applications and document management platforms support “Kupina.”
3. **Training & awareness**: Inform stakeholders (legal, IT, HR) about the change and highlight that current signatures remain valid.
4. **Plan for renewal**: Schedule renewals under the new standard when current certificates expire, avoiding last-minute rushes or compliance gaps.
## Example Scenario
**Case study**: A Ukrainian SaaS provider issues thousands of QES-based invoices annually.
- Their existing certificates expire over the next 6–12 months. They test “Kupina”-compatible signing tools and verify document acceptance with major partners.
- Upon expiration of each certificate, they switch to “Kupina” issuance—thanks to interoperability, no client experiences disruption.
**Bottom line**: The transition brings Colombia-level security without invalidating prior signatures—plan and execute renewals methodically, stay compatible, and avoid surprises.