The short answer: the milkman and the newspaper vendor are, functionally, household staff on a delivery schedule — and the month-end bill dispute ("you missed four days" / "I missed two") has the same cure as a salary dispute: a daily record and one agreed formula. Count the delivered days, multiply by the per-day rate, settle. Two entities that visit your home 25+ times a month deserve better bookkeeping than a guess on the 1st.
The classic month-end standoff
Every household with daily deliveries knows the scene: the milkman says he skipped two days last month, your memory says four, his notebook says one. Nobody is lying — a missed delivery is a non-event, and non-events don't form memories. At ₹60 a day, the difference is ₹120–₹180 every single month, resolved by whoever negotiates harder. The newspaper bill has the same structure with smaller numbers; a tiffin service, water-can delivery, or subziwala on a fixed route has it too.
Treat it like payroll: rate × delivered days
- Agree the per-day rate — either directly ("₹60/day") or as a monthly amount with a base ("₹1,800 for daily delivery" = ₹60/day on a 30-day base).
- Record delivery days, not missed days. Marking what happened is more reliable than remembering what didn't. One tap: delivered, skipped, or partial (half quantity — the "half day" of milk delivery).
- Settle against the record. Delivered days × per-day rate. If you paid anything mid-month, deduct it like an advance.
This is exactly the attendance-based salary formula with a 30-day base — which is why an app built for staff attendance handles deliveries without modification.
Delivery schedules are rarely "every day" — model the real one
| Delivery | Typical schedule | Base / month |
|---|---|---|
| Milk | Daily, sometimes Mon–Sat | 30 (or 26) |
| Newspaper | Daily; some skip one weekday | 30 (or ~26) |
| Water cans | Twice a week or on demand | 8, or count actual |
| Tiffin / dabba | Mon–Fri or Mon–Sat | 22 or 26 |
| Society services (ironing pickup etc.) | Fixed dates, e.g. 1st & 15th | Number of dates |
The same scheduling logic as part-time house help applies: name the days, and the month's expected count computes itself.
Milk delivery is a first-class role in StaffAround
This isn't a workaround use case: StaffAround ships with Milk delivery and Newspaper delivery as built-in staff roles, alongside custom roles for anything else on a route (water, tiffin, ironing). Set the monthly amount and the real schedule — daily, Mon–Sat, twice a week, or fixed dates including the last day of the month — and mark deliveries with the same one-tap Present / Absent / Half Day you use for staff. At month end you get the exact payable amount computed from the record, mid-month payments tracked as advances, and a WhatsApp summary you can send with the payment so both sides close the month on the same number. It all works offline, and the free plan covers 2 entries — enough for the milkman and the paperwala to stop being a monthly negotiation.
The payoff is bigger than the rupees
₹150 a month of over- or under-payment is real but small. The actual win is removing a recurring, slightly adversarial conversation from your month — and being the one customer on the route whose accounts are never in doubt. Vendors notice; disputed households get rounded against, documented households get rounded toward. It's the same trust dividend that keeps good house help for years, applied to the doorstep economy.