Detect duplicate construction payments by comparing invoice identity, supplier, contract, amount, payment status and credit history. Then trace candidates across payment applications and disbursements. Similar documents are candidates for review; a confirmed duplicate requires evidence that the same obligation was settled twice.
What to take away
- Keep invoice duplicates distinct from duplicate cash settlement.
- Normalize invoice numbers while preserving the original.
- Review reversals, partial payments and cumulative billing before recovery.
Build two identities: the obligation and the settlement
Capture supplier legal entity, contract, original invoice number, invoice date, currency, gross amount, tax and revision. Preserve the source value before normalizing spaces, punctuation or case for matching. Keep any invoice image linked to its ledger entry. Two vendor accounts may represent the same supplier, so use an authorized vendor crosswalk where available.
Create a separate payment identity using disbursement reference, date, amount, bank reconciliation status and any reversal. The same invoice can appear on a proposal, a payment package and a ledger without being paid multiple times. Conversely, two differently numbered invoices can describe the same obligation. Review both document identity and settlement evidence.
Run exact and near-match tests with reasons
Start with exact supplier, currency, invoice and amount matches. Then examine near-matches such as punctuation changes, a trailing revision character, the same supporting invoice attached to different change requests, or a recurring charge that overlaps service periods. Keep the reason each rule selected the candidate.
Exclude neither repeated monthly values nor similar amounts automatically. They can be legitimate recurring services. Equally, do not treat a new reference number as proof of a new obligation. Ask whether the site, work period, delivery, quantity and supporting record are the same. A reviewer needs the competing records and their posting history together.
| Pattern | Why it matters | Common legitimate explanation |
|---|---|---|
| Same supplier / invoice / amount | Potential repeated entry | Reversal and repost |
| Same backup in two changes | Possible scope overlap | Explicit allocation |
| Same invoice, two payments | Potential duplicate settlement | Partial settlement |
| Same amount each month | Possible repeated charge | Recurring service |
| Near-identical number | Possible resubmission | Credit and corrected invoice |
Worked example: two payments are not always a duplicate
A fictional $24,000 invoice has two payments: $10,000 and $14,000. With no other adjustments, the combined $24,000 settles the obligation once. Flagging both entries because the invoice number repeats would create a false positive.
A different $24,000 invoice has two completed $24,000 settlements and no reversal, refund or separate obligation. The potential excess is $24,000, not $48,000. Before claiming recovery, obtain the supplier's response and the accounting owner's confirmation. If one payment was voided before clearing, the issue may be a control exception without a cash overpayment. Retain the original candidate and the evidence that cleared it.
Reconcile cumulative draws on their own basis
Payment applications often repeat cumulative values. The repeated total is not itself an additional request. Compare the current amount requested and the relevant prior deduction with the applicable form definitions. Check whether a supplier invoice was included under both a base-contract line and a change line.
Review credits and cancellations around the cutoff. A corrected invoice can coexist with the original while a credit is still waiting to post. Record the financial exposure and the pending remedy separately. Do not count a refund, credit memo and offset as three recoveries when they resolve the same duplicate.
Close candidates with settlement evidence
Assign a named decision owner and give the supplier a concise reconciliation of the obligation and payments. Request only the necessary evidence through approved channels. An owner should follow its actual contract and payment obligations when deciding any hold or offset; an analytical match does not by itself authorize either.
For a Buildalytic trial, scope collection and follow-up for a small set of redacted candidates. Require the final exception record to include a valid duplicate, a legitimate partial payment and a reversal case. Keep the ledger authoritative. Success means verified disposition and fewer hours reconstructing records, with any new detection or integration capability explicitly agreed in the scope.
Common questions
Can the invoice number alone prove duplication?
No. Check supplier identity, work period, revisions, credits and actual settled payments.
What amount should a duplicate report show?
Show the candidate exposure with its calculation. For two full settlements of one obligation, the potential excess is one settlement, subject to confirming reversals and entitlement.
Sources and editorial notes
Prepared with AI assistance. Reference date: 2026-11-05. Worked examples are illustrative and are not customer results. Product details can change; confirm the current scope and terms before rollout.
How we prepare and update field notesScope one evidence-backed review workflow.
Bring a redacted contract, payment packet and one unresolved question. Discuss the supported collection and follow-up steps, any additional scope and the human review needed to validate the result.
Start with the call, text or record your team already handles. Review the expected outcome and the human handoff before choosing a rollout.
Discuss your review workflow Explore the relevant capability
