Disbursement and evidence

An approved loan application can be submitted for disbursement. The application stores the provider instruction ID and value date, while a disbursement row connects the application, loan account, direction and amount. These links let the team compare the requested principal with the provider effect associated with a particular account. Submission is a handoff to the provider. The confirmed status belongs to an effect supported by verified disbursement or settlement evidence, rather than merely a sent instruction.

Application evidence retains a provider event ID, evidence type, received date, amount and verification value. A confirmation or settlement notice can be examined alongside the instruction and disbursement row. Corrections remain part of the case history. Operation receipts hold an operation key, expected revision, result state and effect references, so the team can tell whether an attempted action reached the provider and which local records were affected. A pending or review-needed receipt deserves investigation before anyone retries an instruction.

• Approved case. Credit authority is visible before the officer prepares the provider instruction.
• Provider identity. The instruction ID and event ID tie the request to provider responses.
• Verified effect. Evidence and disbursement records support the confirmed application state.

Agree which provider supplies instructions, disbursement events and settlement notices. Document how its external account ID maps to the loan account and how its event IDs are retained. Decide who verifies an evidence row and which source confirms actual movement of funds. Establish how a delayed provider response appears in the work queue and who investigates it. The Credit Officer needs a clear handoff to the provider contact, while the Independent Credit Approver needs a way to inspect the effect associated with the approved revision.

Use an approved pilot case with a known borrower and account. Submit its instruction once and record the provider identity. A second equivalent submission should be recognized by the stable operation key, not treated as new money movement. Test a delayed response: the application remains submitted or pending while the team waits for verified evidence. Then attach the provider event and confirm that the disbursement belongs to the same application and account before moving the case to confirmed.

An approved request for a stated principal is sent to the lending provider. The Credit Officer records the instruction ID and watches the provider response. A receipt appears, but the external event has not yet been verified. The officer leaves the case in its waiting state and asks for the provider event ID. When a verified settlement notice arrives, the team compares its amount and account with the disbursement record. Only then is confirmation appropriate. If the provider reports a different account or amount, the receipt becomes an investigation item with the discrepancy recorded.

The Auditor can trace the approved decision, submitted instruction, evidence row and effect references without relying on a verbal account of what happened. Corrections to an authorized case preserve verified evidence and earlier decisions, so the history still explains the provider outcome.

• Awaiting provider confirmation — Submitted and pending cases with their instruction identities.
• Verified application evidence — Source events checked against the case.
• Open operation exceptions — Attempts whose effects need investigation.

See disbursement confirmation and repayment servicing for the account handoff.