A Review-First Email-to-FreshBooks Receipt Workflow

A direct Gmail filter solves one narrow step: it sends a message to an address. FreshBooks needs more than a matching sender or subject. Its Send by Email workflow expects a document in a specific shape, sends that document to Uploads, and leaves the accounting decision for review.

That difference matters because FreshBooks says Send by Email supports one document containing one receipt image at a time. Multiple attachments are not supported, and unrelated inline images or signatures can be scanned instead of the intended document. An email with a receipt PDF plus terms, logos, or another receipt may match a Gmail filter while still being a poor FreshBooks input.

The useful alternative is reviewed upstream routing. First identify an email that consistently carries a FreshBooks-ready document. Then route it to the unique address from the correct FreshBooks account. Finally, review the result in Uploads rather than treating delivery as a posted expense or bill.

FreshBooks exposes the account-specific destination under Expenses, Uploads, Upload Documents, Send by Email. Copy that address from the FreshBooks account that should receive the documents. Do not substitute a general FreshBooks contact address or reuse an address copied from a different business.

FreshBooks currently 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 that availability in the receiving account before building a routing workflow around Send by Email.

Documents emailed to that address are scanned and placed in Uploads for later review. FreshBooks says scanning can take from 30 minutes to several hours, depending on the image type and number of files. The document remains in Uploads until it is made into an expense or bill, attached to a likely match, or deleted.

This makes Uploads a staging area, not an email archive and not an automatic posting destination. The upstream workflow should deliver a clean source document. FreshBooks then extracts available details and presents the accounting choice to the reviewer.

FreshBooks lists JPEG, PNG, and PDF as accepted receipt-scanning formats. For Send by Email, the document must appear inline in the message or as an attachment. A link to a portal or download page is not the document FreshBooks needs, so download the actual file before using web upload or sending a clean email.

Inspect the complete message, not only the filename. FreshBooks warns that email signatures and other images can be scanned instead of the receipt. A message that looks like a single-receipt email in Gmail may contain embedded logos, tracking images, or multiple attachments that make it unsuitable for direct forwarding.

Upstream review should therefore answer a FreshBooks-specific question: is this message already a clean one-document input? If yes, it can be routed to Send by Email. If no, isolate the document first or use the FreshBooks upload path after downloading it.

The one-document rule should be the central acceptance test for automated email routing. A recurring vendor message with one clean PDF is a stronger candidate than a digest, statement, or invoice thread with several files. The sender can be trustworthy while the message shape is still wrong for FreshBooks.

When a message contains multiple attachments, select or separate the intended receipt before forwarding. When the only useful content is a receipt rendered in the email body, verify that extra inline images will not compete with it. When the receipt is behind a link, download it and use a new one-document handoff.

This packaging step is not accounting classification. It simply gives FreshBooks the document shape its support workflow expects. The expense-or-bill decision still belongs in FreshBooks Uploads.

FreshBooks distinguishes an expense from a bill by payment timing. A purchase paid in full upfront is an expense. A vendor purchase for which payment is due later is a bill, and bills are part of Accounts Payable on eligible FreshBooks accounts.

Send by Email does not require the mailbox rule to make that accounting decision. After scanning, FreshBooks presents the document in Uploads. The reviewer can attach it to a likely existing expense or bill, or use Create New and choose Expense or Bill before checking the populated fields.

Use a more direct destination when the intended record is already known. FreshBooks offers Upload Receipt from the expense workflow and Upload Bill from the Bills workflow. If the expense or bill already exists, attaching the source document to that record may be clearer than sending it through general Uploads.

An Expensent auto-forward rule matches a sender email pattern and a subject pattern. A rule can require an attachment, and its attachment filter can forward all attachments or include selected attachment types. Those positive controls are useful for a recurring FreshBooks-ready message, such as one stable sender and subject that consistently carries one supported receipt file.

Expensent does not add arbitrary negative phrases or an exclusion-language field to an auto-forward rule. Do not translate a Gmail negative-filter technique into an Expensent setup instruction. If a known unwanted message pattern should be blocked, Expensent models that as a separate reject rule with its own sender and subject match.

Start from an email you have reviewed, create a narrow rule for that observed pattern, and keep uncertain shapes in review. Requiring an attachment or including only relevant attachment types can reduce noise, but neither control proves that FreshBooks will see exactly one receipt image. The one-document check still matters.

A FreshBooks-specific upstream workflow has four checks. Confirm that the email belongs to the correct business, that it contains the actual document rather than a download link, that the document type is supported, and that the message contains one receipt document for the handoff.

Use Expensent review for patterns that do not yet meet those checks. Use an auto-forward rule only after the sender, subject, and attachment behavior are stable enough for the FreshBooks constraint. Route the selected document to the unique Send by Email address configured for that FreshBooks account.

After delivery, open FreshBooks Uploads and review the scan. Check whether FreshBooks found a likely expense or bill match. Otherwise choose the correct record type, verify the populated fields, and create the record. This preserves review on both sides of the handoff: document eligibility before FreshBooks and accounting treatment inside FreshBooks.