Friday, December 18, 2009

, ,

Control Accounts: Receivables and Payables Explained

Last reviewed: July 2026.

A control account summarises transactions recorded in detailed customer or supplier accounts. Traditionally, a receivables control account was reconciled to the list of individual customer balances, and a payables control account was reconciled to supplier balances.

Modern integrated software updates the general ledger and individual account simultaneously, so the old independent double-entry cross-check may not operate in exactly the same way. The concept remains valuable for understanding totals, migrations, interfaces, exception reports and incomplete-records calculations.

Purpose of control accounts

  • summarise the total amount owed by customers or owed to suppliers;
  • support reconciliation between detailed records and the general ledger;
  • identify posting, interface and master-data errors;
  • provide figures for the trial balance and financial statements;
  • support missing-figure calculations in incomplete records.

Typical entries

Receivables control — debitReceivables control — creditPayables control — creditPayables control — debit
Opening debit balancesCash receivedOpening credit balancesCash paid
Credit salesSales returnsCredit purchasesPurchase returns
Interest/charges to customersDiscounts allowedCharges by suppliersDiscounts received
Reinstated balancesBad debts and contra entriesReinstated liabilitiesContra entries

The exact layout depends on whether the account is prepared from the perspective of receivables or payables and whether unusual debit or credit balances are shown separately.

Receivables control worked example

Opening receivables are 48,000 CU. Credit sales are 260,000 CU. Cash received is 238,000 CU, sales returns are 9,000 CU, discounts allowed are 4,000 CU and bad debts are 2,000 CU:

Closing receivables = 48,000 + 260,000 − 238,000 − 9,000 − 4,000 − 2,000 = 55,000 CU

The total should agree with the customer listing after valid timing and other reconciling items are considered.

Payables control worked example

Opening payables are 36,000 CU. Credit purchases are 210,000 CU. Payments are 190,000 CU, purchase returns are 6,000 CU and discounts received are 3,000 CU:

Closing payables = 36,000 + 210,000 − 190,000 − 6,000 − 3,000 = 47,000 CU

Contra entries

A contra can arise when the same entity is both a customer and a supplier and the parties have a valid right and agreement to offset amounts. The receivables control and payables control are both reduced. Contra entries should be authorised, documented and consistent with legal offsetting rights.

Why a reconciliation may differ

  • a transaction posted to the general ledger but not the subledger, or vice versa;
  • duplicate or failed interface batches;
  • manual journals posted directly to a control account;
  • incorrect customer or supplier allocation;
  • timing differences during data import;
  • unusual debit balances in payables or credit balances in receivables;
  • currency translation or cut-off differences.

Modern computerised systems

ACCA’s computerised-accounting guidance explains that integrated sales and purchase systems update the general ledger and individual accounts simultaneously. Consequently, a reconciliation of two reports generated from the same posting event may not provide independent assurance by itself.

Instead, focus controls on source documents, authorisation, interface completeness, exception reports, customer/supplier master data, bank settlement and independent external statements. ACCA’s internal-controls article identifies reconciliations and accounting controls as part of reliable financial reporting.

Control accounts in incomplete records

If one figure is missing, the control-account equation can reconstruct it. For example, opening receivables, receipts, returns, write-offs and closing receivables can determine credit sales. This use does not depend on maintaining a separate manual ledger.

Reconciliation procedure

  1. Confirm the reporting date and currency.
  2. Obtain the control-account balance and detailed listing.
  3. Recalculate totals and identify unusual debit or credit balances.
  4. Trace differences to source documents, batches and journals.
  5. Correct the underlying record, not only the reconciliation.
  6. Document unresolved items, ownership and completion dates.
  7. Obtain independent review.
Avoid a false control
Two reports from the same database may agree even when the original transaction is wrong. Reconciliation should be combined with external evidence, authorisation and exception review.

Common errors

  • putting cash sales into receivables;
  • using gross receipts without separating refunds;
  • omitting discounts, returns, write-offs or contra entries;
  • reversing the payables debit and credit logic;
  • posting journals directly to control accounts without approval;
  • clearing old differences without evidence.

Related learning

Review sales-ledger inputs, source documents, the trial balance worked example and accounting-software workflow and controls.

Manual control accounts versus system-generated controls

In a manual system, the control account may be compiled from separate books and compared with independently maintained personal accounts. In an integrated system, one transaction can update both levels from the same database. Agreement is therefore expected, but it may only prove that the posting engine worked consistently.

Modern assurance should test whether every source transaction entered the system once, whether interfaces completed, whether rejected items were resolved and whether users could bypass normal processing. Useful evidence includes batch-control totals, interface logs, change reports, customer and supplier statements, bank receipts and independent review of journals posted to control accounts.

Period-end and migration use

Control-account reconciliations become particularly important during a system conversion. Reconcile old and new customer or supplier listings, total balances, open invoices, credit notes and unapplied cash. Differences should be resolved before the legacy system is retired. At period end, investigate balances that are very old, negative, disputed, in a foreign currency or inconsistent with recent activity.

Key takeaway

Control accounts connect detailed customer and supplier activity to financial-statement totals. In integrated systems, the strongest process combines ledger reconciliation with external evidence, interface checks, access controls and investigation of exceptions.

Advertisement