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.
- Remittance Platform
- Features
- Counterparties and accounts
Counterparties and accounts
Keep eligible counterparties and their provider accounts tied to the right organization.
OverviewActive Counterparties×
Remittance Platform · Counterparties and accounts
New
Active Counterparties
Financial counterparties
| Name | Code | Active | Contact name | Organization | |
|---|---|---|---|---|---|
| Counterparty 153 | CDE-249 | Contact 100 | ORG-5174 | ||
| Counterparty 382 | CDE-495 | Contact 912 | ORG-7055 | ||
| Counterparty 717 | CDE-217 | Contact 344 | ORG-6418 | ||
| Counterparty 708 | CDE-905 | Contact 454 | ORG-1102 | ||
| Counterparty 793 | CDE-916 | Contact 943 | ORG-2228 |
6 of 6 records
Counterparty 153Financial counterparties · FC-34777
CodeCDE-249
Active✓
Contact nameContact 100
OrganizationORG-5174
What you can do
Parties and provider accounts
An operator begins with the legal organization that owns the instruction. Financial counterparties supplies the counterparty name, code, contact and eligibility note. Financial accounts supplies the provider, external account identity and currency. The account owner reference keeps an account with its counterparty. Treasury Manager checks active status before operations selects a destination.
How the work is organized
- Identify the record. For a transfer to a known counterparty, the Treasury Operator checks the counterparty code and the active account. The provider account identity matters more than a similar display name. If the intended account belongs to a different party, the manager corrects the master record before the operator prepares an instruction. Earlier instructions retain their original counterparty reference for review.
- Keep ownership clear. Treasury Manager maintains the party and account; Treasury Operator selects only active records in the intended organization.
- Follow the account. The provider and external account identity distinguish similar account codes, while the owner reference identifies the counterparty.
The organization reference on financial counterparties defines where a party may be used. The account owner reference lets a reviewer trace each selected debit or credit account back to that party.
What to agree during setup
Agree who maintains counterparty eligibility notes, who can activate an account, and which organization may use each counterparty. Agree how provider account identities are imported and how a retired account becomes inactive. The provider remains the source of the account identity. An active flag is an operational selection control, so the team needs a named owner for changes.
Treasury Manager should assign ownership of eligibility and active flags. Rehearse an instruction that selects an account owned by another counterparty, then correct the selection before review. Keep earlier instruction references available when a party or account becomes inactive.
Check the handoff on an actual case
Treasury Operator opens an instruction for the intended organization and selects an eligible counterparty. Check that the chosen financial account belongs to that counterparty and uses the intended currency. Then inspect the account code and external account identity. A second instruction for another organization should not accidentally reuse the first organization’s scope. Record the selection and reviewer context before changing any master record.
The approver should see the counterparty, provider account identity and account directions on the same instruction. Try another organization and confirm that its operator cannot use the first organization’s party as an approved selection.
What your team sees
- Active Counterparties — Parties available for instruction preparation, with code and organization context.
- Account Snapshot History — Provider account balances ordered by snapshot date for the selected account.
Follow the work through
Use the related process to rehearse the handoff. Review the data model for the source records and roles for access.
What it keeps track of
Data model- Financial counterparties
- Eligible counterparties that receive or originate remittance instructions.
- Financial accounts
- Provider-issued financial accounts held by counterparties.
- Organizations
- Legal entities operating remittance instructions in this workspace.
- Team members
- Authenticated platform identities with an operational role in an organization.
Who uses it
Permissions- Treasury Manager
- Maintains eligible counterparties and account records.
- Treasury Operator
- Selects them for instructions.
- Admin
- Governs organization and team access.
Set up Remittance Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.