These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Neobank Backend
- Features
- Evidence and audit
Evidence and audit
Trace a treasury action from attachments through decisions, provider evidence and receipts.
OverviewVerified Provider Evidence×
Neobank Backend · Evidence and audit
New
Verified Provider Evidence
Bank evidence
| Provider event ID | Occurred at | Amount USD | Evidence type | Verified | Parent | |
|---|---|---|---|---|---|---|
| PEI-174 | 22 Oct | 510 | Statement | Yes | BI-88664 | |
| PEI-825 | 16 Oct | 590 | Confirmation | Yes | BI-43095 | |
| PEI-282 | 17 Oct | 300 | Settlement | Yes | BI-59489 | |
| PEI-986 | 10 Oct | 240 | Correction | Yes | BI-98225 | |
| PEI-387 | 04 Oct | 200 | Statement | Yes | BI-23327 |
6 of 6 records
PEI-174Bank evidence · BE-12585
StatementOccurred at22 Oct
Amount USD510
VerifiedYes
ParentBI-88664
What you can do
Run the work
An auditor follows an instruction from its supporting document to the reviewer decision, provider confirmation and operation receipt. Each record has a parent or reference that preserves the case trail. The receipt distinguishes a claimed effect from a persisted effect that has been checked. An Auditor starts with the parent banking instruction and follows its attachment, review decision, bank evidence and operation receipt. The decision explains who approved a frozen revision and why. Bank evidence identifies the provider event and whether it was verified. The receipt describes an attempted operation and its recorded effects; a receipt is complete only after those effects are found in persisted records.
How the work is organized
- Follow the parent. Use the instruction reference on attachments, decisions, evidence and receipts.
- Compare authority. Check the reviewer, source revision and decision reason against the instruction.
- Verify effects. Compare receipt effect references with persisted records before calling the operation complete.
What to agree during setup
Agree what attachments can be shared and which remain internal. Set retention and access practices for decision reasons and provider evidence. Give auditors read access to the assigned records while keeping write and execution actions with operational roles. Have the Auditor trace a completed instruction and a receipt needing review. Verify that the Auditor can read assigned evidence but cannot change a decision or execute an action. Agree who investigates missing effects.
Check the handoff on an actual case
Take a confirmed instruction and trace its attachment, approval decision, verified provider evidence and completed receipt. Rehearse a receipt whose expected effect is absent; it should require review with a concrete discrepancy rather than claiming completion. Ask the next person to find the parent case and explain its status from the linked records. If a receipt is unclear, compare its claimed effects with persisted records before closing the investigation. A correction event should remain beside the earlier provider event, rather than replacing it. Ask Auditor to explain which event supports the current instruction status and which receipt proves the operation effect.
What your team sees
- Verified Provider Evidence — Inspect the provider events supporting instruction outcomes.
- Receipts Needing Review — Find operations whose claimed effects require investigation.
Follow the work through
Trace instruction control for the decision and provider outcome for the external effect. Use roles to rehearse read access.
What it keeps track of
Data model- Record attachments
- Supporting documents attached to a banking instruction.
- Review decisions
- Independent approver decisions recorded against a frozen instruction revision.
- Bank evidence
- Provider statements, confirmations, settlement notices and corrections for an instruction.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
- Bank instructions
- Typed banking instructions moving through authorization, submission and confirmation.
Who uses it
Permissions- Auditor
- Traces the case.
- Treasury Preparer
- Assembles the operational records.
- Independent Treasury Approver
- Makes independent decisions.
- Auditor
- Reviews the resulting evidence in assigned scope.
- App Administrator
- Maintains organization membership and configuration.
Set up Neobank Backend your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.