These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Micro-finance System
- Features
- Loan application preparation
Loan application preparation
Prepare a lending request with its borrower, owner, amount and supporting evidence.
OverviewMy Applications×
Micro-finance System · Loan application preparation
New
My Applications
Loan applications
| Record number | Subject | Status | Requested principal USD | Revision | Counterparty | |
|---|---|---|---|---|---|---|
| LA-71682 | Draft la-746 | Draft | 470 | 760 | BRR-7407 | |
| LA-31659 | Under Review la-798 | Under Review | 120 | 460 | BRR-9909 | |
| LA-20035 | Approved la-544 | Approved | 670 | 730 | BRR-4797 | |
| LA-14731 | Submitted la-266 | Submitted | 510 | 400 | BRR-6949 | |
| LA-25743 | Pending la-617 | Pending | 330 | 20 | BRR-1490 |
6 of 6 records
Draft la-746Loan applications · LA-71682
DraftRequested principal USD470
Revision760
CounterpartyBRR-7407
What you can do
Make the request reviewable
A Credit Officer prepares each lending request for one borrower and one organization. The application holds a record number, subject, requested principal, owner and revision. Those details should be clear before the request reaches the Independent Credit Approver. A subject that merely repeats the borrower name makes it harder to distinguish a correction from a new request; use it to explain the lending purpose in the team’s own words.
The owner links the request to a team member. Supporting attachments give the reviewer the documents behind the proposed principal, while application evidence can record provider event identity, amount, evidence type and verification. Keep an uploaded document and a verified provider event separate. A file’s presence tells the reviewer what was supplied; it does not itself establish that the provider confirmed an effect.
How the work is organized
- Draft ownership. The officer checks the organization, borrower and principal before sending the application for review.
- Evidence placement. Attach supporting files and associate evidence with the intended application revision.
- Revision control. Treat a material correction as a new review basis rather than silently changing what an approver saw.
What to agree during setup
Agree which documents a Credit Officer must attach for the common request types and who can see material marked internal or shared. Decide how record numbers are assigned when a borrower makes a second request. Agree what the subject must convey, and when an updated requested principal requires renewed independent review. The reviewer should be able to compare the current revision with the evidence and decision recorded for an earlier one.
The team also needs a convention for the submission and value dates. These dates serve different purposes: one identifies when the request went forward, while the other represents the value date used in the lending record. Confirm which provider event supplies the later outcome before the first live cycle. If an external service accepts the instruction, retain its instruction identity with the application.
Check the handoff on an actual case
A borrower asks for a different principal after the officer has already assembled an application. The Credit Officer updates the draft, checks the borrower and organization again, and attaches the revised supporting material. The Independent Credit Approver reviews that revision and records a reason with the decision. If an older decision exists, the new application revision remains distinguishable from the one the reviewer previously considered. The officer does not treat an uploaded document as a confirmed provider outcome.
What your team sees
- My Applications — Requests owned by the signed-in officer, with amount and review position.
- Applications Under Review — Submitted requests waiting for an independent decision.
Follow the work through
Use the application review path and provider outcome path.
What it keeps track of
Data model- Loan applications
- Loan applications moving through authorization, submission and confirmation.
- Borrowers
- Borrowers and their eligibility position, compared before a loan application is raised.
- Organizations
- Banking organizations whose treasury operations are run in this app.
- Team members
- Preparers, approvers, auditors and administrators working in the organization.
- Record attachments
- Supporting documents attached to a banking instruction.
- Application evidence
- Provider evidence supporting a loan application revision, with validity and verification.
Who uses it
Permissions- Credit Officer
- Prepares the request and evidence.
- Independent Credit Approver
- Decides on a reviewed revision.
- App Administrator
- Maintains membership and organization context.
- Auditor
- Reads the resulting record trail.
Set up Micro-finance System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.