Account applications

An account application belongs to an organization and a parent banking instruction. The Treasury Preparer records the applicant and any initial amount, then submits a frozen revision for review. The application status separates a draft request from a submitted one, an approved or rejected decision, and provider-completed work. The provider application identifier connects the local request with the provider’s own processing.

The Independent Treasury Approver checks the submitted revision and its supporting evidence through the guarded account-opening action. The decision is recorded against the parent instruction and submitted application revision before the application outcome changes. Approval by itself does not mean the provider opened an account. The preparer follows the provider response and marks completion only when provider authority has actually been observed. This sequence matters when a provider takes longer than the internal review or rejects a request that was internally approved.

• Request. The preparer records an application against the relevant banking instruction and organization.
• Independent decision. The approver examines a frozen revision, records a reason and decides whether it may proceed.
• Provider authority. The team records the provider identifier and completed outcome only after the provider confirms it.

Decide what supporting document an approver needs for a particular account-opening request, and who receives the provider’s final response. Keep the application’s organization aligned with the parent instruction. Choose a stable reference to the provider application so a follow-up message can be attached to the same request. If a request needs correction, preserve the earlier decision and submit the corrected revision for a new review. Do not let an administrator’s membership rights substitute for an independent decision.

Consider a new settlement account requested to support an existing provider instruction. The preparer enters the applicant, organization and intended initial amount, then attaches the authorizing material to the parent instruction. The approver verifies the exact revision and records approval with a reason. The provider later returns its own application identifier, but completion waits for an actual provider-authorized outcome. A delay stays visible to the operations team instead of being hidden by the internal approval.

Rehearse a submitted application with a real parent instruction and evidence. Attempt a self approval and an outdated revision; both should be rejected by the guarded action. Verify that a review decision exists before the approved or rejected status is stored. Then simulate a provider response arriving after approval and check that the completed status has a corresponding provider reference. Repeat the request with the same operation key and confirm it does not create a duplicate decision or account-opening effect.

• Submitted Account Applications — Review applications waiting for an independent decision.
• Account Application Outcomes — Follow approved, rejected and completed requests by parent instruction.

Read account opening and completion verification.