israeli-e-invoice

Generate and validate Israeli e-invoices per SHAAM Tax Authority standards.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/amitpo23/cfo --skill israeli-e-invoice-amitpo23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: israeli-e-invoice
Source: https://github.com/amitpo23/cfo/tree/main/.claude/skills/israeli-e-invoice
Command: npx skills add https://github.com/amitpo23/cfo --skill israeli-e-invoice-amitpo23

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Issuing legally valid invoices in Israel requires choosing the correct document type, calculating 18% VAT correctly, validating 9-digit TINs, and obtaining SHAAM allocation numbers above progressive thresholds—mistakes make invoices invalid for tax deduction. ## Core Features & Use Cases - Invoice Type Selection: Guides users through Israeli document types 300 (tax invoice), 305 (tax invoice/receipt), 310 (credit invoice), 320 (receipt), and 330 (proforma) with required fields per type. - Compliance Validation: The bundled Python script checks TIN check digits, VAT calculations, invoice dates, and allocation number requirements against date-based thresholds (25,000 NIS down to 5,000 NIS from June 2026). - SHAAM API Guidance: Reference documentation covers allocation number requests, authentication, and error codes for the Israel Tax Authority API. - Use Case: A user asks to create a 15,000 NIS B2B tax invoice; the Skill calculates VAT (2,700 NIS), determines an allocation number is required, and produces a compliant invoice document. ## Quick Start Ask the assistant to create an Israeli tax invoice for a specific amount and client, providing seller and buyer business details.

Frequently Asked Questions about israeli-e-invoice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Israeli tax invoice with an allocation number?

Determine the invoice type (300, 305, or 310), collect seller and buyer details, calculate 18% VAT, then check if the net amount exceeds the current threshold. If it does, request an allocation number from the SHAAM API before issuing the invoice.

What is the Israeli e-invoice allocation number threshold in 2026?

From January to May 2026 the threshold is 10,000 NIS net; from June 1, 2026 it drops to 5,000 NIS net, excluding VAT. Tax invoices (types 300, 305, 310) above the threshold must carry a SHAAM allocation number.

How do I validate an Israeli TIN (mispar osek)?

An Israeli TIN is 9 digits with a weighted check digit: multiply digits by alternating weights 1 and 2, sum the digit products, and verify the total is divisible by 10. The bundled validate_invoice.py script performs this check automatically.

What is the difference between invoice type 300 and 305 in Israel?

Type 300 is a standard tax invoice for B2B sales with later payment, while type 305 combines a tax invoice and receipt for transactions with immediate payment. Both require allocation numbers above the threshold but have different legal implications for payment timing.

When is a SHAAM allocation number not required?

Allocation numbers are never required for receipts (type 320) or proforma invoices (type 330), and not required for tax invoices at or below the current net-amount threshold. Credit invoices follow the same threshold rules as tax invoices.