Credit review

The Independent Credit Approver reviews the loan application as a specific revision. The decision record connects the parent case, source revision, reviewer, decision, date, reason and operation key. That combination matters when an officer later edits the case or an action is retried. A decision to approve, reject or return should have a clear reason that a Credit Officer can act on and an Auditor can read in context. The application status reflects the decision only after the decision row exists.

The reviewer checks organization scope and their independence from the person who prepared the application. A Credit Officer may prepare and submit a case, but should not approve that same submission. The App Administrator maintains membership and organizations without gaining decision authority. The Auditor reads the case and its evidence without editing the request or executing an approval. These separations keep the named decision attached to the person who made it.

• Review queue. Submitted work is filtered to the status the approver can assess.
• Frozen revision. The reviewer sees the application version and supporting records being decided.
• Decision record. Approval, rejection or return carries a reviewer, date and reason.

Agree what an adequate reason looks like for each decision and when a case should be returned for more evidence. Define who qualifies as independent for each organization, and test that an administrator cannot simply assign a reviewer entitlement that bypasses separation. Establish how a revised request reenters the queue. Decide how an officer learns of a returned decision and which attachments belong to the next revision. Keep prior decisions as history rather than editing them to match a later case.

For the first review, submit a complete request and have a different team member approve it. Inspect the decision row, its source revision and the resulting application status. Next, try a self-approval and a decision on an older revision. Both attempts should fail without changing the application or creating a misleading completed receipt. Finally, return a case with a specific reason, revise it, and inspect the new decision against the new revision.

A Credit Officer submits a borrower request with a supporting statement. The Independent Credit Approver finds it in the decision queue, checks borrower and organization scope, reads the attachment and statement evidence, and records an approval reason. The case can then move to the approved status. If the attachment is wrong, the approver returns the request and explains what must change. The officer adds the corrected file and submits a new revision. The earlier return remains linked to the old revision, while the next decision is separately attributed.

The operation receipt gives the team a stable key for an attempted action. If someone retries the same decision, the receipt and the decision history should make the result intelligible without adding a second decision. The credit team can investigate an exception by comparing the recorded effect references with the actual decision and application status.

• Credit decision queue — Applications ready for an independent decision.
• Approved applications — Approved cases waiting for the next operational handoff.
• Open operation exceptions — Decision attempts that need investigation.

See application review for the decision path and disbursement for the approved case handoff.