Ukraine PRRO Receipt Requirements: 2026 Guide

Under Ukraine PRRO receipt requirements, a seller that carries out a settlement transaction must issue a receipt or other settlement document in the official form and with all mandatory requisites. If a mandatory requisite is missing, the document may not be treated as a proper settlement document. The current format and content took effect on March 1, 2025. For internet sales, the document can be given on paper, delivered electronically, shown as a QR code on the device, or sent to the buyer's phone number or email.

In plain English, an RRO is the traditional cash register framework, and a PRRO is the software version of that registrar. Both sit inside the same settlement-document compliance system administered by the State Tax Service of Ukraine. The legal foundation for the modern software model is tied to Law No. 128-IX, which enabled broader use of software registrars, electronic registration, and electronic exchange of fiscal documents. That matters because receipt compliance is not just about taking payment, it is about issuing a document in the correct fiscal form through the recognized RRO or PRRO process.

For everyday operations, you should think about the rule in terms of the transaction moment:

• In-person cash sales: a settlement document is generally required when you accept payment for goods or services.
• Card-based transactions: if payment is made by card, including through POS or comparable payment acceptance flows, the seller still needs the proper settlement document, not just a bank confirmation.
• Internet sales: if the buyer pays online for goods or services, the obligation does not disappear because the sale happened remotely. You still need to issue the settlement document in an allowed form and make it available to the buyer correctly.

That is why receipt compliance should be treated as its own workstream within Ukraine software cash register requirements. A compliant payment flow, website checkout, or acquiring setup does not automatically mean your receipt flow is compliant. You need the right fiscal document, issued at the right time, in the right format, with the required requisites, and delivered in an allowed way.

What a Valid Settlement Document Must Contain

A valid settlement document in Ukraine is not just any proof of payment. It has to follow the officially established form and content for a fiscal receipt or related settlement document, whether it is printed or issued as an electronic settlement document. If you improvise your own checkout slip, payment confirmation, or email summary and it does not contain the required fields, it may not qualify as a proper settlement document for compliance purposes.

That is the core logic behind Ukraine settlement document requirements and Ukraine PRRO mandatory requisites: validity depends on whether the receipt includes the mandatory requisites that apply to that transaction. If a required requisite is missing, the document can be treated as improperly issued, even if the sale itself really happened.

A practical way to review Ukraine fiscal receipt requirements is to use the four questions below while keeping the State Tax Service clarification on mandatory requisites in mind: if at least one mandatory requisite is missing, the document will not be accepted as a settlement document.

1. Who issued the receipt?
The document must identify the seller and the fiscal source of the receipt. In practice, look for the business entity's identifying details, the business unit or point-of-sale details where relevant, and the fiscal identifiers that show it was generated through the proper PRRO or cash-register framework, not from an informal template. If you cannot tell who issued it or which fiscal registration it came from, that is a red flag.

2. What transaction took place?
A valid receipt needs the transaction basics: when the settlement happened, what kind of operation it was, and the payment information tied to that operation. The document should show the date and time, the payment method, and enough transaction detail to make the settlement understandable and auditable. For many businesses, this is the first checkpoint when verifying whether a receipt can stand up in bookkeeping or a tax review.

3. What exactly was sold, and for how much?
The receipt should show the line-level or amount-level substance of the transaction. Depending on the sale, that can include the goods or services, quantity, unit price, tax lines, totals, and the final amount due or paid. This is where many workflow errors surface: a payment may be captured, but the receipt does not clearly describe the transaction in the form expected for a compliant settlement document.

4. Does the receipt include the extra verification fields required for this payment method?
Some requisites appear only in specific scenarios. Card payments are the obvious example. In those cases, the practical test is not "does every receipt need every possible field," but "does this receipt contain the fields required for this type of transaction?" That is especially important for an electronic settlement document used in Ukraine for online or card-based sales, where card-related details, QR-based verification content, or other verification elements may be required when applicable.

For day-to-day compliance, the safest review approach is simple: do not ask whether the receipt looks reasonable. Ask whether it matches the official receipt structure and contains all mandatory requisites for that exact transaction context. If the answer is no, the document may fail as a proper settlement document even if your internal records otherwise look complete.

---

What Changed in the March 1, 2025 Receipt Format

The key date for Ukraine receipt format changes in March 2025 is straightforward: the updated forms and content of settlement documents became effective on March 1, 2025, according to the State Tax Service notice on the March 1, 2025 settlement-document update. If your business was already issuing PRRO receipts before that date, the main question is not whether you needed receipts before, but whether the receipt output your systems generate now matches the post-March-2025 format.

The State Tax Service later summarized the main change themes in the updated receipt form. The additions most businesses will notice are payment means, payment currency, expanded QR code content for checking the receipt in the RRO Accounting System, and the receipt's message authentication code (MAC). The authority also flagged other form changes, including removal of some older fields such as the card ID number and certain signatures, plus new niche requisites for duty-free alcohol and tobacco sales and the amount of the rest where that detail exists.

Operationally, the QR code and MAC are the biggest compliance shift. Under the updated Ukraine QR receipt rules, the QR code is not just a visual convenience for the customer. It carries data that supports receipt lookup and verification in the RRO Accounting System. The MAC serves a different purpose: it is a message authentication code generated by the RRO or PRRO, which helps confirm that the receipt data was produced within the fiscal system and has not simply been retyped, reformatted, or fabricated after the fact. In practice, that makes both elements part of your control environment for receipt verification, not cosmetic add-ons at the bottom of the document.

That matters for both paper and Ukraine electronic receipt requirements. If your PRRO, payment software, webshop, or accounting workflow stores receipt images, PDFs, or structured exports, those downstream records should preserve the post-March-2025 fields accurately. A receipt template that still omits the new QR content, drops the MAC, or maps payment details into old field logic can create avoidable compliance problems even if the sale itself was otherwise processed correctly.

For finance teams, the practical review points are simple: confirm your PRRO or other cash register software was updated for the March 1, 2025 form, test whether issued receipts now show the required payment and verification fields, and make sure your archiving or reconciliation process captures them intact. The same pattern appears in Slovakia eKasa receipt field and QR-code requirements and Slovenia's guide to fiscal verification and QR-based invoice checks: once QR-based checks and authentication fields become part of the official form, they belong in daily compliance checks, system testing, and audit evidence.

How Electronic Receipts Work for Internet Sales

Internet sales do not remove the duty to provide a settlement document of the established form and content. The State Tax Service clarification on RRO/PRRO use for internet sales makes that explicit: if the order or payment happens online, the buyer still must receive a proper fiscal receipt when the goods are delivered or the service is provided. In practice, that means Ukraine PRRO for internet sales is still about issuing a compliant settlement document, not just confirming that money was paid.

The State Tax Service has recognized several ways to deliver that document in remote transactions:

• in paper form
• in electronic form
• by displaying a QR code on the RRO or PRRO device or screen so the buyer can identify the settlement document
• by sending the electronic settlement document to the buyer's phone number or email address

What changes is the delivery channel, not the substance of the receipt. Under Ukraine internet sales receipt rules, an electronic settlement document still has to include the same mandatory requisites discussed earlier in this article. If required fields are missing, the document does not become compliant just because it was sent by email, shown on a screen, or tied to a QR code. A payment gateway notice or card-processing confirmation also does not replace the settlement document itself.

For sellers and finance teams, Ukraine electronic settlement document delivery is mainly an operations question. You need a repeatable process that does three things every time: creates the receipt at the correct point in the transaction, gets it to the buyer through a recognized channel, and preserves a usable copy for your own records. That matters for bookkeeping, daily reconciliation, refunds, buyer questions, and proof during a tax review.

A workable remote-sales flow usually includes:

• issuing the receipt no later than delivery of goods or provision of services
• capturing the buyer's email or phone number if you plan to send the receipt electronically
• making sure the buyer can actually access the document you send or retrieve
• storing the receipt data so accounting can match it to the order, payment, return, or dispute

If you work across markets, the same distinction between delivery method and receipt content also appears in Moldova's virtual cash register and electronic receipt rules. The core compliance point in Ukraine is the same: remote sale or card payment does not cancel the receipt obligation; it only changes how the buyer receives the document.

---

Where the State PRRO Tools Fit in a Compliant Workflow

The State Tax Service of Ukraine does not just publish PRRO rules. On its software registrar page, it also provides official cash register software and user-guide materials that help businesses apply those rules in day-to-day operations. That matters if you are translating Ukraine software cash register requirements into an actual cashier, checkout, or internet-sales workflow.

In practice, the official toolkit covers both sides of the transaction. The Android package on that page includes PRRO.Check.apk for customers to receive payment documents and PRRO.Pos.apk for cashier use, while the same official materials also point users to Windows software and setup guides. For many teams, those materials are the most direct starting point for building a working PRRO process because they show how the official workflow is expected to run in real software.

That said, the tools are only one layer of compliance. Installing a PRRO app does not remove the need to understand which transactions require a settlement document, what requisites the receipt must contain, or how an electronic receipt must be delivered. The software helps you execute the workflow, but the legal standard still sits in the receipt form, issuance rules, and delivery rules.

This is where the official tools matter most. They show businesses where receipt issuance, buyer delivery, and later retrieval happen inside the state-supported workflow, which is exactly the operational gap many fragmented official notices leave the reader to piece together on their own.

---

A Practical Checklist for Ukraine PRRO Receipt Compliance

Use this final review to test whether your process meets Ukraine PRRO receipt requirements in day-to-day operations, not just on paper.

• Confirm the transaction needs a settlement document. Start with the payment event, not the software setup. If you are accepting a covered payment method for a sale, return, or similar settlement operation, determine whether an RRO or PRRO receipt must be issued for that transaction.
• Use the current official receipt form. Check that your template, PRRO configuration, and staff instructions reflect the live official format rather than an older saved layout. For many teams, Ukraine fiscal receipt requirements fail first at the template level.
• Verify all mandatory requisites are present. Review the receipt fields against the transaction type you actually process, such as goods sales, services, card payments, returns, or internet sales. A document that looks complete but misses a required requisite may not qualify as a valid settlement document.
• Test the post-March-2025 fields and logic. Make sure your workflow supports the fields introduced or clarified in the March 1, 2025 format update, including QR-related and MAC-related elements where required. Do not assume your provider, integration, or print layout updated automatically.
• Choose a lawful delivery method. For in-store issuance, the control point is usually immediate delivery to the buyer. For remote and online transactions, confirm how the electronic receipt is sent, what the customer actually receives, and whether your method aligns with the rules for electronic delivery.
• Make issuance repeatable. A compliant process is one your team can perform the same way every time. Document who issues the receipt, when it is issued, how corrections or returns are handled, and where the receipt record is captured for later review.
• Validate edge cases. Run sample scenarios for partial refunds, failed payments, card-acquiring flows, courier handoff, and marketplace or internet sales. Many Ukraine PRRO receipt requirements issues appear only in exception paths.
• Keep evidence of control. Save the internal procedure, screenshots of the active receipt setup, test receipts, and role assignments. That gives accountants, controllers, and managers a practical audit trail for your receipt workflow.

Do not mix PRRO receipt compliance with adjacent regimes. A fiscal receipt under the RRO or PRRO rules is not the same thing as a VAT invoice, and it is not a substitute for SAF-T or other accounting or tax reporting files. Treat the settlement document workflow as its own control layer, then map it separately to VAT, bookkeeping, and reporting obligations.

If you need to prioritize, review three things first: the receipt template your system currently generates, the way online buyers actually receive the document, and any transaction paths that changed after March 1, 2025. That sequence usually exposes the fastest gap between your written policy and your live process.