How it works

Your loan book, bureau-ready in seven steps.

Bureaulens runs the complete cycle: load the book, record activity, accrue interest to the paisa, validate, generate every bureau file and reconcile. Each stage is set out below.

Step by step

From loan book to bureau-accepted, end to end.

Seven stages, from entity setup through filing all four bureaus to reconciling every figure — with no manual editing of submission files.

Set up your entity & bureau identities

Create your NBFC (or each entity in a group) and enter the member IDs, header user IDs, TL member codes and cycle IDs issued by each bureau. Nothing is hardcoded — every entity files under its own credentials, and a super-admin console oversees the group.

  • Member IDs for CIBIL, Experian, Equifax, CRIF
  • Per-entity isolation, one super-admin login
  • Configurable cycle ID and header identities

Load the loan book

Import parties, agreements and transactions from Excel, or enter them directly. Every borrower carries a PAN (format-checked and duplicate-blocked), constitution, addresses and directors; every agreement carries its segment, sanctioned limit, drawing power, asset classification and tranche schedule.

  • Excel import with row-level validation
  • ICDs, debentures (OCD/CCD/NCD) and consumer loans
  • Tranche-level — each drawdown at its own date and rate

Record activity as it happens

Post drawdowns and repayments through the year. Sanctioned limits are enforced at entry — a drawdown that would breach the limit is rejected with the exact headroom; over-repayments warn. Loans close with full history retained, and reopen if needed.

  • Sanctioned-limit checks on every drawdown
  • Duplicate PAN and account-number blocking
  • Closures retain history; cycle-aware for filing

Interest accrues to the paisa

An actual/365 engine accrues interest per tranche at each tranche's own rate. When a loan turns NPA, income recognition stops on the classified date — interest earned before that date is preserved, nothing after is accrued. Monthly and FYTD figures reconcile with your audited workbook exactly.

  • Actual/365, per-tranche rates
  • NPA stops accrual from the classified date
  • Monthly interest book ties to the workbook

Validate before you file

Run the pre-filing check for the cycle. Missing PANs, addresses, classifications and date inconsistencies are listed as errors and warnings on screen, so they are corrected before submission rather than after a bureau rejection.

  • Errors vs warnings, per borrower and account
  • Catches what bureaus reject
  • Cycle-aware inclusion of closures and NPAs

Generate & submit

One click produces a single ZIP per cycle: commercial UCRF V3.10 pipe-files, consumer TUDF V3.74 files, consumer data-submission workbooks built from the bureau's own template package, and a full UCRF preparation workbook — one set per bureau, named and formatted to spec, byte-faithful to previously accepted submissions.

  • UCRF txt + TUDF + Excel, all four bureaus
  • Weekly incremental (W1/W2/W3) and month-end full
  • Reproduces historical cycles exactly as filed

Report & reconcile

Weekly book, monthly loan book, monthly interest book and outstanding-as-on — each exportable to Excel and reconcilable line-by-line with your workbook. A dashboard shows the position as on any date, with a full transaction audit trail behind every figure.

  • Four reports, all Excel-exportable
  • As-on-date dashboard (month or FY)
  • Every transaction and user audited
How it works

Four stages to a filed cycle

Load the book once, then run each reporting cycle as a repeatable process with validation before submission.

  1. Load the book

    Import parties, agreements and transactions from Excel, or enter them directly.

  2. Record as you go

    Drawdowns, repayments, closures — validated against limits at entry.

  3. Validate the cycle

    Pre-filing checks confirm every borrower and account is bureau-complete.

  4. Generate & submit

    One ZIP: txt, TUDF and Excel for all four bureaus, named and formatted to spec.

By the numbers

By the numbers

The operating parameters Bureaulens is built to hold on every reporting cycle.

0
Bureaus Covered
0
RBI Cycles a Year
0
Day-Count Basis
0
Manual File Edits
FAQ

Frequently asked questions

Which bureau file formats does Bureaulens generate?
Commercial UCRF V3.10 pipe-delimited text files, consumer TUDF V3.74 files, consumer data-submission workbooks generated from each bureau's own template package, and a full UCRF preparation workbook (HD/BS/AS/RS/CR/GS/SS/CD/TS sheets) — one set per member ID for TransUnion CIBIL, Experian, Equifax and CRIF High Mark, packaged as a single ZIP per cycle.
How accurate is the interest engine?
Actual/365 with inclusive day-count, applied per tranche at each tranche's own rate. NPA accounts accrue nil, matching standard income-recognition practice. Customers reconcile it against audited workbooks to the paisa.
Can we import our existing loan book from Excel?
Yes. Parties, agreements and transactions import from Excel templates with row-level validation — duplicates are blocked, limit breaches are skipped with reasons, and nothing silently changes.
How are bureau member IDs and headers managed?
Every member ID, short name, TUDF header user, TL member code and cycle ID is configurable per bureau in Settings. Nothing is hardcoded — each entity files under its own identities.
Does it support multiple NBFCs in one group?
Yes. Bureaulens is multi-tenant: each entity's parties, loans, transactions and bureau settings are fully isolated, with a super-admin console for subscriptions across the group.
What about closures, NPAs and historical cycles?
Loans close with full history retained. Filing generation is cycle-aware: a loan live on the cycle date appears in that cycle even if closed later, so historical regeneration always matches what was actually filed.

Request a demonstration

A 30-minute walkthrough on your own data — your agreements, your reporting cycle and your bureau member IDs.

Request a demo See how it works