Short, practical explanations of the terms we use most — for teams evaluating ERPNext, core banking or mobile money integration for the first time.
An open-source enterprise resource planning system built on the Frappe framework, covering finance, inventory, HR, CRM and more in one application.
The open-source web application framework that ERPNext is built on. Custom Frappe apps extend ERPNext beyond its default modules.
An open-source core banking platform for microfinance institutions and SACCOs, built on the Apache Fineract engine.
The open-source core banking engine underlying MifosX, handling accounts, loans, savings and transactions.
Unstructured Supplementary Service Data — the *123# style menu system used for mobile money on any phone, including without internet access.
The process of matching transactions recorded in one system (e.g. mobile money) against another (e.g. a core banking ledger) to confirm they agree.
Modifying an active loan's terms — schedule, amount or interest — typically to help a borrower in difficulty, without closing the original loan.
A portal allowing employees or employer HR teams to initiate loan applications or view payroll-linked lending data, often integrated with core banking.
A browser technology enabling real-time audio/video communication without installing a separate app — used in our teleconsultation platforms.
Software architecture where one deployment serves multiple separate clients (tenants), each with isolated data, from a shared codebase.
A lending metric showing the percentage of a loan portfolio with overdue payments, used to gauge lending risk.
An application design approach where core functions work without an internet connection, syncing data once connectivity returns.
Send us what you're considering — we'll give you a plain-language read on whether it fits.