A completion certificate and a UPD in EDO vs a paper contract: where the evidence base breaks

A typical picture: the contract was signed as a PDF or even on paper, while completion certificates and universal transfer documents (UPDs) have been running through electronic document exchange (EDO) for a year. In a claim it turns out the amount in the UPD does not match the estimate, the subject in the certificate is wider than the contract, and the “current” version of the contract exists only in one party’s email. The evidence base breaks not in court, but in the archive.

Where the gap appears

A paper contract (or “just a file”) and electronic closing documents live in different environments. The gap appears when nobody checks the chain: offer or contract, then addenda, then specifications, then the certificate or UPD, then payment.

• The contract was edited in Word, and a certificate on the old estimate went into EDO
• A UPD was signed with a new item list and no addendum to the contract
• EDO holds several versions of the certificate, while the “paper” contract is one file with no edition date
• The signatory in EDO does not match the person in the contract or the power of attorney

What to compare in a claim

1. Subject and volume

• The wording of the subject in the contract vs the name in the certificate or UPD
• Units, quantity, and milestones — whether they match the annex
• Whether there is work outside the contract that “slipped through” only in the closing documents

2. Amounts and taxes

• The contract or specification price vs the UPD total
• VAT: the rate and how it is shown — as in the contract
• Certificates of partial delivery: the cumulative total does not exceed the contract limit

3. Dates and editions

• The date the contract was signed and the date of the certificate or UPD
• Addenda that were in force on the closing date
• The contract file version (name, hash, date) vs what the claim refers to

4. Signatures and authority

• Who signed the contract, and who signed the document in EDO
• The power of attorney or MChD as of the moment the closing documents were signed
• The document status in EDO: signed by both parties, withdrawn, or rejected

What to archive in advance

1. The final file of the contract and of each addendum (not only a scan “for printing”)
2. Specifications, estimates, and annexes with numbers and dates
3. Exports of certificates and UPDs from EDO, plus signing receipts and protocols
4. Correspondence on a change of volume and price (at least the key emails)
5. Powers of attorney and details of the signatories as of the closing dates

If the contract was edited several times, compare the versions before you write the claim: comparing contract versions.

How not to keep accumulating the gap

• The contract number and date go on every certificate and UPD
• A change of volume or price goes only through an addendum, before the closing documents are signed
• One “reference” contract file in shared storage, with a version
• A rule: without a reference to the specification in force, the certificate is not signed

A 10-minute checklist

Related reading

• Electronic contracts
• Comparing contract versions
• How to compare two documents in Word
• Agreeing edits in a contract

Short conclusion

EDO does not replace the contract and does not repair the gap by itself. A strong position in a dispute is when the contract, the addenda, and the closing documents say the same thing, and the versions sit in an archive with dates. Check the chain before the claim, not after the counterparty’s reply.