Brex Receipts Not Matching? How to Diagnose and Fix It

Open the card expense you expected Brex to match. The useful states are: no receipt is attached there, the receipt is attached to a different expense, or the receipt is attached but shows Receipt failed verification. Each state has a different fix.

For an emailed receipt, no attachment on the expected expense does not mean the document is waiting elsewhere in Brex. Brex says you can see an emailed receipt only when it was successfully matched with an expense. Check the email path to explain the miss, but attach the document manually to the known expense when you need a reliable fix.

If the receipt is on the wrong expense, compare nearby transactions before moving or replacing it. If it is on the right expense but failed verification, review the merchant, amount, purchase date, receipt quality, and company policy rather than troubleshooting email delivery.

Brex support says email receipts forwarded to receipts@brex.com must come from an email address associated with your Brex account or your account copilot. A shared mailbox, alias, bookkeeper address, or personal account may not provide the account context Brex requires.

Compare the sender with the address tied to the cardholder or account copilot. If the sender is wrong, correct that path for future receipts. For the current receipt, attach the file directly to the known expense instead of using repeated forwards as a test.

This is also why broad shared-inbox workflows need care. A finance inbox may receive many receipt emails, but Brex still needs the receipt to land under the right account context. If the cardholder is not the sender, verify the current account copilot and admin setup inside Brex instead of assuming the forwarding address alone is enough.

Brex receipt validation uses a two-of-three standard: merchant, amount, and purchase date. If at least 2 of those 3 fields match the expense, Brex can consider an attached receipt validated. If only one field lines up, an attached receipt can display a Receipt failed verification message.

The amount check is often the easiest to verify. Restaurant tips, hotel incidentals, foreign-currency charges, refunds, and pending-to-cleared changes can make the final card expense differ from the receipt you forwarded. Brex support notes that cleared expenses may have a higher amount than the pending charge, such as when a restaurant tip is added after the original authorization.

Merchant names also differ. The receipt might say the storefront name while the card network descriptor shows a parent company, processor, or location-specific label. Brex says merchant identification can sometimes appear differently than expected. If merchant identity is the only disagreement, use the receipt and expense details to decide whether manual attachment or admin review is appropriate.

Brex support currently says only receipts less than two months old match automatically when forwarded by email. That does not mean an older receipt is unusable. It means automatic matching is no longer the right expectation.

For older catch-up work, search for the expense and attach the receipt directly. For bulk cleanup, Brex documents dashboard upload for up to 500 receipts and shows details when files cannot be matched; unresolved files still need manual attachment to their expenses.

Expensent can help locate historical receipt emails, but forwarding an old message does not extend Brex's automatic email-matching window. Find the source document, then attach it to the expense in Brex.

For the email-forwarding channel, Brex says the receipt can be in the email body or an attachment. Separately, its upload guidance lists PDF, JPG, PNG, and XML files, with Mexico employees sometimes needing an XML CFDI file. Do not assume a portal link or login prompt gives Brex the underlying receipt.

When email forwarding fails, Brex recommends trying a different file type. For example, print or save the original receipt as a PDF, then manually embed the receipt in the email body or upload it as an attachment. This is a practical fix for HTML receipts, images that do not survive forwarding cleanly, and files that display well to a person but do not process reliably.

Expensent should be used honestly here. It can forward supported attachments, and body-proof receipt emails can be reviewed and forwarded from the Action Center. It does not make a portal-only message into a valid Brex receipt unless the actual receipt evidence is present or downloaded first.

Forwarding rules create a different failure path: the receipt may not leave the mailbox. Brex documents receipts+forwarding@brex.com for Gmail and Outlook rules, while a person manually forwarding an email uses receipts@brex.com. Confirm the address that belongs to the channel you used.

Google says Gmail forwarding requires adding and verifying the forwarding address before messages can be forwarded, and filters can forward messages that match specific criteria. Microsoft says Outlook inbox rules can forward or redirect messages, and the sender appearance differs between forwarding and redirecting. These are email-provider mechanics, not Brex matching rules.

The Google Workspace add-on is another distinct channel. Brex says it labels potential receipt emails and forwards relevant labeled messages once hourly after collection is enabled. Wait for that documented collection cycle before diagnosing the add-on, but remember that a forwarded receipt appears in Brex only after a successful expense match.

Manual attachment is the reliable fallback when you know the expense. In the Brex dashboard, open the expense, use the Receipt section in the details pane, and add or drag the file onto the expense. In the mobile app, open the expense from Wallet and use the + control to attach it.

If you need to add context, Brex documents memo entry in the dashboard, app, push notification, SMS, and email. For email specifically, Brex says that if you are already attaching a receipt to an expense by email, you can type memo: in the email body followed by the memo text.

After manual attachment, check whether the expense is still flagged or needs review. Brex documentation says failed validation can lead to a Receipt failed verification message and may be flagged for additional review depending on company policy. That review belongs inside Brex. Expensent can help route the receipt into Brex, but it cannot approve the expense or override policy controls.

When a receipt is attached to the wrong expense, inspect similar transactions before forwarding it again. Brex documents one specific duplication case: if a merchant reuses one authorization code across multiple expenses, receipts or memos can be added to expenses that share that merchant code.

If the receipt attached to the wrong transaction, compare the three validation fields against nearby expenses from the same merchant. Look especially at repeated rides, meals, SaaS renewals, or marketplace orders with similar totals. Remove or replace the receipt according to your Brex admin process, then attach the right document to the right expense.

First search expenses by merchant, date, amount, and employee to determine whether the receipt successfully matched to the wrong transaction. If it did not attach anywhere, return to the known expense and upload it there.

Brex documents separate API paths for creating a receipt match and creating a receipt upload for a specified card expense ID. Both use a pre-signed upload URL; neither is the same workflow as forwarding an email to receipts@brex.com.

That distinction matters for troubleshooting. If an internal tool, travel system, or integration uploaded the receipt through the API, an employee re-forwarding the email may not explain the original failure. Ask which path sent the receipt: manual email, Gmail or Outlook rule, Google Workspace add-on, mobile app, Slack, SMS, bulk upload, direct dashboard upload, Lyft, Uber, or API.

For email, collect the sender, destination, timestamp, and receipt evidence. For an API integration, ask the owner which endpoint was used, whether an expense ID was supplied, and whether the upload completed before the pre-signed URL expired.

Brex can process receipts after they arrive. Expensent helps make sure the right receipt emails get reviewed and routed before they become missing-document work. The product fit is strongest when receipts live in email, vendors change templates, employees forget to forward, or teams need historical catch-up.

In Expensent, likely invoice and receipt emails enter the Action Center for review. From a reviewed email, teams can forward the document or create an email-pattern and subject-pattern rule for recurring messages instead of relying on a broad mailbox keyword filter.

For Brex, the honest workflow is simple: use Expensent to find and route the source document, then use Brex for receipt matching, validation, policy, approvals, accounting export, and admin controls. That boundary keeps automation useful without pretending the upstream inbox layer can decide Brex compliance.