Automate Emburse Receipts With the Right Product Route

Emburse is a product family, not one receipt inbox. Current Emburse pages present the former Certify expense workflow as Emburse Expense Professional, while the Professional help center and older Certify language remain visible. That naming overlap does not make Professional instructions valid for every Emburse product.

Treat product identification as the first automation control. A rule should have a documented product, a destination verified for that product and account, an eligible sender, a known intake channel, and a named downstream owner. If any field is unknown, keep the message in review instead of guessing a destination.

Use this matrix to choose the intake lane before creating an automation rule. The destination is an account control, not a value to infer from the Emburse name alone.

The Professional receipt-address transition is still visible in official sources. The current Emailing Receipts article and the March 13, 2026 release notes point to different primary addresses, with the release notes describing the older destination as temporarily active. The safe control is an account-visible or administrator-confirmed destination. The related address guide covers the transition in detail.

Sender eligibility is separate from destination accuracy. Emburse Professional says receipt submissions must come from the username email address unless the user adds another address on the account page. A shared mailbox, alias, personal inbox, or delegated sending identity must therefore be registered where that Professional account supports it before automation relies on it.

Expensent can route from the connected inbox, but it cannot make an unregistered sender eligible or prove that Emburse accepted the message. Keep the route in review until the sending identity and destination are both confirmed.

For the Professional email lane, official help lists PDF, JPEG, JPG, and PNG and says the total email must be under 6 MB. That total includes message text and signatures, not only receipt attachments. A file that is under 6 MB can still be part of an email that exceeds the channel limit.

The Professional web-upload lane uses a different model. Its help article describes individual image uploads up to 6 MB; when uploading multiple images, each file must be smaller than 6 MB and the combined files must be smaller than 10 MB. Those numbers describe web upload, not email, mobile capture, or another Emburse product.

Route only a message that contains usable receipt proof for the chosen lane. Portal notices, unsupported files, oversized messages, and ambiguous threads belong in the exception lane for a person to resolve.

Emburse Professional describes Wallet as the place where receipts and expenses are stored before they are added to an expense report. Receipt data can require review or editing, and an organization may make imported credit card expenses read-only. Arrival is therefore evidence of intake, not evidence of a completed expense.

Merge Items is also downstream. Official help describes it as a Wallet view that can visually combine a receipt with an imported card expense when date and amount match. It does not make Expensent responsible for card matching, field correction, report creation, or approval. For missing, unmerged, or read-only items, use the related Wallet troubleshooting guide rather than changing the inbox route blindly.

Not every receipt email should become a recurring rule. Keep a message in review when the product is unclear, the destination is not verified, the From address is not eligible, the message exceeds the email limit, the receipt requires a portal download, or the sender mixes receipts with refunds, account notices, and travel changes.

A product-family exception is different from a noisy-email exception. For Nexonia, Tallie, Captio, Cards, Spend, Enterprise, or any other Emburse product, assign the case to that product's administrator or current help center. Do not test the Professional destination and interpret a failure as an Emburse-wide limitation.

Once the product, destination, sender, and document package are known, Expensent rules can use the reviewed email and subject pattern for repeatable routing. Exceptions remain visible for manual action instead of being forced through an uncertain path.

Expensent owns inbox discovery, human review, and routing to the destination the user configures. For repeatable cases, rules use an email pattern and subject pattern from a reviewed message. That provides a controlled handoff without turning Expensent into the expense system of record.

Emburse Professional owns acceptance rules and everything after intake: Wallet, receipt transcription or channel-specific OCR, editable fields, imported card behavior, Merge Items, reports, approvals, policy controls, reimbursements, and exports. The automation is correctly scoped when each exception has a clear owner on one side of that boundary.

Document each recurring route in terms that another finance owner can verify: exact Emburse product, destination source, connected From address, expected attachment type, email or native-upload channel, and the person who owns exceptions. Record the date the destination was confirmed because the Professional address transition makes an old saved contact poor evidence on its own.

The record should also define success at both boundaries. Expensent success means the reviewed message was routed to the configured destination. Emburse success means the item appeared in the expected Professional Wallet and remained available for the required review. A sent-mail entry proves the first event, not sender acceptance, parsing, Wallet placement, merge, or report completion.

When a route stops behaving as documented, pause that rule and use the evidence to choose the owner. Destination or sender changes return to the intake owner; file and channel exceptions return to manual review; Wallet, merge, report, or permission issues stay with the Emburse user or administrator.