Turn a missing receipt into one answerable month-close task

Diagnose the gap

Open the payment or event and ask what is already known:

This changes an unspecific blocker into a bounded task.

A safe recovery sequence

1. Confirm the business, period, amount, currency, and counterparty.
2. Search the original source: supplier portal, email, card account, checkout system, or responsible employee.
3. Ask the supplier for a duplicate or corrected invoice where appropriate.
4. Preserve the bank row and any order or delivery context.
5. Record the business explanation separately from unverified invoice facts.
6. Set a deadline and owner for follow-up.
7. Send the complete known case to the accountant if the original cannot be recovered.

Do not create a document that looks like a supplier invoice. A business note can document facts supplied by the owner, but it should be labelled honestly and reviewed for the specific case.

Whether alternative evidence is sufficient, and whether an expense or input VAT can be recognised, depends on the facts and professional assessment. This article does not make that decision.

Worked example: card payment without invoice

A synthetic agency has a €238.00 card debit labelled with a software supplier. No invoice is in the monthly folder.

The owner confirms the subscription is used by the design team. That explains business purpose, but it does not supply invoice date, service period, tax detail, or exact supplier entity. The next step is to obtain the billing document from the supplier account. Until then, the payment can remain connected to a “missing invoice” exception with amount, date, owner, and attempted recovery.

If the supplier document later shows €198.00 plus a separate €40.00 charge, the visible exception prevents a false one-document match.

What the missing-receipt task should contain

For the €238.00 case, a useful DeinHans task packet contains:

A likely supplier and category reduce search work; they do not complete the case. When the owner answers, the response returns to the same payment and task. If the invoice arrives, preparation resumes from the source. If it does not, the exception remains visible with attempted recovery and professional owner.

Does the month have to stop?

Usually the rest of the month can continue. Bank reconciliation, other evidence, open-item review, and owner questions should proceed. The missing source may still block final treatment, professional approval, or close depending on materiality and the firm’s policy.

The close view should distinguish:

• recovered source;
• alternative evidence awaiting professional review;
• known exception accepted for later follow-up;
• unresolved item that blocks approval.

Those are workflow states, not tax conclusions.

The rest of the month can proceed when this case is isolated and does not undermine source coverage elsewhere. It still blocks its own final proposal. It can also block the whole handoff when the amount, recurrence, VAT relevance or firm policy makes the missing evidence material. That gate is explicit; the software does not hide the item merely to make the month appear complete.

Prevent the same gap next month

After resolution, fix the source routine:

• add the supplier portal to the monthly source list;
• route invoices to a shared address;
• assign each company card to a responsible person;
• review recurring debits against expected invoices;
• collect receipts close to purchase time;
• keep rejected or corrected invoices connected to the original event.

DeinHans can hold the payment, available evidence, owner answer, and missing-source task together. It must not mark the case resolved merely because a plausible merchant or category was found.

Responsibility at handoff

The owner supplies the business fact and attempts to obtain the source. Software makes the gap and follow-up visible. The accountant assesses the available evidence, decides the treatment, and records any required correction or exception. That division keeps the month moving without pretending the gap has disappeared.