All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. KYC / AML Platform
  2. Features
  3. Provider evidence
Feature · Provider evidence

Provider evidence

Keep provider confirmations, settlement notices and corrections with the instruction.

OverviewProvider evidence register
KYC / AML Platform · Provider evidence

Provider evidence register

Bank evidence

New
Line numberRevisionProvider event IDOccurred atAmount USDEvidence type
80330PEI-23106 Oct470Statement
480320PEI-54613 Oct540Confirmation
770340PEI-41403 Oct750Settlement
350670PEI-52713 Oct720Correction
640310PEI-37004 Oct880Statement
6 of 6 records
PEI-231Bank evidence · BE-67856
Statement
Line number80
Revision330
Occurred at06 Oct
Amount USD470
VerifiedYes
Example screen with sample data

What you can do

Let provider evidence establish the external result

An authorized instruction can be submitted to a bank or other provider, but submission alone does not settle the question of what happened. The team records the provider’s instruction identifier, then follows the returned statement, confirmation, settlement notice or correction. Each evidence record stays with the parent instruction and carries its own provider event reference when one is supplied. The verification value tells reviewers whether the event has been checked.

For example, an instruction may be sent in the morning and remain pending until a settlement notice arrives. The Operations Analyst can locate the provider reference while the Independent Finance Reviewer checks the amount and timing on the evidence. The instruction reaches confirmed only when verified confirmation or settlement evidence supports that state. A later correction remains in the evidence history rather than replacing the original event.

How the work is organized

  • Submission reference. The instruction holds the identifier returned by the provider.
  • Event sequence. Evidence rows retain line number, revision, event type, date, amount and verification state.
  • Result record. The instruction keeps its confirmed date after the provider effect has been established.

Statements and confirmations play different roles. A statement may help reconcile the account; a confirmation or settlement notice can establish the result of a specific instruction when verified. Keep the event identifier and parent link intact so a reviewer can distinguish one external event from a duplicate notification.

What to agree during setup

Agree which provider messages can establish confirmation, who checks them, and where the provider event identifier is recorded. Decide how to handle a response whose amount or occurrence date differs from the instruction. The reviewer should retain the discrepant evidence and investigate it with reconciliation items instead of changing the instruction into a successful result by assumption.

Confirm how corrections are labeled and how they connect to the original instruction. If a bank sends an amended statement, retain both records in a way that makes the sequence understandable. The provider connection should supply the external identifiers and event content; the internal instruction status should follow verified evidence.

Check the handoff on an actual case

Submit an authorized instruction and record its provider identifier. Leave it pending while no verified confirmation is present. Add a confirmation with the expected amount and check it before setting the confirmed state and date. Then introduce a second event with a different amount. The reviewer should see the discrepancy and the evidence trail, while the later reconciliation remains open for investigation. Check that a correction does not erase the original confirmation.

What your team sees

  • Provider evidence register — Review evidence type, provider event, amount and verification for each instruction.
  • Confirmed instructions — Inspect instructions supported by a recorded confirmation date.
  • Operations needing review — Find actions whose claimed result still needs verification.

Follow the work through

See provider confirmation and account reconciliation for the provider-to-ledger handoff.

What it keeps track of

Data model
Bank evidence
Provider statements, confirmations, settlement notices and corrections for an instruction.
Bank instructions
Typed banking instructions moving through authorization, submission and confirmation.
Operation receipts
Idempotent operation receipts with stable operation keys and actual effect references.
Reconciliation items
Source-identified provider movements matched against banking instructions.
Financial accounts
Provider-held financial accounts owned by a counterparty.

Who uses it

Permissions
Operations Analyst
Tracks the provider handoff; Independent Finance Reviewer checks the evidence; Reconciliation Analyst investigates movement differences; Auditor reads the retained history.

Set up KYC / AML Platform your way.

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

How to get started