II Overview of Transaction Processing
II Overview of Transaction Processing
INTRODUCTION TO
TRANSACTION PROCESSING
Rhodilet B. Valdez, CPA
TRANSACTION
PROCESSING
• It is an activity composed of three
major subsystems: Revenue, expenditure,
and conversion.
• Even though each cycle performs
different specific tasks and supports
different objectives, each shares
common goals and objectives:
• Capture financial transactions
• Record the effect of transactions
in accounting records
• Provide information about
transactions to users in support
of day-to-day activities.
1
17/02/2025
TRANSACTION PROCESSING
SYSTEM (TPS)
Expenditure Cycle
• Business activities begin with
acquiring materials and property in
exchange for cash.
• Most B2B transactions are based on a
credit relationship between trading
parties (actual cash disbursement
occurs at some point after the receipt
of goods/services).
• From a system’s perspective, a
separate subsystem processes each
component:
• Physical component (acquisition of goods,
fixed asset, and labor incurrence)
• Financial component (cash
disbursements)
2
17/02/2025
Conversion
Cycle
• Manufacturing firms convert raw
materials into finished products
through formal, physical, observable
conversion cycle operations.
• Production system – planning,
scheduling, and control of
physical products through the
manufacturing system.
• Cost accounting – monitors the flow of
cost information including labor,
material, and overhead into
production.
Revenue
Cycle
• Firms sell their goods and
services to customers through
a revenue cycle.
• Physical component (Sales order
processing)
• Financial component (Cash
receipts)
3
17/02/2025
Labor
Customers
Finished goods
Materials
Cash
Cash
Plant
EXPENDITURE CYCLE
CONVERSION CYCLE REVENUE CYCLE
Subsystems:
Subsystems: Subsystems:
Purchasing/Accounts Payable
Production Planning and Control Sales Order Processing
Cash Disbursements
Cost Accounting Cash Receipts
Fixed Assets
Finished
Goods
Cash
Accounting Records
Manual (Traditional) Systems
4
17/02/2025
Accounting Records
Manual (Traditional) Systems
Accounting Records
Manual (Traditional) Systems
• Journal – a chronological record of financial
transactions. The primary source of data
entry into journals is documents.
• Each transaction results in a separate
journal entry, which identifies the accounts
affected and the amounts to be credited and
debited.
• Special journals – used to record specific
classes of transactions that occur in
high volume. Such transactions can be
grouped and processed more efficiently.
• Special journals use a specialized
format of recording.
• Register – often used to denote certain
types of special journals. Can also be
used to denote a log.
10
5
17/02/2025
Accounting Records
Manual (Traditional) Systems
11
Accounting Records
Manual (Traditional) Systems
12
6
17/02/2025
Accounting Records
Manual (Traditional) Systems
13
Accounting Records
Manual (Traditional) Systems
14
7
17/02/2025
Periodically reconciles
subsidiary ledger to general
ledger
AR Subsidiary
ledger
15
Audit Trail
• Accounting records provide audit trail. It
provides utmost importance in the conduct
of financial audit.
• Tracing
– from economic events to source
documents to financial statements.
• Vouching – from financial statements back to
source documents and economic events
that created them.
• Accountants and auditors should be able to
trace in both directions.
16
8
17/02/2025
Accounting Records
Automated (Computerized) Systems
• Master File - generally contains
account data (e.g., general ledger
and subsidiary file)
• Transaction File - a temporary file
containing transactions since the
last update.
• Reference File - contains relatively
constant information used in
processing (e.g., tax tables,
customer addresses)
• Archive File - contains past
transactions that are retained for
future reference and form an
important part of the audit trail.
17
Digital Audit
Trail
The audit trail is less
observable in computer-based
systems than in traditional
manual systems.
18
9
17/02/2025
FILE
STRUCTURE
FLAT-FILE MODEL
Often associated with so-called
legacy (large mainframe) systems.
Serves as an environment where
end-users own their data files
rather than share them with other
users.
Stand-alone applications rather
than integrated systems perform
data processing.
19
DATA REDUNDANCY
Dilemma with Flat-File Model
DATA CAPTURE AND STORAGE
Problem with efficiency
Data should be captured only once
Incur additional cost of both multiple collection
and multiple storage procedures.
DATA UPDATING
Multiple data updates to reflect changes
Add significant rework and cost of data
management
CURRENCY OF INFORMATION
If updated information is not properly
disseminated, changes will not be reflected in
some user’s data, resulting in actions and
decisions based on outdated information.
20
10
17/02/2025
DATA REDUNDANCY
Dilemma with Flat-File Model
TASK-DATA DEPENDENCY
User’s inability to obtain additional information as
his or her needs change.
New information needs tend to be satisfied by
procuring new data files.
DATA INTEGRATION LIMIT
Flat-file approach is a single-user view model.
Files are structured, formatted, and arranged to
suit the specific needs of the owner or primary
user of the data.
Such structuring, prevents the successful
integration of data across the organization.
21
FILE STRUCTURE
DATABASE MODEL
An approach that centralizes the
organization’s data into a common
database that is shared by other
users.
Data are stored in the most granular
format rather than being shaped and
configured to the needs of any single
user.
Pooling of data into a common
database that all organizational user
share.
22
11
17/02/2025
TRUE OR FALSE
The salient point of using
the database model is
having a centralized and
common storage of data
for all users. This means
that all users can access
freely on all the data.
23
DOCUMENTATION TECHNIQUES
“A picture is worth a thousand words”
24
12
17/02/2025
DOCUMENTATION
TECHNIQUES
DATA FLOW DIAGRAM
Use symbols to represent the
processes, data resources, data
flows, and entities in a system.
Represent the logical elements of the
system and not depict the physical
system.
In other words, show what logical
tasks are being performed but not
how they are performed or who
(what) is performing them.
25
DOCUMENTATION
TECHNIQUES
26
13
17/02/2025
Cardinalities
• Represents the numerical
mapping between entities.
• One-to-one
• One-to-many
• Many-to-many
27
DOCUMENTATION
TECHNIQUES
SYSTEM FLOWCHARTS
A graphical representation of the
physical relationships among key
elements of a system.
Flowcharting is much an art form as
it is a technical skill, giving the author
great deal of license.
Primary objective: provide an
unambiguous description of the
system.
28
14
17/02/2025
DOCUMENTATION
TECHNIQUES
PROGRAM FLOWCHARTS
Provide operational details and the
correctness of the edit program logic.
Every program presented in a
flowchart should have a supporting
program flowchart that describes its
logic.
29
Transaction
Processing
Models
• Batch processing is the
gathering of transactions
into groups or batches
then processing the entire
batch as a single event.
• Real-time processing systems
process individual
transactions continuously
as they occur.
30
15
17/02/2025
31
16