A useful evidence packet explains the deduction, connects each supporting record to the transaction and states the correction requested. Its purpose is to make the decision reviewable. A folder containing many files is not a substitute for a clear case summary.
Write a concise case summary.
Start with the customer, account, invoice, deduction reference and amount. State the customer’s reason and your specific disagreement. Explain what you are asking the reviewer to confirm. For example, identify a quantity mismatch rather than saying only that the shipment was complete. Keep the summary factual and avoid unsupported language about intent.
Create a record index.
List the invoice, remittance, purchase order, applicable agreement and shipment or receiving records. For each item, include its reference, date and relationship to the deduction. Mark missing records explicitly. A record index helps reviewers see whether the materials address the actual transaction rather than a similar delivery or another customer account.
Check the contents, not just the filename.
A proof-of-delivery file needs to relate to the correct shipment and receiving location. Check quantities, units, dates, signatures and exceptions where applicable. Shipping arrangements can affect the relevant documentation. SPS Commerce’s Lowe’s shortage guidance, for example, distinguishes collect and prepaid shipments; that example should not be generalized into a rule for every retailer.
Separate evidence from interpretation.
Keep source documents unchanged and place your reasoning in the case summary. Identify a conflict directly: an invoice says one quantity while receiving evidence says another. Do not silently correct the source to make the figures agree. If a record is unclear, assign the clarification to its owner and record the answer separately.
Preserve the version that was approved.
Record which packet the reviewer approved, what amount was authorized and when submission was confirmed. Keep later requests for information and revised files in the history. A changed packet should have a clear version and reason for the change. This makes a subsequent appeal, partial approval or accounting review easier to explain.
Sources and scope
Safa editorial framework. Reviewed October 23, 2026. Examples are illustrative; confirm account-specific requirements with the trading partner.