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
- Provider account links
Provider account links
Review provider account link applications against their parent instruction.
OverviewSubmitted Provider Links×
Neobank Backend · Provider account links
New
Submitted Provider Links
Approval conditions
| Status | Revision | Submitted at | Applicant | Provider application ID | Parent | |
|---|---|---|---|---|---|---|
| Submitted | 290 | 12 Oct | APP-796 | PAI-171 | BI-48273 | |
| Submitted | 280 | 12 Oct | APP-741 | PAI-945 | BI-88444 | |
| Submitted | 510 | 18 Oct | APP-352 | PAI-232 | BI-58198 | |
| Submitted | 180 | 17 Oct | APP-300 | PAI-360 | BI-27989 | |
| Submitted | 80 | 03 Oct | APP-379 | PAI-619 | BI-66440 |
6 of 6 records
APP-796Provider account links · PAL-33669
SubmittedRevision290
Submitted at12 Oct
Provider application IDPAI-171
ParentBI-48273
What you can do
Run the work
A treasury team records a provider account link under an existing banking instruction and organization. The applicant and provider application identifier give the team a concrete case to trace. A submitted link is reviewed against its frozen revision and supporting evidence before its outcome is recorded. A provider account link is recorded under a banking instruction and the same organization. Its applicant, submitted date and provider application identifier let the team follow the case. The independent reviewer checks the frozen submitted revision and supporting source evidence. The decision belongs to the parent instruction, and a completed link must have its required source record.
How the work is organized
- Scope the link. Check that the application and parent instruction belong to the same organization.
- Review the revision. Keep the submitted details and source evidence available to the independent reviewer.
- Record the outcome. Link the decision to the parent and verify the required source record before completion.
What to agree during setup
Agree who supplies the provider application identifier and what document or provider response supports the requested link. Keep the parent instruction and organization consistent. Decide what source event must be recorded before the link can be treated as completed. Give the reviewer the parent instruction, organization, application identifier and source evidence. Rehearse an application whose revision changes after submission. Agree which provider source record establishes completion.
Check the handoff on an actual case
Start with a submitted link whose parent instruction belongs to the same organization. Ask an independent reviewer to inspect the revision and source evidence. Record a decision and compare the decision time and status with the source event that supports 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. When an application is rejected, keep the submitted revision and decision reason available to the preparer. A later application should be reviewed on its own revision and source evidence.
What your team sees
- Submitted Provider Links — Find applications awaiting independent review and inspect their parent instruction.
- Provider Link Status Board — Follow applications through submitted, approved or rejected states.
Follow the work through
Use provider account review for the link decision. The data model shows how its parent instruction carries the review record.
What it keeps track of
Data model- Provider account links
- Domain-specific provider account links supporting reconcile provider account state.
- Bank instructions
- Typed banking instructions moving through authorization, submission and confirmation.
- Organizations
- Banking organizations whose treasury operations are run in this app.
- Review decisions
- Independent approver decisions recorded against a frozen instruction revision.
Who uses it
Permissions- Independent Treasury Approver
- Owns this decision.
- Treasury Preparer
- Assembles the case.
- 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.