QR Invoice and QR Invoicing: How Ukrainian Businesses Bill and Get Paid in One Scan

A QR invoice is an electronic bill with a payment QR code built into it. The code carries every detail a bank needs to move money — the recipient's IBAN, the amount, the payment purpose, the tax ID, and the currency. Instead of dictating bank details over the phone or copying a 29-character IBAN by hand, the buyer opens a banking app such as Privat24 or monobank, scans the code, checks the pre-filled form, and confirms. The payment lands directly on the seller's account.

QR invoicing is the process around that artifact: generating the invoice, delivering it to the customer, and reconciling the incoming transfer. This article explains how both work in Ukraine, how the existing bank and provider solutions compare, and where a bank-agnostic service like pmnt.app fits.

QR Invoice vs QR Invoicing: One Is the Object, the Other Is the Workflow

The two terms are often used interchangeably, but they describe different things.

  • QR invoice — the document itself. A request for payment that encodes the seller's requisites and (optionally) a fixed amount inside a scannable code. It can live as an image on a screen, a printout near a till, an attachment in a chat, or a block on a web page.
  • QR invoicing — the end-to-end practice of issuing those invoices, sending them through whatever channel suits the deal, and tracking which ones got paid. For a business, invoicing is the recurring routine; the invoice is a single output of it.

The distinction matters because most tools in Ukraine optimize one side or the other. Some make a single QR fast to produce; others focus on bulk issuing, reminders, and reconciliation for a steady stream of customers.

What Sits Inside a Compliant QR Invoice

In Ukraine, payment QR codes follow a format standardized by the National Bank of Ukraine (NBU). The current generation is the V003 structure, which encodes a defined set of fields so that every compliant banking app reads them the same way:

  • IBAN of the recipient (UA + 27 characters)
  • Recipient name — company, individual entrepreneur (FOP), or private individual
  • Tax identifier — EDRPOU for companies (8 digits) or RNOKPP for individuals (10 digits)
  • Amount and currency (UAH)
  • Payment purpose — free-text reference, e.g. "Payment for order #123"
  • Reference — a structured code the receiving bank can use to reconcile the transfer

A well-formed QR invoice is not a picture of a number — it is structured data the bank decodes locally on the payer's device. That is why the buyer never types anything: the fields arrive already filled, and the only human step left is verification and confirmation.

How QR Invoicing Works End to End

The lifecycle is short and the same regardless of which tool produces the code.

  1. Create. The seller enters their IBAN, name, tax ID, payment purpose, and (usually) an amount. The tool encodes these into a V003 QR code and renders it.
  2. Deliver. The code reaches the customer in whatever way fits the situation — shown on a screen at the point of sale, printed and taped to the counter, sent as a link in Telegram or Viber, embedded on a checkout page, or posted on social media.
  3. Scan. The customer opens any Ukrainian banking app, taps the QR scanner, and points the camera at the code. The transfer form auto-fills.
  4. Confirm. The customer reviews the recipient, amount, and purpose, picks the card or account to pay from, and authorizes with PIN, fingerprint, or Face ID.
  5. Settle. Money moves directly between the two banks. Through the upgraded electronic payment system (SEP-4.1), instant transfers settle within roughly ten seconds, around the clock. Larger or special transfers route through standard channels and typically complete within an hour.

There is no terminal, no card data, and no payment intermediary holding the funds in transit.

The Existing QR Invoicing Solutions in Ukraine

Several banks and providers already offer some form of QR invoicing. Each is built around its own account, app, or acquiring contract.

NovaPay — Fast Invoices for FOP in the App

NovaPay added quick invoice generation for individual entrepreneurs directly inside its app, letting a FOP produce a payment request in a few taps and send it to a customer. It is convenient for sellers who already run their finances through the NovaPay ecosystem, with settlement into a NovaPay account.

PrivatBank — Invoicing for Business Clients

PrivatBank offers invoicing tools for its business customers, including QR-based payment acceptance and links that open a pre-filled transfer. The flow is tightly integrated with PrivatBank's business accounts and, where acquiring is involved, with its acquiring rates.

Raiffeisen Bank — Pay-by-Link, Chatbot, and E-Invoicing

Raiffeisen bundles several acceptance methods around its "Rakhunok 907" acquiring product: pay-by-link, a chatbot for issuing requests, and e-invoicing. These cover card acceptance and electronic billing, and they are aimed at merchants holding a Raiffeisen acquiring agreement.

4bill.io — QR Payments as a Payment Method

4bill.io provides QR payments as one of its supported acceptance methods within a broader payment-service offering, oriented toward online merchants that want QR alongside cards and other rails.

How They Compare

Solution Account requirement Typical cost model Best fit
NovaPay invoices NovaPay account Provider terms FOPs inside the NovaPay ecosystem
PrivatBank invoicing PrivatBank business account Acquiring/account terms Existing PrivatBank merchants
Raiffeisen 907 (pay-by-link, e-invoicing) Raiffeisen acquiring Acquiring commission Merchants on a Raiffeisen contract
4bill.io QR 4bill.io onboarding Provider/PSP terms Online stores wanting mixed rails
pmnt.app Any IBAN, any bank 0% merchant commission Bank-agnostic QR invoicing

The common thread among the bank and PSP options is lock-in: the invoicing capability is attached to a specific bank account, acquiring contract, or onboarding. That is reasonable for a business already committed to that provider, but it ties the workflow to one institution and, in the acquiring cases, to a per-transaction commission.

Where a Bank-Agnostic Service Fits

pmnt.app takes a different starting point: the invoice is built around the seller's IBAN, not around a particular bank's product. Because the payment is an ordinary interbank transfer rather than card acquiring, the model differs in a few practical ways.

  • Any Ukrainian bank works. The seller can hold their account anywhere; the payer can pay from any banking app that supports the NBU QR standard. Neither side has to share a bank.
  • No merchant commission. A direct IBAN transfer carries no acquiring percentage, so the seller receives the full invoice amount. The payer pays only their own bank's transfer fee, which for hryvnia transfers is often zero.
  • No fiscal hardware. There is no POS terminal to buy, rent, or service, and no card data passing through merchant systems.
  • Multiple ways to issue. Invoices can be created through the web interface, a Telegram bot, an API for automated systems, or an MCP server for AI assistants — useful when invoicing needs to be wired into an existing tool rather than done by hand.

This does not make pmnt.app strictly better than a bank's offering for every business. It makes it a fit for sellers who want QR invoicing without committing to one bank's account or paying acquiring on each sale.

A Note on Fiscalization

Accepting an IBAN transfer through a QR invoice is not acquiring, and the QR code itself does not perform fiscalization. Where a business is legally required to fiscalize a sale, that obligation is handled separately through an RRO or software RRO (PRRO), independent of how the payment was requested. QR invoicing changes how the customer pays — it does not, on its own, remove or satisfy a fiscalization requirement that already applies to the transaction. Treat the payment channel and the fiscal duty as two separate questions.

Practical Limits

QR invoicing is well suited to most retail and small-business situations, but a few boundaries are worth knowing.

  • Instant-transfer ceiling. Instant settlement through SEP-4.1 covers transfers up to 100,000 UAH; amounts above that route through standard channels and may take up to about an hour.
  • Transfer limits for individuals. Under the Ukrainian banks' memorandum, monthly limits apply to P2P and IBAN transfers for private individuals. Transfers to business accounts of FOPs and legal entities are treated differently.
  • Hryvnia only. The current QR invoicing flow is built for UAH. Foreign-currency settlement uses other methods.
  • Internet and a banking app required. The payer needs an online connection and a banking app at the moment of payment; offline scanning is not supported.

Who Benefits Most from QR Invoicing

  • FOPs and freelancers who bill a handful of clients and want the money on their own IBAN without a terminal or a monthly fee.
  • Service businesses — salons, tutors, repair shops — that issue a request and get paid on the spot.
  • Online sellers who want to add a commission-free option alongside cards, or who sell through chat and social media where a link or image is the natural delivery channel.
  • Market and fair traders who can print one static QR invoice and accept payments without owning a smartphone at the stall.

Conclusion

A QR invoice collapses the act of billing into a single scan: the seller's full requisites travel inside the code, the buyer's app fills the form, and the transfer settles directly between banks. QR invoicing is the routine that surrounds it — issuing, delivering, and reconciling those requests at whatever volume a business runs.

Ukraine already has capable bank and provider offerings — NovaPay, PrivatBank, Raiffeisen's 907, 4bill.io — each strong for businesses already inside its ecosystem. The trade-off they share is attachment to a specific account or acquiring contract. A bank-agnostic, commission-free approach like pmnt.app suits sellers who would rather build invoicing around their own IBAN, accept payment from any Ukrainian bank, and keep the full amount of every invoice. The right choice depends on where a business already banks and whether it values integration with one provider over independence from all of them.