Open-source microfinance software: running an MFI on Apache Fineract and Mifos

Open-source microfinance software: running an MFI on Apache Fineract and Mifos

Yes, you can run a microfinance institution on open-source software. Apache Fineract, the core banking engine that grew out of the Mifos project, has what a lending MFI uses every day: groups and centers, joint-liability and individual loans, compulsory savings, collection sheets on meeting days, loan officer portfolios, delinquency tracking, double-entry accounting and a branch hierarchy. The gaps are at the edges. Fineract has no screens of its own, offline field work depends on a Mifos mobile app that is still released as beta, and the built-in report called "Portfolio at Risk" is not the PAR30 your funders ask for.

Below is each thing an MFI needs from its core system, what covers it in Fineract and the Mifos apps, and where you will have to fill a hole yourself. Then the four ways to actually run it. We run managed Apache Fineract, so we have a stake in this. We will still tell you where it falls short.

Where Mifos came from, and where Fineract fits

Mifos started at Grameen Foundation. According to the Mifos Initiative's own history, Grameen Foundation formally launched the project in 2006, as one of the first projects of its Seattle-based Grameen Technology Center, to give microfinance institutions a low-cost system to run on. In 2011 Grameen Foundation returned Mifos to the community as an independent project, and the team rewrote the codebase from scratch as Mifos X, a new API-driven platform. In July 2013 the Mifos Initiative took over the Mifos trademarks.

The next step explains today's naming. In December 2015 the Mifos Initiative submitted that platform to the Apache Incubator as Fineract (ASF announcement). The incubator record gives 15 December 2015 as the start of incubation and 19 April 2017 as the date Fineract graduated to a top-level Apache project. The old Mifos X backend repository on GitHub is now marked deprecated and points to Apache Fineract for all backend development.

So today there are two layers with two owners. Apache Fineract is the engine: a headless server with a REST API, run by the Apache Software Foundation and licensed under the Apache License 2.0. The current release is 1.16.1, published in October 2026. Mifos X is the Mifos Initiative's suite around that engine. Its GitHub repository lists the Fineract back end, a web app for staff, a reporting plug-in, a mobile field operations app and a customer mobile banking app. The web app and the field officer app are licensed under MPL 2.0. If the two names still blur together, we wrote a separate page on Mifos vs Fineract.

Two layers. On top, the Mifos X apps from the Mifos Initiative: the web app for staff (MPL 2.0), the field officer app (MPL 2.0) and the customer mobile banking app. They talk over the REST API to Apache Fineract, the engine: a headless server under the Apache License 2.0, which stores clients, groups, loans, savings and the ledger in its database. The Mifos reporting plug-in is loaded inside Fineract itself.
Two layers, two owners: the Mifos Initiative apps on top, the Apache Fineract engine underneath.

What an MFI needs, and what covers it

Groups, centers and joint-liability lending

Fineract models the group methodology directly. Clients belong to groups, groups can sit inside centers, and both can carry a loan officer and a meeting schedule, though a group inside a center follows the center's meetings once the center has a schedule (see our docs on clients, groups and centers, and on extra group data such as group leader profiles). The loan engine knows the difference between lending styles. Its account types are individual, group, JLG (an individual loan given in a group context) and GLIM (Group Loan Individual Monitoring, a group loan where each member's share is tracked), with GSIM as the savings equivalent.

How Fineract models the group methodology. An office, or branch, holds a center. The center has a loan officer and a meeting schedule and contains Group A and Group B, each with its own loan officer and both meeting on the center's schedule. Each group contains its member clients.
Clients sit in groups, groups in centers. Groups and centers each carry a loan officer, and groups inside a center meet on the center's schedule.

Joint liability is where you need to be precise about what the software does. Fineract supports guarantors on a loan, and a loan product can require that a percentage of the loan be guaranteed, with that amount frozen in the borrower's own savings or in a guarantor's savings while the loan runs (collateral and guarantors guide). If the loan goes bad, there is a recovery command that moves the held funds into the loan. What Fineract does not do is enforce the group's promise by itself. There is no setting that spreads a defaulting member's arrears across the rest of the group. That part of your methodology lives in your product setup and in how your loan officers run the group.

Individual loans

Individual loans run on the same engine, so a client can move from a group product to an individual one without changing systems. If you graduate borrowers by cycle, a loan product can vary the amount and interest rate by borrower cycle (the useBorrowerCycle setting), so a client's third loan can be bigger than their first without a separate product per cycle. Flat and declining-balance interest, weekly or monthly schedules, fees, penalties and rescheduling are all standard (loan management). The bigger decision is which loan engine to use, which we covered in progressive vs cumulative loans.

Savings and compulsory savings

Voluntary savings, fixed deposits and recurring deposits are standard products (savings and deposits). There is no single "compulsory savings" switch, though. You build the policy from one of three mechanisms:

  • A recurring deposit product flagged as a mandatory deposit, with a recommended amount per installment (recurring deposits guide). When the account inherits the group's meeting calendar, the deposit due appears on the group's collection sheet next to the loan repayments, as the collection sheet code shows.
  • A minimum required balance on a savings product, which Fineract can enforce so the client cannot withdraw below it.
  • Guarantee funds held against a loan, as described above: part of the loan amount stays frozen in the borrower's savings and is released as the loan is repaid.

Pick one per product and write down why, so every branch gives clients the same answer about what they can withdraw.

Collection sheets and meeting schedules

This is the part of Fineract that most obviously comes from microfinance. You attach a recurring meeting schedule to a group or center and record attendance at each meeting. On the meeting date Fineract produces a collection sheet: every installment due on the loans members took through the group, plus their savings deposits due, on one form. A member's individual loans and loans held by the group itself are not on it. The loan officer enters what was actually collected and saves it as one batch. There are three kinds (collection sheets guide):

  • A productive sheet for one loan officer, covering every center that meets on that date where the officer runs at least one group.
  • A standard sheet for a single group or center.
  • An individual sheet for non-group loans due on a given date.

The Mifos web app has screens for center meetings, attendance and the individual collection sheet. Its stable release has no screen for group or center collection sheets; the development branch has one that only displays the amounts due. Two things are worth knowing before your first meeting day. Through the API a partial payment is fine and leaves the rest overdue, but the web app's individual collection sheet always posts the full amount due for each account. Payment type can be set once for the whole sheet or separately on each line, so a meeting where some members pay cash and others pay by mobile money fits in one submission.

Loan officer portfolios

Staff records can be flagged as loan officers and assigned to clients, groups, centers and individual loans. When an officer leaves or a territory is split, bulk loan reassignment moves their loans to another officer in one step, and the web app has a screen for it. With roles and office scoping, a loan officer in one branch cannot open another branch's client files (user management). Built-in reports such as Portfolio at Risk take a loan officer filter, so a branch manager can pull one officer's numbers without exporting anything.

Field and offline work

Fineract is a server and the Mifos web app runs in a browser, so neither works without a connection. For the field, the Mifos Initiative maintains the Mifos X Field Officer App, a Kotlin Multiplatform app for processing transactions, managing clients, centers and groups, and handling loan and savings accounts. Its README lists offline capability as a headline feature, for officers who work in areas without coverage.

Be careful here. Every release on the app's GitHub releases page since February 2025 carries a beta label, the latest being 2026.11.1-beta.0.4 from November 2026. That does not make it unusable. It does mean you should test the exact offline workflows you depend on, sync after a day without signal included, before you hand it to a branch full of officers, and decide in advance who supports it when something breaks. There is also an offline-first app for savings groups such as VSLAs and ROSCAs, MifosSave, but its repository says it is a beta not approved for anything beyond test and development.

Portfolio at risk reporting

Delinquency tracking is solid. Every night the close-of-business job works out days past due for each active loan and places it in a delinquency bucket, a set of day ranges you define and attach to each loan product. That lets you line the ranges up with PAR 1, 30, 60 and 90, or with whatever thresholds your regulator uses (delinquency and PAR guide). Fineract also ships ready-made SQL reports, among them "Portfolio at Risk" and "Portfolio at Risk by Branch", which you can filter by office, loan officer, product and fund, and "Aging Detail", which you can filter by office.

Read the built-in PAR report before you send its number to anyone. Its query divides the overdue amount by the outstanding amount. That is an arrears rate. It has no days-past-due threshold, and a late loan counts only its missed installments, not its whole balance. PAR30, as our delinquency guide defines it, is the share of outstanding principal on loans with at least one installment 30 or more days past due. The built-in query also reaches loans through clients, so loans held by a group as a whole are left out. For a real PAR30 you need a short custom report on top of Fineract's arrears data. That is the upside of Fineract's reporting: it is SQL you can read and change. We covered how it works in reporting after Pentaho.

Accounting

Fineract keeps a double-entry general ledger. You map each loan and savings product to GL accounts once, and from then on disbursements, repayments, interest accruals and penalties post journal entries automatically, on a cash or accrual basis (accounting, accounting setup guide). Branch cash can be tracked through tellers and cashiers with end-of-day settlement (teller and cash management). It is the ledger for what happens inside the core system, not a full finance package. Rent, salaries and suppliers either go in as manual journal entries, often through accounting rules and frequent postings, or stay in a separate accounting system.

Branches and offices

Offices form a hierarchy of head office, regions, branches and sub-branches (offices and branches). Users, staff, clients and groups belong to an office, and a user sees their own office and the ones below it. Holidays can be set per office, so a regional holiday shifts repayment dates in one region and leaves the others alone (holidays and working days). Reports follow the same tree, which is why the branch-level PAR report exists at all.

Four ways to run it

The software is free. Running it is not, and the options below differ mostly in who carries that work.

Self-host

Deploy Fineract with a database and the Mifos web app on your own servers or cloud account, and run it yourself. You own upgrades, backups, security patches and the nightly jobs. The Mifos Initiative's own guidance pitches this at institutions that plan to customize or have an in-house IT team ready to maintain it, and we agree. We broke down the real cost in the cost of self-hosting Apache Fineract and what a live system needs in running Apache Fineract in production.

An implementation partner

The Mifos Initiative runs a partner program. Its partners offer implementation, configuration, hosting, customization and support, and certified partners are listed in the Mifos partner directory. A local partner can bring things a remote provider cannot, like training in your language and knowledge of your regulator's reports. Ask any partner which Fineract version they run, how they upgrade, and whether their customizations stay compatible with upstream. A heavily modified install can get stuck on an old release.

A packaged MFI SaaS such as Musoni

Musoni is a cloud core banking system for microfinance, and its CTO said in 2017 that it uses Apache Fineract as one of its core components (our Fineract vs Musoni page has the detail). Its Starter package costs EUR 999 a month for up to 3,000 end clients and 100,000 API requests a month. It includes client, group, loan, savings, shares and accounting modules, plus Musoni's Digital Field Application for 5 users. Musoni's product page says it is hosted on AWS and lists automated SMS and mobile money integration. That bundle closes several of the gaps above in one contract. The trade-offs are the client cap on the published tier and a SaaS-only model, with larger institutions on unpublished pricing.

Managed Apache Fineract

This is what we do. Finecko is managed Apache Fineract hosting, and every plan includes the Mifos web app. It runs on Oracle Cloud (OCI) in Frankfurt by default, and other regions are possible. The Free plan covers up to 100 clients and is for evaluation, not production. Starter is EUR 449 a month and Professional is EUR 1,599 a month (pricing). Enterprise SLAs are set in the contract. Whichever provider you pick, us included, settle the field question early: which mobile app your officers will use, and who supports it.

So, what should you do?

Write down your methodology before you compare software: group or individual, how meetings run, how compulsory savings works, how you define PAR, and what your regulator wants each month. Then test it on a real Fineract instance instead of a demo deck. Set up one center with two groups and a weekly meeting, a JLG product with a guarantee hold, a mandatory recurring deposit and your delinquency buckets. Disburse a few loans, run a collection sheet with one absent member and one partial payment, move the business date forward a few weeks, and check whether the buckets and your PAR report show the numbers you expect. A day of that tells you more than any feature list, this one included.

If you want to run that test without installing anything, the Finecko Free plan gives you Apache Fineract and the Mifos web app for up to 100 clients, which is enough for a pilot center. When you are ready for production, compare the plans.

Frequently asked questions

Is Apache Fineract the same as Mifos X?

No, but they are closely related. Fineract is the core banking engine, developed under the Apache Software Foundation since the Mifos Initiative submitted it to the Apache Incubator in December 2015. Mifos X is the Mifos Initiative's suite built on Fineract, with a web app for staff, a field officer app and a customer mobile banking app.

Does Apache Fineract support joint liability group lending?

Yes. It has groups and centers, JLG and GLIM loan types, meeting schedules and collection sheets. Joint liability itself is modelled through guarantors and savings held against the loan. Fineract will not automatically move one member's arrears onto the others.

Can loan officers work offline with Fineract?

Not with Fineract or the web app alone, since both need a connection. The Mifos X Field Officer App is built for offline field work, but its releases are still labelled beta, so test your offline workflows before you roll it out.

How do I get PAR30 out of Fineract?

Set up delinquency buckets that match your PAR thresholds and build a custom SQL report on Fineract's arrears data. The built-in "Portfolio at Risk" report divides overdue amounts by outstanding amounts, which is an arrears rate, not PAR30.

What does it cost to run an MFI on Fineract?

The license costs nothing under the Apache License 2.0. The cost is in running it: your own team if you self-host, a partner's fees, a SaaS subscription such as Musoni Starter at EUR 999 a month for up to 3,000 clients, or managed Fineract such as Finecko's Starter plan at EUR 449 a month.

Skip the ops. Run managed Apache Fineract.

Finecko runs managed Apache Fineract for you - the Finecko Hub, the right topology, connection pooling, backups, TLS, patching, and on-call. You get the open-source core without the operations, and the free plan is a full environment to try with no credit card.