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.
- Branch Operations
- Features
- Vault transfers
Vault transfers
Follow a transfer from the first request through confirmed provider effect.
OverviewConfirmed transfers×
Branch Operations · Vault transfers
New
Confirmed transfers
Vault transfers
| Record number | Subject | Confirmed at | Amount USD | Provider instruction ID | Party | |
|---|---|---|---|---|---|---|
| VT-70352 | Confirmed vt-605 | 17 Oct | 390 | PII-934 | PRT-8503 | |
| VT-98641 | Confirmed vt-243 | 13 Oct | 760 | PII-603 | PRT-2667 | |
| VT-13779 | Confirmed vt-865 | 12 Oct | 460 | PII-847 | PRT-3320 | |
| VT-55956 | Confirmed vt-727 | 05 Oct | 860 | PII-277 | PRT-6901 | |
| VT-70511 | Confirmed vt-214 | 27 Oct | 730 | PII-297 | PRT-9350 |
6 of 6 records
Confirmed vt-605Vault transfers · VT-70352
Confirmed at17 Oct
Amount USD390
Provider instruction IDPII-934
PartyPRT-8503
What you can do
Keep one transfer record through the decision
A Case Analyst opens the transfer with a record number, subject, organization, owner, party and requested amount. That record remains the point of reference as the team adds account scope, supporting documents, an independent decision and provider evidence. A reviewer can see which revision was presented for approval instead of relying on a separate email or a later edit. The Business Overview gives the team a place to start with recorded exceptions, while the transfer record holds the details behind each one.
The status makes the work visible. Draft means the Case Analyst is still preparing the request. Review brings it to a Credit Reviewer. Authorized records the decision to proceed; Submitted and Pending distinguish an instruction from a confirmed effect. Confirmed needs provider evidence. Rejected closes a request that did not pass review. When a transfer has a provider instruction identifier, keep it with the same record so a later inquiry reaches the original request.
How the work is organized
- Request. Capture the amount, requested date, value date when known, organization, owner and settlement party.
- Decision. Tie the Credit Reviewer’s decision and reason to the transfer revision under review.
- Outcome. Keep instruction, confirmation evidence and receipt references beside the transfer they concern.
What to agree during setup
Agree who creates a draft, who checks the debit and credit accounts, and when a draft is ready for Review. A Credit Reviewer needs an independent path to examine it. Decide how the team will identify a provider instruction, and which confirmation or settlement record is sufficient to mark the transfer Confirmed. Define the organization’s time zone before users interpret requested and confirmation dates across branches.
Also agree who handles a rejected request. The record should preserve its reason and revision; a new proposal can be prepared with the appropriate change history. An administrator maintains organization and membership details but does not inherit the reviewer’s decision authority simply through administration.
Check the handoff on an actual case
Take a draft for a transfer between two provider-held accounts. Confirm that its debit and credit amounts balance the request, its party belongs to the intended organization, and its attachment names the supporting document. Have a different Credit Reviewer examine the revision. Their decision should point back to the transfer and say why they approved or rejected it. For an approved case, follow the provider instruction identifier into the confirmation evidence before treating the transfer as complete. Then ask an Auditor to trace the same case in reverse, from confirmed amount to decision and original request.
What your team sees
- Transfers in progress — Requests that still need preparation, review, provider submission or confirmation.
- Transfer review inbox — Revision and amount beside the request waiting for a Credit Reviewer.
- Confirmed transfers — Provider identifiers and confirmation dates for completed effects.
Follow the work through
Follow transfer authorization and provider outcome. Use the data model to check the related records.
What it keeps track of
Data model- Vault transfers
- Recorded vault transfers moving through authorization, submission and confirmation.
- Transfer accounts
- Debit and credit account scopes that make a vault transfer balanced.
- Credit decisions
- Independent approver decisions recorded against a frozen transfer revision.
- Assessment evidence
- Provider statements, confirmations, settlement notices and corrections for a vault transfer.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
- Record attachments
- Supporting documents attached to a vault transfer.
Who uses it
Permissions- Case Analyst
- , Credit Reviewer, Auditor and App Administrator.
- The analyst prepares the record, the reviewer decides on its revision, and the auditor traces the evidence.
Set up Branch Operations your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.