Contents
A registration receipt that stalls the deal
For a Ukrainian VAT payer, a sale is not finished once it is posted. The seller must register a tax invoice for it in the state register, and only a registered invoice gives the buyer the right to input VAT. If the tax authority suspends registration, the buyer sees no invoice, delays payment or starts asking questions, and the seller has to prove that the transaction was genuine.
Colloquially this is called a blocked tax invoice. Foreign owners usually hear about it as an urgent request from the accountant for contracts, delivery documents and payment records. The pressure is the same everywhere: the documents exist, but they are scattered across mailboxes, archives and departments, and the explanation is written from scratch against the clock.
What a suspended tax invoice means and which rules apply
Legal basis
- Para. 201.16 of the Tax Code; Resolution No. 1165
- Registration of a tax invoice may be suspended. The payer may submit written explanations and copies of documents confirming that the transaction is genuine. A tax authority commission decides whether to register or refuse; a refusal can be appealed administratively or in court.
- Para. 201.10 of the Tax Code; transitional provisions (Law No. 2876-IX)
- For tax invoices issued on or after 16 January 2023, during martial law and for six months after it, the registration deadlines are the 5th and the 18th of the following month. The absolute limit for registration is 1,095 days from the date of issue.
- Para. 198.6 of the Tax Code
- The buyer may claim input VAT from a registered invoice within 365 days of its date; for an invoice registered late, in the period of registration.
- Para. 120-1.1 of the Tax Code
- Late registration is subject to a penalty under this paragraph.
Example: registration of tax invoice No. 31 is suspended
Hypothetical figures from the paired Ukrainian article. On 20 October 2026 a wholesale company ships goods worth UAH 240,000 including VAT to a buyer who is also a VAT payer.
What happens to tax invoice No. 31
20.10
- Event
- Goods shipped, tax invoice No. 31 issued
- Effect
- VAT UAH 40,000; registration deadline 18.11
20.10
- Event
- Invoice posted in the system
- Effect
- Liability recorded on the invoice date (Dr 643 Cr 6412)
29.10
- Event
- Receipt from the tax authority
- Effect
- Registration suspended
After 29.10
- Event
- Explanation and documents prepared
- Effect
- Submitted by the accountant through the Electronic Cabinet
The October liability of UAH 40,000 is already in the books, so the month can be closed and the return prepared without waiting for the commission. The suspended invoice cannot be withdrawn or corrected with an adjustment calculation, because an adjustment can only be registered against a registered invoice. If the transaction was genuine, the accountant submits the explanation. After a positive decision, registration simply adds the ERPN number; no new entry is needed.
If the transaction never took place, no supporting documents are submitted; a written explanation is enough. That call belongs to the accountant; the system does not make it on its own.
How the system prepares the package and the explanation
The package starts from the invoice
In the AI VAT: tax invoices section, each suspended outgoing invoice has a Registration package button. It creates one package per invoice, with the invoice details, the buyer and the content taken from the register. The core documents are a contract, a specification, an invoice for payment, a delivery note or act, and a payment document; the system looks for them in the archive.
Recommended supporting documents, such as transport documents, lease agreements, HR documents, trial balances and statements, are included if found and marked as not found otherwise. For the specific transaction, the system also suggests what else is missing.
The explanation: built from accounting data, AI only on request
The explanation is drafted without AI: the system updates a previously approved base version or builds an outline from the accounting data, with gaps marked for clarification. An AI-written version needs a separate click on Write with AI; without it, nothing is sent to AI. The explanation itself is in Ukrainian, because it goes to the Ukrainian tax authority.
The package moves through the statuses Draft, Needs documents, Ready to file, Filed and Result received. The VAT payer data table (form J1312304) is filled from the books; XML is generated only if it matches the current schema, otherwise CSV and print are available.
Deadlines before anything is suspended
The VAT plan shows the nearest registration deadline, invoices issued and awaiting registration, and incoming invoices expected from suppliers based on the first event. Each invoice's deadline follows the rule in force on its date of issue.
By hand vs in the system
Documents
By hand: Gathered from email and folders against the clock
In the system: Core and recommended documents found in the archive, gaps marked
Explanation
By hand: Written from scratch every time
In the system: Drafted from accounting data or an approved base version
Liability
By hand: Postponed until the decision
In the system: Recorded on the invoice date
Status
By hand: Tracked in a spreadsheet
In the system: Package status from draft to result
What to agree with the accountant in advance
- File contracts, delivery documents and payment records in the archive as transactions happen, not after a suspension.
- Decide first whether the transaction is genuine and whether the invoice is correct: the route depends on the answer.
- Do not try to fix a suspended invoice with an adjustment calculation.
- Track the package status until the result arrives, and record the ERPN number.
Next in the series
Diia City compliance audit: criteria and annual report
Open the demo databases yourself: no sign-up, view only.