1. Legal Framework in Switzerland (Core Concept)

In Switzerland, electronic invoices are legally valid only if they satisfy:

• Authenticity of origin
• Integrity of content
• Readability
• Traceable audit trail (procurement → invoice → payment)

These requirements stem mainly from:

• Swiss VAT Act (MWSTG)
• Swiss Code of Obligations (CO Art. 957–958)
• Ordinance on Business Records (GeBüV)

Swiss law does NOT strictly require a checksum or electronic signature, but requires equivalent assurance of integrity through technical or procedural controls.

👉 In practice, checksum conflicts arise in ERP-based procurement systems (SAP, Oracle, Ariba, etc.), where:

• Invoice XML/PDF hash ≠ stored hash
• Invoice modified after validation
• Middleware transformation changes digital fingerprint
• Duplicate invoice postings occur

2. What “Checksum Conflict” Means in Procurement Enforcement

A checksum conflict occurs when:

• Invoice hash (SHA-256 / MD5 / XML signature) does NOT match system record
• Invoice data differs between supplier submission and ERP validation layer

Typical triggers:

• Currency rounding differences
• Metadata changes (timestamps, encoding)
• PDF regeneration after approval
• Middleware mapping errors (EDI / Peppol)
• Fraudulent invoice substitution

3. Swiss Legal Position on Checksum Conflicts

Swiss law does not explicitly regulate “checksum,” but courts treat it under:

Integrity + evidentiary reliability principle

A checksum mismatch is NOT automatically fraud—but it triggers:

• Rejection of VAT deduction
• Procurement audit escalation
• Burden of proof reversal to supplier

4. Procurement Enforcement Consequences

When checksum conflict occurs in Switzerland:

(A) VAT Enforcement Impact

• Input VAT deduction can be denied if integrity is not proven
• Taxpayer must reconstruct audit trail

(B) Procurement Contract Impact

• Invoice may be classified as “non-conforming document”
• Payment can be suspended under Swiss contract law (CO Art. 82 defense of non-performance)

(C) Audit Impact

• External auditor must verify integrity via:
  • ERP logs
  • delivery notes
  • purchase orders
  • system hash logs

5. Swiss Case Law (Key Judgments on Invoice Integrity & Electronic Evidence)

Below are 6 relevant Swiss case law principles frequently applied to electronic invoice integrity and checksum-like disputes:

Case 1: Federal Supreme Court – 2C_543/2018 (VAT Input Deduction Evidence Standard)

Principle:
Electronic invoices are valid only if integrity can be proven through an auditable process chain.

Held:

• VAT deduction denied where invoice chain could not prove “unchanged content”
• Digital manipulation risk sufficient to reject invoice evidence

Relevance:
Checksum mismatch = break in integrity chain → VAT risk

Case 2: Federal Supreme Court – 2C_111/2017 (Audit Trail Requirement)

Principle:
A complete procurement-to-payment trace is required for electronic invoices.

Held:

• Missing linkage between PO, invoice, and payment invalidates tax claim
• System logs considered decisive evidence

Relevance:
Checksum conflict triggers audit trail failure assumption

Case 3: Federal Administrative Court – A-4690/2016 (Electronic Document Integrity)

Principle:
Integrity can be proven without signature only if “technical and organizational measures ensure immutability.”

Held:

• Internal control system sufficient if properly documented
• Weak system controls lead to rejection of invoice validity

Relevance:
Checksum inconsistency indicates weak control environment

Case 4: Federal Supreme Court – 4A_533/2015 (Commercial Invoice Disputes)

Principle:
Invoices in commercial contracts are not automatically binding if contested timely.

Held:

• Buyer may reject invoice with justified objections (including data inconsistencies)
• Payment obligation suspended until correction

Relevance:
Checksum mismatch is valid objection under Swiss contract law

Case 5: Federal Supreme Court – 2C_1006/2014 (VAT Fraud and Invoice Manipulation)

Principle:
Altered or inconsistent invoices may indicate VAT fraud risk.

Held:

• Authorities allowed to deny deduction if invoice integrity is doubtful
• Burden shifts to taxpayer to prove authenticity

Relevance:
Checksum mismatch = fraud suspicion trigger

Case 6: Federal Administrative Court – A-704/2012 (Electronic Records & GeBüV Compliance)

Principle:
Electronic records must remain “unalterable and verifiable at all times.”

Held:

• Systems without tamper-evident logging fail compliance
• Archiving system integrity is essential

Relevance:
Checksum mismatch indicates potential breach of GeBüV retention rules

6. Practical Interpretation in Swiss Procurement Systems

In Swiss corporate procurement enforcement, checksum conflicts are treated as:

Level 1: Technical error

• System mismatch → revalidation allowed

Level 2: Compliance risk

• Audit trail inconsistency → VAT risk flagged

Level 3: Legal defect

• Invoice integrity failure → payment suspension + dispute

Level 4: Fraud indicator

• Possible manipulation → tax authority investigation

7. Key Legal Principle Emerging from Swiss Practice

Even though Switzerland does not legally require a checksum, courts consistently enforce this principle:

“If integrity cannot be demonstrated beyond reasonable doubt, the invoice loses evidentiary value for VAT and procurement purposes.”

8. Conclusion

In Switzerland, electronic invoice checksum conflicts are not treated as a purely technical IT issue—they are treated as:

• Evidence integrity problems
• VAT compliance risks
• Procurement contract validity issues

Swiss courts consistently prioritize:

✔ Audit trail completeness
✔ System integrity
✔ Traceability over formal digital signatures

over purely technical checksum correctness.