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.
- Microfinance / SHG Management
- Features
- Provider submission
Provider submission
Follow an approved instruction through provider reference, confirmation and settlement evidence.
OverviewConfirmed Instructions×
Microfinance / SHG Management · Provider submission
New
Confirmed Instructions
Loan applications
| Record number | Subject | Counterparty | Requested principal USD | Provider instruction ID | |
|---|---|---|---|---|---|
| LA-41355 | Confirmed la-116 | BRR-4189 | 760 | PII-486 | |
| LA-12311 | Confirmed la-655 | BRR-9777 | 80 | PII-946 | |
| LA-95280 | Confirmed la-608 | BRR-5870 | 730 | PII-781 | |
| LA-58259 | Confirmed la-610 | BRR-9304 | 690 | PII-448 | |
| LA-82934 | Confirmed la-385 | BRR-8953 | 490 | PII-728 |
6 of 6 records
Confirmed la-116Loan applications · LA-41355
CounterpartyBRR-4189
Requested principal USD760
Provider instruction IDPII-486
What you can do
Provider submission in daily work
Follow an approved instruction through provider reference, confirmation and settlement evidence. The record stays with the organization that owns the work. Each handoff has a named owner and a source record that the next person can inspect. This makes the decision and its provider outcome traceable to the same instruction.
How the work is organized
- Prepare. Record the operating context and source references before changing the status.
- Decide. Use the appropriate role to check the current revision and supporting evidence.
- Verify. Compare the recorded outcome with the provider event and retain exceptions.
Loan applications separates Approved, Submitted, Pending and Confirmed statuses. Provider instruction ID records the provider reference. Application evidence holds statements, confirmations, settlements and corrections, with a verification value and received date. A submitted instruction should not be treated as confirmed merely because the provider accepted a request. The team checks the relevant evidence and account scope before recognizing the outcome. Operation receipts connects an attempted action with its actual effect references.
What to agree during setup
Agree which organization owns each account and counterparty, who may prepare an instruction and who may independently decide it. Define where provider references, confirmations and balance snapshots arrive. Give each person the minimum scope needed for their role, including what may be shared in attachments. Choose one real account movement for the first rehearsal and retain its provider source identifiers.
The team should also agree when a returned record needs a fresh revision. Provider events can arrive after an internal action, so an operational status should reflect the observed event. Keep the timing and reason for correction on the related record. This helps the next shift understand why an item is still waiting.
Check the handoff on an actual case
For an approved account movement, Credit Officer sends the instruction and records the provider reference. A provider acknowledgment leaves the item awaiting its final outcome. When a settlement notice arrives, Treasury Reconciler compares the reference, amount and parent instruction, then records verification. The confirmed state belongs to the verified result. A duplicate notice remains part of the evidence trail without creating a second financial effect. Walk through the case with the preparer, reviewer and reconciler together. Ask each person to point to the record they used and the event that made the next state valid. Check the same case in an ordinary screen and in the exception list, then verify that an unauthorized actor cannot make the decision.
What your team sees
- Awaiting Provider Outcome — Follow the records that need the module’s next action.
- Confirmed Instructions — Check the subsequent state against its source information.
Follow the work through
See the related process and the data model for the record handoff.
What it keeps track of
Data model- Loan applications
- Typed banking instructions moving through authorization, submission and confirmation.
- Application evidence
- Provider statements, confirmations, settlement notices and corrections for an instruction.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
- Disbursements
- Debit and credit account scopes that make an instruction balanced.
- Loan accounts
- Provider-held financial accounts owned by a counterparty.
Who uses it
Permissions- Credit Officer
- Follows submission.
- Treasury Reconciler
- Checks provider evidence.
- Independent Credit Approver
- Retains decision authority over the revision.
Set up Microfinance / SHG Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.