In Ukraine, a seller that carries out a covered 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.
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.
A practical way to review Ukraine fiscal receipt requirements is to keep 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. The practical test is transaction-specific: the receipt must include the mandatory requisites that apply to that sale, return, payment method, and delivery channel.
Use four field categories when reviewing a receipt:
- Issuer and fiscal source: the seller, business unit or point of sale where relevant, and fiscal identifiers showing the document came from the proper RRO or PRRO process.
- Transaction basics: the date and time, operation type, payment method, and enough transaction detail to make the settlement auditable.
- Sale substance: the goods or services, quantity, unit price, tax lines, totals, and final amount due or paid where those fields apply.
- Scenario-specific fields: card-payment details, QR-based verification content, MAC data, or other requisites required for that transaction type.
For day-to-day compliance, do not ask only whether the receipt looks reasonable. Ask whether it matches the official receipt structure and contains all mandatory requisites for that exact transaction context.
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 changes to settlement documents. 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.
Treat the QR code and MAC as control fields. The QR code supports lookup in the RRO Accounting System, and the MAC shows the receipt was generated inside the fiscal system rather than recreated later.
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 remote sales, the control is simple: generate the receipt at the required point, deliver it through an allowed channel, and keep a copy that accounting can match to the order, payment, return, or dispute.
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.
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.
- Treat official PRRO tools as implementation aids. State Tax Service software can help execute the workflow, but it does not prove that every transaction path, receipt field, and delivery method is compliant.
- 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.
- 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.
Invoice Data Extraction
Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.
Related Articles
Explore adjacent guides and reference articles on this topic.
Slovakia eKasa Receipt Requirements: 2026 Guide
Practical 2026 guide to Slovakia's eKasa receipt rules: scope, mandatory fields, e-receipt consent, five-year retention, and the EUR 1 cashless rule.
North Macedonia Fiscalization Requirements: Cash Receipt Guide
North Macedonia fiscalization requirements explained: scope, exemptions, receipt fields, spare-register thresholds, ISK-03 fallback, and e-Faktura.
Croatia Fiscal Receipt Requirements: 2026 Guide
What a Croatian fiscal receipt or consumer invoice must include, when fiscalization applies, and how the January 1, 2026 scope change affects payment methods.