Organization and access

The organization record identifies the operating entity, time zone and currency. A team member record connects a user to an organization, active state and role name. The counterparty record identifies banks, custodians and settlement counterparties, including eligibility notes and contact details. A financial account ties a provider account to its counterparty owner and external account ID.

These records determine which business context an instruction belongs to. A counterparty or account active flag helps staff avoid selecting a retired destination for new work while preserving older instructions and their evidence. Administrators maintain membership and master data; they do not become independent financial reviewers merely because they can change configuration.

• Entity. Each operating organization has its own identity, currency and time zone.
• People. Member records connect users with an organization and assigned role.
• Providers. Counterparty and financial account records describe eligible external scope.

Identify the authority for each organization code, counterparty code and external account ID. Verify account ownership before letting an analyst select it for an instruction. Decide how inactive members and counterparties affect new work while keeping historical references readable. Agree how the user role and team member role name are maintained together.

The exchange rate record provides read-only effective rates. If the team uses them for reporting, agree which source maintains each currency and effective date. The instruction and reconciliation amounts in this operating cycle are recorded in USD, so a rate row does not itself authorize conversion or provider execution.

A wallet operator has separate operating organizations. An administrator adds a settlement counterparty for one organization, marks it active and records its eligibility note. A provider-held account uses the counterparty as owner and retains the provider’s external account ID. An analyst assigned to that organization prepares an instruction and selects the correct counterparty. A reviewer from the permitted organization can inspect it; an out-of-scope member should not.

Then deactivate the counterparty. Historical instructions, evidence and decisions remain traceable, while new work no longer treats that counterparty as an eligible destination. Try an administrative account in the approval path. Its configuration rights should not count as a finance review decision.

• Provider accounts — Active external accounts with their owner and currency.
• My instructions — Assigned work within the analyst’s operating context.
• Instructions needing review — The independent decision queue for permitted reviewers.

Prepare an instruction and open a provider account.