agent matched the receipt to the wrong cardholder - shared corporate card

TL;DR

Several cardholders share one card number, so the receipt alone cannot identify who spent: the agent guessed from the receipt content and guessed wrong. Match on the transaction metadata instead: card feed records often carry the individual cardholder or sub-account identifier, and the expense claim's submitter is the authoritative owner. Fall back to asking the claimants only when metadata is absent.

Error

agent matched the receipt to the wrong cardholder  -  shared corporate card

Steps

1. Confirm the misattribution: open the receipt, the matched cardholder, and the actual spender. Expected: the receipt sits under the wrong person's expenses.
2. Check the card feed data for a per-transaction cardholder or sub-account identifier. Expected: the feed exposes who made each transaction.
3. Change the agent's matching logic to key on the transaction's cardholder identifier first, using receipt content only as a secondary signal. Expected: matches follow the feed data.
4. Where the feed has no identifier, assign ownership from the expense claim submitter. Expected: the submitter is treated as the spender.
5. Re-run matching over the shared-card transactions and spot-check the results. Expected: receipts land under the correct cardholders.

When to use

• An agent misattributes receipts on a shared corporate card.
• Department cards are shared across a team.
• Audit shows expenses under the wrong employee.

When not to use

• Each cardholder has their own card number (match on the card number).
• The receipt is matched to the wrong transaction (a different bug).
• The cardholder dispute is about the purchase itself.

Tool compatibility

Applies to custom audit agents matching receipts to card feeds (Expensify, Concur, Ramp feeds; current 2026 releases).

Variant phrasings

department card receipts assigned to the wrong person

Shared cards break receipt-content matching. Use the feed's cardholder identifier.

agent guessed the spender from the receipt

Receipts rarely name the buyer. Metadata, not content, identifies the spender.

shared card reconciliation misattributed

Key the match on transaction metadata and claim submitter.

Why it happens

Shared corporate cards (department cards, team travel cards) put many spenders behind one PAN. Receipt images almost never identify the buyer, so content-based matching is guessing. The card feed and the expense claim both carry better signals: feeds often include sub-account or cardholder fields, and the person who submitted the claim is definitionally the one accounting for the spend. The fix is matching on the strongest available signal instead of the weakest.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ARg-xA1ygJpdmR0667rjkg