7.3 Business Transaction Cycles, Procedures, and Accounting Controls
Key Takeaways
- Business accounting operations are structured around four fundamental transaction cycles: the Sales/Revenue cycle, Purchases/Expenditure cycle, Payroll cycle, and Cash/Treasury cycle.
- The purchases and expenditure cycle enforces rigorous segregation of duties and the classic '3-way match' (Purchase Order, Goods Received Note, and Supplier Invoice) to prevent unauthorized payments and supplier billing fraud.
- Cash control combines the petty cash imprest system, which restores a fixed float only against authorised expense vouchers, with bank reconciliations that act as detective controls over timing differences such as unpresented cheques and uncleared lodgments as well as errors between the cash book and the bank statement.
- An unbroken audit trail consists of sequentially numbered source documents, accounting vouchers, and general ledger records that allow any financial statement figure to be traced back to its underlying transaction, and vice versa.
- Accounting packages enforce control over repetitive high-volume processing, databases store shared structured data once, and spreadsheets suit one-off modelling but carry formula, version and audit-trail risks that make them unsafe as the accounting record.
7.3 Business Transaction Cycles, Procedures, and Accounting Controls
Quick Summary: Commercial enterprises process thousands or millions of individual financial transactions every month. To prevent catastrophic fraud, operational chaos, and financial statement misstatement, accounting systems are organized around four core transaction cycles: the Sales/Revenue Cycle, the Purchases/Expenditure Cycle, the Payroll Cycle, and the Cash/Treasury Cycle. Each cycle relies on a sequential chain of standardized source documents, rigorous internal controls—such as the 3-way match in procurement and the imprest system in petty cash—and regular detective reconciliations. These procedural controls preserve an unbroken audit trail, enabling independent auditors and management to trace any figure from the final financial statements back to its originating commercial evidence.
1. Overview of Core Business Transaction Cycles
Transaction cycles represent recurring operational sequences where economic resources are exchanged for goods, services, labor, and cash. By segmenting commercial activity into structured cycles, organizations establish segregation of duties, define mandatory approval thresholds, and generate auditable documentary records.
THE FOUR CORE TRANSACTION CYCLES
1. SALES & REVENUE (Order to Cash)
Customer Order ➔ Credit Check ➔ Dispatch Note (GDN) ➔ Sales Invoice ➔ Cash Receipt
2. PURCHASES & EXPENDITURE (Procure to Pay)
Requisition ➔ Purchase Order (PO) ➔ Goods Received (GRN) ➔ 3-Way Match ➔ Disbursement
3. PAYROLL CYCLE (Hire to Retire / Time to Pay)
Clock Card / Biometrics ➔ Supervisor Sign-Off ➔ Gross Pay ➔ Deductions ➔ Net BACS Pay
4. CASH & TREASURY CYCLE (Liquidity & Banking)
Cash Receipts ➔ Petty Cash Imprest ➔ Electronic Transfers ➔ Bank Reconciliation
2. The Sales and Revenue Cycle: Step-by-Step Documentation and Controls
The sales cycle encompasses all activities from receiving a customer request to banking the final cash settlement:
THE SALES AND REVENUE CYCLE FLOW
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ CUSTOMER ORDER │ ──► │ CREDIT VETTING │ ──► │ SALES ORDER │
│ Receipt of order│ │ Credit limit ok?│ │ Pre-numbered PO │
└──────────────────┘ └──────────────────┘ └─────────┬────────┘
│
▼
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ SALES INVOICE │ ◄── │ CUSTOMER SIGNS │ ◄── │ GOODS DISPATCH │
│ Billing Dept │ │ Delivery proof │ │ GDN generated │
└────────┬─────────┘ └──────────────────┘ └──────────────────┘
│
▼
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ SALES LEDGER │ ──► │ REMITTANCE ADVICE│ ──► │ DEBTOR STATEMENT│
│ Debit Receivable│ │ Cash collected │ │ Monthly review │
└──────────────────┘ └──────────────────┘ └──────────────────┘
- Customer Order Receipt and Credit Vetting: The customer submits a purchase request. Before accepting the order, the credit control department must perform formal credit vetting. For existing clients, the system checks whether the new order will breach the customer's authorized credit limit or if overdue debts exist. Orders exceeding credit limits are frozen pending executive credit approval.
- Sales Order Processing: Upon credit clearance, an official, sequentially pre-numbered Sales Order is generated. Copies are transmitted to the warehouse picking team, shipping, and accounts receivable.
- Goods Dispatch and Fulfillment: Warehouse staff pick inventory items against the sales order. The shipping department packages the goods and generates a Goods Dispatch Note (GDN) (or Delivery Note). Crucially, the customer's receiving agent must sign a copy of the GDN upon delivery, providing legal proof of fulfillment.
- Sales Invoicing: The billing department prepares a sequentially numbered Sales Invoice based on the signed GDN and approved official price lists. The invoice itemizes quantities, unit rates, trade discounts, and sales tax / VAT. The invoice is entered in the Sales Day Book (Books of Prime Entry) and posted as a debit to the customer's account in the Sales Ledger (Accounts Receivable), with credit entries to Sales Revenue and VAT Output Tax.
- Cash Collection and Banking: When the customer remits payment (via electronic bank transfer, cheque, or card), the payment is accompanied by a Remittance Advice detailing which specific invoices are being settled. Accounts receivable credits the customer's ledger account and debits the Cash Book.
- Periodic Debtor Statements: At the end of each month, the company issues a Statement of Account to every credit customer, listing opening balances, invoices billed, payments credited, and net outstanding debt. Customers review statements and query discrepancies, serving as an external detective control.
- Credit Notes: If goods are delivered damaged, incorrect, or returnable under warranty, the company issues an authorized, pre-numbered Credit Note. A credit note reduces the customer's outstanding balance. To prevent fraud, sales representatives must never have the authority to issue credit notes; authorization must rest with an independent manager.
3. The Purchases and Expenditure Cycle: Procurement and the 3-Way Match
The expenditure cycle governs the acquisition of goods, raw materials, and services, culminating in commercial payment:
- Purchase Requisition: An operational department identifies a commercial need and submits a sequentially pre-numbered Purchase Requisition, authorized by the department head within delegated spending limits.
- Supplier Sourcing and Tenders: The purchasing department checks the Approved Vendor List. For major expenditures, competitive tenders or formal supplier price quotations are solicited.
- Purchase Order (PO) Issuance: Purchasing generates an official, sequentially numbered Purchase Order. The PO constitutes a legal contract with the vendor, establishing agreed specifications, delivery dates, unit prices, and settlement terms. Copies are routed to warehouse receiving and accounts payable.
- Goods Receipt and Inspection: Goods arrive at the receiving dock. Receiving personnel count packages, inspect goods for transit damage, and match items against the supplier's delivery note. Receiving staff generate a sequentially numbered Goods Received Note (GRN). Copies are sent to purchasing and accounts payable.
- The Three-Way Match (Accounts Payable Control): When the supplier's invoice arrives, accounts payable executes the mandatory Three-Way Match before approving payment:
- Approved Purchase Order: Confirms goods were formally authorized at agreed contractual prices;
- Goods Received Note (GRN): Confirms goods were physically received in acceptable condition and correct quantities;
- Supplier Invoice: Confirms arithmetic accuracy, freight charges, and tax computations match the PO and GRN.
- Discrepancy Action: If quantities or unit prices diverge, payment is withheld, and a Debit Note is issued to the supplier requesting an amended invoice or credit note.
- Purchase Ledger Posting: Approved invoices are entered into the Purchase Day Book, credited to the supplier's personal account in the Purchase Ledger (Accounts Payable), and debited to Purchases / Asset / Expense accounts in the General Ledger.
- Payment Disbursement: Invoices are scheduled for payment in accordance with agreed commercial credit terms. Payments are authorized under strict segregation of duties using dual electronic bank signatures or dual cheque signatories. A Remittance Advice is dispatched to the vendor confirming settlement.
4. The Payroll Cycle: Timekeeping, Deductions, and Liabilities
Payroll represents one of the largest cash outflows for modern enterprises. The payroll cycle requires strict operational controls to prevent unauthorized pay rates, inaccurate overtime claims, and fictitious "ghost employees":
THE PAYROLL TRANSACTION CYCLE
TIME RECORDING GROSS PAY COMPUTATION DEDUCTIONS & NET PAY
┌───────────────┐ ┌────────────────────┐ ┌────────────────────┐
│ • Clock cards │ ────────► │ • Basic contracted │ ──────► │ • Statutory: PAYE, │
│ • Biometrics │ │ hours & rates │ │ social insurance │
│ • Timesheets │ │ • Approved overtime│ │ • Voluntary: Pens. │
│ • Supervisor │ │ • Bonuses/commiss. │ │ • Net pay via BACS │
│ authorization │ • Gross Earnings │ │ • Remit taxes/pens.│
└───────────────┘ └────────────────────┘ └────────────────────┘
1. Timekeeping and Authorization
Operating employees record hours worked utilizing electronic clock cards, biometric fingerprint/facial scanners, or detailed project timesheets. Line supervisors must formally review, verify, and sign off on all timesheets and overtime claims prior to payroll submission.
2. Gross Pay Calculation
Gross earnings represent total remuneration before any statutory or voluntary deductions:
3. Deductions: Statutory and Voluntary
Payroll software calculates mandatory and discretionary deductions:
- Statutory Deductions: Mandatory deductions required by fiscal law, including Pay-As-You-Earn (PAYE) income tax withholding and employee national insurance / social security contributions.
- Voluntary Deductions: Employee-authorized deductions, including employee pension scheme contributions, trade union subscriptions, payroll charitable giving, and private medical insurance premiums.
4. Disbursement and Accounting Postings
- Net Pay Transfer: Net pay is transferred directly into employee bank accounts via automated clearing systems (such as BACS in the UK or ACH in the US). Individual confidential payslips are distributed.
- Employer Payroll Liabilities: In addition to employee gross pay, the employer incurs direct statutory costs—notably Employer Social Security Contributions and Employer Pension Contributions.
- General Ledger Accounting Entry:
- Debit: Wages and Salaries Expense (Gross Pay + Employer Social Security + Employer Pension)
- Credit: Bank Account / Net Wages Payable (Net Pay disbursed to workers)
- Credit: Tax Authority Liability (PAYE Income Tax + Total Employee and Employer Social Security)
- Credit: Pension Trustees Liability (Total Employee and Employer Pension Contributions)
- Statutory Remittance: The finance department must remit withheld taxes and pension funds to statutory authorities within strict legal deadlines to avoid severe financial penalties and criminal sanctions.
5. The Cash and Treasury Cycle: Imprest Petty Cash and Bank Reconciliations
Cash is the most liquid and theft-vulnerable asset. Accounting systems employ two indispensable cash controls: the Petty Cash Imprest System and the Bank Reconciliation.
The Petty Cash Imprest System
The imprest system is an internal control mechanism designed to manage minor, day-to-day cash disbursements (e.g., office milk, urgent courier fees, local travel expenses, postage) while preventing theft and unrecorded leaks.
- The Fixed Float Rule: A predetermined fixed cash sum (the imprest float) is entrusted to a designated petty cashier and kept in a secure, locked tin or safe.
- Petty Cash Vouchers: No cash is ever disbursed without an authorized, sequentially numbered Petty Cash Voucher accompanied by third-party receipts (till slips or VAT receipts) and signed by the recipient and an independent department head.
- The Fundamental Imprest Balance Equation: At any given moment, physical cash remaining in the box plus the total face value of paid expense vouchers must exactly equal the agreed fixed float:
- Replenishment: Periodically (e.g., at month-end or when physical cash runs low), the petty cashier submits all vouchers to the senior accountant. The accountant reviews the vouchers, posts the expenses to the appropriate General Ledger nominal codes, and issues a bank cheque or transfer for the exact total amount of the vouchers spent. Reimbursing this exact amount restores physical cash back to the original fixed float level.
Numerical Worked Example: Petty Cash Imprest System
- Agreed Imprest Float: $300.00
- Vouchers Paid During Month:
- Voucher #101: Office hospitality supplies (tea, coffee, milk) = $38.50
- Voucher #102: Emergency courier delivery service = $45.00
- Voucher #103: Registered postage stamps = $26.80
- Voucher #104: Local taxi fare for urgent client document delivery = $52.70
- Voucher #105: Replacement keys for warehouse filing cabinet = $18.00
- Total Expense Vouchers: $38.50 + $45.00 + $26.80 + $52.70 + $18.00 = $181.00
- Physical Cash Remaining in Box: $300.00 - $181.00 = $119.00
- Imprest Reconciliation Check: Physical Cash ($119.00) + Vouchers ($181.00) = $300.00 Float Verified
- Reimbursement Action: The chief accountant reviews receipts and draws a cheque for exactly $181.00. Once cashed and placed into the box, the physical cash returns precisely to the agreed float of $300.00 ($119.00 + $181.00).
Bank Reconciliations
The Bank Reconciliation is a vital detective control performed periodically (daily, weekly, or monthly) to reconcile differences between the cash balance in the company's internal Cash Book and the balance reported on the external Bank Statement.
BANK RECONCILIATION ARCHITECTURE
INTERNAL CASH BOOK EXTERNAL BANK STATEMENT
• Managed by entity's accounts team • Generated by commercial bank
• Records receipts & payments • Independent third-party record
│ │
▼ ▼
DISCREPANCIES IDENTIFIED TIMING DIFFERENCES
• Bank charges & service fees • Unpresented Cheques (Supplier)
• Direct debits & standing orders • Uncleared Lodgments (Deposits)
• Direct customer credits (EFT) • Bank processing lags
• Dishonoured (bounced) cheques │
│ │
▼ ▼
ADJUST CASH BOOK ◄─────────────────────────► RECONCILE TO BANK
Adjusted Cash Book Balance MUST EQUAL Reconciled Bank Balance
Why Balances Diverge
Differences between the Cash Book and Bank Statement arise from two distinct categories:
- Items on the Bank Statement Not Yet Entered in the Cash Book: These are valid transactions processed directly by the bank of which the company was unaware until the statement arrived. The company must update and adjust its Cash Book:
- Deduct: Bank service charges, loan interest fees, direct debits, standing orders, and dishonoured (bounced) customer cheques;
- Add: Bank interest received and direct electronic funds transfers (EFT) from customers.
- Timing Differences (Items in the Cash Book Not Yet Processed by the Bank): These items are correctly entered in the company's internal books, but the commercial banking system has not yet cleared them. These are placed on the Bank Reconciliation Statement:
- Unpresented Cheques: Cheques drawn, signed, and dispatched to suppliers that have been recorded as payments in the Cash Book (crediting cash), but have not yet been presented to or cleared by the payee's bank. Treatment: Deducted from the Bank Statement balance.
- Uncleared Lodgments (Outstanding Deposits): Cash or cheques received and recorded as receipts in the Cash Book (debiting cash) and deposited in the bank, but not yet cleared and credited on the bank statement. Treatment: Added to the Bank Statement balance.
6. Accounting Documents, Vouchers, and the Unbroken Audit Trail
Internal control integrity relies on maintaining a seamless, verifiable audit trail across the enterprise.
The Source Document Chain
Every accounting entry must originate from verifiable commercial evidence:
- Sales Day Book: Sourced from Sales Invoices and Credit Notes;
- Purchase Day Book: Sourced from Supplier Invoices and Debit Notes;
- Cash Book: Sourced from Bank Statements, Remittance Advices, Paying-in Slips, and Cheque Stubs;
- Petty Cash Book: Sourced from Petty Cash Vouchers and third-party receipts;
- General Journal: Sourced from Journal Vouchers authorized by senior finance leadership for period-end adjustments, accruals, prepayments, depreciation, and bad debt write-offs.
The Role of Sequential Pre-Numbering
All source documents (orders, dispatch notes, GRNs, invoices, vouchers, and credit notes) must be sequentially pre-numbered. The regular checking of numerical sequences is a vital control that detects:
- Unrecorded transactions (e.g., missing invoice numbers indicating unrecorded sales or lost dispatch notes);
- Duplicate billing (e.g., identical numbers indicating duplicate payments to suppliers);
- Unauthorized out-of-sequence transactions.
The Audit Trail (Audit Path)
The audit trail is the step-by-step documentary trail that allows any financial figure to be traced in both directions:
- Forward Tracing (Completeness): Tracing a transaction forward from the originating source document (e.g., Goods Dispatch Note) into the day books, general ledger, trial balance, and financial statements to verify that all transactions have been completely and accurately recorded.
- Backward Tracing (Occurrence and Existence): Tracing a figure backwards from the financial statements (e.g., Revenue or Trade Payables) into ledger accounts, day books, and finally inspecting the physical, authorized source document (e.g., signed GRN or approved PO) to verify that recorded transactions genuinely occurred, belong to the entity, and are not fraudulent fabrications.
Transaction Cycles and Controls Summary
| Transaction Cycle | Key Source Documents | Primary Internal Control Procedures | Critical Risk Mitigated |
|---|---|---|---|
| Sales & Revenue | Sales Order, Goods Dispatch Note (GDN), Sales Invoice, Remittance Advice, Credit Note | Customer credit vetting; signed GDNs; sequential invoice pre-numbering; independent credit note authorization | Bad debt defaults; shipping unbilled goods; fictitious invoicing; unauthorized debt write-offs |
| Purchases & Expenditure | Purchase Requisition, Purchase Order (PO), Goods Received Note (GRN), Supplier Invoice | Delegated spending limits; approved supplier list; mandatory 3-way matching; dual payment authorization | Unauthorized purchasing; paying for damaged or undelivered goods; supplier overbilling; duplicate payments |
| Payroll | Biometric logs, Clock Cards, Timesheets, Payroll Journal, BACS Schedule | Supervisory sign-off on hours; HR control over starter/leaver files; independent wage payout review | Fictitious 'ghost employees'; inflated overtime claims; incorrect statutory tax withholdings |
| Cash & Treasury | Paying-in Slips, Petty Cash Vouchers, Bank Statements, Cheque Books | Segregation of cash custody and recording; imprest float ceiling; dual electronic banking keys; monthly bank reconciliations | Cash theft and embezzlement; unrecorded bank fees; lost cash deposits; unrecorded supplier payments |
7. Business Uses of Computers and IT Software Applications
Syllabus outcome C5(d) names three categories of application. Objective test questions turn on choosing the right tool for the task, and on knowing each tool's control weaknesses.
| Application Type | What It Is Best At | Typical Finance Uses | Principal Weaknesses and Control Risks |
|---|---|---|---|
| Spreadsheet applications | Flexible, ad hoc modelling of numbers laid out in a grid, with formulae, pivot tables, and charts | Budgeting and forecasting; investment appraisal; variance analysis; reconciliations; what-if and sensitivity analysis; one-off analysis that no packaged system supports | Uncontrolled formula and input errors that nothing detects; no audit trail of who changed what; uncontrolled versions circulating by email; no enforced segregation of duties; easily copied off-site, creating a confidentiality exposure. Controls: cell protection and locked formulae, input validation, version control, independent review, and restricting spreadsheets to analysis rather than to being the accounting record |
| Database systems | Storing large volumes of structured data once, without duplication, and querying it many ways | Customer and supplier master files; inventory records; fixed asset registers; payroll master data; data warehouses supporting analytics | Corrupted or duplicated master data propagates everywhere at once; unrestricted query access exposes personal and commercial data; poor design produces inconsistent results. Controls: master-data authorisation and maintenance procedures, referential integrity, role-based access rights, backup and recovery |
| Accounting packages | Processing routine accounting transactions through structured, controlled, integrated modules | Sales and purchase ledgers, general ledger, inventory, payroll, fixed assets, and statutory reporting; larger organisations use an integrated enterprise resource planning (ERP) suite linking finance to operations | Rigid — the package dictates the process; configuration errors are systematic and repeat on every transaction; over-reliance on defaults; supplier lock-in and upgrade cost; for cloud packages, dependence on connectivity and on the provider. Controls: configuration and access authorisation, exception and audit-trail reports, user acceptance testing before changes go live |
Choosing Between Them
- Repetitive, high-volume, control-critical work belongs in an accounting package, because it enforces double entry, keeps an audit trail, and restricts who may post.
- One-off, judgemental, assumption-driven analysis belongs in a spreadsheet, because no package anticipates every question management will ask.
- Large-volume structured data that many applications must share belongs in a database, because storing it once removes inconsistency.
The classic weakness examiners probe is the organisation that runs a material process — a revenue reconciliation, a consolidation, a regulatory return — on an unprotected spreadsheet maintained by one person. It has flexibility but none of the controls, and it fails every test of authorisation, segregation, and audit trail set out above.
Identifying an Organisation's System Requirements
Outcome C5(a) asks you to identify an organisation's system requirements in relation to its objectives and policies. Requirements are derived from the business, not from the software catalogue. Work through five questions in order:
- What does the organisation need the system to achieve? Requirements follow objectives. A group planning overseas expansion needs multi-currency and multi-entity consolidation; a single-site retailer does not.
- What volume and complexity must it handle? Transaction volume, number of users, number of entities, currencies, tax jurisdictions, and the expected growth over the system's life.
- What information must it produce, for whom, and how often? Statutory financial statements, management packs by department, real-time operational exception reports — each implies a different data structure and reporting capability.
- What controls and compliance obligations must it enforce? Authorisation limits, segregation of duties through user-access roles, a complete and unalterable audit trail, data-protection and retention requirements, and any industry-specific regulation.
- What must it connect to? Interfaces with banking, payroll, the point-of-sale or production system, and customer or supplier portals. An unintegrated system that requires manual re-keying reintroduces the very error risk the system was bought to remove.
Constraints then filter the answer: the budget available, the implementation timetable, the skills of the users, and the existing infrastructure. The characteristic failure — and a favourite scenario — is an organisation that specifies a system around the features a vendor demonstrated rather than around its own objectives, and then finds it must change its processes to fit the software.
Identifying Weaknesses and Inefficiencies in Accounting Systems
Outcome C5(c) asks you to identify weaknesses, potential for error and inefficiencies. Work through a standard checklist: manual re-keying between systems that should interface; reconciliations performed late or not at all; the same person able to set up a supplier and pay it; no exception reporting, so errors surface only at year end; duplicated data held in more than one place and allowed to diverge; processing bottlenecks concentrated at month end; and undocumented spreadsheets or macros understood by only one employee — a key-person dependency as well as a control weakness.
An accounts payable clerk receives a supplier invoice for 100 components at $25 each. Upon performing the 3-way match, the clerk observes that the purchase order specified $20 each, and the warehouse goods received note (GRN) confirms only 80 components were delivered in acceptable condition. What immediate internal control action should the clerk take?
Under a petty cash imprest system, the petty cashier is entrusted with an agreed fixed float of $300. At the end of the month, physical cash remaining in the petty cash tin is $42, and valid expense vouchers with receipts total $258. How much cash must be reimbursed to the cashier to restore the imprest float?
When preparing a monthly bank reconciliation, a company discovers that several cheques drawn and dispatched to suppliers near month-end have not yet cleared the banking system. How should these unpresented cheques be treated?