Do I need a formal form?

Not in a small business. What you need is one channel and consistent information: document, date, amount, and what for. A message, a simple form or a system all work - what matters is that it is the same every time, so whoever approves is not hunting for missing details.

What if there is no receipt?

Decide in advance that there is no reimbursement without a document, and say so before it happens. If an exception genuinely arises, record it explicitly as an exception and decide on the merits - but do not let it become the norm, because then documents stop arriving.

How quickly should reimbursement happen?

There is no single answer, and there is a principle: a known, fixed date beats fast and unpredictable. Payment alongside payroll is the most common and simplest solution, and it also guarantees it will not be forgotten - because somebody is running payroll anyway.

Whoever owns the budget for that activity, not necessarily whoever pays. In a small business that is usually the owner, and above a certain amount a second approval is worth having - even if only a written message. The principle is covered in [supplier invoice approval in a two-person business](/blog/invoice-approval-workflow-two-people).

Employee Expense Reimbursement: Submission, Approval, Payment, Records

An employee paying out of pocket needs a defined process: one channel, a fixed deadline, approval and a recorded payment. How to build it in a small business.

An employee paying out of pocket for the business creates three problems at once when there is no process: they are waiting for their own money, the document rides around in a pocket until it fades, and the business does not know what it spent this month. A reimbursement process is four simple steps, defined once.

This is an operational description, not advice. Which expenses are recognised and what each document must show is a question for your accountant or tax adviser.

The four steps

Step	What happens	What to define
Submission	The employee sends a document and details	The channel, and what must appear
Approval	Somebody confirms it is a justified expense	Who approves, and above what amount a second is needed
Payment	The money is returned	A fixed date, and a channel
Records	The expense enters the books	Where, and who verifies

Step four gets forgotten when payment goes out as a quick transfer and the document is left behind: the employee has their money, and the business has no record of an expense that genuinely happened.

What must every submission include?

The document itself, readable, and an original rather than a photo of a photo.
What the expense was - not "travel" but where and why.
The date of the expense, not of the submission.
The amount, and where split, which part is business.
Payment details for the employee, once rather than on every request.

The second item saves enquiries a month later, when nobody remembers what it was about. One line is enough.

What to decide in advance

Who may spend, and up to how much without prior approval.
What is approved and what is not - a short list, not a long policy.
The submission deadline - by the 5th of the month for the previous one, for example.
When payment happens - alongside payroll, for example.
What happens with no document - and this must be known in advance, not a surprise.
Who approves, and who approves when the approver is away.

Item five is the landmine: an employee who spent in good faith and is told there is no reimbursement without a document feels cheated - unless they knew beforehand.

Why fast payment pays

An employee who waits two months learns not to spend. The result is not saving but delay: they do not buy what is needed, or they buy and wait, or they ask the business to pay directly - which adds work for somebody else. Payment on a known date, even monthly, solves it entirely. And when reimbursement goes out with payroll, it does not get forgotten either.

What this looks like in a three-person business

No system needed. What works:

One channel - a dedicated mailbox or a dedicated WhatsApp group, for example.
One folder where all the documents land.
One table - date, who, what for, how much, approved, paid.
A fixed day each month for going through the table.

That table is also the report: it says how much employee expense there was this month, and who submits most. Both are useful even when nothing is wrong.

How this relates to document capture

Expense reimbursement is a special case of document capture, and the difference is that the document comes from another person and late. So the channel has to be convenient for them rather than for you: somebody in the field will not log into a system, they will take a photo. Israeli systems offer varied intake channels - SUMIT, for example, presents submission through a WhatsApp bot - and the full detail is in capturing supplier receipts.

What this looks like from the employee's side

It is worth seeing it from the other direction too: an employee spending their own money is doing the business a favour, and they should not feel they are chasing what is owed to them. Three things change that feeling: knowing when the money returns, getting confirmation the request was received, and not having to ask. All three are possible with no system - a short confirmation message and a fixed date are enough - and they are the difference between a process that works and one people avoid.

Why this breaks in small businesses

The process almost always exists on paper and not in practice, for three reasons: there is no single channel, so some requests arrive as private messages and get forgotten; there is no fixed payment date, so every request needs a reminder; and nobody owns it, so it lands on whoever is least busy. All three are solved by the same action - define a channel, a date and an owner - and it takes ten minutes.

What is common and what is exceptional

Most employee expenses fall into four categories, and each deserves a decision in advance:

Travel and parking - the most common, and the easiest to lose receipts for.
Hospitality - usually needs a note of who and what, not only an amount.
Small equipment - a cable, an adapter, an accessory. Usually approved up to an amount.
A large one-off purchase - needs prior approval rather than retrospective.

The fourth category creates friction: an employee who bought something expensive in good faith and found it was not approved. The only way to prevent it is a clear amount above which they ask first.

What to do when an employee leaves

At the end of an engagement, confirm there are no open expenses of theirs - including ones they forgot to submit. One request before the last day handles it, and prevents an enquiry a month later when it is hard to verify. It is also the moment to confirm any subscription or service registered in their name is transferred - covered in limited company versus sole trader in the systems layer.

Employee Expense Reimbursement: Submission, Approval, Payment, Records

Key takeaways