The Evidence Pack That Makes a Cross-Border Trade Dispute Reviewable

The phrase “send us the evidence” is dangerously vague.

A commercial team may respond with 4,000 files. Another team may send five screenshots and one spreadsheet. Both can be unusable.

A good first evidence pack has one purpose: allow an independent reviewer to understand the transaction, test the main allegations, identify missing proof, and decide what to do next without rebuilding the business history from scratch.

This guide focuses on the documents and records that usually create that reviewable structure.

Pack section 1: the one-page dispute map

Start with one page, not a folder.

Include:

• parties and legal entities;
• contract date;
• disputed transaction period;
• headline issue;
• amount or goods affected;
• current operational risk;
• governing-law clause;
• dispute clause;
• urgent deadline;
• one-sentence objective.

Example objective: “Recover the undisputed balance while preserving a defensible claim for defective goods and avoiding disruption to three open customer orders.”

That sentence is more useful than “win dispute.”

Pack section 2: executed agreement set

Do not send only the master agreement.

Include:

• signed agreement;
• schedules;
• amendments;
• side letters;
• guarantees;
• incorporated policies or price lists;
• relevant PO terms;
• later variation documents.

Then add an index:

A reviewer should not have to search 90 pages for every reference.

Pack section 3: transaction table

Build one row per order, shipment or invoice.

Recommended columns:

• transaction ID;
• PO date;
• quantity;
• confirmed quantity;
• unit price;
• currency;
• shipment date;
• delivery date;
• invoice;
• due date;
• payment;
• return;
• credit;
• complaint reference;
• status;
• source-link ID.

This table becomes the control panel for the dispute.

If the table says “paid,” the bank record should exist. If it says “defective,” the inspection evidence should exist.

Pack section 4: order and acceptance records

Include the records that show what the parties actually agreed for the disputed transaction:

• request for quotation;
• quotation;
• purchase order;
• order confirmation;
• amendment;
• cancellation;
• quantity change;
• delivery change;
• approval.

If terms were exchanged through automated systems, keep the relevant system messages and audit trail.

UNCITRAL’s 2024 Model Law on Automated Contracting is a modern reference showing how international trade law is addressing contracts formed or performed through automated systems. Whether it has been implemented or affects a specific transaction depends on local law.

Pack section 5: shipping and delivery chain

For goods disputes, link the physical movement:

• packing list;
• carrier booking;
• bill of lading/waybill;
• export declaration where relevant;
• customs release;
• warehouse departure;
• delivery receipt;
• receiving report;
• damage notation;
• photographs.

Where an electronic transferable record is used, preserve the record and the system information needed to establish control and integrity. UNCITRAL’s MLETR provides a framework for functional equivalence, but local adoption and implementation must be checked.

Pack section 6: quality evidence

A quality allegation without product identity and method is weak.

Include:

• SKU;
• lot/batch;
• serial number;
• sample size;
• test method;
• specification version;
• inspection date;
• inspector;
• photos;
• lab report;
• rejected quantity;
• disposition;
• replacement or repair.

Also include evidence that cuts against your position. If only part of the shipment failed, say so. If testing used a disputed method, flag it.

Reviewability is more valuable than advocacy inside the evidence pack.

Pack section 7: money evidence

For every claimed amount:

• invoice;
• due date;
• bank evidence;
• remittance;
• credit note;
• set-off;
• rebate;
• commission;
• tax adjustment where relevant;
• return/refund.

Build a bridge from gross claimed amount to net disputed amount.

A reviewer should be able to answer:

• what is undisputed;
• what is disputed;
• why;
• which source proves each adjustment.

Pack section 8: communications that changed the deal

Do not include every email first.

Prioritize messages that:

• change price;
• change quantity;
• change delivery;
• grant credit;
• approve exception;
• accept defect;
• reject defect;
• waive deadline;
• threaten termination;
• reserve rights;
• settle or attempt settlement.

Preserve the thread context.

The 2005 UN Electronic Communications Convention is an international instrument designed to facilitate the use of electronic communications in international contracts within its scope. It does not create a universal evidentiary rule, but it underscores why electronically made commercial communications cannot be treated as second-class records.

Pack section 9: authority records

If a dispute involves who could bind the company, include:

• role description;
• approval policy;
• delegation;
• signing authority;
• board or management approval if relevant;
• prior comparable approvals;
• system permission logs.

Authority disputes often become factual before they become legal.

Pack section 10: notice file

Create a separate notice file:

• notice;
• contract clause;
• sending method;
• address used;
• dispatch evidence;
• receipt evidence;
• cure deadline;
• response;
• next deadline.

Do not let formal notices disappear inside general email.

Pack section 11: evidence provenance sheet

For each high-value file, record:

• document ID;
• original file name;
• source system;
• custodian;
• collection date;
• collector;
• method;
• hash if used;
• language;
• translation status.

This is especially useful when files will move between countries, advisers and teams.

Pack section 12: missing-record log

A professional evidence pack says what is missing.

Examples:

• original signed amendment not located;
• former employee mailbox unavailable;
• damaged goods already disposed of;
• one shipping photo missing timestamp;
• chat export incomplete;
• customer confirmation requested but not received.

For each, state the recovery action.

A gap disclosed early can be managed. A gap discovered during a hearing is much more expensive.

Pack section 13: translation layer

For multilingual cases:

• keep originals;
• create working translation;
• identify translator/method;
• note ambiguous commercial terms;
• reserve certified translation for records that actually require it.

Do not translate 2,000 pages before deciding which 50 pages matter.

Pack section 14: preservation record

Keep a short note of:

• when the dispute became reasonably foreseeable;
• which systems were preserved;
• who was instructed;
• whether auto-delete was paused;
• what could not be preserved;
• when the decision was reviewed.

In England and Wales Business and Property Courts, PD57AD expressly addresses preservation and disclosure duties within its scope. Other jurisdictions may impose different obligations.

Pack section 15: a reviewer memo

End the pack with a short memo, not an argument.

Use headings:

• what is clear;
• what is disputed;
• what is missing;
• urgent deadlines;
• questions for local counsel;
• commercial decision needed.

For example: “Clear: 1,800 units delivered. Disputed: whether 220 units failed specification B. Missing: original lab calibration record. Decision: whether to pay undisputed 1,580 units now and reserve the remainder.”

That is immediately actionable.

A naming convention that prevents chaos

Use document IDs:

• AGR-001 agreement;
• AMD-001 amendment;
• PO-771 purchase order;
• INV-455 invoice;
• SHP-114 delivery;
• QLT-018 inspection;
• PAY-009 bank record;
• COM-233 email;
• NOT-004 formal notice.

Then cite these IDs in the chronology and transaction table.

A disciplined naming system saves review time and reduces broken links.

Do not over-collect too early

The first evidence pack should answer the first decision.

If management only needs to decide whether to pay, negotiate or issue notice, do not collect every historical customer file.

Expand the pack only when a defined issue requires it.

What can change the evidence pack

The pack may need additional controls when:

• authenticity is challenged;
• regulatory rules apply;
• personal data is involved;
• employees are custodians;
• litigation has started;
• electronic transferable records are central;
• third-party disclosure is needed;
• privileged legal communications exist.

Local advice should shape collection and handling.

Final test

A reviewable evidence pack should let a new adviser answer five questions in under an hour:

1. What happened?
2. Which contractual terms matter?
3. What amount or performance is disputed?
4. Which facts are proved, uncertain or missing?
5. What decision must be made next?

If the pack cannot do that, adding another 500 files will not fix it. Structure will.

Build the pack in review order, not storage order

A shared drive is normally organized around departments: sales, finance, logistics, quality. A dispute reviewer thinks differently. The reviewer needs to move from issue to proof.

For a payment-and-quality dispute, a useful review order might be:

1. one-page issue map;
2. contract and amendment controlling the order;
3. transaction row for the disputed shipment;
4. delivery evidence;
5. defect notice;
6. inspection record;
7. invoice and payment position;
8. communications changing the parties' position;
9. open evidence gaps;
10. decision required.

That order may duplicate links to files already stored elsewhere. That is fine. The evidence pack can be an index layer rather than a new uncontrolled copy of every document.

Distinguish “original,” “authoritative export,” and “working copy”

Teams often use the word original loosely.

An original may be the native record in the system that created or received it.
An authoritative export may be a controlled export from that source system, with enough context to explain provenance.
A working copy may be a redacted PDF, translated version, annotated spreadsheet or file prepared for review.

Label them differently.

For example:

• COM-044-native.eml
• COM-044-export.pdf
• COM-044-zh-working-translation.pdf

The labels do not decide legal admissibility. They stop the internal team from accidentally presenting a derivative file as the source record.

Make every calculated number traceable

Claims often fail review because the underlying arithmetic is invisible.

If the pack says “$312,450 outstanding,” include a reconciliation showing:

• invoice number;
• gross amount;
• currency;
• payment;
• credit;
• return;
• set-off claimed;
• disputed adjustment;
• net amount;
• source document.

Do the same for quantities, commissions, target shortfalls and defect rates.

A calculated number should be reproducible from the records without asking the employee who built the spreadsheet.

Add a rights-and-deadlines sheet only after facts are stable

The evidence pack is primarily factual, but once core facts are stable it can include one controlled sheet for:

• contractual notice deadline;
• cure period;
• renewal/non-renewal date;
• arbitration or court clause;
• known statutory or procedural deadline requiring local confirmation;
• preservation action already taken;
• person responsible for confirmation.

Mark uncertain legal deadlines as to be confirmed locally rather than converting a preliminary assumption into a false fact.

The evidence pack should become smaller as the decision becomes clearer

Early collection can be broad. The executive review pack should be narrow.

Keep the preservation archive intact, but give decision-makers:

• the decisive records;
• the short chronology;
• the reconciliation;
• the unresolved gaps;
• the decision options.

A 40-page review pack backed by a controlled archive is usually more useful than a 4,000-file folder with no map.

Sources

• UNCITRAL — Model Law on Electronic Commerce (1996), with additional article 5 bis adopted in 1998. accessed 2026-10-03. https://uncitral.un.org/en/texts/ecommerce/modellaw/electronic_commerce
• UNCITRAL — United Nations Convention on the Use of Electronic Communications in International Contracts (New York, 2005). accessed 2026-10-03. https://uncitral.un.org/en/texts/ecommerce/conventions/electronic_communications
• UNCITRAL — Model Law on Electronic Transferable Records (2017). accessed 2026-10-03. https://uncitral.un.org/en/texts/ecommerce/modellaw/electronic_transferable_records
• Courts and Tribunals Judiciary / Justice UK — Practice Direction 57AD, Disclosure in the Business and Property Courts. accessed 2026-10-03. https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part-57a-business-and-property-courts/practice-direction-57ad-disclosure-in-the-business-and-property-courts
• UNCITRAL — Model Law on Automated Contracting (2024). accessed 2026-10-03. https://uncitral.un.org/en/mlac

Related Reading

• Evidence & Transaction Records: Build a File That Survives a Cross-Border Trade Dispute
• Before You Act on Trade Evidence: A 14-Step Decision Checklist
• Trade Evidence Mistakes: How Good Claims Become Hard to Prove