MORTGAGE MANAGEMENT
The Mortgage module is Leaseora's end-to-end mortgage origination and servicing environment. It supports landlords and real estate companies that create mortgage or rent-to-own products, receive client applications, review eligibility, issue offers, manage legal documentation, generate amortisation schedules and collect repayments.
|
LEASEORA MORTGAGE MANAGEMENT Detailed User and Technical Operations Guide Products • Eligibility • Applications • Credit Checks • AI Assessment • Offers • Legal Documents • Amortisation • Payments • Prepayment • Analytics • Government Integration |
For real estate companies, mortgage teams, finance teams, client-service teams, legal teams, risk teams, lenders and authorised administrators
Version 1.0 | July 2026
|
|
Purpose of this guide This guide explains how a real estate company uses Leaseora's Mortgage module from product creation and client eligibility through application processing, offer management, legal documentation, mortgage activation, amortisation, payment collection, prepayment, late-payment handling, analytics, reporting and platform oversight. It also provides a detailed technical reference based on the models, controllers, services, events, notifications, jobs and AI tools supplied for the module. |
1 Purpose, Audience and Scope
The Mortgage module is Leaseora's end-to-end mortgage origination and servicing environment. It supports landlords and real estate companies that create mortgage or rent-to-own products, receive client applications, review eligibility, issue offers, manage legal documentation, generate amortisation schedules and collect repayments.
|
Item |
Description |
|
Primary users |
Real estate companies, mortgage administrators, finance teams, risk and credit teams, legal teams, client-service teams, SuperAdmins and authorised government mortgage users. |
|
Client-facing scope |
Mortgage-product browsing, eligibility checks, AI assessment, application, document upload, application status, mortgage dashboard, payments and prepayment. |
|
Company-facing scope |
Mortgage creation, portfolio management, application review, AI analysis, offers, legal documents, activation, payment management, analytics and reporting. |
|
Technical scope |
Models, controllers, services, Livewire components, events, notifications, jobs, commands, blockchain verification and government-domain integration. |
|
Operational boundary |
Leaseora supports workflow and analysis. It does not replace regulated lending approval, legal advice, independent valuation, credit bureau evidence, affordability policy or statutory compliance. |
|
|
Important decision principle AI predictions and recommendations are advisory. Final eligibility, affordability, approval, pricing, conditions, documentation and enforcement decisions must be made by authorised human users under the applicable policy and law. |
2 End-to-End Mortgage Overview
Figure 1. Complete Mortgage lifecycle
|
Phase |
Business outcome |
|
Product design |
The company defines mortgage type, amount, rate, term, property and eligibility. |
|
Product publication |
Clients can browse active mortgage products. |
|
Eligibility |
Client receives a preliminary score and product recommendations. |
|
Application |
Personal, employment, property and supporting evidence are submitted. |
|
Review |
Credit check, risk assessment, AI insight and human review are completed. |
|
Offer |
Approved terms are formalised with an expiry date. |
|
Legal documentation |
Contracts and related documents are created, stored and optionally blockchain-verified. |
|
Activation |
The mortgage becomes active and amortisation is generated. |
|
Servicing |
Payments, reminders, prepayments, late and missed payments are managed. |
|
Oversight |
Landlord, SuperAdmin and government dashboards provide monitoring, exports and diagnostics. |
3 Roles, Permissions and Segregation of Duties
|
Role |
Main responsibility |
Control |
|
Mortgage Product Administrator |
Creates and maintains mortgage products. |
Should not independently approve applications outside delegated authority. |
|
Credit / Risk Analyst |
Reviews eligibility, credit check, affordability and risk. |
AI result must be verified against evidence. |
|
Mortgage Approver |
Approves, rejects or conditionally approves applications. |
Should record reasons and conditions. |
|
Legal Officer |
Creates and manages legal documents and completion conditions. |
Should control document templates and signatures. |
|
Mortgage Servicing Officer |
Manages schedules, payments, late and missed status. |
Should not change records without evidence. |
|
Finance Officer |
Reconciles mortgage receipts, fees and landlord payouts. |
Should separate payment verification from reconciliation. |
|
Client Service Officer |
Supports applicants and active mortgage clients. |
Should not disclose restricted credit data. |
|
SuperAdmin |
Oversees platform-wide mortgages, documents, risk and reports. |
Should not alter landlord decisions without authorised process. |
|
Government Mortgage Officer |
Processes configured government-backed or rent-to-own schemes. |
Must apply programme and NHF compliance rules. |
|
|
MortgagePolicy Use MortgagePolicy and role-based permissions to restrict product changes, application access, decision actions, payment changes, document downloads and platform-level oversight. |
4 Core Models and Record Relationships
|
Record |
Relationship purpose |
|
Mortgage |
Core mortgage or property-linked financing record. |
|
MortgageProduct |
Published structured financing product. |
|
MortgageApplication |
Client's application for a product. |
|
MortgageApplicationPersonalInfo |
Personal data linked to the application. |
|
MortgageEmploymentHistory |
Employment and income history. |
|
MortgageApplicationDocument |
Application supporting documents. |
|
MortgageOffer |
Formal terms issued after approval. |
|
MortgageLegalDocument |
Legal agreement and compliance documents. |
|
MortgageDocument |
General mortgage documents. |
|
MortgageAmortizationSchedule |
Principal and interest schedule for the full term. |
|
MortgagePayment |
Individual due-date repayment record. |
|
TenantMortgageEligibilityScore |
Pre-application eligibility and AI score. |
|
MortgageImage |
Images associated with a mortgage or property. |
5 Phase 1 - Create a Mortgage
|
STEP |
Create a New Mortgage Record Primary user: Mortgage Product Administrator |
Navigate to Mortgages -> Create Mortgage. MortgageController@create and @store manage the creation workflow.
|
Field |
Purpose |
|
Title |
Clear product or property mortgage name. |
|
Description |
Plain-language explanation of the mortgage. |
|
Property |
Property linked to the mortgage. |
|
Mortgage type |
Fixed, variable, interest-only or rent-to-own. |
|
Loan amount |
Principal being financed. |
|
Property value |
Value used for loan-to-value and affordability analysis. |
|
Currency |
Contractual mortgage currency. |
|
Interest rate |
Applicable annual or configured rate. |
|
Term years |
Mortgage duration. |
|
Payment frequency |
Monthly or other supported repayment frequency. |
|
Down payment |
Amount or percentage contributed by the client. |
|
Status |
Draft, active or archived according to the supplied record design. |
|
Images |
Property or mortgage images stored through image actions. |
Creation process
1. Select the linked property.
2. Choose the mortgage type.
3. Enter the loan, value, currency, interest and term.
4. Enter the required down payment.
5. Review the expected repayment structure.
6. Upload relevant feature images.
7. Use AI auto-fill or analysis only as drafting support.
8. Save as Draft for review or activate under the authorised process.
|
|
Confirm the distinction between Mortgage and MortgageProduct The supplied scenario uses Mortgage for the core record and MortgageProduct for a structured product clients browse. Confirm the production relationship and creation sequence before training users. |
6 Mortgage Creation AI Tools
|
Action |
Purpose |
|
autoFillWithAI |
Uses property data to propose mortgage fields. |
|
analyzeAi |
Reviews terms, flags risks and suggests improvements. |
|
portfolioAnalysisView / Post |
Runs mortgage portfolio analysis. |
|
analyzePortfolioData |
Analyses the landlord's mortgage portfolio data. |
Recommended review before saving AI output
|
☐ |
Property value and loan amount are verified. |
|
☐ |
Interest rate and term are authorised. |
|
☐ |
Down payment complies with policy. |
|
☐ |
Product type is suitable for the intended client segment. |
|
☐ |
Repayment frequency matches servicing capability. |
|
☐ |
Currency and exchange-rate assumptions are correct. |
|
☐ |
Legal and regulatory requirements are satisfied. |
|
|
AI does not create binding terms AI-generated fields and suggestions remain drafts until authorised users review and approve the mortgage terms. |
7 Mortgage Images and Supporting Media
MortgageImage stores images associated with the mortgage. Use storeImage to add approved media and destroyImage to remove it.
|
☐ |
The image belongs to the correct property. |
|
☐ |
The company has permission to use the image. |
|
☐ |
The image does not misrepresent the property's condition. |
|
☐ |
Sensitive personal or document information is not visible. |
|
☐ |
A deleted image is removed from the user interface and controlled storage process. |
8 Mortgage Portfolio Management
|
STEP |
Manage Mortgage Records Primary user: Mortgage Product Administrator / manager |
MortgageController@index, @show, @edit and @update manage the mortgage portfolio.
|
Action |
Purpose |
|
View |
Open the full mortgage record and related information. |
|
Edit |
Update authorised fields. |
|
Bulk action |
Update, archive or delete selected records under permission. |
|
Archived |
View archived mortgages. |
|
Restore |
Return an archived mortgage to the active portfolio. |
|
Destroy |
Delete where policy and record relationships permit. |
|
|
Prefer archive over deletion Mortgage records may have applications, offers, legal documents and payment history. Archive rather than delete whenever the record must remain auditable. |
9 Landlord Mortgage Dashboard
|
STEP |
Use the Mortgage Dashboard Primary user: Mortgage management and executives |
|
Dashboard item |
Meaning |
|
Total mortgages |
All mortgages in the selected scope. |
|
Active |
Currently serviced mortgages. |
|
Pending |
Products or cases awaiting progression according to the deployed definition. |
|
Completed |
Mortgages fully repaid or closed. |
|
Total loan amount |
Gross principal across the portfolio. |
|
Collected payments |
Verified repayments received. |
|
Outstanding balance |
Remaining principal or scheduled amount. |
|
Upcoming payments |
Next scheduled repayment obligations. |
|
AI insights |
Risk, market or portfolio suggestions. |
MortgageDashboardController and the MortgageDashboard Livewire component provide the landlord view. API\MortgageDashboardController provides statistics, recent mortgages, upcoming payments, monthly volumes, amounts by status and top-landlord data.
|
|
Dashboard definitions require confirmation Confirm whether amounts are based on original currency, converted currency, scheduled payment, verified payment, outstanding principal or total repayable. |
10 MortgageService and Portfolio Statistics
|
MortgageService method |
Purpose |
|
getMortgagesForLandlord |
Returns mortgages owned by a landlord. |
|
getMortgageStatistics |
Calculates portfolio statistics in the selected user currency. |
|
convertMortgageCurrency |
Converts mortgage amounts through ExchangeRateService. |
Portfolio statistics controls
· Use the same period and currency for comparison.
· Separate active principal from total repayable.
· Separate collected cash from accrued interest.
· Review concentration by property, mortgage type, client and currency.
· Reconcile dashboard totals to mortgage and payment records.
11 Phase 2 - Create and Publish Mortgage Products
|
STEP |
Create a Mortgage Product Primary user: Mortgage Product Administrator |
|
Field |
Purpose |
|
Product name |
Name shown to clients. |
|
Product type |
Fixed, variable or interest-only under the supplied product design. |
|
Minimum loan |
Lowest eligible amount. |
|
Maximum loan |
Highest eligible amount. |
|
Interest rate |
Published rate or rate basis. |
|
Maximum term |
Longest available term. |
|
Eligibility criteria |
Minimum qualifying requirements. |
|
Required documents |
Documents clients must upload. |
|
Active toggle |
Controls publication and browsing. |
Product publication checklist
|
☐ |
Product name and description are clear. |
|
☐ |
Minimum and maximum amounts are consistent. |
|
☐ |
Interest rate and term are approved. |
|
☐ |
Eligibility criteria are measurable and lawful. |
|
☐ |
Required documents are necessary and proportionate. |
|
☐ |
Currency and property scope are clear. |
|
☐ |
Client disclosures and expiry rules are available. |
|
☐ |
Product is tested before is_active is enabled. |
|
|
Rent-to-own relationship The Mortgage record supports rent_to_own in the supplied scenario, while MortgageProduct lists fixed, variable and interest-only. Confirm whether rent-to-own is also a MortgageProduct type in production. |
12 Mofi Mortgage Products
MofiMortgageProduct stores Mofi-specific mortgage products. MofiMortgageAmortization and MortgageAmortization support Mofi-specific schedules.
|
|
Mofi configuration is specialised Confirm product rules, approvals, repayment calculation, government relationship, data exchange and servicing responsibilities before use. |
13 Phase 2 - Client Browses Mortgage Products
|
STEP |
Browse and Compare Products Primary user: Client |
Clients browse through MortgageProductBrowseController, MortgageProductController or MortgageMobileController.
|
Filter |
Purpose |
|
Product type |
Fixed, variable, interest-only or configured type. |
|
Loan amount range |
Products supporting the required principal. |
|
Interest rate |
Products within the selected rate range. |
|
Term |
Products supporting the preferred duration. |
Product detail should show
· Product name and type.
· Minimum and maximum loan.
· Interest rate and whether it is fixed or variable.
· Maximum term.
· Eligibility criteria.
· Required documents.
· Currency and converted display amount.
· Important conditions and application steps.
|
|
Converted amount is for display CurrencyService and CurrencyExchangeService may display amounts in the client's preferred currency. The contractual mortgage currency and rate basis must remain clear. |
14 Phase 3 - Eligibility Check
|
STEP |
Complete the Preliminary Eligibility Check Primary user: Client |
The client enters income, employment, credit history, existing debt, deposit and property value.
|
Input |
Purpose |
|
Income |
Amount, frequency and evidence source. |
|
Employment |
Status, employer, type and length. |
|
Credit history |
Available score or credit information. |
|
Existing debts |
Current monthly and total obligations. |
|
Deposit |
Cash contribution available. |
|
Property value |
Expected property value. |
Figure 2. Eligibility and application flow
15 Eligibility Analytics and Recommendation Engine
|
Service action |
Purpose |
|
predictLoanApprovalProbability |
Estimates approval probability. |
|
performEnhancedRiskAssessment |
Assesses risk across the supplied application data. |
|
generateRecommendations |
Recommends products and improvement actions. |
TenantMortgageEligibilityScore stores the eligibility result. MortgageScoreFeedback and MortgageScoreInsight provide real-time score feedback and improvement tips.
|
|
Preliminary only An eligibility score is not a mortgage approval, offer or guarantee. It depends on the accuracy of client inputs and does not replace full evidence, credit checks or underwriting. |
16 AI Mortgage Assessment for Clients
|
STEP |
Review AI Eligibility Assessment Primary user: Client |
MortgageAIAssessmentController presents a detailed assessment, improvement tips and product recommendations.
How the client should use the assessment
1. Review which factors improve or reduce eligibility.
2. Check whether income and debt information is accurate.
3. Review deposit and property-value assumptions.
4. Compare recommended products.
5. Take suggested improvement steps where realistic.
6. Re-run the check only after meaningful information changes.
|
|
Explainability and fairness Eligibility feedback should identify relevant factors without exposing protected decision logic, creating discriminatory treatment or presenting a prediction as a final decision. |
17 Phase 4 - Submit a Mortgage Application
|
STEP |
Apply for a Mortgage Product Primary user: Client |
|
Application area |
Required information |
|
Mortgage product |
Selected product. |
|
Loan amount |
Requested principal. |
|
Property value |
Value of the intended property. |
|
Down payment |
Client contribution. |
|
Property address |
Property being financed. |
|
Property type |
Residential or other configured type. |
|
Personal information |
Name, date of birth, nationality and marital status. |
|
Employment information |
Employer, income, employment type and years employed. |
|
Documents |
Payslips, bank statements, ID and proof of address. |
Submission sequence
1. Select the mortgage product.
2. Enter requested mortgage and property information.
3. Complete personal information.
4. Add employment history.
5. Upload all required documents.
6. Review declarations and consent.
7. Submit the application.
8. Record the application reference and status.
The system creates MortgageApplication, MortgageApplicationPersonalInfo, MortgageEmploymentHistory and MortgageApplicationDocument records. Status begins as Pending.
|
|
Personal and financial data Applications contain highly sensitive information. Access, downloads, exports and retention should be restricted and audited. |
18 Automated Credit Check and Application Notifications
ProcessMortgageApplicationCreditCheck is dispatched after submission. It runs the configured automated credit-check process.
|
Notification / event |
Recipient / purpose |
|
NewMortgageApplicationNotification |
Landlord or administrator is told that a new application was received. |
|
MortgageApplicationReceivedNotification |
Client receives submission confirmation. |
|
MortgageApplicationUpdated |
Triggers downstream processing when the application is created or changed. |
|
|
Credit-check consent and source Confirm the client's consent, credit provider, jurisdiction, permissible purpose, result storage and dispute process before enabling live checks. |
19 Client Application Dashboard
|
STEP |
View and Manage Submitted Applications Primary user: Client |
MortgageApplicationController and MortgageMobileController show application status, documents and available credit-check information.
· View all submitted applications.
· Open one application.
· See current status.
· Review submitted documents.
· Review available credit-check result.
· Cancel a Pending application.
|
|
Cancellation effect requires confirmation Confirm whether cancellation stops the credit-check job, removes the application from review, preserves the record and affects any fee or document retention. |
20 Phase 5 - Landlord Application Review
|
STEP |
View and Filter Mortgage Applications Primary user: Credit / Risk Analyst |
MortgageApplicationController@index shows all applications with client profiles.
|
Filter |
Use |
|
Status |
Pending, under review, approved, rejected or conditional approval. |
|
Product |
Applications for a selected mortgage product. |
|
Client |
Name or email. |
|
Date range |
Submission or update period. |
|
Loan range |
Requested amount range. |
Review checklist
· Client identity and application ownership.
· Product and requested amount.
· Property address, type and value.
· Down payment evidence.
· Income and employment history.
· Existing debt and affordability.
· Credit-check result.
· Required documents and authenticity.
· Currency and converted display.
· Any AI risk flags or market context.
21 AI-Powered Application Analysis
|
STEP |
Analyse an Application with AI Primary user: Credit / Risk Analyst |
|
Action |
Purpose |
|
analyzeWithAI |
Runs the case-specific landlord analysis. |
|
analyzeMortgageTerms |
Reviews the proposed terms. |
|
predictLoanApprovalProbability |
Estimates approval probability. |
|
performEnhancedRiskAssessment |
Provides enhanced risk scoring. |
|
generateMarketAnalysis |
Adds market context. |
|
generateMortgageSuggestions |
Suggests a mortgage structure. |
Figure 3. AI-powered mortgage intelligence
|
|
Human decision record Record the evidence reviewed, affordability assessment, reason, conditions and approver. Do not store only an AI score as the decision rationale. |
22 Application Status Management
|
STEP |
Update Application Status Primary user: Authorised Mortgage Approver |
|
Status |
Meaning |
|
Pending |
Application submitted and awaiting action. |
|
Under Review |
Evidence and underwriting are being reviewed. |
|
Conditional Approval |
Potential approval subject to stated conditions. |
|
Approved |
Application approved for offer preparation. |
|
Rejected |
Application declined under authorised decision. |
Figure 4. Mortgage and application status lifecycles
Bulk status update
bulkUpdate can change multiple application statuses. Use it only when each application has been individually reviewed under the same approved decision rule.
|
|
Decision communication MortgageApplicationStatusNotification and MortgageApplicationStatusUpdateNotification inform the client. The message should accurately distinguish review, conditional approval, final approval and rejection. |
23 Status Events and Notifications
|
Item |
Recipient |
Trigger |
|
MortgageApplicationStatusNotification |
Client |
Application status changed. |
|
MortgageApplicationStatusUpdateNotification |
Client |
Detailed status update. |
|
MortgageApplicationLandlordUpdateNotification |
Landlord |
Confirms the landlord action. |
|
MortgageStatusUpdated |
System event |
Triggers downstream notification or processing. |
24 Application Document Download and Review
MortgageApplicationController@downloadDocument allows authorised landlord users to download supporting documents.
|
☐ |
User is authorised for the application. |
|
☐ |
Document belongs to the application. |
|
☐ |
Download is logged. |
|
☐ |
File is scanned and safe to open. |
|
☐ |
Sensitive data is not forwarded outside authorised channels. |
|
☐ |
Any authenticity concern is recorded. |
25 Phase 6 - Create the Mortgage Offer
|
STEP |
Prepare and Issue a Mortgage Offer Primary user: Mortgage Approver / legal team |
|
Offer field |
Purpose |
|
Application |
Approved application being offered. |
|
Landlord / client |
Offer parties. |
|
Offered loan amount |
Approved principal. |
|
Interest rate |
Approved rate. |
|
Term years |
Approved duration. |
|
Monthly payment |
Expected scheduled repayment. |
|
Total repayable |
Principal, interest and configured charges. |
|
Offer expiry |
Last date for acceptance. |
|
Status |
Pending acceptance, accepted, declined or expired. |
Offer preparation controls
|
☐ |
Offer matches the approved application and conditions. |
|
☐ |
Rate, term, monthly payment and total repayable are mathematically consistent. |
|
☐ |
Currency is correct. |
|
☐ |
Down payment and conditions are clear. |
|
☐ |
Offer expiry is reasonable. |
|
☐ |
Required disclosures are included. |
|
☐ |
Authorised approver is recorded. |
|
|
Offer is not activation A pending or accepted offer does not make the mortgage active. Legal and completion conditions must be satisfied first. |
26 Offer Acceptance, Decline and Expiry
|
Offer status |
Operational meaning |
|
Pending Acceptance |
Awaiting client action before expiry. |
|
Accepted |
Client accepted the stated terms. |
|
Declined |
Client rejected the offer. |
|
Expired |
Acceptance period ended without a valid acceptance. |
|
|
Expired-offer control Confirm whether expired offers can be reopened, copied or require a new approval and updated affordability assessment. |
27 Mortgage Legal Documents
|
STEP |
Create and Manage Legal Documents Primary user: Legal Officer |
MortgageLegalDocumentController manages creation, viewing, download and deletion of legal documents.
Legal document process
1. Select the approved mortgage application and offer.
2. Create or upload the correct legal document.
3. Confirm client, property, amount, rate, term and conditions.
4. Review the final document.
5. Record signing and completion status according to the deployed workflow.
6. Download or distribute through the authorised channel.
7. Retain the document and audit history.
BlockchainDocumentService is injected into the controller so documents can be verified for authenticity where configured.
|
|
Blockchain verification is not legal approval A verification record can support authenticity and tamper evidence. It does not prove that the terms are lawful, fair, signed by the correct party or legally enforceable. |
28 Mortgage Document Management
|
STEP |
Upload, Export and Verify Mortgage Documents Primary user: Mortgage and legal teams |
|
Action |
Purpose |
|
Upload |
Add a mortgage document. |
|
Delete |
Remove an authorised document. |
|
Bulk delete |
Remove multiple selected documents. |
|
Export ZIP |
Download the document set. |
|
Export PDF |
Export the document list or configured PDF output. |
|
Export CSV |
Export document metadata. |
|
Verify blockchain |
Check the stored authenticity record. |
MortgageDocumentUpdated should fire when documents are uploaded or changed.
|
|
Export contains sensitive data Restrict ZIP, PDF and CSV exports. Record the user, time, mortgage and purpose of every export. |
29 Offer-to-Activation Readiness
Figure 5. Offer, legal document and activation flow
|
☐ |
Offer accepted within the validity period. |
|
☐ |
Approval and conditions remain valid. |
|
☐ |
Required down payment is confirmed. |
|
☐ |
Legal documents are complete. |
|
☐ |
Signatures and authorisations are recorded. |
|
☐ |
Property and valuation information remain valid. |
|
☐ |
Loan, rate, term and repayment calculation are final. |
|
☐ |
Payment schedule inputs are approved. |
30 Phase 7 - Activate the Mortgage
|
STEP |
Activate an Approved Mortgage Primary user: Authorised Mortgage Servicing Officer |
After the offer and legal conditions are complete, Mortgage.status becomes Active and MortgageAmortizationSchedule records are generated.
1. Open the approved mortgage.
2. Confirm activation readiness.
3. Set the activation or completion date.
4. Change the mortgage to Active.
5. Generate the amortisation schedule.
6. Generate MortgagePayment records.
7. Review the first payment date and amount.
8. Notify and onboard the client.
|
|
Activation changes financial obligations Do not activate a mortgage until all required conditions are confirmed because the amortisation and payment records become the servicing basis. |
31 Amortisation Schedule
MortgageAmortizationSchedule stores the full repayment breakdown over the loan term.
|
Schedule field |
Meaning |
|
Period |
Instalment sequence. |
|
Opening principal |
Principal before the payment. |
|
Interest |
Interest allocated to the period. |
|
Principal |
Principal repaid in the period. |
|
Total payment |
Principal plus interest and configured amount. |
|
Closing principal |
Remaining principal after the payment. |
Amortisation validation
· Loan amount equals the opening principal.
· Interest rate and payment frequency are correct.
· Term length produces the expected number of payments.
· Principal never becomes negative.
· Final balance is zero or matches the defined residual.
· Monthly payment and total repayable agree with the accepted offer.
· Rounding differences are controlled.
32 Generate Mortgage Payment Records
|
STEP |
Generate the Payment Schedule Primary user: Mortgage Servicing Officer |
MortgagePaymentController@generatePayments creates one MortgagePayment record for each due date.
|
MortgagePayment field |
Purpose |
|
Due date |
Scheduled payment date. |
|
Principal amount |
Principal component. |
|
Interest amount |
Interest component. |
|
Total amount |
Total due. |
|
Status |
Pending, paid, late, missed or other implemented value. |
amortizationSchedule displays the full schedule.
|
|
Regeneration risk Confirm whether payment schedules can be regenerated after activation and how duplicate or previously paid records are prevented. |
33 Phase 8 - Client Mortgage Dashboard
|
STEP |
View Active Mortgages and Payments Primary user: Client |
TenantMortgageDashboardController and MortgageMobileController provide the client mortgage view.
|
Dashboard item |
Meaning |
|
Active mortgages |
All current mortgage agreements. |
|
Current balance |
Remaining principal or configured outstanding amount. |
|
Monthly payment |
Regular repayment amount. |
|
Next due date |
Next MortgagePayment due. |
|
Payment history |
Verified completed payments. |
|
Payment schedule |
All upcoming and previous due dates. |
|
Payment detail |
Principal, interest, amount and status. |
|
Prepayment information |
Available principal-reduction options and penalties. |
|
|
Current balance definition Confirm whether the dashboard balance is principal only, principal plus accrued interest, total scheduled amount or settlement balance. |
34 Prepayment Information and Processing
MortgageMobileController@prepaymentInfo shows the permitted prepayment amount, effect and penalty. processPrepayment applies the prepayment.
1. Open the mortgage detail.
2. Review the prepayment information.
3. Confirm minimum amount and penalty.
4. Select the prepayment amount.
5. Choose an available payment method.
6. Complete and verify the payment.
7. Apply the amount to principal according to policy.
8. Regenerate or recalculate the remaining schedule if required.
9. Download confirmation.
|
|
Prepayment treatment must be defined Confirm whether prepayment reduces term, reduces future payment amount, changes interest, creates a fee or requires a new schedule. |
35 Phase 9 - Make a Mortgage Payment
|
STEP |
Pay a Mortgage Instalment Primary user: Client |
MortgagePaymentController and MortgageMobileController support gateway, wallet and bank-transfer methods.
Figure 6. Amortisation and mortgage payment flow
36 Gateway Mortgage Payment
1. Open the MortgagePayment due record.
2. Create a payment intent with the selected gateway.
3. Pass mortgage, payment, amount, currency and client metadata.
4. Complete the provider checkout.
5. Receive the callback.
6. Verify the provider reference and transaction server-side.
7. Call paymentSuccess only after verification.
8. Use paymentFailure for verified failure.
9. Update the MortgagePayment and send notifications.
|
|
Callback is not enough The mobile or browser return should not alone mark the payment as received. Verify status, amount, currency and reference with the provider. |
37 Wallet Mortgage Payment
processTenantWalletPayment debits the client's wallet.
1. Confirm the MortgagePayment is due and not already paid.
2. Convert the amount if the wallet currency differs from the mortgage currency.
3. Calculate the platform fee.
4. Check available wallet balance.
5. Debit amount and fee atomically.
6. Mark the MortgagePayment as paid.
7. Create LandlordPayout.
8. Dispatch ProcessLandlordPayout.
9. Record the transaction and send confirmation.
|
|
Atomic processing Wallet debit, payment update, fee record and payout creation should succeed together or roll back together to avoid financial imbalance. |
38 Bank Transfer Mortgage Payment
The client uploads bank-transfer proof. The company reviews and approves or rejects the transfer.
|
Outcome |
Notification |
|
Approved |
MortgageBankTransferApprovedNotification to the client. |
|
Rejected |
MortgageBankTransferRejectedNotification to the client. |
· Proof belongs to the client and mortgage.
· Reference, account, amount and currency match.
· Funds have reached the destination account.
· The transfer has not already been applied.
· Approval or rejection is recorded with the reviewer.
|
|
Proof is not payment An uploaded receipt is evidence submitted by the client. The MortgagePayment should become paid only after confirmed receipt and approval. |
39 Payment Notifications, Events and Support
|
Item |
Recipient |
Trigger |
|
MortgagePaymentReceivedNotification |
Client |
Payment confirmed. |
|
MortgagePaymentReceivedLandlordNotification |
Landlord |
Payment received. |
|
MortgageDownPaymentNotification |
Client |
Down payment processed. |
|
MortgagePaymentUpdated |
System event |
Triggers downstream processing after payment change. |
contactSupport allows the client to raise a payment issue linked to the MortgagePayment.
|
|
Support should preserve context A payment support request should include mortgage ID, payment ID, client, amount, currency, method, provider reference and current status without exposing credentials. |
40 Payment Analytics
|
STEP |
Review Mortgage Payment Performance Primary user: Mortgage Servicing Officer / manager |
|
Metric |
Purpose |
|
On-time rate |
Payments received on or before due date. |
|
Late payments |
Payments received after due date. |
|
Missed payments |
Payments not received under the defined rule. |
|
Principal paid |
Cumulative principal reduction. |
|
Interest paid |
Cumulative interest received. |
|
Outstanding balance |
Remaining principal or scheduled balance. |
|
|
Metric definitions Document the exact treatment of partial payments, grace periods, bank-transfer pending status, refunds, prepayments and waived amounts. |
41 Late and Missed Payments
|
STEP |
Mark or Process Late and Missed Payments Primary user: Mortgage Servicing Officer |
MortgagePaymentController@markLate and @markMissed manage manual status changes. ProcessLateMortgagePayments automates late-payment processing and penalties.
1. Confirm the due date and grace period.
2. Check gateway, wallet and bank-transfer activity.
3. Confirm no pending payment is awaiting verification.
4. Mark Late or Missed under the approved definition.
5. Apply the configured penalty if authorised.
6. Send the appropriate reminder or notice.
7. Record support, forbearance or remediation action.
|
|
Do not mark missed too early A delayed callback, pending bank transfer or reconciliation issue can make a payment appear unpaid. Verify before applying penalties or adverse status. |
42 Payment Reminders and Scheduled Jobs
|
Job / notification |
Purpose |
|
SendMortgagePaymentReminders job |
Sends reminders before due dates. |
|
SendMortgagePaymentReminders command |
Runs the scheduled reminder process. |
|
MortgagePaymentReminderNotification |
Notifies the client. |
|
ProcessLateMortgagePayments |
Processes late status and configured penalties. |
Reminder controls
|
☐ |
Reminder is linked to the correct mortgage and payment. |
|
☐ |
Amount, currency and due date are current. |
|
☐ |
Already-paid payments are excluded. |
|
☐ |
Client communication preferences are respected. |
|
☐ |
Escalation timing follows policy. |
|
☐ |
Repeated reminders do not become excessive. |
43 Phase 10 - Mortgage Analytics
|
STEP |
Use Portfolio Mortgage Analytics Primary user: Mortgage management / risk |
|
Metric / insight |
Purpose |
|
Total loan book |
Principal across active mortgages. |
|
Collection rate |
Verified receipts relative to scheduled amounts. |
|
Default rate |
Mortgages meeting the defined default condition. |
|
Approval probability |
AI estimate for applications. |
|
Enhanced risk |
AI risk assessment. |
|
Market analysis |
Market context for portfolio decisions. |
|
|
Default definition requires policy The supplied scenario refers to default rates but does not define the number of missed payments, days past due or legal trigger. Confirm before reporting. |
44 Exports and Mortgage Reports
|
STEP |
Export or Email Mortgage Reports Primary user: Mortgage management |
|
Action |
Output |
|
exportPDF |
Mortgage portfolio report in PDF. |
|
exportCSV |
Mortgage portfolio data in CSV. |
|
emailReport |
Sends the report to specified recipients. |
|
MortgageApprovalNotification |
Approval email. |
|
MortgageReportAttachmentMail |
Email with report attachment. |
|
MortgageWeeklySummary |
Automated weekly mortgage summary. |
|
|
Secure report distribution Mortgage reports contain financial and personal data. Confirm recipient, purpose, encryption and retention before sending. |
45 Phase 11 - SuperAdmin Oversight
|
STEP |
Use the SuperAdmin Mortgage Dashboard Primary user: SuperAdmin |
SuperAdmin\MortgageDashboardController and the API controller provide platform-wide mortgage statistics.
|
View |
Purpose |
|
Dashboard stats |
Aggregate platform metrics. |
|
Recent mortgages |
Recently created or updated records. |
|
Upcoming payments |
Platform-wide future due dates. |
|
Mortgages by month |
Monthly volume chart. |
|
Amounts by status |
Loan values grouped by status. |
|
Top landlords |
Landlords ranked by mortgage volume. |
|
STEP |
Monitor Platform Mortgage Risk Primary user: SuperAdmin |
MortgageMonitoringController supports platform-wide monitoring, high-risk flags, default and collection review and authorised intervention.
|
|
SuperAdmin oversight is not silent ownership transfer Platform intervention should preserve landlord responsibility, decision history, permissions and client communication. |
|
STEP |
Review Mortgage Documents Primary user: SuperAdmin |
SuperAdmin\MortgageDocumentController provides platform-wide document oversight and blockchain verification.
|
STEP |
Review Mortgage Legal Documents Primary user: SuperAdmin |
SuperAdmin\MortgageLegalDocumentController supports legal-document oversight and compliance review.
|
STEP |
Export Platform Mortgage Data Primary user: SuperAdmin |
SuperAdmin\MortgageExportController supports PDF, CSV and emailed reports.
47 Phase 12 - Government Mortgage Integration
|
STEP |
Process Government-Backed Mortgage Applications Primary user: Government mortgage administrator |
MortgageOriginationService@processGovMortgageApplication handles configured government-backed applications. handleRentToOwnScheme supports configured government rent-to-own programmes.
|
Component |
Purpose |
|
MortgageOriginationService |
Government mortgage origination and rent-to-own. |
|
NHFComplianceService |
National Housing Fund compliance checks. |
|
ExchangeRateService |
Currency conversion for government mortgage amounts. |
|
MofiMortgageProduct |
Mofi-specific product. |
|
MofiMortgageAmortization |
Mofi-specific schedule. |
|
MortgageAmortization |
Mofi mortgage amortisation model. |
|
|
Government programme rules are external requirements Eligibility, subsidy, NHF, allocation, documentation, approval and reporting must follow the live programme and government authority rules. |
48 Phase 13 - Data Diagnostics
|
STEP |
Run Mortgage Data Diagnostics Primary user: Technical / data administrator |
DiagnoseMortgageData identifies orphaned records, missing amortisation schedules and payment discrepancies.
· Every application references a valid product and client.
· Every approved active mortgage has a valid offer.
· Every active mortgage has an amortisation schedule.
· MortgagePayment totals align with the schedule.
· Payment status and paid amount are consistent.
· Documents reference valid mortgage or application records.
· No duplicate payment schedule exists.
· Archived and deleted records preserve required relationships.
|
|
Diagnostic output requires remediation ownership Assign each issue to a technical, finance, mortgage or legal owner and document the corrective action. |
49 Multi-Currency Mortgage Controls
CurrencyService, CurrencyExchangeService and ExchangeRateService support mortgage amount conversion for landlords and clients.
|
Currency concept |
Meaning |
|
Mortgage currency |
Contractual currency of the loan and payments. |
|
Client display currency |
Preferred currency used for display. |
|
Landlord display currency |
Preferred management currency. |
|
Exchange rate |
Rate used for display or approved conversion. |
|
Original amount |
Amount retained in the mortgage currency. |
|
Converted amount |
Display or processing amount in another currency. |
|
☐ |
Original loan and payment amounts are preserved. |
|
☐ |
The exchange-rate source and time are stored or traceable. |
|
☐ |
Client sees both display and contractual currency where necessary. |
|
☐ |
Payment is processed in the intended contractual currency. |
|
☐ |
FX fees and rounding are disclosed or recorded. |
|
|
FX can change affordability For cross-currency clients, a converted display does not remove exchange-rate risk. Product and client communications should explain who bears that risk. |
50 AI Governance and Fair Lending Controls
|
Control |
Requirement |
|
Data quality |
AI output depends on accurate, complete and current information. |
|
Human review |
Authorised staff make final decisions. |
|
Explainability |
Decision factors and reasons should be understandable. |
|
Fair treatment |
Do not use protected characteristics unlawfully or create unfair outcomes. |
|
Consistency |
Apply policy and conditions consistently. |
|
Audit |
Retain input, version, output and human action. |
|
Privacy |
Restrict use of personal, employment and credit data. |
|
Appeal / correction |
Provide a process to correct inaccurate information. |
|
|
AI model performance is not the same as legal compliance Approval probability and risk accuracy do not by themselves prove fairness, suitability, affordability or compliance. |
51 Document and Data Security
|
☐ |
Use role-based access for personal, employment and credit data. |
|
☐ |
Encrypt sensitive documents at rest and in transit. |
|
☐ |
Log viewing, download, export and deletion. |
|
☐ |
Scan uploads for malware. |
|
☐ |
Restrict report and ZIP exports. |
|
☐ |
Define retention for rejected, cancelled, active and completed cases. |
|
☐ |
Protect blockchain identifiers and document hashes from unauthorised alteration. |
|
☐ |
Do not place sensitive data in ordinary notifications. |
|
|
Sensitive-data classification Mortgage applications should be treated as high-sensitivity financial records with stricter access and retention than ordinary property enquiries. |
52 Operational Status and Exception Matrix
|
Record |
Status |
Meaning |
|
Mortgage |
Draft |
Being prepared. |
|
Mortgage |
Active |
Agreement activated and serviced. |
|
Mortgage |
Archived |
Removed from current operations but retained. |
|
Application |
Pending |
Submitted and awaiting review. |
|
Application |
Under Review |
Assessment in progress. |
|
Application |
Conditional Approval |
Approval subject to conditions. |
|
Application |
Approved |
Approved for offer. |
|
Application |
Rejected |
Declined. |
|
Offer |
Pending Acceptance |
Awaiting client action. |
|
Offer |
Accepted |
Client accepted. |
|
Offer |
Declined |
Client declined. |
|
Offer |
Expired |
Acceptance period ended. |
|
Payment |
Pending |
Due but not confirmed. |
|
Payment |
Paid |
Payment confirmed. |
|
Payment |
Late |
Past due under the defined rule. |
|
Payment |
Missed |
Not received under the defined rule. |
|
|
Confirm exact production enums The guide uses the statuses described in the supplied scenario. Confirm exact database enums, transition rules and automated actions. |
53 Notifications Reference
|
Notification |
Recipient |
Trigger |
|
NewMortgageApplicationNotification |
Landlord / Admin |
New application. |
|
MortgageApplicationReceivedNotification |
Client |
Application submitted. |
|
MortgageApplicationStatusNotification |
Client |
Status changed. |
|
MortgageApplicationStatusUpdateNotification |
Client |
Detailed status update. |
|
MortgageApplicationLandlordUpdateNotification |
Landlord |
Decision action confirmation. |
|
MortgagePaymentReceivedNotification |
Client |
Payment confirmed. |
|
MortgagePaymentReceivedLandlordNotification |
Landlord |
Payment received. |
|
MortgagePaymentReminderNotification |
Client |
Upcoming due date. |
|
MortgageDownPaymentNotification |
Client |
Down payment processed. |
|
MortgageBankTransferApprovedNotification |
Client |
Bank transfer approved. |
|
MortgageBankTransferRejectedNotification |
Client |
Bank transfer rejected. |
54 Events, Jobs, Commands and Livewire Reference
|
Component |
Type |
Purpose |
|
MortgageApplicationUpdated |
Event |
Application created or updated. |
|
MortgageStatusUpdated |
Event |
Mortgage or application status changed. |
|
MortgagePaymentUpdated |
Event |
Payment changed. |
|
MortgageDocumentUpdated |
Event |
Mortgage document changed. |
|
ProcessMortgageApplicationCreditCheck |
Job |
Runs automated credit check. |
|
ProcessLateMortgagePayments |
Job |
Processes late payment penalties. |
|
SendMortgagePaymentReminders |
Job |
Sends payment reminders. |
|
SendMortgagePaymentReminders |
Command |
Runs scheduled reminders. |
|
DiagnoseMortgageData |
Command |
Runs data diagnostics. |
|
MortgagesTable |
Livewire |
Real-time mortgage table. |
|
MortgageDashboard |
Livewire |
Real-time landlord dashboard. |
|
MortgageScoreFeedback |
Livewire |
Real-time eligibility score feedback. |
|
MortgageScoreInsight |
Livewire |
AI eligibility insight. |
55 Backend Models Reference
|
Model |
Purpose |
|
Mortgage |
Core mortgage record. |
|
MortgageProduct |
Published financing product. |
|
MortgageApplication |
Client application and status. |
|
MortgageApplicationPersonalInfo |
Personal details. |
|
MortgageEmploymentHistory |
Employment records. |
|
MortgageApplicationDocument |
Application evidence. |
|
MortgageOffer |
Formal offer. |
|
MortgagePayment |
Repayment due and status. |
|
MortgageAmortizationSchedule |
Full repayment schedule. |
|
MortgageDocument |
Mortgage document. |
|
MortgageLegalDocument |
Legal mortgage document. |
|
MortgageImage |
Property or mortgage image. |
|
TenantMortgageEligibilityScore |
Eligibility score. |
|
MofiMortgageProduct |
Mofi product. |
|
MofiMortgageAmortization |
Mofi schedule. |
|
MortgageAmortization |
Mofi amortisation model. |
56 Controllers Reference
|
Controller |
Purpose |
|
MortgageController |
Mortgage CRUD, AI analysis, portfolio analysis, images and bulk actions. |
|
MortgageApplicationController - Landlord |
Application review, AI analysis, status, bulk update and downloads. |
|
MortgageDashboardController - Landlord |
Landlord dashboard. |
|
MortgagePaymentController |
Payments, amortisation, analytics, wallet, gateway and bank transfer. |
|
MortgageDocumentController - Landlord |
Document upload, delete, export and verification. |
|
MortgageLegalDocumentController - Landlord |
Legal documents and blockchain verification. |
|
MortgageAnalyticsController |
Portfolio analytics. |
|
MortgageExportController - Landlord |
PDF, CSV and email reports. |
|
MortgageProductBrowseController |
Browse, product detail and application form. |
|
MortgageProductController - Client |
Browse, show, apply and submit. |
|
MortgageEligibilityController |
Eligibility check. |
|
MortgageAIAssessmentController |
Client AI assessment. |
|
TenantMortgageDashboardController |
Client mortgage dashboard. |
|
MortgageMobileController |
Mobile browse, apply, applications, mortgages, payments and prepayment. |
|
MortgageDashboardController - SuperAdmin |
Platform statistics. |
|
MortgageMonitoringController - SuperAdmin |
Platform monitoring and risk. |
|
MortgageDocumentController - SuperAdmin |
Document oversight. |
|
MortgageLegalDocumentController - SuperAdmin |
Legal document oversight. |
|
MortgageExportController - SuperAdmin |
Platform exports. |
|
API\MortgageDashboardController |
Dashboard API. |
57 Services Reference
|
Service |
Purpose |
|
MortgageService |
Mortgage retrieval, statistics and currency conversion. |
|
MortgageAIService |
Mortgage-term analysis, suggestions and portfolio analysis. |
|
MortgageAnalyticsService |
Market analysis, approval probability and risk. |
|
MortgageRecommendationEngine |
Personalised product recommendations. |
|
MortgageOriginationService |
Government-backed and rent-to-own processing. |
|
BlockchainDocumentService |
Document authenticity verification. |
|
CurrencyService |
User and property currency context. |
|
CurrencyExchangeService |
Mortgage amount conversion. |
|
ExchangeRateService |
Exchange-rate retrieval. |
|
NHFComplianceService |
National Housing Fund compliance. |
|
FeeCalculationService |
Platform fee calculation for wallet payment. |
|
LandlordPayoutService |
Landlord payout execution. |
58 Worked Example - Residential Mortgage from Application to Payment
|
|
Scenario A real estate company publishes a fixed-rate mortgage product for a completed apartment. A client checks eligibility, applies, receives approval, accepts the offer, signs the legal documents and begins monthly repayment. |
|
Stage |
What happens |
|
1. Product |
The company creates and publishes a fixed-rate MortgageProduct. |
|
2. Browse |
The client reviews loan range, rate, term, eligibility and documents. |
|
3. Eligibility |
The client submits income, employment, debts, deposit and property value. |
|
4. AI score |
The platform generates approval probability, risk and recommendations. |
|
5. Application |
The client uploads ID, payslips, bank statements and proof of address. |
|
6. Credit job |
ProcessMortgageApplicationCreditCheck runs. |
|
7. Review |
The analyst checks documents, affordability and AI output. |
|
8. Decision |
The application moves from Pending to Under Review and Approved. |
|
9. Offer |
The company creates a MortgageOffer with amount, rate, term, payment and expiry. |
|
10. Acceptance |
The client accepts before the expiry date. |
|
11. Legal |
The company creates the mortgage documents and records signatures. |
|
12. Activation |
Mortgage becomes Active. |
|
13. Schedule |
Amortisation and MortgagePayment records are generated. |
|
14. Dashboard |
The client sees balance, payment amount and next due date. |
|
15. Payment |
The client pays through wallet. |
|
16. Fee and payout |
The platform fee is recorded and landlord payout is created. |
|
17. Confirmation |
Client and landlord notifications are sent. |
|
18. Analytics |
The landlord sees principal, interest, on-time rate and outstanding balance. |
59 Implementation and Onboarding Checklist
Product and policy
|
☐ |
Mortgage types and product catalogue approved. |
|
☐ |
Interest, term, deposit and affordability policies documented. |
|
☐ |
Application statuses and decision authority configured. |
|
☐ |
Credit-check provider and consent process confirmed. |
|
☐ |
Offer and legal document templates approved. |
Data and configuration
|
☐ |
Properties and values imported or linked. |
|
☐ |
Currencies and exchange-rate services configured. |
|
☐ |
Required document lists configured. |
|
☐ |
Payment gateways, wallet and bank-transfer processes tested. |
|
☐ |
Landlord bank or wallet payout route configured. |
|
☐ |
Mofi or government programme setup confirmed where used. |
Operations and security
|
☐ |
User roles and MortgagePolicy tested. |
|
☐ |
Document access and export restrictions configured. |
|
☐ |
Jobs and scheduled commands enabled. |
|
☐ |
Notifications and email templates reviewed. |
|
☐ |
Data retention and deletion rules documented. |
|
☐ |
Diagnostic and reconciliation owners assigned. |
60 User Acceptance Testing and Go-Live
|
Test area |
Acceptance test |
|
Mortgage creation |
Create each mortgage type and validate fields. |
|
AI auto-fill |
Generate and review proposed fields. |
|
Portfolio |
Archive, restore, bulk action and filter. |
|
Product |
Create, publish and deactivate. |
|
Browse |
Filter products and verify currency display. |
|
Eligibility |
Submit data and verify score record. |
|
AI assessment |
Review recommendations and improvement tips. |
|
Application |
Submit personal, employment and documents. |
|
Credit job |
Run success, failure and retry cases. |
|
Client applications |
View and cancel Pending application. |
|
Landlord review |
Filter, download and review. |
|
AI analysis |
Run application and market analysis. |
|
Status |
Test every valid transition and notification. |
|
Bulk update |
Test permission and mixed records. |
|
Offer |
Create, accept, decline and expire. |
|
Legal documents |
Create, view, download and delete. |
|
Blockchain |
Verify valid and invalid document. |
|
Document exports |
ZIP, PDF and CSV. |
|
Activation |
Confirm readiness checks. |
|
Amortisation |
Validate schedule and total repayable. |
|
Payments |
Generate MortgagePayment records. |
|
Gateway |
Pay success, fail and callback duplicate. |
|
Wallet |
FX, fee, debit and payout. |
|
Bank transfer |
Approve and reject proof. |
|
Prepayment |
Test principal reduction and schedule effect. |
|
Late / missed |
Test grace period, reminder and penalty. |
|
Analytics |
Validate balances, rates and collections. |
|
Reports |
PDF, CSV and email. |
|
SuperAdmin |
Dashboard, monitoring and document oversight. |
|
Government |
Test configured origination and NHF checks. |
|
Diagnostics |
Detect orphan, missing schedule and discrepancy. |
|
Security |
Permissions, logging, export and retention. |
|
|
Pilot before broad launch Test one product, one property, one application, one offer, one mortgage and one full repayment cycle before wider onboarding. |
61 Daily, Weekly and Monthly Operating Procedures
|
Frequency |
Recommended activities |
|
Daily |
Review new applications, payment exceptions, bank-transfer proofs, upcoming payments, failed jobs and client support. |
|
Weekly |
Review application pipeline, conditional approvals, expired offers, overdue payments, document exceptions and MortgageWeeklySummary. |
|
Monthly |
Reconcile mortgage receipts, principal, interest, fees, payouts and balances; review portfolio risk, defaults and reports. |
|
Quarterly |
Review product pricing, eligibility criteria, model performance, document templates, government programme rules and access rights. |
62 Mortgage Servicing Reconciliation
|
☐ |
MortgagePayment records agree with gateway, wallet and bank-transfer evidence. |
|
☐ |
Principal and interest allocations agree with the amortisation schedule. |
|
☐ |
Prepayments are applied under policy. |
|
☐ |
Late and missed statuses are supported by due-date evidence. |
|
☐ |
Fees are recorded separately. |
|
☐ |
LandlordPayout records agree with verified client payments. |
|
☐ |
Refunds or reversals are reflected in balances. |
|
☐ |
Outstanding principal agrees with the servicing report. |
|
|
Three balances must agree The mortgage record, amortisation schedule and sum of payment activity should reconcile to the same outstanding position. |
63 Common Issues and Troubleshooting
|
Issue |
Recommended action |
|
Mortgage cannot be saved |
Check property, currency, required amount, rate, term and down payment. |
|
Product does not appear |
Check is_active, product type, amount filters and permissions. |
|
Converted amount is wrong |
Check source currency, user currency and ExchangeRateService. |
|
Eligibility score is missing |
Check input validation, analytics service and score record creation. |
|
Application is incomplete |
Check required personal, employment and document fields. |
|
Credit check remains pending |
Review job queue, provider response, consent and retries. |
|
Landlord cannot download a document |
Check MortgagePolicy, application ownership and storage. |
|
Status notification is wrong |
Check transition, listener and message template. |
|
Offer monthly payment is inconsistent |
Recalculate loan, rate, term and frequency. |
|
Blockchain verification fails |
Check document hash, record and verification service. |
|
Mortgage activates without schedule |
Run diagnostics and generate amortisation and payment records. |
|
Payment callback is duplicated |
Apply idempotency and provider transaction checks. |
|
Wallet payment debited but mortgage unpaid |
Review transaction rollback, fee and payment update. |
|
Bank proof was approved twice |
Add duplicate and already-paid checks. |
|
Prepayment did not reduce balance |
Review allocation and schedule recalculation. |
|
Payment marked missed incorrectly |
Check pending gateway or bank-transfer status. |
|
Dashboard balance differs |
Confirm principal definition, payments, prepayments and FX. |
|
Report export missing records |
Review filters, permissions and status scope. |
64 Frequently Asked Questions
Can a real estate company create fixed and variable mortgages?
Yes. The supplied Mortgage record supports fixed, variable, interest-only and rent-to-own.
Can clients compare mortgage products?
Yes. Browse controllers support product detail and filters.
Does the eligibility result guarantee approval?
No. It is preliminary and AI-assisted.
What documents can an applicant submit?
The supplied scenario includes payslips, bank statements, ID and proof of address.
Is a credit check automatic?
ProcessMortgageApplicationCreditCheck is dispatched after application submission.
Can an application be conditionally approved?
Yes. Conditional approval is included in the status transitions.
Can the company create a formal offer?
Yes. MortgageOffer stores amount, rate, term, monthly payment, total repayable and expiry.
Can documents be blockchain-verified?
The supplied design includes BlockchainDocumentService.
How is the payment schedule generated?
MortgageAmortizationSchedule and MortgagePayment records are generated after activation.
Can clients pay through wallet?
Yes, with currency conversion, fee calculation and landlord payout.
Can clients pay by bank transfer?
Yes, subject to proof review and approval.
Can a client make a prepayment?
Yes. Mobile methods provide prepayment information and processing.
Can late payments be processed automatically?
Yes. ProcessLateMortgagePayments is supplied.
Does the module support government mortgages?
Yes, through MortgageOriginationService and NHFComplianceService where configured.
Can reports be emailed?
Yes. Landlord and SuperAdmin export controllers support emailReport.
65 Technical Matters to Confirm Before Production
|
Area |
Confirmation required |
|
Mortgage vs product |
Confirm exact relationship between Mortgage and MortgageProduct. |
|
Status enums |
Confirm mortgage, application, offer and payment status values. |
|
Rent-to-own |
Confirm product type and government integration path. |
|
Eligibility model |
Confirm variables, weighting, versioning and explanation. |
|
Credit check |
Confirm provider, consent, retry and dispute process. |
|
AI service |
Confirm model, data retention, confidence and human review. |
|
Approval policy |
Confirm affordability, LTV, DTI, rate and delegated authority. |
|
Offer calculation |
Confirm amortisation formula, compounding and total repayable. |
|
Offer expiry |
Confirm extension, reopening and reapproval rules. |
|
Legal signatures |
Confirm e-signature workflow and completion conditions. |
|
Blockchain |
Confirm network, hash, timestamp, cost and verification evidence. |
|
Activation |
Confirm required conditions and rollback. |
|
Schedule generation |
Confirm rounding, payment dates, weekends and holidays. |
|
Payment status |
Confirm Pending, Paid, Late, Missed, Refunded and Partial values. |
|
Gateway callback |
Confirm signature, idempotency and verification rules. |
|
Wallet |
Confirm transaction atomicity, fees and FX. |
|
Bank transfer |
Confirm proof storage, account reconciliation and approval roles. |
|
Prepayment |
Confirm penalty, principal allocation and schedule recalculation. |
|
Late penalties |
Confirm grace period, amount and legal limits. |
|
Default |
Define default and reporting treatment. |
|
Payout |
Confirm landlord payout timing, failures and reversals. |
|
Government |
Confirm live Mofi, NHF and authority requirements. |
|
Exports |
Confirm PDF, CSV, ZIP and email content. |
|
Retention |
Confirm application, credit, document and payment retention. |
|
|
Specification basis This guide preserves the supplied Mortgage-module terminology and workflow. Where production behaviour was not defined, it is listed for confirmation rather than assumed. |
66 Quick Reference - 30-Step Mortgage Operating Flow
1. Create the mortgage or financing record.
2. Use AI auto-fill or analysis as drafting support.
3. Review and manage the mortgage portfolio.
4. Create and publish a MortgageProduct.
5. Client browses and compares active products.
6. Client completes preliminary eligibility input.
7. Generate approval probability, risk assessment and recommendations.
8. Store the TenantMortgageEligibilityScore.
9. Client reviews AI score feedback and improvement tips.
10. Client submits the mortgage application and documents.
11. Create personal and employment records.
12. Dispatch the automated credit-check job.
13. Notify landlord and client.
14. Landlord reviews applications and evidence.
15. Run AI application, risk and market analysis.
16. Move application to Under Review.
17. Approve, reject or conditionally approve.
18. Create the MortgageOffer.
19. Client accepts, declines or lets the offer expire.
20. Create and manage legal and mortgage documents.
21. Verify document authenticity where configured.
22. Activate the mortgage after completion conditions.
23. Generate amortisation and MortgagePayment records.
24. Client views balance, schedule and next due date.
25. Client pays by gateway, wallet or bank transfer.
26. Send payment confirmations and update analytics.
27. Process reminders, late or missed payments.
28. Process prepayment and recalculate where required.
29. Review portfolio analytics and export reports.
30. Run SuperAdmin oversight, government processing and data diagnostics.
|
|
Business value Leaseora's Mortgage module gives a real estate company one connected workflow for product design, eligibility, application, underwriting support, offers, legal documentation, amortisation, repayment, client service, analytics and oversight. |
LEASEORA
MORTGAGE MANAGEMENT
Create, assess, approve, activate and service mortgage products from one connected platform.
|
|
Support and onboarding For Mortgage-module onboarding, product setup, application workflow, payment configuration, document management or integration assistance, contact Leaseora through support@leaseora.com. |
leaseora.com
Tags
Was this article helpful?
Your feedback helps us improve our documentation.