Emburse Certify Receipt Email Addresses: Which One Is Current?

If you are using Emburse Professional, also called Emburse Expense Professional and still searched as Certify, the safest answer is: verify the receipt address shown in your account or current finance-admin instructions before creating a forwarding rule. Current official public sources do not line up cleanly.

The Emburse Professional Emailing Receipts help article reviewed for this guide still names receipts@certify.com. The March 13, 2026 Emburse Professional release notes say receipt submission was updated to receipts@pro.emburse.app and that receipts@certify.com remains active temporarily. That is an official-source conflict, not a user mistake.

For a one-time test, both addresses may be visible in old instructions, inbox history, or team docs. For a repeatable workflow, do not settle the question by memory. Open Emburse Professional, check your current help-center or in-account instructions, and ask your admin which destination the company wants employees to use.

The naming problem is real because product language, old bookmarks, training materials, and help-center URLs are not all using the same terms. Current Emburse product pages and help articles use Emburse Professional and Emburse Expense Professional language. Older domains, help URLs, and many finance teams still say Certify because that is the name employees learned first.

When a receipt email address is involved, the name matters less than the product and workflow. Emburse Professional is the relevant product for the receipts@certify.com versus receipts@pro.emburse.app question. Other Emburse products can have different help centers, different upload flows, and different sender rules.

Use Certify as historical or search-intent language, not as proof that a Certify-domain destination is still the best address. Use Emburse Professional or Emburse Expense Professional for current instructions, then point users to the address their account documents.

The conflict is specific. The Emailing Receipts article says users can email receipt attachments or expense data to receipts@certify.com, and that the receipt or expense data will be parsed and added to the Emburse Professional Wallet. The same article lists PDF, JPEG, JPG, and PNG as accepted major image file types for email submission and says the total email must be under 6 MB.

The March 13, 2026 release notes describe a broader domain transition from expense.certify.com to pro.emburse.app. In the What Changed list, Emburse says product URLs moved to pro.emburse.app, system emails now originate from the pro.emburse.app domain, and receipt submission email was updated to receipts@pro.emburse.app. The note also says the legacy receipts@certify.com address remains active temporarily.

Those two sources are both official and both relevant. The release notes are newer and specifically discuss the domain transition. The Emailing Receipts article is the workflow article users are likely to find when they search for how to email receipts. That is why the practical guidance is qualified: use the newer Emburse-domain address when your account or admin confirms it, but do not assume old team docs have caught up.

Emburse is a family of products, not one shared receipt inbox. The official Emburse Help Centers page sends users to separate help centers for products such as Captio, Cards, Nexonia, and Tallie. That structure matters because a receipt address documented for one product should not be copied to another product.

Tallie has its own official receipt-email article and tells users to send receipts to receipts@usetallie.com. Nexonia has a separate article for adding expense receipts by email and tells users to send to receipts@nexonia.com. Captio documents expenses@captio.com for digital expenses received as PDFs. Emburse Cards documents receipt requirements around transaction receipt requests and cardholder upload links rather than the Professional Wallet address.

That means there is no single Emburse receipt email address. A company using Emburse Cards, Emburse Captio, Emburse Nexonia, or Emburse Tallie should not inherit Emburse Professional instructions unless the product itself or an administrator confirms that workflow.

The sender can decide whether the receipt lands correctly. For Emburse Professional, the additional-email article says receipt emails must come from your Emburse Professional username email address. If receipts arrive in another inbox, the user must add that additional sender address on the My Account or Account Details page before using it for receipt submission.

This matters for aliases, shared finance inboxes, forwarded employee mail, and automation tools. A receipt sent to the right destination from an unrecognized sender can fail or land somewhere unexpected. Before turning on recurring routing, send one recent receipt from the real sender address and verify that it appears in the expected Wallet.

Other Emburse products use their own sender rules. Nexonia says receipts can come from the email associated with the account or another authorized address, and its linked-email article says the linked address is only for receipt submission, not login. Tallie documents adding and verifying an additional email address. Captio documents registering alternate email accounts for its digital-expense email function. Do not transfer one product rule to another.

For Emburse Professional, the destination is only the intake step. The Emailing Receipts article says receipt attachments or expense data sent to the receipt submission address are parsed and added to the Emburse Professional Wallet. The Wallet is where receipts and expenses are stored before being added to an expense report.

Wallet review still matters. Emburse Professional help says item details can come from manual entry or Emburse Receipt Transcription, and the user may need to edit details if they are incorrect. A separate Wallet article explains that Merge Items can combine matching receipts and imported credit card expenses visually when date and amount match, while organization settings can restrict imported card expenses as read-only.

Do not treat receipt email forwarding as a replacement for review, policy, approval, reimbursement, or export steps. The receipt address gets proof into the Emburse workflow. Emburse Professional still controls what the Wallet shows, what OCR or transcription fills, when a receipt joins a report, and how the downstream finance process behaves.

Use this checklist before you save an address in a mailbox rule, employee instructions, or an Expensent destination. The goal is not to memorize which address is right for every account. The goal is to prove the exact path your company will use.

Start with product identity. Are you in Emburse Professional, Emburse Expense Professional, Nexonia, Tallie, Captio, Cards, Spend, or Enterprise? Then confirm the receipt destination from the product help center, account UI, or finance-admin instructions. For Professional, specifically ask whether the company has moved to receipts@pro.emburse.app or is still using receipts@certify.com during transition.

Next, prove the sender. Send from the same mailbox, alias, or connected account that will be used later. Attach or include one clean recent receipt that fits the product rules. Check the expected landing area: Professional Wallet, Nexonia Receipt Wallet, Tallie Purchases, Captio Captures, card transaction receipt upload, or the product-specific queue your admin names.

Expensent belongs before Emburse processes the receipt. It helps with the messy inbox layer: likely receipt emails arrive across employee inboxes, shared mailboxes, old email history, and vendor patterns that change over time. A broad Gmail or Outlook rule can send the wrong messages or miss old ones.

With Expensent, the user connects the inbox, reviews likely receipt and invoice emails, forwards selected messages to the Emburse destination they configure, and creates rules from real sender-and-subject patterns that have already been checked. The rule still depends on the correct Emburse product destination and sender setup.

That positioning is deliberately narrow. Expensent does not replace Emburse Professional, Certify, Wallet, OCR, transcription, reports, approvals, policies, reimbursements, corporate cards, or exports. It helps make the inbox handoff more controlled before those Emburse workflows begin.