not-for-profit organizations.

A
CHAPTER 6: Transaction
diagram.
Processing and
Financial Reporting
Expenditure Cycle Overview
Systems Overview
The expenditure cycle involves
Overview acquiring resources—materials,
property, and labor—in exchange for
Financial Transaction: cash. It consists of two main
components:
• Economic events
• Affects assets and Liabilities • Physical component: Receiving
= Equities goods or services.
• Monetary in nature
• Financial component: Paying
- This can be internal or external. for those goods/services
later.
Transaction Cycles Overview:
Most transactions are based on
Businesses operate through three credit, meaning payment occurs after
main transaction cycles that handle receipt.
most economic activities:

1. Expenditure Cycle – Involves

spending resources to acquire Key Subsystems of the Expenditure
goods or services. Cycle

2. Conversion Cycle – Transforms 1. Purchases/Accounts Payable

acquired resources into System
products or services that add
o Identifies the need for
value.
inventory.
3. Revenue Cycle – Generates
o Places orders with
income by selling products or
vendors.
services to external parties.
o Records receipt of goods
These cycles are interconnected and
by increasing inventory
apply to both profit-oriented and
and creating an account
payable.

2. Cash Disbursements System

o Handles payments when

obligations are due.

o Reduces cash and

accounts payable upon
payment.

3. Payroll System
 o Collects employee labor o Tracks and monitors
data. production-related
costs.
o Calculates and disburses
paychecks. o Provides data for:

o Treated as a specialized ▪ Inventory

purchases/cash valuation
disbursement system due
to its complexity. ▪ Budgeting

4. Fixed Asset System ▪ Cost control

o Manages acquisition, ▪ Performance

maintenance, and reporting
disposal of long-term
▪ Managerial
assets.
decisions (e.g.,
o Includes items like make-or-buy
land, buildings, analysis)
machinery, and vehicles.

Application in Different Business

Conversion Cycle Overview Types

The conversion cycle refers to the • Manufacturing Firms: Use

process of transforming raw formal conversion cycle
materials into finished goods or systems to produce physical
services. It consists of two main goods.
subsystems:
• Service/Retail Firms: Engage
in conversion activities
(e.g., preparing
Key Subsystems of the Conversion
services/products for sale,
Cycle
allocating expenses), but
1. Production System typically do not use formal
systems.
o Plans, schedules, and
controls the Revenue Cycle Overview
manufacturing process.
The revenue cycle involves selling
o Determines raw material goods or services and collecting
needs. payment. Like other cycles, it has
two components:
o Authorizes production
and releases materials. • Physical component: Delivering
goods or services.
o Manages the movement of
work-in-process through • Financial component: Receiving
manufacturing stages. and processing payment.
2. Cost Accounting System
Key Subsystems of the Revenue Cycle Accounting Records
1. Sales Order Processing Manual Systems
o Handles credit sales. Manual accounting systems use
o Tasks include: physical records to document and
process transactions. These include:
▪ Preparing sales
orders • Documents

▪ Granting credit • Journals

▪ Shipping goods or • Ledgers

delivering
This section focuses on documents,
services
which serve as evidence of economic
▪ Billing customers events and play roles in initiating
or resulting from transaction
▪ Recording processing.
transactions
(e.g., accounts
receivable,
Documents
inventory,
expenses, sales) 1. Source Documents

2. Cash Receipts o Created at the start of

a transaction.
o Manages incoming
payments from credit o Capture and formalize
sales. transaction data.

o Includes: o Example: A sales order

prepared by a clerk when
▪ Collecting cash
a sale occurs.
▪ Depositing funds o Used by departments like
▪ Recording the cash billing, shipping, and
receipt in accounts receivable
financial accounts (AR).

2. Product Documents

o Generated as a result of
transaction processing.

o Example: A payroll check

issued to an employee or
a customer bill from the
sales system.

3. Turnaround Documents

o Product documents from

one system that become
 source documents for 2. Registers
another.
o A type of special
o Example: A customer bill journal or log.
with a detachable
o Examples:
remittance advice.
▪ Receiving Register
▪ The remittance
– logs incoming
advice is returned
raw materials.
with payment and
helps the cash ▪ Shipping Register
receipts system – logs outgoing
match payments to shipments.
customer accounts.
3. General Journal
Journals
o Used for nonrecurring,
A journal is a chronological record infrequent, or unique
of transactions. Each entry reflects transactions.
the accounts affected and the amounts
to be debited and credited. Journals o Examples:
are primarily populated using data
▪ Depreciation
from documents, and they serve as the
entries
basis for posting to ledger accounts.
▪ Adjusting entries

Types of Journals ▪ Closing entries

1. Special Journals o Flexible format allows

any type of transaction.
o Used for high-volume,
recurring transactions. 4. Journal Voucher System

o More efficient than o Replaces the general

general journals. journal in many
organizations.
o Examples:
o A journal voucher is a
▪ Sales Journal – special source document
records sales with a single journal
transactions. entry.

▪ Cash Receipts o Used for:

Journal
▪ Summaries of
▪ Cash Disbursements routine
Journal transactions

▪ Purchases Journal ▪ Non-routine

transactions
▪ Payroll Journal
(often called a ▪ Adjusting and
Payroll Register) closing entries
Ledgers o Maintained by various
departments (e.g., AR,
While journals record transactions
Inventory, Payroll).
chronologically, ledgers organize
financial data by account type, o Used for daily
showing increases, decreases, and operations and internal
current balances. Ledgers are control.
essential for:
o The total of subsidiary
• Preparing financial statements ledger balances must
match the corresponding
• Supporting daily operations general ledger control
account.
• Generating internal reports

Reconciliation
Types of Ledgers
• Periodic reconciliation
1. General Ledger
between journals, subsidiary
o Contains summarized ledgers, and general ledger
control accounts (e.g., ensures:
Accounts Receivable,
o Accuracy
Accounts Payable,
Inventory). o Completeness
o Updated using journal o Detection of errors or
vouchers from special out-of-balance
journals and other conditions
sources.

o Used for financial

reporting. The Audit Trail

o Does not provide An audit trail is the path that

detailed operational traces a transaction from its origin
data (e.g., individual (source documents) through journals
customer balances). and ledgers, all the way to the
financial statements. It ensures
2. Subsidiary Ledger transparency, accuracy, and
accountability in financial
o Contains detailed
reporting.
account information that
supports control
accounts in the general
ledger. Purpose of the Audit Trail

o Examples: Customer • Supports year-end audits

balances in AR, vendor
details in AP, inventory • Validates financial statement
item records. accuracy

• Helps detect errors or fraud

 • Enables tracing and • Auditor forms an opinion on the
verification of transactions fairness and accuracy of the
financial statements.

• Similar procedures are applied

Audit Process Example: Accounts
to other major accounts.
Receivable (AR)

1. Start at the Financial

Statements Computer-Based Systems
o Auditor checks the AR Types of Files
figure on the balance
sheet. 1. Master File

2. Trace to General Ledger o Stores account data

(e.g., general ledger,
o Verifies the AR control subsidiary ledgers).
account balance.
o Updated by transactions.
3. Reconcile with Subsidiary
Ledger 2. Transaction File

o Ensures detailed o Temporary file

customer balances match containing transaction
the control account. records.

4. Sample Transactions o Used to update master

files.
o Auditor selects a subset
of customer accounts for o Examples: sales orders,
review. inventory receipts, cash
receipts.
5. Trace to Sales Journal
3. Reference File
o Identifies related sales
transactions. o Contains standard data
used during transaction
6. Verify Source Documents processing.
o Confirms the original o Examples: tax tables,
documents (e.g., sales price lists, supplier
orders) are valid and lists, employee rosters,
accurate. credit files.
7. Confirmation Procedure 4. Archive File
o Contacts customers to o Stores historical
confirm transaction transaction records for
details and balances. future reference.

o Examples: prior-period
journals, payroll
Outcome
records, written-off
accounts.
 2. Reconcile the control account
with the AR subsidiary ledger.
Digital Audit Trail Process
3. Sample entries from the
1. Capture the Economic Event
subsidiary ledger and trace
o Source documents (e.g., them to the archive file (sales
sales orders) are journal).
created manually or
4. Identify and verify original
digitally.
source documents.
2. Data Input
5. Confirm transactions with
o Source documents are customers if needed.
digitized and stored in
a transaction file.

3. Transaction Validation

o System checks for errors

(e.g., invalid accounts,
credit issues).

o Invalid records go to an
error file; valid ones
proceed.

4. Update Master Files

o Valid transactions
update relevant master
files (e.g., AR,
inventory).

5. Archive Valid Transactions

o Valid entries are copied

to the archive file
(e.g., digital sales
journal).

o Original transaction
file is erased for the
next batch.

Audit Trail Example: Verifying

Accounts Receivable (AR)

1. Compare AR balance on the

balance sheet with the AR
control account in the master
file.
Documentation Techniques o Show decision points,
loops, and processing
Why Use Visual Documentation? steps.

• Visuals are more effective 5. Record Layout Diagrams

than lengthy text
descriptions. o Describe the structure
of data records.
• Help accountants and auditors
o Useful for understanding
understand, design, and
file formats and data
evaluate systems.
organization.
• Essential for tracing
processes, identifying
controls, and improving Data Flow Diagrams (DFDs)
communication.
Purpose:
DFDs visually represent how data
moves through a system, focusing on
Five Basic Documentation Techniques
processes, data stores, flows, and
1. Data Flow Diagrams (DFDs) external entities.

o Show how data moves Key Elements:

through a system.
• Entities: External
o Focus on processes, data sources/destinations of data
stores, sources, and (e.g., Customer, Supplier).
destinations. Labeled as nouns.

2. Entity Relationship Diagrams • Processes: Actions performed

(ERDs) on data (e.g., Ship Goods,
Approve Sales). Labeled as
o Illustrate relationships
verbs.
between data entities.
• Data Stores: Represent
o Commonly used in
accounting records or files.
database design.

3. System Flowcharts • Data Flows: Arrows showing

movement of data between
o Depict the overall flow elements. Each flow must have
of data and processes in a unique label.
a system.
Levels of Detail:
o Include inputs, outputs,
files, and processing • Can range from general to
steps. highly detailed.

4. Program Flowcharts • Focus on logical tasks, not

physical implementation or
o Detail the logic of responsibilities.
individual programs.
Entity Relationship Diagrams (ERDs) System Flowcharts Overview

Purpose: A system flowchart is a visual

ERDs model the relationships between representation of the physical flow
entities in a system, often used in of processes, documents, and data
database design. across departments and systems. It
shows how manual and computer-based
Key Elements:
activities interact to complete a
• Entities: Represent resources, transaction.
events, or agents (e.g.,
Inventory, Vendor, Customer).
Key Elements Represented
• Relationships: Lines
connecting entities, labeled • Departments (e.g., Sales,
to describe the nature of the Credit, Warehouse, Shipping)
relationship.
• Manual activities (e.g.,
• Cardinality: Indicates how preparing documents, filing)
many instances of one entity
• Computer processes (e.g.,
relate to another:
updating files, validating
o 1:1 – One-to-one data)

o 1:M – One-to-many • Hard-copy records (e.g.,

journals, ledgers)
o M:M – Many-to-many

Example: • Digital files (e.g., master,

transaction, reference,
• A 1:1 relationship might show archive)
each salesperson assigned one
car. • Media types (e.g., magnetic
tape, disks, terminals)
• A M:M relationship might show
multiple vendors supplying the
same inventory item. Flowcharting Manual Activities

Example: Sales Order System

Relationship Between DFDs and ERDs 1. Sales Clerk receives a
customer order and prepares
• DFDs model processes and data
four copies of a sales order.
flow.
2. Credit Department approves the
• ERDs model data structure and order using hard-copy credit
relationships. records.
• They are connected through 3. Sales Clerk distributes copies
data: to the warehouse and shipping
departments.
o Each data store in a DFD
corresponds to a data 4. Warehouse Clerk picks goods
entity in an ERD. and updates stock records.
 5. Shipping Department attaches • Large batches reduce average
packing slip and ships goods. cost.

• Small batches make error

Flowcharting Conventions detection easier.

• Use correct symbols (e.g., • Optimal batch size depends on:

document, manual process, o Transaction volume
file, ledger).
o Error frequency
• Label all symbols and flow
lines clearly. o Financial risk of
undetected errors
• Use arrowheads to show
o Processing costs
direction and sequence.

• Represent physical areas as

vertical columns (e.g., Flowcharting Computer-Based Systems
departments).
Example: Sales Order System with
• Use on-page connectors (e.g., Manual and Computer Processes
circle labeled “A”) to reduce
Departments Involved:
clutter.
• Sales Department
• Focus on document flow, not
physical goods. • Computer Operations Department
• Show single transaction flow • Warehouse
for clarity, even though
systems process batches. • Shipping Department

Process Overview:

Batch Processing 1. Sales Clerk enters customer

order via terminal (manual
Definition:
input → digital system).
Batch processing involves collecting
similar transactions (e.g., sales 2. Computer Program:
orders) and processing them together
as a group. o Edits transactions

Advantages: o Checks credit via

reference file
1. Efficiency: Reduces cost by
processing many transactions o Creates transaction file
at once. 3. Update Program:
2. Control: Errors can be o Posts to AR and
detected by comparing batch inventory master files
totals at different stages.
o Generates 3 hard copies
Design Considerations: of the sales order
 4. Warehouse Clerk: computer program. Unlike system
flowcharts, which show how programs
o Uses PC to update stock
interact with files and departments,
records
program flowcharts focus on how a
o Sends goods and Copy 1 to specific program works internally.
shipping

5. Shipping Clerk:
Key Features
o Reconciles goods with
• Each symbol represents a step
documents
in the program’s logic.
o Ships goods with packing
slip • Connector lines show the
sequence of operations.
o Updates shipping log and
files documents • Each symbol corresponds to one
or more lines of actual code.
Flowcharting Tips:
• Used by auditors and system
• Use correct symbols (e.g., designers to verify program
terminal, process, file, correctness and logic.
document).

• Show physical layout

(departments as vertical
columns).

• Use arrowheads to indicate

Example: Edit Program Logic
flow direction.
1. Start the program.
• Represent document flow, not
physical goods. 2. Retrieve a record from the
unedited transaction file.
• Use on-page connectors to
reduce clutter. 3. Check for EOF (End-of-File):

• Focus on single transaction o If yes → terminate and

flow for clarity. pass control to the next
program.

o If no → continue
processing.

4. Perform validation tests:

o Check for errors (e.g.,

alphabetic characters in
numeric fields).
Program Flowcharts Overview
5. Route records:
A program flowchart provides a
o Valid → edited
detailed visual representation of
transaction file.
the logic and operations within a
 o Invalid → error file. o Field name

6. Loop back to Step 2 until EOF o Data type (e.g.,

is reached. numeric, text)

o Field length (number of

characters or digits)
Use in Auditing
o Key fields (used for
• Auditors compare program indexing or
flowcharts to actual code to identification)
ensure:

o The program performs as

documented. Uses of Record Layout Diagrams

o Internal controls are • Debugging and analyzing system

properly implemented. errors

• Essential for IT audits and • Auditing data integrity and

error detection. structure

• Designing and testing program

logic

• Understanding how data is

stored and accessed

Simplified Layout Example

A basic record layout might look like

this:

Field Name Data Leng Descript

Type th ion
Record Layout Diagrams Overview Customer_I Numer 6 Unique
D ic customer
A record layout diagram visually
identifi
displays the internal structure of a
record within a file or database er
table. It helps accountants, Customer_N Text 30 Full
auditors, and system designers ame name of
understand how data is organized and customer
stored.
Order_Date Date 10 Date of
order
Key Features Order_Amou Numer 8 Total
nt ic amount
• Shows each attribute (field)
of the
in a record.
order
• Includes:
COMPUTER-BASED ACCOUNTING
SYSTEMS
Transaction Processing Models

System designers choose between

batch and real-time processing based
on operational needs, resource
availability, and timing
requirements.

Table 6.1 – Characteristic

Differences

Feature Batch Real-Time

Processing Processin
g

Informati Lag between Processin

on Time the g occurs
Frame economic at the
event and time of
its the
recording economic
event

Resources Requires Requires

Required fewer more
resources resources
(hardware, than batch
programmin processin
g, g
training)

Operation Some All

al records records
Efficienc processed processed
y after the immediate
event to ly as the
avoid event
delays occurs

Differences Between Batch and Real-

Time Systems:

1. Information Time Frame

• Batch Processing:
 o Transactions are grouped • Batch Processing:
and processed later.
o More efficient for high-
o Time lag exists between volume, non-critical
event occurrence and updates.
recording.
o Avoids unnecessary real-
o Example: Payroll time updates.
processed at the end of
a pay period. • Real-Time Processing:

• Real-Time Processing: o Can be less efficient

for large volumes due to
o Transactions are constant updates.
processed immediately as
they occur. o Necessary when immediate
access to current data
o No time lag. is critical.
o Example: Airline
reservation system.
4. Efficiency vs. Effectiveness
Trade-Off
2. Resources • Batch: Best when time delays
don’t impact performance and
• Batch Processing:
efficiency is prioritized.
o Requires fewer resources
(simpler programming, • Real-Time: Best when immediate
less training). data access is essential for
user decisions.
o Uses sequential files
(e.g., magnetic tape).

o Frees up computer Legacy Systems vs. Modern Systems

capacity after
Legacy Modern
processing. Feature
Systems Systems
• Real-Time Processing:
Client-
o Requires more resources Mainframe- server or
Platform
(complex programming, based network-
user-friendly based
interfaces).
Typically Often real-
o Uses direct access files Processing
batch- time (some
(e.g., magnetic disks). Mode
oriented use batch)
o Needs dedicated, often
Flat files,
24/7, processing Data hierarchical Relational
capacity.
Storage , or network databases
databases

3. Operational Efficiency
 Legacy Modern Backup Strategy:
Feature
Systems Systems
1. Before update: Copy the master
file to create a backup.
High
Limited;
Integratio integratio 2. If failure occurs:
single-user
n n and data
environment o Use backup to restore
sharing
pre-update state.

o Reapply the transaction

Updating Master Files from batch to reconstruct the
Transactions current state.

Process Steps: Why It Matters:

1. Read a sales order record. • Ensures data integrity and

recoverability.
2. Use ACCOUNT NUMBER to locate
and update the AR master • Critical for auditing and
record. error recovery.
3. Add INVOICE AMOUNT to CURRENT
BALANCE.
Batch Processing Using Real-Time
4. Use INVENTORY NUMBER to locate Data Collection
and update the inventory
master record. Overview

5. Subtract QUANTITY SOLD from This hybrid approach combines the

QUANTITY ON HAND. accuracy of real-time data capture
with the efficiency of batch
6. Repeat for the next sales processing. It’s especially useful
order. for large organizations handling
Keys Used: high transaction volumes.

• Primary Key: Uniquely

identifies each record (e.g., Process Flow Example: Department
SALES ORDER NUMBER). Store Sales System

• Secondary Keys: Used to locate 1. Real-Time Data Capture:

related records (e.g., ACCOUNT
NUMBER, INVENTORY NUMBER). o Sales clerk enters
customer and item data.

o System checks customer

Database Backup Procedures credit and updates AR
subsidiary record.
Destructive Update:
o Inventory levels are
• Updates overwrite the original updated immediately in
master file record. the inventory subsidiary
file.
• No backup of the previous value
is retained.
 o A sales order record is Real-Time Processing Overview
added to the transaction
Definition:
file.
Real-time systems process
2. Batch Processing: transactions immediately as they
occur, without delay or batching.
o At the end of the day,
the transaction file is
processed in batch mode.
Benefits of Real-Time Processing
o Updates are made to:
• Improved productivity
▪ Sales journal
• Reduced inventory levels
▪ General ledger
accounts (AR • Higher inventory turnover
control, inventory
control, sales, • Faster customer billing
COGS)
• Enhanced customer satisfaction

• Reduced reliance on physical

Why Not Update the General Ledger in documents
Real Time?

• Data Locking: When a record is

Best Use Cases
being updated, it’s locked to
prevent simultaneous access. • Systems with low transaction
volumes
• Unique Records (e.g., customer
accounts): Can be updated in • Systems where transactions
real time without conflict. don’t share common records

• Common Records (e.g., general • Environments using networked

ledger accounts): Used by all terminals (LAN/WAN) for
transactions, causing delays distributed data entry and
if updated in real time. processing

Operational Efficiency Challenge Technology Requirements

• Example: 500 terminals, each • Networked terminals across

transaction causes a 20-second departments
delay due to record locking.
• Digital transmission of
• Result: Last customer in queue transaction data
could wait 2¾ hours.
• Minimal physical documentation
• Solution: Update subsidiary
records in real time, but • Real-time communication
general ledger records in between users and systems
batch to avoid bottlenecks.
Transaction Processing System (TPS) DATA ENCODING SCHEMES
Controls
What Is Data Coding?
• Controls vary by:
Data coding involves using simple
o Application type (e.g., numerical or alphabetical codes to
sales vs. purchasing) represent complex economic data.
This enhances efficiency, accuracy,
o System type (manual,
and clarity in data processing.
batch, or real-time)

• All systems must ensure

authorization of material Why Coding Matters
transactions, but
Without coding:
implementation differs by
context. • Transactions require lengthy
descriptions.

• Increases risk of clerical

errors.

• Slows down data entry,

retrieval, and posting.

• Makes it harder to distinguish

between similar records (e.g.,
multiple customers named John
Smith).

Example: Inventory Without Codes

A machine shop wholesaler carries

nuts with:

• 96 sizes (¼ inch to 1¾ inch in

1/64 increments)

• 4 materials (brass, copper,

mild steel, case-hardened
steel)

• 3 thread types (fine,

standard, coarse)

This results in 1,152 unique items

(96 × 4 × 3). Without codes, each
item must be described in full, e.g.:

Inventory—nut, ½ inch, case-hardened

steel, standard thread
This is inefficient and error-prone Benefits of Data Coding in AIS
across:
1. Efficient Representation
• Sales staff: Difficult and
o Simplifies complex data
slow to record items.
for easier processing
• Warehouse: Hard to locate and and storage.
pick items accurately. 2. Accountability
• Accounting: Slow ledger o Ensures completeness and
posting and high error risk. traceability of
transactions.

3. Unique Identification
With Coding
o Distinguishes individual
Each item can be assigned a unique
transactions and
code (e.g., N-048-CS-ST), making:
accounts.
• Data entry faster
4. Audit Support
• File searches more efficient o Enhances the audit trail
for verification and
• Error detection easier
control.
• System integration smoother
1. Sequential Codes
A System with Codes
Definition:
Using codes (e.g., numeric or Codes assigned in a strict numeric or
alphanumeric identifiers) simplifies alphabetic sequence (e.g., 001, 002,
transaction processing by replacing 003...).
lengthy descriptions with concise
Common Use:
references.
• Prenumbering source documents
Example: Instead of:
(e.g., invoices, checks)
Inventory—nut, ½ inch, case-hardened
steel, standard thread • Tracking transaction flow
AP—Industrial Parts Manufacturer, Advantages:
Cleveland, Ohio
• Easy to detect missing or out-
Use:
of-sequence transactions
Account DR CR
• Supports batch reconciliation
and audit trails
896 1,000
Disadvantages:
321 1,000
• No descriptive information in
• 896 = Inventory item code the code

• 321 = Supplier code • Difficult to insert new items

without renumbering
 • Supports detailed analysis
across multiple dimensions
2. Block Codes

Definition: • Easier to remember and

Codes grouped into blocks where each interpret than sequential
block represents a category or class codes
(e.g., 100–199 for assets, 600–699 Disadvantages:
for expenses).
• Can become overly complex if
Common Use:
overused
• Chart of accounts
• May link unrelated data,
• Categorizing financial data increasing errors and storage
costs
Advantages:

• Easier to insert new items

4. Alphabetic Codes
within a block
Definition:
• Supports logical grouping of
Uses letters (or alphanumeric
data
combinations) to represent data.
Disadvantages:
Advantages:
• Limited descriptive meaning
• Greatly expands coding
unless referenced against a
capacity (e.g., 26 blocks × 676
chart
items = 17,576 items)
• Still lacks detailed attribute
• Useful for categorization and
information
flexible grouping
3. Group Codes
Disadvantages:
Definition:
• Hard to interpret without a
Codes divided into zones or fields,
reference
each representing a specific
attribute. • Sorting alphabetically can be
Example: less intuitive for users
04-09-476214-99

• Store 04 = Hamilton Mall 5. Mnemonic Codes

• Dept 09 = Sporting Goods Definition:

Uses meaningful abbreviations or
• Item 476214 = Hockey Stick acronyms to represent data.
• Salesperson 99 = Jon Innes Examples:
Advantages: • Acctg 101 = Accounting course
• Represents complex, • NY, CA, OK = State codes
hierarchical data
Advantages:
 • Self-explanatory and easy to The General Ledger System
remember (GLS)
• Reduces need for external Overview of GLS
references
The General Ledger System acts as a
Disadvantages: central hub that connects various
subsystems of the organization,
• Limited capacity for
including:
individual item representation
• Transaction Processing Systems
• Best suited for classes, not
(TPS): Provide summarized data
detailed records
from special journals and
subsidiary ledgers.

• Financial Reporting System

(FRS): Uses GLS data to
generate financial statements.

• Management Reporting System

(MRS): Uses GLS data for
internal decision-making and
performance reporting.

Key Components of GLS

1. Journal Voucher

• Primary input to the GLS.

• Represents either:

o Summaries of routine
transactions

o Adjusting entries

o Closing entries

• Requires managerial approval,

adding a layer of control.

2. GLS Database Files

File Name Purpose

Contains current
balances for each GL
GL Master File account; based on
the chart of
accounts.
File Name Purpose The Financial Reporting System

Purpose of the FRS

Stores historical
financial data for • The FRS fulfills legal
GL History File
comparative obligations for management to
reporting. report financial stewardship
to external parties.
Collection of all
Journal Voucher
journal vouchers for • It includes standard financial
File
the current period. statements, tax returns, and
regulatory documents (e.g.,
Archive of past
for the SEC).
Journal Voucher journal vouchers;
History supports audit trail Users of Financial Reports
and accountability.
• Primary users: External
Tracks revenues, stakeholders like
Responsibility expenses, and stockholders, creditors, and
Center File resource usage by government agencies.
department or unit.
• These users need:
Stores budgeted
o Performance trends over
figures for
Budget Master time.
comparison and
File
performance o Comparisons across
evaluation. organizations.

• Reports are designed for a

general audience assumed to be
Information Flow
sophisticated and familiar
• Inbound: Summarized with accounting principles.
transactions from TPS → GLS Financial Reporting Process
• Outbound: The FRS is the final stage of the
accounting cycle, typically done
o GLS → FRS (for external
periodically (batch process), though
reporting)
some organizations use real-time
o GLS → MRS (for internal systems. The steps are:
reporting)
1. Start of Fiscal Year: Carry
• Feedback Loop: FRS may send forward only balance sheet
adjustments or corrections accounts.
back to GLS
2. Capture Transactions: Record
in transaction files.

3. Record in Journals: Use

special or general journals.

4. Post to Subsidiary Ledgers:

Update detailed accounts.
 5. Post to General Ledger (GL): • XBRL is an XML-based standard
Summarize and post entries. designed for automated
financial reporting and data
6. Unadjusted Trial Balance:
exchange.
Check for debit-credit
equality. • It enables computer-readable
7. Adjusting Entries: Correct financial documents that can
errors and include unrecorded be automatically imported,
items. analyzed, and compared.

8. Post Adjusting Entries: Update

GL with adjustments. Understanding XML vs. HTML
9. Adjusted Trial Balance:
• HTML: Focuses on presentation;
Prepare for financial
tags define how data looks.
statements.
• XML: Focuses on data
10. Prepare Financial
structure; tags define what
Statements: Balance sheet,
the data means.
income statement, cash flow.

11. Closing Entries: Close • XML allows data to be stored in

temporary accounts and update relational form, making it
retained earnings. usable by applications.

12. Post-Closing Trial

Balance: Show accounts carried How XBRL Works
forward.
1. Taxonomy Selection:

o Choose an XBRL taxonomy,

XBRL – REENGINEERING FINANCIAL which is a standardized
REPORTING classification scheme
The Problem with HTML-Based (e.g., CI taxonomy for
Financial Reports commercial/industrial
firms).
• Most companies publish
o Taxonomies define what
financial data online using
data should be reported
HTML, which is visually
and how.
readable but not machine-
processable. 2. Data Mapping:

• Analysts and regulators must o Map internal GL accounts

manually re-enter data into to XBRL tags using tools
their systems for analysis. like Taxonomy Mapper.

o This step aligns

internal data with
The Solution: XBRL (eXtensible
standardized external
Business Reporting Language)
formats.

3. Tag Embedding:
 o Once mapped, tags are • 2005: U.S. banking regulators
embedded in the database mandated quarterly call
records. reports in XBRL for over 8,000
banks.
o This only needs to be
done once, and can be • 2005: SEC launched a voluntary
reused for future program allowing companies to
reports. submit XBRL exhibits with
4. Instance Document Creation: their filings.

o Software generates XBRL • 2006: SEC introduced IDEA

instance documents (Interactive Data Electronic
(actual financial Application), a new system for
reports). receiving XBRL filings.

o These are machine- • 2008: SEC required large

readable and can be public companies to adopt XBRL
published on intranets, for financial reporting by
extranets, or the December 15.
Internet.
International Developments
5. Human-Readable Presentation:
• Japan: Tokyo Stock Exchange
o A style sheet (HTML has accepted XBRL since 2003.
layout rules) can be
applied to make XBRL • Canada: CSA launched a
documents visually voluntary program in 2007 to
appealing for human promote XBRL usage.
users.
• Other countries: Regulators in
China, Spain, the Netherlands,
and the UK have mandated XBRL
Benefits of XBRL for certain companies.
• Automates financial data
exchange and analysis.
XBRL and Regulatory Compliance
• Improves accuracy, efficiency,
and comparability. • XBRL supports compliance with
the Sarbanes-Oxley Act (SOX).
• Enables real-time reporting
and instant access to • It enables earlier and more
financial data for accurate reporting, helping
stakeholders. meet SOX’s transparency and
timeliness requirements.
XBRL Adoption and Progress

XBRL is becoming a standard tool for

financial reporting, with growing Key Takeaway
adoption both in the U.S. and
XBRL is rapidly becoming the
internationally:
preferred format for financial data
United States exchange, offering benefits like
automation, standardization, and CONTROLLING THE FRS
regulatory alignment. Its adoption
is expanding globally, making it SOX Compliance and FRS Controls
essential for financial
Under the Sarbanes-Oxley Act (SOX),
professionals to understand and
management must implement controls
implement.
over both:

• The FRS (Financial Reporting

System)

• The Transaction Processing

Systems (TPS) that feed data
into it

Key Risks to the FRS

1. Defective audit trail

2. Unauthorized access to the

general ledger (GL)

3. GL and subsidiary ledger

mismatches

4. Incorrect GL balances due to

unauthorized or erroneous
journal vouchers

These risks can lead to misstated

financial reports, resulting in:

• Legal consequences

• Financial losses

• SOX-related sanctions

COSO Framework-Based Controls

1. Transaction Authorization

• Journal vouchers must be

approved by responsible
managers.

• Vouchers originate from

various departments (e.g.,
cash receipts, sales,
financial reporting).

2. Segregation of Duties
To maintain integrity: o GL Change Report:
Effects of postings on
• GL access should be separate GL accounts
from:

o Journal or subsidiary
ledger maintenance Internal Control Implications of
XBRL
o Journal voucher
preparation 1. Taxonomy Creation

o Physical asset custody • Incorrect taxonomy can cause

misrepresentation of financial
3. Access Controls
data
• Limit GL access to authorized
• Controls must ensure accurate
personnel only
taxonomy generation
• Use IT controls like: 2. Taxonomy Mapping Errors
o User views
• Mapping internal accounts to
o Authorization tables XBRL tags must be accurate

o Data encryption • Errors can lead to material

misstatements
4. Accounting Records (Audit Trail)
3. Validation of Instance Documents
• Ensure transactions are
traceable from input to output • Final XBRL reports must be
independently verified
• Audit trail should support:
• Ensure correct taxonomy and
o Customer/vendor tags before publishing
inquiries

o File reconstruction

o Historical audits

o Regulatory compliance

o Error detection and

correction

5. Independent Verification

• GL serves as a verification
checkpoint

• Key reports:

o Journal Voucher Listing:

Details of posted
vouchers