Skip to main content
GullySystem

Loan Reports and Audit Trail

Reports show the loan book by product, branch and officer, and collection against demand for every collector. A log records who changed which record, and when.

Where the book stands

Disbursements and outstanding

By product, branch and officer, for the day, the month or the year so far. The figures read off live records and are not assembled by hand the night before a meeting.

Demand against collection

Due, received and the difference, per collector and per branch. The report goes into the regular meeting as it is.

Overdue ageing

Each bucket has the borrower list behind its figure. A number that can be opened is easier to act on than one taken on trust.

Commission on recoveries

Where you collect on a bank’s behalf, commission is worked out from receipts actually recorded. If the bank’s figure differs, yours is built from entries you can show.

SHG-wise outstanding

Group totals carry each member’s repayment history beneath them. Both come from the same entries, so the two agree.

The audit trail

The trail is rarely asked about at a demo and wanted by the second year.

  • Every change carrying the person who made it and the time
  • The old amount kept beside the new one on a corrected receipt
  • Approvals on sanction, settlement and write-off, with names against them
  • Access by role, so a collector sees a route and a branch head sees a branch
  • Entries exported for Tally when your accountant closes the month

What buyer guides say a lender should check in an audit log

Vendor guides and software review sites raise much the same few points. They make a fair checklist.

Who did what

The log should name the person who created, edited, approved or removed a record, not just the date.

Before and after

Ask whether the old value stays visible beside the new. A log that records only that something changed is hard to use.

Fee waivers and reversals

These are the entries an auditor questions first. Make sure they appear in the log and the month’s report.

Getting it out

An auditor will want the log as a file. Ask what format it comes in and who is allowed to export it.

Reports a lender’s board or auditor asks for

The names vary, but the questions repeat from one meeting to the next.

  • How much was lent this month, and against which products
  • How much was due, how much came in, and who is behind
  • Which accounts moved into a worse bucket since the last meeting
  • Which loans were settled or written off, and who approved them
  • What each branch and officer is carrying

Reports that sound useful and cost time

A report that nobody opens is clutter. Review your current registers first and mark each one as something the module should produce or something you can drop. The short list that remains is the one worth building well.

A reporting month, from desk to boardroom

Reports travel upward through a lender, from the officer to the manager to the board. Each reader needs a different cut of the same book. Everyone reads the same book.

The officer checks the portfolio

An officer opens the loans in the charge of that person, with balances and overdue amounts. A few accounts need calls. The list is short and personal. It guides the week’s work. Short lists get acted on.

The manager reads collections

The branch manager compares collection with demand for each collector. A shortfall is visible by name. A conversation follows with facts on the table. Praise and correction both rest on the same page. Both sides read one page.

The board asks for the book

Before a board meeting, the owner prints the book by product and branch. At this stage, the figures come from the same loans that staff handle daily. No separate summary has to be built by hand. Answers take a minute.

The auditor asks who changed a record

An auditor picks a loan and asks who changed the rate. The answer takes a minute. The office’s credibility rises because it needs no explanation. Nobody builds a summary by hand.

Decisions about reports before the first audit

Before the first audit or board meeting, a lender settles a few matters. They concern who sees which report, the pace of each run and what the log must show. Habits matter. Settle them early.

Who may open which report

Decide which reports are visible to officers, which to branch managers and which to owners only. Portfolio quality and collector performance are sensitive. Limit them on purpose. The rule is simple to explain. Review the choice each year.

The rhythm for running reports

Agree a rhythm, weekly for collections and monthly for the book. A fixed rhythm gives comparisons that mean something. Reports run only on a whim give figures nobody trusts. Frequency builds trust in figures. Keep the rhythm fixed.

What the audit log must show

Settle which changes are logged, such as rate edits, receipt reversals and waivers. Staff learn that these actions leave a trace. Changes made carefully hold up under questions. Gaps in the log are visible quickly.

Who reads the log

Choose who reviews the log and at what interval. Here, a log nobody reads protects little. A monthly look by a senior person keeps it useful. Questions are asked while memories are still fresh. Reviews stay timely.

Make an informed decision

Questions to settle before rollout.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

Loan Reports and Audit Trail

Does the schedule match the agreed terms and actual release of funds?

For “Loan Reports and Audit Trail”, use a sample already checked by your finance team. Compare due dates and the principal and interest split before relying on the resulting balance.

Background reading: Frappe Lending: repayment schedules

FAQ

Frequently asked questions

Can our auditor be given a login?

Yes, as a read-only role over the reports and the trail. It is not an audit certificate and does not replace the auditor’s work. It gives the auditor records with names and dates in place of a folder of printouts.

What if the report we need is not in your list?

It can be added. A short review of the current setup comes first. The registers and reports you keep by hand are reviewed, and each is marked as something the module should produce or not.

Who owns the loan data?

You do, and that is written down before work starts. The records belong to your organisation, and how the database reaches you if you stop using the module is agreed in the same document.

Does the audit trail show the old value after a correction?

Yes, on a corrected receipt. The old amount stays beside the new one, along with who changed it and when.

Can reports be limited to one branch?

Yes. Access follows the role and the branch assigned, and reports can be limited the same way, so a branch head reads only that branch.

Do the reports update during the day?

They read from the current records, so a receipt entered at noon is in the afternoon’s figures. There is no overnight job to wait for.

Can we export the loan book to Excel?

The figures behind a report can be exported for the accountant or the board. Confirm the exact columns you need during scoping so the sheet matches what you already file.

Where it fits

How this feature fits the system.

Loan Management System: the parts that work with this feature, the trades that use it and the ways to put it in place.

Enquiries and leads

Each loan enquiry is logged with its source and a follow-up date, and reports show which enquiries turned into applications.

Lead Management

Sanction approvals

Approval levels are set by loan amount or product, disbursement waits for the required sign-off, and the log records who approved and when.

Workflow and Approvals

Collection app for field agents

Field collectors record instalment receipts against the borrower from a phone browser, and due and received amounts appear together with collector name and date.

Receipts Management
Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements