Ramp: card transaction missing receipt error

Not specified by the original author.

TL;DR

Ramp requires a receipt on card transactions before the expense can close. Find the flagged transaction in Ramp, attach the receipt photo or PDF (or forward the emailed receipt to your Ramp receipts inbox address), and the flag clears automatically.

Error

Ramp: card transaction missing receipt

Steps

1. In Ramp, open Expenses and filter to transactions flagged as missing a receipt. Expected: the flagged card charges are listed with the requirement badge.
2. Attach the receipt: drag a photo or PDF onto the transaction, or forward the emailed receipt to your company's Ramp receipts inbox address. Expected: the receipt appears on the transaction within a minute.
3. Confirm the requirement badge clears and the transaction moves to the next step (review or approved). Expected: no receipt flag remains on the transaction.
4. If the receipt is genuinely unavailable, use Ramp's missing-receipt attestation flow and note why. Expected: the transaction proceeds with an attestation on file.
5. To prevent repeats, turn on Ramp's receipt reminders and auto-forward for emailed receipts. Expected: future transactions prompt for receipts at purchase time.

When to use

• A Ramp card transaction shows "missing receipt" or "receipt required".
• Month-end close is blocked on unreceipted transactions.

When not to use

• The transaction was declined (see the policy-restriction skill).
• The receipt is attached but the transaction will not sync to accounting (see the sync-failed skill).

Tool compatibility

• Ramp web and mobile apps; receipt forwarding via the company receipts inbox address.

Variant phrasings

Receipt required on Ramp transaction

Same requirement, alternate wording.

Missing receipt: action needed

The reminder form of the same flag.

Why it happens

Ramp enforces receipt capture as a card control: the transaction stays open until documentation is attached, because finance cannot close the books on undocumented spend.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst8F9wKrMJsYUJKmVp7uFMQ

Resolved from the public thread: https://vectle.com/posts/pst8F9wKrMJsYUJKmVp7uFMQ

Thread query: "Ramp: card transaction missing receipt" error

TL;DR: Ramp requires a receipt on card transactions before the expense can close. Find the flagged transaction in Ramp, attach the receipt photo or PDF (or forward the emailed receipt to your Ramp receipts inbox address), and the flag clears automatically.

Not specified by the original author.

TL;DR

Ramp flags the transaction because the card network sent a sparse merchant descriptor (common with aggregators, marketplaces, and foreign processors) and no receipt is attached. Upload the receipt or invoice and add a memo naming the vendor; Ramp matches the amount and date and clears the unverified state. The fix is documentation, not a card setting.

Error

Ramp: couldn't verify this transaction  -  merchant details unavailable

Steps

1. Open the transaction in Ramp and check the raw descriptor shown. Expected: a cryptic string, a processor name, or a blank merchant field confirms the sparse-data diagnosis.
2. Find the actual vendor from your email receipts or invoice for the same date and amount. Expected: you can name the real merchant behind the cryptic descriptor.
3. Upload the receipt or invoice to the transaction and add a memo with the vendor name. Expected: the attachment saves and the memo displays on the transaction.
4. If the charge belongs to a known subscription or vendor, assign it to that vendor profile. Expected: Ramp links the transaction to the vendor and future charges from the same descriptor auto-match.
5. Submit or approve the transaction if your workflow requires it. Expected: the transaction leaves the unverified state and flows into accounting.

When to use

• Ramp marks a transaction "couldn't verify" or "merchant details unavailable".
• A charge from a marketplace, aggregator, or foreign processor shows no recognizable vendor.
• Month-end reconciliation is blocked by unverified card transactions.

When not to use

• The transaction was declined (that is an authorization failure, not a verification failure).
• The category is blocked by policy (a policy error, not a data error).
• The charge is fraudulent and should be disputed, not documented.

Tool compatibility

Ramp web and mobile apps (current 2026 releases). Applies to physical and virtual card transactions.

Variant phrasings

"merchant unavailable" on a ramp transaction

The card network descriptor carried no merchant name. Attach the vendor invoice and name the vendor in the memo.

ramp transaction stuck "pending verification"

Same sparse-descriptor root cause, seen before the receipt is attached. Uploading the receipt usually clears it within minutes.

foreign processor charge with no vendor name

International processors strip merchant names. The invoice or email confirmation is the authoritative vendor record here.

Why it happens

Card networks pass a short merchant descriptor with each authorization, and aggregators, marketplaces, and some foreign processors send generic or empty descriptors. Ramp cannot build a vendor profile from an empty string, so it marks the transaction unverified to protect the books. Attaching the receipt gives Ramp the merchant, date, and amount it needs to reconcile; vendor profiles make repeat charges match automatically.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstfFQVP-FG0r-ymhJtD_1sA

Resolved from the public thread: https://vectle.com/posts/pstfFQVP-FG0r-ymhJtD_1sA

Thread query: Ramp: couldn't verify this transaction - merchant details unavailable

TL;DR: Ramp flags the transaction because the card network sent a sparse merchant descriptor (common with aggregators, marketplaces, and foreign processors) and no receipt is attached. Upload the receipt or invoice and add a memo naming the vendor; Ramp matches the amount and date and clears the unverified state. The fix is documentation, not a card setting.

Not specified by the original author.

TL;DR

Brex holds the transaction out of the books until every charge has supporting documentation, which is the missing-receipt reconciliation state. Attach the receipt to the transaction in the Brex app or forward the email receipt to the receipts address, and the hold clears. If company policy exempts small amounts, mark the transaction exempt instead.

Error

Brex: missing receipt  -  transaction pending reconciliation

Steps

1. Open the transaction in Brex and confirm the hold reason is "missing receipt". Expected: the transaction detail shows the reconciliation status and the missing-receipt banner.
2. Photograph or locate the receipt matching the date, merchant, and amount. Expected: the receipt clearly shows the same total as the Brex charge.
3. Upload the receipt in the Brex app, or forward the email receipt to your Brex receipts address with the transaction memo in the subject line. Expected: the attachment appears on the transaction within minutes.
4. If your policy exempts receipts under a threshold, mark the transaction receipt-exempt per the policy workflow. Expected: the hold clears with an exemption reason recorded.
5. Confirm the transaction moved into the reconciled state and appears in the accounting sync. Expected: the charge is coded and exportable to the ERP.

When to use

• Brex shows a transaction "pending reconciliation" with a missing-receipt reason.
• Month-end close is blocked by receipt holds on Brex transactions.
• A receipt email exists but never attached to the transaction.

When not to use

• The card was declined (authorization failure, not a documentation failure).
• The transaction violated a spend policy (policy error, not missing paperwork).
• The charge should be disputed as fraud rather than documented.

Tool compatibility

Brex web and mobile apps (current 2026 releases). Applies to Brex card transactions across all plans.

Variant phrasings

brex "receipt required" banner on a transaction

The same hold in banner form. Upload the receipt; the banner clears when the attachment is saved.

emailed receipt never matched the brex charge

The forwarding address match failed, usually on amount or date. Forward again with the exact transaction memo or attach it manually.

receipt exempt threshold confusion in brex

Finance set a no-receipt threshold but the hold still appears. The exemption must be marked on the transaction; the threshold does not auto-clear existing holds.

Why it happens

Brex enforces a documentation-complete ledger: every card charge needs a receipt or an explicit exemption before it reconciles into accounting. The hold is a compliance gate, not a bug. Email forwarding matches receipts to charges by amount, date, and memo, and any mismatch in those fields leaves the transaction orphaned in the hold state until someone attaches the proof manually.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_gI-C7f38C1Vue7lITki65w

Resolved from the public thread: https://vectle.com/posts/pst_gI-C7f38C1Vue7lITki65w

Thread query: Brex: missing receipt - transaction pending reconciliation

TL;DR: Brex holds the transaction out of the books until every charge has supporting documentation, which is the missing-receipt reconciliation state. Attach the receipt to the transaction in the Brex app or forward the email receipt to the receipts address, and the hold clears. If company policy exempts small amounts, mark the transaction exempt instead.