Revenue and Expenditure Cycles

Introduction

Accounting information systems (AIS) convert business transactions into reliable information for decision-making, reporting, control and accountability. Two of the most important transaction groupings are the revenue cycle and the expenditure cycle. The revenue cycle concerns the sale of goods or services and the collection of amounts due from customers. The expenditure cycle concerns acquiring goods and services, recognising obligations to suppliers and paying those obligations.

These cycles are closely connected to the general ledger, inventory, human resources, production and financial reporting systems. Weaknesses in either cycle can cause misstated revenue, inaccurate receivables or payables, cash losses, fraud, poor customer service and unreliable financial statements. Modern organisations may process transactions through enterprise resource planning (ERP) systems, e-commerce platforms, electronic data interchange, mobile payments and automated matching tools, but the underlying accounting logic and control objectives remain essential.

Learning objectives

By the end of this chapter, a learner should be able to:

1. Explain the purpose and boundaries of the revenue and expenditure cycles.
2. Analyse sales, receivables and cash-receipt processes.
3. Analyse purchasing, payables and cash-disbursement processes.
4. Identify source documents, records and typical accounting entries.
5. Evaluate risks and internal controls, including segregation of duties and authorisation.
6. Interpret performance information and relevant cycle measures.
7. Assess the effects of technology, ethics, governance and emerging risks.

1. The cycle perspective

A transaction cycle is a recurring set of activities that begins with an economic event and ends with its recording, settlement and reporting. The cycle perspective is useful because it links operational work to accounting information and control.

The revenue cycle normally includes:

• receiving and approving customer orders;
• checking prices, credit and availability;
• picking, packing and shipping goods, or delivering services;
• billing the customer;
• recording sales and receivables; and
• receiving, depositing and reconciling cash.

The expenditure cycle normally includes:

• recognising a need for goods or services;
• preparing a purchase requisition;
• selecting and approving a supplier;
• issuing a purchase order;
• receiving and inspecting goods or services;
• recording the supplier invoice and payable; and
• authorising and making payment.

The cycles should not be viewed as isolated. For example, a sale may reduce inventory and increase cost of sales; a purchase may increase inventory and create a payable; and a cash receipt or disbursement affects bank reconciliations and liquidity reporting.

A useful control model is the input–process–output framework. Source documents and authorised data are inputs. Procedures, applications and people process the data. Reports, journal entries, customer statements, supplier statements and management dashboards are outputs. Controls must protect all three stages.

2. Revenue cycle processes

2.1 Customer order entry

A customer order may be received through a sales representative, website, electronic data interchange, telephone or a formal quotation. The system should capture customer identity, product or service, quantity, price, delivery terms, tax information, payment terms and requested delivery date.

Important controls include:

• use of approved customer master records;
• sequentially numbered sales orders;
• automated price-list and discount checks;
• credit-limit and overdue-balance checks;
• inventory availability checks;
• independent approval of unusual discounts or terms; and
• an audit trail showing who created or changed the order.

A sales order is not itself evidence that revenue has been earned. It is evidence of an intended transaction. Recognition depends on the applicable financial reporting framework and the underlying performance or delivery conditions.

2.2 Credit approval and fulfilment

Credit sales expose an organisation to default risk. Credit approval should be performed by an employee or function independent of sales incentives where practical. Relevant information includes credit history, current balance, payment experience, external credit information and expected exposure.

Once approved, a warehouse or service-delivery function fulfils the order. A picking list authorises warehouse staff to select goods. A packing slip identifies the contents of a shipment. A dispatch note or carrier record provides evidence of shipment. For services, a timesheet, milestone certificate, acceptance record or signed service report may provide evidence of delivery.

Controls should ensure that:

• only approved orders are released;
• quantities picked agree with the authorised order;
• serial numbers or batch numbers are recorded where relevant;
• goods are independently counted before dispatch;
• shipment or service completion is recorded promptly; and
• returns and delivery disputes are documented and authorised.

2.3 Billing and revenue recording

Billing uses evidence of shipment or service completion, approved prices and contractual terms. An invoice generally contains an invoice number, date, seller and customer details, description, quantity, price, tax, delivery charges, payment terms and total amount.

For a credit sale of goods, a simplified entry is:

If the sale is subject to output tax, the entry may be presented as:

The amount debited to receivables is the invoice total, while revenue excludes amounts collected on behalf of a government or other third party. The exact treatment depends on the applicable accounting standards and tax law.

When inventory is sold under a perpetual inventory system, a second entry records the cost:

Under a periodic inventory system, cost of sales is determined through the period-end inventory calculation rather than necessarily at each sale. The accounting system must therefore be configured consistently with the organisation’s inventory method and reporting requirements.

Revenue recognition is not simply a function of issuing an invoice. In a contract involving several obligations, revenue may be recognised when, or as, each obligation is satisfied. For example, a software arrangement may include a licence, implementation and support. The organisation must identify the obligations, allocate consideration appropriately and recognise revenue in accordance with the applicable reporting framework.

2.4 Accounts receivable

Accounts receivable is a subsidiary ledger containing individual customer balances. The total of the subsidiary ledger should agree with the accounts-receivable control account in the general ledger. The system should support customer statements, ageing reports, credit notes, receipts, disputes and write-off approvals.

A sale increases receivables; a credit note, receipt or approved write-off decreases them. A customer payment is normally recorded as:

A credit note may be required for returns, pricing errors or service adjustments. It should not be used to conceal an unauthorised write-off or to manipulate the timing of revenue.

Because not all receivables will be collected, management estimates expected credit losses or an allowance for doubtful accounts as required by the reporting framework. A simplified allowance adjustment is:

The allowance is a contra-asset account. Its amount should be based on supportable evidence, such as ageing, historical collection patterns, customer-specific information and forward-looking economic conditions. It is an estimate, not a substitute for effective credit control.

2.5 Cash receipts

Cash receipts may be received by bank transfer, card, cheque, cash, mobile payment or an online payment intermediary. The process should separate custody of money from recording and reconciliation.

Typical activities include opening mail or electronic payment reports, preparing a remittance list, depositing funds, posting receipts to customer accounts and reconciling bank records. A remittance advice identifies the invoices that a customer intends to settle. An electronic funds transfer report supplies evidence for electronic receipts.

Key controls include immediate or daily deposits, dual custody of physical cash, system-generated receipt numbers, independent bank reconciliation, segregation between cash handling and ledger posting, and investigation of unapplied receipts. A lockbox arrangement, in which a bank receives and reports customer payments, can reduce handling risk and accelerate availability of funds.

3. Expenditure cycle processes

3.1 Need recognition and requisition

The expenditure cycle begins when an employee or department identifies a need. A purchase requisition describes the item or service, quantity, required date, cost centre and justification. It is an internal document and does not normally create a legal obligation to a supplier.

Controls include approved budgets, authorised requisitioners, inventory reorder levels, review of existing stock and prevention of duplicate requests. Emergency purchasing should be permitted only under defined conditions and reviewed afterwards.

3.2 Supplier selection and purchase orders

Procurement may obtain quotations, conduct competitive tendering, use framework agreements or select an approved supplier. Supplier selection should consider price, quality, delivery, financial stability, ethical conduct, data security and continuity risk—not price alone.

A purchase order (PO) is an authorised commitment specifying the supplier, items, quantity, price, delivery terms and other conditions. Sequential numbering, approval thresholds and restricted access to supplier master data strengthen control. Changes to bank-account details require independent verification using trusted contact information, because supplier impersonation and payment diversion are significant risks.

3.3 Receiving and inspection

The receiving function compares delivered goods with the PO and prepares a goods received note (GRN) or receiving report. It should record quantities received, condition, date, discrepancies and the identity of the receiver. Services require equivalent evidence, such as an approved timesheet, milestone acceptance or completion certificate.

Receiving should be independent of purchasing where possible. The receiver should not be able to create a supplier or approve payment without review. Partial deliveries and back-orders must be recorded accurately.

3.4 Invoice processing and accounts payable

The supplier invoice is checked against the PO and receiving evidence. A common control is three-way matching:

1. PO: what was ordered;
2. GRN or service acceptance: what was received; and
3. invoice: what the supplier billed.

A tolerance may allow small, authorised differences in price or quantity. Exceptions should be routed to an identified person rather than automatically paid.

For an ordinary credit purchase of inventory, a simplified entry is:

For a service or expense:

If input tax is recoverable, the debit may be split between the underlying asset or expense and input tax receivable. The accounting treatment depends on tax law and the organisation’s reporting framework.

A payable is recognised when the entity has received goods or services and has a present obligation, even if the invoice has not yet arrived. This is the basis of an accrual or goods-received-not-invoiced entry. Failure to record such obligations understates liabilities and expenses and may overstate profit.

3.5 Cash disbursements

Payment is made only after approval, matching and verification of the supplier and bank details. Payment methods include electronic transfer, cheque, direct debit and purchasing card. A payment run should produce a proposal, exception report, approval record and bank transmission record.

The usual entry for settlement is:

Early-payment discounts should be recorded according to the organisation’s accounting policy. Cancelled or duplicate invoices should be clearly marked in the system. A payment register should be reconciled to the bank statement and the accounts-payable subsidiary ledger.

4. Documents, records and information flow

Source documents should be retained in accordance with legal, tax, contractual and organisational requirements. Digital records need access controls, reliable timestamps, version history, backup, retention rules and protection against unauthorised alteration.

5. Internal control framework and risks

Internal control aims to provide reasonable—not absolute—assurance that operations are effective, assets are safeguarded, records are reliable and laws and policies are followed. The control environment, risk assessment, control activities, information and communication, and monitoring are mutually reinforcing.

5.1 Segregation of duties

Four incompatible responsibilities should normally be separated:

• authorising a transaction;
• custody of an asset or access to funds;
• recording the transaction; and
• reconciling or reviewing the records.

For example, a person who can create a supplier, approve an invoice and release a payment can create a fictitious supplier and divert funds. In a small organisation, full segregation may be impossible; compensating controls include owner review, independent bank statements, payment alerts and periodic audit testing.

5.2 Principal risks and controls

Controls may be preventive, detective or corrective. A credit limit is preventive; an ageing report is detective; recovery of a duplicate payment is corrective. Controls may also be manual, automated or dependent on information technology general controls such as access management, change control and backup.

6. Performance information and analytical measures

AIS data should support both financial reporting and operational management. Useful revenue-cycle measures include:

• sales by product, customer, channel and region;
• gross margin and return rates;
• order-to-cash cycle time;
• percentage of orders delivered on time and in full;
• days sales outstanding (DSO);
• collection effectiveness and dispute resolution time; and
• bad-debt or expected-credit-loss trends.

A common approximation of DSO is:

Average accounts receivable is commonly calculated as opening receivables plus closing receivables divided by two, although a daily or monthly average may be more informative when balances fluctuate substantially. The measure assumes that net credit sales are a reasonable denominator and that the period and day count are consistent. A higher DSO may indicate weak collection, disputed invoices, lenient credit or a changing customer mix; it is not automatically evidence of poor performance.

Useful expenditure-cycle measures include purchase-price variance, supplier defect rate, on-time delivery, requisition-to-PO time, invoice-processing cost, percentage of invoices matched automatically, payment-on-time rate and early-payment discounts captured. A simple purchase-price variance for a quantity purchased is:

Here, quantity is measured in the relevant units and prices are monetary amounts per unit. A positive result generally indicates an unfavourable variance when actual price exceeds standard price, but interpretation depends on the organisation’s sign convention and whether the standard remains realistic.

Metrics must be interpreted together. Reducing invoice-processing time by paying invoices without matching may improve speed while increasing fraud and error. Similarly, maximising collection speed by refusing reasonable customer terms may damage sales and relationships. Balanced dashboards should combine cost, quality, speed, control exceptions, customer outcomes and compliance.

7. Technology, data and artificial intelligence

ERP systems integrate orders, inventory, invoicing, payables, cash and the general ledger. Application programming interfaces connect payment gateways, banks, logistics providers and tax systems. Optical character recognition can extract invoice data, while workflow systems route exceptions for approval. Electronic invoicing can reduce keying errors and improve auditability.

Artificial intelligence and machine learning can assist with duplicate-invoice detection, unusual payment patterns, customer-credit scoring, cash forecasting and prioritisation of collection activity. However, these tools do not remove the need for human accountability. Risks include biased models, false positives, opaque decisions, manipulated training data, privacy breaches and over-reliance on automated recommendations. Governance should include documented purpose, data-quality testing, access restrictions, model validation, monitoring, explainability appropriate to the decision and a human escalation route.

Robotic process automation is most suitable for stable, rules-based activities with structured data. Automating a poorly designed process may accelerate errors. Before implementation, an organisation should map the process, remove unnecessary steps, define ownership, test interfaces, establish exception handling and retain evidence of automated decisions.

8. Ethical, legal and governance considerations

Revenue and expenditure processes affect customers, suppliers, employees, shareholders, governments and communities. Ethical conduct requires truthful invoices, accurate cut-off, fair supplier selection, protection of personal and banking data and resistance to pressure to manipulate results.

Common governance concerns include:

• recognising revenue before performance obligations are satisfied;
• delaying the recording of expenses or liabilities;
• creating fictitious sales near period-end;
• accepting undisclosed supplier benefits or conflicts of interest;
• altering supplier bank details without verification;
• using customer data beyond its lawful or agreed purpose; and
• suppressing control exceptions or whistleblower reports.

Organisations should maintain approval matrices, conflict-of-interest declarations, procurement policies, retention schedules, privacy safeguards, incident-response procedures and independent internal-audit activity. Compliance requirements vary by jurisdiction, industry and reporting framework; professional judgement and current legal guidance are therefore necessary.

9. Illustrative case: Meridian Office Supplies

Background

Meridian Office Supplies sells to corporate customers on credit and purchases inventory from several regional suppliers. It recently implemented an online ordering system connected to its ERP system.

Problem

During a review, management found that sales increased by 18 percent, but cash collections increased by only 5 percent. The receivables ageing report showed a sharp rise in balances over 90 days. At the same time, the organisation discovered two payments to a supplier whose bank account had recently changed. One invoice was paid twice.

Analysis

Investigation identified four weaknesses. Sales staff could override credit holds without independent approval. Dispatch evidence was not consistently linked to invoices, creating cut-off and disputed-sale risks. The accounts-payable clerk could amend supplier bank details and release payment. Finally, invoice numbers were entered manually, so duplicate invoices were not reliably detected.

The data also showed that DSO had risen. Suppose average receivables were CU 1,200,000, net credit sales for a 360-day period were CU 7,200,000, and management used a 360-day convention. Then:

CU means currency units. The calculation indicates that the average collection period was approximately 60 days, which exceeded the standard customer term of 30 days. The difference required investigation rather than an automatic conclusion that every customer was delinquent.

Approach and solution

Meridian introduced independent approval for credit overrides, system-enforced links between dispatch records and invoices, and daily exception reports for orders shipped without approved credit. Supplier bank changes now require verification through a previously known telephone number and approval by procurement and treasury. Supplier master-data changes are logged and reviewed monthly.

The ERP system now checks invoice number, supplier, date and amount combinations for duplicates. A three-way match is mandatory except for defined service categories, which require approved service acceptance evidence. Treasury prepares the payment file, while a separate manager authorises release through multi-factor authentication. Internal audit performs periodic sample testing and reviews analytics for unusual patterns.

Outcome

After three months, disputed invoices declined, overdue receivables began to fall and duplicate-payment exceptions were identified before release. Management also discovered that some customers were receiving invoices late because dispatch data was incomplete. Correcting that process improved collections without imposing unnecessarily strict credit terms.

Learning points

The case demonstrates that revenue and expenditure controls are connected to operational evidence, not merely journal entries. Technology improved detection but did not replace segregation of duties, independent verification or managerial judgement. Performance measures were useful because they prompted analysis of causes rather than serving as isolated targets.

10. Implementation and best practices

A professionally designed cycle should:

1. document the process from initiation to ledger posting and reconciliation;
2. assign a clear owner for each activity and control;
3. maintain complete, accurate and timely source evidence;
4. use sequential identifiers and prevent unauthorised deletion;
5. apply approval limits consistently;
6. reconcile subsidiary ledgers, bank accounts, inventory and the general ledger;
7. review ageing, unmatched items, credit notes, duplicate invoices and unusual journal entries;
8. test access rights and remove access promptly when roles change;
9. assess suppliers, customers, outsourced providers and cyber risks;
10. train staff in ethics, privacy, fraud indicators and escalation procedures; and
11. monitor control performance and improve processes when exceptions recur.

Controls should be proportionate to risk. A small low-value purchase does not require the same procedure as a high-value specialised contract, but exceptions should be defined rather than left to informal discretion. Continuous improvement should consider root causes, user experience, control effectiveness and total cost.

Chapter Summary

The revenue cycle transforms customer demand into delivery, billing, receivables and cash collection. Its essential evidence includes sales orders, credit approval, dispatch or service-completion records, invoices, customer statements and receipt records. The expenditure cycle transforms an internal need into an approved purchase, receipt, payable and cash disbursement. Its central documents include requisitions, purchase orders, receiving reports, supplier invoices and payment records.

Accurate accounting depends on timely evidence and appropriate entries. Credit sales increase receivables and revenue; sales of inventory also reduce inventory and recognise cost of sales. Purchases and services create assets or expenses and payables, while settlement reduces payables and cash. Three-way matching, segregation of duties, authorisation, reconciliations, access controls and exception reporting reduce important risks, although no control provides absolute assurance.

AIS performance information includes collection, delivery, margin, ageing, DSO, supplier quality, processing time and payment measures. Metrics require context and should balance speed and cost with accuracy, compliance, customer service and fraud prevention. ERP systems, electronic invoicing, automation and AI can improve efficiency and detection, but require sound process design, data governance, cybersecurity and human oversight. Ethical revenue recognition, fair procurement, privacy and reliable reporting are central to professional practice.

Key Terms

Revenue cycle: Activities from customer order through delivery, billing and collection.

Expenditure cycle: Activities from recognising a purchasing need through payment to a supplier.

Accounts receivable: Amounts owed by customers for credit sales.

Accounts payable: Amounts owed to suppliers for received goods or services.

Sales order: Authorised record of a customer’s requested goods or services and terms.

Purchase requisition: Internal request to acquire goods or services.

Purchase order: Authorised commitment issued to a supplier.

Goods received note: Evidence of goods received and inspected.

Three-way match: Comparison of purchase order, receiving evidence and supplier invoice.

Remittance advice: Information identifying invoices a customer intends to settle.

Credit note: Document reducing an invoice or customer balance.

Expected credit loss: Estimate of receivables that will not be collected.

Segregation of duties: Separation of authorisation, custody, recording and review responsibilities.

Cut-off: Assignment of transactions to the correct accounting period.

Subsidiary ledger: Detailed record supporting a general-ledger control account.

Bank reconciliation: Comparison of accounting cash records with bank records.

Days sales outstanding: Approximate average number of days required to collect credit sales.

Preventive control: Control designed to stop an error or fraud before it occurs.

Detective control: Control designed to identify an error or fraud after it occurs.

Enterprise resource planning system: Integrated system supporting multiple organisational processes and records.

Review Questions

Short Answer Questions

1. What are the main stages of the revenue cycle?
2. Distinguish a purchase requisition from a purchase order.
3. What evidence is normally compared in a three-way match?
4. Why should cash custody be separated from accounting-record maintenance?
5. What does DSO attempt to measure?

Long Answer Questions

1. Explain the revenue cycle from customer order entry to cash collection, identifying key documents, risks and controls.
2. Discuss how an expenditure cycle should process a purchase from need recognition through payment.
3. Explain the accounting entries associated with a credit sale, the related inventory movement and subsequent customer receipt.
4. Evaluate the importance of segregation of duties, reconciliations and master-data controls in revenue and expenditure cycles.
5. Discuss how ERP systems, electronic invoicing and AI can improve cycle performance while creating new governance risks.

Analytical / Application Questions

1. A company’s sales are rising, but its receivables ageing is deteriorating. Analyse at least four possible causes and recommend information-system controls or management actions.
2. A supplier changes its bank account immediately before a large payment run. Design a control response that balances fraud prevention with timely payment.
3. An organisation wants to reduce invoice-processing time by removing three-way matching for all purchases. Evaluate this proposal and recommend a risk-based alternative.

Multiple Choice Questions with Answers

Question 1

Which document normally provides evidence that goods ordered from a supplier were received?

A. Sales invoice

B. Goods received note

C. Customer statement

D. Remittance advice

Correct Answer: B. Goods received note

Question 2

Which combination best describes a three-way match?

A. Sales order, customer statement and bank statement

B. Purchase requisition, budget and cheque

C. Purchase order, receiving evidence and supplier invoice

D. Invoice, credit note and remittance advice

Correct Answer: C. Purchase order, receiving evidence and supplier invoice

Question 3

What is the usual entry when a customer pays an outstanding credit sale?

A. Dr Accounts Receivable; Cr Cash

B. Dr Cash; Cr Accounts Receivable

C. Dr Sales Revenue; Cr Cash

D. Dr Inventory; Cr Accounts Receivable

Correct Answer: B. Dr Cash; Cr Accounts Receivable

Question 4

If average accounts receivable is CU 300,000, net credit sales are CU 1,800,000 for a 360-day period, what is approximate DSO?

A. 30 days

B. 45 days

C. 60 days

D. 90 days

Correct Answer: C. 60 days

Question 5

Which control most directly reduces the risk that one employee creates a fictitious supplier and pays that supplier?

A. Allowing unrestricted supplier-master access

B. Separating supplier creation, payment approval and payment release

C. Increasing the number of sales invoices

D. Removing bank reconciliations

Correct Answer: B. Separating supplier creation, payment approval and payment release

Question 6

Under a perpetual inventory system, which entry records the cost of inventory sold?

A. Dr Inventory; Cr Cost of Sales

B. Dr Accounts Receivable; Cr Sales Revenue

C. Dr Cost of Sales; Cr Inventory

D. Dr Cash; Cr Inventory

Correct Answer: C. Dr Cost of Sales; Cr Inventory

Question 7

What is the primary purpose of a remittance advice?

A. To authorise a purchase order

B. To identify invoices a customer intends to pay

C. To record goods received from a supplier

D. To approve a credit limit

Correct Answer: B. To identify invoices a customer intends to pay

Question 8

Which is a detective rather than a preventive control?

A. Credit-limit check before order approval

B. Approval required before a payment is released

C. Monthly review of overdue receivables

D. Restricted access to supplier creation

Correct Answer: C. Monthly review of overdue receivables

Question 9

A positive purchase-price variance calculated as actual quantity × (actual price − standard price) generally means that:

A. Actual price exceeded standard price

B. Standard price exceeded actual price

C. Quantity received was zero

D. No purchase occurred

Correct Answer: A. Actual price exceeded standard price

Question 10

Why can revenue recognition not be based solely on invoice issuance?

A. Invoices never contain prices

B. An invoice always represents cash received

C. Recognition depends on satisfaction of applicable performance or delivery conditions

D. Receivables are never recorded from invoices

Correct Answer: C. Recognition depends on satisfaction of applicable performance or delivery conditions