[{"data":1,"prerenderedAt":329},["ShallowReactive",2],{"navigation":3,"\u002Fdocs\u002Fpayments-guide":40,"\u002Fdocs\u002Fpayments-guide-surround":324},[4,8,12,16,20,24,28,32,36],{"title":5,"path":6,"stem":7},"Getting started","\u002Fdocs\u002Fgetting-started","1.docs\u002F1.getting-started",{"title":9,"path":10,"stem":11},"Core concepts","\u002Fdocs\u002Fcore-concepts","1.docs\u002F2.core-concepts",{"title":13,"path":14,"stem":15},"Sales & CRM guide","\u002Fdocs\u002Fsales-crm-guide","1.docs\u002F3.sales-crm-guide",{"title":17,"path":18,"stem":19},"Construction progress guide","\u002Fdocs\u002Fconstruction-progress-guide","1.docs\u002F4.construction-progress-guide",{"title":21,"path":22,"stem":23},"Payments & collections guide","\u002Fdocs\u002Fpayments-guide","1.docs\u002F5.payments-guide",{"title":25,"path":26,"stem":27},"RERA compliance guide","\u002Fdocs\u002Frera-compliance-guide","1.docs\u002F6.rera-compliance-guide",{"title":29,"path":30,"stem":31},"Exports & audit trail","\u002Fdocs\u002Freports-and-exports","1.docs\u002F7.reports-and-exports",{"title":33,"path":34,"stem":35},"Roles & permissions","\u002Fdocs\u002Froles-permissions","1.docs\u002F8.roles-permissions",{"title":37,"path":38,"stem":39},"Frequently asked questions","\u002Fdocs\u002Ffaq","1.docs\u002F9.faq",{"id":41,"title":21,"body":42,"description":318,"extension":319,"meta":320,"navigation":321,"path":22,"seo":322,"stem":23,"__hash__":323},"docs\u002F1.docs\u002F5.payments-guide.md",{"type":43,"value":44,"toc":309},"minimark",[45,50,59,62,125,128,142,146,158,176,180,187,195,199,204,222,225,229,232,250,257,261,267,296,299],[46,47,49],"h2",{"id":48},"payment-plan-templates","Payment plan templates",[51,52,53,54,58],"p",{},"Before you can collect against a booking, your organisation needs at least one ",[55,56,57],"strong",{},"payment plan\ntemplate",". These live under Settings → Payment Plans and are shared across projects.",[51,60,61],{},"A template has:",[63,64,65,73,122],"ul",{},[66,67,68,69,72],"li",{},"A ",[55,70,71],{},"plan type",": Construction Linked (CLP), Down Payment (DPP), Time Linked (TLP), Flexi, or\nCustom. This is mainly for your own reference and reporting.",[66,74,75,76,79,80,83,84],{},"One or more ",[55,77,78],{},"milestones",", each with a name, a percentage of the total price, and a ",[55,81,82],{},"trigger","\nthat decides when it becomes due:\n",[63,85,86,92,98,104,110,116],{},[66,87,88,91],{},[55,89,90],{},"Booking",", due as soon as the deal is booked.",[66,93,94,97],{},[55,95,96],{},"Agreement",", due on signing the agreement for sale.",[66,99,100,103],{},[55,101,102],{},"Construction progress",", due when a linked construction stage such as plinth or slab-casting\nis reported. This is what makes a plan \"construction-linked.\"",[66,105,106,109],{},[55,107,108],{},"Time-based",", due a fixed number of days after a reference date.",[66,111,112,115],{},[55,113,114],{},"Possession",", due at handover.",[66,117,118,121],{},[55,119,120],{},"Manual",", triggered by a team member when it's ready to be raised.",[66,123,124],{},"Milestone percentages must add up to 100%, and each milestone needs a unique code. The template\nform validates both before you can save.",[51,126,127],{},"You can mark a template as the default for a project type (Residential, Commercial,\nInfrastructure, Mixed Use), so it's pre-selected when someone generates a schedule for a matching\nproject.",[129,130,131],"blockquote",{},[51,132,133,136,137,141],{},[55,134,135],{},"Note:"," Payment plan templates are admin-configurable under Settings. If you don't see this\noption, your role may not include template management. See ",[138,139,33],"a",{"href":140},".\u002Froles-permissions",".",[46,143,145],{"id":144},"generating-a-payment-schedule-for-a-booked-unit","Generating a payment schedule for a booked unit",[51,147,148,149,153,154,157],{},"Once a ",[138,150,152],{"href":151},".\u002Fsales-crm-guide","deal is booked"," against a unit, open the deal's ",[55,155,156],{},"Payments"," tab to turn\na template into an actual schedule for that buyer.",[159,160,161,167,170,173],"ol",{},[66,162,163,164,141],{},"From the deal's Payments tab, choose ",[55,165,166],{},"Generate schedule",[66,168,169],{},"Pick a payment plan template. The picker shows how many milestones each template has.",[66,171,172],{},"Review the tax and fees breakdown (GST and any applicable statutory dues) that will apply on top\nof the base price, and confirm the GST collection approach for this deal.",[66,174,175],{},"Confirm to generate the schedule. Each milestone from the template becomes a line item on this\ndeal, with its own amount, trigger, and due date once triggered.",[177,178],"screenshot",{"id":179},"payment-plan",[51,181,182,183,186],{},"If a schedule already exists, you can ",[55,184,185],{},"replace"," it with a different template. Existing receipts\nare kept and reallocated automatically to the new milestone structure once you confirm.",[129,188,189],{},[51,190,191,194],{},[55,192,193],{},"Tip:"," Percentages are fixed on the template, but the rupee amount on each milestone is\ncalculated from the deal's actual price, so the same template works across units at different\nprice points.",[46,196,198],{"id":197},"how-due-dates-are-driven-by-construction-milestones","How due dates are driven by construction milestones",[200,201],"illustration",{"alt":202,"src":203},"A completed construction milestone triggers a schedule demand, which is settled by a recorded receipt","\u002Fillustrations\u002Fdocs-payment-flow.svg",[51,205,206,207,209,210,213,214,217,218,221],{},"For milestones with a ",[55,208,102],{}," trigger, the due date isn't set manually. It\nfollows what's actually happening on site. When the linked construction stage is reported (see the\n",[138,211,17],{"href":212},".\u002Fconstruction-progress-guide","), the milestone flips from\n",[55,215,216],{},"pending"," to ",[55,219,220],{},"due",", and a due date is set from that point. This keeps collections tied to real\nprogress instead of a fixed calendar, which is the point of a construction-linked plan.",[51,223,224],{},"Milestones tied to booking, agreement, or possession work the same way. They sit as pending until\ntheir triggering event happens, then become due.",[46,226,228],{"id":227},"recording-receipts","Recording receipts",[51,230,231],{},"When money comes in against a due milestone, record it as a receipt from the deal's Payments tab:",[159,233,234,241,244,247],{},[66,235,236,237,240],{},"Choose ",[55,238,239],{},"Record payment",". The amount defaults to what's currently outstanding, with quick-fill\nbuttons for 25%, 50%, 75%, or the full outstanding amount.",[66,242,243],{},"Select how it was received (cash, bank transfer, cheque, online payment, or TDS) and fill in\nthe reference number, bank name, or cheque number as relevant.",[66,245,246],{},"Optionally attach a proof of payment (bank slip, screenshot, or similar) and add a note.",[66,248,249],{},"Save. The receipt gets its own receipt number and appears on the deal's payment history.",[51,251,252,253,256],{},"A recorded receipt can be edited later, and its status can be changed (to refunded, partially\nrefunded, marked in error, or cancelled) by team members with the right permissions. Separately, a\nreceipt can be marked ",[55,254,255],{},"verified",". Editing a receipt that's already verified asks for a reason,\nwhich is kept on the deal's activity timeline for an audit trail, and a verified receipt can no\nlonger be cancelled or deleted.",[46,258,260],{"id":259},"tracking-collected-vs-due","Tracking collected vs due",[51,262,263,264,266],{},"The ",[55,265,156],{}," section (available at organisation, project, and customer level) gives you a\nrunning view of collections:",[63,268,269,272,290],{},[66,270,271],{},"A summary of total demand, amount collected, and outstanding amount.",[66,273,68,274,277,278,281,282,285,286,289],{},[55,275,276],{},"Demand"," tab listing schedule items that are due, with filters for ",[55,279,280],{},"Overdue",", ",[55,283,284],{},"Due this\nweek",", and ",[55,287,288],{},"All",". Each row links straight to the deal.",[66,291,68,292,295],{},[55,293,294],{},"Collected"," tab listing recent receipts as they come in.",[51,297,298],{},"On an individual deal, the payment summary shows a progress bar for that unit's collection status\n(on track, overdue, or fully paid) along with counts of paid vs pending milestones, so you can tell\nwhether a buyer is current without opening the schedule.",[129,300,301],{},[51,302,303,305,306,308],{},[55,304,193],{}," Because overdue items are flagged automatically from due dates, your collections team\ncan work the ",[55,307,280],{}," filter directly instead of chasing every deal manually.",{"title":310,"searchDepth":311,"depth":311,"links":312},"",2,[313,314,315,316,317],{"id":48,"depth":311,"text":49},{"id":144,"depth":311,"text":145},{"id":197,"depth":311,"text":198},{"id":227,"depth":311,"text":228},{"id":259,"depth":311,"text":260},"Set up payment plans, generate a collection schedule when a unit is booked, and track what's been received against what's due.","md",{},true,{"title":21,"description":318},"R8sviwsKsxu0ZwZapDPmNduVejrIqVYrQS1ANQAH7hI",[325,327],{"title":17,"path":18,"stem":19,"description":326,"children":-1},"Track real construction work, from setting up activities to seeing roll-up percentages at every level of the Project → Phase → Building → Unit hierarchy.",{"title":25,"path":26,"stem":27,"description":328,"children":-1},"Set up your organization's RERA categories and scope weights, and see how the Project → Phase → Building → Unit structure keeps your progress data aligned with how RERA registration actually works.",1789206849162]