A seller says a customer owes USD 87,400.

The finance team has six invoices. Sales has the signed framework agreement. Logistics has delivery records in a portal that will delete old data after 90 days. The buyer's purchasing manager admitted part of the balance in a messaging app. Two credit notes exist, but nobody agrees which invoices they belong to.

The number “87,400” may be correct. The file is not ready.

A payment-default evidence file should let a new reviewer answer four questions quickly:

  1. Why did the payment obligation arise?
  2. When did it become due?
  3. What part remains unpaid?
  4. What defenses or deductions has the debtor actually raised?

The goal is not to create a dramatic bundle. It is to preserve the transaction chain.

Start with the hard numbers

Create a one-page debt ledger before collecting thousands of pages.

Item Amount
Gross invoiced 102,400
Payments received 10,000
Accepted credit notes 5,000
Claimed balance 87,400
Debtor-admitted amount 62,400
Disputed amount 25,000

Every number needs a record behind it.

If the arithmetic cannot be reconstructed from source documents, the claim is not ready for escalation.

Record 1: the contract formation set

Preserve:

  • signed master contract;
  • purchase order;
  • order confirmation;
  • schedules;
  • price list;
  • specifications;
  • amendments;
  • incorporated terms.

Why it matters: the invoice does not create the whole legal relationship. The contract set may determine payment triggers, currency, set-off, interest, dispute forum and notice.

Do not keep only a flattened “final.pdf” if earlier versions explain a later disagreement.

Record 2: proof of performance

For goods:

  • bill of lading or waybill;
  • warehouse receipt;
  • delivery note;
  • carrier event data;
  • receiving signature;
  • quantity records.

For services:

  • milestone approvals;
  • work logs;
  • acceptance email;
  • deliverables;
  • time sheets where contractually relevant.

Why it matters: many payment defenses begin with “you did not perform what triggered payment.”

Preserve portal exports before retention periods expire.

Record 3: inspection and acceptance evidence

Keep inspection reports, non-conformity notices, test results, acceptance certificates, return requests, photos with original metadata where relevant, and agreed cure records.

Why it matters: a buyer may say the price is unpaid because goods were defective. The seller may say the buyer accepted them. The evidence needs to show what happened, not just each side's conclusion.

Record 4: the invoice set

For every invoice, capture:

  • invoice number;
  • issue date;
  • currency;
  • gross amount;
  • tax treatment where relevant;
  • referenced PO;
  • due date;
  • delivery or milestone it relates to;
  • recipient or address used.

Keep the original invoice file and any corrected version.

Do not silently replace Invoice 104 with “Invoice 104 corrected” and delete the earlier document.

Record 5: statement of account and payment history

Create a chronological ledger:

Date Event Debit Credit Balance Source

Include partial payments, refunds, credits and reallocations.

Why it matters: a claim may fail operational review because finance and legal use different balances.

If the debtor has paid in multiple currencies, record original currency and conversion treatment rather than inventing one blended number.

Record 6: the debtor's admissions and objections

Preserve statements such as:

  • “We agree Invoice 104 is payable.”
  • “We dispute only Lot 3.”
  • “We will pay EUR 25,000 on Friday.”
  • “We are withholding because of the warranty claim.”

Save the full context, not a cropped screenshot.

Why it matters: it identifies the real dispute.

But do not assume an admission has the same limitation or evidentiary effect in every jurisdiction. Local law decides that.

Record 7: credit notes, set-off and counterclaim material

This folder should answer:

  • what credit was issued;
  • who approved it;
  • which invoice it applies to;
  • whether the debtor claims a separate loss;
  • whether set-off is contractually restricted;
  • whether the alleged counterclaim is quantified.

A buyer saying “we have damages” is different from a documented, quantified and legally available set-off.

Record 8: payment-chasing communications

Keep the sequence:

  • ordinary reminder;
  • AP response;
  • escalation;
  • promised date;
  • missed promise;
  • settlement proposal;
  • formal demand.

The value is in chronology.

A clean sequence can show whether the matter was administrative for two weeks and became a legal dispute only later.

Record 9: debtor identity and enforceability records

Preserve lawful corporate information showing:

  • exact legal name;
  • registration number;
  • registered address;
  • known trading address;
  • contract-signing entity;
  • guarantor or security documents, if any;
  • known asset locations at a high level.

Why it matters: the company that sent purchase emails may not be the company that signed the contract.

Avoid speculative asset allegations. Mark unverified information as unverified.

Record 10: applicable-law, deadline and procedure documents

Collect:

  • governing-law clause;
  • court or arbitration clause;
  • escalation clause;
  • notice or service clause;
  • guarantee deadlines;
  • credit-insurance notice requirements;
  • any insolvency filing affecting the debtor.

Then create a deadline sheet.

This is where payment collection becomes legal process management.

Digital evidence: preserve before reorganizing

Electronic commerce often depends on emails, portals, PDFs and system logs.

UNCITRAL's Model Law on Electronic Commerce is a useful international reference for the legal recognition of electronic information, but it is a model for domestic enactment rather than a universal evidence code.

Operationally:

  • preserve original exports;
  • note export date;
  • keep message headers where relevant;
  • avoid overwriting source files;
  • hash critical files if the matter is serious;
  • separate originals from working annotations.

A spreadsheet summary can be excellent, provided it points back to the source.

Interest and recovery-cost documents belong in their own folder

If interest or recovery costs will be claimed, preserve the legal basis.

For example, the UK's Late Payment of Commercial Debts (Interest) Act 1998 creates a statutory-interest framework for qualifying debts. EU Directive 2011/7/EU addresses late payment in commercial transactions within its scope through Member State implementation.

A demand should not simply say “interest applies” because another company used that sentence.

Keep:

  • contract interest clause;
  • applicable statutory source;
  • rate calculation;
  • start date;
  • currency;
  • recovery-cost basis.

The CISG file, if relevant

For qualifying international sales, keep a short legal-research note:

  • parties' places of business;
  • Contracting State status;
  • exclusion wording, if any;
  • governing-law clause;
  • payment obligation;
  • any notice or conformity dispute;
  • Article 78 interest issue if a sum is in arrears.

Do not turn this note into a homemade legal opinion. Its job is to help counsel see the questions immediately.

What not to do to your evidence

Do not:

  • delete “bad” emails;
  • edit screenshots and discard originals;
  • backdate documents;
  • rewrite an admission;
  • merge documents and lose source files;
  • change filenames in a way that destroys version history;
  • call an internal summary “the contract”;
  • calculate a balance without showing credits.

Good evidence organization increases clarity. It should never change history.

A folder structure that works

00_DEBT_LEDGER
01_CONTRACT
02_PERFORMANCE
03_INSPECTION_ACCEPTANCE
04_INVOICES
05_PAYMENTS_CREDITS
06_DEBTOR_COMMUNICATIONS
07_SET_OFF_COUNTERCLAIMS
08_DEMANDS_SETTLEMENT
09_DEBTOR_ID_ENFORCEMENT
10_LAW_DEADLINES

Inside each folder, use date-first filenames where practical, such as 2026-08-14_Buyer_AP_email_invoice104.pdf.

Quality-control test before escalation

Give the folder to someone who has never seen the transaction.

Can they answer within 20 minutes:

  • What was sold?
  • For how much?
  • Was it delivered or performed?
  • When was payment due?
  • What has been paid?
  • What exactly is disputed?
  • What does the debtor admit?
  • Which deadline runs next?
  • Where will the dispute be heard?
  • Where could recovery realistically occur?

If not, the file needs work before it needs more pressure.

Record 11: the entity map

A surprising number of collection files identify the brand but not the debtor.

Create a one-page entity map showing:

  • legal name on the contract;
  • legal name on the purchase order;
  • invoice recipient;
  • delivery recipient;
  • parent or affiliate names appearing in correspondence;
  • registration details where lawfully available;
  • bank-account payee previously used.

Do not assume a parent company is liable simply because its logo appears in the email footer. The point of the map is the opposite: expose where the identities differ so a lawyer can analyze them.

Record 12: the dispute register

If the buyer has raised complaints, do not bury them in the correspondence folder. List each one.

Date raised Buyer allegation Amount affected Creditor response Evidence
date “20 units damaged” amount if stated pending / answered inspection/photos
date “shipment late” amount if stated answered transport record

A dispute register stops the team from saying “they are just making excuses” before anyone has actually tested the allegations.

Record 13: the calculation sheet

Separate:

  • principal;
  • contractual interest, if any;
  • statutory interest, if any and applicable;
  • contractual fees;
  • statutory recovery amounts, if any and applicable;
  • credits;
  • returns;
  • set-offs actually agreed;
  • taxes or currency adjustments.

Every number should point to its source and date.

This matters because legal frameworks differ. A UK statutory late-payment amount, for example, cannot simply be pasted into a claim governed by another country’s law. EU late-payment rules also operate through the applicable Member State legal framework. The calculation sheet should therefore include a column called legal basis / to verify.

Record 14: the asset and collectability note

This is not proof of liability. It is proof of whether spending more may make commercial sense.

Record only lawfully obtained, reasonably reliable information:

  • operating status;
  • known locations;
  • public insolvency or restructuring information;
  • known property or accounts only where properly verified;
  • other creditor developments;
  • collection constraints.

Mark rumors as rumors or exclude them.

Record 15: the authority and settlement log

If several managers can negotiate, record:

  • who can approve a discount;
  • maximum payment extension;
  • minimum upfront payment;
  • whether security is required;
  • who can suspend shipments;
  • who can authorize formal proceedings.

Many weak settlements happen because the person on the call does not know the company’s limits.

Evidence hygiene: keep originals and working copies separate

For emails, PDFs, spreadsheets and electronic order records:

  • preserve the original file where possible;
  • avoid overwriting it with annotated versions;
  • keep export date and source system;
  • preserve attachments;
  • record who created a summary;
  • label translations and OCR as derivatives.

UNCITRAL’s electronic-commerce framework is useful background for thinking about electronic records, but evidentiary admissibility and authentication remain matters of applicable law and procedure.

The handoff test

Before sending the file to a lawyer or collection professional, give the index to a colleague who has never seen the matter.

If that person cannot answer these questions in ten minutes, the file is not ready:

  1. Who owes whom?
  2. How much principal is claimed?
  3. What made it due?
  4. What was delivered?
  5. What does the buyer dispute?
  6. Which contract and forum clause apply?
  7. What has already been promised?
  8. What is the next deadline?

The goal is not a beautiful archive. It is a file that lets the next decision-maker work without reconstructing the company’s memory.

Bottom line

A payment claim becomes usable when its arithmetic and story can both be reconstructed from source records.

Build the debt ledger first, then prove formation, performance, invoice, balance, objections and procedure. Preserve originals. Separate facts from conclusions. Let the legal team decide what is admissible and legally sufficient in the actual forum.

General commercial information only, not legal advice. Evidence, limitation, interest, set-off and enforcement rules vary by jurisdiction.

Related Reading

Sources and Jurisdiction Boundaries