AE112: ACCOUNTING INFORMATION SYSTEMS (AIS)

Chapter 3: Transaction Processing

By: Robert E. Regala

A. DESCRIPTION
This module provides an overview of transaction processing within accounting
information systems. It defines transaction cycles (expenditure, conversion, and
revenue) and the types of files (master, transaction, reference, and archive) used in
computer-based systems to create an audit trail. It explains the flow of data through
these files, using the sales order process as an example. The module also differentiates
between batch and real-time processing, discussing their characteristics, resource use,
operational efficiency, and suitability for different tasks. The module further explores
data structures, including sequential and direct access files, and their implications for
processing methods. Finally, it examines a combined approach of batch processing with
real-time data collection to optimize operational efficiency.

Transaction processing is the backbone of any accounting information system, ensuring

that financial data is accurately captured, processed, and reported. As future accounting
professionals, mastering these concepts will empower you to make informed decisions,
enhance operational efficiency, and uphold the highest standards of accountability in
financial management.

B. LEARNING OUTCOMES/OBJECTIVES
PRIMARY: Design a hybrid transaction processing system that integrates both real-time
and batch processing methods to optimize operational efficiency and data accuracy
within a business process. This objective requires understanding the trade-offs
between efficiency and effectiveness when selecting a data processing mode and the
ability to design a system that leverages the strengths of each method. To be able to
achieve this objective, the student needs to first attain the enabling objectives as
described below.

SECONDARY (Enabling):
1. Explain and differentiate the different transaction cycles. The student should be
able to explain and differentiate between the expenditure, conversion, and revenue
cycles and how they process an entity's economic activity. Comprehend how these
cycles capture financial transactions and provide essential data for financial
statements.

2. Describe Data Flow among the different types of files. The student should be able
to illustrate how data is captured and moves from one file to another, ultimately
affecting the general ledger master file. Detail how this flow supports the generation
of financial statements.

3. Compare Batch and Real-Time Processing. The student should be able to explain
the characteristics, differences, advantages, and disadvantages of batch and real-
time processing. For instance, batch processing involves waiting for a certain
condition before processing transactions, while real-time processing handles each
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

transaction immediately. Understand the trade-offs between efficiency and

effectiveness when selecting a data processing mode.

4. Evaluate the Efficiency and Effectiveness of Hybrid Processes. The student should
be able to assess scenarios where combining batch and real-time processing can
optimize operational efficiency. Recognize that updating subsidiary accounts in
real-time while processing common records in the general ledger using batch
methods can improve efficiency.

C. PRE-TEST (NOT GRADED)

[Link]

D. LEARNING MATERIALS AND STUDY GUIDE

By following the Study Guide through the learning
materials and the accompanying assessment questions
and participating in the associated activities, including
the hands-on solving of a case study on business
process design and development, you will gain a comprehensive understanding of the
Transaction Processing System (TPS), which serves as the operational backbone of
modern Accounting Information Systems. You will master the three primary transaction
cycles—expenditure, conversion, and revenue—and learn how these cycles process the
majority of an entity's economic activity. You will develop the technical skill to
differentiate between various digital file types, including master, transaction, reference,
and archive files, while understanding the intricate flow of data from initial input through
to the final financial statements.

Furthermore, you will acquire the expertise to evaluate and apply different processing
methodologies, specifically batch and real-time processing, and determine the most
appropriate data structures and access methods—such as sequential or direct access—
to optimize organizational efficiency. Finally, you will learn to construct and navigate a
digital audit trail for tracing transactions and gain insights into designing sophisticated
coding schemes for the Chart of Accounts, ensuring data integrity and compliance with
modern regulatory frameworks.

STUDY GUIDE

A. Watch main lecture video: Transaction Processing

P a g e 2 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

LINK: [Link]
LENGTH: [Link]

TIMELINE TOPICS

[Link] Transaction Cycles

CHECK YOUR UNDERSTANDING

1. Describe the two components (physical and financial) of transactions within
the expenditure cycle.
2. Explain why the payroll system is often a separate subsystem within the
expenditure cycle.
3. How do the conversion cycle activities of manufacturing firms differ from
those in service or retail establishments?
4. Explain how Point-of-Sale (POS) systems handle cash transactions.

[Link] Types of Files

CHECK YOUR UNDERSTANDING

1. Describe the purpose and contents of master files in a computer-based
system. Provide an example.
2. Explain the role of transaction files in updating master files. How are
transaction files managed after processing?
3. What are reference files and how are they used in processing transactions?
Give an example of how a reference file might be used in a point-of-sale
system.
4. Discuss the function of archive files and their importance in maintaining an
audit trail. What kind of data is typically stored in archive files?
5. Explain the importance of understanding the relationship between different
file types (master, transaction, reference, and archive) in a computer-based
information system. How does this understanding aid in auditing?

[Link] Flow of Data and Audit Trail

CHECK YOUR UNDERSTANDING

1. Describe the flow of data in a computer-based system, starting from the initial
transaction to its digital representation. What role does the data-input stage
play in this process?
2. Explain how transactions are processed in a batch system. What happens to
transactions that are found to be in error during processing?
3. Discuss the role of master files and archive files in maintaining a digital audit
trail. How do these files contribute to the accuracy of financial records?
4. Describe the steps an auditor might take to evaluate the accuracy of accounts
receivable using a digital audit trail.
5. How do online selling systems, such as those used by Shopee and Lazada,
capture sales order information? Discuss the implications of such systems for
audit trails compared to traditional manual systems.

Batch and Real-time Processes

P a g e 3 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

[Link] Differences Between Batch and Real-Time Processes

CHECK YOUR UNDERSTANDING

1. What are the key differences between batch and real-time processing in terms
of information timeframe? Provide examples to illustrate these differences.
2. How do batch and real-time systems differ in terms of the organizational
resources they demand, such as programming costs, computer time, and user
training? How have advances in digital storage technology affected these cost
differentials?
3. Describe the concept of operational efficiency in the context of data
processing modes. How does batch processing improve operational efficiency
compared to real-time processing in systems that handle large volumes of
transactions?
4. Explain the trade-off between efficiency and effectiveness that a designer
must consider when selecting a data processing mode. Provide examples of
scenarios where real-time processing and batch processing would be the
logical choice.
5. How can batch and real-time processing be used in a single process? Provide
an example of a business process that might use a hybrid approach
combining both batch and real-time processing.

[Link] Data Structures

CHECK YOUR UNDERSTANDING

1. What are the two fundamental components of data structures, and how do
they influence transaction processing?
2. Describe sequential file structures. How are records arranged, and for which
file processing operations are they efficient?
3. Explain why sequential files are not efficient for locating only one or a few
records on a file. Provide an analogy to illustrate this inefficiency.
4. Describe direct access structures. How do they store data, and what is
essential for determining the disk address?
5. How does the direct access approach compare to accessing songs on a music
player like an iPod or Youtube Music? What are some examples of primary
keys used in direct access structures?

[Link] Batch Processing with Sequential Files

CHECK YOUR UNDERSTANDING

1. What is batch processing, and what are its advantages?
2. What are the key assumptions and conditions underlying sequential file
updates in batch processing?
3. Describe the keystroke process in batch processing. What internal controls
are implemented during this stage, and why are they important?
4. Explain the purpose and process of the edit run in batch processing. What
happens to error records, and how are batch totals adjusted?
5. Describe the update run and explain the steps with respect to updating both
the AR (Accounts Receivable) and inventory master files.

[Link] Batch Processing with Direct Access Files

P a g e 4 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

CHECK YOUR UNDERSTANDING

1. How does using direct access files simplify a system compared to sequential
files, and what are the two noteworthy changes that occur when shifting to
direct access files?
2. What are the three reasons why the logic for updating direct access files is
simpler than that used for sequential files?
3. Describe the general logic for updating direct access files.
4. Explain how a transaction record (T7) is processed in a direct access file
update.
5. What are the advantages of direct access file updates compared to sequential
file updates?

[Link] Hybrid Processes

CHECK YOUR UNDERSTANDING

1. How does batch processing with real-time data collection enhance
operational efficiency in sales order systems?
2. Describe the steps involved in a sales order process that uses batch
processing with real-time data collection.
3. Explain why updating the sales journal and general ledger accounts is done in
batch mode rather than real-time, even when subsidiary accounts are updated
in real-time.
4. What are the implications of data-locking on system users when processing
customer transactions in real-time, and how does batch processing address
these issues?
5. What are the potential benefits of real-time processing in a sales order system,
and under what conditions is real-time processing best suited?

B. Read the research article: Transaction Processing in Modern Accounting

Information Systems

P a g e 5 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

LINK: [Link]
hosz7_0OCCS9jLjnCTcCf/view?usp=sharing
PAGES: 19, excluding references

CHECK YOUR UNDERSTANDING

1. What are the four core, non-negotiable characteristics of a robust Transaction
Processing System (TPS) in the modern era?
2. Differentiate between a Master File and a Transaction File in an Accounting
Information System (AIS), providing a clear example of each.
3. Define a "digital audit trail" and explain its fundamental importance in modern,
computerized accounting systems.
4. How is blockchain technology changing the nature of the audit trail and the
focus of the auditing profession?
5. According to the revised ISA 315 standard, what new responsibility must
auditors undertake regarding an organization's IT environment?

C. Read the research article: The Architecture of Financial Taxonomy

LINK: [Link]
nsBNZgVHey42BJbz/view?usp=sharing
PAGES: 24, excluding references

CHECK YOUR UNDERSTANDING

1. What is the primary difference between a "Thick" General Ledger and a "Thin"
General Ledger, particularly regarding how they handle business attributes like
location and department?
2. Explain the "Gap Principle" in block coding and why it is considered a critical
best practice for designing a scalable Chart of Accounts.
3. Define hierarchical coding and explain how it facilitates multi-level financial
analysis like "drilling down" and "rolling up."
4. What is the "combinatorial explosion" problem associated with legacy
segmented coding schemes in large organizations?
5. How is the role of the account code changing in modern user interfaces, and
what impact does this have on coding scheme selection?

P a g e 6 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

E. LEARNINGS SUMMARY
Every organization, whether large or small, relies on a well-structured system to process
financial transactions efficiently. In this module, you have explored the fundamentals of
transaction processing—how financial data moves through an accounting information
system, ensuring accuracy, security, and efficiency. From capturing raw data to updating
records and generating financial statements, every step in the process plays a crucial
role in maintaining an organization’s financial integrity.

Watch the summary video: Transaction Processing (Summary)

LINK: [Link]
LENGTH: [Link]

Here is a synthesized summary of lessons:

This module synthesizes key principles governing modern Accounting Information

Systems (AIS), focusing on the architecture of transaction processing, data
organization, and the strategic design of the Chart of Accounts (COA). The analysis
reveals a fundamental shift from rigid, linear data structures to agile, dimensional
models, driven by technological advancements and evolving regulatory demands.
P a g e 7 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

The Transaction Processing System (TPS) serves as the operational backbone of any
AIS, managing the flow of economic activity through three primary cycles: Expenditure,
Conversion, and Revenue. The integrity of these cycles is maintained through a
structured data hierarchy comprising Master, Transaction, Reference, and Archive files,
which collectively form the digital audit trail.

A core strategic element is the COA coding scheme, which has evolved from simple
Sequential and Block codes to complex Hierarchical structures. Modern cloud-based
ERPs have ushered in a paradigm shift from "Thick" General Ledgers, which suffer from
combinatorial complexity, to "Thin" General Ledgers that utilize flexible, dimensional
tagging. This evolution is mirrored in data processing methodologies, where a trade-off
exists between the operational efficiency of Batch Processing and the informational
immediacy of Real-Time Processing, with hybrid systems offering a pragmatic balance.

Finally, the concept of the audit trail is being redefined by immutable ledger technologies
like blockchain, enabling Continuous Auditing and ensuring data integrity. This
technological evolution aligns with revised regulatory frameworks such as ISA 315 and
COSO, which place greater emphasis on understanding and controlling the IT
environment and its associated risks.

1. The Foundation of Accounting Information Systems

An Accounting Information System (AIS) is the central nervous system of an
organization, with the Transaction Processing System (TPS) acting as its operational
backbone. The TPS is a specialized system designed to support daily operations by
capturing, processing, and storing data from economic events. Its core purpose is to
provide a "fast and accurate execution environment" that ensures data availability,
security, and integrity.

The intellectual scaffolding of the AIS is the Chart of Accounts (COA), a classification
system that maps distinct economic events to standardized financial concepts
(accounts). The COA functions as the primary index of the General Ledger (GL) and is
best understood as the "grammar of business"—it provides the syntax that structures
transactional vocabulary into coherent financial reports.
P a g e 8 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

1.1 Core Characteristics of a Modern TPS

A robust and effective Transaction Processing System exhibits several non-negotiable
characteristics:
• Rapid Response: In client-facing environments, processing must occur in sub-
second timeframes to maintain operational continuity and customer satisfaction.
• Reliability and Availability: As TPSs support critical operations, they must
incorporate robust backup, disaster recovery, and failover mechanisms to prevent
disruptions.
• Inflexibility and Standardization: A TPS must be rigid, processing identical
transactions in a standardized manner to ensure consistency, auditability, and error
prevention. Business logic, such as tax calculations or credit checks, must be applied
identically regardless of when or by whom a transaction is processed.
• Controlled Processing: Data handling must align with the firm's authorization
hierarchies to preserve data integrity, ensuring only authorized personnel can initiate
specific transactions.

2. Core Transaction Cycles

To manage the high volume of economic activity, AIS groups similar events into three
primary transaction cycles. These cycles exist in all businesses, whether for-profit or
non-profit, and represent the repetitive flow of activities that characterize the enterprise.

2.1 The Expenditure Cycle

The expenditure cycle encompasses the acquisition of resources—such as labor,
materials, and fixed assets—and the subsequent cash disbursements to pay for them.
Business activities typically begin with this cycle. Most expenditure transactions are
credit-based, creating a time lag between the physical acquisition of goods/services
and the financial component of payment.

• Purchasing/Accounts Payable System: This subsystem recognizes the need for

inventory, places an order with a vendor, and records the event by increasing
inventory and establishing an account payable upon receipt of goods. A critical
internal control is the separation of the purchasing and receiving functions.

P a g e 9 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

• Cash Disbursement System: When the obligation is due, this system authorizes
payment, disburses funds, and records the transaction by reducing cash and
accounts payable.
• Payroll System: A specialized purchasing system for labor. It collects usage data,
computes payroll, and disburses funds. Due to its complexity and fraud risk, it is
typically a separate system.
• Fixed Assets System: Processes non-routine transactions related to the acquisition,
maintenance, depreciation, and disposal of long-term assets like property, plant, and
equipment.

2.2 The Conversion Cycle

The conversion cycle transforms input resources into finished goods or services. While
most formal in manufacturing firms, service and retail businesses also engage in
conversion activities, such as repackaging merchandise or allocating prepaid expenses.

• Production System: This subsystem involves the planning, scheduling, and control
of the physical product through the manufacturing process. It determines raw
material needs and authorizes their release into production.

P a g e 10 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

• Cost Accounting System: This informational system monitors the flow of cost
information related to production. The data is used for inventory valuation,
budgeting, cost control, and management decisions.

2.3 The Revenue Cycle

The revenue cycle involves selling goods or services to customers and collecting cash.
Like the expenditure cycle, it often has a physical component (shipping goods) and a
financial component (receiving cash) that are processed separately.

• Sales Order Processing System: Manages credit sales, which includes preparing
sales orders, granting credit, shipping products, billing customers, and recording the
transaction in accounts like accounts receivable, inventory, and sales.
• Cash Receipts System: Processes payments from customers. This includes
collecting and depositing cash and updating the accounts receivable and cash
accounts. In point-of-sale (POS) systems, the lag time between sale and cash receipt
is very short, and subsidiary accounts receivable are often not maintained.

3. The Architecture of Financial Data

The vast amount of data generated by transaction cycles is organized and stored in a
structured hierarchy. Understanding this architecture is crucial for system design, data
flow analysis, and auditing.

3.1 Data File Hierarchy

In a computer-based AIS, accounting records are represented by four distinct types of
digital files that form the basis of the audit trail.

• Master Files: Contain permanent or semi-permanent data about an entity's core

items, analogous to a ledger. Data values are updated by transactions, but the record
itself persists. Examples include the General Ledger, Customer Subsidiary Ledger,
and Inventory Master File.
• Transaction Files: Temporary files containing records of economic events for a
specific period, analogous to a journal. These files are used to update master files
and are then typically archived. Examples include a sales order file or cash receipts
file.
P a g e 11 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

• Reference Files: Store data used as standards for processing transactions, such as
price lists, tax tables, or customer credit limits. The data is relatively permanent but
is updated periodically to reflect new business policies.
• Archive Files: Contain records of past transactions retained for future reference,
forming a critical part of the historical audit trail. Examples include prior-period
journals and ledgers.

3.2 Chart of Accounts Coding Schemes

Account coding is the process of assigning unique identifiers to financial concepts. The
choice of scheme is a strategic decision that impacts data integrity, reporting, and
operational efficiency. An effective coding system must be unique, expandable, simple,
brief, and facilitate sorting.

Traditional Coding Architectures

P a g e 12 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

Coding Description Best Use Pros Cons

Scheme Case
Assigning Transaction Simple, no gaps, No logical
Sequential
consecutive IDs, Invoices, detects missing grouping,
numbers as items POs items. inflexible for
are created (1, 2, insertions.
3...).
Reserving ranges SME Chart of Logical Finite ranges
Block
of numbers for Accounts grouping, allows can become
specific insertion via full, sub-
categories (e.g., gaps, standard. categories are
1000s for Assets). opaque.
Assigning Large Highly granular, Rigid, long
Hierarchical
meaning to corporations, allows for drill- strings, high
specific positions legacy ERPs down analysis. risk of data
within the code entry errors.
(e.g., 610-25-101
for Expense-Dept-
Item).
Using letters or Inventory Easy for humans Difficult to
Mnemonic
abbreviations that SKUs, to remember and sort logically,
resemble the item Subledgers recognize. prone to
(e.g., UTIL-ELEC). inconsistency.

The Modern Paradigm: "Thick" vs. "Thin" General Ledgers

Modern ERP systems have driven a shift away from complex, linear code strings toward
a more flexible, dimensional approach.

• "Thick" General Ledger: Found in legacy systems, this approach bakes every
business attribute (Company, Location, Department, Account) into a single, long
hierarchical code string. This leads to a "combinatorial explosion," creating a
massive, bloated COA that is difficult to maintain. Adding a new department may
require creating hundreds of new account code combinations.

P a g e 13 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

• "Thin" General Ledger: Championed by modern cloud ERPs, this architecture uses a
COA with only the "Natural Account" (e.g., 5000 - Travel Expense). All other attributes
are treated as separate "Dimensions" or "Tags" (e.g., Department: Sales, Location:
New York). This keeps the COA small and manageable. Adding a new department is
a simple, singular update, and reports can be flexibly "pivoted" by any dimension.

Thick Ledger (Segmented) Thin Ledger (Dimensional)

Feature
Single long string (01-100- Independent fields (Acct: 5000,
COA
5000) Loc: 100)
Structure
Huge (Thousands of strings) Small (Hundreds of accounts)
Chart Size
High effort (Combinatorial Low effort (Modular updates)
Maintenance
explosion)
Reporting Rigid (Defined by segment Flexible (Pivot by any dimension)
order)
Complex (Must know valid Intuitive (Select attributes
Data Entry
strings) separately)

4. Data Processing Methodologies and Structures

The timing of when transactions are processed defines the system's architecture,
involving a trade-off between efficiency and the currency of information.

4.1 Batch vs. Real-Time Processing

Feature Batch Processing Real-Time Processing (OLTP)

Data Delayed (Lag exists between Immediate (Instantaneous

event and update) update)
Availability
Transactions are accumulated Transactions are processed
Processing
and processed together at individually as they occur.
scheduled intervals.
Resource Efficient; can use off-peak Intensive; requires constant
computing time. system uptime.
Utilization
P a g e 14 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

Feature Batch Processing Real-Time Processing (OLTP)

Lower; can use less expensive Higher; requires high-
Cost
hardware. performance, high-availability
architecture.
High-volume, non-time-sensitive E-commerce, banking, airline
Ideal Use
tasks like payroll or monthly reservations, fraud detection.
Case
billing.

The choice between methods depends on user needs. When immediate access to
current information is critical, real-time is the logical choice. When time lags are
acceptable and operational efficiencies can be gained, batch processing is superior.

4.2 Hybrid Systems

Many systems employ a hybrid approach to balance efficiency and effectiveness. A
common configuration is to use real-time processing for updating unique subsidiary
records while using batch processing for common general ledger accounts. For
example, in a large department store, individual customer and inventory records
(subsidiary files) are updated in real-time as sales occur. However, the associated GL
control accounts (AR Control, Inventory Control, Sales) are updated in a batch at the end
of the day. This prevents operational bottlenecks that would occur if hundreds of
concurrent users were trying to lock and update the same few GL accounts
simultaneously.

4.3 Data Structures and Access Methods

The efficiency of processing is dictated by the underlying data structure.

• Sequential Structure: Records are stored in contiguous locations in a specified order

(e.g., by account number). To access a record, the system must read through all
preceding records. This structure is efficient for batch processing where a large
portion of the file is updated at once (e.g., payroll).
• Direct Access Structure: Records are stored at a unique address, allowing the system
to retrieve data immediately without reading other records. This is accomplished via
P a g e 15 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

indexing or hashing algorithms that translate a primary key into a storage address.
This structure is essential for real-time systems that require rapid, random access
to individual records.

5. The Evolving Audit Trail and Regulatory Landscape

In a computerized system, the paper audit trail is replaced by a digital one—a
chronological record of system activities that tracks who accessed what data, what
changes were made, and when. This digital trail is crucial for fraud prevention, regulatory
compliance, and system integrity.

5.1 The Shift to Immutable Ledgers

A key risk in traditional databases is that privileged users can alter or delete transaction
logs, compromising the audit trail. Modern technology is addressing this risk through a
shift toward immutable and append-only ledgers.

• Blockchain Integration: This technology

provides a distributed, cryptographically
secured ledger where transactions, once
recorded, cannot be altered without
breaking the chain of all subsequent
records. This creates a tamper-proof
history.
• Continuous Auditing (CA): Real-time data
flows combined with immutable logs
enable the use of automated software
agents to monitor transactions for
anomalies 24/7, shifting the audit
paradigm away from periodic, point-in-
time reviews toward constant verification.

5.2 Regulatory Drivers

P a g e 16 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

This technological evolution is reinforced by modern regulatory standards that demand

a deeper understanding of IT environments.

• ISA 315 (Revised): Places a greater burden on auditors to identify and assess risks
arising from the use of IT (RAUIT), requiring a thorough understanding of the TPS
architecture and its general IT controls.
• COSO Framework: Recent guidance explicitly links internal control effectiveness to
the management of cybersecurity risks and the governance of automated processes.
• IFRS Digital Reporting: The expansion of digital taxonomies (XBRL) to include
sustainability disclosures (IFRS S1 and S2) extends the scope of the TPS to capture
and report on non-financial ESG data points, further integrating technology with
compliance.

P a g e 17 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

F. POST-TEST (NOT GRADED)

[Link]

G. TEAM AND INDIVIDUAL ACTIVITY.

Will be conducted in-person and graded.

H. SUMMATIVE TEST
Will be conducted in-person and graded.

I. LEARNING OBJECTIVE ACTIVITY

1. Conduct a summary review discussion of the module
lessons, including a question-and-answer portion that doubles as team competition.
Questions are a mix of True or False, Identification and Multiple Choice with varying
points for each item. Teams compete to answer questions and earn the greatest
number of points. Individual points are also assigned to team members based on
their individual participation when called for by the instructor.

2. Case Study
BioTech Solution’s Hybrid Payroll Processing System
Scenario: BioTech Solutions is a medium-sized manufacturing company using a hybrid
payroll system that combines real-time data collection with periodic batch processing.
Employees clock in and out using a biometric time clock system, which captures their
attendance data in real time. However, the actual payroll processing—including
calculations for basic pay, overtime, deductions, and net payouts—is performed every 15
days using an Excel-based system. Payslips are then printed from the data in Excel.

Objective: To illustrate how real-time and batch processing components integrate within
a payroll system and to detail the manual and automated tasks involved in each phase.

Real-Time Component: Data Collection

Manual Tasks:
• Employees clock in and out using the biometric time clock.
• Supervisors verify any missed clock-ins or clock-outs and make necessary
corrections in the biometric system.

Automated Task:
• The biometric system automatically records employee attendance data in real-
time.
• The system stores the data in a digital format, ready for batch processing.
• Daily, the system generates a raw time record file that captures all clock-in and
clock-out activities and saves these files in a pooling folder share over the
network, ready for collection by the payroll department.

Batch Component: Payroll Processing (Every 15 Days)

1. Data Extraction (Automated): The payroll administrator downloads the daily time
record from the biometric machine.

2. Data Consolidation: All daily files from the past 15 days are consolidated into a single
data set for processing.

P a g e 18 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

3. Data Calculation (Automated/Manual):

• The consolidated data is imported into an Excel program.
• Excel formulas automatically calculate basic pay, overtime, and gross pay based
on the hours worked.
• Payroll administrator manually inputs data related to deductions, such as:
o Taxes (income tax, social security contributions).
o Insurance premiums.
o Loan repayments.
o Other authorized deductions.
• Excel automatically calculates total deductions and net payouts.

3. Review and Validation (Manual):

• The payroll administrator reviews the calculated payroll data for accuracy.
• Compares the payroll register against source documents and employee records.
• Verifies control totals to ensure no data is lost or incorrectly processed.
• Any discrepancies or errors are identified and corrected manually in the Excel
sheet.

4. Payslip Generation (Automated): The Excel program uses the payroll data to
automatically generate individual payslips.

5. Disbursement and Reporting (Manual/Automated):

o Payslips are printed and distributed to employees.
o Net payouts are disbursed to employees through direct deposits in the
employee’s bank accounts.
o Payroll reports (e.g., payroll journal, tax reports) are generated from
Excel for record-keeping and compliance purposes.

Internal Controls: To ensure data accuracy, operational efficiency, and compliance, the
following internal controls are implemented:

• Data Validation:
o Biometric system validates employee identity at clock-in and clock-out.
o Excel formulas include checks to ensure hours worked do not exceed
maximum limits and pay rates are within acceptable ranges.

• Segregation of Duties: Different personnel handle timekeeping, payroll

processing, and disbursement to prevent fraud and errors.

• Control Totals: The payroll administrator calculates control totals before and
after each processing run to ensure all records are processed correctly.

• Reconciliation: Payroll data is reconciled with bank statements and general

ledger accounts to verify accuracy.

• Regular Audits: Internal audits are conducted periodically to review payroll

processes and ensure compliance with policies and regulations.

Requirements:
P a g e 19 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

1. Prepare a system flow chart illustrating the process, clearly differentiating the
manual and automated tasks of the real-time data collection component of the
payroll system. This should include how:
• employees clock in and out using the biometric time clock
• supervisors verify missed clock-ins or clock-outs and make corrections (BioTech
Solution’s policy is for the employee to submit a written request for correction
reviewed and approved by the supervisor and the corrections are made by an IT
personnel in charge of the data from the biometrics machines via a correcting
clock-ins and outs menu on the backend application.
• the biometric system automatically records and stores employee attendance
data in real-time
• the system generates a raw time record file daily

Clearly differentiate the manual and automated tasks of the batch payroll processing
component (performed every 15 days). This should include how:
• the payroll administrator downloads the daily time record from the biometric
machine and consolidates the files
• the consolidated data is imported into an Excel program
• Excel formulas automatically calculate basic pay, overtime, and gross pay
• the payroll administrator manually inputs data related to deductions (taxes,
insurance, loan repayments, etc.)
• Excel automatically calculates total deductions and net payouts
• the payroll administrator reviews the calculated payroll data for accuracy and
verifies control totals
• any discrepancies or errors are identified and corrected manually in the Excel
sheet
• the Excel program generates individual payslips
• pay slips are printed and distributed, and net payouts are disbursed
• payroll reports are generated for record-keeping and compliance

2. In one paragraph each, describe the internal controls implemented to ensure data
accuracy, operational efficiency, and compliance. This should include:
• Data validation methods in the biometric system and Excel formulas
• Segregation of duties among personnel
• Use of control totals before and after each processing run
• Reconciliation processes with bank statements and general ledger accounts
• Regular internal audits

Submission Requirements:
The system flowchart, as a visual representation of the information system.
The submission must be in a digital format, such as a PowerPoint, Word or PDF
document.

Evaluation Criteria:
30% Accuracy in identifying and classifying resources, events, and agents.

P a g e 20 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

30% Clarity and logical flow in the design of the REA flowchart.
30% Effectiveness in depicting the interactions between resources, events, and agents.
10% Professional presentation and adherence to submission guidelines.
By completing this case study, you will gain hands-on experience in designing business
processes and relational-database information system using the REA model,
underscoring the critical role of accountants in system design and internal control. You
will also see how a properly designed system will pave the way for a smooth transition
into an integrated AIS.
Deadline: To be announced in class.

J. GLOSSARY OF KEY TERMS

TERM DEFINITION

Access Method The technique used to locate records and to navigate

through a database or file. The two primary methods are
Sequential and Direct.

Archive File A digital file containing records of past transactions

retained for future reference and forming an important
part of the audit trail. It is the digital equivalent of a
journal in a manual system.

Audit Trail The path that allows a transaction to be traced through

a data processing system from point of origin to final
output or backward from output to origin. In digital
systems, this consists of logs, references, and metadata.

Batch Processing A processing method where similar transactions are

accumulated over a period and then processed together
as a single group or "batch."

Block Coding A coding scheme that reserves specific ranges (blocks)

of numbers for specific categories of data, such as
1000-1999 for Assets.

Chart of Accounts (COA) The central classification system of a General Ledger

that maps distinct economic events to standardized
financial concepts (accounts). It acts as the primary
index and "grammar" for a business's financial data.

Conversion Cycle The transaction cycle composed of the production and

cost accounting subsystems, which involves the
planning, scheduling, and control of the physical product
through the manufacturing process and monitoring the
related cost information.

P a g e 21 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

TERM DEFINITION

Direct Access Structure A data structure where records are stored at a unique
location (address) on a storage device, allowing them to
be retrieved immediately without searching through
other records. Essential for real-time systems.

Dimensional Accounting The modern approach used in a "Thin" General Ledger

where the natural account is kept separate from other
business attributes (e.g., department, location, project),
which are treated as "dimensions" or "tags."

Edit Run A process in batch processing that identifies and

removes clerical errors from the transaction file,
ensuring data accuracy before further processing.

Expenditure Cycle The transaction cycle involving the acquisition of

resources (labor, materials, property) in exchange for
cash. It includes subsystems for purchasing, cash
disbursements, payroll, and fixed assets.

Financial Transaction An economic event that affects the assets and equities
of an entity, is reflected in its accounts, and is measured
in monetary terms.

Hierarchical Coding A coding scheme that assigns specific meaning to

specific positions or subgroups within a code, allowing
for "drill down" analysis. It often embeds the
organizational structure into the account code.

Master File A main file containing relatively permanent data about

an entity's core items, such as customers, inventory, or
employees. Data values are updated by transactions, but
the record itself persists.

Mnemonic Coding A coding scheme that uses alphabetic characters or

abbreviations to create codes that are easy for humans
to remember (e.g., TEL for Telephone Expense).

Plan Comptable Général The highly standardized, state-mandated Chart of

(PCG) Accounts used in France, which employs a strict
decimal-based classification system to ensure
uniformity across all businesses.

Real-Time Processing A processing method that handles transactions

individually as they occur, providing immediate feedback
and updates to master files. Also known as Online
Transaction Processing (OLTP).

Reference File A file that stores relatively permanent data used as

standards for processing transactions, such as tax
tables, price lists, or customer credit limits.

P a g e 22 | 43
AE112 ACCOUNTING INFORMATION SYSTEMS: Transaction Processing Module

TERM DEFINITION

Revenue Cycle The transaction cycle involving the processing of cash

sales and credit sales, and the subsequent receipt of
cash. It includes the sales order processing and cash
receipts subsystems.

Sequential Coding The simplest coding scheme, where consecutive

numbers are assigned to items as they are created (e.g.,
1, 2, 3). It is primarily used for transaction numbers like
invoices or checks.

Sequential File Structure A data structure where records are stored in contiguous
locations in a specified sequence (e.g., by primary key).
Accessing a record requires starting from the beginning
of the file.

Sort Run A process in batch processing that arranges the

transaction file in the same sequence as the master file
before updating, ensuring efficient processing.

Standardkontenrahmen Dominant industry-standard Chart of Accounts

(SKR) frameworks in Germany. SKR 03 is based on the
business process lifecycle, while SKR 04 is based on the
structure of financial statements.

"Thick" General Ledger A legacy Chart of Accounts structure where every

possible permutation of business attributes is combined
into a single, long, linear account code string, leading to
a massive and unwieldy COA.

"Thin" General Ledger A modern Chart of Accounts structure that contains only
natural accounts, while other business attributes are
handled as separate dimensions. This results in a small,
manageable, and flexible COA.

Transaction File A temporary file of transaction records used to change

or update data in a master file. It is typically re-initialized
after processing.

Transaction Processing A specialized information system designed to support

System (TPS) daily business operations by capturing, processing, and
storing data from economic events. It is the operational
backbone of the AIS.

Update Run A process in batch processing that modifies the values

of records in the master file to reflect the effects of
financial transactions.

- end of module -

P a g e 23 | 43