Disputes and Arbitration

Winning a VND 12 Billion EPC Dispute with Emails: Case Study

Làm việc với laptop trên bàn văn phòng, minh họa chuỗi email làm chứng cứ trong tranh chấp hợp đồng EPC

Winning a VND 12 Billion EPC Dispute with Emails: Case Study and 5 Lessons

Case facts have been anonymized and simplified; party names, locations and some details changed for confidentiality. The VND 12 billion figure is an illustrative disputed value per the topic brief; details have been generalized.

In EPC (engineering–procurement–construction) disputes, "variations" are the classic trigger: contractors perform extra work on verbal orders, and owners later deny them for lack of signed appendices. The case below — with nearly VND 12 billion recovered — shows how well-governed email chains can become the "savior".

Contents

1. Case background

The contractor (Party A) signed an EPC contract to build an industrial plant for the owner (Party B). During construction, Party B repeatedly ordered design changes and additional items for new technology — all via site management instructions and daily email exchanges.

At final settlement, Party B only paid per the original contract, rejecting nearly VND 12 billion in variations: "no appendix, no handwritten document".

2. The deadlock: no signed appendix

A situation thousands of contractors face: tight schedule, owner urging "work first, paperwork later", then at payment time "no paperwork, no payment". Party A's file then contained:

  • The original EPC contract (clause: all changes require written appendix);
  • Site diaries and field records — but many items lacked Party B's countersignature;
  • And an email chain exchanged between the two sides throughout construction.

3. The turning point: the email chain

Reviewing all emails, Party A's lawyers reconstructed the full picture:

  • Variation orders: emails from Party B's authorized personnel (corporate domain) requesting design changes with clear scope;
  • Quantity confirmation: back-and-forth emails confirming completed quantities per phase, with calculation sheets;
  • Payment confirmation: emails from Party B confirming variations would enter payment — corroborated by actual payment records.

The three links "order – quantity confirmation – payment confirmation" formed a closed evidentiary chain.

Key legal grounds:

  • Law on Electronic Transactions 20/2023 (effective 01/7/2024): data messages have documentary value when integrity and extractability conditions are met;
  • Civil Procedure Code 2015: data messages are a form of evidence.

Party A's arguments:

  1. Sender authentication: corporate-domain emails from authorized personnel — sufficient to establish Party B's intent;
  2. Integrity: emails preserved intact with full metadata; Party B could not prove alteration;
  3. Consistency with other evidence: payment records and site minutes matching the email contents corroborated the email chain;
  4. Clear agreement intent: email content showed complete offer–acceptance on work scope and pricing principles, constituting a binding agreement despite no signed appendix.

5. Outcome

The court granted Party A's claims: ordering Party B to pay the email-proven variations plus late-payment interest — nearly VND 12 billion recovered in total.

6. Five project email governance lessons

  1. Every variation order needs email confirmation. "Work first, paperwork later" is the fastest road to disputes — at minimum, get it in an email.
  2. Use corporate-domain email. Personal emails are hard to tie to representative capacity; corporate domains link directly to the entity.
  3. Define speaking authority clearly. State who may confirm quantities and commit payments by email — avoiding "staff promised, company denied".
  4. Centralize backups; never delete project emails. When disputes loom, notarize or certified-backup immediately.
  5. Confirm quantities periodically by email. Do not wait until final settlement — per-phase email confirmation is both evidence and cash-flow control.

7. Frequently asked questions

Q: Are emails admissible as evidence before the court?

A: Yes. Emails are data messages under the Law on Electronic Transactions 2023 and are recognized as evidence if conditions are met: identifiable sender/recipient, content integrity, and extractability/storage.

Q: What conditions give emails evidentiary value?

A: Three core conditions: (1) authenticated sender (address tied to the entity); (2) intact, unaltered content; (3) extractable, printable and storable for presentation. Work emails on corporate domains are more persuasive than personal ones.

Q: Can a case be won with only emails and no signed contract appendix?

A: Yes, as this illustrative scenario shows. When email chains clearly show the parties' agreement intent (variation orders, quantity confirmation, payment commitments), courts may recognize them as binding agreements.

Q: How should emails be preserved for use as evidence?

A: Never delete work emails; back up regularly; when disputes loom, notarize or certified-backup immediately; keep metadata intact (timestamps, sender/recipient). See T-247 for in-depth electronic evidence.

Q: What if the counterparty denies the emails?

A: Technical forensics can verify (email addresses, servers, integrity), cross-checked with other evidence (meeting minutes, payment records) to corroborate.

Q: How should enterprises govern project emails to prevent disputes?

A: Five principles: use corporate-domain email; confirm every variation order by email; define who may speak for the company; centralize backups; set project email retention periods.

8. When to work with a lawyer

Work with a lawyer as soon as: off-contract variations arise without written confirmation; the counterparty starts delaying payment for "missing paperwork"; electronic evidence needs litigation-standard collection and preservation; or litigation is prepared in EPC/construction disputes. For the in-depth electronic evidence framework, see T-247. FLAT Law Firm represents construction and EPC disputes — contact hotline 0988424851.

References

  • Law on Electronic Transactions 20/2023/QH15 (effective 01/7/2024).
  • Civil Procedure Code 2015 (92/2015/QH13).
  • Content cross-checked at time of writing (28/9/2026).

—