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.
- BNPL (Buy Now Pay Later)
- Features
- Evidence and receipts
Evidence and receipts
Keep provider proof and operation outcomes attached to the instruction.
OverviewUnverified Provider Evidence×
BNPL (Buy Now Pay Later) · Evidence and receipts
New
Unverified Provider Evidence
Assessment evidence
| Application | Evidence type | Provider event ID | Occurred at | Amount USD | |
|---|---|---|---|---|---|
| APP-32829 | Statement | PEI-663 | 18 Oct | 410 | |
| APP-54409 | Confirmation | PEI-904 | 07 Oct | 570 | |
| APP-62784 | Settlement | PEI-952 | 07 Oct | 480 | |
| APP-21150 | Correction | PEI-256 | 09 Oct | 670 | |
| APP-64860 | Statement | PEI-626 | 14 Oct | 560 |
6 of 6 records
PEI-663Assessment evidence · AE-70309
StatementApplicationAPP-32829
Occurred at18 Oct
Amount USD410
What you can do
Evidence and receipts in daily work
The team needs evidence for what a provider actually did. Each evidence line records its number, instruction revision, provider event ID, occurrence date, amount, type and verification result. A statement, confirmation, settlement notice or correction can be kept with the same instruction. Supporting files retain a title, upload time, visibility and uploader.
An operation receipt describes an attempted action under a stable operation key. It includes the expected revision, result state, occurrence time, external reference and effect references. When a receipt says needs review, a credit reviewer can inspect the discrepancy instead of assuming a repeat action is safe. Before treating a receipt as completed, the team checks the recorded local effects.
For a provider funding instruction, a submitted request, a provider confirmation and a settlement notice are separate facts. The finance officer records each as it arrives. The auditor can then trace the confirmed status to verified provider evidence, and trace an operation result to the instruction and the reference returned by the provider.
How the work is organized
- Keep source events. Finance Officer records each provider event with its type, date, amount and verification result.
- Keep supporting files. Attachments show their uploader and visibility alongside the instruction.
- Inspect uncertain actions. A receipt’s result and effect references give the reviewer a place to investigate.
What to agree during setup
Agree which provider documents count as confirmation or settlement proof. Define who verifies each evidence line and what to do with a correction from the provider. Keep the original event reference and the corrected event separate enough for the reviewer to understand the sequence.
Set attachment visibility rules for internal and shared files. Decide who investigates a receipt marked Failed or needs review, and what local effects must exist before it is marked Completed. The team should avoid resending a provider action simply because a local completion check is inconclusive.
Check the handoff on an actual case
Submit a reviewed instruction and record its provider instruction ID. Add a confirmation event with its provider event ID, date and amount. Verify the evidence, then confirm the instruction. Ask an auditor to locate the event and the finance officer who uploaded its supporting file.
Rehearse an ambiguous response as well. Create an operation receipt whose result needs review, inspect its external and effect references and keep the instruction’s current state until the claimed effect is verified. Add a provider correction and show that it can be examined without deleting the original evidence.
What your team sees
- Unverified Provider Evidence — Provider events awaiting verification against an instruction.
- Receipts Needing Review — Failed or disputed operation results requiring inspection.
Follow the work through
Follow the preparation or review steps and the provider handoff.
What it keeps track of
Data model- Assessment evidence
- Provider statements, confirmations, settlement notices and corrections for an instruction.
- Record attachments
- Supporting documents attached to a banking instruction.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
- Applications
- Typed applications moving through authorization, submission and confirmation.
Who uses it
Permissions- Finance Officer
- Prepares the case; Credit Reviewer examines the decision and provider evidence.
- Auditor
- Reads the resulting trail.
- App Administrator
- Maintains organizational access.
Set up BNPL (Buy Now Pay Later) your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.