Ukraine Blocked Tax Invoice Guide: Unblocking and VAT Credit

A blocked tax invoice in Ukraine is a tax invoice whose registration in the Unified Register of Tax Invoices has been suspended by automated risk monitoring. Until registration is restored or a refusal is successfully challenged, the supplier has no registered invoice on file and the buyer's VAT credit is interrupted.

Separate suspension from refusal first. Suspension means the invoice has stopped pending explanations, documents, and corrective action tied to the notice. Refusal comes later if the authority rejects the case or the taxpayer fails to cure the issue. Because 2025 State Tax Service updates expanded automatic-registration relief and taxpayer-data-table treatment, the useful sequence is to identify the blocking reason, separate risky-taxpayer status from transaction-risk or data-table issues, submit coherent evidence, monitor whether registration resumes automatically or needs escalation, and then reassess the buyer-side VAT-credit position.

Why Ukraine Suspends Tax Invoice Registration

Ukraine tax invoice suspension is driven by automated monitoring tied to registration in the Unified Register of Tax Invoices, not by a manual audit as the first step. In practice, the system screens invoice registration against risk criteria and taxpayer-profile criteria, then pauses registration if the case matches a rule that requires further explanation.

That is why Government Resolution No. 1165 matters so much in day-to-day operations. It is the framework that shapes how monitoring works, which cases are flagged, and what finance teams are reacting to when they receive a suspension receipt. For finance teams, Resolution 1165 explains the operating problem: why an invoice that reflects a real supply can still stop at registration.

The most important distinction is between risky taxpayer status and transaction-risk criteria. Risky taxpayer status is about the taxpayer profile. It asks whether the supplier itself has been classified as risky. Transaction-risk criteria are about the specific invoice or adjustment calculation being submitted. A supplier can have a real commercial transaction and still face suspension if the register sees a pattern that does not fit its profile, product codes, filing history, or supporting data.

Positive tax history and unconditional-registration logic can reduce the chance of a block, but they should not be treated as a guarantee. They are better understood as filters that can help transparent businesses avoid unnecessary friction. If your team already works with reporting controls such as Slovakia VAT control statement and invoice cross-checking, the logic is familiar: the issue is not whether an invoice exists, but whether the reported data fits the rule set that governs recognition.

For diagnosis, the most useful habit is to read the suspension receipt line by line and identify what kind of problem it actually describes. Is the issue tied to risky taxpayer status, to a transaction-level criterion, or to a mismatch between invoice data and the supporting documents that should prove the supply? That answer determines everything that follows.

How the Taxpayer Data Table Changes the Outcome

The taxpayer data table matters because it helps the tax authority see whether the goods or services on the invoice fit the taxpayer's normal business pattern. In plain terms, it is part of the mechanism that tells the system, "these are the codes, activities, and transaction types this business genuinely carries out." That is why taxpayer data table work often belongs in the same workflow as blocked-invoice remediation.

What the taxpayer data table does not do is solve every suspension by itself. If the invoice was blocked because the supplier has risky taxpayer status, clearing that status is a separate issue. If the block came from a specific transaction-risk rule, the case still has to be answered on its facts. The taxpayer data table can support smoother future registration and can help the system recognize recurring activity as normal, but it is not a substitute for dealing with the actual reason the invoice stopped.

This is where teams often confuse two different tracks. The taxpayer-data-table track is about proving that the transaction pattern matches the real business. The risky-status track is about removing or curing the classification attached to the taxpayer itself. Sometimes both tracks matter. Sometimes only one does. Treating them as the same problem can waste time and lead to a response package that answers the wrong question.

What to Submit After a Suspension Notice

A response to a blocked invoice in Ukraine should be built around the exact reason named in the suspension notice, not around a generic bundle of paperwork. Teams trying to unblock a tax invoice in Ukraine need the commercial logic of the transaction to be easy to follow from source documents to invoice data. If the notice points to a specific risk criterion, your explanation and evidence should answer that criterion directly.

The document package usually needs to show that the supply is real, correctly described, and consistent across records. That commonly means:

• the tax invoice itself
• the contract, purchase order, or other source agreement
• delivery, acceptance, or service-completion records
• payment evidence where payment timing is relevant
• any supporting documents that explain quantities, product codes, or the nature of the service

Before you submit, compare the documents against the invoice field by field. Check vendor and buyer details, product or service descriptions, quantities, dates, and values. Many blocked cases turn on small inconsistencies that make the transaction look less coherent than it really is. A strong package does not just prove that the business is legitimate in a broad sense. It proves that this specific invoice fits this specific supply and that the supporting documents tell the same story.

The response should show a clear factual chain from the underlying transaction to the suspended register entry, not broad assurances that the business is legitimate.

---

What Changed on 2025-03-03 and 2025-09-27

The blocked-invoice mechanism changed in 2025. On 2025-03-03, the State Tax Service of Ukraine said the blocked-invoice rate had fallen to 0.39% in February 2025 and outlined six changes to the suspension mechanism, according to State Tax Service of Ukraine's March 2025 update on blocked tax invoices. The policy direction was to reduce unnecessary blocking for transparent businesses instead of treating every edge case as a full stop.

The March 2025 package widened unconditional-registration relief. The STS said the thresholds were expanded, including monthly supply volume up to 1 million UAH, a per-counterparty cap up to 100,000 UAH, small transactions up to 10,000 UAH per invoice, total monthly volume for those small transactions up to 3 million UAH, and a higher manager-overlap threshold.

Rules changed again from 2025-09-27 under Government Resolution No. 1048, as described in the State Tax Service of Ukraine's September 2025 update on tax invoice registration rules. The reforms included automatic registration after risky status is cleared and qualifying conditions are met, improved automatic acceptance of taxpayer data tables, and a shift in the relevant adjustment-calculation risk criterion from 30 days to 90 days. For some taxpayers, compliant behavior could reopen registration without the same repeated manual friction. The practical takeaway is not that blocking disappeared; it is that older summaries may understate how quickly some cases move back toward registration once risky status is cured or the taxpayer data table is accepted.

What Happens to the Buyer's VAT Credit, and When to Escalate

While the supplier's invoice remains suspended, the buyer's right to VAT credit is interrupted. That is the buyer-side consequence: VAT credit timing follows the registration outcome. The supplier may be focused on unblocking registration, while the buyer is focused on whether it can recognize input VAT. Those are related questions, but they are not the same question.

The State Tax Service of Ukraine addressed this point directly in its 2024 explanation of tax credit during suspension: the period for determining the buyer's right to form tax credit is interrupted while registration remains suspended, and the normal position resumes once the supplier's invoice is registered. Teams that work across multiple VAT regimes will recognize a similar dependency in the Belarus ESChF electronic VAT invoice workflow, where tax treatment also depends on recognized electronic invoice status.

From a workflow perspective, there are two broad endings. The first is automatic or successful restoration: the taxpayer clears risky status, the data-table or evidence issues are resolved, the invoice is registered, and the buyer can reassess VAT credit on the basis of the restored registration. The second is refusal or continued blockage: the authority does not restore registration, and the taxpayer has to move into the relevant challenge or escalation path. Escalation is usually the right track when the authority refuses registration, the suspension remains unresolved after a targeted evidence package, or the taxpayer must protect a buyer relationship by documenting the challenge timeline.

For day-to-day operations, the most useful checklist is short:

1. Identify the exact blocking reason in the receipt.
2. Build the evidence package around that reason, not around generic business documents.
3. Address taxpayer-data-table issues and risky-status issues as separate tracks if both are present.
4. Monitor whether registration is restored automatically or only after further action.
5. Reassess the buyer's VAT-credit position only after the register status changes.

That sequence keeps the blocked-invoice workflow grounded in the real issue: the buyer's VAT position follows the registration outcome, and the registration outcome follows the quality of the supplier's remediation path.