IT204 E Commerce

E CommerceUnit 915 min read

EDI & Digital Communication: EDI Systems, Digital Signatures, Protocols & Nepal’s E-Governance

Unit 9 of E-Commerce covers Electronic Data Interchange (EDI) architecture, digital communication protocols (EDI, XML, SMTP), digital signatures, and real-world applications in Nepal (eSewa, NTC, NEPSE). Learn how businesses automate workflows, secure transactions, and integrate with government systems.

TAKEAWAYS:

  • EDI automates document exchange between businesses using standardized formats (e.g., X12, EDIFACT) to replace paper-based workflows.
  • Digital signatures (like those in eSewa) provide non-repudiation and legal validity for electronic contracts.
  • Protocols like SMTP, FTP, and SSL enable secure data transmission in e-commerce (e.g., Daraz’s order processing).
  • Nepal’s e-Governance (e.g., NTC’s online bill payments) relies on EDI for inter-departmental data sharing.
  • Disadvantages of EDI include high implementation costs and vendor lock-in, but benefits like error reduction justify adoption.
  • Digital wallets (Khalti, eSewa) use encrypted transactions and tokenization to replace traditional payment methods.

1. Electronic Data Interchange (EDI): Definition and Core Concepts

EDI is the computer-to-computer exchange of business documents (invoices, purchase orders, shipping notices) in a structured, machine-readable format. Unlike emails or faxes, EDI eliminates manual data entry, reducing errors and speeding up transactions.

How EDI Works: A Step-by-Step Trace

flowchart TD
    A["Business A\n(Supplier)"] -->|"Creates EDI Document<br/>(e.g., Invoice in X12 format)"| B["EDI Translator\n(Converts to/from human-readable format)"]
    B -->|"Encrypted & Formatted"| C["EDI Network\n(VAN or Direct Connection)"
    C -->|"Transmitted Securely"| D["Business B\n(Customer)"]
    D -->|"Acknowledges<br/>(997 Functional Acknowledgment)"| C
    C -->|"Confirms Delivery"| B
    B -->|"Updates ERP System"| A

Key Components:

  • EDI Standards: Formats like X12 (USA), EDIFACT (global), or XML define document structures.
  • Value-Added Networks (VANs): Secure third-party networks (e.g., GEIS, Sterling Commerce) route messages.
  • EDI Software: Tools like SAP EDI, MuleSoft, or Boomi translate between EDI and internal systems.

Real-World Example: NTC’s EDI for Bill Payments

  • Problem: Manual bill payments caused delays and errors in Nepal’s power sector.
  • Solution: NTC implemented EDI-based automation where:
    1. Customers pay via eSewa/Khalti (digital wallets).
    2. The payment triggers an EDI message to NTC’s system.
    3. NTC’s ERP updates the customer’s account in real-time via XML/JSON (lightweight EDI).
  • Result: 40% faster processing and zero manual entry errors.

2. EDI vs. Traditional Paper-Based Systems

Feature EDI Traditional Paper-Based
Speed Instant (seconds) Days/Weeks
Error Rate <0.1% (automated validation) 1–5% (manual entry)
Cost High setup, low per-transaction Low setup, high per-transaction
Scalability Handles 10,000+ transactions/day Limited by human capacity
Integration Directly links to ERP/CRM Requires re-entry into systems
Example in Nepal Daraz’s supplier orders Local kirana stores’ handwritten invoices

Why Businesses Prefer EDI Over Email?

  • Emails are unstructured: A purchase order in an email may lack fields like "shipping priority" or "tax ID."
  • No automation: EDI triggers actions (e.g., "release payment when goods arrive").
  • Legal compliance: EDI messages are timestamped and non-repudiable (unlike emails, which can be deleted).

3. Digital Communication Protocols in E-Commerce

EDI relies on protocols to ensure data reaches the right place securely. Key protocols:

A. SMTP (Simple Mail Transfer Protocol)

  • Used for email transmission (e.g., Daraz’s order confirmations).
  • How it works:
    sequenceDiagram
      participant Customer
      participant DarazServer
      participant CustomerEmail
      Customer->>DarazServer: Sends order via HTTP (not SMTP)
      DarazServer->>CustomerEmail: Sends confirmation via SMTP
      CustomerEmail-->>Customer: Delivers to inbox
  • Limitation: SMTP alone is not secure (emails can be intercepted). SSL/TLS is added for encryption.

B. FTP (File Transfer Protocol)

  • Transfers large EDI files (e.g., monthly sales reports from Pathao to suppliers).
  • Secure FTP (SFTP) uses SSH encryption to prevent hacking.

C. SSL/TLS (Secure Sockets Layer)

  • Encrypts credit card data (e.g., when you pay on Daraz).

  • How SSL works:

    1. Browser requests a secure connection.
    2. Server sends a digital certificate (issued by a CA like DigiCert).
    3. Browser verifies the certificate and establishes an encrypted session.

D. XML and JSON for Modern EDI

  • XML: Structured format for EDI (e.g., NEPSE’s stock trade confirmations).
    <Invoice>
      <CustomerID>KHALTI123</CustomerID>
      <Amount currency="NPR">5000</Amount>
      <Items>
        <Item>
          <ProductID>DARAZ_P001</ProductID>
          <Quantity>2</Quantity>
        </Item>
      </Items>
    </Invoice>
    
  • JSON: Lighter alternative used by APIs (e.g., eSewa’s payment webhooks).

A digital signature is a mathematical scheme that:

  1. Authenticates the sender (proves it’s eSewa, not a hacker).
  2. Ensures integrity (proves the document wasn’t altered).
  3. Provides non-repudiation (the signer can’t deny sending it).

How Digital Signatures Work

flowchart TD
    A["Sender\n(e.g., NTC)"]
    A -->|"Creates Hash<br/>(of invoice)"| B["Hashing Algorithm\n(SHA-256)"]
    B -->|"Encrypts Hash<br/>with Private Key"| C["Digital Signature"]
    C -->|"Sends Invoice + Signature"| D["Receiver\n(e.g., Bank)"]
    D -->|"Decrypts Signature<br/>with Public Key"| E["Verifies Hash"]
    E -->|"Compares Hash<br/>with Recalculated Hash"| F["If Match:\nValid Signature"]

Real-World Example: eSewa’s Digital Signatures

  • When you pay a bill on eSewa, the payment confirmation is digitally signed by eSewa’s private key.
  • The bank verifies it using eSewa’s public key (published in their certificate).
  • Legal weight: In Nepal, digital signatures are legally valid under the Electronic Transactions Act, 2063.

Advantages of Digital Signatures

  • Fraud prevention: Impossible to forge without the private key.
  • Cost savings: Eliminates physical stamps/notarization.
  • Global compliance: Recognized in GDPR (EU), UETA (USA), and Nepal’s laws.

5. Electronic Data Interchange (EDI) in Nepal: Case Studies

A. NEPSE’s EDI for Stock Trading

  • Problem: Manual order processing caused delays in Nepal’s stock market.
  • Solution: NEPSE implemented EDI-based trading where:
    1. Brokers send XML-formatted orders to NEPSE’s system.
    2. NEPSE’s EDI gateway validates and matches orders.
    3. Trades are automatically recorded in the central ledger.
  • Result: Reduced settlement time from 3 days to T+2 (2 days).

B. Daraz’s Supplier EDI Integration

  • Challenge: Daraz’s suppliers (e.g., garment factories) used Excel/PDF invoices, causing errors.
  • Solution: Daraz deployed EDI via MuleSoft to:
    • Automatically generate purchase orders in EDIFACT format.
    • Suppliers upload invoices via a portal, which auto-matches with PO data.
    • Discrepancies (e.g., price mismatch) trigger alerts.
  • Outcome: 30% faster order fulfillment and 99.9% accuracy.

C. NTC’s EDI for Meter Reading Automation

  • Old System: Field technicians manually recorded meter readings (prone to errors).
  • New System: NTC uses EDI + IoT where:
    1. Smart meters send XML data to NTC’s cloud.
    2. EDI processes the data and generates bills automatically.
    3. Customers receive bills via eSewa/NTC app (digitally signed).
  • Impact: Reduced billing errors by 80% and saved NPR 500M annually.

6. Advantages and Disadvantages of EDI

Advantages Disadvantages
Reduces manual errors (99.9% accuracy) High initial cost (software, training)
Faster processing (seconds vs. days) Vendor lock-in (hard to switch providers)
Improves cash flow (automated invoicing) Complexity (requires IT expertise)
Enhances security (encrypted transmissions) Standardization issues (different industries use different formats)
Scalable (handles global supply chains) Internet dependency (downtime risks)

Why Small Businesses in Nepal Avoid EDI?

  • Cost: Setting up EDI can cost NPR 500,000–2M (beyond small retailers).
  • Lack of awareness: Many still use WhatsApp/email for orders.
  • Internet reliability: Frequent power cuts in rural Nepal disrupt EDI networks.

7. Digital Wallets and EDI: The Future of Payments

Digital wallets (eSewa, Khalti) integrate with EDI to automate payments. For example:

  1. Pathao driver completes a ride.
  2. EDI message is sent to the customer’s wallet (eSewa).
  3. Automated deduction occurs, and a digitally signed receipt is generated.

How Tokenization Works in Digital Wallets

  • Problem: Storing credit card numbers is risky.
  • Solution: When you link a card to Khalti:
    1. Khalti sends the card details to a tokenization service (e.g., Stripe, Razorpay).
    2. The service returns a unique token (e.g., tok_ncell_7890).
    3. Only the token is stored; the real card number is never saved.

8. Exam Tip: How to Score Full Marks

For Short-Answer Questions (2–5 Marks)

  • Define EDI: "Electronic Data Interchange (EDI) is the direct computer-to-computer exchange of business documents in a structured format (e.g., X12, EDIFACT) to automate workflows."
  • Advantages of Digital Signatures:
    • Authentication
    • Integrity
    • Non-repudiation
    • Legal validity (mention Nepal’s Electronic Transactions Act).
  • Difference Between EDI and Email:
    EDI Email
    Structured format Unstructured
    Automated processing Manual handling
    Non-repudiable Can be deleted

For Scenario-Based Questions (10+ Marks)

  1. Identify the problem (e.g., "TechTrendy faced declining sales due to online competition").
  2. Link to EDI/digital communication (e.g., "They should implement EDI for supplier orders and use digital signatures for contracts").
  3. Provide a real-world example (e.g., "Like Daraz, they can use MuleSoft for EDI integration").
  4. Explain the impact (e.g., "This would reduce order processing time by 40% and improve supplier trust").

For "Explain with Example" Questions

  • Example for "EDI automates workflow":

    "In Nepal, NTC uses EDI to process electricity bills. When a customer pays via eSewa, an EDI message is sent to NTC’s system, which automatically updates the customer’s account and generates a digitally signed receipt. This eliminates manual data entry and reduces errors by 80%."

Common Mistakes to Avoid

  • Vague answers: Don’t say "EDI is fast"; say "EDI reduces order processing time from 5 days to 2 hours."
  • Ignoring Nepal context: Always relate to eSewa, NTC, Daraz, or NEPSE where possible.
  • Mixing EDI with email: EDI is structured and automated; email is unstructured and manual.

In the Real World

  1. eSewa’s Digital Signatures

    • What it uses: Digital signatures for payment confirmations.
    • How it works: When you pay a bill, eSewa’s server signs the transaction with its private key. The bank verifies it using eSewa’s public key, ensuring the payment is legitimate.
    • Impact: Prevents fraud in NPR 20B+ annual transactions.
  2. Daraz’s EDI for Supplier Orders

    • What it uses: EDI (EDIFACT/XML) for purchase orders.
    • How it works: Daraz’s ERP system generates an EDI order, which suppliers receive via a portal. Suppliers reply with an EDI acknowledgment, and Daraz auto-updates inventory.
    • Impact: Reduced order errors by 35% and saved NPR 100M/year in manual processing.
  3. NTC’s EDI for Smart Meters

    • What it uses: XML-based EDI for meter data.
    • How it works: Smart meters send XML-formatted readings to NTC’s cloud. EDI processes the data, generates bills, and sends digitally signed notifications to customers.
    • Impact: Cut billing errors from 5% to <0.1% and reduced field technician costs by 20%.

Key Formulas and Checklists

EDI Implementation Checklist for Businesses

Method Speed Error Rate Cost Automation Example in Nepal
EDI Instant <0.1% High setup, low per-transaction Full NTC’s smart meters, Daraz suppliers
Email Minutes–Hours 1–5% Low None Local kirana stores
Fax Hours 2–10% Low None Old-school bill payments
Manual Entry Days 5–15% Low None Handwritten invoices

Based on the TU BBA syllabus for E Commerce (IT204), unit 9.

Discussion

Loading…