Automate Receipt Emails to Wave

Expensent finds current and historical receipt emails and sends selected documents to the Wave forwarding address saved for the correct business.

Confirmed sender-and-subject patterns can route new recurring receipts automatically. Keep one receipt in each email so Wave receives the intended document.

Wave continues with scanning, transaction creation, attachment, categorization, and reconciliation.

Wave currently documents two rules that shape the inbound envelope: receipts can be sent to the saved forwarding address from any email address, and only one receipt can be emailed at a time. The sender is therefore not an authorization boundary. The destination and the contents of the message carry the control.

Any-sender support is useful when receipts arrive across an owner mailbox, purchasing alias, employee inbox, or upstream routing service. It also means a workflow should never infer the Wave business from the sender alone. A marketplace, card processor, or shared billing platform can issue documents for more than one entity.

Interpret one receipt per email operationally. A message with one clear receipt is a forwarding candidate. A message with several receipts, an invoice plus unrelated supporting documents, or a statement covering many charges needs separation or a different Wave path before routing.

Allow multiple source mailboxes only when the business destination remains explicit. Split bundled receipts before sending them to Wave. Keep statements, refunds, credits, and account notices in review unless the intended accounting path is clear.

Wave says receipt email forwarding automatically creates a transaction with the receipt attached. Its scan-and-upload workflow likewise creates a corresponding expense transaction after a successful receipt upload. Those routes are transaction-creation inputs, even when a matching imported expense may later be merged.

Wave's attach-receipt workflow starts from an expense transaction on the Transactions page and stores the selected receipt file on that transaction. It does not carry the same transaction-creation intent. This distinction should be decided before the handoff, especially when a bank feed has already supplied the expense.

Do not convert every document exception into an email forward. Portal retrieval, file upload, and attachment to an existing transaction use their matching Wave paths. Expensent keeps the source email available while the document is routed.

Forward or scan when the intended result is a receipt-created expense transaction. Attach when the intended result is a file on a known existing transaction. Keep the original email available until the Wave-side result is reviewed.

Wave documents automatic merging for certain duplicate expense transactions when a receipt-created transaction and a matching imported transaction share the required match conditions. That behavior is not a promise that every forwarded receipt will collapse into a bank-feed record.

Wave says it will not auto-merge when an imported transaction has multiple potential matches. Its attachment guidance also warns that manually creating a transaction before the same transaction is imported can produce a duplicate that may need manual merging.

The routing model should therefore record the expected Wave outcome as "new transaction, possibly merged," not "attachment guaranteed to match." The Wave reviewer owns confirmation, manual merge or unmerge decisions, and reconciliation impact.

Expect transaction creation first; treat auto-merge as a conditional Wave action. Review ambiguous or multiple match candidates manually. Do not let an upstream "sent" state imply that duplicate handling is complete.