1. Bank + Lending + Insurance
  2. Features
  3. Evidence and reconciliation
Feature · Evidence and reconciliation

Evidence and reconciliation

Connect each operational result to the application revision and persisted effect.

OverviewOperations Needing Review
Bank + Lending + Insurance · Evidence and reconciliation

Operations Needing Review

Operation receipts

New
Receipt numberOperationParentExpected revisionResult stateFailure reason
OR-26087Application SubmittedLA-56846520PendingCut to length
OR-50553Evidence VerifiedLA-46847150FailedWeld frame
OR-35358Review Decision RecordedLA-93657740Needs reviewDrill and tap
OR-21717Application ApprovedLA-50631920PendingDeburr
OR-57192Account BookedLA-18685300FailedAssemble
6 of 6 records
Cut to lengthOperation receipts · OR-26087
Application Submitted
ParentLA-56846
Expected revision520
Result statePending
Performed at16 Oct
Effect referencesER-305
Example screen with sample data

What you can do

Close the operation with evidence

A successful request should leave an effect the team can inspect. Operation receipts retain the action, expected revision and result, together with external and local effect references. The reconciliation workflow reads those receipts and checks the persisted effects before marking completion. When the expected effect cannot be confirmed, the receipt remains available for investigation with a Needs review result.

Independent Credit Approver follows exceptions to their cause. Auditor reads the authorized evidence without becoming an operator. Credit Officer can use the receipt to understand whether preparation or an eligible action needs attention. Operations Overview brings the authorized lending position and exceptions into the working discussion, while individual receipts preserve the detail behind a result.

How the work is organized

  • Application evidence. Keep document type, verification state and reviewer note with the application reference. Preserve the evidence revision and provider reference where available. The reviewer should be able to identify the material that supported a decision.
  • Action receipts. Retain the stable operation identity with its expected revision and effect references. Keep failed attempts visible. A later successful action should remain distinguishable from the failure that prompted investigation.
  • Read-first reconciliation. Compare the recorded result with persisted local effects before making another attempt. Completed means the expected effect was confirmed. Needs review identifies an unresolved discrepancy for an accountable person to examine.

What to agree during setup

Agree who investigates each exception and what evidence closes it. A disbursement issue may require a provider event, while an allocation issue requires the repayment and schedule references. Record the distinction between the operation outcome and the reconciliation result. A Succeeded outcome still needs a confirmed effect before the team treats reconciliation as complete.

Set attachment visibility rules and rehearse access with actual role accounts. Decide which files may be Shared and which remain Internal. Align review responsibility with the organization and application assignment. The person investigating an exception needs enough authorized evidence to explain it, without receiving access to unrelated borrowers or another organization’s lending work.

Check the handoff on an actual case

Take a disbursement request whose provider response arrived after an initial timeout. Independent Credit Approver opens the operation receipt, follows the external reference and compares the local disbursement with the expected effect. Once the identities and recorded amount agree, reconciliation can mark the result Completed. The earlier uncertainty remains understandable in the retained operational history.

Repeat with a receipt that names an effect which cannot be found. Reconciliation should return Needs review and leave the discrepancy open. Credit Officer supplies the relevant application or provider reference for investigation. Rehearse a cancellation of an unexecuted draft separately from a funded case: retain the original application and successor evidence rather than erasing an accepted or executed obligation.

Before ending the exercise, ask Auditor to trace an application approval through the receipt to its decision evidence. Then repeat with an account outside that auditor’s permitted scope. The operational trace and the access boundary must both hold before the team relies on the overview for daily work.

What your team sees

  • Operations Needing Review — Investigate pending, failed and unresolved results using their effect references.
  • Pending Application Evidence — Follow documents awaiting verification before relying on them in a decision.

Follow the work through

Follow funding and reconciliation for effect checks and repayment and servicing for allocation and correction evidence.

What it keeps track of

Data model
Operation receipts
Evidence ledger of operations performed against lending records, with outcome.
Application evidence
Supporting documents and evidence collected for an application.
Record attachments
Files attached to a loan application with visibility and evidence type.
Review decisions
Independent credit review decisions recorded against an application.
Loan applications
Loan applications submitted by borrowers, with requested amount and lifecycle status.
Bundled applications
Bundled lending and insurance applications reviewed together for one parent loan application.

Who uses it

Permissions
Independent Credit Approver
Investigates review and reconciliation evidence.
Credit Officer
Resolves assigned preparation issues.
Auditor
Examines authorized records.
App Administrator
Maintains organization membership; Admin supports technical access configuration.

Set up Bank + Lending + Insurance your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started