The loan management platform that adapts to your lending rules
GoDravix runs the whole loan lifecycle, sanction, disburse, accrue interest, allocate repayments, waive, certify and close. Built for lenders whose workflows never fitted retail-shaped software.
- 09:14Loan sanctionedLoan entry
- 09:22ApprovedSanction approval
- 10:03Disbursed, tranche 1Disbursement
- 11:40Interest accrual runAccounting
- 14:06Repayment allocatedAccounting
- 14:11NOC certificate issuedCertificates
Lending operations break in three predictable places
None of these are exotic. They are the reasons the shortlist keeps getting re-opened every two years.
The ledger nobody fully trusts
Interest gets recalculated in a spreadsheet, someone rekeys it, and by year end the balance in the system and the balance in the file have quietly drifted apart.
Software shaped like somebody else’s business
Most lending platforms were built for retail credit. If you sanction against schemes or committee approvals, recover by deduction or instalment rather than auto-debit, or waive only on a written authorisation, you are fighting the product.
Twenty years of history holding you hostage
The single most common reason a lender stays on a system they dislike is the fear that switching will lose or corrupt the loan history they are legally required to hold.
What the engine enforces
- Maker–checker approval
- Role builder and permission editor
- Zone and entity-level scoping
- Append-only audit trail
- Multi-factor authentication
- Multi-tranche disbursement
- Simple and compound interest
- Separate penal rate
- Penal → interest → principal
- Recompute after back-dated entries
- Monthly, half-yearly and yearly
- EMI schedule at sanction
- Grant deduction and cheque
- Authorised waivers with order number
- Closure, NOC and part payment
- Six statutory certificates
- Running loan ledger
- Five exportable reports
- Borrower read-only portal
- Excel and PDF export
One system for the full loan lifecycle
Five modules, running in production.
Loan Lifecycle Core
Sanction, maker–checker approval, single or multi-tranche disbursement, repayment, waiver and closure. Disbursement is blocked in software until an approval has been recorded by a different user.
Explore the moduleInterest & Accrual Engine
Simple and monthly-compound interest with a separate penal rate held distinctly throughout the ledger. Accrual is an explicit run you trigger, and existing accruals recompute after a back-dated entry.
Explore the moduleRecovery & Repayment
Every repayment allocates down one fixed waterfall (penal, then interest, then principal) so any historical allocation can be re-derived rather than reconstructed from memory.
Explore the moduleCertificates & Audit Trail
Six statutory certificates generated from live ledger balances rather than typed into a template, and an append-only event log that no role can edit, including Admin.
Explore the moduleReporting & Dashboards
A portfolio dashboard filtered by financial year, scheme and zone; five standard reports; and the running ledger behind every figure. Data scoping is enforced at query level, not by hiding a menu item.
Explore the module
Run your loan book on a ledger that reconciles, without replacing your finance stack
Your records stay where they are | No rip-and-replace | Cut-over only after sign-off
How migration worksTwo people.
Never one.
Disbursement is blocked in software until an approval event exists, and the software will not accept that approval from whoever created the record.
See the loan lifecycleBetween your records and what your auditors ask for
GoDravix is the deterministic core: the system your auditor questions, and the one that has to answer.
We moved a live government loan book and reconciled it loan by loan
Migration is the reason most lenders never switch. So we solved it as a discipline before we sold it as a feature.
- Proven on real historical data
One loan with multiple disbursements and more than a dozen repayments spread across years, rebuilt month by month and reconciled against the board’s own books.
- A documented reconciliation method
A written back-dated onboarding procedure and a reconciliation tracker, not an undocumented one-off performed by whoever was available.
- The interest-method decision made up front
Where a legacy book will not reproduce exactly under either interest method, we surface that before cut-over and agree the treatment in writing.
AI will propose. The engine and a human will approve.
No two lending books need the same AI, so each of the seven is built against your own documents, languages and thresholds. None of them is running today. What does run is the rule they all inherit: nothing a model generates writes to a loan balance without a named human approving it.
- 1The requestAn operator asks in plain language. Nothing is written yet.
- 2The proposalThe model reads the ledger and drafts a timeline, dates and amounts.
- 3The engineInterest, penal and waterfall stay with the production code, never the model.
- 4The approvalIt sits pending. No balance moves until a named person accepts it.
- 5The writeAppended with proposer, approver and timestamp. Still reversible.
- ExplainableEach proposal states the records it read and the reasoning behind the figure.
- AttributableProposer and approver are two distinct identities in the ledger.
- ReversibleAn approved proposal is undone by a correcting event, never by an edit.
Any organisation that sanctions money and recovers it over time
Five lender types, and an honest note on each about where the fit breaks.
State finance boards and municipal lending
Scheme-based sanctions, zone and entity data scoping, grant-deduction recovery, board-order waivers and statutory certificates. This is where GoDravix runs live today, and where the workflows were shaped.
- Live production reference
A state government finance board lending to more than a hundred municipal bodies, every loan migrated from legacy records and reconciled before cut-over.
- Multi-tier oversight
A regional permission sees one zone in full. A borrower sees only itself.
NBFCs and digital lenders
Term lending on a deterministic engine with a real audit trail. The honest read: the lifecycle, interest and reporting are solid; retail-specific machinery like DPD bucketing, NACH mandates and bureau integrations is built to scope.
- Fits today
Term loans, tranche disbursement, penal interest, waterfall allocation, portfolio reporting.
- Does not fit yet
Working capital and OD, DPD buckets, collections dashboards, NACH and bureau links.
Cooperative banks and credit societies
Member lending with a defensible ledger and a real approval separation. Priced by portfolio size rather than per seat, which usually suits a society with many small loans and few users.
- Approval separation by role
The person who creates a loan cannot be the person who disburses it.
- Audit-ready by construction
The event log is append-only. Nothing is edited away quietly.
Microfinance and self-help groups
Worth a conversation, with one caveat stated plainly: joint-liability group lending is a scoped build rather than a switch. If your book is individual lending through a federation structure, the platform fits today. If it is JLG, it does not yet.
- Fits today
Individual lending, federation-level scoping, frequent small repayments, entity dashboards.
- Roadmap
Group formation, joint liability, centre meeting collections, group-level waivers.
Corporate and group-company loan books
Staff loans, vendor and dealer finance, inter-company lending. Usually the simplest fit on this list: a modest number of loans, clear rules, and an auditor who wants to see a ledger that reconciles without a spreadsheet in the middle.
- Low complexity, fast rollout
Few loan products, few users, a book that fits the built feature set closely.
- Payroll recovery is roadmap
Recovery is by cheque or deduction entry today, not an automated payroll hook.
A live deployment, not a pilot deck
GoDravix began as a loan management system built for a state government finance board that lends to municipalities. It is in production, holding a migrated portfolio, with real users in six distinct roles. That deployment is the reason the workflows on this site are specific rather than generic.
We will arrange a call with the board’s accounts team through the programme’s lead contractor, so you can put your questions to the people who run it daily. Publicly, they are a state government finance board.
The deployment factsStraight answers
Loan management software runs a loan after it has been approved: disbursement, interest accrual, repayment allocation, restructuring, waivers, certificates, closure and the audit record of all of it. It is distinct from a loan origination system, which handles application, underwriting and credit decisioning up to sanction.
GoDravix is a loan management system. It picks up at sanction and runs the loan to closure. It does not score applicants or pull credit bureau data.
An origination system answers “should we lend to this borrower, and on what terms?” A loan management system answers “what is this loan’s balance today, how did it get there, and can we prove it?” Some vendors sell both under one name. GoDravix does the second. If you need origination, you would keep or buy that separately.
The full loan lifecycle, the interest and accrual engine, repayment waterfall allocation, waivers, six certificate types, the running ledger, six default roles with a role builder and query-level data scoping, a read-only borrower portal, portfolio and borrower dashboards, five reports, and an append-only audit trail. All of it is running in the live deployment today.
Built into the engagement rather than shipped in the box: the AI layer, multi-tenancy, custom fields and templates, working capital and overdraft products, group lending, collections and DPD bucketing, borrower-side transactions, and the external integrations. Those are scoped, quoted and delivered as part of a deployment, and they carry a build label wherever they appear on this site.
Yes, and it is the part of the work we take most seriously. We have rebuilt a multi-year loan with multiple disbursements and more than a dozen repayments from a legacy register and reconciled it against the board’s own figures using a documented procedure.
One honest caveat: where a legacy book was maintained under an interest convention that neither simple nor monthly-compound reproduces exactly, we surface the variance before cut-over and agree in writing whether to replicate the historical method or adopt the new one and adjust the residual. We would rather have that argument in week two than in year two.
Pricing is by portfolio size (active loans or assets under management) rather than per seat, because the lenders this is priced for have many loans and few operators. There are two shapes: a cloud subscription, and an enterprise engagement with one-time migration and setup.
We do not publish price points, and we will not quote a number before understanding your book. Anyone who quotes lending platform pricing off a web form is guessing.
DigiWagon Technologies holds ISO 9001 and ISO 27001, and GoDravix is built and supported under those certified management systems. We send both certificates with their scope statements on request.
SOC 2 is not held, and DPDP alignment has not been formally assessed. The security page sets out both the certifications and the remaining gaps.
See the platform on real data
A 45-minute walkthrough of the live deployment: the ledger, the audit trail and the reconciliation method, on real data.
45 minutes | On the live deployment | A straight answer on fit