## TL;DR

Email forwarding can corrupt PDFs when a client re-encodes the attachment or truncates it (common with nested forwards and mobile mail clients). Get the original PDF again, forward it as a fresh attachment without inline previewing, and confirm the expense tool parses it. If forwarding keeps corrupting it, upload the file directly in the expense app instead.

## Error

```text
receipt pdf corrupted during email forwarding to receipts inbox
```

## Steps

1. Open the expense and try to view the attached PDF. Expected: the viewer shows a corruption error or a truncated document, confirming the diagnosis.
2. Go back to the original email and download the PDF attachment directly. Expected: the downloaded file opens correctly on your device.
3. Forward the original email as an attachment (not inline), or send the downloaded PDF as a new attachment to the receipts inbox. Expected: the receipts inbox receives a clean copy.
4. Check the expense for the new attachment and open it. Expected: the PDF renders fully and legibly.
5. If corruption recurs, upload the PDF directly through the expense tool's web or mobile app. Expected: the direct upload bypasses the mail pipeline entirely.

## When to use

- A receipt PDF is corrupted after email forwarding to a receipts inbox.
- The same PDF opens fine outside the expense tool.
- Nested forwards repeatedly damage attachments.

## When not to use

- The PDF opens but the scan is too blurry to read (an image-quality problem).
- The original PDF is itself corrupted at the source.
- The inbox never received the email at all.

## Tool compatibility

Applies to email-based receipt capture across expense tools (Expensify, Concur, Fyle, and others; current 2026 releases).

### Variant phrasings

### forwarded receipt "cannot be opened" in the expense tool

The attachment was damaged in transit. Re-send the original.

### nested forward broke the receipt pdf

Each forward risks re-encoding. Forward as an attachment from the original message.

### mobile mail client corrupted the receipt attachment

Some mobile clients downsample attachments. Upload via the expense app instead.

## Why it happens

Email was not designed as a file-transfer protocol: clients re-encode attachments, strip metadata, and truncate large files, and each forward in a chain compounds the damage. Receipt-inbox ingestion expects an intact PDF, so a truncated or re-encoded file fails to parse. Sending the original as a fresh attachment, or uploading directly, avoids the mail pipeline's transformations.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Bjst6k6lVMg5nYGRMox5IA
