Imagine sending a perfectly ordinary invoice to a business customer — say, ₪6,000 for a month of consulting — and getting a reply you have never seen before: "We can't pay this until it has an allocation number." Since June 1, 2026, that reply is not a quirk of one difficult customer. It is the law. Any tax invoice you issue above ₪5,000 needs a number from the Israel Tax Authority's platform printed on it, or your customer cannot deduct the VAT you charged them. No number, no deduction — and an invoice your customer cannot use is an invoice you may have to reissue, credit, and explain.
This guide walks through what the "Israel Invoice" model requires of you as an osek murshe (licensed dealer), how the threshold reached ₪5,000, and the exact routine to build into every B2B sale so your invoices keep clearing without friction.
What the Israel Invoice Model Actually Is
Israel runs a continuous transaction control model for VAT, introduced under the "Israel Invoices" reform. Since May 5, 2024, dealers have been required to apply online for an allocation number (mispar haktzaa) for qualifying tax invoices, and obtaining that number is a precondition for the customer to deduct input tax. The reform was legislated through the Economic Efficiency Law of 2023, which amended the Value Added Tax Law of 1975 to add this extra control over tax invoice issuance.
The policy target was never ordinary small businesses. The reform was built to fight black capital and, specifically, the trade in fictitious invoices — fake VAT invoices that let buyers claim input tax credits on purchases that never happened, draining the state treasury year after year. The allocation number turns every significant B2B invoice into a transaction the Tax Authority has seen and logged in near real time, which makes inventing invoices out of thin air far harder.
For you as a seller, the practical meaning is simple: above the threshold, your invoice is not a complete tax invoice until the Tax Authority has issued an allocation number for it. The number must appear on the invoice itself before it goes to the buyer.
The Threshold Schedule: How ₪25,000 Became ₪5,000
The minimum invoice sum requiring an allocation number has stepped down on a fixed timetable. All amounts exclude VAT — that detail matters more than it looks, as explained below.
| In force from | Threshold (excluding VAT) |
|---|---|
| May 5, 2024 | ₪25,000 |
| January 1, 2025 | ₪20,000 |
| January 1, 2026 | ₪10,000 |
| June 1, 2026 | ₪5,000 |
Two things about this schedule deserve attention. First, the rollout was accelerated compared with the original multi-year plan published when the reform launched, which had penciled in ₪15,000 for 2026 and would not have reached ₪5,000 until 2028. Instead, the Tax Authority cut the threshold twice within 2026 — to ₪10,000 in January and to ₪5,000 in June. If you set up your invoicing workflow around the January threshold and then stopped paying attention, June quietly pulled a whole new band of everyday invoices into scope.
Second, at ₪5,000 — roughly US$1,550 — the mandate now reaches the ordinary middle of small-business B2B life: a few days of subcontracted labor, a restock order from a wholesaler, a quarterly retainer installment, a single piece of office equipment. Invoices you used to fire off without a second thought now each need a round trip to the Tax Authority's system first.
Test every invoice against the threshold that was in force on its issue date. A March 2026 invoice is judged against ₪10,000, not ₪5,000; a July invoice against ₪5,000. And always test the VAT-exclusive amount: a ₪5,900 VAT-inclusive invoice at 18% VAT is exactly ₪5,000 before VAT, sitting precisely on the line.
Who Has to Comply — and Who Is Out of Scope
The obligation falls on dealers who issue tax invoices (cheshbonit mas) — in practice, osek murshe businesses and companies selling to VAT-registered customers. If your B2B sale exceeds the threshold, requesting the allocation number is your job as the issuer, even though the pain of a missing number lands mostly on your customer.
Osek patur (exempt) dealers are outside the reform: they issue receipts, not tax invoices, and there is no input VAT for anyone to deduct. If you are still on the exempt track, this mandate is one more item on the list of new obligations waiting for you if your turnover crosses the ₪120,000 ceiling and you convert to osek murshe.
One implication sellers routinely underestimate: because the buyer's deduction depends on your compliance, your invoicing hygiene is now part of your customer relationship. A client whose accountant flags your invoice as missing its allocation number experiences it the same way as a pricing error — your paperwork cost them money. At 18% VAT, a disqualified ₪20,000 invoice leaves ₪3,600 of input tax the buyer cannot recover. That is the kind of friction that gets a supplier quietly replaced.
What Happens Without an Allocation Number
The consequence is mechanical, not discretionary. A tax invoice above the threshold that lacks a valid allocation number is disqualified as a tax invoice, and the buyer loses the right to deduct the input VAT on that transaction entirely. The VAT becomes an irrecoverable cost baked into whatever the buyer paid you.
Note the asymmetry: the defect is created by the seller but paid for by the buyer. There is no published schedule of administrative fines attached specifically to forgetting the number — the enforcement mechanism is the disqualification itself, plus the commercial pressure from customers who need deductible invoices. That makes compliance less about fearing an inspector and more about protecting every B2B relationship you have.
If an allocation request is refused, the Tax Authority's guidance covers refusal cases, dealer notifications, alternatives, and appeal rights — so a refusal is the start of a defined process, not a dead end. Build enough lead time into your billing cycle that a refused request does not turn into a missed payment run.
The Routine: What to Do Before Every B2B Sale Over ₪5,000
Make this a checklist your billing process follows every time, not a judgment call per invoice:
- Check the amount before VAT. If the VAT-exclusive total exceeds ₪5,000 (for invoices issued on or after June 1, 2026), the invoice needs an allocation number. Build the test on the net amount in your invoicing software so nobody has to remember to strip out VAT by hand.
- Request the number through the Tax Authority's online service. Issuers apply via the authority's identification system and web application; most mainstream Israeli accounting packages can submit the request through an API as part of invoice issuance. If your software does not do this yet, that integration is now urgent, not optional.
- Print the number on the invoice before delivery. The allocation number must be integrated into the invoice before it reaches the buyer — a number obtained after the fact and emailed separately does not fix an invoice that already went out without one. Reissue properly if you catch a miss.
- Verify what you receive, not just what you send. You are also somebody's buyer. The Tax Authority provides a verification service for invoice recipients — use it, or the equivalent check in your accounting software, on every incoming supplier invoice above the threshold. A supplier's missing number is your lost deduction.
- Keep the technical specs current. The Tax Authority has released updated e-invoicing technical specifications (version 2.0), which extended allocation-number requirements to additional document types, including the Agent Tax Invoice and Journal Command. If you issue anything beyond plain tax invoices, confirm with your software provider that every affected document type is covered.
Five Mistakes That Disqualify Invoices
Most failures are boring process errors, not exotic edge cases:
- Testing the VAT-inclusive total. The threshold excludes VAT. Testing the gross amount either pulls small invoices into the process unnecessarily or — worse, if your rule is inverted — lets qualifying invoices slip through unnumbered.
- Applying the wrong year's threshold. With two different thresholds inside 2026 alone, hard-coding "₪5,000" into your process mishandles every invoice issued before June. Keep the threshold as a dated configuration, and let the invoice date pick the band.
- Treating the number as month-end paperwork. The number must be on the invoice when the buyer receives it. Batching allocation requests at month-end means every invoice you sent that month went out defective.
- Forgetting you are also a buyer. Sellers obsess over their own issuance and never check incoming supplier invoices. Run the verification on payables too, and push non-compliant suppliers to reissue before you pay.
- Assuming small suppliers are exempt. The threshold is about the invoice amount, not the size of the business issuing it. A one-person osek murshe subcontractor billing you ₪8,000 owes you an allocation number exactly like a large vendor does.
Keep Your Books Reconciliation-Ready
The allocation-number regime rewards one habit above all: reconciling issuance against records continuously instead of reconstructing everything at VAT-return time. Log each B2B invoice the day it goes out, record its allocation number alongside it, and run a simple month-end check for qualifying invoices with the number field empty. That single control catches every failure mode above while there is still time to reissue cleanly.
This is the kind of discipline that gets easier when your records are transparent and auditable rather than locked inside one person's spreadsheet. Version-controlled, human-readable books let you see invoice totals, VAT collected, and running thresholds at a glance — exactly the rigor the Tax Authority now expects behind every invoice.
Simplify Your Financial Management
As allocation-number compliance becomes part of every B2B sale, maintaining clear, complete invoicing records is essential. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready, so your books stay accurate and auditable as e-invoicing mandates keep expanding. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
