Is a card statement enough for an expense claim?

Sometimes, but often not. A card statement usually proves that a payment was posted; it may not show the items purchased, tax details, business purpose, or whether the amount included personal spending.

What is the best evidence for a reimbursable expense?

An itemized merchant receipt or supplier invoice is usually the clearest starting point. Follow the client's policy because some also require proof of payment, project references, or written pre-approval.

What should I do if I lost a receipt?

Ask the merchant for a duplicate first. If that is impossible, disclose the missing receipt and ask the client which alternative evidence they accept, such as a card statement plus a written explanation.

Does OCR prove that a receipt is authentic?

No. OCR extracts text from an image. It can help create a reviewable record, but it does not prove that the document or transaction is genuine.

Does ClaimInvoice store or verify every receipt?

ClaimInvoice helps users extract and review receipt fields and generate an invoice PDF. Current verification should be based on the original evidence and the recipient's policy; the product does not claim merchant authenticity.

August 1, 2026

Receipt Evidence vs. Card Statement: What Should You Attach to an Expense Claim?

Learn when a receipt, supplier invoice, card statement, or payment confirmation is useful evidence for a client expense claim—and what each one cannot prove.

For most expense claims, an itemized receipt or supplier invoice is stronger evidence than a card statement. The receipt explains what was purchased; the statement usually shows only that a payment occurred. Some clients require both. The correct choice comes from the contract or expense policy—not from whichever document is easiest to find.

This guide explains what each evidence type contributes, where it falls short, and how to prepare a claim without overstating what the documents prove.

Evidence is a chain, not a badge

No single file answers every approval question.

A reviewer may need to establish:

Purpose — what was bought and why it relates to the work;
Amount — what currency and total were charged;
Payment — whether the charge was actually paid;
Authority — whether the cost was allowed or pre-approved;
Allocation — which client, project, or period should carry it.

Different records answer different parts of that chain.

Quick comparison

Evidence type	Usually shows	Usually does not show	Best use
Itemized receipt	Merchant, items, date, amount, tax	Contract approval or project purpose	Primary evidence for ordinary purchases
Supplier invoice	Supplier, billed items, terms, tax details	Proof that payment cleared	Services, subscriptions, larger purchases
Card statement	Posted merchant, date, amount, currency	Item detail or business purpose	Supporting proof of payment
Payment confirmation	Transfer reference and amount	What was purchased	Supporting bank transfer or online payment
Booking confirmation	Traveller, dates, route, booking total	Final charged amount or changes	Travel context
Written pre-approval	Who approved what and under which limit	Proof of purchase or payment	Authority for exceptional costs

The strongest pack often combines records instead of pretending one file does everything.

When an itemized receipt is the right starting point

Use a merchant receipt when it clearly identifies:

supplier or merchant;
transaction date;
goods or services;
amount and currency;
applicable tax details;
payment method, if shown.

For meals, materials, taxis, parking, and small project purchases, this is usually the most direct evidence.

Check that the image is readable from top to bottom. A close crop that removes the merchant or total may save file size but destroy context.

When a supplier invoice is stronger

A supplier invoice is often better for:

professional services;
software subscriptions;
equipment;
venue hire;
accommodation;
purchases where tax registration details matter.

It identifies the billed party and describes what was supplied. But an invoice can remain unpaid, so a client may also ask for payment confirmation before reimbursing it.

Do not label a quotation, pro forma invoice, or order confirmation as proof of final payment unless the client's policy explicitly accepts it.

What a card statement can and cannot prove

A card statement is useful supporting evidence when:

the merchant receipt is missing;
the statement uses a clearer local-currency conversion;
the client needs proof that the charge cleared;
the receipt shows a tip or deposit differently from the final charge.

Its limits are important:

the merchant name may be abbreviated;
it rarely lists the items purchased;
one transaction may contain both business and personal items;
the posting date may differ from the purchase date;
it does not explain the business purpose;
it does not prove the cost was authorized by the client.

Therefore, “it appears on my card” is not the same as “the client agreed to reimburse it.”

What to do when the receipt is missing

Use this recovery order:

Request a duplicate from the merchant or download it from the supplier account.
Check email for the invoice, booking record, or order confirmation.
Find proof of payment such as the card statement or bank transfer.
Write a factual explanation of the business purpose and why the original is unavailable.
Ask the client whether that alternative evidence is acceptable.

Do not manufacture a replacement receipt or imply that a bank line contains details it does not.

A concise disclosure can say:

“The original taxi receipt is unavailable. Attached are the card transaction and trip booking showing the date and amount. Please confirm whether this meets the project's evidence requirement.”

Honesty reduces the chance that a small documentation gap becomes a larger trust problem.

The EVIDENCE test

Before attaching a document, run this seven-part check:

E — Exact: Does the amount match the requested line?
V — Visible: Can the recipient read the relevant details?
I — Identified: Are merchant and date clear?
D — Described: Is the purchase or business purpose understandable?
E — Entitled: Was it allowed under the agreement?
N — Non-duplicate: Has it already been claimed?
C — Connected: Is it tied to the correct client or project?
E — Explained: Are conversion or missing-document exceptions disclosed?

This is not a legal standard. It is a practical review discipline.

Extraction is not verification

Receipt-reading software can turn a document into editable fields. That is useful because it saves typing and makes totals easier to organize.

It does not establish:

that the merchant issued the document;
that the underlying transaction happened;
that the cost belongs to your project;
that the client agreed to reimburse it;
that the tax treatment is correct.

The right product language is therefore “extracted for review,” not “verified expense.”

ClaimInvoice follows that boundary. It can prefill merchant, date, currency, and amount, but users review those fields before they become claim lines. If extraction cannot read a document, manual entry remains available.

How to organize the final request

Create a summary where each line uses a stable order:

Line	Date	Merchant	Purpose	Currency	Amount	Evidence
1	2026-07-12	Metro Transit	Client-site travel	HKD	45.00	Receipt
2	2026-07-12	Harbour Print	Workshop materials	HKD	286.00	Supplier invoice + card line

Keep filenames equally clear:

01-2026-07-12-metro-transit-hkd45.jpg
02-2026-07-12-harbour-print-hkd286.pdf

The numbering is a small act of consideration for the reviewer. It gives them a stable path from summary to evidence.

How ClaimInvoice fits

ClaimInvoice helps create the structured layer:

capture or upload a receipt;
extract fields through the authenticated cloud workflow;
review each field;
group reviewed expenses into a draft;
generate an invoice-style PDF summary.

It does not replace your original evidence, your client's policy, or professional advice. That is deliberate: a trustworthy tool should tell you where its responsibility ends.