LAND MANAGEMENT
The Land Management module provides one connected workflow for managing land inventory, publishing parcels, receiving buyer applications, approving transactions, collecting payments and completing sales. It is designed for companies that manage individual plots, estates, large acreage, subdivisions or mixed land portfolios.
|
LEASEORA LAND MANAGEMENT Detailed User and Technical Operations Guide Create Parcels • Subdivide • Publish • Capture Applications • Structure Payments • Collect Instalments • Generate Documents • Complete Sales |
For real estate companies, land developers, sales teams, finance teams, legal teams and customer-support teams
Version 1.0 | July 2026
|
|
Purpose of this guide This guide explains how a real estate company uses Leaseora's Land Management module from parcel creation and publication through buyer applications, payment plans, multi-channel payments, legal documents, reporting and final sale completion. It also provides a technical reference based on the models, controllers, services and notifications supplied for the module. |
The Land Management module provides one connected workflow for managing land inventory, publishing parcels, receiving buyer applications, approving transactions, collecting payments and completing sales. It is designed for companies that manage individual plots, estates, large acreage, subdivisions or mixed land portfolios.
|
Item |
Description |
|
Primary users |
Corporate Real Estate Companys, land developers, real estate companies, sales teams, finance teams, legal teams, operations teams and executives. |
|
Client users |
Individuals or organisations browsing, applying for, paying for and tracking land purchases or lease applications. |
|
Core scope |
Parcel creation, images, subdivision, publication, enquiries, applications, approvals, sales, payment plans, instalments, payouts, documents, completion and reporting. |
|
Terminology |
This guide uses Client or Buyer. Some platform areas or technical class names may still use Tenant. |
|
Operational boundary |
Leaseora supports the digital workflow but does not replace title verification, survey validation, legal due diligence, regulatory approvals, tax advice or physical land handover. |
|
|
Important legal and operational principle Changing a parcel or sale status in Leaseora records the company's operational decision. Legal ownership transfer remains subject to the signed agreement, applicable law, required payments, title documentation, registration and the company's approved handover process. |
What the module connects
· Land inventory - parcel identity, location, zoning, size, price, images and status.
· Subdivision - creation of separately managed child parcels from a larger parcel.
· Public discovery - published parcels, filters, statistics and client currency display.
· Applications - buyer offer, application type, payment preference, documents and status.
· Sales - buyer, Real Estate Company, sale price, sale type and lifecycle.
· Payment plans - deposit, balance, interest, frequency, duration and instalments.
· Payments - wallet, payment gateways and bank-transfer receipt verification.
· Payouts - Real Estate Company payment method resolution, recording and payout execution.
· Documents - agreements, payment schedules and individual receipts.
· Reporting - revenue, collection performance, overdue payments and exports.
2 Module Overview and Recommended Navigation
Figure 1. End-to-end Land Management lifecycle
|
Menu area |
Primary purpose |
|
Land Management Dashboard |
Portfolio summary, parcel status, applications, sales and payment indicators. |
|
All Parcels |
View and filter all owned, for-sale, pending, active and sold parcels. |
|
Add Parcel |
Create a new parcel with location, zoning, size, price and media. |
|
Parcel Detail |
Review parcel information, child parcels, applications, sale and history. |
|
Applications |
Review, approve or reject client applications. |
|
Sales Management |
View active, completed and cancelled LandSale records. |
|
Payment Plans |
Review deposits, balances, instalments, due dates and collection status. |
|
Bank Transfer Verification |
Review uploaded transfer receipts before confirming payment. |
|
Documents |
Generate or download sale agreements, schedules and receipts. |
|
Reports and Analytics |
Revenue, collections, overdue instalments and export. |
|
Client App / Portal |
Browse, contact owner, apply, pay and download documents. |
|
|
Configuration note Menu labels and available actions may vary slightly according to account permissions or future product updates. The core operating responsibilities described in this guide remain the same. |
Company information and controls to prepare
|
☐ |
Approved company profile and authorised staff accounts. |
|
☐ |
Land title, survey, zoning and due-diligence information. |
|
☐ |
Parcel location, size, price, currency and approved media. |
|
☐ |
Subdivision plan where a large parcel will be split. |
|
☐ |
Approved outright and instalment sale policies. |
|
☐ |
Deposit, interest, frequency, duration and late-payment rules. |
|
☐ |
Company bank accounts and accepted payment gateways. |
|
☐ |
Real Estate Company payout method and wallet configuration. |
|
☐ |
Standard sale agreement, schedule and receipt formats. |
|
☐ |
Application approval, rejection, cancellation and refund authority. |
Recommended staff responsibilities
|
Role |
Primary responsibility |
|
Land Administrator |
Create parcels, manage images, subdivision, publication and parcel status. |
|
Sales Officer |
Respond to enquiries, review applications and communicate with clients. |
|
Finance Officer |
Configure payment methods, verify payments, reconcile instalments and monitor payouts. |
|
Legal Officer |
Review due diligence and sale agreements before issue. |
|
Director / Approver |
Approve applications, direct sales, exceptions, cancellations and completion. |
|
Customer Support |
Assist clients with applications, payments, documents and status enquiries. |
|
Reporting Officer |
Review revenue, collections, overdue reports and exports. |
|
|
Segregate duties Where possible, the person who creates a parcel or application should not be the only person who approves payment exceptions, cancels a sale or marks a sale completed. |
4 Phase 1 - Create and Configure a Land Parcel
Steps 1 to 4: create inventory, subdivide where needed, publish or create a direct sale.
|
STEP |
Create a Land Parcel Primary user: Land Administrator / authorised Real Estate Company user |
Navigate to Land Management -> Add Parcel. Enter the approved parcel information and save the record with status Owned. At this stage, the parcel is part of the company's inventory but is not yet available to public buyers.
|
Field |
Purpose |
Good practice |
|
Title |
Public or internal name of the parcel. |
Use an approved and recognisable name. |
|
Description |
Land characteristics, access, intended use and relevant information. |
Avoid unsupported claims. |
|
Address / city / state / country |
Location and regional context. |
Confirm the exact area and country. |
|
Size |
Area in acreage, square metres or configured unit. |
Use an approved survey measurement. |
|
Zoning type |
Residential, commercial, agricultural, industrial or mixed-use. |
Confirm legal and planning status. |
|
Asking price |
Advertised parcel price. |
Use management-approved pricing. |
|
Currency code |
Currency in which the parcel is listed. |
Confirm before publication. |
|
Status |
Owned initially. |
Change to For Sale only after review. |
|
Feature image and gallery |
Approved parcel, layout, access or estate images. |
Use accurate, current media. |
Parcel creation checklist
|
☐ |
Ownership and authority to market the parcel have been verified internally. |
|
☐ |
Surveyed size and location are accurate. |
|
☐ |
Zoning type is supported by available information. |
|
☐ |
Asking price and currency are approved. |
|
☐ |
Images do not misrepresent the parcel. |
|
☐ |
Public description does not promise approvals or infrastructure not yet secured. |
|
☐ |
Status remains Owned until publication review is complete. |
|
STEP |
Subdivide a Parcel (Optional) Primary user: Land Administrator / survey and legal review |
Use the subdivision action when a large parcel will be split into smaller saleable plots or sub-parcels. Each child parcel becomes its own LandParcel record and can have an independent size, price, status and sales history.
Subdivision controls
· Confirm the parent parcel and approved subdivision plan.
· Create a unique title or parcel reference for every child parcel.
· Record the correct size and location for each child parcel.
· Assign an individual asking price and status.
· Upload parcel-specific images or layout references where available.
· Ensure the total child areas reconcile with the approved subdivision basis.
· Keep the parent-child relationship for audit and portfolio reporting.
|
|
Subdivision is not a survey approval The Leaseora subdivision function creates separate management records. It does not itself create, approve or register a legal subdivision. |
|
STEP |
Publish the Parcel for Sale Primary user: Authorised Real Estate Company user |
After internal review, publish the parcel. Its status changes from Owned to For Sale and it becomes visible through the public web, mobile and API browsing experiences.
Publication readiness checklist
|
☐ |
Parcel details, size, location and zoning are correct. |
|
☐ |
Price and currency are approved. |
|
☐ |
Feature image and gallery have been reviewed. |
|
☐ |
Client-facing description is accurate. |
|
☐ |
Company contact information is current. |
|
☐ |
Accepted payment options and sales terms are ready. |
|
☐ |
Staff responsible for enquiries and applications are assigned. |
|
STEP |
Create a Manual Sale for a Known Buyer Primary user: Director / authorised sales administrator |
The manual-sale option allows the company to bypass the public application workflow for a known buyer. Enter the buyer, sale price, currency, sale type and payment-plan information directly.
|
|
Manual sales need the same controls A direct sale should still follow the company's identity, due-diligence, pricing, legal, payment and approval process. The manual route changes the system workflow, not the company's obligations. |
5 Phase 2 - Client Discovers and Applies for Land
Steps 5 to 9: browse, review, contact the owner, apply and track status.
|
STEP |
Browse Published Parcels Primary user: Client / buyer |
The client opens the land browsing page in the Leaseora web or mobile experience. Only parcels with status For Sale should appear.
|
Filter |
How it helps |
|
Country / state / city |
Narrows parcels by geography. |
|
Zoning type |
Finds residential, commercial, agricultural, industrial or mixed-use land. |
|
Minimum / maximum price |
Matches the client's budget. |
|
Size |
Finds parcels within the required area range. |
|
Currency display |
Shows converted values using the client's preferred currency where supported. |
LandParcelApiController can provide countries, states, zoning types and aggregate statistics to support the browsing interface.
|
|
Converted prices are indicative The parcel remains priced in its listing currency. Currency conversion helps the client understand the approximate value, while the sale record and payment terms should clearly state the contractual currency. |
|
STEP |
View Parcel Details Primary user: Client / buyer |
The parcel detail page displays the approved parcel information, gallery, asking price, zoning, location and owner information. The system can also check whether the client already has an active application for the parcel.
|
Detail area |
What the client reviews |
|
Parcel identity |
Title, reference and description. |
|
Location |
Country, state, city and address information. |
|
Land characteristics |
Size, zoning and other approved details. |
|
Price |
Asking price in listing currency and converted client currency where supported. |
|
Media |
Feature image and gallery. |
|
Owner information |
Verified company or Real Estate Company contact information. |
|
Application status |
Whether the client already has an active application. |
|
STEP |
Contact the Owner Primary user: Client / buyer |
The client can send an enquiry before submitting a formal application. The message triggers LandParcelContactNotification so the company can respond.
Recommended response practice
· Respond from the company account rather than a private personal account where possible.
· Refer to the parcel title or reference.
· Answer verified questions only.
· Explain that an enquiry does not reserve the parcel.
· Direct serious clients to the formal application process.
|
STEP |
Submit a Purchase or Lease Application Primary user: Client / buyer |
The client submits a formal application stating the transaction type, proposed price and preferred payment method. The system creates a LandApplication with status Pending and a unique application code.
|
Application field |
Purpose |
|
Application type |
Purchase or lease. |
|
Offered price |
The client's proposed amount. |
|
Currency |
Currency code and symbol used for the offer. |
|
Payment preference |
Outright or instalment. |
|
Preferred duration |
Requested number of months for instalment payment. |
|
Message |
Optional note or proposal to the Real Estate Company. |
|
Attachment |
Optional supporting document. |
|
|
Application is not approval A Pending application records the client's formal interest. It does not reserve the parcel or create a sale until the Real Estate Company approves it and the parcel status changes accordingly. |
|
STEP |
View My Applications Primary user: Client / buyer |
The client can view all submitted applications and their current status through web, mobile or API. Application statistics can show pending, approved and rejected counts.
6 Phase 3 - Real Estate Company Reviews and Responds to Applications
|
STEP |
View All Applications Primary user: Sales team / Real Estate Company |
Open the applications dashboard to review LandApplication records across all parcels. Filter by status, parcel, applicant, email or date range. Offered prices can be displayed in the Real Estate Company's preferred currency through CurrencyConversionService.
|
Dashboard information |
Why it matters |
|
Application code |
Provides a unique reference for communication and audit. |
|
Applicant profile |
Identifies the client and contact details. |
|
Parcel |
Confirms which land record is being requested. |
|
Application type |
Purchase or lease. |
|
Offered price |
Shows client proposal in original and converted view where supported. |
|
Payment preference |
Outright or instalment. |
|
Status |
Pending, approved or rejected. |
|
Submission date |
Supports prioritisation and service levels. |
|
STEP |
Review Application Detail Primary user: Sales, legal and management |
Open the application to review the full client profile, offered price, message, payment preference and attachments. Confirm the parcel is still available and the application can proceed under company policy.
Application review checklist
|
☐ |
Applicant identity and contact details are complete. |
|
☐ |
Parcel is still available and not already reserved. |
|
☐ |
Application type is supported for the parcel. |
|
☐ |
Offered price and currency are clear. |
|
☐ |
Requested payment duration is acceptable or requires negotiation. |
|
☐ |
Supporting documents have been reviewed. |
|
☐ |
Legal or compliance checks required by the company are complete. |
|
☐ |
Approval authority has been identified. |
|
STEP |
Approve the Application Primary user: Authorised Real Estate Company approver |
When the application is approved, the system records the approval date and approver, creates a LandSale record and changes the parcel status to Pending. The buyer receives LandApplicationApprovedNotification and is prompted to continue with payment.
|
|
Parcel reservation control Approval should prevent the same parcel from being sold to another client through an active transaction. Staff should confirm that the parcel status changes correctly before approving another application. |
|
STEP |
Reject the Application Primary user: Authorised Real Estate Company approver |
If the application will not proceed, record a clear rejection reason and change the application status to Rejected. LandApplicationRejectedNotification informs the client.
Good rejection practice
· Use a factual and professional reason.
· Avoid discriminatory or unsupported explanations.
· Do not expose confidential internal information.
· Confirm the parcel remains available if no other active sale exists.
Figure 2. Parcel, application and sale status relationships
7 Phase 4 - Land Sale and Payment Plan Setup
|
STEP |
Review the LandSale Record Primary user: Sales and finance teams |
Approval creates a LandSale linking the parcel, buyer and Real Estate Company. The sale record contains the agreed price, currency, sale type and status.
|
LandSale field |
Purpose |
|
Land parcel |
Identifies the parcel being sold or leased. |
|
Buyer |
Links the approved client. |
|
Real Estate Company |
Identifies the selling company or owner. |
|
Sale price |
Agreed transaction amount. |
|
Currency |
Contractual sale currency. |
|
Sale type |
Outright or instalment. |
|
Status |
Active, completed or cancelled. |
|
STEP |
Generate the Payment Plan Primary user: Finance / authorised sales administrator |
For an instalment sale, create a LandPaymentPlan containing the total amount, deposit, balance, interest, frequency and duration. The system generates individual LandPaymentInstallment records for each due date.
|
Plan field |
Meaning |
|
Total amount |
Full agreed sale value. |
|
Deposit amount |
Initial payment due. |
|
Balance amount |
Amount remaining after deposit. |
|
Interest rate |
Approved financing rate, if applicable. |
|
Frequency |
Monthly, quarterly or configured schedule. |
|
Duration |
Number of months in the plan. |
|
Total instalments |
Number of payment records. |
|
Instalment amount |
System-calculated where auto-calculate is enabled. |
|
Start / end date |
Payment-plan period. |
|
Plan notes |
Approved conditions or explanations. |
Computed payment information
|
Computed value |
Meaning |
|
Total paid |
Sum of all confirmed paid instalments. |
|
Balance remaining |
Total amount less confirmed payments. |
|
Next due instalment |
Earliest pending instalment by due date. |
|
|
Validate the schedule before use Finance should confirm that the deposit, interest, instalments and dates match the approved agreement. Auto-calculation reduces manual work but does not replace financial review. |
8 Phase 5 - Client Payments and Real Estate Company Payouts
|
STEP |
Client Views the Payment Plan Primary user: Client / buyer |
The client opens the payment-plan page to view the total sale amount, deposit, balance, instalments, due dates and available payment methods. Amounts may be displayed in the client's preferred currency while preserving the sale currency.
|
STEP |
Pay an Instalment Primary user: Client / buyer |
The client chooses one of the supported payment methods. After successful confirmation, the instalment record is marked Paid, the balance is updated and the Real Estate Company payout flow is triggered.
|
Payment method |
Client action |
System / Real Estate Company control |
|
Wallet |
Pays from the Leaseora wallet. |
Currency conversion applies where required; wallet is debited and payout service is triggered. |
|
Payment gateway |
Completes payment through a configured gateway such as Flutterwave, Stripe, Revolut, Paystack or Squad. |
Session and callback are verified before the instalment is treated as paid. |
|
Bank transfer |
Transfers to the approved account and uploads the receipt. |
Authorised staff manually verify the transfer before confirming payment. |
Figure 3. Land payment and Real Estate Company payout flow
Payment processing sequence
1. Client selects an outstanding instalment.
2. System displays amount and supported methods.
3. Currency conversion is applied where necessary.
4. Payment is initiated through wallet, gateway or bank transfer.
5. Successful payment or verified transfer updates the instalment status.
6. Real Estate CompanyPaymentRecorder records the transaction.
7. Real Estate CompanyPayoutService executes the configured payout process.
8. Buyer and Real Estate Company receive the relevant notifications.
9. Payment history and remaining balance are refreshed.
|
|
Uploaded receipt is not proof of settlement A bank-transfer receipt must be checked against the company's bank record before the instalment is marked Paid. |
|
STEP |
Pay Outright Primary user: Client / buyer |
For an Outright sale, the client pays the full sale price in one transaction using wallet, payment gateway or bank transfer. When the payment is successfully confirmed, the LandSale can move to Completed and the parcel can be marked Sold.
|
|
Completion should follow approval Even after full payment, staff should confirm the legal documents, payment reconciliation and handover requirements before final completion. |
9 Phase 6 - Reminders and Overdue Management
|
STEP |
Automated Payment Reminders Primary user: System / finance oversight |
LandPaymentReminderNotification is sent before an instalment due date according to the configured schedule. Reminders should clearly state the parcel, sale reference, amount, due date and approved payment channels.
|
STEP |
Overdue Payment Alerts Primary user: System / finance team |
When an instalment passes its due date without confirmed payment, LandPaymentOverdueNotification alerts the client. The finance team should review the overdue report and follow the company's escalation process.
Recommended overdue workflow
1. Confirm the instalment is truly unpaid and no transfer is awaiting verification.
2. Contact the client using the approved communication channel.
3. Record any payment commitment or dispute.
4. Apply contractual actions only under the approved agreement and policy.
5. Escalate material defaults to authorised management or legal staff.
6. Keep the sale and parcel status accurate.
|
|
Do not automate sensitive enforcement without review Reminders can be automated, but penalties, cancellation, repossession or legal enforcement require authorised human review and must follow the signed agreement and applicable law. |
10 Phase 7 - Agreements, Schedules and Receipts
|
STEP |
Generate and Download the Sale Agreement Primary user: Legal / authorised Real Estate Company and buyer |
LandDocumentService generates the land sale agreement PDF. Both the Real Estate Company and buyer can view or download the document through their respective portals.
Agreement control checklist
|
☐ |
Correct parcel and buyer are linked. |
|
☐ |
Sale price and currency match the approved LandSale. |
|
☐ |
Outright or instalment terms are correct. |
|
☐ |
Payment-plan values match the generated schedule. |
|
☐ |
Required legal clauses have been reviewed. |
|
☐ |
Parties and authorised signatories are correct. |
|
☐ |
Document version and date are clear. |
|
STEP |
Generate the Payment Schedule Primary user: Finance / legal / client |
LandDocumentService generates the full instalment schedule showing the deposit, instalment amounts, due dates and balance progression. Both parties can view and download it.
|
STEP |
Generate Payment Receipts Primary user: Finance / client |
Each confirmed payment can have an individual receipt generated through LandDocumentService. The receipt should identify the parcel, sale, buyer, amount, currency, payment date and transaction reference.
|
|
Documents reflect recorded data A generated PDF is only as accurate as the underlying sale and payment records. Correct the source record through an authorised process rather than editing the PDF manually. |
11 Phase 8 - Sale Completion and Cancellation
|
STEP |
Mark the Sale as Completed Primary user: Authorised Real Estate Company approver |
After the company confirms full payment and completion requirements, change the LandSale status to Completed and the LandParcel status to Sold. LandSaleCompletedNotification informs the buyer.
Completion checklist
|
☐ |
All required payments are confirmed and reconciled. |
|
☐ |
No pending bank-transfer proof remains unverified. |
|
☐ |
Sale agreement and required documents are complete. |
|
☐ |
Outstanding disputes or refunds are resolved. |
|
☐ |
Parcel identity and buyer information are correct. |
|
☐ |
Legal transfer or handover conditions have been satisfied under company policy. |
|
☐ |
Completion has been authorised by the appropriate person. |
|
STEP |
Cancel an Active Sale Primary user: Authorised Real Estate Company approver |
When a sale is cancelled, change the LandSale status to Cancelled. The LandParcel returns to For Sale so it can be offered again, subject to the company's cancellation, refund and legal process.
|
|
Cancellation requires a recorded basis Record the reason, approval, financial treatment and client communication. Do not re-list a parcel while the previous transaction is still legally disputed. |
12 Phase 9 - Real Estate Company Sales Dashboard and Reports
|
STEP |
View All Land Sales Primary user: Real Estate Company / management |
The sales list shows active, completed and cancelled LandSale records with buyer profiles, sale amounts and payment positions. API endpoints can provide the same information to authorised connected experiences.
|
STEP |
Review the Sales Dashboard Primary user: Management / reporting team |
LandSalesReportController provides a portfolio-level view of sales performance.
|
STEP |
Track Revenue Primary user: Finance / management |
Review total revenue collected by parcel and reporting period. Compare expected sale values with confirmed collections.
|
STEP |
Review Payment Collection Primary user: Finance |
Monitor collection rates, on-time payments and late instalments across active sales.
|
STEP |
Review Overdue Payments Primary user: Finance / management |
Use the overdue report to prioritise client follow-up, verify unconfirmed transfers and escalate material defaults.
|
STEP |
Export Sales Data Primary user: Reporting / authorised management |
Export land sales data in the configured CSV or Excel format for management review, reconciliation or approved external reporting.
Figure 4. Land sales reporting and management views
|
Report |
Management question answered |
|
Sales overview |
How many sales are active, completed or cancelled? |
|
Revenue tracking |
How much has been collected by parcel and period? |
|
Payment collection |
What percentage of instalments is paid on time? |
|
Overdue payments |
Which clients and instalments require action? |
|
Parcel inventory |
How many parcels are owned, for sale, pending or sold? |
|
Applications |
How many applications are pending, approved or rejected? |
|
Exports |
Can the data be shared for authorised analysis or reporting? |
13 Phase 10 - Client Purchase Dashboard
|
STEP |
View My Purchases Primary user: Client / buyer |
The client can view all active and completed land purchases through web, mobile or API. Each purchase should show the parcel, sale price, payment plan, paid amount, balance, next due instalment and available documents.
|
Client dashboard item |
What it shows |
|
Purchase status |
Active, completed or cancelled. |
|
Parcel details |
Title, location, size and zoning. |
|
Payment summary |
Total, paid amount and remaining balance. |
|
Next due instalment |
Amount and due date. |
|
Payment history |
Confirmed instalments and transaction references. |
|
Agreement |
View or download the sale agreement. |
|
Payment schedule |
View or download the full schedule. |
|
Receipts |
Download individual payment receipts. |
|
|
Client support When a client reports a difference between their dashboard and their payment record, finance should investigate the underlying transaction before making any manual adjustment. |
14 Currency Conversion and Multi-Currency Controls
The supplied design uses CurrencyExchangeService for client-facing conversion and CurrencyConversionService for Real Estate Company-side application review. The parcel and sale should retain a clear listing or contractual currency while converted values support understanding.
|
Context |
Service |
Control |
|
Parcel browsing |
CurrencyExchangeService |
Shows asking price in the client's preferred currency. |
|
Application review |
CurrencyConversionService |
Displays the offered price in the Real Estate Company's preferred currency. |
|
Payment plan |
CurrencyExchangeService |
Displays schedule values to the client. |
|
Wallet payment |
CurrencyExchangeService |
Converts between wallet and sale currency where necessary. |
|
Reporting |
Configured currency context |
Management should know whether values are original, converted or consolidated. |
|
|
State the contractual currency Converted values can change with exchange rates. Agreements, invoices and payment instructions should clearly state the currency in which the obligation is legally payable. |
15 Payment, Payout and Reconciliation Controls
|
System / service |
Responsibility |
|
Real Estate CompanyPaymentGatewayService |
Creates and verifies gateway payment sessions for land transactions. |
|
Real Estate CompanyPaymentMethodResolver |
Determines the appropriate Real Estate Company payment or payout method. |
|
Real Estate CompanyPaymentRecorder |
Records the land-sale payment transaction. |
|
Real Estate CompanyPayoutService |
Executes the Real Estate Company payout after confirmed payment. |
|
Wallet |
Stores buyer funds for wallet payments and can receive Real Estate Company funds where configured. |
|
Real Estate CompanyPayout |
Tracks payout amount, method, reference and status. |
|
LandPaymentInstallment |
Tracks individual amount, due date and payment status. |
Daily finance controls
|
☐ |
Review new wallet and gateway payments. |
|
☐ |
Verify gateway callbacks against provider records. |
|
☐ |
Review uploaded bank-transfer receipts. |
|
☐ |
Reconcile confirmed payments with bank or gateway settlement. |
|
☐ |
Check Real Estate CompanyPayout status and exceptions. |
|
☐ |
Confirm buyer balances and next due instalments. |
|
☐ |
Investigate duplicate, failed or reversed transactions. |
|
|
Immediate payout is a workflow outcome, not a guarantee The supplied design triggers payout after confirmed payment. Actual settlement timing may depend on gateway processing, bank availability, compliance checks, payout configuration and transaction status. |
16 Notifications Reference
|
Notification |
Recipient |
Trigger |
|
LandApplicationReceivedNotification |
Real Estate Company |
New application submitted |
|
LandApplicationApprovedNotification |
Buyer |
Application approved |
|
LandApplicationRejectedNotification |
Buyer |
Application rejected with reason |
|
LandParcelContactNotification |
Real Estate Company |
Buyer sent an enquiry |
|
LandPaymentReceivedNotification |
Buyer |
Payment confirmed |
|
Real Estate CompanyPaymentReceived |
Real Estate Company |
Buyer payment received |
|
LandPaymentReminderNotification |
Buyer |
Upcoming instalment reminder |
|
LandPaymentOverdueNotification |
Buyer |
Instalment overdue |
|
LandSaleCompletedNotification |
Buyer |
Sale completed |
|
|
Notification count The supplied specification identifies nine targeted notifications for the module. The deployed delivery channels and exact message content should be confirmed during implementation. |
17 Backend Models Reference
|
Model |
Purpose |
|
LandParcel |
Core parcel record: location, size, zoning, price, images and status. |
|
LandApplication |
Buyer application: type, offered price, payment preference, documents and status. |
|
LandSale |
Core transaction: parcel, buyer, Real Estate Company, sale price, sale type and status. |
|
LandPaymentPlan |
Instalment plan: total, deposit, balance, interest, frequency and duration. |
|
LandPaymentInstallment |
Individual due date, amount and payment status. |
|
Wallet |
Buyer wallet for payment and Real Estate Company wallet for configured payout. |
|
Real Estate CompanyPayout |
Tracks each payout associated with a confirmed land payment. |
18 Controllers and Services Reference
|
Controller |
Main purpose |
|
LandManagementController |
Real Estate Company: create parcel, images, subdivision, publish and manual sale. |
|
LandApplicationController |
Real Estate Company: list, view, approve and reject applications with FX display. |
|
LandSalesController |
Real Estate Company: view sales, complete, cancel and access documents. |
|
LandSalesReportController |
Dashboard, revenue, collection, overdue and export. |
|
LandBrowsingController |
Client web: browse, detail, contact owner, apply and view applications. |
|
TenantLandPurchaseController |
Client web: purchases, payment plan, instalment and outright payments, documents. |
|
LandMobileController |
Mobile: browsing, parcel detail, applications, purchases and payments. |
|
LandParcelApiController |
API: parcels, filters and statistics. |
|
LandApplicationApiController |
API: submit, list, view, delete and application statistics. |
|
LandSaleApiController |
API: sales, payment plan and statistics. |
|
LandPaymentApiController |
API: wallet, gateway, callback and receipt upload. |
|
Service |
Purpose |
|
LandDocumentService |
Generates agreement, payment schedule and receipt PDFs. |
|
Real Estate CompanyPaymentGatewayService |
Creates and verifies payment-gateway sessions. |
|
Real Estate CompanyPaymentMethodResolver |
Determines the Real Estate Company payment or payout method. |
|
Real Estate CompanyPaymentRecorder |
Records payment transactions. |
|
Real Estate CompanyPayoutService |
Executes payout after confirmed payment. |
|
CurrencyExchangeService |
Client-facing FX conversion. |
|
CurrencyConversionService |
Real Estate Company-side FX display for applications. |
19 Status and Transition Matrix
|
Record |
Status |
Meaning |
|
LandParcel |
Owned |
Created and held in inventory; not publicly available. |
|
LandParcel |
For Sale |
Published and available to clients. |
|
LandParcel |
Pending |
Approved sale application or transaction in progress. |
|
LandParcel |
Active |
Active sale process where used by the configured workflow. |
|
LandParcel |
Sold |
Sale completed. |
|
LandApplication |
Pending |
Submitted and awaiting decision. |
|
LandApplication |
Approved |
Accepted; LandSale created. |
|
LandApplication |
Rejected |
Will not proceed. |
|
LandSale |
Active |
Current outright or instalment transaction. |
|
LandSale |
Completed |
Transaction completed. |
|
LandSale |
Cancelled |
Transaction cancelled; parcel can return to For Sale. |
|
LandPaymentInstallment |
Pending |
Not yet confirmed paid. |
|
LandPaymentInstallment |
Paid |
Payment successfully confirmed. |
|
LandPaymentInstallment |
Overdue |
Past due without confirmed payment where supported. |
|
|
Confirm exact production enums The status values above are based on the supplied scenario. Exact database enums, automatic transitions and cancellation behaviour should be confirmed in the deployed environment. |
20 Worked Example - Subdivided Estate Sale
|
|
Scenario Horizon Estates owns a 20-acre parcel and subdivides it into 80 independently priced plots. Client Amina Yusuf applies for Plot H-24 using a 12-month instalment plan. |
|
Stage |
What happens |
|
1. Parent parcel |
Horizon Estates creates the 20-acre record with status Owned. |
|
2. Subdivision |
The company creates 80 child LandParcel records with unique plot references. |
|
3. Publication |
Available plots are reviewed and published with status For Sale. |
|
4. Discovery |
Amina filters by location, residential zoning, price and size. |
|
5. Enquiry |
She contacts the owner and receives verified information. |
|
6. Application |
She submits a Purchase application for Plot H-24 with instalment preference. |
|
7. Approval |
The Real Estate Company reviews the application, approves it and the plot changes to Pending. |
|
8. Sale record |
A LandSale is created with the agreed price and Instalment sale type. |
|
9. Payment plan |
Finance creates the deposit and 12-month schedule. |
|
10. Deposit |
Amina pays through a configured gateway and the payment is verified. |
|
11. Payout |
Real Estate CompanyPayoutService processes the configured payout. |
|
12. Instalments |
Amina pays monthly and receives confirmations and receipts. |
|
13. Reminders |
Upcoming reminders are sent; any overdue instalment is flagged. |
|
14. Documents |
Both parties download the agreement and payment schedule. |
|
15. Completion |
After full payment and legal completion, the sale becomes Completed and Plot H-24 becomes Sold. |
21 Recommended Operating Rhythm
|
Frequency / event |
Recommended review |
|
Daily |
Review new enquiries, applications, payments, receipt uploads and payout exceptions. |
|
Weekly |
Review pending applications, parcel status, collection performance and overdue instalments. |
|
Monthly |
Reconcile revenue, payment plans, completed sales, cancellations and inventory. |
|
Before publication |
Validate parcel details, title basis, zoning, size, price, media and staff assignment. |
|
Before approval |
Review applicant, offered price, payment preference, availability and internal approvals. |
|
Before completion |
Confirm full payment, documents, reconciliation and legal handover conditions. |
|
After cancellation |
Record reason, financial treatment, communication and parcel re-listing status. |
22 Implementation and Onboarding Checklist
Data to prepare
|
☐ |
Parcel titles, references and descriptions. |
|
☐ |
Addresses, cities, states and countries. |
|
☐ |
Surveyed sizes and measurement units. |
|
☐ |
Zoning information and permitted-use notes. |
|
☐ |
Approved asking prices and currencies. |
|
☐ |
Feature images, galleries and layout documents. |
|
☐ |
Parent and child parcel relationships for subdivisions. |
|
☐ |
Existing applications, sales and payment schedules where migration is required. |
Financial configuration
|
☐ |
Accepted payment gateways. |
|
☐ |
Company bank accounts. |
|
☐ |
Buyer and Real Estate Company wallet configuration. |
|
☐ |
Default payout method. |
|
☐ |
Outright and instalment policies. |
|
☐ |
Deposit, interest, frequency and duration rules. |
|
☐ |
Bank-transfer verification responsibility. |
|
☐ |
Refund and cancellation process. |
Documents and governance
|
☐ |
Approved sale-agreement template. |
|
☐ |
Payment-schedule format. |
|
☐ |
Receipt format. |
|
☐ |
Identity and due-diligence requirements. |
|
☐ |
Approval authorities. |
|
☐ |
Completion and handover checklist. |
|
☐ |
Document retention policy. |
|
☐ |
Client support and escalation process. |
23 User Acceptance Testing and Go-Live
|
Test area |
Acceptance test |
|
Parcel creation |
Create a test parcel with images, zoning, size, price and Owned status. |
|
Subdivision |
Create child parcels and verify parent-child relationships. |
|
Publication |
Publish a test parcel and confirm it appears in web, mobile and API browsing. |
|
Filters |
Test country, state, city, zoning, price and size filters. |
|
Currency |
Confirm converted display and original currency remain clear. |
|
Contact owner |
Send a test enquiry and verify notification. |
|
Application |
Submit a purchase and an instalment application. |
|
Approval |
Approve an application and verify LandSale and parcel Pending status. |
|
Rejection |
Reject an application with reason and verify client notification. |
|
Payment plan |
Generate deposit and instalment records and verify calculations. |
|
Wallet payment |
Complete a controlled wallet payment. |
|
Gateway payment |
Complete and verify a test gateway callback. |
|
Bank transfer |
Upload and manually verify a test receipt. |
|
Payout |
Confirm Real Estate CompanyPayout creation and status. |
|
Documents |
Generate agreement, schedule and receipt PDFs. |
|
Reminder |
Test upcoming payment reminder. |
|
Overdue |
Test overdue status and client notification. |
|
Completion |
Complete a test sale and verify parcel Sold status. |
|
Cancellation |
Cancel a test sale and verify parcel returns to For Sale. |
|
Reports |
Verify dashboard, revenue, collection, overdue and export. |
|
|
Pilot first Begin with a small group of parcels and authorised staff. Confirm parcel data, payments, documents, notifications and reports before moving the full land portfolio onto the module. |
24 Common Issues and Troubleshooting
|
Issue |
Recommended action |
|
Parcel does not appear publicly |
Confirm status is For Sale and required public information is complete. |
|
Wrong currency is displayed |
Review parcel currency, client preference and currency-service configuration. |
|
Subdivision totals do not reconcile |
Review child-parcel sizes against the approved subdivision plan. |
|
Client cannot apply |
Check parcel status, client account and whether an active application already exists. |
|
Approval does not create a sale |
Review transaction logs, permissions and parcel availability. |
|
Parcel remains For Sale after approval |
Verify the approval workflow changed the parcel to Pending. |
|
Payment plan amount is incorrect |
Review deposit, interest, frequency, duration and auto-calculate settings. |
|
Gateway payment not confirmed |
Review callback verification and provider transaction status. |
|
Bank-transfer receipt is pending |
Authorised finance staff must verify it against the bank record. |
|
Real Estate Company payout is delayed |
Check payout method, bank or wallet configuration, gateway status and payout record. |
|
Client cannot download document |
Confirm the sale, document generation and access permission. |
|
Sale cannot be completed |
Review payments, documents, permissions and unresolved conditions. |
|
Cancelled parcel not re-listed |
Confirm cancellation completed and parcel status returned to For Sale. |
|
Report totals differ from finance |
Reconcile confirmed payments, reversals, unverified transfers and reporting period. |
25 Frequently Asked Questions
Can a large parcel be divided into smaller plots?
Yes. The subdivision action creates child LandParcel records that can be independently priced, published and sold.
Can a client apply to lease land instead of buying it?
The supplied application model supports Purchase or Lease. The exact downstream lease workflow should be confirmed if it differs from LandSale.
Can the client offer a different price?
Yes. The application includes an offered price which the Real Estate Company reviews.
Can the company sell directly to a known buyer?
Yes. The manual-sale route bypasses the public application stage.
Can the buyer pay in instalments?
Yes. A LandPaymentPlan can include deposit, interest, frequency, duration and individual instalments.
Can the buyer pay through bank transfer?
Yes. The client uploads a receipt and authorised staff verify it.
Are converted currency values contractual?
No. The agreement should state the contractual sale currency.
Does the system generate legal documents?
LandDocumentService generates sale agreement, payment schedule and receipt PDFs from recorded data.
Does a completed status automatically transfer legal ownership?
No. Completion records the operational status. Legal transfer depends on the signed documents and applicable requirements.
Can a cancelled parcel be sold again?
The supplied workflow returns the parcel to For Sale, subject to legal, refund and dispute clearance.
Does every payment create a Real Estate Company payout?
The supplied workflow triggers payout after confirmed payment, subject to payment and payout status.
Can sales data be exported?
Yes. LandSalesReportController includes an export action for configured CSV or Excel output.
26 Technical Matters to Confirm Before Production Sign-Off
|
Area |
Confirmation required |
|
Lease application path |
Confirm how application_type = lease proceeds after approval and whether it creates LandSale or a separate lease record. |
|
Parcel status enum |
Confirm exact use of Pending and Active and all allowed transitions. |
|
Application uniqueness |
Confirm whether multiple active applications are permitted for one parcel and the conflict-resolution rule. |
|
Subdivision rules |
Confirm parent-child pricing, area reconciliation and whether the parent remains saleable. |
|
Currency provider |
Confirm exchange-rate source, refresh frequency, fallback and rounding. |
|
Gateway support |
Confirm enabled gateways for each country and environment. |
|
Wallet flow |
Confirm debit, reversal and insufficient-balance behaviour. |
|
Bank transfer |
Confirm upload limits, verification roles and rejection workflow. |
|
Payout timing |
Confirm synchronous or queued processing, retries and failure handling. |
|
Payment-plan calculation |
Confirm interest formula, rounding, deposit treatment and schedule generation. |
|
Manual sales |
Confirm required buyer fields, document requirements and approval controls. |
|
Legal documents |
Confirm templates, signature process, jurisdiction and versioning. |
|
Completion |
Confirm prerequisites and any automatic status changes. |
|
Cancellation |
Confirm refunds, penalties, document state and parcel re-listing restrictions. |
|
Notifications |
Confirm delivery channels, templates, retries and preferences. |
|
Exports |
Confirm exact formats, columns, permissions and currency presentation. |
|
|
Source basis This guide is based on the end-to-end scenario and technical reference supplied for Leaseora. Matters not explicitly defined in that material are identified for confirmation rather than assumed. |
27 Quick Reference - 32-Step Operating Flow
1. Create the land parcel with status Owned.
2. Upload feature and gallery images.
3. Subdivide the parent parcel where required.
4. Review and publish the parcel as For Sale.
5. Create a manual sale for a known buyer where appropriate.
6. Client browses published parcels.
7. Client filters by location, zoning, price and size.
8. Client views parcel details and converted price.
9. Client contacts the owner if clarification is needed.
10. Client submits a Purchase or Lease application.
11. System creates a Pending application and notifies the Real Estate Company.
12. Client views application status.
13. Real Estate Company reviews the application and documents.
14. Real Estate Company approves or rejects the application.
15. Approval creates a LandSale and changes the parcel to Pending.
16. Finance creates the instalment payment plan where required.
17. System generates LandPaymentInstallment records.
18. Client views the plan and available payment methods.
19. Client pays through wallet, gateway or bank transfer.
20. System or finance confirms the payment.
21. Real Estate Company payout is recorded and processed.
22. Client and Real Estate Company receive payment notifications.
23. Automated reminders are sent before due dates.
24. Overdue instalments are flagged and followed up.
25. Agreement PDF is generated.
26. Payment schedule PDF is generated.
27. Individual payment receipts are generated.
28. Real Estate Company reviews sales, revenue, collections and overdue reports.
29. Client views purchases, balance, next due date and documents.
30. Authorised staff complete the sale after all requirements are met.
31. Parcel status changes to Sold.
32. If the sale is cancelled, record the reason and return the parcel to For Sale when appropriate.
|
|
Business value Leaseora's Land Management module gives a real estate company one connected process for land inventory, subdivision, public sales, applications, flexible payment plans, multi-channel collection, document generation, reporting and final completion. |
LEASEORA
LAND MANAGEMENT
Manage land inventory, applications, payments, documents and sales from one connected platform.
|
|
Support and onboarding For company-account setup, land-portfolio onboarding, staff training or operational assistance, contact Leaseora through support@leaseora.com. |
leaseora.com
Tags
Was this article helpful?
Your feedback helps us improve our documentation.