The three common Israeli business documents and what separates them: one records the transaction, one records the payment, and one combines both.
Key takeaways
- A tax invoice records the transaction; a receipt records that money arrived.
- When transaction and payment happen at the same moment, a combined document saves issuing two.
- When payment arrives later, there are two separate events and usually two documents.
- A good system links the two so you do not have to do it by hand.
These three documents confuse people because they look alike and record different things: one records the transaction, one records that money was received, and the third combines both when they happen together. The difference is not semantic - it decides which document you send, when, and what happens when payment arrives later.
This is an operational description, not advice. What applies to your business and when is a question for your accountant or tax adviser and the Tax Authority pages.
What is the difference between the three documents?
| Document | What it records | When it is usually issued |
|---|---|---|
| Tax invoice | The transaction itself | When the transaction happens, paid or not |
| Receipt | That money was received | When payment actually arrives |
| Invoice-receipt | Both together | When transaction and payment happen at the same moment |
So in a business that sells and is paid immediately - a shop, a clinic, a service paid on completion - the combined document is the natural default. And in a business working on payment terms - sending an invoice and receiving money weeks later - two separate documents are the accurate picture.
Two scenarios, two flows
Scenario A: immediate payment. A customer buys, pays, and receives one document. This is the simpler of the two, and the only thing that matters is that the document is created automatically from the transaction rather than typed by hand.
Scenario B: payment later. An invoice is sent, the customer pays after some time, and then a receipt is created linked to that invoice. Two things to verify in the system:
- That the receipt links to the specific invoice, not just to the customer.
- That the invoice is marked paid, so it stops appearing in the debtors report.
The second is a common source of a service failure: a balance settled in reality but not in the system produces a payment reminder to a customer who already paid.
Other documents people confuse with these
- A quote - a sales document, before the transaction is closed. It records no transaction.
- A payment demand - a request for money that is not a tax invoice. Useful when asking for money before issuing an invoice.
- A credit note - a counter-document to an existing invoice, not a deletion of it. Detail in the credit note process.
- A delivery note - records goods handed over, not money.
The distinction between a quote and a payment demand is what confuses service businesses. The practical difference: a quote asks for a decision, a payment demand asks for money - and neither is the invoice itself.
What this actually changes in a business
- In cash flow: an invoice sent is not money. Anyone measuring income by invoices sees a rosier picture than reality.
- In collections: the debtors report rests on invoices with no linked receipt. If the link does not exist, the report lies.
- In service: a customer who paid and receives a reminder feels ignored.
- In bookkeeping: correctly separating the two events is what makes it possible to reconcile sales against the bank.
What to check in your system
- Whether all three types can be issued, each in its own series.
- Whether a receipt automatically links to the invoice it settles.
- Whether an invoice marked paid leaves the debtors report.
- Whether the combined document is created automatically when a cleared payment arrives.
- Whether the customer record shows both documents side by side.
Item four is the difference between a business that issues documents and one that types them: with clearing connected, every payment produces the right document with no action at all.
What belongs on the document itself
Beyond the document type, certain details cause enquiries when missing: full business details including the registration number; the customer's details as they identify themselves; a clear description of what was sold rather than just "services"; the amount and its breakdown; and a date. The third produces the most phone calls: a customer receiving a document with a single line reading "service" calls to ask what they paid for, and occasionally disputes it with their card company because they did not recognise it.
Automation also fixes timing. A document created at the moment of payment carries the right date; one typed at the end of the week carries the date somebody happened to type it, and that small difference is what turns a clean month into a month with questions.
Why the document should be automatic
Every manual document is an opportunity for three errors: a wrong number, a wrong customer, and a document that never gets issued at all. When clearing is connected to the invoicing system, the document is created from the transaction and all three disappear. That is also why the first thing to check in any system is not which document types exist but whether they are produced automatically from a payment - a point covered in payment-to-invoice automation.
What happens when payment is split across methods
A customer paying part by card and part by transfer is routine and confuses systems. What to verify: that several receipts can be recorded against one invoice; that each receipt records its own payment method; and that the invoice closes only when the receipts cover it. A system allowing one receipt per document forces the team to round, split invoices, or write a note - and all three break reconciliation later.
How this looks on the customer record
A good customer record shows three things side by side: which documents were issued, what was paid, and what is open. That sounds obvious and is exactly what many systems lack - so answering a customer asking "how much do I owe" means opening two reports and subtracting. Check that screen during a trial, because it is the screen you will open most often all year.
Sources
Frequently asked questions
When do I issue a combined document and when two separate ones?
When transaction and payment happen at the same moment, a combined document describes reality and saves work. When there is a time gap - an invoice now, payment in a month - there are two events, so two linked documents are usually issued.
I received a partial payment. Which document?
A receipt for the amount actually received, linked to the invoice. The balance stays open in the debtors report. What is wrong is marking the invoice fully paid - that removes it from tracking and creates a balance nobody chases.
Is a quote enough instead of an invoice?
No. A quote is a sales document asking for a decision, and records no transaction. Once the customer approves, the appropriate document is issued. Many systems convert a quote into an invoice in one click, which saves re-typing and errors.
Who decides which document suits my business?
Your accountant or tax adviser, based on the nature of the activity and how you report. What this article describes is the operational difference between the documents, so you know what to check in a system and what to ask - not which obligation applies to you.
Keep reading
Related service
Integrations
Make the systems you already pay for talk to each other.
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 and I'll tell you the fastest reliable way to ship it.