Skip to main content
Israel & the Middle East

B2B Software Consulting in Tel Aviv

Tel Aviv ERP buyers ship against three live clocks: Israel Tax Authority allocation numbers at NIS 5,000 since 1 June 2026, Amendment 13 enforcement since 14 August 2025, and Bank of Israel Directive 364. ERPStack, remote-first, builds those clocks into the ERP — PostgreSQL and Next.js inside AWS il-central-1, clearance inside the invoice transaction.

Quick Answer

In short: Israel's allocation-number threshold fell to NIS 5,000 on 1 June 2026, and Amendment 13 to the Protection of Privacy Law has been enforceable since 14 August 2025. ERPStack builds a Tel Aviv ERP that clears invoices against the Tax Authority API and keeps records in AWS il-central-1, 49 ms from Milan and 57 ms from Frankfurt.

Regional Compliance

  • Protection of Privacy Law 5741-1981, Amendment 13 — in force 14 August 2025
  • Privacy Protection (Data Security) Regulations 5777-2017 — basic/medium/high tiers enforced in PostgreSQL
  • EU adequacy (Decision 2011/61/EU) + Transfer of Data Abroad Regulations 5761-2001 for GDPR data
  • Israel Tax Authority allocation numbers — NIS 5,000 API clearance since 1 June 2026
  • Bank of Israel Directive 364 (December 2024) — replaces Directives 357, 361 and 363
  • SOC 2 and ISO 27001 controls built into the ERP schema — RBAC, Immutable Audit Trail

Security & Compliance Architecture

Amendment 13 to the Protection of Privacy Law, 5741-1981 came into force on 14 August 2025 and turned Tel Aviv privacy work from registration paperwork into enforcement with a price list.

Amendment 13 prices failure per database and per person

The Privacy Protection Authority can fine a controller that fails to report a severe security incident NIS 80,000 for a medium-level database and NIS 320,000 for a high-level one, charge NIS 2 per individual (NIS 4 where data is sensitive, minimum NIS 20,000) for not appointing a DPO, and up to NIS 150,000 for registration failures — doubled above a million data subjects. A Tel Aviv controller needs its ERP to expose database inventory, security level and subject counts as queryable PostgreSQL facts: the fine is computed from them.

Security level is an architecture decision taken by regulation

The Privacy Protection (Data Security) Regulations 5777-2017 grade every Israeli database as basic, medium or high and scale duties with the grade: a database definition document, a security procedure, access control and logging, periodic risk assessment, with penetration testing and external audit higher up. ERPStack makes the tier tenant metadata inside a Multi-tenant Architecture, so Role-Based Access Control (RBAC), Row-Level Security (RLS) and an Immutable Audit Trail switch on from classification — a Tel Aviv healthcare database cannot land on basic settings by accident.

European GDPR data in an Israeli region, in both directions

Israel holds an EU adequacy decision, Commission Decision 2011/61/EU, covered by the European Commission’s 15 January 2024 report on the eleven pre-GDPR adequacy decisions — so GDPR data can lawfully rest in il-central-1. Israeli law pushes the other way: the Privacy Protection (Transfer of Data to Databases Abroad) Regulations 5761-2001 permit outbound transfers only on defined grounds. ERPStack keeps residency in Terraform variables, so a Tel Aviv tenant moves between il-central-1, Microsoft Azure’s Israel Central and Frankfurt without a rewrite.

Directive 364 is what a Tel Aviv bank audits you against

Tel Aviv finance and insurance buyers are supervised under Bank of Israel Proper Conduct of Banking Business Directive 364, issued December 2024, which consolidated and replaced Directives 357 (IT management), 361 (cyber defence) and 363. Board accountability, continuous monitoring, incident response and third-party risk now sit in one instrument. ERPStack ships CI/CD Deployment Pipelines with Semgrep SAST, Vitest, Sentry and OpenTelemetry Observability, so a Tel Aviv ERP is auditable against SOC 2 and ISO 27001 rather than asserted to be.

Engineering Blueprint

Tel Aviv is one of the few markets outside the US and EU where residency is a real choice: AWS opened the Israel (Tel Aviv) Region, il-central-1, with three Availability Zones on 1 August 2023; Microsoft Azure runs Israel Central.

What an il-central-1 primary costs a multi-tenant Tel Aviv SaaS

Microsoft’s July 2026 P50 dataset puts Israel Central 49 ms from Milan, 57 ms from Frankfurt, 59 ms from London and 121 ms from East US. A Tel Aviv PostgreSQL write primary suits European users and punishes chatty American traffic: ERPStack fronts US users with read replicas and Edge Caching / CDN, and collapses chatter into one REST API round trip. Project Nimbus — the 2021 government cloud award to AWS and Google, about USD 1.2 billion — is why in-country capacity exists.

Allocation numbers put the Israel Tax Authority in your write path

Since 1 June 2026 a Tel Aviv invoice of NIS 5,000 or more excluding VAT needs an allocation number from the Israel Tax Authority before the buyer may deduct input VAT — down from NIS 10,000 on 1 January 2026, against 18 % VAT. Clearance sits inside order-to-cash: the ERP models the invoice as a PostgreSQL state machine in Drizzle ORM, validates with Zod, applies Idempotency in API Design against double documents, and ERPStack degrades to draft rather than blocking a sale.

// Zod — an ERP invoice that cannot post without ITA clearance
      export const taxInvoice = z.object({
        amountExVat: z.number().positive(),
        allocationNumber: z.string().min(1).nullable(),
      }).refine(v => v.amountExVat < 5000 || v.allocationNumber !== null,
        { message: 'ITA allocation number required at or above NIS 5,000' });

The Tel Aviv R&D centre that closes into a foreign parent

Tel Aviv’s foreign-owned R&D centres — healthcare, biotech, aerospace, agriculture and chip design — make the common build a satellite ERP settling cost-plus into a parent’s SAP S/4HANA, NetSuite or Microsoft Dynamics 365 ledger while Israeli books stay in shekels. Where the entity took Israel Innovation Authority grants under the 1984 Innovation Law, supported-product revenue carries royalties — 3 % under current directives — and moving know-how abroad needs IIA approval, so product-level revenue tagging and an R&D cost pool are ERP requirements.

Israeli ERP payroll is bracket arithmetic with a monthly ceiling

From January 2025 a Tel Aviv employer pays National Insurance to Bituach Leumi at 4.51 % up to ILS 7,703 a month and 7.6 % on the slice to ILS 51,910. Mandatory pension adds 6 % employee, 6.5 % employer and 8.33 % severance — 20.83 % of gross — while tofes 101 supplies tax-credit data and Form 126 reconciles the year to the Israel Tax Authority. The ERP holds every rate as dated PostgreSQL configuration behind one payroll API.

Evaluate Your Stack

Take our interactive audit to see if your architecture is ready for operational scale.

Start Free Audit

Regional Infrastructure

Infrastructure Region

il-central-1 (Tel Aviv)

Latency Metrics

49 ms Milan, 57 ms Frankfurt, 121 ms East US (Azure P50)

Primary Datacenter

AWS il-central-1 + Microsoft Azure Israel Central

Target Industries in Tel Aviv

Frequently Asked Questions

Microsoft’s July 2026 P50 dataset puts Israel Central 49 ms from Milan, 57 ms from Frankfurt, 59 ms from London and 121 ms from East US. For a Tel Aviv ERP one PostgreSQL primary in il-central-1 serves Europe comfortably, while ERPStack gives American users read replicas on AWS and Edge Caching / CDN rather than a second write region.

As dated brackets, never constants. From January 2025 a Tel Aviv employer pays National Insurance at 4.51 % up to ILS 7,703 of monthly income and 7.6 % on the slice to ILS 51,910, and mandatory pension adds 6 % employee, 6.5 % employer and 8.33 % severance — 20.83 % of gross. ERPStack versions every rate in PostgreSQL so a retroactive rerun reproduces the original ERP calculation.

They make product-level revenue a statutory dimension. Under the 1984 Innovation Law, revenue from IIA-supported products carries royalties — 3 % of revenue under current directives — and moving know-how out of Israel needs IIA approval. So a Tel Aviv ERP tags revenue by supported product in PostgreSQL, keeps an R&D cost pool, and can prove where source code and IP live.

If you need multi-country statutory depth quickly and your processes are conventional, SAP S/4HANA or Microsoft Dynamics 365 wins on time to value, and an honest vendor tells you that. A Tel Aviv medtech usually has the opposite profile: a regulated device and healthcare data model no ERP ships, allocation-number clearance inside the invoice path, and an EU rollout under GDPR — where a custom ERP on PostgreSQL and Next.js costs less to change than the licence costs to keep.

Yes, on the current adequacy footing. Israel holds Commission Decision 2011/61/EU, and the European Commission reported on the eleven pre-GDPR adequacy decisions on 15 January 2024, so GDPR data may rest in the AWS Israel (Tel Aviv) Region without standard contractual clauses. ERPStack still treats residency as configuration, so a Tel Aviv ERP tenant can be pinned to il-central-1 or moved to an EU region without a schema rewrite.

It is a clearance identifier issued by the Israel Tax Authority for an invoice at or above the threshold, and without it the buyer cannot deduct input VAT. Since 1 June 2026 the threshold is NIS 5,000 excluding VAT, down from NIS 10,000 on 1 January 2026. A Tel Aviv ERP must call the tax authority API inside the PostgreSQL transaction with idempotent retries, or your customer’s finance team rejects the document.

Only on defined triggers. Amendment 13 requires a DPO where the controller is a public body, where a database holds personal data on more than 10,000 subjects for transfer to third parties, where processing means regular systematic monitoring at large scale, or where especially sensitive data is processed at scale. Many Tel Aviv SaaS products cross the monitoring trigger early, so ERPStack keeps monitoring and consent flags in PostgreSQL.

Proper Conduct of Banking Business Directive 364, issued in December 2024, which consolidated and replaced Directive 357 on IT management, 361 on cyber defence management and 363. A Tel Aviv finance or insurance supplier is assessed on board accountability, continuous monitoring, incident response and third-party risk, so ERPStack builds an ERP with RBAC, an Immutable Audit Trail in PostgreSQL and CI/CD Deployment Pipelines that produce that evidence.

Priority Software, headquartered in Rosh Ha’ayin and used by over 75,000 companies in 70+ countries, already speaks Israeli VAT, allocation numbers and Israeli payroll; monday.com, headquartered on Yitzhak Sadeh in Tel Aviv, covers work management. For a conventional Tel Aviv manufacturing or logistics group they are cheaper. A custom ERP earns its place when the parent’s SAP S/4HANA ledger, defence-adjacent limits on who may hold source code, and a product model nobody sells collide.

Related reading

Explore Custom ERP Solutions by Location, Industry, and Alternatives

Global Architectures