Chapter 3
Accounting Cycle and Accounting Information Systems
Bachelors Program in Banking Finance and Insurance
Financial Accounting
•
Bachelor
Accounting Cycle and Accounting Information Systems
Introduction
Financial accounting transforms economic events into reliable information for managers, investors, lenders, regulators and policyholders. This transformation is not a single bookkeeping act. It is a controlled sequence in which evidence is captured, transactions are authorized and classified, amounts are recorded in journals, account balances are updated in ledgers, and reports are prepared and reviewed.
An accounting information system (AIS) comprises the people, procedures, data, software, infrastructure and controls used to collect, process, store and report accounting information. A small enterprise may use cloud bookkeeping software, while a bank or insurer may integrate core operational systems with an enterprise resource planning (ERP) platform. In either setting, the accounting logic remains grounded in double-entry bookkeeping, accrual accounting and a verifiable audit trail.
The quality of financial reports depends on the quality of every preceding stage. An incorrectly authorized payment, misclassified account or incomplete interface may flow through an automated system rapidly while remaining wrong. Automation increases processing capacity, but it does not remove the need for professional judgment and internal control.
Learning Objectives
After studying this chapter, students should be able to:
Explain the stages and control objectives of the accounting cycle.
identify and evaluate source documents used in banking, finance and insurance.
Record transactions in journals and post them to general-ledger accounts.
Prepare unadjusted, adjusted and post-closing trial balances.
Design a practical chart of accounts.
Distinguish the general ledger from subsidiary ledgers and reconcile control accounts.
Explain audit trails, batch controls and automated transaction processing.
Evaluate ERP systems, cloud accounting, artificial intelligence and related risks.
Apply ethical, governance and regulatory principles to accounting systems.
1. The Accounting Cycle
The accounting cycle is the recurring process through which transaction data become financial statements. Although software may perform several stages simultaneously, the logical sequence remains important.
Stages of the accounting cycle
Figure: Stages of the accounting cycle
Figure: Logical stages of the accounting cycle.
The principal stages are:
Identify and analyze events. Determine whether an event meets the recognition requirements and identify the affected accounts.
Journalize. Record the transaction chronologically with equal debits and credits.
Post. Transfer journal effects to individual ledger accounts.
Prepare an unadjusted trial balance. Test the arithmetic equality of ledger debits and credits.
Record adjustments. Recognize accruals, deferrals, depreciation and estimates relating to the period.
Prepare an adjusted trial balance and financial statements. Use adjusted balances to prepare the statements.
Close temporary accounts. Transfer revenues, expenses and distributions to equity.
Prepare a post-closing trial balance. Confirm that permanent-account debits equal permanent-account credits.
Reversing entries may be made at the start of the next period for selected accruals. They are optional and do not replace properly prepared adjusting entries.
2. Source Documents and Transaction Recognition
A source document provides evidence about an economic event and supports data entry, authorization and subsequent verification. A document does not by itself prove that an amount should be recognized. Accountants must also consider whether the entity controls an asset, has incurred a liability, has earned revenue or has consumed a resource.
Activity
Typical source document
Key information or control
Cash receipt
Deposit record, receipt or bank advice
Date, payer, amount and account
Credit sale
Invoice and service record
Customer, price, terms and evidence of delivery
Purchase
Purchase order, receipt report and supplier invoice
Three-way matching and authorization
Payroll
Time record and approved payroll register
Employee validity, hours, rates and deductions
Lending
Approved loan agreement and disbursement record
Borrower, principal, rate, term and approval
Insurance premium
Policy schedule, invoice and collection record
Policyholder, coverage period and premium
Insurance claim
Claim form, assessor report and payment approval
Insured event, estimate, authorization and payee
Securities trade
Trade confirmation and settlement report
Instrument, quantity, price, counterparty and date
Electronic source records include application programming interface (API) messages, electronic invoices, digital receipts and system-generated transaction logs. Their reliability depends on authentication, completeness, integrity and retention controls.
Document controls
Good document controls include unique sequential identifiers, approval limits, restricted access, duplicate-document detection, validation rules and retention schedules. Missing document numbers should be investigated because they may indicate unrecorded, deleted or failed transactions.
3. Accounts, Double Entry and the Chart of Accounts
An account accumulates increases and decreases relating to a particular financial statement element. The accounting equation is:
Assets = Liabilities + Equity
Revenues increase equity, whereas expenses and owner distributions reduce it. Every transaction must preserve the equation.
Under double-entry bookkeeping, total debits equal total credits for each journal entry:
∑ Debits = ∑ Credits
Debit and credit are positional terms, not synonyms for increase and decrease. Assets and expenses normally increase by debits. Liabilities, equity and revenues normally increase by credits.
3.1 Designing the chart of accounts
A chart of accounts is an organized list of account names and identifiers. It should support statutory reporting, management analysis, tax reporting, consolidation and system integration without becoming excessively complex.
A financial institution might use a segmented code such as:
02-115-3100-07
where 02 identifies the legal entity, 115 the branch, 3100 the natural account and 07 the product category. Segment meanings must be documented and consistently governed.
A well-designed chart of accounts should be:
mutually exclusive, so transactions have one appropriate classification;
collectively sufficient for reporting needs;
scalable across branches, products and entities;
stable, with controlled additions and deactivation;
compatible with consolidation and regulatory mapping; and
no more detailed than decision-making and control require.
Customer names or other rapidly changing attributes should usually be stored as subsidiary-ledger dimensions rather than embedded permanently in natural-account codes.
4. Journals and Journalizing
A journal records transactions chronologically. A journal entry normally includes the date, accounts, debit and credit amounts, explanation, source-document reference and posting reference.
A general journal can record any transaction. High-volume organizations also use special journals, such as cash receipts, cash payments, sales and purchases journals. Banks and insurers often receive summarized journal feeds from operational systems for loans, deposits, premiums, claims and investments.
Worked Example: Harbor Advisory Services
Harbor Advisory Services is an illustrative enterprise. All April source documents are assembled and reviewed before the following complete journal is prepared. Amounts are in currency units (CU).
Date
Account debited
Debit (CU)
Account credited
Credit (CU)
Apr. 1
Cash
120,000
Owner’s Capital
120,000
Apr. 2
Equipment
24,000
Cash
24,000
Apr. 3
Supplies
9,600
Accounts Payable
9,600
Apr. 5
Cash
18,000
Service Revenue
18,000
Apr. 8
Accounts Receivable
30,000
Service Revenue
30,000
Apr. 12
Accounts Payable
6,000
Cash
6,000
Apr. 18
Cash
20,000
Accounts Receivable
20,000
Apr. 22
Wages Expense
8,400
Cash
8,400
Apr. 25
Rent Expense
4,500
Cash
4,500
Apr. 28
Utilities Expense
1,800
Accounts Payable
1,800
Total
242,300
242,300
The journal is balanced because both columns total CU 242,300. This equality is necessary but not sufficient for accuracy: an equal debit and credit could still use incorrect accounts or amounts.
If a transaction is discovered after posting, the accountant should not silently insert or delete historical records. The correction should be entered with the actual correction date, linked to the original entry and approved under the organization’s correction policy. A reversing entry may first cancel the incorrect entry before the correct entry is posted.
5. Ledgers and Posting
The general ledger (GL) contains all general-ledger accounts used to prepare the entity’s financial statements. These include assets, liabilities, equity, revenues and expenses. Some, but not all, general-ledger accounts are control accounts.
A subsidiary ledger contains detailed records supporting a control account. Examples include individual customer receivables, supplier payables, loans, depositor accounts, insurance policies and claim files.
General-ledger control account
Possible subsidiary detail
Accounts Receivable
Balance of each customer
Loans Receivable
Principal balance of each borrower or facility
Accounts Payable
Amount owed to each supplier
Deposit Liabilities
Balance of each depositor account
Claims Payable
Estimate for each reported insurance claim
Posting transfers journal information to the affected ledger accounts. A posting reference links each journal line to its ledger destination and each ledger movement back to its source journal.
After posting Harbor’s entries, the balances are:
Account
Debit balance (CU)
Credit balance (CU)
Cash
115,100
—
Accounts Receivable
10,000
—
Supplies
9,600
—
Equipment
24,000
—
Accounts Payable
—
5,400
Owner’s Capital
—
120,000
Service Revenue
—
48,000
Wages Expense
8,400
—
Rent Expense
4,500
—
Utilities Expense
1,800
—
Total
173,400
173,400
For a debit-balance receivables control account, the period balance can be computed as:
This form applies to a normal debit-balance account. For a normal credit-balance liability, credit postings increase the balance and debit postings decrease it.
At a common cutoff date and under consistent currency and valuation rules, the control relationship is:
Differences may arise from timing mismatches, interface failures, duplicate records, postings to the wrong customer, unauthorized adjustments or foreign-currency conversion inconsistencies.
6. Trial Balances, Adjustments and Financial Statements
A trial balance lists ledger balances to test whether total debits equal total credits. It does not prove that every transaction is correct. It may fail to detect:
complete omission of a transaction;
use of the wrong debit and credit accounts;
equal errors on both sides;
two errors that offset each other; or
an incorrect estimate recorded through a balanced entry.
6.1 Adjusting entries
Accrual accounting requires revenues and expenses to be recognized in the appropriate period. Common adjustments include:
accrued revenue: earned but not yet billed;
accrued expense: incurred but not yet recorded;
deferred revenue: cash received before revenue is earned;
prepaid expense: cash paid before consumption;
depreciation or amortization: systematic allocation of cost; and
estimates: such as expected credit losses or insurance claim liabilities.
At April 30, Harbor determines that:
supplies remaining are CU 3,100;
monthly equipment depreciation is CU 400; and
wages of CU 2,200 have been incurred but not paid.
Supplies consumed are:
Supplies expense = CU 9,600 − CU 3,100 = CU 6,500
The adjusting entries are:
Adjustment
Debit (CU)
Credit (CU)
Supplies Expense
6,500
—
Supplies
—
6,500
Depreciation Expense
400
—
Accumulated Depreciation—Equipment
—
400
Wages Expense
2,200
—
Wages Payable
—
2,200
The adjusted trial balance is:
Account
Debit (CU)
Credit (CU)
Cash
115,100
—
Accounts Receivable
10,000
—
Supplies
3,100
—
Equipment
24,000
—
Accumulated Depreciation—Equipment
—
400
Accounts Payable
—
5,400
Wages Payable
—
2,200
Owner’s Capital
—
120,000
Service Revenue
—
48,000
Wages Expense
10,600
—
Rent Expense
4,500
—
Utilities Expense
1,800
—
Supplies Expense
6,500
—
Depreciation Expense
400
—
Total
176,000
176,000
Total expenses are CU 23,800, so April profit is:
Profit = CU 48,000 − CU 23,800 = CU 24,200
Ending equity is CU 144,200, assuming no owner withdrawals. Net assets also equal CU 144,200:
Assets CU 151,800 − Liabilities CU 7,600 = Equity CU 144,200
6.2 Closing and post-closing trial balance
Revenue and expense accounts are temporary because they measure performance for one period. Closing entries transfer their net effect to equity and reduce their balances to zero. Permanent accounts—assets, liabilities and equity—continue into the next period.
After Harbor closes CU 24,200 profit to capital, the post-closing trial balance totals CU 152,200 on each side. Its credit balances comprise accumulated depreciation of CU 400, accounts payable of CU 5,400, wages payable of CU 2,200 and capital of CU 144,200.
7. Audit Trails and Processing Controls
An audit trail is the documented path from an original event to the financial statements and back again. A complete trail allows an auditor to trace a reported balance to ledger entries, journals, source documents, approvals and system logs. It also permits vouching from accounting records to supporting evidence and tracing from source evidence forward to the records.
Important controls include:
authorization controls: only approved transactions proceed;
validation controls: dates, account codes and amounts meet defined rules;
segregation of duties: authorization, custody, recording and reconciliation are separated;
access controls: permissions follow job responsibilities and least privilege;
change management: program and configuration changes are tested and approved;
interface controls: record counts and totals confirm complete transfer;
reconciliations: independent comparisons identify unexplained differences; and
exception reports: unusual, duplicate or rejected transactions receive review.
Batch controls
A batch-processing system may use:
record count: number of records processed;
financial control total: sum of monetary amounts;
hash total: sum of a nonfinancial field, such as customer numbers, used only as a completeness check; and
run-to-run total: a balance carried between processing stages.
A hash total has no accounting interpretation. Its value lies in detecting missing or substituted records when the input and output totals differ.
8. ERP Systems, Cloud Accounting and Automation
8.1 Enterprise resource planning
An ERP system integrates functions such as procurement, sales, payroll, treasury, assets and general accounting using shared data and standardized processes. Integration can reduce duplicate entry and improve real-time reporting. However, configuration errors may affect many entities or periods, and weak access design can create incompatible responsibilities.
A bank may retain a specialized core banking platform while sending summarized entries to the ERP general ledger. An insurer may similarly integrate policy administration, billing, claims and investment systems. Interface design and reconciliation therefore remain essential even when an ERP is used.
8.2 Cloud accounting
Cloud accounting software is hosted by a service provider and accessed through a network. Potential advantages include scalability, frequent updates, remote access, lower initial infrastructure expenditure and easier integration.
Risks include service outages, cyberattack, vendor dependence, unauthorized access, unclear data location and difficulties in extracting data when changing providers. Responsibility is shared: the provider may secure infrastructure, while the customer remains responsible for user access, data classification, configuration, review and legal compliance.
Before adoption, an organization should assess service-level commitments, encryption, backup and recovery, incident notification, audit reports, data residency, retention, portability and termination provisions.
8.3 Automated transaction processing and AI
Automation may involve:
APIs that transfer approved transactions between systems;
optical character recognition that extracts invoice data;
robotic process automation that performs repetitive rules-based tasks;
matching engines that reconcile payments and invoices;
workflow systems that route approvals; and
machine-learning models that identify anomalies or predict account classifications.
Automation should not be confused with autonomous recognition. A system may extract an amount correctly while applying an inappropriate accounting policy. Material estimates, unusual transactions and low-confidence classifications require competent human review.
AI governance should address model accuracy, explainability, bias, privacy, version control, override authority and monitoring. Training data may reproduce past errors, while generative systems may produce plausible but unsupported entries. AI output must therefore be treated as a recommendation or exception signal unless formally validated within an approved control framework.
9. Illustrative Case: Meridian Bank’s Loan Reconciliation
Background
Meridian Bank is a fictional regional bank. Its loan-administration system maintains borrower-level records, while the general ledger contains a Loans Receivable control account. A nightly interface summarizes approved loan movements for posting to the GL.
Problem
At month-end, the GL Loans Receivable balance is CU 1,268,000. The borrower-level subsidiary schedule totals CU 1,260,000. Thus, the GL exceeds the subsidiary schedule by CU 8,000.
Difference = CU 1,268,000 − CU 1,260,000 = CU 8,000
An initial suggestion is to debit Loans Receivable in the GL by CU 8,000. This suggestion is rejected because it would increase, rather than eliminate, the excess.
Analysis
The reconciliation team traces the CU 8,000 difference through the journal identifier, interface log, loan agreement and disbursement record. It discovers that a newly originated CU 8,000 loan was properly posted to the GL but was omitted from the borrower-level schedule because the subsidiary-system update failed.
The omission makes the subsidiary schedule too low. Adding the missing loan to the schedule gives:
Corrected subsidiary schedule = CU 1,260,000 + CU 8,000 = CU 1,268,000
The corrected schedule now agrees with the existing GL balance. No additional GL debit is appropriate. If the bank debited the GL again, its balance would become CU 1,276,000, duplicating the loan and creating a new CU 8,000 difference against the corrected schedule.
Approach and Solution
Meridian:
restores the missing borrower-level record using the approved source documents;
makes no additional GL entry;
documents the exception, cause, reviewer and resolution;
verifies that the next interface run includes the record correctly;
introduces automated record-count and control-total comparisons; and
configures an alert when a GL control balance differs from its subsidiary schedule.
Outcome
Both records report CU 1,268,000. The correction preserves the valid GL posting and repairs the incomplete subsidiary data without duplicating the loan.
Learning Points
A reconciliation difference must be investigated directionally. Accountants should determine which record is wrong before posting a correction. Blindly forcing the GL to change can magnify an error. Effective reconciliation combines arithmetic comparison, source-document examination, system-log analysis and independent approval.
10. Governance, Ethics and Regulatory Considerations
Accounting systems contain sensitive information about customers, borrowers, employees, claimants and counterparties. Governance must therefore address confidentiality, integrity, availability and lawful use.
Ethical accounting requires entries to reflect economic substance rather than desired results. Employees should not accelerate revenue, defer known expenses, override credit-loss estimates or suppress exceptions to achieve targets. Management override is particularly dangerous because senior personnel may bypass controls designed for ordinary users.
Regulatory requirements differ across jurisdictions, but commonly affect record retention, privacy, cybersecurity, audit access, anti-money-laundering monitoring, consumer protection and financial reporting. Organizations should map each requirement to data ownership, control responsibility and evidence of compliance.
Best practices include:
assigning ownership of accounts, interfaces and reconciliations;
reviewing access rights periodically;
prohibiting shared user accounts;
retaining immutable logs for sensitive actions;
applying approval thresholds and dual authorization;
testing backups and disaster recovery;
monitoring unresolved exceptions; and
documenting accounting judgments and model overrides.
Challenges and Limitations
No AIS can eliminate all error or fraud. Trial balances test debit-credit equality but not economic validity. Integrated systems improve speed but may spread configuration errors rapidly. Detailed data enhance analysis but increase privacy and cybersecurity exposure. Automated controls are consistent but may fail when rules are incomplete or data quality is poor.
Professional judgment remains necessary for recognition, measurement, estimates, materiality and correction. The most reliable environment combines sound accounting principles, well-designed technology, competent personnel, independent review and continuous monitoring.
Chapter Summary
The accounting cycle converts supported economic events into financial statements through analysis, journalizing, posting, trial balances, adjustments, reporting and closing. Source documents provide evidence, while double-entry bookkeeping preserves the accounting equation. The general ledger contains all financial-statement accounts; subsidiary ledgers provide detail for selected control accounts and must be reconciled to them.
A chart of accounts should balance reporting detail with consistency and scalability. Audit trails, authorization, segregation of duties, access restrictions, interface controls and reconciliations support data integrity. ERP and cloud systems can improve integration and processing efficiency, but they introduce configuration, cybersecurity, vendor and governance risks. Automated processing and AI require validation, exception handling and accountable human oversight. A correction should address the record that is actually wrong rather than mechanically forcing accounts to agree.
Key Terms
Accounting cycle: The recurring process used to transform transaction evidence into financial statements.
Accounting information system (AIS): The people, procedures, data, software, infrastructure and controls used to process accounting information.
Adjusting entry: An entry made to recognize period-end accruals, deferrals, depreciation or estimates.
Audit trail: The traceable path linking source evidence, journal entries, ledgers and reported balances.
Batch control: A count or total used to test the completeness and integrity of batch processing.
Chart of accounts: The organized list of account names and codes used by an entity.
Closing entry: An entry that transfers temporary-account balances to equity.
Control account: A general-ledger account supported by detailed subsidiary records.
Double-entry bookkeeping: A system in which each entry has equal total debits and credits.
Enterprise resource planning (ERP): An integrated system supporting multiple organizational functions through shared data and processes.
General ledger: The complete collection of general-ledger accounts used in financial reporting.
General journal: A chronological record capable of recording any type of accounting transaction.
Hash total: A total of nonfinancial identifiers used to test processing completeness.
Posting: The transfer of journal-entry effects to ledger accounts.
Reconciliation: The comparison of related records and investigation of differences.
Source document: Evidence containing information about an economic event or transaction.
Subsidiary ledger: A detailed ledger supporting a general-ledger control account.
Trial balance: A list of ledger balances used to compare total debits with total credits.
Review Questions
Short Answer Questions
What are the principal stages of the accounting cycle?
Why does a source document not automatically establish that an amount should be recognized?
How does a subsidiary ledger differ from the general ledger?
What types of errors can remain undetected by a balanced trial balance?
What is the purpose of a hash total?
Long Answer Questions
Explain how source documents, journals, ledgers and trial balances collectively support reliable financial reporting.
Discuss the principles that should guide the design and governance of a chart of accounts.
Evaluate the benefits and risks of integrating a core banking or insurance platform with an ERP general ledger.
Explain how adjusting and closing entries affect the accounts and financial statements.
Discuss the internal controls required for cloud accounting and automated transaction processing.
Analytical / Application Questions
A receivables control account reports CU 845,000, while the customer subsidiary ledger totals CU 837,500. Describe a systematic investigation before proposing any correcting entry.
Design a segmented chart-of-accounts code for a financial institution that reports by legal entity, branch, natural account and product. Explain the purpose of each segment.
An invoice-extraction system records supplier invoices automatically. Develop controls addressing duplicate invoices, invalid suppliers, incorrect tax amounts and low-confidence AI classifications.
Multiple Choice Questions with Answers
Question 1
Which statement best describes the role of a source document?
A. It provides evidence about an event but does not eliminate the need to assess recognition and classification.
B. It guarantees that the transaction has been recorded in the correct period.
C. It replaces authorization when generated electronically.
D. It proves that every amount on the document is economically valid.
Correct Answer: A. It provides evidence about an event but does not eliminate the need to assess recognition and classification.
Question 2
Which definition of the general ledger is correct?
A. A chronological collection of source documents
B. A collection containing all general-ledger accounts, some of which may be control accounts
C. A ledger containing only customer and supplier balances
D. A collection consisting only of control accounts
Correct Answer: B. A collection containing all general-ledger accounts, some of which may be control accounts
Question 3
At the same cutoff date, a properly reconciled Loans Receivable control account should equal:
A. The total of all loan repayments during the period
B. The total of approved loan applications
C. The sum of individual loan balances in the subsidiary ledger
D. The cash balance plus interest revenue
Correct Answer: C. The sum of individual loan balances in the subsidiary ledger
Question 4
Harbor had supplies of CU 9,600 before adjustment and CU 3,100 remained at period-end. What amount should be recorded as Supplies Expense?
A. CU 3,100
B. CU 6,500
C. CU 9,600
D. CU 12,700
Correct Answer: B. CU 6,500
Question 5
Which error can remain undetected when a trial balance has equal debit and credit totals?
A. Posting a CU 900 debit as CU 90 without changing the credit
B. Posting only the debit side of an entry
C. Completely omitting a balanced transaction
D. Adding the debit column incorrectly while the credit column is correct
Correct Answer: C. Completely omitting a balanced transaction
Question 6
Under the shared-responsibility approach to cloud accounting, which responsibility normally remains with the customer organization?
A. Manufacturing the provider's server hardware
B. Managing its users, permissions and accounting configuration
C. Operating the provider's physical data center
D. Writing the provider's network protocols
Correct Answer: B. Managing its users, permissions and accounting configuration
Question 7
Meridian Bank's GL Loans Receivable balance is CU 1,268,000, while its subsidiary schedule is CU 1,260,000. An CU 8,000 loan is already in the GL but was omitted from the schedule. What is the correct action?
A. Debit the GL by CU 8,000 and leave the schedule unchanged.
B. Credit the GL by CU 8,000 and delete the loan documents.
C. Add the CU 8,000 loan to the subsidiary schedule and make no additional GL entry.
D. Debit both the GL and the subsidiary schedule by CU 8,000.
Correct Answer: C. Add the CU 8,000 loan to the subsidiary schedule and make no additional GL entry.
Question 8
Which batch control sums nonfinancial fields such as customer identification numbers solely to test processing completeness?
A. Financial control total
B. Hash total
C. Adjusted trial balance
D. Bank reconciliation
Correct Answer: B. Hash total
Question 9
Which transaction requires an adjusting entry at period-end?
A. Cash received and revenue earned and recorded on the same date
B. Equipment purchased for cash and correctly recorded
C. Wages incurred by employees but not yet recorded or paid
D. A supplier invoice recorded and paid before period-end
Correct Answer: C. Wages incurred by employees but not yet recorded or paid
Question 10
Which arrangement best supports segregation of duties?
A. The employee who approves payments also prepares and reviews the bank reconciliation.
B. The system administrator shares an account with the financial controller.
C. The employee holding cash independently authorizes write-offs.
D. Different authorized employees approve payments, maintain custody and perform reconciliations.
Correct Answer: D. Different authorized employees approve payments, maintain custody and perform reconciliations.