Handle a receipt supplied in the email body instead of an attachment

Inspect the message body before declaring the receipt missing

Preserve the usable evidence through your approved channel so staff do not request something the client has already supplied.

If your evidence is a supplier invoice PDF, ParseMill can turn its invoice details and line items into a reviewable Excel workbook. Compare the source and correct the result before export. Receipt photos, missing-document requests and transaction matching belong in your existing receipt and accounting tools.

The aim is to capture what was supplied without overstating what it proves. An inline image, text summary and merchant email can have different evidential roles. Record the source and limitations, then let the authorized reviewer decide whether the content answers the query or requires another document.

Preserve the source before making a working copy

Record message reference, sender as displayed, received time, subject and relevant transaction query. Keep the original message in the approved record system. If creating a PDF or image copy for review, label it as derived from that message and check that the relevant content and context survived the conversion.

Microsoft: Inline images and attachments distinguishes pictures inserted in the message body from attached files. Microsoft: Save an Outlook message describes saving received messages in supported Outlook versions. These features support preservation, but they do not guarantee that a printed or exported copy contains every image, link target or message detail. Inspect the actual result.

Build an inline-evidence record

The fictional example below concerns a merchant receipt embedded in a forwarded message. The intake owner records the chain without treating the forwarder as the original issuer.

If the inline image is missing or depends on unavailable remote content, record that limitation and request a supported copy through the approved channel. Do not reconstruct a receipt from a thumbnail or follow unfamiliar links solely to make the query appear complete.

Check capture quality and context

Compare the working copy with the message view. Confirm that cropping has not removed the merchant, currency or relevant item details, and that the message's explanatory text remains linked. A screenshot of only the total can lose the information needed to identify the purchase.

• Preserve the original received message reference.
• Distinguish the sender from the apparent evidence issuer.
• Label converted material as a derived copy.
• Check readability and completeness after capture.
• Retain the reviewer's evidence and matching decision separately.

If the body contains several receipts, assign separate artifact references and link each to the appropriate query. Do not attach the entire unrelated conversation to every transaction when a scoped record and controlled source link can preserve the needed context under your firm's process.

Verify retrieval from the query

Ask a colleague to open the evidence from the transaction query and find the original message context. They should be able to tell what the client supplied, what was derived for review and what remains uncertain. An attachment icon is not required for that relationship to be useful.

Use the related workflow guide for the broader receipt workflow and the workflow audit checklist to identify evidence lost between inboxes and review systems. Test an inline image, a text-only merchant record and an unavailable image so the process handles different forms without pretending they are equivalent.