Appearance
Loan Datatables (m_loan)
Loan datatables attach custom data to individual loan records. This is one of the highest-value datatable targets because loan-level data requirements span regulatory reporting, risk management, product suitability, and collections - all with different field sets.
All examples below use apptableName: "m_loan".
Collateral Management (One-to-Many)
Secured lending requires tracking one or more collateral items per loan. Since a single loan can have multiple pieces of collateral, this is multiRow: true.
Use case: Recording collateral details for secured loan products - property, vehicles, equipment, or inventory - for risk assessment and recovery operations.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Collateral_Type | Dropdown | Linked to a collateral type code list (Land / Building / Vehicle / Equipment / Inventory / Cash Deposit / Other) |
Description | String (200) | |
Estimated_Value | Decimal | Market or assessed value at origination |
Currency | Dropdown | |
Registration_Number | String (100) | Title deed, vehicle registration, or asset tag |
Ownership_Verified | Boolean | Ownership documentation confirmed |
Valuation_Date | Date | Date of most recent valuation |
Valued_By | String (100) | Appraiser name or institution |
Insurance_Policy_Number | String (100) | If the collateral is insured |
Insurance_Expiry | Date | |
Location | String (200) | Physical location or registration jurisdiction |
Credit officers can query total collateral coverage across the portfolio, identify loans with expiring insurance, or filter by collateral type for recovery planning.
Loan Purpose and Use of Funds
Regulatory frameworks and internal credit policy typically require the stated purpose of each loan to be recorded. This is one-to-one per loan.
Use case: Capturing the declared purpose of borrowing for credit decisioning, regulatory classification, and portfolio analysis.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Primary_Purpose | Dropdown | Business investment / Working capital / Education / Housing / Medical / Agriculture / Consumption / Debt refinancing / Other |
Purpose_Description | Text | Free-text elaboration |
Economic_Sector | Dropdown | Linked to a sector classification code list |
Sub_Sector | Dropdown | More granular sector breakdown |
Intended_Use_Verified | Boolean | Whether officer verified the stated purpose |
Verification_Method | Dropdown | Site visit / Documentation / Self-declaration |
Verification_Date | Date |
Central bank and development finance reporting almost always requires portfolio breakdowns by purpose and sector. Capturing this at origination as structured data - rather than in a notes field - makes these reports straightforward.
Regulatory Classification
Many jurisdictions require loans to be classified according to central bank or development finance authority frameworks - by product type, borrower category, or use category. These are typically one-to-one fields set at disbursement.
Use case: Satisfying central bank return requirements and development finance institution reporting frameworks.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Regulatory_Product_Code | String (20) | Central bank product classification code |
Borrower_Category | Dropdown | Retail / SME / Corporate / Agriculture / Government |
Gender_of_Borrower | Dropdown | For disaggregated reporting (linked to Gender code list) |
Is_MSME | Boolean | Micro, small, or medium enterprise flag |
Is_Green_Finance | Boolean | Loan supports climate or environmental goals |
Development_Finance_Category | Dropdown | Linked to a development category code list |
First_Time_Borrower | Boolean | |
Rural_Urban | Dropdown | Rural / Peri-urban / Urban |
Disaggregated loan portfolio reports - required by development finance institutions, impact investors, and regulators - pull directly from these fields rather than requiring manual data extraction.
Insurance and Credit Protection
Some institutions offer or require credit life insurance, loan protection insurance, or other credit enhancement products alongside the loan. Tracking insurance linkage as a datatable allows it to be queried and reported without a custom insurance module.
Use case: Recording insurance policy details linked to a loan for claims management and regulatory reporting.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Insurance_Provider | Dropdown | Linked to a provider code list |
Policy_Type | Dropdown | Credit life / Loan protection / Crop insurance / Asset insurance |
Policy_Number | String (100) | |
Premium_Amount | Decimal | |
Premium_Frequency | Dropdown | Monthly / Quarterly / Upfront single premium |
Coverage_Start_Date | Date | |
Coverage_End_Date | Date | |
Coverage_Amount | Decimal | Maximum payout amount |
Claim_Filed | Boolean | Whether a claim has been initiated |
Claim_Date | Date | |
Claim_Status | Dropdown | Filed / Under review / Approved / Rejected / Paid |
Loan Officer Visit Log (One-to-Many)
For field-based lending, loan officers visit borrowers for disbursement verification, usage checks, repayment follow-up, and relationship management. Each visit is a separate record, so use multiRow: true.
Use case: Maintaining a complete interaction log per loan for collections management, credit monitoring, and officer accountability.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Visit_Date | Date | |
Visit_Type | Dropdown | Pre-disbursement / Post-disbursement / Routine / Collections / Delinquency / Other |
Officer_Name | String (100) | |
Borrower_Present | Boolean | |
Business_Operating | Boolean | Whether the business was operating at time of visit |
Repayment_Commitment | Dropdown | Confirmed / Partial / Refused / Deferred |
Next_Payment_Date | Date | Commitment date given by borrower |
Risk_Flag | Boolean | Whether the visit identified a risk requiring escalation |
Notes | Text |
Collections teams can query recent visit outcomes across delinquent loans, and branch managers can review visit frequency per officer.
Agricultural Loan Seasonality
Agricultural lenders need to record planting season, crop type, and harvest timing to align repayment schedules and assess portfolio concentration risk. One-to-one per loan.
Use case: Capturing crop and season data for agricultural portfolio management and repayment scheduling alignment.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Crop_Type | Dropdown | Linked to a crop type code list |
Planting_Season | Dropdown | Long rains / Short rains / Dry season / Year-round |
Planting_Date | Date | |
Expected_Harvest_Date | Date | |
Farm_Size_Hectares | Decimal | |
Irrigated | Boolean | Whether the farm uses irrigation |
Seed_Type | Dropdown | Hybrid / Improved / Traditional |
Off-taker_Name | String (150) | Buyer or aggregator committed to purchase the harvest |
Off-taker_Contract | Boolean | Whether a formal off-take agreement exists |
This enables analysis of portfolio concentration by crop, exposure to seasonal repayment risk, and identification of loans with aligned off-take agreements.
Guarantor Information (One-to-Many)
Some loan products require one or more guarantors. Since multiple guarantors are possible, use multiRow: true.
Use case: Recording guarantor details for loan documentation and credit assessment, when guarantors are not registered as clients in the system.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Full_Name | String (150) | |
Relationship_to_Borrower | Dropdown | Spouse / Parent / Sibling / Employer / Business partner / Other |
Phone_Number | String (20) | |
ID_Number | String (50) | |
Employer_Name | String (150) | |
Monthly_Income | Decimal | |
Property_Owner | Boolean | Whether the guarantor owns property |
Guarantee_Amount | Decimal | Amount the guarantor is guaranteeing |
Guarantee_Type | Dropdown | Personal / Corporate / Property-backed |