Bill-wise outstanding and ageing: knowing exactly who owes what

Bill-wise outstanding means every receipt is matched against the specific invoices it pays, so that what remains is a list of unpaid bills with dates, not a single balance. A party ledger that says ₹2,40,000 is a number. A list that says four invoices, the oldest from 14 June, two of them past the thirty-day credit period, is a phone call. Most billing software can produce the first. Whether it produces the second is worth checking before you buy.

Ledger balance against bill-wise outstanding

Both are needed and they must agree. The total of the unpaid bills, adjusted for any money received on account, has to equal the ledger balance. If your software lets those two numbers differ, one of them is being maintained by hand and will eventually be wrong.

How receipts should be adjusted

When a customer pays ₹50,000 against four outstanding bills, someone has to decide which bills that money clears. There are three sane approaches, and software should support all three.

1. Oldest first, which is the default in most Indian businesses and the correct one for ageing. A receipt clears the earliest bills until it runs out.
2. Against specified bills, when the customer says which invoice they are paying, which is common where each bill is matched to a purchase order.
3. On account, when nobody knows yet. The money sits against the party, reduces the balance and stays visible as unadjusted until it is applied.

The third option is the one that keeps books honest. Forcing every receipt to be allocated immediately produces arbitrary allocations that someone has to unpick later. Allowing on-account money that is never reviewed produces a party whose bills all look overdue while their balance is nil. The answer is to permit it and report it: an on-account figure that nobody has cleared in a month is a task, not a state.

Ageing buckets that are actually useful

The conventional buckets are 0 to 30, 31 to 60, 61 to 90 and over 90 days. They are a reasonable default and slightly wrong for most businesses, because they age from the invoice date rather than from the due date. If you give one customer 30 days and another 60, the same 45-day-old bill is healthy for one and overdue for the other.

• Store a credit period on the party, and a due date on the bill.
• Age from the due date, and show the invoice date next to it.
• Show the oldest unpaid bill per party, which is the single most predictive number in the report.
• Sort by value within the oldest bucket, because effort should follow money.
• Keep a column for the last follow-up date, so two people do not call the same customer on the same morning.

Tatva ERP produces outstanding with first-in-first-out ageing, shows pending bills on the party's own page alongside their ledger and what they have bought, and puts overdue customers on the dashboard so the list is seen without anyone running a report. Financial year close carries bill-wise outstanding forward, so an invoice from March is still an invoice in April rather than an opening lump.

The migration trap

When a business moves to new software, the fastest migration brings party balances in as one opening figure each. It is also the migration that destroys the outstanding report for a year, because a single opening balance has no bill dates and therefore no age. Bring opening balances in as the individual pending bills with their original dates. It takes an extra afternoon and it is the difference between a working ageing report in month one and an ageing report that starts to mean something next April. The general version of this advice is in moving off Excel, Tally or legacy software.

A collection routine that works

1. Every Monday, print or export the bills past their due date, sorted by value.
2. Send a statement rather than a reminder. A customer who can see the invoice numbers and dates pays faster than one who is told they owe money.
3. Call the top ten. Record what was said and the date promised, against the party.
4. On the promised date, call again the same day. A promise followed up on the day it was made is worth several that are not.
5. Once a month, review the customers whose oldest bill keeps getting older, and decide whether to keep supplying them on credit.

Two related pieces cover the surrounding process: receivables and dues tracking for SMEs, and WhatsApp follow-ups that get replies, which applies as much to a payment reminder as to a sales follow-up.

Frequently asked questions

What is bill-wise outstanding?

A record of which specific invoices remain unpaid for each party, with their dates and amounts, produced by matching every receipt to the bills it settles. It is different from the party's ledger balance, which is a single net figure and cannot tell you how old the debt is.

What are the standard ageing buckets?

0 to 30, 31 to 60, 61 to 90 and above 90 days are the common ones. Age from the due date rather than the invoice date if your customers have different credit periods, otherwise the report treats a punctual 60-day customer as though they were late.

How should advances from customers be handled?

As an on-account receipt against the party, visible as unadjusted until an invoice is raised and the money is applied to it. Keep advances out of the ageing buckets, and review unadjusted amounts monthly. Note that advances received for goods and services have their own GST treatment, which your accountant will set out for your case.

Does an outstanding report replace a ledger statement?

No, they answer different questions and you need both. Send the ledger statement to the customer, because it shows every transaction and reconciles; use the outstanding report internally, because it tells your team which bill to chase first.