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.
- P2P Lending Platform
- Features
- Loan applications
Loan applications
Keep a requested loan, its owner and its provider outcome on one traceable record.
OverviewMy applications×
P2P Lending Platform · Loan applications
New
My applications
Loan applications
| Record number | Subject | Status | Requested at | Amount USD | Counterparty | |
|---|---|---|---|---|---|---|
| LA-16987 | Draft la-915 | Draft | 06 Oct | 320 | BRR-9280 | |
| LA-24567 | Review la-485 | Review | 07 Oct | 870 | BRR-8832 | |
| LA-31023 | Authorized la-453 | Authorized | 20 Oct | 450 | BRR-9296 | |
| LA-27786 | Submitted la-777 | Submitted | 27 Oct | 390 | BRR-5743 | |
| LA-90509 | Pending la-673 | Pending | 12 Oct | 690 | BRR-3347 |
6 of 6 records
Draft la-915Loan applications · LA-16987
DraftRequested at06 Oct
Amount USD320
CounterpartyBRR-9280
What you can do
Prepare a request for a real decision
The Credit Officer opens an application for a borrower in the appropriate organization. It records a request number, subject, requested date, amount and responsible team member. The application carries a revision, so the Independent Credit Approver can decide on the version actually presented. Supporting files stay with the request. The Operations Overview helps the team see recorded exceptions that need attention today.
An application can move from draft into review, then to an authorized or rejected result. Authorized work may be submitted to a provider. The provider instruction reference, value date and confirmation time distinguish the submitted request from the final provider outcome. An application marked submitted has not necessarily been confirmed. That distinction matters when a Credit Officer answers a borrower asking whether money moved.
How the work is organized
- Preparation. The Credit Officer checks borrower, organization, owner and requested amount before sending the current revision for review.
- Independent decision. The Independent Credit Approver records a reasoned decision tied to that revision, separate from the preparer’s edit access.
- Provider outcome. The team connects the provider instruction and verification evidence to the same request before treating it as confirmed.
What to agree during setup
Choose a request-number convention and decide when the officer moves a draft to review. Agree who can correct a returned application and how a new revision is identified. The approver must be separate from the person who prepared the work. Make the review reason useful to a future reader: a terse approval label does not explain a changed amount or a returned request.
Decide how the provider acknowledges an instruction and which evidence will count as confirmation or settlement. The application has space for the provider’s instruction identity and dates. The provider connection must supply the actual event; staff should not infer it from a local status change alone. Agree how rejected or failed submissions will be reviewed and how a correction will preserve prior decisions and evidence.
Check the handoff on an actual case
A Credit Officer receives a request from an existing borrower. They confirm the borrower code and organization, enter the amount, requested date and subject, and attach the source documents. The officer sends the current revision to review. The Independent Credit Approver checks the amount and borrower relationship, compares the attachments, and records a reasoned approval or rejection. If the amount changes after a return, the officer presents a new revision rather than relying on an earlier decision.
For an authorized request, the officer submits the instruction to the provider. The team records the provider reference and checks the returned confirmation evidence. A pending provider response stays visible. Once the effect is verified, the confirmed date and value date help the servicing team place the instruction alongside the account movement. A later correction keeps the decision and provider evidence available to the Auditor.
What your team sees
- My applications — Requests assigned to the Credit Officer, with their current status and borrower.
- Applications in review or pending — Requests awaiting a credit decision or a provider response.
- Confirmed applications — Provider-confirmed requests with reference and timing for servicing.
Follow the work through
See application and credit review, then provider submission. The roles page explains the decision boundary.
What it keeps track of
Data model- Loan applications
- Loan applications moving through recording, independent credit review and approval or decline.
- Borrowers
- Borrowers eligible for loan applications and lender funding commitments.
- Organizations
- Organizations whose lending and servicing operations are run in this app.
- Team members
- Credit officers, approvers, auditors and administrators working in the organization.
- Record attachments
- Supporting documents attached to a loan application.
- Application evidence
- Supporting evidence recorded against a loan application, with validity and verification.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
Who uses it
Permissions- Credit Officer
- Prepares the request and handles its authorized submission.
- Independent Credit Approver
- Decides the reviewed revision and checks the effect.
- App Administrator
- Maintains organization membership.
- Auditor
- Follows the application and evidence trail.
Set up P2P Lending Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.