Loan Management System on Apache Fineract: What It Covers and What It Doesn't

Apache Fineract covers the servicing core of a loan management system out of the box: loan products, interest methods and repayment schedules, disbursement, repayments, fees and penalties, rescheduling, delinquency, write-offs, double-entry accounting, reporting and a complete REST API. It does not cover the front of the funnel or the money movement. Borrower-facing applications, credit scoring and decisioning, KYC checks and connections to payment rails are separate systems that you build or integrate.
That split is on purpose. The Fineract documentation names loan origination, credit decisioning, scoring, KYC, credit bureaus and payment hubs as systems that sit around the core, and states that "none of these other components or systems are part of the Apache Fineract core distribution" (Fineract docs, surrounding systems). Knowing exactly where that line falls is most of the decision.
We run managed Apache Fineract, so this is the map we would want a lender to have before choosing it. Everything below is checked against Fineract 1.16.1, released on 26 October 2026 and the current stable version.
What a loan management system has to do
A loan management system (LMS) is the system of record for a loan from approval to closure. It holds the terms, generates the repayment schedule, records money going out and coming back, ages arrears, books every movement to the ledger and reports on the portfolio. Origination, the path from applicant to approved loan, sits upstream. Payments and collections sit beside it.
Vendors of lending software often sell all three under one name, which is why "loan management software" comparisons are so hard to read. One product is an origination-to-collections suite, the next is a servicing engine with an API. Fineract is the second kind. The short version:
| Capability | In Fineract out of the box | You build or integrate |
|---|---|---|
| Origination hand-off | Application states, maker-checker approval, custom fields, originator tracking | Application forms, underwriting, credit scoring, decision engine |
| KYC | Identity documents and identifiers stored on the client | Identity verification, AML and sanctions screening |
| Loan products | Products with currency, amount, term and rate limits, charges and GL mappings | Product design (configuration, not code) |
| Interest and schedules | Flat or declining balance, equal installments or equal principal, day-count options, grace, recalculation, floating rates | Testing unusual structures before launch |
| Disbursement | Single or tranche disbursement, down payment, disbursement to savings | Actually sending the money |
| Repayments | Partial, early and bulk repayments, allocation rules, refunds, standing instructions | Collecting the money and posting it through the API |
| Fees and penalties | Charges by timing and calculation type, overdue penalties, waivers | Making sure the setup respects any caps you are under |
| Rescheduling | Reschedule requests with approval, re-ageing, re-amortization | Hardship policy and eligibility |
| Delinquency and arrears | Days past due, configurable buckets, pause, events, PAR and ageing reports | Collections workflow and borrower contact |
| Write-offs | Charge-off, write-off, recovery payments, rule-based provisioning | Expected credit loss models, for example for IFRS 9 |
| Accounting | Double-entry GL, cash or accrual, automatic journal entries, period closures | Feeding a separate company ERP, if you have one |
| Reporting | Built-in reports, custom SQL reports, a report API | Regulatory returns, BI dashboards |
| APIs | REST API with an OpenAPI spec, business events over Kafka or JMS | The integrations themselves, your borrower app |
Capability by capability
Origination hand-off
Fineract has a loan application lifecycle. An application is submitted, then approved, rejected or withdrawn, and an approved loan is disbursed (loan lifecycle). Approval can sit behind maker-checker, so one person enters and another confirms. Any extra application data your origination system collects can be stored against the client or the loan in datatables, Fineract's way of adding custom fields. Fineract 1.16.1 can also tag a loan with its originator (a merchant, broker, affiliate, platform or channel) for revenue sharing and reporting (loan origination details).
What it does not do is decide. There is no scoring model and no decision engine in the core. The codebase has a credit bureau framework, but the only bureau it ships a connector for is ThitsaWorks in Myanmar (source). So the usual pattern is that the origination system captures the application, runs KYC, pulls the bureau report, scores and decides, then calls the Fineract API to create the client and the loan, approve it and disburse it.
KYC splits the same way. Fineract stores identity documents and client identifiers, and the project site lists KYC documentation support as a feature. Checking that a document is genuine, screening names against sanctions lists and monitoring for money laundering are jobs for a specialist service.
Loan products
Products are where most of the setup work goes, and where Fineract is strongest. A loan product fixes the currency, the allowed range for principal, term and interest rate, the repayment frequency, the schedule type, the charges that apply and the general ledger accounts every transaction posts to. Loans are opened from a product and can only vary the terms the product lets them vary. Our docs cover loan products and the newer progressive schedule type.
One choice deserves real time up front: cumulative or progressive schedule. It decides how multiple disbursements and recalculation behave, and which features you can use later (progressive vs cumulative). Also know that a loan copies the product's interest recalculation settings when the loan application is created, and editing the product afterwards does not change loans already on the books (interest recalculation explained). Get the product right before the first loan application is created.
Interest methods and schedules
Fineract supports flat and declining-balance interest, and amortization as equal installments or equal principal payments. Interest is calculated either daily or per repayment period, and the year can count actual days, 360, 364 or 365 days (loan product parameters). Repayments fall every so many days, weeks or months, with optional grace on principal, on interest or on arrears ageing. Due dates that land on a holiday or non-working day move according to rules you set (holidays and working days). Declining-balance loans can use interest recalculation, which re-derives interest from the dates payments actually arrived, so early and late payments change the installments that follow. Floating rates tied to a base lending rate are supported too.
For a standard installment loan you add nothing here. If your product has an unusual structure, open a test loan on a test tenant and compare the schedule to your own spreadsheet before you promise anything to a borrower. Schedule math is the last place you want a surprise.
Disbursement
Fineract disburses in one go or in tranches on a multi-disbursement product, can collect a down payment at disbursement, and can disburse straight into a linked savings account. Each disbursement can carry a payment type, so you can record which channel it went through.
It does not move the money. Fineract records that a disbursement happened. The bank transfer, mobile money push or card payout runs in a payment hub or your bank's systems, and the Fineract docs put the payment hub outside the core.
Repayments
Fineract records full, partial and early repayments, pre-closure and overpayments. An allocation strategy decides whether a payment settles penalties, fees, interest or principal first, and progressive loans get a finer-grained advanced allocation (progressive loan guide). The transaction types consumer and BNPL lenders need are already there: refunds, chargebacks, goodwill credits, merchant-issued refunds and payout refunds (transaction types). Repayments can also come from a client's savings account on a schedule through standing instructions, or in bulk through a spreadsheet import.
Collecting the money is yours: direct debit mandates, card collection, mobile money, matching bank statement lines to loans. Whatever collects the payment posts it to Fineract through the API.
Fees and penalties
Charges are defined once and attached to products or to individual loans. They can apply at disbursement, on a specified date, with each installment, or on an overdue installment as a penalty, and they can be a flat amount or a percentage of the loan amount, the interest, both, or the disbursed amount (loan charges). Charges and interest can be waived, and the waiver stays in the transaction history. Our charges guide walks through the setup.
What you add is policy. If your market caps late fees or the total cost of credit, your configuration has to stay inside those caps, and checking that is your job.
Rescheduling and restructuring
A reschedule request can move a due date, add grace on principal or interest, add extra installments or change the interest rate, and it has to be approved before it takes effect. Progressive loans also support re-ageing, which builds a new set of installments from the outstanding principal, and re-amortization, which spreads overdue amounts across the remaining installments without changing their dates.
Who qualifies for a restructure, and on what terms, is a credit policy question. Your team or your collections tool makes that call, and Fineract carries it out.
Delinquency and arrears
Every night the close-of-business job works out days past due for every active loan. You define delinquency ranges, group them into buckets and assign a bucket to each product, so a loan moves from 1-30 days to 31-60 days without anyone touching it (delinquency buckets). Delinquency is tracked per loan, and per installment too if you enable it on the product, and it can be paused for a borrower going through a temporary hardship. Each bucket change raises a business event, and the built-in reports include portfolio at risk and arrears ageing.
Fineract classifies, it does not chase. Call queues, reminder messages and letters, field visits, promise-to-pay tracking and agency placement live in a collections system that listens to those events. The delinquency guide shows the event payload you would subscribe to.
Write-offs
Fineract has two separate actions for a loan that will not be repaid. A charge-off recognises the loan as a loss but keeps it on the books, so it can still be recovered, and it can be undone. A write-off removes the receivable entirely. Money collected after a write-off is booked as a recovery payment. The exact journal entries for each are in our charge-off and write-off post and the accounting setup guide. For loan-loss provisions, you define provisioning criteria, a provisioning percentage for each days-overdue range in categories such as standard, sub-standard, doubtful and loss, and Fineract posts the provisioning entries.
That provisioning is driven by days overdue. If your reporting framework requires an expected credit loss model, as the IFRS 9 impairment requirements do, the model runs outside Fineract and you post its result as journal entries.
Accounting
The general ledger is built into the core. Each product maps to general ledger accounts, and Fineract posts double-entry journal entries automatically for disbursements, repayments, fees, penalties and accruals, on cash basis or accrual basis, the latter either periodic or upfront (accounting setup). You can post manual entries, set up accounting rules for recurring postings, close accounting periods so nobody posts into them, and run a trial balance, balance sheet and income statement from the built-in reports.
If your company books live in a separate ERP, you feed the journal entries into it. That integration is yours, usually built on the journal entry API or the event stream.
Reporting
Fineract ships dozens of reports, among them Portfolio at Risk, Aging Detail, Expected Payments By Date, Loans Pending Approval and Written-Off Loans (report definitions). Custom reports are SQL queries registered in the system and run through one API endpoint, and most of them need nothing beyond the core (reporting after Pentaho).
What you add is whatever is specific to your regulator and your board: returns in the format your supervisor wants, and dashboards. The Fineract docs describe analytics as usually reading from a data warehouse fed from replicas or the event stream, not from the transactional database (surrounding systems).
APIs and integration
This is where Fineract is unusually good for a lending core. It is headless: it exposes every capability through a single HTTPS REST API, and there is no private interface reserved for a bundled front end (system overview). The API is described by an OpenAPI descriptor that client SDKs are generated from (implementer notes), and our API overview covers the conventions. To react to changes without polling, Fineract publishes business events in Avro format to Kafka or a JMS broker such as ActiveMQ, in order and with at-least-once delivery (reliable event framework, business events guide). The older hooks feature still exists, but it is fire-and-forget (webhooks vs events).
Headless also means there is no staff UI in the box. For staff, the open-source Mifos web app connects to the same API (UI options, which front-end to run), and the borrower-facing app is yours to build against the API.
Who Fineract fits
- Digital lenders that already build their own app and decisioning and want a servicing core and ledger behind them. The API and the event stream are the reason to choose it.
- Microfinance institutions. Fineract handles individual and group lending, groups and centers, and collection sheets that take a whole center's joint liability group repayments at its meeting (collection sheets guide). Flat interest and weekly repayments are configuration, not custom code.
- SACCOs and credit unions. Loans sit next to savings, fixed and recurring deposits and share accounts in the same system and ledger, and a loan can require guarantors whose pledged savings are put on hold when the loan is approved and released as it is repaid.
- BNPL-style lenders. The progressive schedule handles disbursements made over time, down payments are built in, merchant-issued refunds and chargebacks are native transaction types, and originator records tag which merchant a loan came from.
Who it does not fit
- Lenders that want one boxed product, from application form to collections, with no integration work. Fineract is the core, and the rest is assembly.
- Teams with nobody to own the integrations. Even when someone else runs the servers, a person on your side owns product configuration and the connections to origination, KYC, payments and collections.
- Card-based credit. Card networks connect through a payment switch or processor, which the Fineract docs list as a surrounding system, not part of the core.
- Anyone who wants the software to carry their compliance. Fineract gives you the records and a report engine. Interpreting your regulator's rules and building the returns is still your work.
Build, buy, or open source plus managed
There are four realistic ways to get a loan management system, and each puts the cost somewhere different.
Build it yourself
You get exactly the product you want, and you own every line of interest, accrual and reversal logic. Those edge cases are where lending systems get hard: backdated payments, reversed repayments, recalculation that rewrites a schedule overnight. Building makes sense when the loan product itself is what sets you apart and you have the engineering budget to match.
Buy a proprietary system
A vendor carries the roadmap and, depending on the contract, some of the operations. You pay in license fees, in waiting for the vendor to get to the change you need, and in how hard it is to leave. Our comparison pages go through specific vendors.
Run open source yourself
Fineract is licensed under the Apache License 2.0, so there is no license fee and you can read and change every line. You pay in operations instead: hosting, the database, backups, monitoring, security and upgrades. Our cost of self-hosting breakdown and our notes on running Fineract in production put numbers and shape on that.
Open source, managed
You keep the open-source core and hand the running of it to someone else. That is what Finecko does: managed Apache Fineract hosting, with the Mifos web app included on every plan, on Oracle Cloud Infrastructure in Frankfurt by default and in other regions where needed. Prices are in EUR. 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, and enterprise SLAs are agreed by contract (pricing). The integrations in the table above are still yours to plan.
So, what should you do?
Write down the four systems you will need around the core: origination and decisioning, KYC, payments, and collections. For each one, decide whether you already have it, will buy it or will build it. If that list does not scare you, Fineract covers the rest.
Then put your real loan products through a test tenant. Configure them, run a handful of loans through disbursement, an early payment, a late payment, a reschedule and a write-off, and check the schedules and journal entries against what your finance team expects. A day of that tells you more than any feature list, this one included.
The quickest place to run that test is a Free Finecko tenant: managed Apache Fineract with the Mifos web app, for evaluation with up to 100 clients. Start a free evaluation, and look at the plans when you are ready for production.
FAQ
Is Apache Fineract a loan management system?
Yes, for servicing. It manages a loan from application through disbursement, repayment, delinquency, rescheduling and write-off, with double-entry accounting built in. It is not an origination or credit decisioning suite.
Does Apache Fineract include credit scoring or KYC?
No. It stores KYC documents and identifiers on the client record, but scoring, decisioning, identity verification and AML screening are separate systems. The only credit bureau connector in the codebase is for ThitsaWorks in Myanmar.
Is Apache Fineract free?
The software is free under the Apache License 2.0. Running it is not: hosting, the database, monitoring, security and upgrades cost money and engineering time, whether you do it yourself or pay a managed provider.
Can Apache Fineract handle BNPL or group lending?
Both. Progressive schedules, down payments and merchant-issued refunds cover BNPL-style products. Group and joint liability group loans with collection sheets cover the microfinance group model.
Does Apache Fineract come with a user interface?
No, it is headless. The open-source Mifos web app gives staff a UI, and Finecko includes it on every plan. The borrower-facing app is something you build on the API.
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.