Find a Missing Receipt in Wave

A missing Wave receipt is easier to diagnose once you name the path that created the expectation. Wave has receipt scan in the mobile app, receipt file upload in a web browser, receipt email forwarding, and manual receipt attachment on a transaction.

If you scanned a receipt in the Wave mobile app, check Accounting > Receipts and the related transaction. If you uploaded a receipt file from the Receipts page or Transactions page, check Recent Scans and Accounting > Transactions. If you forwarded a digital receipt by email, verify the forwarding address and the one-receipt email package. If you manually attached a file to an existing transaction, open that transaction; the receipt may not appear as a new scan.

Do this before changing settings or resending the same document. A receipt attached to an existing withdrawal is not missing from Wave; it is attached somewhere different from where you expected to see a scanned receipt. A scan waiting for review is not the same as a reviewed accounting record. The intake path tells you where to look first.

Wave's current help pages say receipt scan and receipt email forwarding require either the Pro Plan or a Receipts subscription. Wave also says subscription fees apply per business profile, so a user with multiple businesses should not assume receipt access on one profile means receipt access on another.

Region and legacy status can also explain why a control is missing. Wave's current regional notice says Wave shifted focus to the United States and Canada. Wave's legacy-business FAQ says some legacy businesses moved to the Starter Plan on June 1, 2026, depending on account state and paid services.

Collaborator access is another practical check. Wave's subscription-fee article says admin and editor users on the business have access to the receipts scan feature. If a teammate cannot see the receipt controls, confirm the active business profile, role, plan or Receipts subscription, and country/account state before treating the missing receipt as a processing failure.

Wave documents both mobile and web receipt scan paths. In the mobile app, users go to Accounting > Receipts, use the camera, and can add multiple receipt images before tapping Done. Wave says a successfully uploaded image is added to recent scans and creates an expense transaction on the Transactions page.

On web, Wave says users can upload receipt files from the Receipts page or from Accounting > Transactions > Add transaction > Scan receipt. Its scan-upload article currently lists JPG, GIF, PNG, and PDF for web receipt upload, up to 10 files at a time, with each file up to 5 MB. If a file was outside that scan-upload shape, re-save it into a documented format and test one clean file.

The diagnostic question is not only “did I upload it?” It is “which surface did I use, and what did Wave say it created?” A mobile scan with incomplete details needs review. A web upload that created a transaction may be visible on the Transactions page even if you first looked only in a dashboard or report.

Wave does not use a single public receipt email address. Wave says users create a receipt forwarding email address from Receipts in a web browser or from Accounting > Receipts in the mobile app. The same help article says the forwarding email cannot be changed after it is saved.

That makes stale contacts and copied addresses a real source of “missing” receipts. Copy the address again from Wave before testing. On web, Wave says the forwarding address is at the bottom of the Receipts page. In the mobile app, it appears under the Email forwarding address section after tapping the three-dot menu in Receipts.

Run a controlled test before broad troubleshooting. Copy the address directly from Wave, send one known receipt from your own mailbox, and wait for the result in Receipts and Transactions. If that test works, the problem is likely an old destination, email package, rule, sender pattern, or attachment behavior rather than Wave account access.

Wave's current forwarding article says you can send receipts to your forwarding email from any email address. It also says you can only email one receipt at a time. Those two facts belong together: sender address may not be the blocker, but email shape often is.

A vendor email can include a receipt PDF, a logo, a shipping notice, a refund note, calendar files, and a portal link in the same thread. A person can understand which item matters, but receipt forwarding systems are built around a much cleaner package. If you forwarded a multi-attachment thread, split the documents and send one receipt per email.

Also distinguish a receipt file from a receipt-looking email. Wave's receipt scan documentation names supported upload formats; it does not say that a login-only portal page, encrypted file, or ambiguous notification email will become the expected transaction. Download the actual receipt when needed, then forward or upload the supported document by itself.

Wave's receipts scan feature is different from manually attaching a file to a transaction. Wave says scan and upload receipts can create expense transactions. It separately documents Upload receipt from Accounting > Transactions as a way to attach a saved file to an existing or newly created transaction in a web browser.

This distinction explains many false alarms. If you used Upload receipt from a transaction dropdown, the file belongs on that transaction. It may be visible through the transaction receipt icon or receipt filters, not as a new recent scan waiting to become a transaction. If you expected a new expense transaction, use the scan/upload or receipt forwarding path instead.

The file format list is also broader for attachment-only than for scan upload. Wave's attachment article lists formats such as JPG, JPEG, GIF, TIFF, TIF, BMP, PNG, PDF, and HEIC for attaching receipt files to transactions. Do not use that broader attachment list to assume every format is valid for the scan-upload or email-forwarding result you expected.

Wave receipt scan does not remove review work. Wave's verify/edit article says users can review or edit a receipt transaction in a web browser from Receipts, and can edit a receipt transaction in the mobile app from Accounting > Receipts. On web, users can review the original receipt details, edit fields, split the transaction, add tax, customer, vendor, and notes, then save.

That means “not showing up” may mean “not reviewed yet,” “missing details,” or “not visible in the list I checked.” Wave's transaction receipt filter can show transactions created from scanned receipts, any transactions with receipt attachments, or transactions without attachments. Wave also uses receipt icons and dots to indicate scanned receipts and missing transaction details.

Mobile and web are not identical for review. Wave's verify/edit article says receipts can only be marked as reviewed in a web browser. If a teammate edited the receipt on mobile but expected it to be marked reviewed, finish that specific review action on web.

Wave's scan-upload article says Wave automatically merges duplicate expense transactions with created receipt transactions. Its auto-updates article narrows the mechanics: Wave merges when a receipt upload, paid bill, or paid invoice matches an imported transaction with the same account and amount. If an imported transaction has multiple potential matches, Wave says it will not merge it automatically.

This matters when users resend receipts during troubleshooting. If you scan, upload, forward, and manually create a withdrawal for the same purchase, you may create several objects that need review. If Wave merges the receipt transaction with a bank-imported transaction, the receipt may still be present, but the visible record changed. Wave says a merged transaction with an attached receipt keeps the image attached and can be viewed from the receipt icon.

Before resending, search by amount, date, vendor, and receipt status. If the receipt exists on a merged transaction, document the result and stop sending duplicates. If it did not merge, decide whether to manually merge transactions or delete a duplicate based on your bookkeeping process.

Wave processes receipts after they arrive in Wave. Expensent helps one step earlier: it connects to the inbox, finds likely receipt and invoice emails, separates items that are ready to forward from items that need download or review, and routes selected supported documents toward the Wave forwarding address you configure.

Use Expensent when the real problem is the inbox handoff before Wave sees anything. Common examples are subscription receipts buried in old email, vendor messages with several attachments, portal-only receipts that need download first, stale mailbox rules, and teams that need a visible review queue before forwarding to Wave.

Keep the boundary clear. Expensent does not replace Wave receipts, Pro Plan or Receipts subscription access, Wave's scan processing, accounting review, categorization, reconciliation, or duplicate-merge decisions. It helps make sure the right email receipts are found, reviewed, and routed before the Wave workflow starts.

Escalate only after you know where the trail breaks. Contact an email administrator when a rule did not forward, a security policy changed the message, or an attachment was stripped. Contact Wave support when the receipt reached the correct Wave workflow but does not behave like Wave's current help articles describe. Handle it internally when the issue is a wrong business profile, stale forwarding contact, multi-receipt email, skipped review step, or duplicate resend.

A useful escalation includes the active business profile, user role, subscription state, region if relevant, intake path, forwarding address used, original sender, sent time, file name and type, whether there was one receipt in the email, and the exact area checked in Wave.