Country deep dive
Israel's mandate was legislated in 2023 but rolled out via a shrinking invoice threshold rather than taxpayer-size waves: a genuine no-rejection pilot from May 2024 above NIS 25,000, tightening enforcement from January 2025 at NIS 20,000, then an acceleration announced in December 2025 that compressed the remaining five-year rollout into two, reaching NIS 10,000 in January 2026 and the permanent floor of NIS 5,000 in June 2026.
Israel's Economic Efficiency Law (Budget Amendments) for 2023-2024 amended the VAT Law 1975 to introduce a real-time invoice clearance system via temporary provisions, with the Ministry of Finance empowered to extend the regime. The law took effect 1 January 2024, though implementation was postponed due to the security situation at the time.
The SHAAM clearance platform went live for domestic B2B invoices exceeding NIS 25,000 (excluding VAT). This was a genuine pilot: every valid request received an allocation number automatically in 2024, with no rejections for content reasons, giving businesses a low-risk period to build out submission processes.
The mandatory threshold fell to NIS 20,000, and the pilot's no-rejection grace ended: the ITA gained the ability to scrutinize submissions and refuse allocation numbers for invoices it deems irregular, with a formal review and hearing process available within 2 business days of a refusal.
The threshold fell to NIS 10,000, skipping the NIS 15,000 step originally planned -- part of a December 2025 acceleration under the Law for Achieving Budgetary Goals and Implementing Economic Policy for the 2025 Fiscal Year, which compressed what was legislated as a five-year rollout through 2028 into two years, ending mid-2026.
The threshold reached its final, permanent floor of NIS 5,000 (excluding VAT) -- no further reductions are currently scheduled. This completes the accelerated rollout roughly 18 months earlier than originally legislated, and brings the large majority of domestic B2B invoices into scope.
SHAAM invoices are submitted as structured JSON via API, or entered manually through the ITA's web portal — there is no separate legacy Israeli schema, and no UBL or XML authoring step as seen in some other mandates in this tracker.
There is no invoice-authoring standard to learn here comparable to UBL or Peppol — the integration work is almost entirely about the API connection and field mapping, since the underlying format is plain structured JSON.
The Accounting_Software_Number field matters specifically for businesses using accredited accounting software rather than a custom integration — confirm with your software vendor whether this is populated automatically.
The absence of a line-item submission requirement is a genuine simplification compared to peer mandates -- but the 7-year retention period and Section 40B contingency process still deserve real process design, not an afterthought.
Israel's mandate is domestic B2B only: it applies to invoices between VAT-registered businesses inside Israel above the current threshold. B2C, B2G, and cross-border (export/import) transactions are explicitly out of scope — a narrower reach than most CTC mandates covered in this tracker.
The threshold-based rollout is a genuinely different mechanic from every other mandate in this tracker -- there are no taxpayer-size waves here, just a shrinking invoice-value floor that eventually catches nearly all domestic B2B activity.
This narrower B2B-only scope is worth double-checking against your own transaction mix -- a business with mostly B2C or export revenue may have far less SHAAM exposure than the headline "mandatory e-invoicing" framing suggests.
Every in-scope SHAAM invoice moves through the same sequence:
The buyer needs a valid allocation number on the invoice before they can deduct the input VAT -- this is what makes SHAAM a genuine clearance model rather than a post-transaction reporting system.
Getting compliant means confirming whether your invoice volumes clear the current threshold, choosing a submission route, mapping your invoice data to SHAAM's required fields, and building in contingency handling for when the system or your connection is unavailable.
Check your typical domestic B2B invoice values against the current NIS 5,000 floor -- remember B2C, B2G, and cross-border invoices are out of scope regardless of value.
Higher-volume businesses should integrate directly via the SHAAM API; the free gov.il manual portal suits lower-volume submitters without in-house development resources.
Line-item detail isn't required in the initial submission, which simplifies the mapping compared to peer mandates -- but taxpayer identity and invoice-value fields still need to be accurate.
If you submit through accredited accounting software rather than a custom integration, confirm this field is populated correctly -- check with your software vendor rather than assuming.
Section 40B allows retroactive allocation-number requests when SHAAM or your own systems are unavailable -- design this handling in advance rather than improvising during an outage.
Confirm your VAT return process references the allocation numbers correctly -- an invoice without one is not just a compliance risk, it blocks your customer's input VAT deduction.
Israel has no published, quantified fine schedule for SHAAM non-compliance. Instead, enforcement runs through the VAT system itself: from 2025, the ITA can refuse to issue an allocation number for an irregular invoice, and without a valid allocation number the buyer cannot deduct the input VAT — turning invoice compliance into a precondition for tax recovery rather than a separately fined offense.
Other countries in the same region, ordered by their next dated milestone. Each links to a full briefing.