1. Open Banking API Platform
  2. Features
  3. Organizations and counterparties
Feature · Organizations and counterparties

Organizations and counterparties

Keep organization membership and eligible bank relationships clear before an instruction starts.

OverviewActive Counterparties
Open Banking API Platform · Organizations and counterparties

Active Counterparties

Financial counterparties

New
NameCodeContact nameEligibility noteOrganization
Counterparty 369CDE-561Contact 359EN-541ORG-4849
Counterparty 114CDE-531Contact 110EN-348ORG-7238
Counterparty 215CDE-756Contact 595EN-313ORG-6305
Counterparty 302CDE-275Contact 521EN-423ORG-2510
Counterparty 257CDE-894Contact 988EN-593ORG-4907
6 of 6 records
Counterparty 369Financial counterparties · FC-19873
CodeCDE-561
Contact nameContact 359
Eligibility noteEN-541
OrganizationORG-4849
Example screen with sample data

What you can do

Establish the operating boundary

An instruction belongs to an organization. The App Administrator maintains its name, code, active state, time zone and currency, then associates the team members who prepare, review and audit its work. That boundary matters when an instruction changes hands: a person who can see one organization’s records should not gain a decision on another organization’s banking activity merely because the provider is shared.

The counterparty record holds the banks, custodians and settlement parties eligible for an instruction. The administrator records the counterparty’s contact, address and eligibility note. An active counterparty can be selected by the Treasury Preparer when the banking work is prepared. The note is a useful place to explain why a counterparty belongs in the operating scope, so the approver has context beyond a name.

How the work is organized

  • Organization ownership. Each bank instruction and counterparty refers to the organization whose treasury work it serves.
  • Membership. Team members connect a user to an organization and carry an active state and role name.
  • Eligibility. A counterparty has its own active state and note; it is not inferred from a financial account’s provider text.

What to agree during setup

Name the organization that owns each operating cycle and the administrator who maintains its membership. Agree how to identify a bank or custodian across internal records, and who is responsible for updating the eligibility note when the relationship changes. Set the organization’s time zone before using dated reviews and provider events as an audit sequence.

Also agree how an inactive team member or counterparty should be handled in work already under review. The record of an earlier decision remains part of the trail; changing eligibility for new instructions is a separate operational action. Reviewers should be able to recognize the person and counterparty that applied at the time of the decision.

Check the handoff on an actual case

A treasury team prepares a payment instruction for a custodian that serves one organization. The App Administrator first checks the custodian’s code, active state and eligibility note. The Treasury Preparer then chooses that counterparty on the new instruction and assigns a team member as owner. Before authorization, the Independent Treasury Approver checks that the chosen counterparty is the one intended for this organization and that the owner belongs to the operating team. If the relationship has changed, the administrator updates the counterparty record and the preparer revisits the instruction while it is still in draft or review.

What your team sees

  • Active Counterparties — The names, codes and eligibility notes available when preparing banking work.
  • Instructions by Status — The owner and counterparty beside each instruction’s current state.

Follow the work through

Start with instruction preparation, then see provider submission. Roles describes the access handoff.

What it keeps track of

Data model
Organizations
Banking organizations whose treasury operations are run in this app.
Team members
Preparers, approvers, auditors and administrators working in the organization.
Users
Users
Financial counterparties
Banks, custodians and settlement counterparties eligible for banking instructions.

Who uses it

Permissions
App Administrator
Maintains organization and membership records.
Treasury Preparer
Selects the eligible party for an instruction.
Independent Treasury Approver
Checks the relationship during review; Auditor traces the recorded organization and actors.

Set up Open Banking API Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started