Transaction Processing Systems (TPS) & Office Automation Systems (OAS): Core Functions & Real-World Impact

Key Definitions & Core Concepts

1. Transaction Processing Systems (TPS)

TPS are real-time information systems designed to capture, store, modify, and retrieve data from routine business transactions (e.g., sales, payments, inventory updates). They ensure data accuracy, security, and consistency while supporting operational efficiency.

Key Characteristics of TPS:

How TPS Works (Step-by-Step):

1. Data Capture: Input from users, sensors, or machines (e.g., POS scanners in supermarkets).
2. Data Validation: Checks for errors (e.g., invalid amounts in Ncell top-up).
3. Processing: Updates databases (e.g., Nepal Rastra Bank’s loan records).
4. Storage: Saves data in structured formats (e.g., NEPSE trading logs).
5. Output: Generates reports (e.g., bank statements).

2. Office Automation Systems (OAS)

OAS streamlines administrative tasks using software tools to reduce manual work. Examples include:

• Email systems (e.g., Gmail for Pathao dispatch coordination)
• Document management (e.g., Nabil Bank’s loan application forms)
• Spreadsheets (e.g., Daraz inventory tracking)
• Project management tools (e.g., Trello for Chaudhary Group logistics)

Comparison: TPS vs. OAS

Real-World Applications in Nepal

1. eSewa & Khalti: TPS in Digital Payments

• How it uses TPS: Every transaction (e.g., Ncell bill payment, Daraz checkout) is logged in real-time with validation, encryption, and audit trails.
• Example Worked Trace:
  1. User initiates payment via eSewa app.
  2. System validates account balance and merchant details.
  3. Transaction is recorded in the database (TPS core function).
  4. Confirmation SMS/email is sent (OAS integration).

sequenceDiagram
    participant User
    participant eSewa(TPS)
    participant Bank
    participant Merchant

    User->>eSewa: Initiates payment (₹1,000 to Daraz)
    eSewa->>Bank: Checks balance & validates
    Bank-->>eSewa: Approves/Rejects
    eSewa->>Merchant: Updates inventory (TPS)
    eSewa->>User: Sends receipt (OAS)

2. NTC’s Billing System: TPS in Utility Payments

• TPS Role: Tracks call records, bill generation, and payment processing for millions of users.
• OAS Role: Automates customer service emails and bill reminders via SMS/email.

3. Daraz’s Order Processing: TPS + OAS Integration

• TPS: Handles inventory updates, order status changes, and payment confirmations.
• OAS: Uses spreadsheets for logistics tracking and emails for delivery updates.

Types of Transaction Processing Systems

TPS can be classified based on transaction type and processing mode:

A. By Transaction Type

1. Sales & Marketing TPS

   • Tracks customer orders, sales reports (e.g., Daraz sales dashboard).
   • Example: POS systems in supermarkets.

2. Human Resource TPS

   • Manages payroll, attendance, recruitment (e.g., Nabil Bank’s HR software).
   • Example: e-Attendance systems in universities.

3. Financial TPS

   • Handles banking, loans, investments (e.g., NEPSE trading system).
   • Example: eSewa’s transaction logs.

4. Manufacturing TPS

   • Monitors production schedules, inventory (e.g., Himalayan Java’s supply chain).
   • Example: Toyota’s Just-in-Time (JIT) inventory system.

B. By Processing Mode

1. Real-Time Processing
   • Immediate updates (e.g., ATM transactions).
2. Batch Processing
   • Grouped transactions (e.g., monthly payroll).

Advantages & Disadvantages

Advantages of TPS

✅ Efficiency: Reduces manual errors (e.g., NTC’s automated billing). ✅ Accuracy: Minimizes data entry mistakes (e.g., bank transfers). ✅ Security: Encryption protects sensitive data (e.g., eSewa’s fraud detection). ✅ Auditability: Tracks all changes for compliance (e.g., NEPSE records). ✅ Scalability: Handles high transaction volumes (e.g., Daraz’s peak sales).

Disadvantages of TPS

❌ High Initial Cost: Requires robust infrastructure (e.g., ERP setup for Chaudhary Group). ❌ Complexity: Needs trained staff (e.g., Nabil Bank’s IT team). ❌ Dependency on Technology: Downtime disrupts operations (e.g., NTC outages). ❌ Data Overload: Excessive transactions can slow systems (e.g., Ncell’s peak-hour issues).

Case Study: Nabil Bank’s Loan Processing System

Scenario: A customer applies for a ₹500,000 home loan. TPS Workflow:

1. Application Submission (OAS: digital form via bank’s website).
2. Credit Check (TPS: validates CIBIL score in real-time).
3. Approval/Rejection (TPS: updates loan database).
4. Disbursement (TPS: transfers funds to the customer’s account).
5. EMIs & Tracking (TPS: automates monthly deductions).

Why TPS?

• Speed: Approval in <24 hours (vs. weeks manually).
• Accuracy: No manual entry errors in loan records.
• Security: Encrypted customer data and transaction logs.

In the Real World

1. eSewa (Nepal)

   • Idea Used: Real-time TPS for digital payments.
   • How: Every UPI transaction (e.g., paying Pathao ride) is processed instantly with validation, encryption, and audit trails. If a user disputes a charge, eSewa’s TPS retrieves the exact timestamp and merchant details for resolution.

2. Daraz (Nepal)

   • Idea Used: TPS for order fulfillment + OAS for logistics coordination.
   • How: When you buy a Nepalgunj laptop, Daraz’s TPS:
     • Updates inventory (reducing stock).
     • Triggers OAS emails to the courier (e.g., Nepal Post).
     • Generates a trackable order ID (visible on the app).
   • Worked Example: During Janai Purnima sales, Daraz’s TPS handles 10,000+ orders/hour without errors, while OAS tools (like Trello) assign drivers in real-time.

3. NTC (Nepal)

   • Idea Used: Batch TPS for billing + OAS for customer notifications.
   • How: Every month, NTC’s TPS:
     • Processes millions of call records in batches.
     • Generates bills (TPS output).
     • Sends SMS reminders (OAS integration) if payment is delayed.
   • Real Impact: Reduces manual billing errors by 90% and cash collection delays by 50%.

Exam Tip

How to Score Full Marks in Unit 5:

1. Define Clearly: Always start with precise definitions (e.g., "TPS is a real-time system that processes transactions...").
2. Use Real Examples: Link concepts to Nepali businesses (e.g., eSewa, Daraz, NTC)—examiners love this!
3. Compare TPS vs. OAS: Highlight key differences in a table (as shown above).
4. Trace a Workflow: For TPS, describe step-by-step (e.g., bank transfer process).
5. Mention Desirable Characteristics: Focus on accuracy, security, auditability.
6. Avoid Vague Answers: Instead of "TPS is important", say:

   "TPS ensures real-time accuracy in NEPSE trading, preventing fraud and delays in stock transactions."

Common Mistakes to Avoid:

• ❌ Confusing TPS with ERP (TPS is transaction-specific; ERP is enterprise-wide).
• ❌ Forgetting to mention audit trails (a key TPS feature).
• ❌ Not linking OAS to real tools (e.g., Microsoft Office, Google Workspace).

Final Visual Summary

mindmap
  root((Unit 5: TPS & OAS))
    TPS[Transaction Processing Systems]
      Characteristics[Accuracy, Real-Time, Security, Audit Trail]
      Examples[eSewa, NTC, Daraz]
      Workflow[Capture → Validate → Process → Store → Output]
    OAS[Office Automation Systems]
      Tools[Email, Spreadsheets, Project Management]
      Examples[Nabil Bank HR, Chaudhary Group Logistics]
      Integration[TPS + OAS = End-to-End Automation]
    RealWorld[Applications in Nepal]
      eSewa[Digital Payments (TPS)]
      Daraz[Order Fulfillment (TPS + OAS)]
      NTC[Billing System (Batch TPS)]
      NabilBank[Loan Processing (TPS + OAS)]