FreshBooks Receipt Scanning vs Email Forwarding: Which Should You Use?

Use mobile scan or photo capture for a paper receipt in your hand. Use web Uploads for a JPEG, PNG, or PDF saved on your computer when FreshBooks should scan it. Attach the file directly when the expense or bill already exists. Use Send by Email when one clean supported receipt document already lives in email.

These methods do not decide the accounting destination for you. A purchase paid upfront belongs in the expense workflow. A vendor amount due later belongs in the bill workflow when Accounts Payable is available. FreshBooks still requires review of scanned details before a new record is created or a document is attached to a match.

Reviewed upstream routing is relevant only to emailed documents. It can help decide which email is ready for the FreshBooks handoff, but it does not replace mobile capture for paper, FreshBooks OCR, Uploads review, or the expense-versus-bill decision.

Each row uses the same six checks: source document type, FreshBooks destination, user action, whether the Send by Email one-document constraint applies, review location, and the fallback when capture fails.

FreshBooks documents receipt scanning in its iOS and Android apps for expense receipts. The user opens Expenses, takes a photo or chooses one from the library, adjusts the crop if needed, and uploads it to Uploads. OCR then populates fields for review before the mobile app creates the expense with the receipt attached.

This is the direct path for restaurant slips, fuel receipts, and other paper proof collected away from a computer. A flat, well-lit receipt gives the scan a better input than a crumpled, faded, blurry, or sharply angled photo. Long-receipt mode is available in the documented mobile flow for capturing a receipt in sections.

Mobile review is expense-focused. FreshBooks tells Android users to complete the workflow in a web browser when the document should create a bill. Treat that as a destination decision: capture can begin on the phone, but a payable vendor document may need web review before it becomes a bill.

Web Uploads is the flexible scan path for saved JPEG, PNG, and PDF documents. FreshBooks offers general Upload Documents, Upload Receipt from the expense menu, and Upload Bill from the bills menu. After scanning, the document remains in Uploads until it is used to create an expense or bill, attached to a potential match, or deleted.

Direct attachment solves a different job. If the correct expense or bill already exists, open that record and attach the receipt there. FreshBooks documents JPEG, PNG, and PDF attachments for both record types and says uploaded receipts can be downloaded later. This avoids asking the scan workflow to propose a new record when the destination is already known.

Choose Uploads when OCR and matching may help. Choose attachment when the accounting record is settled and the file is supporting evidence. If direct attachment fails, FreshBooks recommends checking the 2 MB limit, retrying, trying another browser or private browsing, and re-saving files that may be corrupted or use non-standard formatting.

FreshBooks provides a unique Send by Email address under Expenses, Uploads, Upload Documents. An inline or attached JPEG, PNG, or PDF sent to that address is scanned and placed in Uploads for review. FreshBooks says the scan can take between 30 minutes and several hours.

The input rule is strict: one document containing one receipt image per email, with no multiple attachments. Remove signatures and other inline images because FreshBooks warns that they can be scanned instead of the intended receipt. A download link by itself is not a supported Send by Email document.

Email forwarding is therefore a capture choice, not automatic bookkeeping. Once the document appears in Uploads, review possible matches or choose Expense or Bill under Create New, verify the extracted fields, and then create or attach the record.

A capture method answers how the proof reaches FreshBooks. The destination answers what record the proof supports. FreshBooks defines an expense as a business purchase already paid upfront. It defines a bill as a vendor purchase for which payment is due later.

That distinction applies across capture methods. A photographed lunch receipt normally becomes an expense. A saved contractor invoice due next month may become a bill. An existing bank-imported expense may need only a direct attachment. Uploads can also show potential expense or bill matches based on amount, currency, and a nearby date, but the reviewer still chooses the correct record.

Bills and vendors are part of FreshBooks Accounts Payable, which FreshBooks currently documents for trials, Premium, and Select plans. Separately, FreshBooks documents receipt scanning for accounts 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. Confirm both controls in the specific account rather than assuming every capture path can create every destination.

Mobile capture should fail back to another copy of the image: retry in the app, export it, or upload it on the web. Web Uploads should fail back to file and browser checks. Direct attachment should fail back to the documented size, browser, corruption, and formatting checks. Send by Email should fail back to a cleaner one-document message or a manual web upload.

Do not use the same troubleshooting checklist for every source. A bad paper scan is usually an image-quality problem. A failed attachment may be a file-size or browser problem. A missing emailed document may still be scanning, may include competing images, or may violate the one-document rule.

For ongoing inbox review and routing design, use the separate FreshBooks automation guide. This page stops at choosing the capture method and identifying where its review and fallback belong.