Not who wins on features, but who answers the phone when an invoice is rejected. A decision frame built on the accountability chain and local connections.
Key takeaways
- A global platform is not disqualified in Israel. What happens is that the local connection moves to a different layer, and you have to decide in advance who holds it.
- An accountability chain with four parties is a chain in which every party can point at the next one. That is the real risk, not response time.
- The Tax Authority operates the Israel Invoice allocation-number scheme, so obtaining an allocation number is an operational requirement someone in the software stack must supply.
- Checked in September 2026, Rivhit is the only vendor among those reviewed that publishes an explicitly named operation for obtaining a confirmation number for a document.
- This is a technical description of what is published, not tax, legal or accounting advice.
The choice between an Israeli system and a global platform is settled by two questions: who is accountable when something breaks at three in the afternoon, and which local connections the business has to produce regardless. Features are not the axis. The accountability chain and the documents regulation requires are the axis.
What actually happens when something breaks
At three in the afternoon an invoice is rejected. In a business running one system from one vendor, that is one phone call. In a business running a global platform plus an Israeli invoicing add-on, a payments module and a local implementer, that is four calls, and each one can end with the sentence "that is not on our side".
This is what people mean when they say "an Israeli system". They do not mean the interface language. They mean there is one address that cannot deflect.
The global platform is not necessarily worse. It simply demands an explicit decision: who owns the chain. If the answer is "we do", that is a legitimate decision that requires a named person. If there is no answer, the chain will break at exactly the point nobody chose.
Who is accountable when the invoice is rejected?
Trace that one failure hop by hop, and write a name beside every hop:
- The customer ordered in the store. Who is accountable that the stored amount is right.
- The payment was captured. Who is accountable that the amount charged equals the amount ordered.
- The invoice was produced. Who is accountable that the document was created at all.
- The document was submitted for an allocation number. Who is accountable for that call and for handling its failure.
- The document was sent to the customer. Who is accountable that it was sent once and not twice.
- The record reached bookkeeping. Who is accountable that it arrived complete.
- Month end. Who is accountable that the export to the accountant is valid.
If the same name appears on all seven rows, you have one accountable vendor. If four names appear, that is not a problem in itself, but it does require one of them to be defined, in writing, as accountable for the seam.
Five local connections to check by name
- The invoice allocation number. The Tax Authority's Israel Invoice scheme. Someone in the stack has to make the call and handle the answer.
- The uniform-format export. The file an accountant or an audit asks for, which a PDF cannot substitute for.
- The periodic VAT report. Who produces it and from which data source, when sales sit in one platform and credit notes in another.
- A local courier shipping label. In Israel this is almost always a separate integration; see Israel Post versus a private courier.
- Local card acquiring. An Israeli gateway behaves differently from a global one in both documentation and reconciliation; see comparing Israeli payment gateways.
Where each of those connections actually lives
| Local connection | Found in an Israeli system's public documentation | Found in a global commerce platform's public documentation | Who supplies it in practice |
|---|---|---|---|
| Invoice allocation number | Yes. Rivhit publishes an operation named Document.InvoiceApproval, described as "Acquire confirmation number for given document" | Not located in the developer documentation reviewed | The invoicing system, not the commerce platform |
| Uniform-format export | Yes. Rivhit publishes OpenFormat.ZIP | Not located in the developer documentation reviewed | The bookkeeping system |
| VAT report | Yes. Rivhit publishes Accounting.VatReport | Not located in the developer documentation reviewed | The bookkeeping system |
| Free reading of business data for control checks | Yes. Priority documents an OData interface with $filter, $select, $expand | Partly. Commerce platforms document per-entity interfaces, not a free query over every table | Depends on which side the data sits |
| Local courier label | Not located in the documentation of the systems reviewed | Not located in the developer documentation reviewed | The courier, or an intermediate layer |
"Not located in the developer documentation reviewed" means we searched the platforms' public documentation indexes for the item by name in September 2026 and found no page for it. It is not a claim that the capability is unavailable through a third-party application. On the contrary: that is the normal architecture, and the point is to choose who supplies it rather than assume it is included.
Does a global platform disqualify itself in Israel?
No. It moves the local connection into a layer you hold, and that is where the difference ends. It takes three practical forms:
- A third-party application. Fast to start with, but it adds a fourth party to the accountability chain and has a lifecycle of its own.
- An intermediate layer you own. A small service that reads from the platform and writes to the invoicing system. More work up front, full control afterwards.
- The Israeli system as the source of truth. The platform becomes a shop window, and every document is born on the Israeli side. See connecting an online store to an ERP.
There is no single right answer here. There is one question that must be answered: which of the three you are choosing, and who maintains it in year three.
What to get in writing before you sign
- Who is the single address for a fault that crosses two systems, by name and role.
- In which hours and in which language support is provided, and how an urgent ticket is opened.
- What happens when a regulatory requirement changes: who updates it, and within what time.
- Whether a separate test environment exists, and what its base address is.
- Who owns the data at the end of the engagement, and in what format it is handed over.
- Whether interface documentation is open to read, or released only after signature.
Cost shape, without numbers
- What scales with users. Per-seat licensing is the visible cost, and usually the only one that gets compared.
- What scales with transactions. Many system interfaces are metered on write operations, not on user logins. A business that triples its sales can triple its interface cost without adding a single employee.
- What scales with the number of parties in the chain. Each extra party adds a phone call, not just an invoice.
- What scales with customisation. A customisation that leans on undocumented behaviour has to be retested at every upgrade.
- What stays flat. A written procedure that someone maintains. It is the cheapest line in the table and almost always the one that gets dropped.
Related: the Israeli business software stack, connecting an Israeli ERP to anything.
Sources
Frequently asked questions
Is an Israeli system always better for an Israeli business?
No. It usually shortens the accountability chain and ships local documents ready-made, which is a real advantage. A global platform, on the other hand, usually publishes more accessible developer documentation, which shortens development. The choice depends on who in the business will hold the seam between the two.
What does it mean that the local connection "moves to a different layer"?
That the capability still exists, but someone else supplies it: a third-party application, an intermediate service you wrote, or an Israeli invoicing system running alongside the platform. The one decision you cannot defer is which of the three, because the default is nobody.
How many vendors in a chain is too many?
There is no magic number, but there is a test: if no single party is defined in writing as accountable for the seam between two vendors, the chain is too long regardless of its length. Two vendors with defined accountability beat one without it.
Is any of this tax or legal advice?
No. It is a technical description of operational requirements and of what appears in public documentation, for the purpose of planning an architecture. Any question about reporting obligations, classification or applicability goes to your accountant and to the Tax Authority's own publications.
Keep reading
Related service
Business Automation
I build custom automations that remove repetitive work end to end.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build. I reply within 24 business hours with a few targeted questions, then we walk through it on a free 30-minute call, with no commitment. You come away with a scope, a timeline and a fixed price - or a straight answer that it isn't worth building.