Registered with the Israel Tax Authority: What It Means for a Custom-Built System

In a custom-system project, separate three things that are often mixed together: an operational system for customers and orders, an accounting component that issues documents, and the Israel Tax Authority requirements that apply to record keeping or regulated files. A system that looks like an invoice or creates a PDF is not, by itself, evidence of compliance.

Before development starts, decide what the custom system will do and what remains in the existing invoicing or accounting product. For many businesses, the lower-risk design is for the custom system to manage the business event and send controlled data to a dedicated invoicing or accounting system. That avoids rebuilding regulatory logic unnecessarily.

Questions to settle in the specification

• Does the custom system issue an accounting document, or only submit an instruction to issue it in a dedicated system?
• Who owns numbering, cancellations, credit notes, and retention?
• Is a uniform-format file required, and against which current specification?
• Who checks the workflow with the accountant before production launch?

If the scope changes a component that affects tax requirements, do not rely on an article or older project. Collect source instructions, document examples, cancellation and correction scenarios, then write acceptance tests. A sound design traces every transaction from the operational screen to the accounting-system record.

Source

Israel Tax Authority