Quick answer
Build a transaction record map, not a general document pile. For each disputed obligation, link the controlling contract term to the purchase order, performance or delivery record, acceptance or rejection evidence, invoice and payment entry, complaint, notice, and claimed loss.
How to use this guide
Keep the native email, message, accounting or logistics record where possible. A screenshot or exported PDF may be useful for reading, but it should not replace the source file and surrounding thread. The aim is to show who did what, under which version of the agreement, when it happened, how the other party responded, and what commercial consequence followed.
This page is about business-record provenance. The broader legal framework belongs in the breach of contract guide, while an immediate exposure review belongs in the supplier-dispute risk register.
Start with a contract hierarchy
Supplier relationships often use several documents at once. Put them in an order that shows which document may govern if terms conflict.
| Layer | Records to locate | Question the records must answer |
|---|---|---|
| Parties and authority | Signed agreement, company details, delegation, board or procurement authority | Which legal entities contracted, and who could approve the transaction or a change? |
| Master terms | Framework agreement, standard terms, schedules and service levels | Which obligations, exclusions, remedies and dispute clauses formed the baseline? |
| Transaction terms | Quote, tender response, purchase order, order confirmation and statement of work | What was ordered, for what price, by which date and to which specification? |
| Changes | Variation, change request, revised drawing, scope email and price approval | Was the original obligation changed, and by whom? |
| Priority rules | Entire-agreement, order-of-precedence and non-variation clauses | Which document prevails if two records say different things? |
Do not assume the latest attachment automatically replaced the signed agreement. Mark every version with its source, date, sender, recipient and approval trail. If a document is missing, write “missing” and identify the likely custodian instead of recreating it from memory.
Map each obligation to what happened
Create one row for each material promise in dispute. Avoid a chronology that says only “the supplier failed.”
| Field | Example of the record category |
|---|---|
| Obligation | Contract clause, specification, milestone, quantity, service level or delivery date |
| Supplier act | Dispatch note, service log, timesheet, test result, delivery record or system event |
| Business response | Goods-received note, inspection, acceptance, rejection, return or complaint |
| Money | Quote, purchase order, invoice, credit note, payment, retention or disputed set-off |
| Communication | Complete email or message thread, meeting minute and call note |
| Notice | Breach, cure, escalation, dispute or termination communication plus delivery proof |
| Consequence | Downtime, replacement purchase, wasted cost, customer impact or other recorded loss |
| Gap | Record not yet found, person who may hold it and preservation step taken |
This structure separates the legal question from the evidence question. A lawyer may still need to decide what the contract means, whether conduct amounts to acceptance, and which remedy is available. The map simply makes the underlying transaction traceable.
Preserve order, delivery and acceptance records
For goods, locate the original order, supplier confirmation, dispatch details, delivery note, receiving record, inspection result, batch or serial reference where relevant, return authorisation, defect report and credit note.
For services, collect the statement of work, project plan, dependency list, work logs, milestone submissions, testing evidence, sign-off request, rejection reasons, remediation plan and final status record.
Record who signed a delivery note and what that signature was intended to confirm. Receipt at a loading bay does not necessarily answer whether technical performance was accepted. Conversely, continued use, approval messages or payment conduct may become important facts. Do not label a record “acceptance” or “rejection” unless the document and contract support that description.
If photographs or measurements matter, retain the original files with dates and device metadata where lawfully available. Identify who took them, where, and what they show without editing the originals.
Reconcile price, invoices and payments
Use a separate money schedule. It should show:
- the agreed price and approved variations;
- each invoice number, date, amount and due date;
- disputed line items and the reason recorded at the time;
- payments, allocations, credits, retentions and reversals;
- any interest, penalty or collection amount claimed; and
- the general-ledger, bank or supplier-statement source for each entry.
Do not use only the current account balance. A dispute may concern whether a variation was approved, whether an invoice matched a milestone, whether payment signalled acceptance, or whether a credit was allocated correctly. Preserve both the source transaction and the later reconciliation.
Keep complete electronic provenance
The Electronic Communications and Transactions Act recognises data messages and addresses matters such as writing, electronic agreements, integrity, evidential weight, retention, dispatch, receipt and attribution. That does not make every screenshot conclusive.
For important email, messaging, procurement and accounting material:
- export the complete thread or transaction where the system permits;
- retain attachments in the form received;
- keep sender, recipient, date and time information;
- record the business system or mailbox from which it came;
- preserve any audit log, version history or approval event; and
- make working copies without altering the preserved source.
The Constitutional Court’s approach to contract interpretation requires text to be considered with context and purpose. Contemporaneous business records can therefore matter not only because they show an event, but because they may explain the commercial setting in which a term was used. Context remains a legal assessment; do not select only the messages that favour one reading.
Separate notices from ordinary complaints
A complaint email, support ticket, meeting escalation and formal breach notice may do different work. For every potentially formal communication, record:
- its intended purpose;
- the clause or legal basis relied on;
- the alleged breach and supporting facts;
- any cure period or response date;
- the person and entity to whom it was addressed;
- the required and actual delivery method; and
- proof of dispatch, receipt and response.
Before sending a new communication, use the pre-letter supplier-dispute check. Do not rewrite an old message after the event or give a formal label to a document that did not comply with the governing process.
Record loss and mitigation without inflating either
Create a loss schedule that links each amount to a source. Possible categories may include replacement supply, additional labour, downtime, rework, storage, customer credits or other direct effects. Include saved expenditure and recovered amounts as well as costs.
For each item, state the date, amount, calculation, source document, payment status, connection to the disputed event and action taken to reduce further loss. Keep forecasts separate from incurred amounts. Whether a loss is legally recoverable depends on the contract, causation, remoteness, proof and other facts; the accounting entry alone does not settle that question.
Protect the record without over-collecting
Issue an internal preservation instruction to the relevant procurement, operations, finance and IT custodians when material records may be overwritten. Suspend routine deletion only within lawful and proportionate scope. Keep privileged advice separate and restrict access to the working file.
Do not take supplier systems, employee personal information, customer data or confidential material merely because it may be relevant. Record where externally held evidence exists and let an authorised legal process deal with access where necessary.
Final record-map check
- The exact parties and authority trail are identified.
- Every disputed obligation points to the correct contract layer.
- Order, performance, delivery and acceptance records are linked.
- Invoice and payment entries reconcile to source documents.
- Native electronic records and complete threads are preserved.
- Complaints and formal notices are not confused.
- Loss items include their calculation and mitigation record.
- Missing evidence has a named custodian and next step.
Use the contract-dispute evidence guide for the later question of presenting evidence. If the record map exposes a live deadline, cancellation issue or operational dependency, move to the commercial-lawyer escalation test.
Legal disclaimer
This record map provides general South African legal information and an evidence-organisation method. It does not decide contract formation, authority, interpretation, breach, acceptance, notice validity, prescription, loss or remedy. Those issues require the operative agreement and the facts of the particular supplier relationship.
FAQs
What is the most important record in a supplier contract dispute?
There is rarely one decisive record. Start with the contract hierarchy, then link each disputed obligation to the relevant order, performance or delivery record, acceptance or rejection evidence, invoice, payment, notice and recorded commercial consequence.
Are screenshots of supplier emails and messages enough?
Screenshots can be convenient working copies, but retain the complete native thread, attachments, sender and recipient details, timestamps, export information and any approval or version history where possible. Integrity, origin and context may matter.
Should delivery notes be kept if quality is the real dispute?
Yes. A delivery note can help prove what arrived, when and who received it, but it may not determine technical acceptance. Keep it with inspection, testing, rejection, return, remediation and later-use records.
How should a business record losses from a supplier breach?
Use a schedule that records each amount, date, calculation, source document, payment status, connection to the disputed event and mitigation step. Separate incurred costs, forecasts, saved expenditure and recovered amounts.
Related Lexuno paths
Related articles
Source notes
Legal note
This article is general legal information for South African readers. It is not legal advice. Speak to a qualified legal professional about your specific facts before taking action.