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.
- Digital Wallet Platform
- Features
- Account applications
Account applications
Track provider-authorized account requests and their independent decisions.
OverviewAccount applications awaiting decision×
Digital Wallet Platform · Account applications
New
Account applications awaiting decision
Approval conditions
| Applicant | Parent | Organization | Status | Revision | Submitted at | |
|---|---|---|---|---|---|---|
| APP-251 | INS-65022 | ORG-3856 | Submitted | 890 | 27 Oct | |
| APP-162 | INS-92478 | ORG-1120 | Submitted | 790 | 21 Oct | |
| APP-948 | INS-51481 | ORG-5933 | Submitted | 90 | 11 Oct | |
| APP-299 | INS-61387 | ORG-2609 | Submitted | 680 | 12 Oct | |
| APP-406 | INS-98721 | ORG-8050 | Submitted | 860 | 26 Oct |
6 of 6 records
APP-251Account applications · AA-88117
SubmittedParentINS-65022
OrganizationORG-3856
Revision890
Submitted at27 Oct
Initial deposit USD240
What you can do
Keep account opening tied to authority
An account application connects a provider account request to a parent instruction and organization. It records the applicant, submitted date, initial deposit amount, revision, decision time and provider application identifier. The Operations Analyst can prepare the request and supporting material, then send the submitted revision for an independent decision.
The finance reviewer checks the applicant context and evidence before approving or rejecting. The review decision on the parent instruction retains the source revision and reason. Approval is an internal decision; the application reaches completed only when the provider has granted authority and the supporting evidence is retained with the parent instruction. This distinction helps the team find work that has passed review but still awaits the external result.
How the work is organized
- Draft. The analyst gathers applicant and instruction context.
- Decision. A submitted revision enters the reviewer queue.
- Provider follow-up. Approved applications remain visible until provider completion.
What to agree during setup
Agree what evidence is sufficient for an application, who is responsible for the provider handoff and how the provider application identifier will be entered. Keep the organization of the application aligned with its parent instruction. Define the reviewer independence check and what counts as a changed revision. The record includes an initial deposit amount, so the team should agree how that amount relates to the provider account request and its supporting instruction.
Administrators maintain the organization and member scope, but financial decisions stay with the independent reviewer. Auditors need read access to the decision and provider result. A rejected application retains its reason and can be distinguished from an approved request waiting on the provider.
Check the handoff on an actual case
An analyst prepares an application for a provider-held account connected to an instruction. They identify the organization and applicant, record the initial deposit amount and attach supporting material to the instruction. The reviewer checks the submitted revision and approves with a reason. The analyst records the provider application identifier when the request is sent. The application remains approved until the provider has granted the account authority, when it can become completed.
For the exception rehearsal, submit an application whose parent belongs to another organization or whose supporting evidence changed after review. The decision should stop and the team should see the mismatch before any completed status appears. Keep the prior decision row even when a corrected revision is reviewed later.
What your team sees
- Account applications awaiting decision — Submitted revisions requiring independent review.
- Account application workboard — Applications from draft through provider follow-up.
- Provider accounts — Active provider-held accounts available for future instruction scope.
Follow the work through
What it keeps track of
Data model- Account applications
- Applications to open a provider-authorized account against an instruction.
- Instructions
- Typed instructions moving through authorization, submission and confirmation.
- Review decisions
- Independent approver decisions recorded against a frozen instruction revision.
- Record attachments
- Supporting documents attached to an instruction.
- Organizations
- Organizations whose operational work is run in this app.
- Financial accounts
- Provider-held financial accounts owned by a counterparty.
Who uses it
Permissions- Operations Analyst
- Prepares applications and provider follow-up.
- Independent Finance Reviewer
- Approves or rejects submitted revisions.
- App Administrator
- Maintains organizational access.
- Auditor
- Reads the final evidence.
Set up Digital Wallet Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.