How to Automate Brex Receipts Without Gmail Rules

Brex documents several ways to add receipt evidence, and each has a different control point. A person can forward an online receipt to receipts@brex.com. Gmail and Outlook rules use receipts+forwarding@brex.com in Brex's instructions. Gmail organizations can use the Brex Google Workspace add-on. A user who already knows the expense can attach the receipt directly in the Brex dashboard or app.

These paths are not interchangeable labels for the same automation. Manual forwarding depends on the user choosing the message. A mailbox rule depends on its conditions. The Workspace add-on applies Brex-defined Gmail labels and a scheduled collection cycle. Direct attachment skips automatic email matching because the user selects the expense.

The useful decision is therefore where selection should happen. Use a Brex-native automated channel when its selection logic and access model fit. Add upstream review when finance needs to inspect the receipt evidence before anything is sent to Brex.

For an individual online-expense receipt, Brex tells the user to forward the message to receipts@brex.com. Brex says the receipt may appear directly in the email body or be included as an attachment. That makes this the appropriate destination when a person or an upstream review tool has selected a specific receipt message.

The sender is part of the receipt handoff. Brex requires the email to be forwarded from an address associated with the user's Brex account or account copilot. Sending the same document from an unrelated shared inbox, accounting-firm address, or alias does not remove that requirement.

A successful send is not proof of a successful match. Brex says a copy appears under Attached receipts only when it successfully matches an expense, and only receipts less than two months old match automatically. The expense record in Brex is where the user should confirm the result.

Brex documents receipts+forwarding@brex.com inside its Gmail and Outlook rule instructions. That plus-address is the destination to use when following Brex's native mailbox-rule workflow. It should not be collapsed into the manual-forwarding guidance for receipts@brex.com.

The automation risk is in message selection. A rule can send every message that satisfies its conditions, even when the sender also produces order notices, credits, cancellations, or non-receipt updates. Brex can attempt to process what arrives, but the mailbox rule does not know whether a message should become evidence for a particular expense.

This is where an alternative to Gmail rules earns its place: selection can happen in a receipt review workflow before the message is sent. The Brex destination remains the documented manual receipt path, and the downstream Brex controls remain unchanged.

Brex for Google Workspace is not merely another forwarding address. Brex says the add-on identifies potential expense receipts using terms such as payment, receipt, invoice, Mastercard, and order. It applies a Receipt to be sent to Brex label, and after automatic collection is enabled, relevant labeled emails are sent to Brex once hourly.

That model has useful administrative controls. A Workspace admin can install it for everyone or selected groups, while each user turns automatic collection on. Brex also says installation may take up to a day and recommends leaving its labels and filters unchanged so collection continues to work as designed.

The tradeoff is that selection follows Brex's add-on logic rather than a finance user reviewing each candidate first. It is Gmail-specific, requires the requested mailbox permissions, and still depends on account association: Brex says the add-on may be installed on Gmail accounts that are not associated with Brex, but receipts from those accounts will not be delivered. Brex also says users should turn collection off before uninstalling because uninstalling alone may leave collection running.

Receipt automation is easier to diagnose when four outcomes stay separate. Delivery means the email reached the Brex intake path. Automatic matching means Brex associated the evidence with an expense. Attachment means the receipt is visible on that expense. Verification is the later comparison between the receipt and expense data.

Brex says automatic email matching applies only to receipts less than two months old. Separately, its auto-validation control compares merchant, amount, and purchase date. Where that feature is enabled, a receipt is considered validated when at least two of those three fields match. Brex describes validation as best effort and notes that results can depend on image quality, merchant data, account settings, and admin review.

The two-of-three threshold therefore should not be used as a promise that an emailed document will attach. A receipt can fail before validation because the sender is ineligible, the evidence is missing from the body or attachment, the receipt is outside the matching window, or no expense match is found. It can also attach and then fail verification.

Expensent can connect to the mailbox where receipts arrive, surface likely financial-document messages in the Action Center, and let the user inspect a receipt before forwarding it. For a recurring message type, the user can create an auto-forward rule based on an email pattern and subject pattern from the reviewed message.

For Brex card receipts selected this way, configure the documented manual receipt destination, receipts@brex.com. The connected sender mailbox must still satisfy Brex's account or account-copilot requirement. Expensent cannot make an unrelated sender eligible and should not be presented as a bypass for Brex controls.

This layer changes selection and routing, not the Brex outcome. It can prevent a broad mailbox rule from deciding what enters Brex, and it can keep uncertain messages available for review. It cannot choose the matching expense, force an attachment, pass the two-of-three validation test, clear a policy requirement, or approve an expense.

When an emailed receipt does not appear on the expected expense, first confirm that the message came from an associated sender and contained the receipt in its body or attachment. Then check the receipt age. Re-sending an item older than Brex's automatic matching window does not make it younger.

If the expense is known, open it in the Brex dashboard and add or drag the receipt file into the Receipt section. In the Brex app, open the expense from Wallet and use the add control. This direct path avoids asking Brex to infer which expense should receive the document.

After attachment, keep the remaining work in Brex. A failed verification message, missing memo, policy flag, or approval task is a Brex expense-control issue. Expensent can help recover and route the source receipt email, but it does not override those states.