R1 invoice: what it is, who issues it and an example (2026)

What an R1 invoice is and when it is issued, the mandatory data (buyer OIB), an example layout, and how it differs from a consumer receipt.

Published: June 25, 2026

What is an R1 invoice?

An R1 invoice is issued to a business buyer who uses it to recognize cost and deduct input VAT. It must carry the buyer's OIB.

vs consumer invoice

A B2C invoice needs no buyer data; an R1 (B2B) needs the buyer's name and OIB. From 2026 B2B is increasingly issued as a structured e-invoice.

R1 on a webshop

When a webshop buyer enters an OIB, Fiskalizator issues an R1 - as an e-invoice where required.

Example: what an R1 invoice looks like

An R1 invoice looks like any invoice, plus a mandatory buyer block. In order it contains:

  • Issuer data: name, address, OIB, VAT status.
  • Buyer data: company name, address and OIB (this is what makes it an R1).
  • Invoice number in number-premise-device format, e.g. 152-PP1-1, with date and time.
  • Line items, VAT per rate and the total.
  • JIR and ZKI when fiscalized, or the e-invoice reference when issued as an e-invoice.

Frequently asked questions

Who gets an R1?
A business buyer needing an invoice with an OIB.
Mandatory R1 data?
Buyer name and OIB plus the usual invoice data.
Is R1 the same as an e-invoice?
R1 is a type (B2B); e-invoice is a format. B2B is issued as an e-invoice from 2026.

Get compliant in 15 minutes

Fiskalizator issues fiscal receipts (JIR/ZKI) and e-invoices - for Shopify, WooCommerce or manually. 14-day free trial.

Ready to talk?Send an enquiry

A short conversation about your business. After the conversation we agree on the documentation phase and an initial proposal, before any code is written.

Email us