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.

This is the Concur version of a classic accounting-intake mistake: users search the final report before checking the intake queue. A receipt can be waiting for attachment, converted into an expense item, blocked by sender verification, or rejected because the document was not usable. The fix starts by locating the layer where the chain broke.

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.

This is where many automated forwarding setups produce false confidence. They forward an email that says "your receipt is ready" but not the actual receipt. A human can click the link and understand what happened; an expense system needs the document or the supported receipt data. Keep portal-link messages in review until the attachment is downloaded.

ExpenseIt is designed to create expense entries from receipt images, using OCR, machine learning, and newer AI reasoning capabilities. When ExpenseIt is active, the result may not feel like a simple uploaded image. It can become an item that needs review, correction, or selection from Available Expenses.

This is helpful when it works, but it changes troubleshooting. If an ExpenseIt receipt is not visible, check whether ExpenseIt is enabled for your company and user, whether the workflow is available on web, mobile, or email for your environment, and whether the item landed in a different area than a plain receipt image would.

Also expect review. OCR and AI can prefill details, but employees and approvers still need accurate categories, business purpose, attendees, allocation, and policy context where required. A receipt that lands as an Available Expense may still require human completion before it is report-ready.

Most Concur troubleshooting happens after the receipt should already be in Concur. Expensent moves the first control point earlier. It finds invoice and receipt emails in the inbox, separates ready-to-forward items from documents that need review or download, and lets users send the right proof to the chosen Concur destination.

That does not replace Concur, ExpenseIt, policy checks, approvals, or reimbursement. It makes the handoff more reliable. The practical win is fewer receipts forgotten in email, fewer month-end searches, and a clearer trail of what was forwarded and what still needs attention.

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 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.

A simple email rule can create silent failure. It may forward only future messages, miss receipts from new travel vendors, send portal notices without attachments, or route emails from an unverified sender. The user may not notice until an expense report is due and the receipt is still in the inbox.

Expensent is a stronger fit when the problem is receipt discovery and routing. It gives the user a queue, exposes exceptions, and allows rules to be created from reviewed messages. That does not make Concur less important. It gives Concur cleaner inputs.

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 makes the support request specific instead of emotional.

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.

Employees should run a short receipt check before submitting a report. Search the inbox for recent travel, meals, SaaS, and transportation receipts. Confirm which items already appear in Concur. Forward missing clean documents to the approved destination. Keep portal-link messages visible until the actual receipt is downloaded.

This habit reduces urgent back-and-forth with approvers. It also makes Concur more useful because the receipt proof is present before the report is reviewed. Expensent can make the checklist faster by surfacing likely receipt emails and separating ready-to-forward items from exceptions.

A company does not need to change Concur policy to improve receipt capture. It can standardize the upstream habit: employees review receipt emails, forward usable proof to the approved destination, and leave Concur to enforce reporting and approval rules. The improvement is operational, not a policy bypass.

For teams that use Expensent, the rollout should begin with high-volume receipt patterns and historical catch-up. Prove the destination, create rules for recurring senders, and keep exceptions visible. That gives administrators a controlled receipt collection layer while preserving Concur as the expense system of record.