A mismatch between payment records and product records creates two connected problems: unclear financial trail and uncertainty about what was ordered versus what was delivered. Your job is to make the discrepancy visible, preserve evidence so others can review it, and stop additional actions until you have a documented explanation. The following method turns ad hoc emails and screenshots into a usable record that supports the next sourcing decision.

Immediate containment: capture, label, and pause

Start by capturing every item tied to the transaction. Save the payment confirmation, bank remittance advice, SWIFT or payment receipt, the supplier invoice, purchase order, order confirmation, packing list, and any shipment photos or tracking details. Use time-stamped screenshots or PDF exports so the original messages and timestamps remain visible.

Next, label and store these files in a central folder for the incident. Mark each file with the date, who provided it, and where it came from. Pause any related follow-on payments or release of goods only if your internal payment policy allows a hold pending clarification. The goal is to prevent further divergence while keeping a clean record of the state at discovery.

• Save bank payment receipt and remittance information
• Export invoice, PO, order confirmation, and packing list
• Capture supplier emails, chat logs, and shipment photos with timestamps
• Move items into a named incident folder and avoid editing originals

Compare records line by line to isolate the mismatch

With the documents gathered, compare matching fields across records to locate precisely what differs. Check beneficiary name, account number, bank name, and branch code on the payment receipt against the payee details on the invoice and your purchase order. For amounts, confirm unit price, quantity, currency, fees, and total so you can see whether the payment amount matches the billed amount or a variation.

Do the same for product information. Match SKU or part number, product description, color, material, unit weight, and ordered quantity to the packing list and any shipment photos. Note any product changes that could explain a price or beneficiary change, such as a subcontracted supplier or a third-party fulfillment partner receiving funds.

• Financial fields to match: invoice number, currency, gross amount, fees, beneficiary name, account number, and bank identifiers
• Product fields to match: PO number, SKU, description, quantity, unit price, packing list, and shipment photos

Build a Supplier Escalation Record and Product Change Log

Translate your findings into a single, dated Supplier Escalation Record. Include incident ID, discovery date, parties involved, a concise summary of the mismatch, a chronological list of actions taken, and links to the captured evidence. Add a clear status field such as Open, Clarification Requested, Supplier Response Received, or Resolved so reviewers know where the issue stands.

Create a parallel Product Change Log if the discrepancy involves product differences. Record the original specification, the received or billed specification, who authorized any change, dates, sample approvals, and supporting photos. These two linked logs create a visible trail for procurement, finance, and operations to review and reduce the chance that the same mismatch recurs.

• Supplier Escalation Record fields: incident ID, discovery time, documents attached, statement of mismatch, actions, and status
• Product Change Log fields: original spec, changed spec, authorization source, dates, and photographic evidence

Ask focused questions and request specific documents

Send one concise written request to the supplier that references your Escalation Record. Ask them to confirm whether the beneficiary change or product variation was intentional, who authorized it, and on what date. Request supporting documents: corrected invoice, bank payment confirmation from their bank, written authorization for beneficiary changes, and the export or shipping documents that match the goods

Phrase questions so answers will be documentary rather than conversational. Examples include: Which invoice number corresponds to the payment received? Who approved payment to the current beneficiary and can they provide a signed authorization? Can you provide a bank acknowledgement or remittance confirmation showing receipt? Ask for email replies only and include a deadline for response so the record shows elapsed time.

• Documents to request: corrected invoice, beneficiary authorization, supplier bank receipt, packing list, and delivery photos
• Questions to ask: Who authorized the change? Which invoice matches this payment? Can you supply proof of receipt and authority in writing?

Decide next steps and when to involve specialists

Use the collected evidence and supplier response to choose a practical next step. If the supplier supplies corrected documents that reconcile payment and product records, update your logs and proceed according to internal approvals. If the supplier cannot provide documentary proof or disputes your view, escalate internally for a payment review and consider instructing your bank to trace the payment or requesting a recall, subject to your bank's policies.

Engage qualified specialists when the documents you need are outside normal sourcing records. Ask your bank to trace or advise on reversals when funds went to an unexpected beneficiary. Contact legal counsel if contract terms are disputed or if you receive threats or demands. Include your customs broker or insurer when shipment status, import duty, or insurance claims may be affected. Each specialist should receive the Supplier Escalation Record and Product Change Log so their input is efficient and evidence-driven.

• Accept corrected documents and update logs
• Request payment trace or recall from your bank if documentary reconciliation fails
• Involve counsel, bank, customs broker, or insurer when specialized action is required

Open a dated Supplier Escalation Record now and attach the payment receipt, invoice, PO, and shipment files.