Chapter 5 — Computerised Accounting System

What is a Computerised Accounting System (CAS)?

A Computerised Accounting System (CAS) uses accounting software to record, process and report financial transactions. It replaces manual books with digital records stored in databases and automates routine accounting tasks such as journalising, posting to ledgers, preparing trial balances and generating financial statements.

Key components

• Hardware: Computers, servers, printers and backup devices.
• Software: Accounting packages or ERP modules for bookkeeping, payroll, inventory and reporting.
• Database: A central repository that stores masters (customers, suppliers, ledgers) and transaction data.
• People: Users such as accountants, data-entry operators and system administrators.
• Procedures & Controls: Documented ways to enter, verify and secure data.

Basic processing cycle

1. Input: Capture source documents (invoices, receipts) and enter transactions (voucher entry).
2. Processing: System validates data, updates ledgers and inventory, computes taxes and depreciation.
3. Storage: Transactions and masters are stored in the database for retrieval.
4. Output & Reporting: Generates trial balances, ledgers, profit & loss, balance sheet and management reports.

Features & Functions

• Automated posting: One entry updates all relevant accounts.
• Immediate reports: Trial balance and financial statements on demand.
• Inventory integration: Real-time stock updates with goods movements.
• Tax and statutory compliance support (GST/VAT, TDS).
• Payroll processing with statutory deductions.
• Backup & restore, user access control and audit trails.

Advantages over manual accounting

• Speed — much faster data entry and report generation.
• Accuracy — reduces arithmetic and posting errors.
• Reliability — consistent application of rules (tax, depreciation).
• Real-time information — up-to-date balances and stock levels.
• Space saving & retrieval — electronic storage and quick search.

Limitations & risks

• Initial cost of hardware/software and training.
• Dependence on electricity and system availability.
• Need for regular backups and security against unauthorized access.
• Risk of incorrect results if data entry or configuration is wrong.

Internal controls in CAS

• User authentication and role-based access.
• Segregation of duties (data entry, approval, reconciliation separate).
• Regular backups and off-site storage.
• Audit trail that logs who changed what and when.

How CAS helps accounting learning and business

For students, CAS demonstrates how accounting theory (journal, ledger, trial balance, financial statements) is applied in practice. For businesses, it improves efficiency, compliance and decision-making by producing timely and accurate financial information.

Overview

Manual accounting is the traditional method of recording financial transactions by hand in books of original entry (journals) and ledgers. Computerised accounting uses accounting software to record, process and report transactions electronically.

Key differences

• Speed and efficiency: Manual systems are slower because each entry is written and posted individually. Computerised systems post entries automatically and update all related records instantly.
• Accuracy: Manual posting is prone to arithmetic and transcription errors. Software minimizes computation errors and enforces double-entry rules, reducing mistakes.
• Cost: Manual accounting has lower initial cash outlay (no software/hardware), but higher ongoing labour cost. Computerised systems have upfront costs for software and hardware and training, but lower recurring posting costs and faster processing.
• Reporting and analysis: Manual reports require time-consuming compilation. Computerised systems produce instant trial balances, ledgers, profit & loss statements, and customizable reports.
• Scalability: Manual systems become cumbersome as transaction volume grows. Computerised systems scale easily to large transaction volumes.
• Control, audit trail and security: Manual books provide a physical audit trail but are susceptible to forgery, loss, and unauthorized alterations. Computerised systems offer user access controls, logging, backups and time-stamped audit trails, though they require IT security measures.
• Backup and recovery: Manual records are vulnerable to fire, theft or deterioration (unless duplicated). Computerised systems can be backed up regularly and recovered if hardware fails.
• Flexibility and standardisation: Manual entries vary by preparer and can lack standard formats. Computerised systems enforce standard templates, chart of accounts, and consistent classifications.

When each is appropriate

• Small, very low-volume businesses or one-person operations may use manual accounting due to low cost and simplicity.
• Businesses with moderate to high transaction volume, multiple users, statutory reporting needs (e.g., GST), payroll complexity, or the need for timely management information should use computerised accounting.

Typical components of a computerised accounting system

• Chart of accounts, ledgers and journals implemented in software
• Transaction entry modules (sales, purchases, receipts, payments, payroll)
• Automated posting and double-entry enforcement
• Report generator (trial balance, profit & loss, balance sheet)
• Access controls, audit logs, and backup mechanisms

Advantages and disadvantages at a glance

• Manual: advantages – Low initial cost, simple for tiny businesses, easy to understand the basic mechanics of accounting.
• Manual: disadvantages – Slow, error-prone, hard to scale, time-consuming reporting, weak security and backups.
• Computerised: advantages – Fast processing, accurate calculations, instant reports, strong audit trail, easier compliance and backups.
• Computerised: disadvantages – Initial cost, training required, dependence on electricity/IT, risk of data breach if not secured.

Practical notes for learners

• Understanding manual accounting is essential: it teaches the logic behind double-entry bookkeeping, debit/credit rules, and account classification.
• Learning a computerised package (for example Tally, QuickBooks, or practise modules) shows how the same principles are implemented in software and highlights automation benefits.

A Computerised Accounting System (CAS) is an automated system that records, processes and reports financial transactions using computer hardware, software and defined procedures. The main components work together to ensure accurate, timely and secure accounting. Below are the key components with their roles and interaction:

• Hardware: Physical devices used to run the accounting application and capture transactions. Typical items: servers (central processing and database), desktop PCs/laptops, barcode scanners, POS terminals, printers, UPS and storage devices. Hardware provides computing power, input/output and storage.
• Software: The accounting application and supporting programs. This includes packaged accounting software (e.g., Tally, QuickBooks, Zoho Books), payroll modules, inventory modules, report generators and operating system software. Software implements accounting rules, performs calculations, posts to accounts, and produces reports.
• Database / Data: Structured storage for master data (chart of accounts, customer/supplier records, inventory items) and transaction data (sales, purchases, receipts, payments). A database management system (DBMS) such as SQL Server or MySQL ensures data integrity, indexing and fast retrieval.
• People (Users): All human actors—accountants, clerks, managers, auditors and IT staff—who interact with the system. They enter data, approve transactions, design reports and maintain the system. Proper training and segregation of duties are essential.
• Procedures & Policies: Standard Operating Procedures (SOPs) that define how transactions are recorded, authorized, reviewed and archived. These include data entry rules, approval workflows, reconciliation routines and change-control processes.
• Networks & Communications: Connectivity components (LAN, WAN, Internet) that enable multi-user access, remote offices and cloud services. Secure communication protocols (VPN, SSL) protect data in transit.
• Internal Controls & Security: Access controls (user IDs, passwords, role-based permissions), encryption, audit trails, approval workflows and activity logs to prevent errors and fraud. Controls also include physical security of servers and workstations.
• Backup & Recovery: Regular backup schedules (full, incremental), offsite/cloud storage and documented recovery procedures to restore data after hardware failure, data corruption or disaster.
• Integration Interfaces: Connectors or APIs that allow the accounting system to exchange data with other systems—bank feeds, POS systems, e-commerce platforms, payroll systems and ERP modules.
• Reports & Output Devices: Financial statements (balance sheet, profit & loss), management reports, invoices and tax returns generated by the system and delivered via screens, printed reports, PDFs or emails.
• Documentation & Training: User manuals, process documentation and training materials that help users operate the system correctly and understand controls.

How the components interact: Source documents (invoices, receipts) are captured via input devices or entered manually → validated by software using procedures and controls → stored in the database → processed (posting, calculations) by software → outputs (reports, invoices, alerts) are generated for users and management. Networking and security protect the flow; backups and documentation ensure continuity.

What is Accounting Software / Packages?
Accounting software (or packages) are computer programs designed to record, process and report financial transactions of a business. They automate bookkeeping tasks (journals, ledgers, trial balance), generate financial statements, help with taxation (e.g., GST tasks), manage inventory, payroll and provide reports for decision making.

Key Components and Modules

• Ledger/General Accounting: Journal entries, ledgers, trial balance.
• Inventory Management: Stock in/out, valuation, reorder levels.
• Sales & Purchases: Invoicing, receipts, supplier bills.
• Accounts Receivable / Payable: Customer and vendor balances, ageing reports.
• Payroll: Employee records, salary processing, statutory deductions.
• Taxation: GST/VAT computation, return filing support.
• Bank Reconciliation: Match book entries with bank statements.
• Reporting & Analytics: Profit & loss, balance sheet, cash flows, customized reports.

Types of Packages

• Desktop/Standalone: Installed locally (e.g., TallyPrime desktop version, Busy).
• Cloud/Online: Web-based, accessible anywhere (e.g., QuickBooks Online, Zoho Books).
• Industry-specific ERP: Larger integrated systems for manufacturing/retail (e.g., SAP Business One).

Advantages

• Automation reduces manual errors and speeds up bookkeeping.
• Real-time reports for faster decision-making.
• Standardised financial statements and audit trails.
• Integrated tax computations and e-filing features.
• Scalability—modules can be added as business grows.

Limitations & Risks

• Initial cost and learning curve.
• Data security and backup risks if not managed properly.
• Dependence on accurate master data—wrong setup leads to wrong results.
• Version compatibility and software updates may cause disruptions.

Implementation Steps & Controls

1. Requirement analysis: choose suitable modules and deployment (desktop vs cloud).
2. Data migration: import opening balances, masters (customers, suppliers, inventory).
3. Chart of accounts setup and user roles/permissions.
4. Training users and defining accounting policies (vouchers, approval workflows).
5. Backups, data encryption and access controls; maintain audit trails.
6. Periodic reconciliation (bank, stock) and regular software updates.

How Software Helps Accounting Concepts

Software enforces double-entry accounting: every entry has a debit and a credit; ledgers automatically update balances; trial balance is prepared instantly; financial statements are generated from the same data source, reducing reconciliation effort.

Overview
Basic accounting concepts are the foundation rules and assumptions on which accounting records are prepared. In a Computerised Accounting System (CAS), these concepts are implemented through software features (voucher types, validation rules, auto-posting, reports, access control) so that transactions follow accounting principles automatically and consistently.

Key concepts and how CAS implements them

• Business Entity — Accounts are maintained for the business separately from owners. In CAS: separate ledgers, separate company files, separate capital accounts.
• Money Measurement — Only transactions measurable in monetary terms are recorded. CAS restricts entries to numeric currency fields and disallows non‑monetary notes as ledger postings.
• Going Concern — Accounts assume the business will continue. CAS uses depreciation schedules and amortisation over useful lives rather than immediate write‑offs.
• Dual Aspect (Double Entry) — Every transaction has equal debit and credit effects. CAS enforces balanced voucher entry and prevents saving an unbalanced voucher.
• Matching Principle — Expenses are matched with related revenues in the same period. CAS supports period closing, accruals and prepayments entries, and automatic allocations for period reports.
• Accrual Concept — Revenues and expenses are recorded when earned/incurred, not when cash changes hands. CAS allows accrual journal entries, recurring accrual templates and period cut‑offs.
• Conservatism/Prudence — Anticipate losses, not gains. CAS provides provisions/allowance ledgers, rounding/truncation settings and flags for material write‑downs.
• Cost Concept — Assets are recorded at purchase cost. CAS stores cost price per inventory item and uses it in valuation and COGS calculations.
• Materiality — Only significant items affect reporting. CAS can apply thresholds for capitalization vs expense and summarize small transactions.
• Realisation Concept — Record income when earned (usually on sale). CAS posts sales to revenue ledgers when invoice/voucher is entered according to chosen revenue recognition rules.

CAS features that support these concepts

• Voucher types (sales, purchase, receipt, payment, journal) that map to standard accounting entries.
• Automated double‑entry posting and ledger updation.
• Validation (mandatory fields, date ranges, numeric checks) to enforce Money Measurement and Periodicity.
• Recurring transactions and templates for accruals, depreciation, subscriptions.
• Audit trail (time stamps, user IDs, change logs) supporting Business Entity and internal control.
• Reconciliation tools (bank reconciliation, ledger vs subledger) ensuring accuracy.
• Role‑based access and backups to protect data integrity and continuity (Going Concern).

Example of transaction flow in CAS

1. User enters a Sales Invoice voucher (date, customer, items, amounts).
2. CAS validates fields, computes taxes, totals, and auto‑creates journal entries:
   Debit: Accounts Receivable (Customer)  XXX
   Credit: Sales Revenue                      XXX
   Credit: Tax Payable (if any)               YYY
3. Ledgers and stock (if enabled) update automatically.
4. Reporting shows the effect in trial balance, P&L and balance sheet immediately.

Because of these automated controls, CAS reduces manual errors, enforces accounting concepts, and speeds up preparing accurate financial statements.

Overview

In a computerised accounting system, a voucher is the primary document (electronic or scanned) that records the details of a business transaction and authorises its recording in the books. Voucher and transaction processing describe the steps from capturing a transaction to posting it in the ledger and producing reports, together with controls to ensure accuracy and authenticity.

What is a Voucher?

• A voucher is a source document or an electronic record that supports an accounting entry. It contains details such as date, parties, amount, narration, voucher number and supporting attachments (invoice, receipt, challan).
• In a computerised system a voucher is captured through a voucher entry screen or imported from invoice/bank feeds and saved as a transaction record.

Types of Vouchers

• Payment Voucher: Records cash/bank payments (e.g., cheque to a supplier).
• Receipt Voucher: Records cash/bank receipts (e.g., money received from a customer).
• Journal Voucher (Journal Entry): For adjustments and non-cash entries (depreciation, provisions, correction of errors).
• Contra Voucher: For transfers between cash and bank or between bank accounts.
• Purchase/Sales Voucher (Sales Invoice, Purchase Invoice): Records credit or cash sales and purchases.
• Debit Note / Credit Note: Adjustments to purchase or sales returns and allowances.
• Petty Cash Voucher: Small cash payments supported by petty receipts.

Components of a Voucher

• Voucher number (unique, sequential)
• Date
• Account(s) to be debited and credited
• Amount(s)
• Narration explaining the transaction
• Authorization (prepared by, checked by, approved by)
• Attachments or links to supporting documents (invoices, receipts)

Transaction Processing Steps (Computerised)

1. Capture: Data entry via voucher screens, OCR or import from bank/invoice feeds.
2. Validation: Format checks, mandatory fields, numeric ranges, GST/ tax validations, account code validation.
3. Authorization: Approval workflow — preparer → verifier → approver (electronic signatures or role-based approvals).
4. Recording/Posting: Once approved, voucher is posted to the relevant ledgers (general ledger, sub-ledgers like debtors/creditors, inventory).
5. Aggregation and Reporting: Trial balance, profit & loss, balance sheet, ledger reports and statutory returns (GST, TDS etc.).
6. Audit Trail & Controls: System logs (who entered/modified/approved), voucher numbering, restriction by user roles, backups and versioning.

Advantages of Computerised Voucher Processing

• Faster entry and automated posting to multiple ledgers
• Automatic arithmetic and GST/tax computations
• Immediate validation and error-checking
• Searchable electronic attachments and audit trail
• Better internal controls (role-based approvals, segregation of duties)

Controls and Good Practices

• Unique, sequential voucher numbers to prevent tampering
• Role-based access and approval workflows
• Mandatory supporting documents for each voucher
• Periodic review of exception reports (unapproved vouchers, out-of-period entries)
• Reconciliation procedures (bank reconciliation, supplier and customer reconciliations)

Common Processing Scenarios (brief)

• Purchase on credit: Enter purchase voucher (debit Purchases/Inventory, credit Accounts Payable). Attach supplier invoice.
• Payment to supplier: Create payment voucher (debit Accounts Payable, credit Bank/Cash). Attach cheque image or bank advice.
• Sales on credit: Enter sales invoice voucher (debit Accounts Receivable, credit Sales). System calculates GST and updates tax ledger.
• Adjustment: Journal voucher for depreciation (debit Depreciation Expense, credit Accumulated Depreciation).

How Computerised Systems Enforce Double-entry

Every voucher entry must involve at least two ledger effects (debit and credit). The system rejects or flags entries where total debits ≠ total credits. Posting is automated so ledgers and trial balance update instantly.

Link to Statutory Requirements

Computerised voucher processing often includes built-in modules for GST, TDS and other statutory returns. Taxable value, tax rate and tax amount are computed automatically and posted to tax control ledgers.

Audit Trail & Evidence

Each voucher carries metadata (who entered, modified, approved, timestamps) and links to scanned documents. This provides strong evidence for audits and helps trace errors.

Summary

Voucher and transaction processing in a computerised accounting system provide a structured, controlled, and auditable way to capture, validate, authorise and post business transactions into the accounting records with speed and accuracy.

Overview
In a computerised accounting system, 'Books and Records' are the electronic equivalents of traditional ledgers, journals and subsidiary books. 'Automated Posting' is the process by which transactions entered once (via a voucher, invoice or data-entry screen) are automatically routed and recorded into the appropriate accounts, sub-ledgers and reports without manual transfer.

Components (Books & Records)

• Source documents: invoices, receipts, purchase orders, payment advices — the primary evidence of transactions.
• Vouchers/Journal entries: transaction entry screens that capture date, accounts, amounts, narration, tax codes, cost centres.
• Subsidiary books / sub-ledgers: accounts receivable (customer ledger), accounts payable (supplier ledger), inventory records, fixed asset register, payroll register.
• General ledger: consolidated control accounts that receive automated postings from sub-ledgers.
• Audit trail & logs: time-stamped records showing who entered, edited or deleted transactions (critical for internal control).

How Automated Posting Works (Process Flow)

1. Capture: enter transaction via invoice/voucher screen or import from POS/bank feed.
2. Validation: system checks mandatory fields, GST/VAT rates, account codes and available stock or credit limits.
3. Mapping rules: based on transaction type the system applies posting rules (e.g., Sales Invoice → Debit Accounts Receivable, Credit Sales).
4. Auto-post: entries are written simultaneously to the appropriate sub-ledger and to control accounts in the general ledger.
5. Aggregation & reports: trial balance, aged receivables/payables, stock valuation and financial statements update in real time.
6. Audit trail & reversal: system records origin and allows authorised reversing entries or credit notes with traceability.

Advantages of Automated Posting

• Speed and efficiency — one entry updates many books instantly.
• Reduced errors — fewer manual transfers and automatic validation rules.
• Real-time information — up-to-date balances, reports and cash position.
• Improved internal control — access rights, edit logs and approval workflows.

Risks & Controls

• Incorrect mapping or configuration can cause systematic errors — mitigate by carefully setting up chart of accounts and posting rules.
• Dependence on source data quality — ensure validation, mandatory fields and exception reporting.
• Segregation of duties and approval workflows must be implemented to prevent fraud.

Practical notes for students
Understand the mapping between vouchers and ledger accounts, be able to trace a transaction from source document to final report, and recognise how automated posting preserves the fundamental double-entry accounting principle (every debit has a corresponding credit, recorded automatically).

Concise example flow: Sales invoice entered → system posts: Debit Customer A/c, Credit Sales A/c, calculates GST and posts GST payable, posts cost side: Debit Cost of Goods Sold, Credit Inventory (if integrated).

What is Inventory/Stock Accounting?
Inventory (stock) accounting is the process of recording, valuing and controlling the goods a business holds for sale (finished goods) or for use in production (raw materials & work-in-progress). In a computerised accounting system, stock records are updated automatically as purchase, production and sales transactions are entered.

Objectives

• Ensure correct valuation of closing stock for the balance sheet and correct Cost of Goods Sold (COGS) in the income statement.
• Control physical stock (avoid stock-outs, pilferage, over‑stocking).
• Provide timely management information (reorder levels, slow-moving items, batch/expiry tracking).

Types of stock

• Raw materials
• Work in Progress (WIP)
• Finished goods
• Stores & spares

Inventory systems

• Periodic system: Physical count at period end; COGS = Opening stock + Purchases – Closing stock.
• Perpetual system: Stock quantity and value updated real‑time on each purchase/sale/issue—standard in computerised accounting software.

Common valuation methods

• FIFO (First In First Out): Oldest costs assigned to COGS first.
• LIFO (Last In First Out): Latest costs assigned to COGS first (note: disallowed under some accounting standards, but taught conceptually).
• Weighted Average Cost: Average cost per unit after each purchase or for the period.
• Specific Identification: Track exact cost for distinct items (e.g., vehicles, jewellery).
• Retail method: Used by retail businesses to estimate ending inventory using retail-to-cost ratios.
• Lower of Cost and Net Realisable Value (LCNRV): Stock is carried at the lower of cost and NRV (NRV = estimated selling price – costs to complete & sell).

Computerised accounting features for inventory

• Real‑time stock updates linked to purchases, sales, returns and production entries.
• Item Master (SKU), batch numbers, expiry dates, serial numbers and barcodes.
• Multiple valuation methods selectable (FIFO, Wt. Avg.).
• Automatic generation of GRN, stock ledger, bin cards and stock issue vouchers.
• Reorder point/manual/automatic reorder, alerts for low stock, expiry warnings.
• Reports: stock summary, ageing, slow‑moving items, stock movement, valuation and margin analysis.

Accounting entries (typical, simplified)

• Purchase (on credit): Purchase A/c Dr; Accounts Payable Cr. (Stock quantity updated in system)
• Sales: Accounts Receivable Dr; Sales Cr. + Cost of Goods Sold Dr; Inventory Cr. (perpetual system)
• Stock adjustment (shrinkage/damage): Inventory Dr/Cr; Loss on stock/Stock adjustment Cr/Dr

Internal controls & records

• Purchase orders, Goods Received Note (GRN), Bin cards, Stock ledger, Periodic physical verification (cycle counts).
• Segregation of duties, barcode scanning, access controls in software, audit trail.

Key management measures

• Reorder level and safety stock to avoid stockouts.
• ABC analysis to prioritise control effort: A – high value/low volume, B – medium, C – low value/high volume.
• Stock turnover and ageing analysis to identify slow‑moving items and obsolescence.

Effect on financial statements
Inventory valuation affects closing stock (current assets) and COGS (expense). Choice of valuation method changes profit and tax in periods of changing prices.

What it is
Banking and Reconciliation is the process of matching the company's Cash Book (or bank ledger in the accounting system) with the Bank Statement (Pass Book) to find and explain differences. In a computerised accounting system, the ledger shows transactions entered by the business while the bank provides a statement of transactions it has processed. Reconciling ensures the accounting records are complete and accurate and helps detect errors, omissions and fraud.

Why differences arise

• Timing differences: cheques issued but not yet presented (outstanding cheques); deposits made but not yet credited by the bank (deposits in transit).
• Bank-initiated entries not recorded in books: direct credits (collections), direct debits (standing instructions, loan EMIs), bank interest, bank charges.
• Dishonoured (bounced) cheques previously recorded in Cash Book as receipts.
• Errors: mistakes in the cash book, or errors made by the bank in the pass book.

Objective
To prepare a Bank Reconciliation Statement (BRS) which reconciles the balance shown by the company’s Cash Book (or the bank ledger in the accounting software) with the balance shown in the Bank Statement (Pass Book).

Procedure (typical steps)

1. Obtain balance as per Cash Book (ledger balance) and balance as per Bank Statement.
2. Compare transactions one-to-one: match deposits/credits and withdrawals/debits.
3. Identify items recorded in Cash Book but not yet appearing in Pass Book: usually outstanding cheques (deductions) and deposits in transit (additions).
4. Identify items appearing in Pass Book but not recorded in Cash Book: bank charges, direct credits, direct debits, interest, dishonour of cheques.
5. Adjust the Cash Book for items the bank has recorded but the company hasn’t (make journal entries in the accounting system where required).
6. Prepare the Bank Reconciliation Statement by adjusting either the Cash Book balance or the Pass Book balance for the identified items; both adjusted balances must agree.
7. Investigate and correct any errors found (in books or by contacting the bank).

Computerised accounting features

• Import bank statements (CSV, MT940) and auto-match transactions to ledger entries.
• Auto-suggest matches for payments and receipts, flag unmatched items, and allow bulk clearing of reconciled items.
• Reconciliation reports by date, account, and reason code; audit trail of reconciliation actions.
• Automatic posting of recurring bank fees, standing instructions, and interest entries when configured.

Internal control & practical benefits
Regular reconciliation improves cash control, detects unauthorised transactions early, ensures bank charges/interest are captured, and provides reliable bank balances for decision-making and statutory reporting.

Payroll Processing is the series of steps a business follows to calculate employee wages/salaries, statutory and voluntary deductions, employer contributions, generate payslips, make payments and record accounting entries. In a computerised accounting system payroll is automated using software which ensures accuracy, compliance and timely reporting.

Key components

• Salary structure: Basic pay, Dearness Allowance (DA), House Rent Allowance (HRA), other allowances (conveyance, medical, special), overtime, bonuses.
• Gross salary: Total of all earnings before deductions.
• Deductions: Statutory (Provident Fund, ESI, Professional Tax, TDS) and voluntary (loan EMIs, insurance, employee contributions).
• Employer contributions: Employer’s share of PF, ESI and other benefits — these increase the employer’s cost.
• Net pay: Amount payable to employee after deductions.
• Payslip: Document showing earnings, deductions and net pay for each pay period.

Typical steps in payroll processing

1. Collect attendance/time-sheet and leave, calculate days worked and overtime.
2. Compute gross salary for the period (monthly/weekly).
3. Compute statutory & voluntary deductions as per applicable rates and thresholds.
4. Compute employer contributions.
5. Generate payslips and pay advice; transfer net pay by bank or cash.
6. Make payments to statutory authorities (PF, ESI, TDS) within due dates.
7. Pass accounting entries (salary expense, liabilities for deductions and contributions, bank payments).
8. Maintain records for audits, produce payroll reports and returns.

Payroll accounting entries (simple format)

• On salary computation:
  • Salary Expense A/c Dr (Gross Salary)
  • To Provident Fund Payable A/c (Employee PF)
  • To ESI Payable A/c (Employee ESI)
  • To Professional Tax Payable A/c
  • To TDS Payable A/c
  • To Bank/Cash A/c (Net Pay)
• For employer contributions:
  • Employer PF Expense A/c Dr
  • Employer ESI Expense A/c Dr
  • To PF Payable A/c (Employer)
  • To ESI Payable A/c (Employer)
• On payment of liabilities:
  • Provident Fund Payable A/c Dr
  • To Bank/Cash A/c

Statutory compliance notes

• Rates and thresholds for PF, ESI, professional tax and TDS change from time to time. Always use current government rates.
• Maintain statutory registers and file returns within prescribed due dates to avoid penalties.

Advantages of computerised payroll

• Faster calculation, fewer errors, automated statutory calculations and report generation.
• Secure record-keeping, easy retrieval of payslips and reports for audits.
• Integration with attendance systems and accounting ledgers reduces manual entries.

Example payslip layout (fields)

• Employee name, ID, designation, pay period
• Earnings: basic, DA, HRA, allowances, overtime
• Deductions: PF, ESI, PT, TDS, loans
• Net pay and payment mode

Points for controls

• Segregation of duties (attendance, payroll processing, approvals, payment).
• Access controls in payroll software and regular reconciliation of payroll ledger with bank statements.

All calculations, journal entries and payslip generation are typically handled by payroll modules in computerised accounting systems which also produce compliance reports and statutory returns.

Overview
Taxation and compliance in a computerised accounting system covers recording tax-related transactions, calculating tax automatically (primarily GST in India), maintaining statutory ledgers, generating tax invoices and e‑invoices where applicable, preparing and reconciling returns, and ensuring timely payment and filings. The accounting software automates computations, populates statutory reports and helps meet compliance deadlines.

Key components of GST

• Types of tax: For supplies within a state the tax is split as CGST (central) + SGST (state). For inter-state supplies it is IGST (integrated).
• Taxable event: Supply of goods or services for consideration.
• Taxable value: The value on which GST is charged (transaction value less allowable discounts, excluding tax itself).
• Time of supply: Determines the tax period for recording and reporting (e.g., invoice date, payment date—rules differ for goods and services).
• Place of supply: Determines whether CGST+SGST (within state) or IGST (inter-state) applies.

Input Tax Credit (ITC)
ITC allows taxpayers to set off tax paid on purchases against tax collected on sales, subject to conditions: purchase from a registered supplier, possession of tax invoice/debit note/e-invoice, receipt of goods/services, tax paid to government, and use for business. Certain supplies (like personal consumption, motor vehicles in many cases, exempt supplies) are ineligible.

Invoicing & e‑invoicing
A tax invoice must show taxable value, GST rate and tax amount, and type of tax (CGST/SGST or IGST). Where e‑invoicing is mandated, B2B invoices must be uploaded to a government portal to get a unique IRN before issuing; the accounting software typically integrates e‑invoicing APIs.

Returns and reconciliation
Software generates periodic returns (summary returns and detailed returns). Returns must be reconciled with purchase records and supplier filings (auto-populated dashboards like GSTR-2A/2B help). The typical process in a computerised system: record invoice -> system computes GST -> classify as intra/inter-state -> post to tax ledgers -> generate return -> reconcile with vendor/sales registers -> make payment.

Other taxes and compliance items
Besides GST, computerised systems may handle TDS (tax deducted at source on payments), TCS, customs duties, excise (legacy/where applicable), and local taxes. Systems maintain separate ledgers, prepare TDS returns and certificates, and produce statutory reports required for audits.

Penalties and interest
Non-compliance (late filing, short payment, wrong claim of ITC) attracts interest and penalties. Computerised systems help reduce errors by validation rules (GSTIN format checks, HSN/SAC code validation, rate validation).

Benefits of computerised handling

• Automatic tax calculation and split (CGST/SGST or IGST).
• Auto-population of returns and statutory reports.
• Faster reconciliation and detection of mismatches.
• Less manual errors and easier audit trail.

Best practices

• Maintain timely and complete invoices with correct GSTIN and HSN/SAC codes.
• Reconcile purchases with supplier returns regularly (monthly).
• Keep separate ledgers for output tax, input tax, and reverse charge liabilities.
• Use software validation for rate eligibility and e‑invoice/e‑way requirements.

What are Final Accounts?
Final accounts are the set of accounting statements prepared at the end of an accounting period to show the trading results and financial position of an enterprise. They typically include:

• Trading Account – to calculate gross profit or loss from buying and selling goods.
• Profit & Loss Account – to show operating and non-operating incomes and expenses to arrive at net profit or loss.
• Balance Sheet – to present assets, liabilities and capital at a particular date.

Purpose of Final Accounts: assess profitability, show financial position, comply with statutory requirements, and provide information for decision-making by owners, lenders, investors and regulators.

Final Accounts in a Computerised Accounting System
Computerised accounting software (e.g., Tally, QuickBooks, Zoho Books) automates many steps that are manual in traditional accounting. Key features include:

• Automated Posting – vouchers entered are auto-posted to ledger accounts.
• Trial Balance Generation – software compiles trial balance from ledgers automatically.
• Auto-adjustments – recurring entries (depreciation, provisions), stock valuation and tax calculations can be scheduled.
• Real-time Final Accounts – trading, profit & loss and balance sheet are produced instantly on valid data.
• Audit trail & controls – user roles, change logs and validation rules reduce errors and improve data integrity.

Key Accounting Adjustments handled by software: closing stock, depreciation, outstanding/prepaid expenses, accrued income, unearned income, outstanding/unpaid incomes, bad debts & provisions, suspense/rectification entries, and inventory valuation (FIFO/LIFO/Weighted Average where supported).

Steps (typical computerized workflow):

1. Record vouchers (sales, purchases, receipts, payments, journals).
2. Software auto-posts to ledger and updates inventory and GST/VAT records.
3. Run trial balance & review exception reports (unbalanced entries, negative stock).
4. Enter year-end adjusting entries (depreciation, provisions, accruals).
5. Generate final accounts (Trading, P&L, Balance Sheet) and financial reports (ratio analysis, schedules).
6. Export/print reports for stakeholders and filing.

Advantages of Computerised Final Accounts: speed, accuracy, instant reports, standardized formats, easier compliance, backup & recovery, ability to drill-down to source vouchers.

Limitations: relies on correct data entry and correct configuration (accounts, tax codes, depreciation methods). Software cannot replace accounting judgement — adjustments and interpretations still need human review.

Financial Reporting
Financial reporting is the communication of financial information to users through statements and notes. It should be relevant, reliable, comparable and understandable. In a computerised system, financial reporting includes schedules, notes to accounts, comparative statements and management information (budgets vs actuals).

Compliance and Presentation: Final accounts must follow applicable accounting standards and statutory formats. Computerised systems often offer templates aligned to local reporting requirements (e.g., formats prescribed by law).

What is a Database and DBMS?

A database is an organized collection of related data (tables, records, fields) used to store accounting information such as ledgers, vouchers, inventory and customer details. A Database Management System (DBMS) is software that creates, manages and controls access to the database — it handles storage, retrieval, update, security, backup and concurrency.

Why DBMS is important in Computerised Accounting System (CAS)

• Centralised storage: all accounting data (journals, ledgers, masters) are stored in one place.
• Data integrity and consistency: DBMS ensures accurate and consistent data (constraints, keys, transactions).
• Multi-user access and concurrency control: many users (data entry, manager, auditor) can work simultaneously without corrupting data.
• Security and access control: roles and privileges prevent unauthorized access to accounting records.
• Reliable backup & recovery: automatic backups and recovery mechanisms protect financial data.
• Fast queries and reporting: generate financial statements, trial balance and custom reports quickly using queries and indexes.

Core concepts and objects

• Table (relation): stores a type of entity, e.g., Account, Voucher, Inventory.
• Record/Row: one instance, e.g., one voucher entry.
• Field/Column: attribute, e.g., AccountName, Amount, Date.
• Primary Key: unique identifier for a row (e.g., VoucherID).
• Foreign Key: links tables (e.g., Voucher.AccountID -> Account.AccountID).
• Indexes: speed up search on key columns (e.g., index on Date, AccountID).
• Views, Stored Procedures and Triggers: reusable queries, business logic and automatic actions (e.g., update stock on sale).

Relationships

Common relationship types in accounting databases:

• One-to-one: e.g., Company -> CompanyDetails (rare).
• One-to-many: e.g., Account -> Voucher (an account can have many vouchers).
• Many-to-many: e.g., Invoice <-> Item (resolved via InvoiceItems table storing quantity & rate).

Transactions and ACID properties (critical for accounting)

A transaction is a logical unit of work (e.g., entering a sales invoice). ACID ensures reliable transactions:

• Atomicity: all parts of the transaction succeed or none do (no partial journal entry).
• Consistency: database moves from one valid state to another (debit = credit).
• Isolation: concurrent transactions don’t interfere (concurrent voucher entries safe).
• Durability: once committed, transaction remains even after crashes.

Normalization (why it matters)

Normalization reduces redundancy and anomalies. In CAS you typically apply 1NF–3NF so master data (Accounts, Items, Parties) are stored once and referenced by keys; this keeps reports and balances accurate.

Typical DBMS operations in CAS

• Data entry: save vouchers, receipts, payments.
• Validation: check account codes, date ranges, amount formats.
• Posting: update ledgers and balances automatically.
• Query & reports: Trial Balance, Profit & Loss, Balance Sheet, Ageing, GST reports.
• Reconciliation & audit trails: timestamped changes and user IDs for each entry.

Example schema (conceptual)

• Account(AccountID PK, AccountName, Type)
• Voucher(VoucherID PK, Date, TotalDebit, TotalCredit, CreatedBy)
• VoucherLine(LineID PK, VoucherID FK, AccountID FK, Debit, Credit, Narration)
• Item(ItemID PK, Name, Rate, StockQty)

How DBMS improves real accounting tasks

• Automatic balancing: voucher lines must sum to equal debit and credit before commit.
• Fast consolidated reports: compute monthly sales, expenses using aggregate queries.
• Controlled access: clerks can enter vouchers; managers approve; auditors view read-only.

Best practices in CAS with DBMS

• Enforce primary/foreign keys and transactions for financial integrity.
• Index frequently queried columns (Date, AccountID) to speed reports.
• Keep master data normalized; use views for reporting-friendly joins.
• Schedule regular backups and test recovery procedures.

Overview
Security, internal controls and audit trail are essential elements of a computerised accounting system. They protect accounting data from loss, theft or manipulation, ensure accuracy and reliability of financial information, and provide evidence of transactions and changes for review and audit.

Objectives

• Safeguard assets and data integrity.
• Ensure completeness, accuracy and timeliness of accounting records.
• Prevent and detect errors and fraud.
• Provide a reliable record (audit trail) to support verification and compliance.

Types of Controls

• Preventive controls — stop errors or fraud before they occur (examples: passwords, access rights, segregation of duties, physical locks).
• Detective controls — identify errors or irregularities after they occur (examples: exception reports, reconciliations, log monitoring).
• Corrective controls — restore systems or data and fix problems (examples: backups, restore procedures, patching).

Components of an Internal Control System (COSO-style)

• Control environment — management tone, policies and ethics.
• Risk assessment — identify what could go wrong (data breaches, unauthorized changes).
• Control activities — specific policies and procedures (authorisations, approvals, reconciliations).
• Information & communication — timely, reliable reporting and communication channels.
• Monitoring — review and update controls (internal audit, management review).

Computer-specific Controls

• General IT controls (GITCs) — environment around IT: physical security, network firewalls, system backups, change management, user administration.
• Application controls — built into accounting applications to ensure transaction accuracy: input validation (format checks, range checks), processing controls (sequence checks, hash totals), output controls (report reconciliation), authorization checks.

Audit Trail
An audit trail is a chronological record that traces the detailed transactions and changes in the accounting system from origin to final output. It documents who did what, when and how. A good audit trail contains source documents (invoices), transaction records, change logs, approval records and system logs.

Key Features of a Reliable Audit Trail

• Uniquely identify each transaction (transaction ID, timestamp).
• Record actor (user ID), action performed (create, modify, delete), time and IP or workstation.
• Store original and modified values when changes occur (before/after).
• Be tamper-evident (write-once logs or secure hash chaining).

Processes and Best Practices

• Segregation of duties: separate authorization, recording and custody roles (e.g., one person orders goods, another records them, another approves payments).
• Least privilege: give users only the access they need.
• Strong authentication: complex passwords, multi-factor authentication (MFA).
• Encryption of sensitive data at rest and in transit.
• Regular backups and tested restore procedures; maintain offsite copies.
• Automated logging and regular review of logs; keep logs for required retention periods.
• Version control and change management for application updates.
• Regular reconciliations (e.g., bank reconciliations) and exception reporting.

Compliance and Audit
Audit trails support internal and external audits, legal discovery and regulatory compliance (tax laws, data protection rules). Auditors use audit trails to verify transaction authenticity, trace errors and detect fraud.

Limitations
No control is perfect. Controls can be bypassed if not properly designed or monitored, and audit trails are useful only if they are complete, protected and regularly reviewed.

Overview: Backup, Recovery and Disaster Management is the set of processes and technologies used to protect accounting data in computerised systems, to restore it after failures, and to ensure business continuity when major incidents occur. It includes creating copies of data (backups), restoring data and systems (recovery), and planning/responding to large-scale events (disaster management).

Key concepts:

• Backup: Making a copy of data so it can be restored after data loss. Backups may be stored on local media, offsite, or in the cloud.
• Recovery: The process of restoring lost or corrupted data and returning systems to normal operation. Measured by Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
• Disaster Management: Planning and actions to prevent, prepare for, respond to and recover from major incidents (e.g., fire, flood, ransomware, prolonged power outage).

Types of backups:

• Full backup: Complete copy of all selected data. Fastest to restore, needs most storage and time to create.
• Incremental backup: Backs up only data changed since the last backup of any type. Efficient storage/time for backup but slower restore (requires full + each incremental).
• Differential backup: Backs up data changed since the last full backup. Restore faster than incremental (full + latest differential) but grows over time until next full.

Backup media and locations: Local disk, network-attached storage (NAS), tape, removable drives, and cloud storage. Important principle: the 3-2-1 rule — keep 3 copies of data, on 2 different media, with 1 copy offsite.

Recovery strategies and sites:

• Cold site: Alternate site with infrastructure but no live data or active systems. Cheapest, longest recovery time.
• Warm site: Partially configured site with data backups and some systems. Moderate cost and recovery time.
• Hot site: Fully configured and synchronized site with near-immediate failover. Expensive, minimal downtime.

Disaster management phases:

1. Prevention/Mitigation: Reduce risk (UPS, fire suppression, network segmentation, patching, anti-malware).
2. Preparedness: Create backup schedules, disaster recovery plan (DRP), assign roles, maintain contact lists, and test procedures.
3. Response: Activate DRP, communicate with stakeholders, contain damage (isolate infected systems), begin recovery steps.
4. Recovery: Restore systems and data from backups, verify integrity, resume normal operations, perform post-incident review.

Best practices:

• Follow the 3-2-1 backup rule.
• Encrypt backups and secure access controls.
• Automate backups and monitor for failures.
• Document procedures and maintain an up-to-date DRP.
• Regularly test restores (periodic restore drills) to ensure backups are usable.
• Define and agree RTO and RPO based on business needs and cost trade-offs.
• Keep at least one offsite or cloud copy to protect against site-level disasters.

Accounting-system-specific considerations: For computerized accounting, backups should include the accounting database files, application configuration, transaction logs, and any custom reports. Maintain sequential backup logs and reconcile backup lists with accounting cycles (e.g., end-of-month full backup before financial close).

Testing and compliance: Periodic table-top exercises and full restore tests validate procedures. Compliance requirements (tax, audit) may mandate retention periods and secure storage of accounting records.

Summary: Effective backup, recovery and disaster management ensure that accounting records are protected, recoverable within acceptable time and data-loss limits, and that the organization can continue critical accounting operations after incidents.

Overview
Implementation, migration and data conversion are interlinked activities when an organisation moves from manual accounting or an old accounting software to a new computerised accounting system. Implementation is the process of installing and configuring the new system. Migration is the planned move of processes and users from the old system to the new one. Data conversion is the technical process of transforming accounting data (master and transactional) from the old format to the new system’s format.

Key steps in implementation

• Planning and requirement analysis: Define objectives, scope, users and modules (sales, purchases, ledger, inventory).
• Selection and configuration: Choose software and configure chart of accounts, tax settings, and user roles.
• Customisation and testing: Apply required customisations and perform unit/system tests.
• Training and documentation: Train users and prepare user manuals and SOPs.
• Go-live and support: Move to production, provide helpdesk and monitor performance.

Migration strategies

• Big Bang: Entire system switches to new software on a single cut‑over date (fast but higher risk).
• Phased: Modules or departments move in stages (lower risk, longer duration).
• Pilot: Start with a small business unit to validate before full roll-out.
• Parallel run: Old and new systems run together for a period to compare results (safe but resource intensive).

Data conversion process

1. Data discovery: Identify what to convert — opening balances, master data (customers, suppliers, items), historical transactions, opening inventory.
2. Mapping: Map old chart of accounts and fields to the new system’s accounts and fields (account codes, GST/VAT types, cost centers).
3. Extraction: Export data from the old system (CSV, Excel, XML, database dump).
4. Cleaning & validation: Remove duplicates, correct errors, standardise names, check account classifications.
5. Transformation: Convert data formats, recalculate balances if needed (currency, period adjustments), aggregate or split records per mapping rules.
6. Loading/Import: Import into the new system via import utilities, APIs or ETL tools; or enter manually where necessary.
7. Reconciliation & testing: Reconcile trial balances, lists and totals between old and new systems; perform sample transaction checks and UAT.
8. Go-live & cut-over: Freeze source data at cut-off, do final migration, and start processing in the new system.

Common issues and controls

• Missing or duplicate records — use validation rules and deduplication routines.
• Incorrect account mapping — maintain a clear mapping table and test sample ledgers.
• Rounding and currency conversion differences — document rounding rules and exchange rate sources.
• Loss of audit trail — preserve source reports and keep read-only archive of old system.
• Inadequate backup & rollback plan — always take backups before each major conversion step and have a tested rollback procedure.

Testing types

• Unit testing (each conversion script / import).
• System testing (end-to-end accounting workflows).
• User Acceptance Testing (UAT) by actual users.
• Reconciliation testing (trial balance, ledger totals, tax reports).

Post-implementation activities
Monitor data integrity, resolve user queries, compare periodic financials to expected results, and update documentation. Maintain both systems in read-only mode if required for audit purposes.

Learning points for Class 11 students
Understand the need for accurate mapping of accounts, importance of backups, difference between migration strategies, and why reconciliation (trial balance equality) is essential after conversion.

Overview: A Computerised Accounting System (CAS) automates recording, processing and reporting of financial transactions. While CAS increases speed, accuracy and reporting capability, it requires specific controls to ensure integrity and introduces limitations and risks that must be managed.

Controls in CAS

• Access controls - User IDs, strong passwords, role-based access control (RBAC) so users only perform permitted tasks.
• Input controls - Validation checks: range checks, type checks, mandatory fields, dropdowns and input masks to prevent bad data entry.
• Processing controls - Reconciliation routines, control totals (hash totals), and edit checks to ensure calculations and batch processing are correct.
• Output controls - Review and authorization of reports, restricted distribution of sensitive outputs and print controls.
• Audit trail and logging - Detailed logs of who changed what and when to support audits and detect fraud.
• Segregation of duties - Separate data entry, authorization and reconciliation duties to reduce fraud risk.
• Backup and recovery - Regular automated backups, offsite storage, and tested restore procedures (RTO and RPO defined).
• Change management - Controlled updates, testing in a non-production environment and documented approvals.
• Security measures - Firewalls, encryption (data at rest and in transit), antivirus and intrusion detection/prevention systems.
• Periodic audits and monitoring - Internal and external audits, continuous monitoring of logs and exception reports.

Limitations of CAS

• Cost - Initial setup, licensing, hardware, and skilled staff are expensive for small organisations.
• Dependence on technology - Power outages, network failures or hardware faults can halt accounting operations.
• Software defects - Bugs or incorrect configuration can produce incorrect outputs.
• Need for trained staff - Users must be trained; human errors still occur (wrong master-data, wrong mapping).
• Obsolescence - Rapid technological change may require frequent upgrades or migrations.
• Limited flexibility - Predefined workflows may not suit special transactions without customization.

Risks in CAS

• Unauthorized access and data theft - Weak access controls can lead to confidential data leakage.
• Data alteration and fraud - Malicious users may manipulate records unless audit trails and segregation are enforced.
• Ransomware and malware - Can encrypt or corrupt financial records; backups and endpoint security are critical.
• System failure and downtime - Causes business interruption and delayed reporting.
• Data loss and corruption - Incomplete backups or failed restores can lead to permanent loss.
• Privacy and compliance risks - Incorrect handling of personal/financial data can breach laws (e.g., data protection rules).
• Third-party/vendor risks - Cloud or outsourced providers may introduce continuity, security or privacy exposures.

Mitigation / Best Practices

• Design strong access control and role separation; enforce multi-factor authentication for critical functions.
• Implement strict input validations, reconciliation procedures and automated exception reporting.
• Maintain regular, tested backups (including offsite copies); define and practice disaster recovery plans (RTO/RPO).
• Keep software patched, use reputable security tools and restrict administrative rights.
• Document change management, conduct periodic internal/external audits and continuous monitoring of logs.
• Train users regularly on procedures, security and fraud awareness.

Summary: A CAS improves accounting efficiency and accuracy, but only if adequate controls are implemented to reduce its limitations and risks. Regular monitoring, backups, segregation of duties and strong security are essential to maintain trustworthiness of computerized accounting.

Meaning and Scope

Audit of Computerised Accounting Systems is the process of examining and evaluating the controls, records and procedures of an organisation whose accounting information is processed by computers. The aim is to ensure accuracy, completeness, integrity and security of financial data and reports produced by the system.

Objectives

• Verify reliability and accuracy of financial records produced by computer systems.
• Ensure completeness and validity of transactions (no unauthorised or missing records).
• Evaluate strength of internal controls (general and application controls).
• Detect and prevent fraud, data manipulation and security breaches.
• Confirm adequate backup, recovery and business continuity arrangements.

Types of Controls

Controls in a computerized environment are normally grouped into General Controls and Application Controls.

General Controls

• Access controls: user IDs, passwords, multi-factor authentication, role-based access.
• Physical & environmental controls: restricted access to servers, fire suppression, temperature control.
• Change management: authorised development, testing and migration of software changes.
• Backup & recovery: scheduled backups, off-site storage, periodic restore testing.
• System operations: job scheduling, logging, antivirus, patch management and system monitoring.

Application Controls

• Input controls: validation checks, edit checks, completeness checks and authorised entry.
• Processing controls: sequence checks, batch totals, error handling and reconciliations.
• Output controls: reports distribution, reconciliation of printed reports to electronic totals.
• Master-file controls: restricted modification of rate/price lists, customer or supplier master data.

Audit Approach and Procedures

Typical audit steps:

1. Planning: understand the business processes, systems in use (ERP, Tally, bespoke), and identify risks.
2. Risk assessment: evaluate material risks due to system weaknesses or fraud.
3. Evaluate internal controls: assess design and implementation of general and application controls.
4. Tests of controls: observe, inspect logs, examine change records, test user access, and review backups.
5. Substantive testing: vouching, confirmation, re-performance, data extraction and analytical procedures.
6. Use of CAATs: Computer Assisted Audit Techniques — data analytics, full-population testing, hash comparisons, parallel simulation and test data.
7. Reporting: document findings, recommend improvements and follow up on remediation.

Evidence and Audit Trail

Audit evidence in computerized systems includes system logs, access lists, change control records, backup tapes/files, configuration settings, reconciliation reports, electronic signatures, and hash values. Maintaining and reviewing an audit trail (transaction records from input to output) is critical for traceability.

Common Risks & Weaknesses

• Unauthorised access and inappropriate segregation of duties.
• Weak change control allowing untested code into production.
• Inadequate backups or inability to restore data.
• Missing or incomplete audit trails due to log purging or manipulation.
• Over-reliance on system reports without independent verification.

Best Practices for Controls

• Segregation of duties: separate system development, operations and record-keeping functions.
• Least privilege: users have only the access needed to perform duties.
• Regular user access reviews and timely removal of ex-employee accounts.
• Encrypt sensitive data in transit and at rest; use secure passwords and MFA.
• Periodic DR (Disaster Recovery) and backup restoration tests.
• Maintain detailed change logs and require approvals for changes to master files.

Reporting and Follow-up

Audit reports should list weaknesses by risk level, recommended remedial actions, responsible persons and timelines. Follow-up audits verify that corrective actions have been implemented.

Definition: Coding and numbering systems are structured methods used in computerized accounting to identify, classify and retrieve accounting records, documents and items. "Coding" assigns a code (which may be alphabetic, numeric or alphanumeric) that carries meaning; "numbering" usually refers to simple sequential unique identifiers.

Objectives / Benefits:

• Ensure unique identification of vouchers, accounts, invoices and items.
• Support quick classification and grouping (e.g., assets, liabilities, revenue).
• Improve data-entry speed and reduce mistakes through standardization.
• Make retrieval, reporting and auditing efficient.
• Allow automation (validation rules, check-digits) and error detection.

Common types of systems:

• Sequential numbering: Simple incrementing numbers for invoices, vouchers, receipts (e.g., 000001, 000002...). Ensures uniqueness and audit trail.
• Block coding: Reserve number ranges for major groups (e.g., 1000–1999 for Assets, 2000–2999 for Liabilities).
• Group (or structured) coding: Code composed of fields where each field has meaning (e.g., 1.01.005 where 1 = Assets, 01 = Current Assets, 005 = Cash).
• Mnemonic coding: Short meaningful codes using letters (e.g., CASH, BANK, INV) that are easy to remember.
• Alphabetic / Alphanumeric: Combines letters and numbers for compact expressive codes (e.g., INV-2025-000123, SKU-ELEC-0234).
• Significant-digit / Hierarchical coding: Leading digits identify primary group, subsequent digits identify sub-groups (useful in chart of accounts).

Principles of a good coding/numbering system:

• Uniqueness: each code identifies a single entity only.
• Simplicity and memorability: easy to use and minimally prone to input errors.
• Scalability & flexibility: leave room for future additions (reserve unused ranges).
• Consistency & standardization: uniform application across organization.
• Meaningfulness where useful: codes should, when possible, convey the category or type.
• Validation capability: include check digits or format checks to detect typing errors.

Error detection & check digits: In accounting systems, codes may include check digits computed by a formula (modulus arithmetic) to detect common transcription errors. For example, Modulus-11 or Luhn algorithm (mod 10) are used to compute a control digit appended to a code.

Implementation tips: Document the coding rules, train users, automate generation (software should auto-assign sequential numbers and validate structure), and avoid changing codes once used (use new codes instead of renaming).

Example code structures commonly used in Chart of Accounts:

• Single-level numeric: 100 = Cash, 200 = Accounts Payable.
• Multi-level hierarchical: 1.01.005 where - 1 = Assets; 01 = Current Assets; 005 = Cash.
• Alphanumeric invoice: INV-2025-000123 where INV = invoice prefix, 2025 = year, 000123 = sequential number.

Overview
In a computerised accounting system, Reports, Queries and MIS (Management Information System) are tools that convert transaction data into meaningful information for operational control and managerial decision-making.

Reports
Reports are structured outputs generated from the accounting system. Typical accounting reports include Day Book, Cash Book, Bank Book, Ledger, Trial Balance, Profit & Loss Account, Balance Sheet, Inventory Reports, GST and tax returns, Receivables (Debtors) and Payables (Creditors) reports. Reports can be standard (predefined) or customised and are usually exported as PDF, Excel or shown on dashboards.

Queries
Queries are requests to the database to retrieve specific information. They can be simple filters (e.g., unpaid invoices) or aggregated queries (e.g., monthly sales totals). Queries enable drill-down, ad-hoc analysis and data extraction for further processing. In many accounting packages queries are built with search panels or via SQL-like statements.

MIS (Management Information System)
MIS organises reports and queries into a coherent set of metrics and dashboards for management. MIS focuses on KPIs (Key Performance Indicators), trends, exceptions and variances (budget vs actual). MIS helps managers monitor performance, spot issues early and take corrective actions.

Characteristics & Best Practices

• Timeliness: Reports must be produced on schedule (daily cash position, monthly financials).
• Accuracy: Source data, reconciliation and validations are essential.
• Relevance: Include only meaningful KPIs and avoid data overload.
• Drill-down & Audit Trail: Users should go from summary to transaction level.
• Automation: Schedule report generation and distribution to reduce manual work.

How they work together
Transactions are recorded → database stores entries → queries extract or aggregate data → reports format the data for stakeholders → MIS compiles dashboards and interprets trends/variance for decision-making.

Computerised accounting systems bring speed and accuracy, but they require careful planning, controls and ongoing maintenance. This topic covers practical considerations when selecting and running accounting software, and best practices to ensure data integrity, security, compliance and usefulness.

1. Selection and planning: Choose software that fits business size, industry and future growth. Check features (ledgers, inventory, GST/Tax modules, payroll, reporting), scalability, integration ability (CRM, bank feeds, POS) and vendor support. Consider cloud vs on‑premises: cloud reduces hardware upkeep and enables remote access; on‑premises may give more control over data.

2. Implementation and data migration: Prepare a clean Chart of Accounts, standardise ledgers and master data (customers, suppliers, items) and map old account codes to new ones. Test data import on a copy, reconcile opening balances and trial balance before going live.

3. Security and access control: Use strong password policies, role‑based access (segregation of duties), two‑factor authentication if available, and limit administrative privileges. Apply encryption for data at rest and in transit, and secure physical access to servers/workstations.

4. Backups and disaster recovery: Implement automated regular backups (daily incremental + weekly full), keep copies offsite or in cloud, and periodically test restores. Have a documented disaster recovery plan with Recovery Time Objective (RTO) and Recovery Point Objective (RPO).

5. Internal control and audit trails: Ensure the system maintains immutable audit trails (who changed what and when). Segregate duties (e.g., persons making payments should not reconcile bank statements). Enable user activity logs and periodic review by management or internal audit.

6. Reconciliation and periodic checks: Perform routine reconciliations: bank, creditors, debtors, stock and GST/tax returns. Schedule monthly/quarterly checks and correct errors timely. Reconcile inter‑company and control accounts regularly.

7. Updates, patches and vendor support: Keep software and OS updated for security and compliance. Plan updates outside peak business hours and test patches in a non‑production environment when possible. Maintain an active support contract or access to expert help.

8. Training and documentation: Provide role‑based training for users and refreshers after updates. Maintain written procedures (how to enter vouchers, run payroll, backup policy) and a change log for customisations.

9. Compliance and reporting: Configure tax rates, statutory reports and retention policies to meet legal requirements. Keep records in forms required by tax authorities and follow document retention timelines.

10. Performance, capacity and integrations: Monitor system performance (transaction volumes, response times). Archive old data if necessary. Use standard APIs or connectors for point‑of‑sale, e‑banking and inventory systems to avoid manual re‑entry.

11. Best practice checklist (summary):

• Design clear Chart of Accounts and naming conventions.
• Use role‑based access and segregation of duties.
• Automate backups and test restores.
• Maintain audit trails and perform regular reconciliations.
• Keep software and security patches current.
• Document procedures and train users.
• Ensure compliance (GST, TDS, statutory reports).

Following these practical considerations ensures a computerised accounting system is reliable, secure and delivers timely, accurate financial information for decision making.