Skip to content
Lenviq
Request a demo

About

A lending system written by people who have had to defend the numbers.

We are FastLegal Technologies Private Limited, and we have been building compliance software for Indian regulated entities since 2018. Lenviq is that work applied to NBFC lending — which is why the compliance pages carry citations rather than adjectives, and why the ledger is a real double-entry ledger rather than a reporting table.

Why it exists

The gaps this was built into

Six things that go wrong in lending software often enough to be worth naming. Each one is a position this product took early, and each has a piece behind it working the reasoning through.

Compliance treated as reporting

Most lending software computes what it likes and assembles a compliance view at quarter-end. That works until a position has to be defended, at which point the number in the return and the number in the ledger are two different numbers — and no one can say which is right.

Books kept somewhere else

A loan system that hands a summary to an accounting package leaves the reconciliation to a person, every month, forever. Here the posting is the loan event: a disbursement writes its own double entry, so there is nothing to tie back.

An NPA number that changes with the time of day

Classification asks what position the book stood in at the close of a named day. A system that recomputes it on demand answers a different question each time it is asked, and the figure in a board pack stops matching the one filed a week earlier.

A loan that reads its terms from today's master

Reprice a scheme and every loan ever sanctioned on it silently reprices with it. A loan should carry a copy of what it was sanctioned on — the rate band, the appropriation order, the charges — so the agreement in the borrower’s hand and the account in the system say the same thing.

A code path per product

When a product is written into the software rather than configured in it, every new scheme is a release, and the gold book and the vehicle book slowly diverge on rules that were meant to be identical. Products here are data; behaviour binds to the asset class, not to a name.

Corrections made by editing

A wrong posting fixed in place leaves a record of the corrected state and no record of the correction. Financial entries here are never updated or deleted — a mistake is reversed, and both the error and the reversal stand in the ledger where an auditor can see them.

What else we build

Compliance software for Indian regulated entities, since 2018

Every one of these exists because a rulebook makes something hard to get right by hand. Lenviq is the same problem in NBFC lending, which is a larger one than the rest.

  • CoSecOffice

    Entity master, board process, compliance calendar and statutory drafting, for company secretaries in practice and in-house.

  • Cred

    Bank-ready project reports for MUDRA, PMEGP and PM Vishwakarma lending, with the DSCR and CMA workings behind them.

  • NidhiExpert

    Compliance for Nidhi companies.

  • Sanstha ERP

    Receipts, accounts and reporting for trusts, temples and other charitable institutions.