Appearance
Office Datatables (m_office)
Office datatables attach custom data to office and branch records in Fineract. The office hierarchy in Fineract represents the institution's organizational structure - head office, regional offices, branches, and sub-branches. Data requirements at this level are typically operational and regulatory: licensing details, physical location attributes, regional classification for reporting, and compliance status.
All examples below use apptableName: "m_office".
Branch Profile and Contact Details
Fineract's built-in office record captures name, opening date, and position in the hierarchy. A datatable extends this with operational detail. This is one-to-one per office.
Use case: Maintaining a complete branch directory with contact, location, and operational details for network management and client-facing communications.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Branch_Code | String (20) | Internal branch code for reporting and reconciliation |
Street_Address | String (200) | |
City | String (100) | |
Region | Dropdown | Linked to a region code list |
Country | Dropdown | For multi-country institutions |
Postal_Code | String (20) | |
Phone_Number | String (20) | |
Email_Address | String (150) | Branch contact email |
Branch_Manager_Name | String (150) | |
Branch_Manager_Phone | String (20) | |
Operating_Hours | String (100) | e.g. "Mon-Fri 8:00-17:00" |
Has_ATM | Boolean | |
Is_Agent_Banking_Point | Boolean | Whether the location is also an agent banking outlet |
Regulatory Licensing
Financial institutions operating branches must hold regulatory approvals for each location. A datatable captures the license details and expiry dates, enabling compliance monitoring across the branch network.
Use case: Tracking branch-level regulatory licenses, approvals, and renewal deadlines for compliance management.
Example fields:
| Field name | Type | Notes |
|---|---|---|
License_Type | Dropdown | Full branch / Limited branch / Deposit-taking / Credit-only / Agent outlet |
License_Number | String (100) | Issued by the regulator |
Issuing_Authority | String (150) | Name of the regulatory body |
Issue_Date | Date | |
Expiry_Date | Date | |
Renewal_Status | Dropdown | Current / Renewal pending / Expired / Suspended |
Last_Inspection_Date | Date | Date of most recent regulatory inspection |
Inspection_Outcome | Dropdown | Satisfactory / Minor issues / Major issues / Enforcement action |
A compliance report querying offices with Expiry_Date within the next 90 days gives the compliance team advance notice for renewals without maintaining a separate tracking spreadsheet.
Regional and Portfolio Classification
For management reporting, branches are often grouped into regions, tiers, or market segments beyond the standard Fineract hierarchy. A datatable captures these classifications.
Use case: Segmenting the branch network for management reporting, resource allocation, and portfolio analysis by geography or market type.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Region_Code | Dropdown | Linked to a region code list |
Market_Type | Dropdown | Urban / Peri-urban / Rural |
Branch_Tier | Dropdown | Tier 1 (flagship) / Tier 2 (standard) / Tier 3 (outpost) |
Portfolio_Segment | Dropdown | Microfinance / SME / Agricultural / Mixed |
Catchment_Population | Number | Estimated population in the branch catchment area |
Competition_Level | Dropdown | Low / Medium / High |
Climate_Zone | Dropdown | For agricultural lenders tracking exposure by agro-ecology zone |
These fields allow management reports to break down portfolio performance by market type or branch tier - for example, comparing repayment rates in urban versus rural branches, or average loan sizes by tier.
Branch Performance Metadata
A datatable can capture branch-level performance benchmarks or targets set at the start of each period, enabling variance analysis in reports.
Use case: Recording annual or quarterly targets per branch for performance management dashboards.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Reporting_Period | String (10) | e.g. "2024-Q2" |
Target_Disbursements | Decimal | |
Target_Active_Clients | Number | |
Target_PAR30 | Decimal | Portfolio-at-risk target (%) |
Target_OSS | Decimal | Operational self-sufficiency target (%) |
Staff_Count | Number | Headcount at start of period |
Loan_Officers | Number | Number of active loan officers |
With this data, a stretchy report can calculate actual vs target for each branch and period without exporting to spreadsheets.
Infrastructure and Connectivity
For institutions in emerging markets managing branches across varied infrastructure environments, capturing connectivity and power availability informs technology deployment decisions.
Use case: Tracking branch infrastructure for IT planning, connectivity budgeting, and offline capability requirements.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Internet_Connection_Type | Dropdown | Fibre / 4G / 3G / 2G / Satellite / None |
Power_Reliability | Dropdown | Stable grid / Frequent outages / Generator-dependent / Solar |
Has_Generator | Boolean | |
Has_Solar | Boolean | |
IT_Equipment_Owned | Number | Number of devices (PCs, tablets) at the branch |
Offline_Operations_Capable | Boolean | Whether the branch can operate during connectivity outages |
Last_IT_Audit_Date | Date |