Duplicate reimbursement is usually a workflow failure
A company can pay the same business cost twice without anyone intending to overcharge it. The owner submits a receipt, the bookkeeper records a company-card feed, and an assistant approves a separate reimbursement from an emailed summary. Each step looks reasonable in isolation. The control should connect those steps to the original transaction. An accountable reimbursement process needs substantiated expenses, and duplicate payments should be identified rather than left inside an expense total.
Give each expense report a unique identifier and preserve the vendor invoice number, transaction date, amount, currency, and payment source. Do not use only the receipt image filename as the identifier; the same receipt can be photographed or downloaded several times. The review should compare economic transactions, including credits and refunds, rather than merely search for identical documents.
A hypothetical duplicate hotel charge
Assume a hotel charges $1,480 to a company card for an owner’s business trip. The owner forwards the receipt to the bookkeeper for documentation, then includes it in a personal reimbursement report by mistake. The company sends the owner another $1,480. The books now show $2,960 of hotel expense even though there was one stay. The presence of two payments does not create two underlying business expenses.
First verify that both payments occurred and identify whether the company-card charge was later reversed. If there was no reversal, record the duplicate and obtain advice on its correction. The owner may return the excess, but the team should document the repayment and any reporting implications based on the facts and timing. Simply deleting the expense report leaves no explanation for the extra cash that reached the owner.
Suppose the hotel later refunds $200 for an overcharge. That refund is a third transaction tied to the original stay, not a reason to create another reimbursement. The ledger should show the original cost, duplicate owner payment, correction, and vendor credit separately. This lets the preparer identify the final business cost and any unresolved balance without guessing from a net general-ledger number.
Place the check before payment
Have the expense reviewer inspect the payment-source field and compare it with company-card records. If the company already paid, mark the item documentation only and exclude it from the reimbursement total. For owner-paid costs, match the payment evidence to the report. If the card feed is incomplete, hold the uncertain item for review rather than automatically pay it because the owner supplied a receipt.
Automated duplicate flags can help, but matching only vendor and amount will miss some duplicates and flag legitimate recurring expenses. A hotel invoice can be split into room and meals; a monthly software charge can legitimately repeat. The reviewer needs context and should record why a flagged item was approved or rejected. Preserve the original amounts and decisions rather than silently changing data to make the software stop flagging it.
Correct the records across systems
When a duplicate is found, update the expense platform, bookkeeping ledger, reimbursement register, and any relevant payroll instructions. Identify the person responsible for each step and verify that the final bank activity agrees. A corrected expense platform does not automatically undo a bank transfer or an accounting entry already imported elsewhere.
Include open duplicates and unresolved advances in the monthly owner statement. Reconcile returned amounts to the specific original report. If repeated errors involve the same payment channel, redesign that workflow: one submission route, one approval owner, and one settlement record. Tax treatment of an unreturned amount requires professional review. The operational goal is to prevent the same invoice from becoming both a company-card expense and a second owner payment, while preserving a clear history whenever a mistake occurs.
Add a second review for large owner reimbursement batches, especially when someone other than the bookkeeper initiates the bank transfer. The reviewer should compare the approved reimbursement total with the exact transfer instruction and note the payment reference. If the batch is resubmitted after a failed payment, verify the first attempt truly failed before sending another. Bank status, expense-platform status, and an owner email can disagree, so close the loop with the actual settlement evidence.
Sources & further reading
Consult the original guidance and its effective dates. These references support the educational discussion; their application depends on the specific facts.