SAP Concur Receipts Not Showing Up? Practical Fixes for 2026

SAP Concur has more than one receipt destination. A receipt image may land in Available Receipts. A receipt processed by ExpenseIt may become an Available Expense. A company card transaction may also appear in Available Expenses for reasons unrelated to emailed receipts. If you check only one area, it can look like the receipt disappeared when it is actually in another queue.

Start by matching the address or method you used with the place you expect the receipt to appear. If your company uses ExpenseIt, the receipt may be converted into an expense-like item. If the email went to a receipt image workflow, it may be a stored image waiting to be attached to a report or expense entry.

Check the intake queues before the final report. A receipt can be waiting for attachment, converted into an expense item, blocked by sender verification, or rejected because the document was not usable.

Check Available Receipts for image-style receipt storage. Check Available Expenses for ExpenseIt-created expense items. Check open reports in case the receipt or expense was attached during a report workflow.

SAP Help says users must verify an email address before emailing receipts to the Available Receipts library. That verification step is easy to overlook, especially when people forward from a personal address, a travel alias, a delegated mailbox, or a mobile mail account that differs from the address in their Concur profile.

Admin-approved sender workflows add another layer. SAP Help describes scenarios where approved senders can email receipts on behalf of employees, but those workflows have sender-list and subject-line requirements. If your company uses a central travel desk, scanning service, or delegated forwarding setup, ask the Concur administrator which sender rules apply.

For troubleshooting, use the exact sending path you plan to automate. A test from your primary work mailbox may succeed while a delegated inbox, alias, or third-party forwarding path fails. That does not mean Concur is inconsistent. It means sender identity is part of the receipt-control model.

Receipt processing is document processing. If the proof of purchase is only an HTML body, a portal link, or a confirmation email without an attached image or PDF, Concur may not receive a usable receipt image. Airline, hotel, SaaS, and online-order emails often look like receipts to humans but do not always include a clean attachment.

SAP release notes also show that Concur has invested in notifications for failed digital receipt processing, including unsupported file-type scenarios. That is useful, but it does not remove the need to send a readable document in a supported workflow. When a receipt is missing, inspect the original email before blaming the Concur queue.

A forwarding rule can send an email that says "your receipt is ready" without sending the receipt itself. Download the document from the portal before routing it to Concur.

Look for a real attachment, not only a receipt-looking email body. Avoid password-protected, corrupted, or very low-quality scans. Confirm the file type and size against your company guidance and SAP Concur documentation.

When ExpenseIt is active, a receipt may become an Available Expense instead of a stored image in Available Receipts. If you already confirmed sender, file, and address but still cannot find the item, the issue may be ExpenseIt-specific — access, workflow path, OCR quality, or admin policy.

For a full ExpenseIt troubleshooting path — including when the receipt exists but ExpenseIt failed to process it — see our dedicated ExpenseIt guide linked below.

Expensent finds current and historical receipt emails and sends selected documents to the chosen Concur destination. Confirmed recurring patterns can route new receipts automatically.

Portal-only and unusual messages remain visible, while Concur continues with ExpenseIt, policy checks, approvals, and reimbursement after delivery.

The strongest prevention habit is a short review cadence. Check the queue before submitting reports, before month-end, or before travel-expense deadlines. Ready documents can go to Concur. Portal-only emails stay visible until the PDF is downloaded. Ambiguous messages stay out of the expense workflow until someone makes a decision.

Use Expensent to find current and historical receipt emails. Forward with one click when the document is ready. Create future routing rules from real receipt emails, not guessed sender filters.

Use a fixed order so troubleshooting does not become guesswork. First confirm the original email has a usable receipt. Then confirm the sender is verified or approved. Then confirm the destination address or upload method. Then check the likely Concur landing area. Only after those checks should you treat the issue as an ExpenseIt or Concur processing problem.

This order helps teams avoid duplicate work. If the receipt never left the inbox, checking Available Expenses will not help. If it landed as an Available Receipt, sending it again may create duplicates. If the sender is not verified, improving the image quality will not solve delivery.

Original email: usable attachment or supported receipt content. Sender: verified user email or admin-approved sender path. Destination: correct receipt address, upload flow, or ExpenseIt method. Landing area: Available Receipts, Available Expenses, or the open report.

If the receipt still does not appear, collect the details an administrator needs: sending email address, recipient address, timestamp, file type, file size, original subject, whether the email was forwarded or composed directly, and the Concur area you checked. This gives support a specific case to investigate.

For companies with strict travel and expense controls, this evidence matters. The admin may need to inspect verified senders, approved sender lists, region-specific receipt addresses, ExpenseIt availability, or policy settings. Expensent can reduce future misses, but company configuration still belongs to Concur administration.