Handle a receipt that covers several transactions

Map the receipt to every transaction it may explain

Record the relationship carefully so each transaction has a traceable explanation without duplicating the purchase.

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.

Several payments may relate to one purchase, but that is a hypothesis to verify. Deposits, split payments or separate charges can produce superficially plausible patterns. The intake task is to assemble a transparent comparison, not to infer accounting treatment from arithmetic alone.

Preserve one evidence identity

Give the receipt a stable artifact reference and link candidate transactions to it. Record source date, apparent merchant, currency, total and any explicit payment details. If the system requires copies for different records, retain the common source reference so those copies are not mistaken for separate purchases.

Intuit: Transaction attachments describes attaching files to supported QuickBooks records. Intuit: Matching bank transactions describes connecting bank transactions with existing records. Those mechanics do not decide which relationship is valid. The proposed map helps the reviewer see the full set of candidate links before taking any posting or matching action.

Compare a combined purchase with split payments

In this fictional example, receipt E18 totals EUR 180.00. Two observed payments may relate to it, but the relationship remains a review question until the supporting context is confirmed.

The zero remainder is a useful check, not proof. Compare dates, merchant context and any payment references. If B47 instead concerns another purchase, the arithmetic coincidence should not drive the decision. Record the evidence that supports the relationship or the question that remains.

Keep unresolved portions visible

If only one payment can be explained, mark that relationship separately and leave the other candidate unresolved. Do not label the entire receipt handled while another transaction still needs evidence. Conversely, do not request a second copy of the same receipt when the issue is confirming how it relates to another payment.

• Retain the receipt's full total and currency.
• List every proposed transaction link.
• Show the arithmetic remainder explicitly.
• Check identity and context in addition to totals.
• Record the reviewer's accepted and rejected relationships.

Do not adjust amounts merely to make the map balance. Fees, refunds, exchange differences or unrelated payments require their own evidence and reviewer decisions. If currencies differ, preserve each original amount and avoid subtracting unlike currencies as though they were one unit.

Test the handoff as a relationship map

Ask another reviewer to identify which transactions are supported, which are only candidates and what remains unexplained. They should be able to reach that answer without opening several duplicate receipt copies and guessing how they fit together.

Use the related workflow guide for the wider missing-receipt process and the workflow audit checklist to examine repeated evidence requests. A useful workflow supports many-to-one and one-to-many relationships visibly, while keeping the actual accounting decision with the authorized person.