Payments & collections guide

Payment plan templates

Before you can collect against a booking, your organisation needs at least one payment plan template. These live under Settings → Payment Plans and are shared across projects.

A template has:

• A plan type: Construction Linked (CLP), Down Payment (DPP), Time Linked (TLP), Flexi, or Custom. This is mainly for your own reference and reporting.
• One or more milestones, each with a name, a percentage of the total price, and a trigger that decides when it becomes due:
  • Booking, due as soon as the deal is booked.
  • Agreement, due on signing the agreement for sale.
  • Construction progress, due when a linked construction stage such as plinth or slab-casting is reported. This is what makes a plan "construction-linked."
  • Time-based, due a fixed number of days after a reference date.
  • Possession, due at handover.
  • Manual, triggered by a team member when it's ready to be raised.
• Milestone percentages must add up to 100%, and each milestone needs a unique code. The template form validates both before you can save.

You can set one template per plan type as the Default. When someone generates a schedule, the default is picked for them unless the deal already has a plan.

Note: Payment plan templates are admin-configurable under Settings. If you don't see this option, your role may not include template management. See Roles & permissions.

Generating a payment schedule for a booked unit

Once a deal is booked against a unit, open the deal's Payments tab to turn a template into an actual schedule for that buyer.

1. From the deal's Payments tab, choose Generate schedule.
2. Pick a payment plan template. The picker shows how many milestones each template has.
3. Review the tax and fees breakdown (GST and any applicable statutory dues) that will apply on top of the base price, and choose how GST is collected: One-time (a single GST payment) or Split (GST added to each instalment). You can change this later from the deal's tax settings.
4. Confirm to generate the schedule. Each milestone from the template becomes a line item on this deal, with its own amount, trigger, and due date once triggered.

If a schedule already exists, you can replace it with a different template. Existing receipts are kept and reallocated automatically to the new milestone structure once you confirm.

Tip: Percentages are fixed on the template, but the rupee amount on each milestone is calculated from the deal's actual price, so the same template works across units at different price points.

Money received before a schedule exists

If a buyer pays before the deal has a schedule (or an import brings in an amount already received), Construvex holds it as an advance. The deal's Payments tab says so. When you generate the schedule, the advance is applied to its milestones.

When GST applies to a sale

Construvex decides once, at booking, whether a sale carries GST. It compares the unit's OC date (the date its occupancy certificate was received) with the booking date, or with the first payment if that came earlier:

• On or before the OC date: the sale is taxable.
• After the OC date: the sale is GST-free.

The decision is kept for the whole contract. Entering a unit's OC date later does not change deals already booked. On a GST-free deal, a payment dated on or before the OC date is refused, because it would make the whole sale taxable. The deal's tax card shows the basis it used.

Note: This describes how the software applies the dates you enter. Confirm the tax position for your project with your CA.

How due dates are driven by construction milestones

For milestones with a Construction progress trigger, the due date isn't set manually. It follows what's actually happening on site. When the linked construction stage is reported (see the Construction progress guide), the milestone flips from pending to due, and a due date is set from that point. This keeps collections tied to real progress instead of a fixed calendar, which is the point of a construction-linked plan.

Milestones tied to booking, agreement, or possession work the same way. They sit as pending until their triggering event happens, then become due.

Recording receipts

When money comes in against a due milestone, record it as a receipt from the deal's Payments tab:

1. Choose Record payment. The amount defaults to what's currently outstanding, with quick-fill buttons for 25%, 50%, 75%, or the full outstanding amount.
2. Select how it was received (cash, bank transfer, cheque, online payment, or TDS) and fill in the reference number, bank name, or cheque number as relevant.
3. Optionally attach a proof of payment (bank slip, screenshot, or similar) and add a note.
4. Save. The receipt gets its own receipt number and appears on the deal's payment history.

A recorded receipt can be edited later, and its status can be changed (to refunded, partially refunded, marked in error, or cancelled) by team members with the right permissions.

Tracking collected vs due

The Payments section (available at organisation, project, and customer level) gives you a running view of collections:

• A summary of total demand, amount collected, and outstanding amount.
• A Demand tab listing schedule items that are due, with filters for Overdue, Due this week, and All. Each row links straight to the deal.
• A Collected tab listing recent receipts as they come in.

On an individual deal, the payment summary shows a progress bar for that unit's collection status (on track, overdue, or fully paid) along with counts of paid vs pending milestones, so you can tell whether a buyer is current without opening the schedule.

Tip: Because overdue items are flagged automatically from due dates, your collections team can work the Overdue filter directly instead of chasing every deal manually.