Find the missing handoff
An installment can be due without appearing in an overdue report. If nobody raised the demand, collections may never have been given a balance to chase. This is a different problem from a buyer paying late.
The operational question is simple: which approved schedules have become billable, and which of those installments have not yet been demanded?
Give each stage a clear owner
The site team records progress and the supporting evidence. The office checks whether that event satisfies the agreed billing condition. Accounts reviews the affected bookings and issues the demands.
Keep exceptional terms visible. Not every buyer has the same approved payment plan, and a stage update should not erase an agreed date, concession or approval requirement.
Run the batch with a review step
- Select the project and completed stage.
- Identify installments due under approved schedules.
- Review taxes, credits, advances and any exceptions.
- Issue the demands and retain the numbered documents.
- Compare eligible installments with issued demands to expose omissions.
Measure two different queues
Due-but-unbilled asks whether the office completed its billing work. Billed-but-unpaid asks whether the buyer has settled a demand. Put both in the collection review, with different owners and next actions.
A single outstanding number can hide the distinction. Reporting by the relevant dates helps the team act on the right queue.
In NirmaanOne
Demand runs connect construction stages to approved installments, with configurable follow-up rules and due-but-unbilled reporting. Bungalow stages are recorded per plot, but automatic stage-driven bungalow demands are on the roadmap. Validate the exact project workflow during your demo.