Where a FreshBooks Receipt Can Disappear

When a FreshBooks receipt is missing, start by naming the intake path, not the expected accounting result. FreshBooks has several receipt paths: Send by Email into Uploads, manual web upload into Uploads, mobile receipt scanning into Uploads, manual attachment to an existing expense or bill, and review of a scanned document into a new expense or bill. Those paths do not all create the same visible state.

If you emailed a document to the unique FreshBooks address, check Expenses > Uploads first. If you scanned on iOS or Android, check the mobile Uploads review banner and the Uploads area. If you manually attached a file to an existing expense or bill, look on that record; it may never appear as a separate Uploads item. If you reviewed a scanned document and created an expense or bill from it, FreshBooks says the document moves out of Uploads and into the expense or bill list.

This first distinction saves time. A receipt that is attached to a bill is not missing from FreshBooks; it is missing from the place you expected to see it. A document waiting in Uploads is not a completed expense. A mobile scan waiting for review is not a bill until you finish the bill path on web. Treat each destination as a separate queue.

FreshBooks Send by Email uses a unique email address shown inside eligible accounts under Expenses > Uploads > Upload Documents > Send by Email. It is not a shared public FreshBooks address. If you copied an old address, used a teammate account, pasted a typo into an email rule, or gave a vendor the wrong destination, the document may never enter the Uploads workflow you are checking.

The cleanest test is a controlled resend. Copy the address directly from FreshBooks again, send one clear PDF or image from your own mailbox, and wait for the documented processing window. Do not test with a vendor email containing signatures, icons, a portal link, and several attachments.

Also confirm account availability. FreshBooks support says receipt scanning is available in Canada, the United States, and the United Kingdom on trials and Plus, Premium, and Select plans, with the correct country selected in Basic Information settings. Expensent can route email receipts toward a configured destination, but it cannot make FreshBooks expose Send by Email where FreshBooks has not made it available.

FreshBooks is strict about emailed receipts. Its Send by Email notes say only one document containing one receipt image can be emailed at a time, and multiple attachments are not supported. A vendor email with three PDFs, two images, and a signature logo is not one clean receipt submission even if a person can tell which attachment matters.

If you sent multiple documents, split the message. Put each supported receipt or bill document in its own email. If a PDF contains several receipts, split the PDF first instead of expecting FreshBooks to create several review items from one file. If the email contains a signature image, remove it because FreshBooks specifically warns that other images, including email signatures, can be accidentally scanned and uploaded instead of the intended document.

Broad Gmail or Outlook forwarding can make this worse. A filter forwards the whole message it matched; it does not know which attachment FreshBooks should scan or whether a vendor bundled invoice and receipt files together. If the original message is cluttered, fix the package before sending it again.

FreshBooks says emailed documents must be in the email body as an inline JPEG, PNG, or PDF image, or included as an attachment. It also says the document should not be a link to download outside the email. That distinction matters for subscription vendors, travel portals, marketplaces, and utilities that send a notification email instead of the actual receipt file.

A portal-only email can look like a receipt to a person because it includes a total, a date, and a button. But FreshBooks cannot scan a login-required web page from a link in the message. Download the actual receipt or bill first, confirm it is a JPEG, PNG, or PDF, and send that file as the only document in a new email.

Manual receipt attachment has a separate failure pattern. FreshBooks support says JPEG, PNG, and PDF receipts can be attached to bills and expenses. Its upload FAQ lists temporary issues, browser problems, corrupted or non-standard files, and files over 2 MB as possible reasons a receipt upload may fail. Keep that 2 MB note tied to manual attachment unless FreshBooks shows the same limit for Send by Email in your account.

FreshBooks mobile receipt scanning is related to Uploads, but it is not the same as emailing documents or finishing bill review on web. FreshBooks iOS and Android support pages describe scanning an expense receipt with the camera or choosing a photo, then uploading it to Uploads as a document. The mobile pages say scanning can take up to 10 minutes before the document is available to review.

FreshBooks mobile review creates an expense when you save the scanned document. The iOS and Android pages also include an important note: to create a bill from a document, upload the receipt and complete the remaining steps in a web browser. If you expected a mobile scan to become a bill automatically, the document may be waiting for the web bill path rather than missing.

Web uploads and emailed documents have a different timing note. FreshBooks says uploaded JPEG, PNG, or PDF files can take 30 minutes to several hours to scan depending on image type and number of files. So a missing mobile scan after five minutes and a missing emailed PDF after five minutes are not the same diagnostic case. Use the timing and platform that match how the document entered FreshBooks.

A FreshBooks scanned document can become either an expense or a bill during review, but those records mean different things. FreshBooks describes expenses as immediate purchases from a merchant, while bills are purchases from a vendor that will be paid in the future and can create liabilities. A receipt attached to the wrong type of record will look missing to the person checking the other list.

In Uploads review, FreshBooks looks for potential matches first. If your account has expenses or bills that match the amount, currency, and a date within 0 to 2 days of the uploaded document, the Attach sub-tab can be selected by default. If no match exists, the Create New sub-tab is used, and you choose Expense or Bill under Document Type. That means a scanned document may be waiting for you to attach it, not waiting for FreshBooks to create a new item.

FreshBooks also has bill-specific plan nuance. The receipt scanning support page says automatic capture of multi-line items on a bill is only available for Select plans. The bills support page notes that if an account downgrades to a plan without Accounts Payable, existing bills can still be viewed and edited. Verify the account plan and bill workflow before resending the document.

FreshBooks receipt scanning does not mean the expense is finished. Support says scanned documents remain in Uploads until made into an expense, made into a bill, or deleted. If the document exists in Uploads, the next task is review. Open the item, check extracted fields, attach it to a match or create a new record, and save the result.

If the document is not visible yet, compare the elapsed time with the documented path. FreshBooks says emailed and web-uploaded documents can take 30 minutes to several hours to be scanned and ready to review. For mobile receipt scans, FreshBooks says the scan can take up to 10 minutes before it is available to review. During the wait, avoid repeated sends unless you have evidence the first message was wrong.

If scanning fails or produces poor extraction, FreshBooks lists several likely reasons: incorrect file type, temporary error, blurry photo, crumpled or faded receipt, light background, or odd angle. Those are document-quality problems, not routing problems. A clearer scan, flatter receipt, higher contrast, or fresh upload is a better fix than changing the destination address.

Repeated troubleshooting can create its own problem. If you send the same receipt several times, FreshBooks may leave you with duplicate review work or duplicate expenses after review. FreshBooks documents duplicate expense detection when two or more expenses have matching date, amount, and description, but it is still better to find the original upload or attachment before creating another record.

Also check whether the receipt is already attached where it belongs. FreshBooks manual attachment flows put a receipt thumbnail on the bill or expense. FreshBooks Uploads review can attach a scanned document to a matching bill or expense. Once that happens, the document is no longer a standalone mystery item in Uploads; it is evidence attached to the accounting record.

For team workflows, keep a small audit trail: original sender, FreshBooks destination, sent time, attachment filename, file type, intake path, and where the reviewer last saw it. That evidence separates FreshBooks behavior from inbox routing, browser upload, and internal handoff issues.

FreshBooks can scan supported documents after they arrive. Expensent helps one step earlier: finding receipt and invoice emails, showing which ones are ready to forward, and routing selected supported documents toward the FreshBooks destination you configure. That is useful when the real failure is not FreshBooks OCR, but a messy inbox-to-Uploads handoff.

Use Expensent to catch emails that need a download, review emails with several attachments, and route only the supported document FreshBooks should receive. For recurring patterns, create rules from reviewed sender and subject patterns instead of relying on broad mailbox filters. FreshBooks still controls Send by Email availability, scanning, Uploads review, bills, expenses, and final bookkeeping decisions.

Expensent does not replace FreshBooks receipt scanning or approve accounting records. It gives the team a visible checkpoint before FreshBooks receives a receipt email, so the wrong destination, portal-only message, signature image, multi-attachment thread, or stale inbox rule is easier to catch before month-end.

Escalate only after you know where the trail breaks. Contact an email administrator when a forwarding rule did not send, an attachment was stripped, or a security setting changed the message. Contact FreshBooks support when the document reached the correct FreshBooks workflow but failed to scan, stayed unavailable beyond the documented window, or behaves differently from FreshBooks support guidance. Handle it internally when the issue is a wrong address, unsupported message shape, skipped review step, or unclear bill-versus-expense ownership.

A useful escalation includes the original sender, FreshBooks recipient address used, sent time, attachment names and types, whether the document was inline, attached, or linked, upload path, FreshBooks area checked, elapsed processing time, and intended result. That turns a vague missing-receipt complaint into a traceable intake path.