Month-end billing for water suppliers without disputes

Month-end is when a customer sees everything at once. Thirty days of deliveries become one number, and if that number feels wrong, you get a phone call. Most disputes in a jar business are not about bad faith. They come from records that were never checked against what really happened at the door.

This guide covers why disputes happen, how to build a bill that holds up, and what to say when a customer pushes back.

Why disputes happen

• The bill was built from the plan, not from the deliveries. The standing order says two jars a day. On Tuesday the customer got one, on Thursday four. A bill that says sixty jars is wrong either way.
• Skipped stops were billed. The customer was away for four days and the standing order ran anyway.
• Extras were forgotten or double counted. An extra jar on the day was either never added or added twice.
• Part payments were not applied. The customer paid ₹1,000 mid-month and the bill does not show it.
• Price changes were not explained. A customer was quoted one price, and a different one appears on the bill.
• The customer has no record of their own. They cannot check, so they guess, and guesses lean in their favour.

Notice that the cause is nearly always the same. The daily record was not reliable, so the bill built on it was not either.

Build the invoice from a reconciled day

The sequence matters. Reconcile each day first, then bill from the days.

1. Close each day. At the end of every day, check delivered, skipped, extras and empties for each route. Fix mistakes while the driver remembers.
2. Lock the day. Once checked, treat it as final. Changes after that go through the office, with a note.
3. Bill from the locked days. At month-end, the invoice lines come from the days that were closed, not from the standing orders.
4. Show the lines. Each invoice should list the delivery dates and quantities, so the customer can check it against their own memory.

If you cannot trust a day, do not bill it until you have resolved it. A late correct bill is easier to collect than a quick wrong one.

Handling short, extra and skipped stops

These three cases cause most arguments. Decide the rule once and apply it everywhere.

• Short. The customer ordered 4 and received 3. Bill 3. Record the shortfall so you can see whether it was a loading error, a stock problem or a customer decision. If you owe the missing jar, record that and deliver it next visit, but do not bill it twice.
• Extra. The customer took 2 more than the standing order. Bill the actual 6 on that day. If the extra jars were at a different price, note that on the delivery so the price on the invoice can be explained.
• Skipped. The customer was away or the stop was missed. Do not bill it. Record the reason. If empties were collected at a skipped stop, record them anyway, since they affect your jar count.

Tell customers the rule in plain words: “We bill what we delivered, on the days we delivered it.”

Apply part payments oldest first

Customers often pay an amount that does not match any one bill. The cleanest rule is to apply each payment to the oldest unpaid invoice first, then the next, and so on.

Example (illustrative numbers only, not a result or an average): a customer has an invoice for August of ₹1,800 and one for September of ₹2,200. They pay ₹2,500 on 5 October.

• August invoice: ₹1,800 cleared, status Paid.
• September invoice: ₹700 applied, status Part paid, ₹1,500 still due.

Why oldest first? It keeps your ageing honest. If you applied the money to September, August would look overdue for ever and the customer would argue that they have “already paid something”. A fixed rule also means two staff members reach the same answer.

Say the rule on the invoice or when you speak to the customer. People accept a rule they were told about.

A dispute-handling script

When a customer says “this bill is wrong”, follow the same few steps each time. Stay calm and keep it factual.

1. Listen first. Let them say what they think is wrong. Write it down.
2. Thank them for raising it. “Thank you for telling us. Let us check the dates.”
3. Ask which dates. “Which days do you feel are wrong?” Usually it is two or three.
4. Check the record for those days. Read out what was delivered, what was skipped and what was paid.
5. Correct if you were wrong. “You are right, we billed 2 on the 14th when you were away. We will take it off.”
6. Stand by the record if it is right. “On the 21st the driver delivered 4 jars and recorded 3 empties back. We billed 4.”
7. Offer to settle the rest now. Agree to resolve the disputed lines separately, and ask for payment of the undisputed part.
8. Confirm in writing. Send a short message or a corrected invoice with the outcome.

Never argue about memory. Argue from the dated record, and be quick to concede when it shows you made an error. Conceding one wrong line builds more trust than defending it.

Example

This is an illustrative example with made-up round numbers. It is not a result or an average.

A household has a standing order of 1 jar every day, at ₹40 a jar. In a 30-day month the plan says 30 jars, which is ₹1,200.

• They were away for 4 days. Those 4 stops were skipped with a reason, so 26 days were delivered.
• On 3 days they took 1 extra jar each, so 3 extra jars were delivered.
• Total delivered is 26 + 3 = 29 jars.
• Invoice is 29 × ₹40 = ₹1,160.

If the invoice had been built from the plan, it would say ₹1,200, ₹40 too much, and the customer would be right to dispute it. The reconciled day record gives the lower and correct number, and the delivery lines let the customer check it.

Month-end checklist

Before any invoice goes out, check these.

• Every day of the month is closed and locked, for every route.
• Skipped stops have reasons. Extras are recorded as extras.
• Price changes during the month are noted against the deliveries.
• Every payment received is recorded with date and method.
• Part payments are applied oldest first.
• Customers with zero deliveries are not invoiced.
• You have a list of customers likely to dispute, based on last month, and you have looked at their lines in advance.
• Invoice numbers or dates are in order, with no gaps.
• You know who will answer disputes and by when.

After sending, set a day, a week later, to check unpaid invoices and chase the oldest first. See how to stop credit leakage for the weekly routine.

How Pyaau helps

Pyaau is an Android app for jar delivery businesses. For billing, it does the following today:

• Invoices are raised from reconciled days.
• Customers who pay monthly are invoiced. Customers set to pay daily are not.
• An invoice is a summary: one row per product and rate, then a day-by-day grid of jars delivered for each month. The per-delivery layout is still available from the invoice menu.
• You can keep a vendor code on a customer. It is copied onto each new invoice and printed on its PDF, which helps with corporate customers.
• You can change prices on an issued invoice. Type a new rate for a product and every delivery at the old rate changes. The total and status are worked out again, the customer’s balance follows, and the invoice keeps a record of each change: who, when, why, and the totals before and after.
• An invoice can be shared from the phone as a PDF through WhatsApp or any other app. Coming next: WhatsApp billing.
• Payments are applied to the oldest invoice first, and each invoice shows Paid, Part paid or Unpaid.
• Each customer has a ledger that lists invoices and payments together, separates invoiced-unpaid from delivered-not-yet-invoiced, and shows “Owes you” or “Credit”.
• A dues report shows ageing buckets and the customers owing the most.
• A short-and-extra report shows the stops behind any difference from plan.

Payments are recorded in the app against the customer’s ledger. The method above works on paper or in a spreadsheet as well, with more checking by hand.