What to collect on a sale to a foreign customer: order, invoice, proof of delivery and payment records. How the pack differs for products and services.
Key takeaways
- The pack is built during the transaction, not after it. Later, some documents are no longer available.
- A physical product and a service produce entirely different packs - one has proof of delivery and one does not.
- The invoice description matters more on an international sale, because no supporting documents explain it.
- Storing it in one place, findable by customer and by period, is what makes it useful.
A transaction with a foreign customer produces more documents than a local one, and they scatter across systems: the order in email, the invoice in the system, the shipping confirmation at the courier, and the payment at the provider. Anyone who does not assemble them in real time ends up hunting for them exactly when somebody asks - the accountant, the customer, or a reviewer.
This is an operational description, not advice. Which documents your business needs and for how long is a question for your accountant and the official authority pages.
What needs to be in the pack?
| Document | Physical product | Service |
|---|---|---|
| Order or agreement | Yes | Yes, and especially important |
| Invoice | Yes | Yes |
| Proof of payment | Yes | Yes |
| Shipping and delivery documents | Yes | Not applicable |
| Export and clearance paperwork | Depends on the shipment type | Not applicable |
| Evidence the service was delivered | Not applicable | Yes - the critical item |
| Correspondence with the customer | Useful | Very useful |
The sixth row is the main difference. On a product sale, the courier produces proof for you. On a service sale, nobody does - so you have to create it: a meeting summary, confirmation that a deliverable was handed over, or a confirmation message from the customer.
What to collect in real time
- The order or agreement - one document describing what was sold, for how much, in which currency.
- Confirmation from the customer accepting the terms - even a short message.
- The invoice with a clear description, as covered in foreign currency invoices.
- Payment records - the transaction identifier at the payment provider or a transfer confirmation.
- Proof of delivery - shipment tracking and delivery, or confirmation the service was provided.
- Any change agreed along the way - a delay, an addition, a discount.
Item six is the forgotten one that helps most in a dispute: a customer who asked for a delay and agreed in writing is a customer who will not claim six months later that the delay was yours.
Where to store it
It matters less where and more that there is one place, findable two ways: by customer, and by period. Three options work in practice:
- A folder per customer in a cloud service, with a sub-folder per large transaction.
- Attachments on the customer record in your system, if it supports files.
- A document management system, in a business that already has one.
What does not work: an email inbox. Email is an excellent place to receive documents and a poor place to keep them, because whoever searches in a year will search by subject rather than by customer - and will not find it.
What is special about a service sale abroad
- There is no external document evidencing delivery, so whatever you create is all there is.
- The invoice description carries all the weight - "consulting services" is not a description.
- Correspondence is evidence, so keep the email in which the deliverable was handed over.
- A confirmation from the customer - one line - is worth more than any internal document.
The last item is easy to obtain and rarely requested: "could you confirm you received it" at the end of a project produces the strongest evidence you will have.
What happens in a refund or a dispute
On an international transaction, a dispute usually runs through the customer's card company rather than directly with them, so the pack is all you have. The three documents needed almost every time are the order, proof of delivery and the correspondence - exactly the detail set out in refunds and chargebacks.
What to do in advance:
- Make sure the statement descriptor the customer sees is recognisable as your business.
- Write a returns policy that also suits international sales, including the currency question.
- Keep all correspondence in one place rather than in an employee's personal mailbox.
How long to keep it
The answer is set by the rules applying to your business, which makes it a question for your accountant. What is true operationally: decide one period, write it down, and apply it to every pack - rather than each person keeping whatever seems right. The broader archive and retention subject is covered in digital archives and document retention.
The five minutes that save an hour
At the close of every international transaction, five minutes of tidying saves an hour later: save the order and the main correspondence in the customer folder; confirm the invoice was also retained in Hebrew; add the transaction identifier from the payment provider; and attach the delivery or acceptance confirmation. Those four together are the pack, and they will never require more work - unlike reconstructing them a year later from three different systems.
What to do when the customer asks for extra documents
Corporate customers abroad sometimes request documents nobody asks for in Israel: confirmation of company details, a document confirming bank account details, or a vendor onboarding form for their own systems. All three are legitimate and worth preparing for - keep a ready English version of your business details, and know who in the business is authorised to sign them.
One thing to watch especially: a request to change bank account details arriving by email is a known fraud point, so the reverse direction demands verification. If a customer asks to change the account they pay into, verify it on a separate channel before changing anything.
Why build this as a process rather than from memory
On the first transaction all of this looks unnecessary, and by the fifth nobody remembers what was collected. The simple approach: a short checklist saved in each transaction's folder, with five items and a tick beside each. It takes a minute and guarantees the pack is complete - and it is also what lets you hand the task to another employee without explaining everything again.
Sources
Frequently asked questions
What differs between a product pack and a service pack?
A product has external documents - shipping, delivery, sometimes export paperwork - evidencing the transaction happened. A service has none, so all the evidence is what you create: an agreement, a detailed invoice description, confirmation the deliverable was handed over, and correspondence.
Do I need special documents for selling abroad?
It depends what is sold and how it ships, and on the rules applying to your business - a question for your accountant. What is operationally true for any transaction: an order, an invoice with a clear description, proof of payment, and proof the product or deliverable arrived.
The customer signed nothing. What now?
Collect what exists: a confirmation email, correspondence in which they accept terms, or an order confirmation from the site. Many international transactions have no signature, and that is fine - what matters is having some record showing the customer agreed to what was agreed.
Where is the best place to keep the pack?
One place that allows searching by customer and by period. A cloud folder per customer works fine in a small business. What does not work is leaving documents in different people's mailboxes, because then the pack is scattered and cannot be reassembled when you need it.
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.
