Track receipt requests across multiple cardholders

Map each transaction to a responsible cardholder

Assign each gap to the right cardholder so the next message reaches someone who can actually supply the evidence.

If your evidence is a supplier invoice PDF, ParseMill can turn its invoice details and line items into a reviewable Excel workbook. Compare the source and correct the result before export. Receipt photos, missing-document requests and transaction matching belong in your existing receipt and accounting tools.

The map should identify who can answer the query, not merely who administers the card program. A finance contact may coordinate responses without knowing every purchase. Keep coordinator and responder roles distinct so replies can be reconciled to the right person and transaction.

Record responsibility with effective dates

Use limited card references, internal employee identifiers, effective-from and effective-to dates, backup contact and approval source. Avoid storing unnecessary full card details in the tracker. A card reassignment or staff departure can make the current owner different from the person responsible for a historical purchase.

Intuit: Email receipt images describes permissioned receipt forwarding. Microsoft: Data validation describes restricting worksheet entries. Those controls can support collection and a consistent map, but the proposed responsibility record still needs review. A user's ability to upload a receipt does not prove they own every transaction on the account.

Apply the map to a mixed statement

In this fictional example, one company statement contains purchases for two cardholders and one unresolved item. The correct output is scoped requests plus an internal ownership task.

If card 1111 moved to another employee in October, that does not automatically transfer responsibility for September's receipt. Confirm the relevant history. If a shared card is used, record the approved method for identifying the purchaser rather than assigning every item to the nominal card owner.

Keep responses linked to the master queue

Give each request a stable transaction query reference. When a coordinator gathers several responses, preserve the actual responder and source for each item. Do not mark all of one cardholder's questions complete because they sent a single message; reconcile the supplied evidence item by item.

• Check the transaction period against assignment dates.
• Distinguish coordinator from knowledgeable responder.
• Use only the transaction subset needed by each recipient.
• Escalate unknown ownership internally.
• Update the map when an authorized change is confirmed.

If a recipient says the purchase is not theirs, retain that response as evidence of a routing problem and investigate. Do not keep resending the same request to them or immediately expose the query to every employee. The next action is to establish responsibility through the approved process.

Audit the routing map with real exceptions

Sample queries that bounced between people and compare them with the map. Look for missing effective dates, shared-card ambiguity or an outdated contact. Repair the specific cause and record who approved the change so the next cycle starts from a reliable assignment.

Use the related workflow guide for the wider receipt workflow and the workflow audit checklist to assess routing delays. Test the process with a cardholder change and an unknown item, since those cases reveal whether the map handles historical responsibility rather than only today's contact list.