Handle several receipts for one transaction

Check the full evidence set for one transaction

Keep the relationship visible so the reviewer can assess the complete purchase once.

If your evidence is a supplier invoice PDF, ParseMill can turn its invoice details and line items into a reviewable Excel workbook. Compare the source and correct the result before export. Receipt photos, missing-document requests and transaction matching belong in your existing receipt and accounting tools.

The relationship may arise from several purchases paid together or from a document set containing separate details. Do not assume the reason from the number of attachments. The authorized reviewer should confirm the relationship and decide whether the evidence is sufficient for the work.

Define what each document contributes

Create a transaction evidence set with a stable reference. For each artifact, record apparent merchant, date, amount, currency, purpose in the set and review state. Distinguish receipts from summaries, payment records and explanatory messages. Several files can describe the same purchase without adding new coverage.

Intuit: Receipt review describes review of uploaded receipts. Intuit: Transaction attachments describes files attached to supported transactions. The proposed evidence-set register adds a completeness check across the files. A visible attachment icon establishes that something is attached, not that every required component has been supplied and accepted.

Work through a partial set

This synthetic example compares one EUR 250.00 payment with three expected purchase records. The figures illustrate a check only; the reviewer must confirm the actual relationship.

The EUR 70.00 gap is an arithmetic observation, not a new receipt amount to invent. Ask the client to explain the remaining payment coverage and provide the relevant source. If the relationship is different from the initial hypothesis, update the map rather than pressuring the evidence to fit it.

Prevent double counting inside the set

Check whether two files are copies of the same receipt, a receipt and its payment confirmation, or distinct purchases. Preserve their roles. Adding every visible total together can double count a summary and its underlying records. Record excluded-from-total items with a reason so another reviewer understands the calculation.

• Assign each artifact a distinct source reference.
• State the contribution of each file to the evidence set.
• Keep duplicate copies out of arithmetic totals.
• Show any unexplained coverage separately.
• Record the reviewer's decision on the whole relationship.

If one file is unreadable, the set remains partly unreviewed even when the other amounts appear to balance. If currencies differ, compare them only through an authorized method with the relevant evidence. Intake staff should preserve the original values and escalate the difference rather than inventing a conversion.

Close the set only after review

The query can close when the authorized reviewer has accepted the evidence relationship or recorded an approved alternative outcome. Retain the set manifest so a future reviewer can identify which files support the transaction and which were reference material or rejected candidates.

Use the related workflow guide for the overall receipt workflow and the workflow audit checklist to examine whether partial submissions are creating false completion. A useful test case includes a duplicate file and a missing component, since a simple attachment count will fail both checks.