EDI, E-Commerce Infrastructure & Data Exchange Systems

Core Concepts: What is EDI?

Definition & Purpose

Electronic Data Interchange (EDI) is the computer-to-computer exchange of structured business documents (invoices, orders, shipments) in a standardized electronic format. Unlike emails or PDFs, EDI automates data processing, eliminating manual re-entry and errors.

graph LR
    A["Business Partner A"] -->|"EDI Message"| B["EDI Translator"]
    B -->|"Standard Format"| C["Business Partner B"]
    C -->|"Automated Processing"| D["ERP/Accounting System"]

Why EDI?

• Speed: Instant transactions (e.g., NTC’s automated billing for telecom providers).
• Accuracy: No human errors in data entry.
• Cost savings: Reduces paper, postage, and manual labor.

EDI vs. Traditional Data Exchange

EDI Layers: How It Works

EDI operates in 7 layers, similar to the OSI model but tailored for business data. Each layer ensures interoperability between systems.

classDiagram
    class ApplicationLayer {
        +Business Documents (INVOICE, ORDERS)
        +EDI Standards (X12, EDIFACT)
    }
    class PresentationLayer {
        +Data Encoding (ASCII, XML)
        +Translation (EDI → ERP)
    }
    class SessionLayer {
        +Connection Management
        +Error Recovery
    }
    class TransportLayer {
        +Reliable Data Transfer (TCP/IP)
    }
    class NetworkLayer {
        +Routing (Internet/VPN)
    }
    class DataLinkLayer {
        +Physical Addressing (MAC)
    }
    class PhysicalLayer {
        +Cables/Wireless (Ethernet, 5G)
    }
    ApplicationLayer --> PresentationLayer : "Uses"
    PresentationLayer --> SessionLayer : "Uses"
    SessionLayer --> TransportLayer : "Uses"
    TransportLayer --> NetworkLayer : "Uses"
    NetworkLayer --> DataLinkLayer : "Uses"
    DataLinkLayer --> PhysicalLayer : "Uses"

Key Layers Explained

1. Application Layer:

   • Defines EDI standards (e.g., X12 for North America, EDIFACT for global trade).
   • Example: A Daraz supplier sends an ORDERS message in EDIFACT format to a manufacturer.

2. Presentation Layer:

   • Converts data into a machine-readable format (e.g., XML, ASCII).
   • Example: Khalti’s EDI gateway translates a bank transfer into an EDI-compliant PAYMENT message.

3. Session Layer:

   • Manages secure connections between trading partners.
   • Example: NTC’s EDI system uses VPNs to connect with telecom providers securely.

Real-World Applications of EDI in Nepal

1. NTC (Nepal Telecom) & Telecom Billing

• How EDI is used: NTC automates billing, inventory, and customer data exchange with telecom providers (e.g., Ncell, Smart Cell) via EDI.
• Example Workflow:
  1. A telecom provider (e.g., Ncell) sends a SUBSCRIBER_DATA EDI message to NTC.
  2. NTC’s system validates and processes the data in real-time.
  3. Automated invoices are generated and sent back to Ncell.
• Benefit: Reduces billing errors by 90% and speeds up payments.

2. Banking & Financial Transactions (Global Ime, NMB Bank)

• How EDI is used: Banks use EDI for automated loan processing, SWIFT messages, and interbank transfers.
• Example: Global IME Bank uses EDI to exchange LOAN_APPLICATION and PAYMENT_CONFIRMATION messages with corporate clients.
• Real Scenario:
  • A company applies for a ₹10M loan via an online portal.
  • The bank’s system automatically generates an EDI LOAN_REQUEST and sends it to the credit department.
  • Approval/rejection is sent back via EDI, eliminating paper trails.

3. Retail & Supply Chain (Daraz, Mega Mart)

• How EDI is used: Retailers like Daraz use EDI to automate order fulfillment with suppliers.
• Example Workflow:
  1. Daraz places an order for 500 smartphones via EDI (ORDERS message).
  2. The supplier (e.g., Transcend) confirms via EDI (ORDER_ACKNOWLEDGEMENT).
  3. Shipping details (SHIPMENT_NOTICE) are exchanged automatically.
• Benefit: Reduces order processing time by 70% and cuts costs.

EDI Standards: X12 vs. EDIFACT

Which One Does Nepal Use?

• Banks & Telecom: Mostly EDIFACT (global standard).
• Retail (Daraz): XML/JSON (modern APIs).
• Government (NTC): Custom EDI formats for billing.

E-Commerce Infrastructure: Supporting EDI

EDI requires robust infrastructure to function. Key components:

1. Hardware Requirements

• Servers: High-performance machines to handle large EDI volumes.
• Network: Dedicated leased lines or VPNs (e.g., NTC uses MPLS for secure EDI).
• Storage: Databases to store EDI logs (e.g., PostgreSQL for transaction history).

2. Software Requirements

3. Security in EDI

EDI transactions must be confidential, intact, and non-repudiable (cannot be denied).

• Confidentiality: Encrypted messages (e.g., AES-256).
• Integrity: Digital signatures (e.g., SHA-256 hashing).
• Non-repudiation: Certificates (e.g., Nepal’s e-SDS for legal validity).

Worked Example: EDI in a Bank Loan Process

Scenario: A company applies for a ₹5M loan via Global IME Bank. The bank uses EDI for processing.

sequenceDiagram
    participant Client as Company
    participant Bank as Global IME Bank
    participant EDI_Gateway as EDI Gateway
    participant ERP as Bank ERP System

    Client->>Bank: Submits Loan Application (Online Portal)
    Bank->>EDI_Gateway: Converts to EDI (LOAN_REQUEST)
    EDI_Gateway->>ERP: Sends LOAN_REQUEST (EDIFACT)
    ERP->>EDI_Gateway: Processes & Generates LOAN_APPROVAL
    EDI_Gateway->>Bank: Returns Approval (EDI)
    Bank->>Client: Notifies via Email/SMS

Key Steps:

1. Client submits loan details via a web portal.
2. Bank’s EDI gateway converts the data into an EDI LOAN_REQUEST (EDIFACT format).
3. ERP system processes the request and generates an APPROVAL message.
4. EDI gateway sends the approval back, and the bank notifies the client.

Why EDI?

• No manual data entry → 0% errors.
• Faster approval (hours vs. days).
• Audit trail via EDI logs.

Challenges & Limitations of EDI

Exam Tip: How to Score Full Marks

1. Define EDI clearly (automated, structured, B2B).
2. Compare EDI vs. traditional methods (speed, cost, accuracy).
3. Explain EDI layers (focus on Application & Presentation).
4. Give real-world examples:
   • NTC’s telecom billing (automated invoicing).
   • Bank loan processing (EDI + ERP).
   • Daraz’s supplier orders (XML/EDI).
5. Discuss security: Always mention confidentiality, integrity, non-repudiation.
6. For infrastructure questions:
   • Hardware: Servers, VPNs, storage.
   • Software: EDI translators, middleware, ERP.

Common Mistakes to Avoid:

• ❌ Confusing EDI with email attachments (EDI is automated, not manual).
• ❌ Forgetting standards (X12 vs. EDIFACT).
• ❌ Ignoring security (always link EDI to PKI, encryption, digital signatures).

Final Note: EDI is the backbone of B2B e-commerce in Nepal. From NTC’s billing to bank loans, understanding EDI will help you analyze how businesses automate transactions—a key skill for e-commerce analysts, IT consultants, and ERP specialists. Always relate your answers to real-world Nepalese examples (NTC, banks, Daraz) to score full marks!