What Is a Fiscal Receipt? Definition, Rules, Bookkeeping

A fiscal receipt is a receipt issued through a cash register or point-of-sale system that has been approved and supervised by a tax authority, with the transaction recorded to the tax administration as it happens. That regulated channel — known as fiscalization — is what makes a receipt fiscal. As the IMF's how-to note on electronic fiscal reporting puts it, fiscalization is the automated reporting of a taxpayer's business activities to the tax administration. Whatever the local mechanism — certified fiscal cash register, certified POS application, electronic-receipt scheme — the seller cannot issue the receipt without the tax authority being told about the sale.

Inside the broader taxonomy of receipt types finance teams encounter, a fiscal receipt sits alongside commercial sales receipts and payment receipts, distinguished from all of them by the regulatory channel through which it has to be issued. Whether it is enough on its own for the books, or whether a tax invoice has to replace it, depends on the supplier's VAT-registration status, the type of supply, the buyer's identification, and above all the rules of the jurisdiction the receipt was issued in.

What Makes a Receipt "Fiscal" Rather Than Ordinary

Fiscalization rests on three structural elements that show up, in different configurations, in every regime that uses the term. First, the transaction has to pass through a certified device or certified software — a fiscal cash register, an approved POS application, an authorised electronic-receipt service; an uncertified till cannot legally issue the receipt at all. Second, transaction data is transmitted to the tax administration in real time or near real time, either as the sale completes or in batched submissions on a tight schedule. Third, the receipt itself carries an identifier — a serial number, a transaction code, a QR code, a fiscal memory reference — tying the printed document back to a sale already recorded in the tax authority's systems. Take any of those three away and the receipt stops being fiscal.

The identifier is the easiest signal for a finance team to recognise, and four families recur across regimes. Device or fiscal-memory identifiers anchor the receipt to a specific certified machine — Malta's EXO number is one example. Unique transaction identifiers anchor it to a specific sale; Croatia's JIR (the unique invoice identifier returned by the tax administration when the sale is reported) and ZKI (the issuer's locally computed protective-code fallback for network outages) is the cleanest case — Croatia's JIR and ZKI fiscal receipt requirements cover the detail. QR codes resolving to a tax-authority verification page make the central-record link buyer-visible; Serbia, Slovakia under eKasa, and several Western Balkan regimes use this pattern, and at volume the QR is also the most reliable cross-check when extracting Serbian fiscal receipts into a bookkeeping-ready spreadsheet. Electronic-receipt schemes that replace the paper-device model — Moldova's eBon, Slovenia's miniBlagajna, Slovakia's eKasa — let small businesses use certified software instead of certified hardware, with the same real-time submission obligations.

A printed slip with none of these signals — no device or transaction identifier, no QR resolving to a verification page, no serial tying it to a certified system — is not a fiscal receipt for any purpose, no matter how much it resembles one.

Fiscal Receipt vs Invoice: a Compliance Question, Not a Vocabulary One

Most fiscal-receipt-vs-invoice explainers stop at the generic distinction — an invoice requests payment, a receipt confirms it — and that distinction is real and well covered elsewhere. If that is all the reader needs, the generic difference between an invoice and a receipt handles it cleanly. The compliance layer is the one that explainer cannot cover, because the answer there is jurisdictional: which document the seller is legally required to issue, and which document the buyer is allowed to rely on for VAT recovery or expense substantiation, depends on the country's rules. In strict regulatory terms a fiscal receipt is not an invoice — they are distinct document types with distinct compliance functions, and whether one stands in for the other is the local regime's call.

Malta's regime is the cleanest illustration. A Maltese supplier's choice between issuing a tax invoice and a fiscal receipt depends on three variables together: the supplier's VAT-registration article status (Article 10, 11, or 12 under the Maltese VAT Act, each carrying different invoicing obligations), the type of supply, and whether the customer has provided a valid VAT identification number. Malta's rules for choosing between a tax invoice and a fiscal receipt walk through the article-by-article logic.

The Philippines' EOPT regime — the Ease of Paying Taxes Act, implemented through Revenue Regulations No. 7-2024 — frames the same choice differently. Under EOPT, the invoice is the primary tax document for both goods and services; what used to be official receipts have been recategorised as supplementary documents that do not on their own carry the same weight for input-VAT substantiation. The Philippines' invoice-versus-supplementary-document rules after EOPT show how the post-EOPT split works.

The two regimes together make the point: which document the books need is governed by the seller's country, the seller's VAT status, the supply, and the buyer's profile, in some combination set by national law. A team that defaults to "invoice and receipt are interchangeable for our books" is the team that loses input-VAT recovery in a tax review, because the regime asked for the document type the team did not keep.

When a Fiscal Receipt Is Enough for Bookkeeping

The decision a bookkeeper or AP clerk actually faces with a fiscal receipt in hand is narrower than the regulatory background suggests: post it on its own, post it but flag it for an invoice request, or refuse it until a tax invoice arrives. The right answer is jurisdictional, but the questions to work through before answering are common across regimes.

Start with what is being claimed. A fiscal receipt supporting a small expense charged to general overheads is a different decision from a fiscal receipt being used to recover input VAT, which is a different decision again from a receipt being reimbursed to an employee out of petty cash. Higher-stakes claims attract stricter document requirements almost everywhere, and input-VAT recovery is consistently the line above which regimes start to insist on a tax invoice rather than a fiscal receipt — not because the receipt is somehow defective, but because the recovery claim is a tax position the supplier-identifier and supply-detail content of an invoice is designed to substantiate.

From there, the questions chain naturally:

• Does the local regime allow input-VAT recovery from a fiscal receipt at all? Some regimes allow it for any qualifying supply; others cap it at a transaction value above which a full tax invoice becomes mandatory; others restrict it to specific supply categories — typically retail and catering.
• Does the supplier need to identify the buyer on the receipt itself for the document to support recovery? Several regimes require a buyer VAT number, a buyer business name, or both, printed on the fiscal receipt before it can be used for input-VAT recovery. A receipt without that identification supports the expense for accounting purposes but not the VAT claim — which is a different bookkeeping outcome from posting it as fully recoverable.
• For the low-value retail and catering expenses where a fiscal receipt is typically sufficient, what does sufficiency actually require? At minimum: a legible total, a recognisable supplier identifier, and the tax-authority signal that proves the receipt passed through the regulated channel. Without those, what is on the desk is a slip, not a fiscal receipt, and the decision is not really about VAT recovery — it is about whether the document supports the expense at all.

Whatever the local regime says, there is a physical-verification step before posting that is the same everywhere. Look for a device or fiscal-system identifier — the serial, the EXO, the JIR and ZKI pair, or the local equivalent. Look for a QR code or transaction code that resolves where the regime expects it to: a verification page on the tax administration's site, an SMS confirmation, an emailed link. Look for the supplier's VAT number in the form the regime requires it on the receipt. And look for a supply description specific enough to support the bookkeeping classification; "miscellaneous" on a EUR 480 receipt is a problem regardless of what else is on the document.

A receipt missing the regulated-channel signals is not a fiscal receipt for bookkeeping purposes, even when the supplier or the till has framed it that way; posting it into VAT-recoverable categories on the assumption that it counts as fiscal is exactly the kind of position a tax-authority review unwinds. When receipts from a new country start crossing the desk, pull the local tax administration's published guidance, identify the receipt type the supplier is issuing under it, and confirm what that document type supports for the claim being posted — the country-specific compliance pages on this site (Malta, Croatia, Slovakia, Slovenia, Moldova, the Western Balkan regimes) are written to answer that question for the regime they cover.