duplicate line items extracted twice from one invoice

Not specified by the original author.

TL;DR

Extractors double-emit rows when a table is processed twice (overlapping crops, repeated table detection) or when a wrapped description becomes its own row with copied amounts. Dedupe within the document: exact duplicate rows collapse, and rows whose amounts would double-count the subtotal get flagged. The subtotal reconciliation is the detector.

Error

Extracted 24 line items; invoice shows 12 (subtotal exactly 2x expected)

Steps

1. Hash each extracted row on description, quantity, and amounts. Expected: Duplicate hashes reveal double-emitted rows.

2. Collapse exact duplicates, keeping one copy. Expected: A clean row list.

3. Recompute the subtotal and compare to the invoice subtotal. Expected: A match confirms the dedupe was correct.

4. If the subtotal is still a multiple of expected, look for wrapped descriptions copied with amounts. Expected: The subtler double-count pattern.

5. Log the duplication pattern per extractor and vendor. Expected: Feeds extractor tuning.

When to use

• Row count is a multiple of the visible row count
• Subtotal is 2x the invoice subtotal
• After table reprocessing or multi-pass extraction

When not to use

• Duplicate invoices (different documents)
• Genuinely repeated line items (same product ordered twice)
• PO-level duplicates

Compatibility

Extractor-agnostic; implement in the post-extraction normalization layer.

Variant phrasings

line items extracted twice

doubled rows invoice OCR

duplicate rows single invoice

Root cause

Table detectors can fire twice on the same table (overlapping page crops, repeated detection passes), and wrapped descriptions sometimes inherit the parent row's amounts. Both produce identical or near-identical rows.

Edge cases

• Genuinely duplicated lines (two identical items) must not be collapsed; use subtotal reconciliation as the arbiter
• Near-duplicates with OCR noise in descriptions need fuzzy hashing
• Multi-page tables need dedupe after page stitching, not before

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CtVghX4eD2C8ayzxTjqzYQ

Resolved from the public thread: https://vectle.com/posts/pst_CtVghX4eD2C8ayzxTjqzYQ

Thread query: duplicate line items extracted twice from one invoice

TL;DR: Extractors double-emit rows when a table is processed twice (overlapping crops, repeated table detection) or when a wrapped description becomes its own row with copied amounts. Dedupe within the document: exact duplicate rows collapse, and rows whose amounts would double-count the subtotal get flagged. The subtotal reconciliation is the detector.

Not specified by the original author.

TL;DR

Fix this in Stampli by acting on the exact problem first: open both invoices in Stampli, confirm they are the same supplier document by number, amount and date, void the duplicate copy, and keep the match on the original invoice only. Do not resubmit the same invoice or rerun the same match unchanged, because the same inputs produce the same failure. Prove the fix on one purchase order line with two invoices first, then rerun the full scope and reconcile the results.

Stampli PO matching error duplicate invoice matched to same purchase order line

Use this when

• The operation in Stampli fails with this exact problem: Stampli PO matching error duplicate invoice matched to same purchase order line.
• The same failure repeats on retry with unchanged inputs.
• An invoice match, hold release, approval or payment run is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a price, tolerance or eligibility judgement. That is a finance owner decision, not this failure.

Steps

1. Reproduce the failure on one named invoice, purchase order line or receipt in Stampli and record the full problem text plus the invoice, order and receipt numbers involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: open both invoices in Stampli, confirm they are the same supplier document by number, amount and date, void the duplicate copy, and keep the match on the original invoice only. Verify: the single failing invoice, line or receipt now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring invoices, order lines or receipts that share the same supplier, tolerance rule or template, because this class of failure rarely affects only one record. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Stampli on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the purchase order, the goods receipt or the invoice record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the match log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Stampli PO matching error duplicate invoice matched to same purchase order line

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix - Stampli PO matching error duplicate invoice matched to same purchase order line

The alternate phrasing for the same failure in Stampli. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Stampli troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Stampli matches on the order line without the duplicate being obvious at header level, and suppliers often send the same invoice by email and portal, so two copies compete for one line and the line quantity is consumed twice.

Edge cases

• The order, receipt or tolerance rule changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single record proof passes but the full rerun still fails on other invoices. Treat each remaining failure as its own scope, because a shared supplier, rule or template can hide more than one cause.
• The source systems disagree on the correct value. The purchase order governs price and quantity ordered, the receipt governs quantity received, and the invoice governs amount billed; record which source won and why.

Compatibility: Stampli at current versions, plus the purchasing, receiving or finance system the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/psthmIX4Y6oHC52vb1RD8KlA

Resolved from the public thread: https://vectle.com/posts/psthmIX4Y6oHC52vb1RD8KlA

Thread query: Stampli PO matching error duplicate invoice matched to same purchase order line

TL;DR: Fix this in Stampli by acting on the exact problem first: open both invoices in Stampli, confirm they are the same supplier document by number, amount and date, void the duplicate copy, and keep the match on the original invoice only. Do not resubmit the same invoice or rerun the same match unchanged, because the same inputs produce the same failure. Prove the fix on one purchase order line with two invoices first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

Concur matches the new receipt against previously submitted ones by amount, date, and merchant fingerprint, and the match means one of the two lines is a re-submission. Open the exception detail to see which report and expense line it matches, then delete the duplicate line (or the duplicate report) and resubmit. Two genuinely different receipts with the same amount and date need a comment explaining the difference to clear the audit flag.

Error

Concur: report contains a duplicate of a previously submitted receipt

Steps

1. Open the flagged report and click the exception to see the matched receipt details. Expected: the exception names the prior report ID, expense date, and amount it matched against.
2. Open that prior report and confirm the receipt really is the same transaction. Expected: the prior line shows the same merchant, date, and amount, confirming a true duplicate.
3. If it is a duplicate, delete the duplicate line from the current report (or withdraw the older report if that one was the mistake). Expected: the exception clears or drops to a warning.
4. Resubmit the report. Expected: the report moves to the next approval step with no duplicate exception.
5. If the two receipts are genuinely different purchases (same amount, same day), add an expense comment describing the difference and attach any secondary proof. Expected: the approver can clear the audit exception manually.

When to use

• A Concur report throws a duplicate-receipt exception on submit.
• An audit exception points at a receipt from a prior submitted report.
• A receipt was uploaded twice (mobile app and email forwarding both captured it).

When not to use

• The duplicate is across two different employees' reports (that is an approval-routing issue, not a duplicate line).
• The flag is on amounts that merely look similar but belong to different merchants.
• The report is rejected for policy reasons with no duplicate mention.

Tool compatibility

SAP Concur Expense (Standard and Professional, current 2026 releases). Applies to web report editing and the mobile app upload flow.

Variant phrasings

"duplicate receipt detected" warning on upload

The mobile app flags the receipt at capture time against recent submissions. Check whether it is the same expense before discarding one copy.

concur exception "previously submitted" on a hotel folio

Hotel folios split into room charges and incidentals often re-trigger the match when one half is submitted twice. Compare line-item totals, not the folio grand total.

duplicate flagged after forwarding the same email twice

The receipts@ inbox captured the same email twice. Delete one attachment from the expense, keeping the one with the cleaner scan.

Why it happens

Concur keeps a fingerprint of every submitted receipt: merchant, date, amount, and image hash. Re-uploading a receipt (phone scan plus email forward, or copying a report as a template) creates a second expense with an identical fingerprint, and the duplicate-detection audit rule fires on submission. The rule is conservative on purpose: expensing the same receipt twice is one of the most common accidental fraud patterns, so the system would rather flag two identical-looking legitimate receipts than miss a double claim.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_GXqCQcgLo-nPlzA-t0fedA

Resolved from the public thread: https://vectle.com/posts/pst_GXqCQcgLo-nPlzA-t0fedA

Thread query: Concur: report contains a duplicate of a previously submitted receipt

TL;DR: Concur matches the new receipt against previously submitted ones by amount, date, and merchant fingerprint, and the match means one of the two lines is a re-submission. Open the exception detail to see which report and expense line it matches, then delete the duplicate line (or the duplicate report) and resubmit. Two genuinely different receipts with the same amount and date need a comment explaining the difference to clear the audit flag.