Separate purchase evidence from payment evidence

Ask what each source actually establishes

Keep payment evidence and purchase evidence distinct so the reviewer can identify the actual gap instead of accepting a convincing-looking attachment.

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.

This distinction is an operational review aid. It does not establish a universal rule about acceptable tax evidence or decide the accounting treatment. The authorized reviewer should determine what is sufficient for the engagement and applicable requirements, using the actual facts rather than the document's filename alone.

Define the unresolved question first

Ask whether the team needs to establish payment, purchase details, recipient, period or business context. More than one question may remain. Record source type, observed facts and limitations separately. A receipt, invoice, bank line and client explanation can contribute different information without any one item proving the entire relationship.

Intuit: Transaction attachments describes storing files with supported transactions. Intuit: Matching bank transactions describes linking bank transactions with existing records. These software relationships help organize evidence, but an attachment or match does not itself establish every detail the reviewer needs. The proposed comparison focuses on what the underlying sources actually contain.

Compare a fictional evidence set

A bank line and a supplier document appear to concern the same purchase. The table separates observations from conclusions so the reviewer can see the remaining questions.

The matching amounts support a comparison but do not prove identity. Check merchant context, dates, references and any contradictory information. If the supplier document is an unpaid invoice or an order confirmation, preserve that stage rather than relabeling it paid simply because a similar bank line exists.

Request the missing evidence purpose

A focused follow-up should say what remains unknown. For example, the payment is visible, but please provide the supplier record showing what was purchased. If the client cannot obtain it, record that obstacle and route it to the reviewer instead of implying a bank screenshot automatically satisfies the requirement.

• State the evidence question before selecting a document.
• Record only facts visible in each source.
• Preserve document stage and payment status separately.
• Check the relationship between sources.
• Let the reviewer decide sufficiency and treatment.

Avoid renaming a payment confirmation as receipt in the register if that hides its limited content. Likewise, do not reject useful purchase evidence merely because it does not show settlement; the payment question can be answered by a separate linked source when the reviewer accepts the relationship.

Verify the handoff tells the whole story

Ask a colleague to identify what is known about payment, purchase details and context from the evidence map. They should also identify what remains unresolved. If the record says evidence complete without those distinctions, add the missing purpose and limitation fields.

Use the related workflow guide for the overall missing-receipt process and the workflow audit checklist to examine repeated requests for the wrong source. A useful workflow asks for information that resolves a specific gap, while preserving the reviewer's decision about whether the combined evidence is sufficient.