Guide to Israel's six financial document types: tax invoices, receipts, pro-forma invoices, credit invoices. Tax point rules, mandatory fields, e-invoicing.
Israel's financial document system operates under a taxonomy defined by the Israel Tax Authority (Rashut HaMisim) that bears little resemblance to the invoice categories used in most other countries. Where many Western systems distinguish broadly between invoices, receipts, and credit notes, Israel mandates a set of legally distinct document types, each carrying specific VAT and tax point implications. If you're familiar with a general guide to invoice types used worldwide, you'll find that Israel's categories don't map neatly onto those international conventions.
Six main financial document types form the backbone of Israel's system:
| Document | Hebrew Name | Creates a Tax Point? |
|---|---|---|
| Tax invoice | Heshbonit mas | Yes — triggers VAT liability |
| Tax invoice-receipt | Heshbonit mas kabala | Yes — combines invoice and payment confirmation |
| Pro-forma invoice | Heshbon iska | No |
| Receipt | Kabala | No — confirms payment received |
| Credit invoice | Heshbonit zikui | Yes (reversal) — reverses a prior tax invoice |
| Agent tax invoice | Heshbonit mas sochen | Yes — issued by agents on behalf of principals |
The distinction between a tax invoice and a receipt is not merely procedural. A heshbonit mas creates a tax point, the moment at which VAT liability crystallizes for the transaction. Issuing the wrong document, or issuing one at the wrong time, can result in incorrect VAT reporting and penalties from Rashut HaMisim. The heshbon iska (pro-forma invoice), by contrast, carries no tax point at all, making it suitable for price quotations and pre-payment documentation without triggering any VAT obligation.
Not every Israeli business can issue every document type. The documents available to you depend on whether your business is registered as an Osek Murshe (authorized dealer, VAT-registered) or an Osek Patur (exempt dealer, below the revenue threshold). This registration category determines your document permissions and, by extension, your VAT reporting obligations.
Israel's tax document landscape is also shifting. A national e-invoicing mandate now requires businesses to obtain a SHAAM allocation number for tax invoices above certain thresholds, adding a digital verification layer to several of these document types. If you need to quickly determine which document to issue for a specific transaction, the decision framework in the final section provides a scannable reference.
The Tax Invoice (Heshbonit Mas): Fields, Rules, and Tax Point
The heshbonit mas is Israel's primary commercial document for business-to-business transactions. Only VAT-registered businesses, known as Osek Murshe, are authorized to issue tax invoices. For any professional dealing with Israeli commercial documentation, understanding this document's requirements is non-negotiable.
What makes the heshbonit mas consequential is the tax point it creates. The moment a tax invoice is issued, it triggers an immediate tax point, establishing both VAT liability at the current rate of 18% and income tax reporting obligations. This means the act of issuing the document itself carries legal weight with the Israel Tax Authority (Rashut HaMisim). There is no mechanism to retract or defer the tax obligation once the document is issued.
Mandatory Fields
Every Israeli tax invoice must contain the following elements to be considered valid:
- Supplier name and address
- Buyer name and address
- Supplier VAT number (identifying the business for Israel VAT, or Ma'am, purposes)
- The words "Tax Invoice" and "Authorized Entrepreneur" printed in Hebrew (חשבונית מס and עוסק מורשה)
- Transaction details, including a description of goods or services, quantities, and amounts
- VAT amount calculated at the current rate of 18% (as of January 2025), shown as a separate line item
A tax invoice missing any of these fields can be rejected by the buyer's accountant, and the buyer may lose the right to claim the input VAT credit. If you are processing received Israeli invoices, checking against this list should be standard practice — the full scope of Israel's VAT invoice field and compliance requirements extends further for foreign businesses dealing with Hebrew formatting, reverse charge scenarios, and SHAAM allocation numbers.
The 14-Day Rule
Israeli tax law requires that a heshbonit mas be issued within 14 days of a taxable supply or cash settlement, whichever comes first. Missing this window does not eliminate the tax obligation, but it does create a compliance exposure. The Israel Tax Authority expects timely documentation, and late issuance can draw scrutiny during audits.
Language and Currency Requirements
Tax invoices for domestic transactions must be written in Hebrew. When a transaction involves foreign currency, the invoice must still display the NIS equivalent alongside the foreign amount, together with the conversion rate used. This dual-display requirement ensures that the VAT calculation is traceable back to the shekel amount on which it was assessed.
SHAAM Allocation Number for High-Value Transactions
For B2B transactions exceeding the current threshold, the tax invoice must include a SHAAM allocation number obtained through Israel's e-invoicing mandate. This system, administered by the Israel Tax Authority, adds a verification layer to prevent fraudulent invoices. The allocation number confirms the invoice has been registered before payment is made.
Withholding Tax Interactions
Israeli tax invoices also intersect with withholding tax requirements in certain scenarios. When businesses make payments to service providers, they may be required to withhold a percentage of the payment and remit it directly to the tax authority. This is particularly relevant for freelancers and contractors operating as Osek Murshe. For a detailed breakdown of how withholding tax works on Israeli invoices, the rules vary based on the provider's withholding tax certificate and the nature of the service.
Tax Invoice-Receipt and Pro-Forma Invoice: Two Key Alternatives
Not every transaction follows the standard pattern of issuing a tax invoice now and collecting payment later. Two document types address the most common alternatives: the tax invoice-receipt for transactions where payment happens immediately, and the pro-forma invoice for situations where you want to document a transaction without triggering tax obligations.
Tax Invoice-Receipt (Heshbonit Mas Kabala)
The Israel heshbonit mas kabala is a combined document that functions as both a tax invoice and a payment confirmation in a single form. Instead of generating two separate documents, the tax invoice-receipt creates a tax point and confirms payment simultaneously.
This combined format is standard in retail and service environments where the customer pays at the point of sale or upon delivery. A restaurant meal, a consulting session paid on completion, a retail purchase — these are all natural fits for the heshbonit mas kabala rather than separate paperwork.
The document carries the same mandatory fields as a standard tax invoice (supplier and buyer details, VAT registration numbers, itemized descriptions, VAT amounts) plus payment confirmation details such as payment method, amount received, and date of payment.
When to use the combined form vs. separate documents: If your customer pays at the time of the transaction, the tax invoice-receipt is the more efficient choice — one document instead of two. Separate tax invoice and receipt documents are necessary when invoicing and payment occur at different times, such as net-30 payment terms. In those cases, you issue the tax invoice at the point of sale or service delivery, then issue a standalone receipt (kabala) once payment arrives.
Pro-Forma Invoice (Heshbon Iska)
The Israel heshbon iska proforma invoice occupies a fundamentally different role in Israel's document hierarchy. Its defining characteristic is that it does not create a tax point. This single distinction separates it from every other transactional document in the system.
By issuing a heshbon iska instead of a tax invoice, the seller defers both income tax and VAT obligations until payment is actually received. This makes it a practical tool for quotes, estimates, and transactions where the seller wants to document the arrangement without immediately triggering tax liabilities.
However, this deferral comes with a critical limitation for the buyer: the recipient cannot claim input VAT from a pro-forma invoice. In B2B transactions where the purchasing business needs a VAT deduction, this matters directly. A buyer who receives only a heshbon iska has no document that supports an input VAT claim — which can create friction in negotiations or require follow-up documentation.
The pro-forma invoice is not a final document. Once payment is received, the seller must issue a proper tax invoice or tax invoice-receipt to formalize the tax point. Only then does the transaction enter the tax system, and only then can the buyer use the document for VAT recovery. Understanding the Israel tax invoice vs receipt distinction here is essential: the heshbon iska is a placeholder, not a substitute for the documents that carry actual tax authority.
Receipts (Kabala) and Credit Invoices (Heshbonit Zikui)
Beyond tax invoices and their variants, two other document types appear constantly in Israeli transactions: the kabala (receipt) and the heshbonit zikui (credit invoice). Both serve distinct legal functions, and understanding them is essential for anyone processing Israeli financial documents.
The Receipt (Kabala)
A kabala is a confirmation that payment has been received. It acknowledges the transfer of funds from buyer to seller and serves as the payer's proof of payment — but it does not contain VAT charges or create a tax point.
The critical rule: every Israeli business must issue a kabala when payment is received, regardless of registration category. This includes VAT-exempt small businesses (Osek Patur) that cannot issue tax invoices. For an Osek Patur, the receipt is the minimum and often the only financial document they are authorized to provide. If you receive payment and operate any type of registered business in Israel, you are legally obligated to issue a receipt.
In practice, many businesses combine the receipt with a tax invoice into a single tax invoice-receipt (covered in the previous section). But when these documents are issued separately — for example, when a tax invoice is sent at the time of supply and payment arrives weeks later — the kabala stands on its own as the payment confirmation.
The Credit Invoice (Heshbonit Zikui)
A heshbonit zikui functions as Israel's equivalent of a credit note. It exists for one purpose: to reverse or adjust a previously issued tax invoice.
When a seller issues a credit invoice, it creates a negative tax point — effectively unwinding the VAT liability and income tax implications recorded on the original document. The VAT that was charged on the original invoice is reversed, and both parties adjust their records accordingly.
Common scenarios that require a heshbonit zikui include:
- Returned goods where the original transaction is fully or partially reversed
- Pricing corrections after an invoice was issued with an incorrect amount
- Partial cancellations of previously invoiced services or deliveries
- Negotiated discounts applied retroactively to a completed transaction
Under Israel's new e-invoicing framework, a credit invoice must reference the allocation number of the original invoice it is reversing. This traceability requirement ensures that the tax authority can match every reversal to its source transaction, closing a historical gap that made VAT fraud through fictitious credit notes difficult to detect.
If you encounter a heshbonit zikui from an Israeli supplier or client, treat it as a formal reversal with direct VAT and income tax consequences for both parties — not as a routine credit memo.
Osek Murshe vs Osek Patur: Document Permissions by Business Type
Israel's VAT law creates two distinct business registration categories, and the category you fall under determines exactly which financial documents you are authorized to issue. Getting this wrong has real consequences — issuing a document you're not permitted to create renders it invalid, and the other party cannot rely on it for VAT deductions.
Osek Murshe (Authorized Dealer)
An Osek Murshe is a VAT-registered dealer with full document-issuing authority. This category is required for any business exceeding the Osek Patur revenue threshold, and certain regulated professions must register as Osek Murshe regardless of revenue.
Key obligations and permissions:
- Can issue all document types: tax invoices (heshbonit mas), tax invoice-receipts, receipts, credit invoices, and pro-forma invoices.
- Must charge 18% VAT on taxable transactions.
- Files bi-monthly VAT returns with the Israel Tax Authority.
- Entitled to claim input VAT deductions on business purchases.
Osek Patur (Exempt Dealer)
An Osek Patur is a small business with annual revenue under NIS 120,000 that operates with a simplified tax burden — but significantly restricted document permissions.
Key restrictions:
- Can only issue receipts (kabalot) and pro-forma invoices (heshbon iska).
- Cannot issue tax invoices. This is the single most important distinction.
- Cannot charge VAT on transactions.
- Cannot claim input VAT deductions on purchases.
- Certain professions — including architects, doctors, teachers, and lawyers — are barred from Osek Patur registration regardless of how low their revenue is.
Document Permission Matrix: Osek Murshe vs Osek Patur Invoices
| Document Type | Osek Murshe | Osek Patur |
|---|---|---|
| Tax Invoice (Heshbonit Mas) | Yes | No |
| Tax Invoice-Receipt (Heshbonit Mas/Kabala) | Yes | No |
| Receipt (Kabala) | Yes | Yes |
| Credit Invoice (Heshbonit Zikui) | Yes | No |
| Pro-Forma Invoice (Heshbon Iska) | Yes | Yes |
| Charges VAT | Yes (18%) | No |
| Claims Input VAT | Yes | No |
Why This Matters: Validation in Practice
If a vendor registered as Osek Patur hands you a tax invoice, that document is invalid. An Osek Patur has no legal authority to issue tax invoices or charge VAT. Any VAT amount shown on such a document is fictitious, and the buyer cannot claim an input VAT deduction based on it. Before accepting a tax invoice from any vendor, verify their registration status — the consequences of relying on an invalid document fall on the buyer as well as the seller.
Transitioning Between Categories
Many businesses start as Osek Patur and transition to Osek Murshe as their revenue grows past the NIS 120,000 threshold. This shift changes your entire document workflow: you gain the ability to issue tax invoices and charge VAT, but you also take on bi-monthly VAT reporting obligations and must update your invoicing systems to include all mandatory tax invoice fields. A detailed comparison of the invoicing obligations for each registration category covers the VAT treatment, document requirements, and SHAAM implications that differ between the two. Planning for this transition in advance — setting up compliant invoice templates and understanding your new reporting schedule — prevents disruption when the change takes effect.
Israel's E-Invoicing Mandate and the SHAAM Allocation Number System
Israel's document taxonomy now operates within a digital verification framework that has fundamentally changed how invoices are issued. The SHAAM allocation number system, operated by the Israel Tax Authority (Rashut HaMisim), requires businesses to obtain a unique verification number for qualifying invoices in real time before issuing them to the recipient. Each allocation number confirms that the Tax Authority has reviewed and approved the transaction, creating an auditable trail from the moment an invoice is generated.
Three document types require a SHAAM allocation number when they exceed the threshold amount: tax invoices (heshbonit mas), credit invoices (heshbonit zikui), and agent tax invoices (heshbonit mas sochen). Receipts (kabalot) and pro-forma invoices (heshbon iska) fall outside the allocation number requirement regardless of amount. For a deeper look at the verification process and compliance steps, see the full guide on Israel's e-invoicing allocation number requirements.
The threshold has been deliberately reduced over time to bring more transactions under scrutiny. When the system launched, only invoices above NIS 25,000 required allocation numbers. That figure has since dropped in stages, and the Tax Authority's published roadmap signals further reductions ahead. Each threshold cut means a larger share of routine business invoices must pass through real-time verification, expanding the system's coverage across the economy.
The Agent Tax Invoice (Heshbonit Mas Sochen) is a relatively recent addition to Israel's document taxonomy, introduced as part of the Tax Authority's version 2.0 e-invoicing specifications. This document type applies when an agent or intermediary issues a tax invoice on behalf of a principal — a common arrangement in sectors like real estate, advertising, and import/export brokerage. The agent tax invoice carries the same VAT implications as a standard tax invoice but includes additional fields identifying both the agent and the principal. Like other qualifying documents, it requires a SHAAM allocation number when the invoice amount exceeds the current threshold.
The stakes behind this verification infrastructure are substantial. According to The Jerusalem Post's reporting on Israel's invoice fraud prevention efforts, the Tax Authority reported that fictitious invoice transactions worth NIS 8 billion were thwarted in 2024 through the allocation number system. That figure underscores why Israel treats document classification with such rigor — each document type's rules around issuance, VAT treatment, and input tax deductions are now reinforced by a digital layer designed to catch fraud before it enters the books.
For businesses operating in Israel, the practical effect is that issuing the correct document type is no longer just a tax compliance matter. Every tax invoice, credit invoice, and agent tax invoice above the threshold must clear the SHAAM system before it reaches the customer. Accounting software and ERP systems need to integrate with the Tax Authority's API, and manual invoicing workflows must account for the verification step. Getting the document type wrong — or attempting to issue without an allocation number when one is required — can result in the invoice being rejected outright.
Which Document Do You Need? A Quick Reference
Choosing the correct Israeli financial document comes down to three questions: what is the transaction, when is payment happening, and what is your VAT registration status?
| Scenario | Document to Issue |
|---|---|
| Selling goods/services to another business with standard tax reporting | Tax invoice (heshbonit mas) — creates a tax point and triggers VAT reporting |
| Payment occurs at the point of sale | Tax invoice-receipt (heshbonit mas kabala) — combines invoice and payment confirmation in one document |
| You need to document a transaction but defer tax obligations | Pro-forma invoice (heshbon iska) — no tax point; formal tax invoice follows when payment is made |
| You received payment and need to confirm it | Receipt (kabala) — mandatory record-keeping document; does not create a VAT obligation |
| You need to reverse or adjust a previously issued invoice | Credit invoice (heshbonit zikui) — issues a negative amount, adjusting the VAT reported |
| You are issuing an invoice on behalf of another party | Agent tax invoice (heshbonit mas sochen) — used when an intermediary invoices on behalf of a principal |
Consolidated Document Comparison
The table below brings all six document types into a single reference. No column is redundant — each captures a distinction that matters for compliance and processing.
| Document Type | Hebrew Name | Creates Tax Point | Requires SHAAM Allocation Number | Who Can Issue |
|---|---|---|---|---|
| Tax Invoice | Heshbonit Mas | Yes | Yes (above threshold) | Osek Murshe only |
| Tax Invoice-Receipt | Heshbonit Mas Kabala | Yes | Yes (above threshold) | Osek Murshe only |
| Pro-Forma Invoice | Heshbon Iska | No | No | Both Osek Murshe and Osek Patur |
| Receipt | Kabala | No | No | Both Osek Murshe and Osek Patur |
| Credit Invoice | Heshbonit Zikui | Yes (reversal) | Yes (above threshold) | Osek Murshe only |
| Agent Tax Invoice | Heshbonit Mas Sochen | Yes | Yes (above threshold) | Osek Murshe only |
Key takeaway from the table: Only an Osek Murshe can issue documents that create a tax point. Osek Patur businesses are limited to pro-forma invoices and receipts. The SHAAM allocation number requirement applies to tax-point documents that exceed the monetary threshold set by the Israel Tax Authority.
Correctly identifying which document type you are dealing with is the first step in processing Israeli financial documents, whether for bookkeeping, tax compliance, or data extraction. Organizations that handle Israeli documents at volume may benefit from tools for extracting data from Israeli financial documents that support Hebrew and right-to-left document formats.
Related Articles
Israel VAT Invoice Requirements: Complete 2026 Guide
Complete guide to Israeli VAT invoice requirements for foreign businesses. Covers the 18% rate, mandatory fields, Hebrew requirements, reverse charge, and SHAAM allocation numbers.
Poland White List (Biała Lista): VAT Verification Guide
How to verify supplier bank accounts on Poland's White List. Covers the PLN 15,000 threshold, sanctions, recovery options, and AP workflow integration.
Israel Osek Patur vs Osek Murshe: Invoicing Requirements Explained
Side-by-side comparison of Israel's Osek Patur, Osek Murshe, and Osek Zair invoicing rules, VAT treatment, the NIS 120,000 threshold, and SHAAM e-invoicing impact.
Invoice Data Extraction
Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.