How to Detect Duplicate Expense Postings

A duplicate expense posting occurs when the same economic purchase is recognized more than once in the ledger. Similar-looking records are only candidates: two meals may share a total, a recurring service may legitimately bill monthly, and a receipt plus a card-feed line can be two views of one purchase rather than two ledger postings. Detection therefore requires tracing records to their source and payment path before correcting anything.

Build useful candidate matches

Compare transaction identifiers, receipt references, card account, employee, merchant, transaction and posting dates, currency, gross amount, and account coding. Search across manual journals, imported card activity, expense reports, reimbursement entries, and later corrections where relevant. Exact reference matches are strong clues; matching merchant and rounded amount alone is weak evidence. Use sensible date windows for posting delays, and flag split transactions, foreign currency, refunds, tips, and recurring charges for manual review.

Verify the record relationship before action

• Two ledger entries tied to one receipt and one purchase may indicate a duplicate; confirm that neither is a split allocation or legitimate correction.
• A card transaction and an employee expense report may describe the same purchase; determine whether the workflow records both as ledger entries or links one as evidence.
• An expense and its reimbursement or card-issuer payment are different accounting events; a settlement entry should not be mistaken for a second purchase.
• A credit and original charge may both be valid records; compare signs, references, and settlement status before netting them.
• Repeated identical subscriptions can be separate monthly services; inspect service periods and invoice or transaction references.

Worked example: card feed and manual upload

The ledger shows two $84.60 office-supply expenses dated April 12, one from a card import and one entered from a receipt. Both name the same employee and merchant. Before labeling one a duplicate, the accountant compares the card reference with the receipt, checks the receipt’s item list and date, and confirms that both entries relate to one basket of supplies. The manual entry has no distinct purchase reference, and the import already includes the transaction. The reviewer documents the evidence, follows the organization’s correction process to reverse or otherwise remove the duplicate recognition, and links the correction to both original records. If the receipt instead described a separate order with its own receipt number, both expenses would remain.

Do not delete history to make totals agree

Preserve the original posting and its approval trail according to the organization’s recordkeeping process. Corrections should identify the affected entries, reason, reviewer, and period treatment. If a duplicate was already paid to an employee, a card charge is still pending, or a prior period is closed, route the issue to the responsible accountant for appropriate handling; do not assume a simple deletion or current-period offset is acceptable.

Turn findings into a targeted review

Maintain a queue of candidates with source references and a disposition: confirmed duplicate, valid separate transaction, linked supporting record, or unresolved. Review clusters by cause, such as duplicate imports or repeated manual entry, and improve the relevant handoff. Similarity rules can surface leads, but they cannot establish authorization, period, or proper correction without review. Treatment depends on company policy, evidence, and accountant judgment.