How to collect payments faster: seven practices for small businesses

Why do customers pay late?

Customers pay late mostly because nothing in the process asks them to pay on time. The invoice reaches them days after delivery, the due date is unclear, and nobody follows up until the money is badly overdue.

Each practice below removes one of those reasons. Together they form a routine an owner or one accountant can run in an hour a week. The worked examples use Lakshmi Steel Furnitures, the fictional Coimbatore business on this site, which sells steel racks and office furniture to dealers, mostly on 30 days' credit.

1. Invoice the same day you deliver

Credit days count from the invoice date, so every day you wait to invoice is a day added to the time you wait for money. A delivery made on 3 October and invoiced on 10 October on 30-day terms is due on 9 November, not 2 November.

Same-day invoicing also cuts disputes. The customer checks the invoice against goods they unloaded that morning, not against a memory from last week. Make it a rule that no vehicle leaves the godown without its invoice.

• Mechanism: the clock starts earlier, and the invoice matches what the customer just received.
• Example: Lakshmi Steel moved from weekly batch invoicing to invoicing at dispatch. Its average delay between delivery and invoice fell from 4 days to zero, which on its own pulls every due date 4 days earlier.

2. Put a UPI QR code on the invoice

A UPI QR code on the invoice lets the customer pay the moment they agree with it, from the phone already in their hand. Many small buyers delay simply because paying means finding your bank details, typing an account number and checking an IFSC code.

In SimpleERP the invoice prints a UPI QR code, so a dealer who receives the PDF can scan and pay without asking for details. You still record the payment against the invoice when it reaches your bank, which keeps the invoice balance right.

• Mechanism: fewer steps between deciding to pay and paying.
• Example: a dealer settling a ₹23,600 invoice for four racks can pay by scanning the code on the printed invoice at the counter, instead of promising a bank transfer "by Friday".

3. State the due date and credit days on the document

An invoice that shows a due date gets paid closer to that date than one that only says "30 days credit" or says nothing at all. A date is a commitment the customer's accountant can schedule; a term is something to work out later.

Set payment terms and credit days per customer, so the due date is calculated on each invoice rather than typed. SimpleERP keeps payment terms, credit days and a credit limit on every customer and prints the due date on the invoice. Agree the terms in writing when you open the account, and repeat them on the first invoice.

• Mechanism: a fixed date removes the room to interpret the terms.
• Example: invoice INV-2026-27-0241 dated 1 October to Sri Murugan Traders on 45 credit days prints "Due 15 November 2026".

4. Send a statement of account on the first of the month

A monthly statement collects more than a reminder because it shows the customer every open invoice, every payment and one closing balance on a single page. Their accountant can tick it off against their own ledger and pay the lot, instead of paying whichever invoice happens to be on top.

Send it on the first working day of each month to every customer with a balance, and weekly to anyone overdue. SimpleERP produces a statement of account per party with an opening balance, dated rows, a running balance, the closing balance and an ageing footer. Print it, save it as a PDF, or use copy share text and send it from your phone. See the statement of account guide for wording.

• Mechanism: the customer sees the full balance and any missing credit notes surface early.
• Example: Kovai Office Interiors disputed one ₹14,160 invoice for months. The statement showed it was the only open item older than 30 days, and the dispute was settled in one phone call.

5. Call on day 7 past due, not day 60

A polite call one week after the due date recovers most overdue invoices, because at that point the delay is usually an oversight, not a cash problem. By day 60 the invoice has slipped behind newer suppliers who asked sooner.

Use the ageing report to build the list. Anything in the 1 to 30 days overdue bucket gets a message on day 1 and a call on day 7. SimpleERP gives you reminder text to copy for each overdue customer; you send it from your own phone or email. The debtors ageing report guide explains what to do with each bucket.

1. 1

   Day 1 past due

   Send the copied reminder with the invoice number, amount and due date.

2. 2

   Day 7 past due

   Call the person who approves payments. Ask for a date, not a promise.

3. 3

   Day 15 past due

   Send the statement again and confirm the date agreed on the call.

4. 4

   Day 30 past due

   The owner calls the owner. Hold new orders until the date is met.

6. Offer a settlement discount through a credit note

A small discount for paying early can be cheaper than waiting, and the clean way to give it is a credit note against the invoice after the money arrives. The invoice stays as issued, the credit note records the discount, and the customer's balance closes at zero.

Agree the discount in writing before the sale, for example 2% if paid within 10 days. Whether the credit note also reduces your output GST depends on how and when the discount was agreed, so confirm it with your CA. Here is Lakshmi Steel's credit note to Sri Murugan Traders on an intra-state invoice at 18%:

Before offering it, compare the cost with what the money is worth to you. ₹2,360 to receive ₹1,15,640 about five weeks early is a high price if you have no pressing use for the cash, and a fair one if it saves you a month on an overdraft. Read credit notes and debit notes under GST for the reporting rules.

7. Stop supply when a customer reaches the credit limit

A credit limit only shortens collection if new orders wait when the customer reaches it. Without that, a slow payer keeps buying on credit and the oldest invoices never get paid, because there is always a newer one to pay instead.

When an invoice would take a customer over their limit, SimpleERP shows a warning at invoice time. The warning does not block the invoice; posting needs the approve permission anyway, so the person who approves decides whether to supply. Set limits using the method in credit limits and credit days.

• Mechanism: the next order becomes the reason to clear the old balance.
• Example: Annai Enterprises has a ₹3,00,000 limit and owes ₹2,85,000. A new order for ₹40,000 triggers the warning, and the approver asks for ₹1,00,000 against the oldest invoices before dispatch.

How much difference do these practices make?

The usual measure is days sales outstanding (DSO): receivables divided by average daily sales over the last 90 days. The figures below are an example, not a promise, for a business with ₹12,20,000 of sales in 90 days.

What is a weekly collections routine that works?

A weekly routine of under an hour keeps all seven practices running. Do it on the same day every week:

• Check that every dispatch from last week has a posted invoice
• Record every payment received and allocate it to the right invoices
• Open the ageing report and list customers with anything past due
• Send copied reminders for invoices 1 to 6 days overdue
• Call customers with invoices 7 or more days overdue and note the promised date
• Review customers near their credit limit before approving new invoices
• On the first of the month, send every customer with a balance their statement

How does SimpleERP help you collect faster?

SimpleERP puts the due date, credit days and a UPI QR code on every invoice, ages receivables by party with a row that expands to invoices, and produces statements and reminder text you can copy and send. Payments can be split across many invoices, and the database marks each invoice posted, partially paid or paid.

See payments and receivables for the full module, and the accounts receivable management guide for the system these practices sit in.