Israel

What the pack carries

Charts of accountsWhat a company installs, and who each chart is published for.

• default (default) — 123 accounts, for companies

TaxesHow many the pack carries, at which distinct rates, and which treatments it can express.

11 taxes at rates of 0, 18

domestic, exempt, export, foreign_services_received, import

Periodic declarationThe form the accounts are read into, the cadences it is filed on, and how many boxes it has.

• IL-VAT-PERIODIC — 15 boxes, filed month or bimonth

When it is dueA rule of the country, not a date. A pack that cannot state its rule states nothing.

• day 23 of the month after the period

The file it is deposited asThe brick of packages/formats that writes it, where one exists.

• filed by hand on the administration’s portal

Electronic invoicingThe profile the country imposes, the day it starts, and the text that imposes it.

no profile — no obligation in law

No statute this pack's research found obliges an Israeli business to exchange a structured electronic invoice — a Peppol-style document a buyer's software can read — with another business. What the Economic Efficiency Law (Legislative Amendments to Achieve the Budget Targets for the 2023 and 2024 Budget Years), 5783-2023 requires instead, from 1 January 2024, is a real-time control of a different shape: a seller who wants a buyer to be able to deduct the input tax of a tax invoice above a declining threshold must first request an 'allocation number' (מספר הקצאה) from the Tax Authority's own system for that specific invoice, and print it on the document — the threshold itself falling from NIS 25,000 in May 2024 to NIS 20,000 from 1 January 2025, NIS 10,000 from 1 January 2026 and NIS 5,000 from 1 June 2026. The invoice a buyer receives is not itself required to be a structured document of any named format; the control is an authorisation number requested and returned over the Tax Authority's own API before or when the invoice is issued, closer to a real-time clearance model than to a Peppol exchange. This pack format has a field for the profile of a structured invoice exchanged between two parties and none for a clearance control of this shape, so `profile` and `mandatory_from` stay empty rather than naming something this is not; the allocation-number regime itself is documented in this pack's README and in docs/international.md under "Israel", and is not patched into the schema.

Where the tax balance landsThe accounts a filed declaration settles to, by role.

• payable 2110
• receivable 1155

Bank statementsThe formats this country’s banks send, and whether anything here reads them.

no format named

Payment filesThe formats the country’s banks accept for an outgoing payment.

no format named

Financial statementsThe schemes the chart reports on, and the taxonomy their keys are written against.

• IL-IAS1-SFP — 23 lines
• IL-IAS1-IS — 9 lines

Who has read itA pack is reviewed when a named professional has read it against the law, and never before.

community no named reviewer

11 sources cited

Last checked against the lawThe most recent day somebody opened one of the texts the pack was built from.

2026-09-25

Pack versionWhat this pack calls itself, the day it says its transcription is true, and the languages it publishes.

0.3.0 — published 2026-10-23

he, en

Free, and operated

Where the open core stops.

The line is operational, not functional. Everything that keeps working on its own is open core; what needs credentials, a certificate or a channel somebody keeps running is the hosted edition.

What it was built from

Partners