Israel Invoices: Allocation Numbers for US-Owned Firms

A US software group sets up an Israeli subsidiary, wins its first few local customers, and runs the billing out of the parent's accounting system in Chicago, the way it bills everyone else. Six months in, an Israeli client calls the finance team and refuses to pay the VAT on a NIS 40,000 invoice. The invoice, the client explains, has no allocation number, so the client cannot reclaim the 18% and will not carry the cost. Nobody in Chicago has heard of an allocation number. This is now one of the most common compliance surprises for foreign-owned Israeli companies, and it has nothing to do with tax planning and everything to do with plumbing.

Israel now checks large invoices before they are issued rather than after they are claimed. For a US owner the rule itself is simple. The difficulty is that the system was built for companies with a live Israeli presence, and a company managed from another time zone has to engineer that presence deliberately.

What the Israel Invoices Model Requires

The Israel Invoices model was introduced by the Economic Efficiency Law (Legislative Amendments for Achieving Budget Targets for 2023 and 2024) 5783-2023 and carried into Section 47 of the VAT Law 5736-1975. It requires a tax invoice above a set amount to carry an allocation number (mispar haktzaa) obtained in real time from the Israel Tax Authority.

The mechanism is unforgiving in its simplicity. Before issuing a tax invoice above the threshold to a registered Israeli business, the issuing company transmits the invoice details to the Tax Authority system and receives an allocation number in seconds, which is then printed on the invoice. The number is not a formality or a reference code you generate yourself. It is the condition on which the recipient may deduct the input VAT, so an invoice issued without one leaves your Israeli customer holding a bill on which it cannot recover 18%.

The Authority can decline to issue a number where a transaction looks irregular. When that happens the issuer has a narrow set of choices: cancel the invoice, issue it without the number and accept that the customer loses the deduction, or ask for a hearing. A declined number is a signal, not a glitch, and reissuing the same invoice in the hope of a different result is the wrong response.

The Thresholds Keep Falling

The reason a company that set up its billing correctly a year ago can be non-compliant today is that the threshold has stepped down deliberately since the model went live. Each drop pulls a wider band of ordinary invoices into the system.

| Effective date | Threshold (before VAT) | |----------------|------------------------| | May 2024 (launch) | NIS 25,000 | | 2025 | NIS 20,000 | | 1 January 2026 | NIS 10,000 | | June 2026 | NIS 5,000 |

A company that configured its invoicing once, at the NIS 25,000 launch level, and left it alone is now issuing non-compliant invoices on anything above NIS 10,000, and will be exposed on anything above NIS 5,000. The system does not warn you. Your customers do, by withholding the VAT.

In Practice: The allocation-number requirement flows from the Economic Efficiency Law 5783-2023 and Section 47 of the VAT Law 5736-1975, and is administered in real time by the Israel Tax Authority. The threshold was NIS 25,000 from May 2024, NIS 20,000 in 2025, NIS 10,000 from 1 January 2026 and NIS 5,000 from June 2026, in each case before VAT. An invoice above the threshold without a number leaves the Israeli customer unable to deduct input VAT at 18%, so on a NIS 30,000 invoice the customer is out of pocket by roughly NIS 5,400 until it is corrected, which is why the practical consequence is a stalled payment rather than a penalty notice.

Why the Plumbing Is the Hard Part for a US Owner

For a US owner the friction is entirely in the connection, not in the rule. Requesting allocation numbers requires the company to be linked to the Tax Authority's system, either through invoicing software with a certified interface or through the Authority's own portal. Access is granted to an identified Israeli representative rather than to a foreign shareholder, so the credentials sit with the company's Israeli accountant or an authorised local employee.

The real-time element is what breaks a US billing operation. A month-end batch run out of a US accounting system, disconnected from the Israeli platform, does not produce compliant invoices, because the number has to be pulled at the moment the invoice is created. A company run entirely from abroad discovers that nobody is able to press the button on a Sunday morning in Israel, the start of the Israeli business week, when a customer wants the invoice in order to close its own month. The gap between a Chicago finance calendar and an Israeli one is not cosmetic. It is the difference between an invoice that can be paid in full and one that cannot.

Two structural points matter for a US group in particular. First, intercompany invoices between the Israeli subsidiary and the US parent are outside the model where the recipient is not an Israeli registered business, so the parent's own invoices are not the problem. Invoices to Israeli customers are inside the model regardless of who owns the company. Second, this is not US sales tax and does not behave like it: there is no exemption certificate to collect and no destination-based rate to look up, only a single national VAT and a real-time gate on the invoice itself.

Whether the entity even needs to register for VAT is a prior question, and the answer differs depending on how you structured the Israeli activity. The guide to invoicing Israeli customers and VAT for foreign companies covers the registration question, and the specifics of the allocation number for a US-owned entity are set out in the answer on whether a US-owned Israeli company needs an allocation number.

Subsidiary, Branch, or Invoicing From the US Company

The invoicing obligations differ sharply depending on the vehicle. An Israeli subsidiary, incorporated in Israel and owned by the US parent, registers for VAT as an ordinary Israeli business and connects to the Israel Invoices system like any local company. A US company that invoices Israeli customers directly, without an Israeli entity, is in a different position: it generally has to appoint an Israeli VAT representative before it can operate inside the Israeli VAT system at all, which in turn is what makes allocation numbers obtainable.

In Practice: A foreign company that sells into Israel without an Israeli subsidiary generally must appoint an Israeli VAT representative under Section 60 of the VAT Law 5736-1975 before the VAT Authority will treat it as a registered dealer, and only a registered dealer connected to the system can obtain allocation numbers. VAT has stood at 18% since 1 January 2025, and appointing a representative and completing registration typically takes a few weeks, so a US company that wins an Israeli contract and expects to invoice immediately usually cannot, and should start the registration before the first large invoice falls due rather than after.

The choice between an Israeli subsidiary, a branch, and direct invoicing from the US company also drives corporate tax exposure, filing obligations, and liability, and it is worth deciding deliberately rather than by default. The trade-offs are set out in the comparison of an Israeli branch versus a subsidiary, and the VAT position should be part of that decision, not an afterthought bolted on once the customers are already there.

Common Mistake: Treating the allocation number as a one-time setup. A US-owned company that connected its billing at the NIS 25,000 launch threshold and never revisited it is, from 1 January 2026, issuing invoices above NIS 10,000 with no number, and from June 2026 the same failure reaches invoices above NIS 5,000. Because the Israeli customer cannot deduct input VAT at 18% on a numberless invoice, on a NIS 30,000 bill the customer withholds roughly NIS 5,400 and delays the whole payment, and the company only learns of the problem from its own aged-receivables report. The fix is to reconfigure the invoicing at each threshold change and to give an Israeli representative live access to the Israel Tax Authority system.

What This Means in Practice

The allocation number is a small technical step that quietly decides whether your Israeli customers can pay you in full. For a US owner the correct posture is to treat Israeli invoicing as a local function that must run on Israeli infrastructure and Israeli hours, not as a module of the parent's accounting stack. Companies that get this wrong rarely face a penalty from the Tax Authority. They face something more corrosive: a steady stream of Israeli customers holding back the VAT and paying late, which is a cash-flow problem disguised as a compliance one.

Practical Checklist

• Confirm whether you are invoicing through an Israeli subsidiary or directly from the US company, because the registration route differs
• If invoicing directly, appoint an Israeli VAT representative under Section 60 before the first large invoice falls due
• Connect the company to the Israel Tax Authority system through certified invoicing software or the Authority's portal
• Give an identified Israeli representative the credentials to obtain allocation numbers during Israeli business hours
• Reconfigure the invoicing threshold at each step-down, currently NIS 10,000 and falling to NIS 5,000 in June 2026
• Keep intercompany invoicing to the US parent separate, since it generally falls outside the model
• Treat a declined allocation number as a question about the transaction, not a reason to reissue

Speak With an Israeli Attorney

The allocation number is a minor step that decides whether your Israeli revenue arrives in full or arrives late and short. We confirm the right VAT registration for your structure, make sure the company is connected and compliant at the current threshold, and arrange the local authority and credentials so your invoicing does not depend on someone being awake in Israel.

Contact us for a confidential initial consultation.