Access consents

An access consent belongs to a bank instruction and an organization. It carries a revision and status, with a provider, decision time, grant time, account count and provider application identifier available for the authority trail. The Treasury Preparer can prepare an access request for the relevant instruction. The Independent Treasury Approver makes the separate decision on the submitted revision, and provider activation establishes when access has actually been granted.

Consent approval and live provider access are separate moments. The team should keep the request in its review path until an independent decision is recorded. A completed consent reflects a provider grant, with its grant date and provider details available to check against the accounts the provider made accessible.

• Request. The consent links the request to its parent instruction and organization.
• Review. Its revision and decision date frame the independent decision.
• Activation. Provider, application identifier, grant date and account count describe the resulting authority.

Decide which instructions need bank-data access and which provider application represents the organization. Define who collects supporting evidence for a consent and who checks its relationship to the parent instruction. Agree which independent approver can decide a submitted request and how a rejected consent returns for correction. The provider connection needs an agreed way to report an actual grant before the team calls access complete.

Set a routine for checking provider and account details once a grant appears. The account count can help spot a mismatch between the intended access scope and what the provider returned, but the count alone is not a substitute for examining the actual provider authority.

A preparer opens a consent for a bank instruction that needs provider account data. The preparer identifies the organization and provider, then submits the current revision. The Independent Treasury Approver checks the parent instruction and evidence, records a decision and its reason, and leaves a rejected request visible if the scope is wrong. When the provider later activates the grant, the team records when it happened, the provider application identifier and the resulting account count. An Auditor can then follow the request, decision and grant as distinct events tied to the same banking work.

• Submitted Consents — Requests waiting for the independent access decision.
• Consent Status — Draft, reviewed and completed requests with provider details.
• Instructions by Status — The parent instruction and its operating context.

Follow consent activation and provider connections for the access handoff.