Termsheet & schedule

The termsheet is the buyer's copy of the deal: the charges that make up the agreed price and the installments in which they fall due. This tab shows each installment with its GST, the TDS the buyer deducts under section 194-IA, and what is payable to the developer, and lets you take the termsheet from draft to signed, move an installment's date, or rebuild the schedule from a new payment plan.

Where to find it

Open a booking and choose the Termsheet & schedule tab (the third tab), or click Schedule on the Termsheet card of the Booking overview. Anyone who can view the booking (the View permission on Bookings) can see it.

Before you start

The termsheet is created with the booking, from the approved estimate and its finalized payment plan. If a booking somehow has none, the tab reads "No termsheet" / "This booking has no termsheet; it is created with the booking."

What you see

Termsheet card

The status badge, the line "The agreed charges and the payment schedule for <booking no>." and the action buttons (see below). Then:

• Agreed: the booking's agreed total.
• Scheduled: the total of all schedule rows.
• Paid: money placed on the schedule's installments so far.
• Issued and Signed: the dates, once set.
• Offered carpet area (Mofa): the unit's carpet area as recorded at booking, in sqft.
• Payment plan: "v<n> · <summary>" of the payment plan version the schedule was built from.

Payment schedule card

The subtitle explains the columns: "Each installment across every charge: Total amount (excluding GST), GST, the TDS the buyer deducts under 194-IA and pays to Income Tax, and what is payable to the developer." When no TDS applies it adds "No TDS applies to this deal." If there are no rows the card reads "No installments scheduled."

The installments table:

Column	What it shows
#	The installment number, in due order.
Due	The due date; or "On <stage>" with "milestone achieved" / "awaiting milestone" for a construction-linked installment; or "At possession" with "at possession" / "date to be fixed on the project".
Total amount	The charges in the installment, excluding GST.
GST	The GST on those charges.
TDS	"−₹…" with the rate underneath, or "—" when none applies.
Payable to developer	Total amount + GST − TDS: what the buyer actually pays you.
Status	Pending, Paid, Partially Paid, Waived or Cancelled, plus a Manual badge on installments whose date was set by hand.
Paid	Money placed on the installment, or "—".
Demand	The demand that bills it (a link, with the View permission on Demands) or "draft", with the demand's status underneath.
(pencil)	"Edit installment <n>", on Pending installments only, for users who can edit.

Installments from the payment plan come first. Charges the pricing plan collects at possession, outside the plan, sit under a divider "At the time of possession"; that section is hidden when the plan's show-possession switch is off. A Total row closes the table.

An installment groups every charge row that falls due together (same date, same construction stage, or at possession). Its status is Cancelled when every row is cancelled, Paid when every row is paid, waived or cancelled, Partially Paid when any money sits on it, otherwise Pending.

What you can do

Every action here needs the Edit permission on Bookings and an Active booking. In the default roles that is the Administrator, the Sales Manager and Legal & Documentation. Without the permission, or on a cancelled booking, no buttons or pencils are shown.

Issue

Shown on a Draft termsheet. Issues it with today's date; no letter is generated. A toast reads "Termsheet issued." A workflow rule can email the termsheet at this point ("Buyer term sheet issued: email it (system)"), but it ships switched off.

Mark accepted

Shown on an Issued termsheet. Records that the buyer accepted it. A toast reads "Termsheet marked accepted."

Mark signed

Shown on an Issued or Accepted termsheet. Opens "Mark termsheet signed" with a Signed on date ("Leave empty for today."); confirm with Mark signed. A toast reads "Termsheet marked signed."

Reopen

Shown on an Issued or Accepted termsheet. Asks "Reopen termsheet?" with "The termsheet goes back to Draft and its issued date is cleared, so the schedule can be changed and issued again." Confirm with Reopen. A toast reads "Termsheet reopened as Draft."

A signed termsheet can't be reopened, and none of the four status actions can run out of order; the app answers "Cannot issue a <status> termsheet" (or "Cannot accept…", "Cannot sign…", "Cannot reopen…") in an alert on the card if the screen was stale.

Regenerate schedule

Shown in every status except Cancelled. Opens "Regenerate payment schedule":

• A warning when the termsheet is past Draft: "This termsheet is <status>. Regenerating changes the schedule the buyer has already seen."
• An info line: "<n> paid, partially paid, waived or hand-edited rows are kept; only the open remainder is rebuilt from the plan below." (or "No rows are locked yet; the whole schedule is rebuilt from the plan below.") followed by "The plan is saved as version <n> on estimate v<n>."
• The payment plan editor, prefilled with the booking's current plan.
• "Preview (full line amounts, before locked rows are subtracted)": the schedule the server will write, refreshed as you edit.

Confirm with Regenerate. A toast reads "Schedule regenerated." The plan is saved as the next finalized payment plan version on the booked estimate, the booking points at it, and the open part of the schedule is rebuilt: every charge row that is not Pending, and every hand-edited row, stays as it is; the fresh rows are scaled to the open remainder of each charge.

The plan editor's checks include: "Add at least one row", "Must be above 0", "Enter the due date", "Enter the days after booking", "Choose a milestone", "The rows add up to <n>%, not 100%", "Choose a calendar cadence", "At least 1 installment", "A one-time cadence allows exactly 1 installment", "Enter the first installment date", "Add at least one milestone", "This milestone is listed twice", "Down payment plus milestone percents add up to <n>%, not 100%", "This charge is already on another schedule" and "Choose at least one charge". If a Draft payment plan is already sitting on the estimate the app refuses with "A Draft estimate already exists for this opportunity. Edit that draft instead of creating another."; deal with that draft plan on the estimate first.

Edit installment

The pencil on a Pending installment opens "Installment <n>":

• When the installment waits on a construction stage: "This installment waits on <stage>; a date here overrides that for every charge row."
• Due date.
• Note (placeholder "Optional; written on every charge row"; up to 255 characters).
• "Amounts per charge stay as scheduled; change those in the charge-wise breakdown."

Confirm with Save. A toast reads "Installment <n> updated." Every pending charge row in the installment takes the new date and note and is marked Manual, which keeps it safe from a later regenerate. If the installment has no pending rows left the app answers "Installment <n> has no Pending rows left to edit".

Statuses

• Draft → Issued (Issue) → Accepted (Mark accepted) → Signed (Mark signed, also straight from Issued).
• Issued or Accepted → Draft (Reopen).
• Any status → Cancelled when the booking is cancelled. A cancelled booking termsheet can't be revived.

Installment statuses: Pending, Partially Paid, Paid, Waived, Cancelled.

Things to know

• TDS is worked out per installment from your organization's 194-IA rule in force on the due date (Settings › Organization › TDS on sales (section 194-IA)). It applies only when the deal's consideration excluding GST reaches the rule's threshold (the rule seeded by default is 1% from ₹50,00,000). Example: on an ₹80,00,000 deal, an installment of ₹8,00,000 with ₹40,000 GST carries ₹8,000 TDS and ₹8,32,000 payable to the developer. A demand recomputes TDS by the rule on the demand date, so the two can differ if the rule changed in between.
• "Paid" on this tab moves only by appropriation. A receipt settles a demand as a whole; an accountant then places that money on the demand's charge lines by hand, and only then does an installment's Paid figure change. That is why this figure can lag the money actually in the bank, and why it differs from Paid on the overview.
• Regenerate keeps what is settled. Paid, partly paid, waived and hand-edited charge rows are never rebuilt, so a buyer's history stays intact; only the open remainder follows the new plan.
• Construction-linked installments fall due when the stage is achieved on the project's Construction Stages; charges collected at possession are dated by the project's expected possession date.
• The installment number is a position in due order, not a fixed label: re-dating an installment can change the order, and with it the numbers.
• With charges collected at possession, check the result of an edit. The table lists the possession rows last, under their divider, but the edit counts every group of rows in plain date order and treats a possession row on the same date as a plan row as part of that installment. So when the schedule has an "At the time of possession" section, the number you edit may land on a different group than the table shows; look at the dates after saving.
• The edit dialog mentions a "charge-wise breakdown"; there is no such view on this tab. Charge amounts are changed by regenerating the schedule.
• The edit dialog always opens with an empty Note, and saving writes what is in the box, so re-dating an installment replaces any note it already carried. A due date can't be cleared from the dialog: leaving it empty keeps the date the rows already have.
• Regenerating on a signed or issued termsheet is allowed but warned about, because the buyer has already seen the schedule; the termsheet keeps its status.

Related

• Booking overview
• Demands & money
• Cancel booking
• Demand
• Organization
• Construction Stages
• Unit Pricing
• Expected possession date and charges at possession