From Documents to Data: How Accounting Systems Capture Transactions

Learning objectives

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

• Identify common source documents used in routine accounting cycles and explain what each document evidences.
• Classify typical business transactions so they are posted to the correct journals and ledgers.
• Explain how transaction data flows from business activity into accounting records, while maintaining accuracy and completeness.
• Describe key features of a computerised accounting system, including access controls, audit trails, and cloud-based storage.
• Apply practical checks to confirm that transaction data is complete, timely, authorised, and reliable.

Overview & key concepts

Financial statements depend on the quality of the transaction data that feeds them. In practice, an accounting system converts business activity (deliveries, services, payments, returns, approvals) into journals and ledger balances that can be reported consistently.

Two ideas must be kept separate:

• Recording evidence: source documents support what happened, when, and for how much.
• Accounting treatment: recognition and measurement depend on accounting principles (for example, whether goods or services have been delivered, whether an obligation exists, and whether amounts are recoverable), not simply on the existence of an invoice.

The double-entry system keeps records internally consistent, preserving the accounting equation.

Accounting equation:
Assets = Liabilities + Equity

A useful expansion when explaining movements is:

Equity = Share capital + Retained earnings
Retained earnings = Opening retained earnings + Profit for the period − Dividends

Source documents

Source documents are original records that provide evidence of transactions and support auditability. They help ensure entries are authorised, complete, and correctly measured, and they allow balances to be traced back to underlying activity.

Typical source documents include:

• Quotation– a price offer from a supplier (evidence for decision-making; not an accounting entry by itself).
• Purchase order (PO)– authorises a purchase and sets out what is being ordered.
• Goods received note (GRN)– confirms delivery and inspection of goods received.
• Supplier invoice– supports the amount billed and the tax details; often used for processing and settlement.
• Sales invoice– supports amounts charged to customers and tax details; often used for billing and settlement.
• Credit note– reduces a previously billed amount (issued for returns, pricing adjustments, or overbilling).
• Remittance advice– explains how a payment should be allocated to invoices (useful for allocation; not an accounting entry by itself).
• Receipt / bank confirmation– evidence that cash has been received.

Transaction classification

Before posting, identify the type of transaction and the accounts affected. A practical classification approach is to map transactions into cycles:

• Sales cycle: sales invoices, sales credit notes, customer receipts, write-offs.
• Purchases cycle: supplier invoices, supplier credit notes, supplier payments.
• Cash and bank: bank receipts and payments, charges, interest.
• Inventory and cost of sales: inventory purchases, issues to cost of sales, inventory adjustments.
• Accruals and deferrals: prepayments, accruals, deferred income.
• Financing and equity: loans/notes payable, interest, share issues, dividends.

Correct classification is essential because it determines both measurement and where the item appears in the financial statements.

Debits, credits, and cash vs credit

A computerised system may post automatically, but every transaction still follows double-entry logic.

Rules of debits and credits

• Assetsincrease withdebits, decrease withcredits.
• Liabilitiesincrease withcredits, decrease withdebits.
• Equityincreases withcredits, decrease withdebits.
• Incomeincreases withcredits.
• Expensesincrease withdebits.

Cash vs credit transactions

The underlying event may be similar, but the balance sheet account differs.

Credit sale (goods/services provided, customer billed):

• Debit: Trade receivables
• Credit: Revenue (and any indirect tax liability, if applicable)

Cash sale (cash received immediately):

• Debit: Bank/cash
• Credit: Revenue (and any indirect tax liability, if applicable)

Credit purchase (goods/services received, obligation exists):

• Debit: Expense / Inventory / Asset (depending on what was acquired)
• Credit: Trade payables (and any recoverable indirect tax, if applicable)

Cash purchase (paid immediately):

• Debit: Expense / Inventory / Asset
• Credit: Bank/cash

Invoices are commonly used as evidence for amounts and tax processing, but the accounting entry should reflect when the entity has received goods/services (for purchases) or delivered goods/services (for sales), and when an obligation or right exists.

Core theory and frameworks

Capturing transactions: a reliable flow

A disciplined process helps ensure completeness and accuracy:

1. Trigger– a business event occurs (delivery, service, payment, return).
2. Evidence– collect the supporting document(s) and confirm authorisation.
3. Verify– check key details: date, parties, quantities, unit prices, tax codes, totals, references.
4. Classify– determine accounts affected and whether it is cash/credit, capital/revenue, inventory/expense.
5. Record– enter into the appropriate module or journal.
6. Post– update sub-ledgers (receivables/payables) and the general ledger.
7. Review– run exception reports and perform reconciliations; resolve differences promptly.

Reviewing document quality

High-quality records reduce error and fraud risk. Common checks include:

• Correct supplier/customer name and account
• Document dates and sequential numbering
• Quantities delivered vs quantities invoiced
• Prices, discounts, and totals
• Indirect tax rate and tax code
• Authorisation evidence (approval, PO match)
• Duplicate detection (same number/amount/date)

Processing in computerised systems

Computerised systems typically process transactions through modules (sales, purchases, inventory, cashbook). Common features include:

• Master data controls (customer/supplier records, product codes, tax codes)
• Validation rules (mandatory fields, arithmetic checks)
• Posting logic that updates both sub-ledgers and the general ledger
• Document attachment (scans, approvals, delivery notes)
• User access controls and approval workflows
• Audit trail showing who posted/changed entries and when
• Real-time reports and exception listings (aged balances, unmatched invoices, overrides)

Cloud-based storage

Cloud-based systems store data on remote servers accessed over the internet. Benefits can include:

• Remote access and collaboration
• Centralised backups and updates
• Scalability as transaction volumes grow

Cloud access does not remove the need for strong user permissions, segregation of duties, and review controls.

Matching and reconciliation

Matching links related documents to confirm validity and accuracy. A common purchase control is linking:

• PO (authorisation)
• GRN (delivery)
• Supplier invoice (billing)

Reconciliation confirms that balances are complete and consistent. Examples include:

• Bank reconciliation (statement to cashbook)
• Receivables/payables control accounts (general ledger control to sub-ledger totals)
• Indirect tax control account reconciliation (output vs input vs payments/refunds)
• Inventory reconciliations (records to counts and movement analysis)

Error prevention and correction

Controls reduce the likelihood of errors and help detect them early:

• Approval limits and workflows
• Mandatory matching rules (for example, invoice requires GRN)
• Regular reconciliations and ageing reviews
• Exception reports (unmatched items, overrides, unusual journals)
• Clear correction procedures (credit notes, reversals, and adjustment journals)

Common transaction areas that need careful treatment

Operating expenses vs inventory and cost of sales

• Operating expense: items consumed by the business (for example, office supplies). Recognise as an expense when consumed, and consider whether any material amount remains unused at period end.
• Inventory: items held for resale or production. Recognise as inventory until sold, then transfer to cost of sales.

Deferred income (unearned revenue)

If cash is received before goods/services are provided, the entity has an obligation to deliver in the future.

On receipt of advance payment:

• Debit: Bank
• Credit: Deferred income (liability)

When goods/services are provided:

• Debit: Deferred income
• Credit: Revenue

Notes payable and interest

A note payable is a formal borrowing. Interest is recognised over time, not only when paid.

On receipt of loan funds:

• Debit: Bank
• Credit: Notes payable

Accruing interest at period end (if unpaid):

• Debit: Finance cost (interest expense)
• Credit: Interest payable

Allowance for receivables (expected credit loss allowance)

Trade receivables should be shown at the amount the entity realistically expects to collect. If some balances may not be recovered, a loss allowance (often called an expected credit loss allowance) is recognised so receivables are not overstated. The older phrase “allowance for doubtful debts” may still be encountered, but modern terminology focuses on expected credit losses.

Creating or increasing the loss allowance:

• Debit: Impairment loss (expense)
• Credit: Loss allowance on receivables (contra-asset)

Writing off a specific irrecoverable balance (when confirmed):

• Debit: Loss allowance on receivables
• Credit: Trade receivables

Equity transactions (share capital, dividends, retained earnings)

Equity transactions are not operating expenses.

Issue of shares for cash:

• Debit: Bank
• Credit: Share capital (and share premium, if applicable)

A dividend payable is recognised only when it has been properly approved and is no longer at the entity’s discretion.

When a dividend is properly authorised and unpaid:

• Debit: Retained earnings (distribution)
• Credit: Dividends payable

When the dividend is paid:

• Debit: Dividends payable
• Credit: Bank

Worked example

Narrative scenario

Greenfield Supplies records routine purchases and sales during the month. The business is registered for an indirect tax such as VAT, where sales create output tax and eligible purchases create recoverable input tax.

All supplier documents below relate to office supplies purchased from the same supplier. Customer transactions relate to sales to customers made during the month.

Transactions:

1. Greenfield obtains a quotation and raises a purchase order for office supplies with a list price of £1,000 (net).
2. The supplies are delivered and a goods received note is prepared confirming receipt.
3. The supplier sends an invoice for £1,000 plus indirect tax at 20%.
4. Greenfield issues a sales invoice to a customer for £500 plus indirect tax at 20%.
5. The customer returns goods worth £100 (net), and Greenfield issues a credit note.
6. Greenfield receives £400 from the customer.
7. Later in the month, a second supplier invoice is received for £1,200 (net), but only £1,000 (net) of goods were delivered and accepted. The supplier agrees the invoice should be corrected to match the delivery.
8. Greenfield pays £800 to the supplier by bank transfer and sends remittance advice.
9. Greenfield returns some office supplies to the supplier and receives a supplier credit note for £200 (net).
10. A customer pays £450 to settle an invoice that was outstanding at the start of the month (from a prior period).

Required

• Compute the total indirect tax payable (or recoverable) for the month.
• Prepare the purchase ledger control account.
• Reconcile the sales ledger control account.
• Identify and correct the discrepancy in the supplier invoice.
• Describe the impact of these transactions on the financial statements.

Solution

1) Indirect tax payable (or recoverable)

This illustration assumes a VAT-style system at 20% and that the entity can recover input tax on the purchases shown. In practice, indirect tax rules and recoverability depend on local legislation and eligibility.

Output tax (sales)

• Sales invoice: £500 x 20% = £100
• Sales credit note (return): £100 x 20% = £20
• Net output tax = £100 − £20 = £80

Input tax (purchases)

• Supplier invoice 1: £1,000 x 20% = £200
• Supplier invoice 2 (corrected to delivered amount): £1,000 x 20% = £200
• Supplier credit note (return to supplier): £200 x 20% = £40
• Net input tax = £200 + £200 − £40 = £360

Indirect tax control position
Indirect tax control = Output tax − Input tax
Indirect tax control = £80 − £360 = −£280

A negative balance indicates input tax exceeds output tax, so it is recoverable.

Indirect tax recoverable for the month = £280

2) Purchase ledger control account (trade payables)

Control accounts are commonly maintained at gross amounts (including indirect tax) because suppliers are paid gross. Some systems maintain net payables with tax posted separately; the key is to be consistent with system design.

Gross amounts:

• Supplier invoice 1: £1,000 + £200 = £1,200
• Supplier invoice 2 (corrected): £1,000 + £200 = £1,200
• Supplier credit note: £200 + £40 = £240
• Supplier payment: £800

Purchase ledger control account:

• Opening balance: £0
• Credit: Supplier invoices £1,200 + £1,200 = £2,400
• Debit: Supplier payment £800
• Debit: Supplier credit note £240

Closing trade payables = £2,400 − £800 − £240 = £1,360

3) Sales ledger control account reconciliation (trade receivables)

Control accounts are commonly maintained at gross amounts (including indirect tax) because customers pay gross.

Gross amounts:

• Sales invoice: £500 + £100 = £600
• Sales credit note: £100 + £20 = £120
• Receipt during month: £400
• Receipt for prior-period invoice: £450

Sales ledger control account:

• Opening balance (prior-period invoice outstanding): £450 (debit)
• Debit: Sales invoice £600
• Credit: Sales credit note £120
• Credit: Receipts £400 + £450 = £850

Closing trade receivables = £450 + £600 − £120 − £850 = £80

The closing balance should agree to the total of customer balances in the receivables sub-ledger. Differences typically arise from unposted items, misallocations, or entries posted to the wrong customer.

4) Discrepancy in supplier invoice (identification and correction)

A supplier invoice was received for £1,200 (net) when only £1,000 (net) of goods were delivered and accepted. The invoice should be recorded (or adjusted) to match the delivered amount.

Correct figures:

• Net amount: £1,000
• Indirect tax at 20%: £200
• Gross payable: £1,200

If the £1,200 (net) invoice had already been entered, reverse the excess:

Excess net amount: £200
Excess indirect tax: £40
Excess gross: £240

Correcting entry (reduce payable and reduce the claim for input tax):

• Debit: Trade payables £240
• Credit: Office supplies expense (or inventory, if appropriate) £200
• Credit: Input tax £40

5) Impact on the financial statements

This example treats office supplies as an operating expense and indirect tax as a balance sheet control item rather than an expense.

Statement of profit or loss (net of indirect tax)

• Net revenue effect:
• Net sales = £500 − £100 = £400
• Office supplies expense:
• Office supplies expense = £1,800 net
• This assumes all office supplies received and retained are consumed in the period.

Statement of financial position

• Trade receivables (gross):£80
• Trade payables (gross):£1,360
• Indirect tax recoverable:£280(current asset)
• Bank: cash receipts of £850 and supplier payment of £800 give a net increase of £50 for the month.

Common pitfalls and misunderstandings

• Treating invoices as the sole trigger for revenue or liability recognition, rather than focusing on delivery/service and the existence of rights and obligations.
• Mixing net and gross figures within control accounts (be consistent with system configuration).
• Forgetting that credit notes reverse both the base amount and the related indirect tax.
• Recording supplier invoices for amounts not delivered/accepted and failing to adjust disputed overbilling.
• Misclassifying operating expenses as inventory (or vice versa), leading to incorrect cost of sales.
• Misallocating receipts to the wrong customer or the wrong invoice, causing reconciliation differences.
• Skipping reconciliations because the system “looks right” (errors can be systematic and repeatable).
• Weak cut-off control: recording transactions in the wrong period by ignoring delivery/service dates.
• Poor audit trail discipline: missing references, missing attachments, or unclear correction entries.

Summary

Reliable transaction capture depends on three building blocks: credible evidence, correct classification, and disciplined double-entry posting. Source documents support the recording process and strengthen the audit trail, but accounting treatment still depends on recognition and measurement principles. Computerised systems improve speed and consistency, yet matching, approvals, exception reporting, and reconciliations remain essential to keep data complete and dependable.

FAQ

What is the importance of source documents in accounting?

They provide evidence that a transaction occurred and support the amount and timing recorded. They also help prevent omissions, duplicates, and unauthorised transactions, and they enable balances to be traced back to underlying activity.

Do invoices decide when revenue or liabilities are recognised?

Invoices are important evidence for billing and measurement, but recognition depends on whether goods or services have been delivered (for revenue) and whether goods or services have been received and an obligation exists (for liabilities).

How do computerised accounting systems improve transaction processing?

They standardise data entry, automate postings between modules and the general ledger, and provide real-time reports. They also support validation rules, user permissions, and audit trails that help prevent and detect errors.

What are common pitfalls when handling indirect taxes such as VAT?

Typical errors include using incorrect tax codes, ignoring tax reversals on credit notes, and claiming input tax on amounts later corrected or disputed. Regular reconciliation of the tax control account helps identify issues early.

Why is reconciliation important in accounting?

Reconciliation confirms that records are complete and consistent. It highlights missing postings, duplicate postings, misallocations, and timing differences before they distort reported results and balances.

What is the role of an audit trail?

It provides traceability between source documents, journals, ledgers, and reported balances. This supports transparency, speeds up error investigation, and strengthens the credibility of financial information.

Summary (Recap)

This chapter explains how accounting systems convert business activity into dependable financial data. It covers source documents, transaction classification, double-entry logic, and the way computerised systems process and store transactions while maintaining an audit trail. It also emphasises matching and reconciliations as essential controls. The worked example demonstrates the treatment of invoices, credit notes, payments, disputed supplier billing, and indirect tax, and shows how these affect receivables, payables, bank, and tax control balances.

Glossary

Source document
Original evidence of a transaction or event used to support accounting entries and traceability.

Transaction
A business event that can be measured and recorded because it changes assets, liabilities, equity, income, or expenses.

Quotation
A supplier’s price offer provided before an order is placed.

Sales order
A record that a customer has requested goods or services, used to initiate fulfilment and billing.

Purchase order (PO)
A document raised by the buyer to authorise a purchase and request supply under agreed terms.

Goods received note (GRN)
Evidence that goods were delivered and checked, supporting invoice verification and completeness.

Sales invoice
A document issued to a customer requesting payment for goods or services supplied.

Supplier invoice
A document received from a supplier requesting payment for goods or services provided.

Credit note
A document that reduces a previously billed amount, commonly used for returns or pricing adjustments.

Debit note
A document notifying the other party of an additional charge or upward adjustment.

Remittance advice
A message sent with payment explaining how it should be allocated to invoices.

Receipt
Evidence that money has been received, typically supported by bank confirmation or cash documentation.

Audit trail
The traceable link from source evidence through journals and ledgers to reported balances, and back again.

Cloud-based storage
Holding accounting data on remote servers accessed via the internet, enabling remote access and centralised backups.

Loss allowance on receivables
A contra-asset that reduces receivables to the amount expected to be collected (often described in practice as an expected credit loss allowance).