Receivables, Payables, Banking and Cash Management

Introduction and Context

Credit sales and credit purchases create timing differences between the recognition of a transaction and the movement of cash. For an organisation, this difference produces receivables, payables, bank balances, outstanding cheques, deposits in transit, and liquidity risk. Tally.ERP 9 provides an integrated environment for recording these transactions, tracking bill references, monitoring overdue balances, calculating interest where configured, issuing reminders, reconciling bank accounts, and controlling cash movements.

For a Chartered Certified Accountant, the objective is not merely to enter vouchers. The objective is to design reliable records that answer five questions:

1. Who owes the entity money, and when is it due?
2. Whom does the entity owe, and when must payment be made?
3. Which recorded bank transactions have actually cleared?
4. What cash is available for operating and financing commitments?
5. Are controls sufficient to prevent unauthorised, duplicate, late, or misclassified transactions?

Tally.ERP 9 supports these objectives through ledger masters, bill-wise details, credit limits, credit periods, interest parameters, reminders, payment and receipt instruments, post-dated vouchers, and bank reconciliation facilities. Its effectiveness depends on accurate configuration, disciplined source documentation, and periodic review.

Learning Objectives

After completing this chapter, the learner should be able to:

• configure receivable and payable ledgers for bill-wise accounting;
• record credit terms, bill references, advances, adjustments, and settlements;
• analyse receivable and payable ageing and calculate simple overdue interest;
• use reminders and statements to support collection and payment decisions;
• process cheques, deposits, post-dated transactions, and bank charges;
• perform bank reconciliation and investigate differences;
• establish cash-flow controls and evaluate the limitations of accounting-system reports;
• apply professional judgement, segregation of duties, and audit evidence requirements.

1. Conceptual Foundation: From Transaction to Cash

A credit transaction normally passes through the following stages:

Invoice → bill reference → due date → collection or payment instrument → bank clearance → reconciliation → reporting.

The accounting entry may be complete before the bank statement reflects the related cash movement. For example, when a customer cheque is received, the entity may record a receipt into a cheque-in-hand or undeposited-funds account. Cash at bank should not be increased until the cheque is deposited and, depending on the organisation's policy, cleared. Recording the receipt directly into the bank ledger before clearance can overstate available bank cash.

Receivables represent enforceable claims against customers. Payables represent obligations to suppliers and other creditors. Both are monetary working-capital balances. Their management involves not only accounting accuracy but also credit risk, liquidity planning, supplier relationships, and fraud prevention.

Important terminology

2. Configuration for Receivables and Payables

2.1 Company and accounting features

Before entering transactions, the administrator should review the company date, financial year, currency, statutory settings, voucher numbering, and security controls. In Tally.ERP 9, bill-wise details are generally enabled through F11: Accounting Features, using the option for maintaining bill-wise details. The exact menu labels may vary by release and localisation, so configuration should be validated against the organisation's installed version.

For customer and supplier ledgers, the account group is significant. Customer accounts are normally placed under Sundry Debtors and supplier accounts under Sundry Creditors. The ledger master should contain an appropriate credit period where applicable. Credit limits should be established through documented credit policy rather than entered arbitrarily.

A sound master-data design includes:

• unique customer and supplier names;
• tax registration and legal identification details where required;
• approved credit period and credit limit;
• salesperson, territory, or cost-centre attributes where useful;
• bank details subject to independent verification;
• contact details for statements and reminders;
• opening balances split by bill reference, not merely entered as one unexplained total.

2.2 Bill-wise references

When a sales invoice is recorded with bill-wise details, the system can create a New Reference, commonly representing an invoice number. A receipt may subsequently be allocated against that reference. If a customer pays before an invoice exists, the receipt is recorded as an Advance or On Account, depending on the organisation's policy and configuration. Once the invoice is raised, the advance can be adjusted.

The same logic applies to suppliers. A payment may be allocated to a specific purchase bill, recorded as an advance, or left on account. Incorrect allocation causes misleading ageing, apparent overdue balances, and unreliable statements even when the control-account total is correct.

2.3 Credit terms and due dates

A due date is normally determined from the invoice date and agreed credit period. If the invoice date is D and the credit period is n days, a basic due-date rule is:

This formula assumes calendar-day terms and excludes special contractual rules such as month-end terms, business-day conventions, grace periods, or statutory payment rules. The system's due-date calculation should therefore be compared with the contract or purchase order.

3. Recording and Settling Receivables

3.1 Credit sales

A credit sales voucher records the customer, items or services, tax treatment, invoice number, invoice date, and bill reference. The accounting effect is generally:

• Debit: Customer receivable
• Credit: Sales revenue and applicable tax liabilities

The invoice should be supported by delivery evidence, an approved order, pricing terms, and tax documentation. A posting that lacks a valid customer or reference may prevent accurate collection follow-up.

3.2 Receipts and allocation

A receipt voucher records money received. The debit account depends on the instrument:

• Bank account, when the amount is credited or treated as cleared under policy;
• Cash account, when physically received in cash;
• Cheque-in-hand or undeposited-funds account, when received but not deposited;
• Electronic collection account, when a clearing or payment gateway account is used.

The customer ledger is credited and the receipt is allocated to one or more bill references. Partial settlement should be allocated to the relevant bill, leaving a controlled balance. If a receipt covers several invoices, allocation should follow remittance advice or documented oldest-due-first policy.

3.3 Adjustments, returns, and write-offs

Credit notes may reduce customer balances for returns, price concessions, or other approved adjustments. A write-off should not be used as a convenient substitute for correcting an incorrectly allocated receipt. Bad-debt write-offs require authorisation and appropriate tax and financial-reporting treatment. The accounting system should preserve the original invoice and adjustment trail.

3.4 Customer statements and reminders

Customer statements should show opening balance, invoices, credit notes, receipts, adjustments, and closing balance. A reminder process should be graduated:

1. pre-due courtesy communication;
2. due-date reminder;
3. first overdue notice;
4. escalation to account management or credit control;
5. credit hold, collection action, or legal review where justified.

Reminders should be based on verified balances. Sending a demand for an invoice already paid damages customer relationships and indicates weak reconciliation.

4. Managing Payables

4.1 Purchase bills and supplier references

A purchase voucher records the supplier, invoice number, date, goods or services, tax, terms, and bill reference. The normal effect is:

• Debit: Inventory, expense, fixed asset, or other appropriate account;
• Debit: Recoverable tax, where legally applicable;
• Credit: Supplier payable and related tax obligations.

The three-way match—purchase order, receipt evidence, and supplier invoice—is an important control. A bill should not be paid solely because it appears in the system; the organisation must establish that the goods or services were authorised and received.

4.2 Payments and supplier advances

A payment voucher debits the supplier ledger and credits bank, cash, or another payment account. The payment should identify the bill or bills settled. Supplier advances should be separately visible and periodically matched against subsequent invoices. Unallocated debit balances in a supplier ledger require investigation because they may represent advances, duplicate payments, wrong-party postings, or unapplied credits.

4.3 Payment scheduling

A payable schedule should consider due date, contractual discounts, cash availability, supplier criticality, and risk of late-payment penalties. Paying every invoice immediately may reduce cash unnecessarily; delaying all invoices may damage credit standing. A professional payment proposal separates:

• due and approved invoices;
• invoices awaiting approval;
• disputed invoices;
• statutory and payroll obligations;
• strategic supplier payments;
• future-dated or scheduled payments.

5. Ageing Analysis and Interest

5.1 Ageing principles

Ageing reports classify open bills by age. Two bases are common:

• Invoice-ageing basis: time elapsed since invoice date;
• Due-date ageing basis: time elapsed since contractual due date.

For credit control, due-date ageing is usually more decision-useful because an invoice within its agreed credit period is not yet delinquent. A report must state its basis, date of analysis, and treatment of advances and credit balances.

If the analysis date is A and the due date is D, overdue days are:

where o is overdue days. This expression assumes dates are measured in calendar days and that an invoice due on the analysis date is not overdue. Organisations may adopt different contractual conventions.

Typical bands are Current, 1–30 days overdue, 31–60, 61–90, and over 90 days. Bands should reflect the entity's collection cycle and risk profile rather than being copied mechanically.

5.2 Overdue interest

Where a contract permits simple interest, the amount may be calculated as:

where I is interest, P is the overdue principal, r is the annual interest rate expressed as a decimal, and t is time in years. If time is measured in days and a 365-day convention applies:

This formula assumes a constant principal, simple—not compound—interest, a 365-day year, and that interest is legally and contractually chargeable for the entire stated period. Tax treatment, minimum interest thresholds, leap-year conventions, and compounding terms may differ.

Worked example. An approved overdue principal of CU 120,000 is outstanding for 45 days at 12% per annum. Therefore:

I = 120,000 × 0.12 × (45 ÷ 365)

I ≈ CU 1,775.34.

The figure is an accounting estimate under the stated assumptions. It should not be posted automatically unless the contract, approval policy, and applicable law support the charge. In Tally.ERP 9, interest parameters may be configured in ledger or company settings, but the resulting calculation must be reviewed for rate, date basis, exemptions, and settlement status.

5.3 Interpreting ageing

Ageing is not a probability-of-default model. A customer in the over-90-day column may be financially sound but disputing one invoice; another customer with a current balance may be highly risky. Advanced analysis combines ageing with payment history, concentration, disputes, credit insurance, collateral, sector risk, and subsequent receipts.

6. Banking and Cheque Processing

6.1 Bank ledger design

Separate bank ledgers should normally be maintained for each bank account and, where useful, for distinct currencies or operational purposes. Bank charges, interest, direct debits, standing orders, and electronic transfers must be recorded in the correct ledger. Mixing personal, petty-cash, and corporate accounts undermines auditability.

6.2 Cheques received

A controlled cheque process may use the following sequence:

1. record receipt into cheque-in-hand;
2. preserve cheque number, date, drawer, bank, and amount;
3. deposit the cheque and record transfer to bank or deposit account;
4. reconcile the bank credit when it appears;
5. reverse or reclassify the receipt if the cheque is dishonoured.

A dishonoured cheque should not remain as a valid reduction of the customer's receivable. The original receipt may be reversed, and bank charges may be charged to the customer only where contractually and legally permitted.

6.3 Cheques issued

A payment may be entered when a cheque is prepared, or when it is released/cleared, depending on the organisation's accounting policy and system design. The chosen approach must be consistent. If the supplier payable is reduced when the cheque is issued, the cheque should be included in an outstanding-cheque control until it clears. If the payable is reduced only on clearance, the payment instrument remains a commitment rather than a completed settlement.

Cheque registers should control serial numbers, cancellations, stale items, stop-payment instructions, signatories, and supporting approvals.

6.4 Post-dated transactions

Post-dated vouchers are useful for recording a future transaction without treating it as effective before its date. They are particularly relevant for scheduled instalments, future-dated cheques, and recurring commitments. A post-dated entry must not be confused with a present cash movement. Reports should distinguish current transactions from post-dated commitments so that liquidity forecasts are not overstated.

7. Bank Reconciliation

7.1 Purpose and method

Bank reconciliation compares the book balance with the balance shown by the bank statement at the same date. Differences commonly arise from:

• cheques issued but not yet presented;
• deposits recorded in books but not yet credited by the bank;
• bank charges or interest not yet entered in the books;
• direct debits and standing orders;
• errors by the entity or bank;
• duplicate or omitted entries;
• timing differences caused by electronic payment processing.

A reconciliation is not merely a matching exercise. Each difference must be classified, evidenced, and cleared within an expected timeframe.

A standard adjusted-balance relationship can be stated as:

This is a reconciliation framework, not a universal sign convention. The sign applied to an error depends on whether the book balance is too high or too low. The adjusted book balance should agree with the bank balance after all timing differences are considered.

Worked example. The book bank balance is CU 84,600. The bank statement shows CU 80,000. Cheques issued but not presented total CU 6,200, and deposits in transit total CU 3,100. The bank-side adjusted balance is:

80,000 + 6,200 − 3,100 = CU 83,100.

The difference from the book balance is CU 1,500. Investigation may reveal, for example, bank charges of CU 900 and a direct debit of CU 600 not recorded in the books. After recording both debits, the adjusted book balance is CU 83,100, agreeing with the bank-side figure.

7.2 Practical reconciliation procedure in Tally.ERP 9

A disciplined procedure is:

1. obtain the complete bank statement and establish the reconciliation date;
2. verify the opening balance against the prior reconciled closing balance;
3. enter or import bank transactions according to approved procedures;
4. use the bank reconciliation facility to compare transaction dates, amounts, and instruments;
5. identify uncleared receipts, uncleared payments, bank-originated items, and errors;
6. post legitimate bank-originated transactions with supporting evidence;
7. correct errors through authorised vouchers rather than silent deletion;
8. review old uncleared items and document follow-up;
9. retain the reconciliation, statement, explanations, and approvals.

Depending on the release and setup, Tally.ERP 9 may provide bank-date fields and reconciliation views. Automatic matching is helpful but is not a substitute for human review, especially where amounts repeat or narration is incomplete.

8. Cash-Flow Controls and Management Information

Accounting profit does not equal cash available. A cash-flow control system should combine:

• daily cash and bank positions;
• receivable collection forecasts;
• payable due-date schedules;
• payroll, tax, loan, and lease commitments;
• minimum operating cash thresholds;
• approved payment batches;
• short-term borrowing and investment plans.

A simple weekly cash forecast is:

This identity assumes all flows are expressed for the same period and that financing and investing flows are included where relevant. A forecast should distinguish committed, probable, and speculative flows.

Key controls include segregation between vendor creation, invoice approval, payment preparation, payment authorisation, and bank reconciliation. Other controls are dual approval for high-value payments, independent verification of changes to supplier bank details, restricted access to post-dated vouchers, sequential cheque control, daily cash counts, and review of negative cash or unusual on-account balances.

9. Integrated Illustrative Case

The following is a fictional illustrative case.

Background

Northbridge Components Ltd sells industrial parts on 30-day credit and purchases packaging materials on 45-day credit. It uses Tally.ERP 9 but has enabled bill-wise details inconsistently. Receipts are often posted directly to the bank ledger when cheques are received. Bank reconciliation is performed quarterly.

Problem

Management reports a healthy bank balance, yet suppliers complain about late payment and the finance director cannot explain why receivables over 90 days have increased. A review finds that two customer receipts were allocated on account, three supplier advances were netted against unrelated bills, and several cheques issued six weeks earlier remain unpresented.

Analysis

The apparent bank position includes cheques received but not cleared. The receivables ageing is overstated for individual invoices because receipts were not allocated to bill references. The payable report understates future obligations because advances and disputed invoices were not classified. Quarterly reconciliation has allowed old errors to accumulate.

Approach and solution

The controller implements the following programme:

1. enable and test bill-wise accounting for all material customer and supplier ledgers;
2. reconstruct opening bill references from invoices, receipts, and supplier statements;
3. establish a cheque-in-hand account for received cheques;
4. require receipt allocation using remittance advice or an approved allocation rule;
5. introduce weekly bank reconciliation and a 30-day review of uncleared items;
6. create receivable ageing based on due date, with dispute and credit-risk flags;
7. prepare a 13-week rolling cash forecast;
8. impose dual approval for supplier-bank-detail changes and payment batches;
9. issue customer statements and supplier confirmations monthly;
10. review system access and retain an audit trail for corrections.

Outcome

After two reporting cycles, management identifies that the true overdue receivable balance is lower than originally reported, but liquidity is tighter because several supplier obligations had been concealed by poor allocation. The revised forecast allows management to negotiate payment dates, accelerate selected collections, and avoid an unnecessary short-term borrowing drawdown. The organisation also detects one duplicate supplier invoice before payment.

Learning points

The case demonstrates that system functionality cannot compensate for weak process design. Bill-wise accuracy improves both collection activity and supplier payment planning. Bank reconciliation is a control over cash existence and completeness, not merely a month-end administrative task. Finally, ageing, cash forecasts, and ledger balances must be interpreted together.

10. Limitations, Governance, and Contemporary Practice

Tally.ERP 9 reports are only as reliable as the masters, dates, references, and vouchers entered. Common limitations include inaccurate opening balances, excessive use of “On Account,” backdated entries, shared user credentials, unreviewed automated calculations, and failure to distinguish cleared from uncleared instruments.

Electronic banking and bank-statement imports can reduce manual entry, but imported data may contain ambiguous narration, duplicate lines, reversals, or settlement delays. Rules-based matching and emerging AI-assisted reconciliation can prioritise likely matches, but final responsibility remains with an authorised accountant. AI should not independently approve payments, alter supplier bank details, or write off receivables without documented governance.

Professional and regulatory considerations include applicable financial-reporting standards, tax and invoicing requirements, data-protection obligations, anti-fraud controls, retention of source documents, and statutory payment rules. Interest must be charged only when contractually and legally supportable. Customer and supplier information should be accessed on a need-to-know basis.

Best practice is to reconcile control accounts to subsidiary bill-wise reports, confirm material balances externally, investigate aged unapplied items, monitor credit-limit breaches, review subsequent receipts and payments, and document all significant judgements. A strong month-end close should include receivables ageing, payables ageing, bank reconciliations, cash forecast variance, uncleared-instrument review, and management sign-off.

Chapter Summary

Receivables and payables management in Tally.ERP 9 depends on properly configured ledgers, bill-wise references, reliable credit terms, and disciplined allocation of receipts and payments. Ageing should state whether it is based on invoice date or due date, and overdue interest should be calculated only under valid contractual and legal assumptions. Cheque-in-hand accounts, post-dated vouchers, cheque registers, and bank reconciliation distinguish accounting recognition from actual cash clearance. Cash management combines ledger information with forecasts of receipts, payments, statutory obligations, and financing needs. Effective governance requires segregation of duties, independent bank-detail verification, approval controls, audit trails, periodic confirmation, and professional review of automated or AI-assisted processes.

Key Terms

Bill-wise accounting: Tracking individual invoices and settlements rather than only ledger totals.

Credit period: Agreed time allowed before an amount becomes due.

Credit limit: Maximum approved exposure to a customer or counterparty.

Receivable: Amount owed to the entity by a customer or other debtor.

Payable: Amount owed by the entity to a supplier or other creditor.

Bill reference: Identifier linking a settlement to an invoice or other bill.

On account: Entry not allocated to a specific bill reference.

Advance: Amount received or paid before the related invoice or obligation is settled.

Ageing: Classification of open balances by elapsed or overdue time.

Due-date ageing: Ageing measured from the contractual payment date.

Interest: Compensation charged or earned for the use or late payment of money.

Cheque-in-hand: Temporary account for received cheques awaiting deposit or clearance.

Post-dated voucher: Voucher with a future effective date.

Bank reconciliation: Process of explaining differences between book and bank balances.

Deposit in transit: Book-recorded deposit not yet credited by the bank.

Unpresented cheque: Issued cheque not yet processed by the bank.

Liquidity: Ability to meet obligations when due.

Cash forecast: Estimate of future cash receipts and payments.

Segregation of duties: Division of incompatible responsibilities among different people.

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

Review Questions

Short Answer Questions

1. Why is bill-wise accounting important for receivables and payables?
2. Distinguish invoice-ageing from due-date ageing.
3. What is the purpose of a cheque-in-hand account?
4. Identify four common causes of bank-reconciliation differences.
5. Why should supplier bank-detail changes be independently verified?

Long Answer Questions

1. Explain the complete process for recording, allocating, and monitoring customer receipts in Tally.ERP 9.
2. Discuss how credit periods, credit limits, ageing, reminders, and interest calculations interact in receivables management.
3. Explain the accounting and control implications of cheques received, cheques issued, dishonoured cheques, and post-dated vouchers.
4. Describe a rigorous bank-reconciliation procedure and explain how unresolved items should be investigated.
5. Design a cash-management control framework for a medium-sized trading entity using Tally.ERP 9.

Analytical / Application Questions

1. A customer has a CU 200,000 invoice due 30 days ago, a CU 80,000 unapplied receipt, and a CU 40,000 credit note awaiting approval. Analyse the information required before calculating the customer's true overdue exposure.
2. The book bank balance exceeds the bank statement by CU 9,500. Explain how you would determine whether the difference consists of timing items, unrecorded bank charges, errors, or fraud indicators.
3. A company reports strong profits but repeatedly misses supplier due dates. Using receivables, payables, bank reconciliation, and cash forecasting concepts, diagnose three possible causes and recommend controls.

Multiple Choice Questions with Answers

Question 1

Which Tally.ERP 9 feature most directly supports matching a receipt to a particular customer invoice?

A. Bill-wise details

B. Cost categories

C. Stock journal

D. Payroll attendance

Correct Answer: A. Bill-wise details

Question 2

If an invoice is due on 10 June and the analysis date is 25 June, using calendar days and treating the due date as not overdue, the overdue period is:

A. 10 days

B. 15 days

C. 16 days

D. 25 days

Correct Answer: B. 15 days

Question 3

Which item is normally classified as a timing difference in bank reconciliation?

A. An unapproved duplicate purchase invoice

B. A cheque issued but not yet presented

C. A permanently omitted sales invoice

D. An incorrect customer allocation

Correct Answer: B. A cheque issued but not yet presented

Question 4

Under simple interest at 12% per annum, interest on CU 120,000 for 45 days using a 365-day year is approximately:

A. CU 540.00

B. CU 1,200.00

C. CU 1,775.34

D. CU 5,400.00

Correct Answer: C. CU 1,775.34

Question 5

A customer cheque received but not yet deposited should generally be recorded initially in:

A. Sales revenue

B. Cheque-in-hand or undeposited funds

C. Supplier payable

D. Capital reserve

Correct Answer: B. Cheque-in-hand or undeposited funds

Question 6

What is the principal purpose of due-date ageing?

A. To identify balances according to contractual delinquency

B. To calculate inventory turnover

C. To replace bank reconciliation

D. To determine gross profit

Correct Answer: A. To identify balances according to contractual delinquency

Question 7

Which control best reduces the risk of unauthorised supplier payments?

A. Allowing one employee to create vendors and approve payments

B. Removing all voucher narrations

C. Segregating vendor creation, payment preparation, and approval

D. Posting all payments on account

Correct Answer: C. Segregating vendor creation, payment preparation, and approval

Question 8

If a supplier payment is made before the related invoice is received, it should normally be tracked as:

A. A supplier advance or on-account payment

B. Sales revenue

C. A bank reconciliation error automatically

D. A customer credit note

Correct Answer: A. A supplier advance or on-account payment

Question 9

The basic cash-flow forecast identity is:

A. Closing cash = Opening cash − receipts + payments

B. Closing cash = Opening cash + forecast receipts − forecast payments

C. Closing cash = Revenue − gross profit

D. Closing cash = Assets + liabilities

Correct Answer: B. Closing cash = Opening cash + forecast receipts − forecast payments

Question 10

Why should automated or AI-assisted bank matching be reviewed by an authorised accountant?

A. Because matching can never use transaction amounts

B. Because ambiguous, duplicate, or reversed transactions may be incorrectly matched

C. Because bank statements contain no dates

D. Because reconciliation does not involve evidence

Correct Answer: B. Because ambiguous, duplicate, or reversed transactions may be incorrectly matched