On Page Navigation
On Page Navigation
Loan products, origination, disbursement, interest accrual, collateral and collections, running on a platform you own outright. One flat monthly price with no charge per active loan.
What Managed Frappe Lending Covers
Installing Frappe Lending takes an afternoon. What takes a quarter is deciding how your loan products behave, mapping your delinquency policy onto a classification engine written for a different regulator, and reconciling an existing book to the penny before anyone cuts over. That is the work we do. It sits on top of a full ERPNext implementation, because every accrual and every repayment posts to a real chart of accounts.
The order of that work matters more here than on most projects. Loan products and their interest behaviour are modelled and tested against known cases before anything else is touched. Classification and provisioning rules are mapped to your regulator rather than to the defaults that shipped. Then the existing book is loaded and reconciled to the penny, with a parallel run before cutover instead of after it. Nobody should go live on a lending system because the configuration looked right.
Origination is a separate stack from loan management, and buyers routinely forget it exists until someone asks how an application gets in. A form builder collects them, a rules engine scores and routes them, and approved applications become loans with electronic signing wired in. We scope both halves up front, then tell you which one to launch first.
A Loan Product carries the rate, the repayment method, the penalty structure and the accounts each charge posts to. Get it right and the system behaves for years. Get it wrong and you spend those years correcting loans one at a time. This is deliberately where most of your setup time goes.
Repayment schedules generate from the product, and interest accrual, demand raising and loan classification run on a nightly schedule. When one of those fails quietly your book is wrong and every screen still looks completely normal. We monitor them per run instead of watching a server uptime graph.
Securities are held as masters with prices, assigned against a loan and released on repayment, with the sanctioned amount deriving from pledged value. Days Past Due updates daily and feeds an automatic non-performing classification. You can override that classification when a borrower is genuinely recovering, which is the behaviour a rigid platform never gives you.
Disbursements, charges, waivers and write-offs each post into ERPNext with their own treatment. Suspense accounting handles the payment you cannot yet allocate. Posting date is tracked separately from value date, so a repayment received on the last day of a month lands in the period it belongs to.
Borrowers see balances, schedules and statements without calling anyone, which removes a cost you already pay whether or not you measure it. We brand it, configure what is visible, and treat it as the public production surface it actually is rather than as an internal screen.
Frappe Lending Against a Licensed Servicing Platform
Most lenders arrive here from a servicing platform priced per active loan, or from a spreadsheet and a servicing bureau. Both hold up until the book grows. The comparison that matters is not feature against feature. It is what you own at the end, and whether you can answer a question about your own portfolio without raising a ticket. Reporting is the usual sticking point, which is why we normally pair this with an analytics layer sitting on the live tables.
On infrastructure we manage in a region you pick, in a database your own analysts can read.
A flat monthly price with no charge per active loan, so a good year does not arrive with an invoice attached to it.
Disbursements, accruals, charges and repayments post straight to your chart of accounts. No nightly export and no reconciliation spreadsheet.
New fields, approval rules and whole record types are configuration work rather than a change request with a release date attached.
Query access and a report builder over the live loan tables. Ask a new question on a Tuesday, answer it the same afternoon.
AGPL source, a full database export, and handover documentation written for whoever replaces us.
Who This Is Built For
There is a boundary worth naming. This runs a lending business, from the application through to the final repayment. It is not a sales pipeline, and if what you need is somewhere to work the deals before they become applications, that is a different application entirely and we manage it separately. There is a second boundary too. The compliance layer was written for Indian regulation. The loan mechanics carry across to a US book cleanly, the regulatory report formats do not, and we say so before you sign anything.
How the Implementation Runs
The risk in a lending project is almost never the software. It is the book you already have. Balances, accrued interest and partial allocations all have to arrive intact and then agree with your current system to the penny, in writing, before anyone switches anything off.
1
We model your loan products, your charge structure and your delinquency policy, then map each of them onto the accounts they post to. This phase decides how much correcting you do for the rest of the system's life, so we run it slowly and on purpose.
2
We build the products, import the existing book with its schedules and accrual history, then reconcile it against your current system and hand you the variance report to sign. The reconciliation is a deliverable, not a step somebody does quietly.
3
Both systems run together through at least one full billing cycle. When the numbers agree twice, we cut over. Nobody switches off a servicing platform on a promise, and we would not ask you to.
Pricing
Standalone Service
DETAILS
Standalone Service
DETAILS
Testimonials
Everything included in the monthly price
