Wave Receipt Automation: A Routing and Exception Model

Wave receipt automation starts with a destination map. For every business profile you operate, record the legal or operating entity, the Wave business name, and the receipt forwarding address displayed while that business is active. Do not use one account-level address as a catch-all: Wave applies receipt subscriptions per business profile, and the address you copy from Receipts must lead to the business that owns the expense.

Wave says a saved forwarding email cannot be changed. That makes the destination a durable workflow control. Copy it from Wave instead of typing it from memory, restrict who can edit the routing map, and update upstream rules only after confirming the active Wave business profile.

Plan eligibility is a precondition, not the subject of this workflow. Wave currently requires a Receipts or Pro subscription for receipt email forwarding. Use the plan explainer for eligibility and billing decisions; once access exists, this article governs routing and exceptions.

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.

A clean digital receipt for the correct business can go to that profile's saved forwarding address. A portal notice cannot: the notice is evidence that a document may exist, not the receipt document Wave is expected to process. Retrieve the file, confirm the business, then use receipt scan/upload or attach it to an existing Wave transaction.

A body-only e-receipt sits between those cases. Wave describes forwarding digital receipts and e-receipts, but its forwarding help article does not publish a separate channel-specific format table. Test the exact vendor shape before allowing repeat routing, and return it to review if the template changes.

An existing bank-imported expense changes the accounting intent. If the objective is to preserve a file on that known transaction, Wave documents an upload-receipt action on the transaction. That path is different from forwarding or scanning a receipt to create a receipt transaction.

Expensent owns discovery, review, and routing before Wave. It can surface likely receipt or invoice emails, let a reviewer forward selected items, and apply recurring rules based on email and subject patterns. It does not choose the accounting category, reconcile the books, decide whether Wave should merge transactions, or mark a Wave receipt reviewed.

Build a rule only when the sender and subject pattern also imply a stable business profile and document state. A dedicated billing sender with one consistent receipt is stronger evidence than a shared marketplace sender that mixes purchases, refunds, delivery updates, and account notices.

Use exception states explicitly: wrong business, portal download required, several receipts, uncertain document type, existing transaction, or bookkeeping review required. Those states should stop forwarding rather than broaden the rule.

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 require a person or downstream Wave process. Expensent can preserve the upstream item for review and routing, but Wave owns the resulting accounting record.

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.

Delivery to Wave is a handoff, not completion. Wave documents editing receipt transactions in both web and mobile, but says receipts can only be marked as reviewed in a web browser. If reviewed status is your close-out control, the process must return to Wave on the web.

The Wave reviewer should confirm the business, date, amount, account, category, tax treatment, vendor or customer context, notes, and duplicate state. Those are accounting controls outside Expensent's upstream scope.

Use separate statuses for routed and completed. "Routed" means the correct receipt was sent to the correct profile. "Completed" means the Wave transaction and any merge were checked and, where required, the receipt was marked reviewed in the web browser.