# Banking & financial services use cases

> Connect customer reviews, lending decisions, and financial approvals to the evidence behind them.

Canonical page: https://www.truthlocks.com/industries/financial-services
Category: Finance & professional services

A bank needs to know which information a reviewer used and who approved the next step. Truthlocks adds signed records and a reviewable history around your existing banking processes.

## Retail banking: Keep customer-review evidence together

Onboarding teams receive different document versions through branches, portals, and email.

### What to record

Sign a review record containing document fingerprints, source references, reviewer identity, and the version of the checklist used. Keep sensitive originals in approved storage.

### What to review

Check the signed version and review outcome before moving the application forward. Request fresh evidence when a source or document changes.

### The outcome

A traceable handoff between onboarding reviewers and the team responsible for the account decision.

## Commercial lending: Follow a credit decision from submission to approval

An updated financial statement can become separated from the approval that relied on it.

### What to record

Link the submitted statement fingerprint, assessment reference, approved terms, and authorized reviewer to a signed decision record.

### What to review

Compare the documents presented at the next stage with those used during approval. Route differences back to the credit team.

### The outcome

A clear record of which evidence supported each lending decision.

## Treasury operations: Record the resolution of reconciliation exceptions

Unmatched entries are investigated across spreadsheets and messages, leaving the final explanation hard to find.

### What to record

Capture transaction references, the exception, supporting evidence, and the reviewer’s resolution through a configured finance workflow.

### What to review

Review the recorded explanation and approval history before an authorized system executes an adjustment or payment.

### The outcome

An exception history that finance and internal reviewers can inspect together.

## Before you begin

Start with one document-review workflow. Connect your approved source systems and keep identity checks, lending rules, and payment authorization with the responsible teams.

## Relevant capabilities

- [Digital records](https://www.truthlocks.com/product/attestation-service)
- [Finance workflows](https://www.truthlocks.com/product/finance-autopilot)
- [Governance](https://www.truthlocks.com/product/governance)

These are practical workflow examples, not certification claims or a record of customer deployments.