Research · Published:
Corporate-card and employee-reimbursement overlap research
A transaction-level method for identifying when the same business expense may appear in a card feed and an employee reimbursement request.
Methodology
The same restaurant, hotel, subscription, or transport expense can appear once in a corporate-card feed and again in an employee reimbursement claim. Similarity is not proof of duplicate payment: one record may be a temporary authorization, a reversed charge, a deposit, a split bill, a personal card used after the corporate card failed, or a reimbursement claim that discloses a company-paid portion. This study develops a neutral evidence method for identifying overlap candidates without accusing an employee or deciding recovery, tax, payroll, disciplinary, or accounting treatment. The output is a transaction packet that shows both payment channels, documentary support, employee explanation, system history, and approving owner. Outsourced AP support can prepare that packet and monitor the exception. It must not label conduct as fraud, reject a claim based on resemblance alone, change a card record, deduct pay, net a future reimbursement, or decide whether an expense has an adequate business purpose.
Evidence and scope
The population combines a frozen corporate-card extract and reimbursement submissions for the same declared entities and date window. Each source retains its stable transaction or report identifier, employee and cardholder identifiers, merchant name and location, authorization date, posted date, transaction and billing currencies, original and converted amounts, card status, expense-report line, receipt reference, business-purpose field, attendee or trip reference where policy permits, reimbursement status, approver, and source timestamps. Pending authorizations are separated from posted transactions. Credits and reversals remain linked to their original charge. Cash advances, per diem, mileage, and centrally billed travel are classified before comparison because they do not behave like ordinary receipt-backed charges. The study reconciles every included and excluded record to its source totals and keeps personal data in approved systems, exposing only the minimum identifiers required for the assigned review.
Key Stats
Candidate generation uses layered tests. Exact references, receipt-image hashes, merchant transaction identifiers, booking numbers, dates, currencies, and amounts can provide strong signals. Normalized merchant text, nearby dates, converted values, and similar descriptions provide weaker signals and must not be called matches. A hotel may split room, tax, and incidentals; a restaurant may post a tip adjustment; a ride service may issue several same-day charges; and an employee can legitimately share an expense with colleagues. The register records why each pair was surfaced, which fields agree, which conflict, and whether one record has already been reversed or disclosed. It preserves separate source amounts rather than converting them solely to make a pair appear equal. A company-approved exchange-rate comparison can support analysis, but only the original currencies show whether the sources actually describe the same charge.
Research-to-practice
Documentary review follows the money path. A receipt may show the purchase but not the funding source. A card statement may show funding but not the business purpose. An expense report may contain an employee certification, while a travel platform may show that the company paid centrally. The packet links each assertion to its source. If an employee notes that the corporate card failed, the preparer checks for a later captured card transaction and retains both authorization and posting history. If a merchant refunded one channel and charged another, the full chain stays visible. The IRS's 2025 Publication 463 explains accountable-plan concepts such as business connection, adequate accounting, and return of excess reimbursement for U.S. tax contexts. It does not decide a particular claim, apply globally, or authorize AP to interpret payroll and tax consequences.
Implementation
The chronology begins with purchase or booking and ends only after card settlement, reimbursement payment, credit, repayment, or owner disposition. It includes submission, approval, edits, rejected attempts, feed refresh, and employee responses. Event time is not silently replaced by entry time. A card charge posted after reimbursement approval is a later fact, not proof that the reviewer ignored visible evidence. Conversely, a pending authorization known during review should remain in the packet even if it later disappears. This time-aware method supports fair review because it shows what each participant could see. It also prevents a later credit from erasing the fact that two outflows may have occurred temporarily. Status labels such as candidate, employee explanation pending, source conflict, credit pending, owner decision pending, and resolved with evidence are preferable to “duplicate” until the relationship is established.
Key Takeaways
Challenge cases include a hotel deposit on the company card and balance on a personal card; a restaurant tip posted separately; the same receipt attached to two reports; a card charge reversed after reimbursement; foreign-currency travel with different conversion dates; a centrally billed airfare plus employee-paid seat fee; a shared meal divided between employees; and a subscription accidentally charged to both cards. Two reviewers independently classify the relationship and identify the next evidence needed. Reproducibility does not require them to infer intent. It requires the same source facts, signal strength, cash-flow possibilities, and unresolved owner question. The method fails if a normalized merchant name is treated as identity, if credits vanish from the population, if an employee response is summarized without the original record, or if a support analyst clears the case by editing one system to agree with another.
Findings
Roles remain explicit. Support may collect approved sources, run documented comparisons, preserve transaction histories, request a missing receipt or explanation through approved channels, and assemble an exception packet. The employee supplies required evidence. A manager determines business purpose and approval under policy. Finance, payroll, tax, card administration, human resources, or legal owners decide recovery, wage treatment, discipline, accounting, and card actions as applicable. NIST least privilege supports restricting the support role from card administration and payroll actions, while audit-record concepts support attributable changes. GAO principles support reliable information, clear responsibility, and monitoring. Neither framework establishes employee misconduct. Access design should prevent the convenience of overlap review from becoming broad visibility into unrelated travel, personal information, or complete card accounts.
Findings
Metrics report candidates and evidence states, not allegations or “fraud caught.” They can include records compared, exact-reference pairs, receipt-hash pairs, weak similarity candidates, later reversals, employee explanations, confirmed dual outflows, credits or repayments evidenced, unresolved owner decisions, false positives by signal, and second-review agreement. Denominators, date windows, currency treatment, and feed timing are disclosed. A rising candidate count may reflect better coverage or a changed travel pattern rather than worse behavior. Limitations include delayed card feeds, truncated merchant data, missing receipts, shared purchases, privacy constraints, and policy differences across jurisdictions. The method cannot establish intent, taxability, deductibility, employment consequences, or final accounting treatment. Its supported conclusion is that a suspected overlap becomes reviewable when both channels, their timing, funding evidence, documents, explanations, and authorized disposition remain linked without premature accusation.
Findings
A fair employee-facing handoff avoids loaded language. It states that two records may refer to the same expense, lists the fields that prompted review, identifies the missing fact, and gives an approved response channel. It does not demand sensitive personal account data when a receipt, card record, or merchant credit can answer the question. The final disposition records whether the sources described different expenses, one charge was reversed, an amount was disclosed and netted under policy, a dual outflow occurred, or evidence remained insufficient. Any recovery or payroll event receives its own authorized record. Keeping false positives and their causes improves the comparison rules and reduces repeated inconvenience without hiding real exceptions. The operational reader outcome is a respectful, reproducible review process, not a surveillance score.
Surface overlap without accusing or adjudicating
Support can compare controlled card and reimbursement records and prepare a neutral exception. Authorized company owners decide business purpose, repayment, payroll, discipline, accounting, and approval.
Review expense report supportSources
These primary sources support the control principles and evidence boundaries in this report.
FAQs
Are the planning numbers benchmarks?
No. They describe a testable workflow shape and are not promises, market averages, or production targets.
What should an outsourced AP assistant own?
Repeatable preparation, documentation, status tracking, and follow-up within least-privilege access. Named finance owners retain approval and payment decisions.
When should an item be escalated?
When evidence is missing, a request changes payment details, a duplicate or fraud signal appears, or the item falls outside the written rule.