1. Wealth Management Platform
  2. Features
  3. Operations Control
Feature · Operations Control

Operations Control

Keep a receipt of every guarded action and its outcome, with supporting files on each instruction.

OverviewOperation Exceptions
Wealth Management Platform · Operations Control

Operation Exceptions

Operation receipts

New
ParentActionOperation keyResult stateOccurred atFailure reason
INS-15746ACT-741OK-515Pending14 OctCut to length
INS-41376ACT-910OK-621Failed19 OctWeld frame
INS-44247ACT-374OK-213Needs review09 OctDrill and tap
INS-85870ACT-144OK-873Pending11 OctDeburr
INS-67856ACT-338OK-684Failed13 OctAssemble
6 of 6 records
ACT-741Operation receipts · OR-46920
Pending
ParentINS-15746
Operation keyOK-515
Occurred at14 Oct
Failure reasonCut to length
External referenceER-188
Example screen with sample data

What you can do

Know what happened to every action

Every guarded action on an instruction, such as an authorization, a submission to the provider or a reconciliation, leaves an operation receipt. The receipt records the action, a unique operation key, the version it expected, the outcome, the time, any external reference, the records it affected and the failure reason where there is one. Outcomes are Pending, Completed, Failed or needs review.

A repeated action with the same key returns the original receipt and makes no second change. A conflicting action is refused. This is what lets the Operations Analyst tell a client with confidence that an instruction was sent once.

How the work is organized

  • Receipts for every guarded action. Authorizations, submissions, approvals and reconciliations each leave a receipt.
  • Exceptions in one queue. Pending, Failed and needs review receipts sit together for the Operations Analyst.
  • Documents on the instruction. Mandates, forms and call notes are attached with a title, evidence type, uploader and visibility of Internal or Shared.

What to agree during setup

Agree who reviews operation exceptions and how quickly. Decide when a receipt may be marked Completed and what evidence is required. Agree the evidence types you use for attachments and which may be shared outside the firm. Set the schedule for the routine reconciliation of receipts.

Check the handoff on an actual case

During a provider outage, an analyst submits an authorized instruction and the connection times out. The receipt is left Pending with the timeout recorded. When the analyst retries, the same operation key returns the same receipt, and the instruction is not sent twice.

The routine reconciliation reads the Pending receipt, checks the provider’s evidence and finds the instruction was received before the timeout. The receipt is marked Completed with the external reference. Another receipt, for a submission the provider has no record of, is marked needs review with the discrepancy, and the analyst raises it with the provider without resending.

What your team sees

  • Operation Exceptions — Receipts waiting for review, with action, outcome, failure reason and external reference.
  • Active Counterparties — The eligible counterparties with contacts and eligibility notes.

Follow the work through

Map the source records before importing history.

What it keeps track of

Data model
Operation receipts
Idempotent operation receipts for guarded actions
Record attachments
Supporting files attached to instructions
Organizations
Firms and client organizations served by the platform
Team members
Internal staff with platform identity and role scope
Counterparties
Eligible external counterparties per organization

Who uses it

Permissions
Operations Analyst
, Compliance Reviewer, Admin.
The Operations Analyst resolves exceptions.
The Compliance Reviewer reads the trail during reviews.
Admin
Maintains organizations, team members and counterparties.

Set up Wealth Management Platform your way.

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

How to get started