Independent review

The Independent Credit Approver reviews an application prepared by a Credit Officer. A review decision records its source revision, reviewer, time, reason and outcome. This prevents a later change to the application from quietly inheriting a decision made on an earlier amount or borrower. The approver’s decision can approve, reject or return the work for correction. A return gives the preparer a clear path to amend the request and present it again.

Supporting files and provider evidence belong to the application. A file has a title, upload time, visibility and evidence type. Provider events carry their own identifier, occurrence time, amount and verification result. The reviewer considers the appropriate evidence for the decision at hand and retains a reason that another person can understand months later. The Auditor can read the record trail without acquiring edit or execution authority.

• Decision inbox. Reviewed requests show the current amount, revision and owner, so the approver can identify whose work is being assessed.
• Evidence trail. Supporting attachments and event evidence remain linked to the application after a correction or provider response.
• Effect verification. An operation receipt carries a stable key and expected revision to explain what action was attempted and which effects were observed.

Define which documents an approver needs for a typical application and which are internal or shared. Decide how a return reason will be written and who can see it. Confirm the separation of preparer and approver in both the user assignment and the guarded decision path. Administrative access should maintain membership without becoming a route to approve one’s own request.

For provider events, agree who verifies the source identity and how a repeated event is recognized. The verification result is a factual assertion about the evidence, not an approval shortcut. A duplicate operation key should lead the team to the previous receipt and its effect references. When a receipt needs review, the approver should inspect the actual linked records before changing its result.

A Credit Officer submits a request at its current revision. The Independent Credit Approver opens the decision inbox, reads the amount, borrower and attachments, and checks that they were not the preparer. They record an approval with a reason. The decision names the revision they saw. If the officer later changes the amount, the old decision remains in the history; it cannot silently authorize the revised request.

After provider submission, a confirmation event arrives. The reviewer compares its source identity and amount with the application and the operation receipt. A verified effect can close the receipt. If the provider reference exists but the local effect is missing, the receipt needs review; the team investigates the discrepancy before retrying anything. The Auditor can follow this sequence without altering either the approval or the provider evidence.

• Application decision inbox — Requests awaiting an independent decision on a known revision.
• Receipts needing review — Attempted effects with pending, failed or discrepant results.
• Application status board — The request’s current decision and provider state at a glance.

Read application and credit review and provider submission. The roles page details access boundaries.