From client-operations
Designs workflow automation for securities operations including task routing, multi-level approvals, SLA monitoring, escalations, and regulatory audit trails. For account opening, maintenance, transfers, corporate actions.
npx claudepluginhub joellewis/finance_skills --plugin client-operationsThis skill uses the workspace's default tool permissions.
Guide the design and implementation of workflow automation for securities operations. Covers business process management (BPM) fundamentals, task routing and assignment strategies, multi-level approval chains with delegation of authority, escalation rules and SLA monitoring, process orchestration patterns (sequential, parallel, conditional, event-driven), workflow engine selection for financial...
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Guide the design and implementation of workflow automation for securities operations. Covers business process management (BPM) fundamentals, task routing and assignment strategies, multi-level approval chains with delegation of authority, escalation rules and SLA monitoring, process orchestration patterns (sequential, parallel, conditional, event-driven), workflow engine selection for financial services, audit trail requirements for regulatory compliance, and workflow effectiveness measurement. Enables building or improving operations workflows that route work correctly, enforce approval controls, meet service-level commitments, and produce defensible audit trails.
12 — Client Operations (Account Lifecycle & Servicing)
prospective
Business process management (BPM) is the discipline of modeling, executing, monitoring, and improving operational processes. In securities operations, BPM applies to every repeatable process that involves multiple steps, multiple participants, or decision points: account opening, account maintenance requests, transfer processing, corporate action elections, reconciliation break resolution, and billing exception handling.
Process modeling. A workflow begins as a process model — a formal representation of the steps, decision points, roles, and data flows in an operational process. The model serves three purposes: (1) it documents how the process works for training, audit, and examination purposes, (2) it provides the blueprint for automation, and (3) it establishes the baseline for measurement and improvement.
BPMN notation basics. Business Process Model and Notation (BPMN 2.0) is the industry standard for process modeling. Key elements relevant to securities operations:
Process decomposition. Complex operations workflows are decomposed into sub-processes. An account opening workflow decomposes into: data collection, KYC verification, document review, custodian submission, confirmation processing, and account activation. Each sub-process can be modeled, automated, and measured independently while the parent process orchestrates the sequence.
State machines for financial workflows. Many operations items are best modeled as state machines — an item exists in one of several defined states, and transitions between states are triggered by events or actions. A transfer request might have states: Initiated, Validated, Submitted to ACATS, In Progress, Completed, Rejected, Cancelled. Each transition has a guard condition (e.g., the transition from Validated to Submitted requires all validation checks to pass) and an action (e.g., send ACATS message). State machines enforce that items follow valid paths and prevent invalid transitions (an item cannot move from Initiated to Completed without passing through Validated and Submitted).
Task routing determines which person or team receives a work item when it enters the workflow. Effective routing minimizes queue wait time, balances workload, and ensures items reach someone with the appropriate skill and authority.
Role-based routing. The simplest routing strategy. Each task type is assigned to a role (e.g., "Account Opening Analyst," "Transfer Specialist," "Senior Operations Reviewer"), and any person filling that role can pick up the task. Role-based routing is sufficient when all members of a role have equivalent skills and authority.
Skill-based routing. Extends role-based routing by matching task attributes to individual skill profiles. A trust account opening routes to analysts certified in entity account processing. A cross-border transfer routes to analysts with international custody experience. Skill-based routing reduces rework by ensuring the first handler has the competence to resolve the item.
Round-robin assignment. Tasks are distributed evenly across team members in rotation. Round-robin prevents any one person from being overloaded but does not account for task complexity or individual capacity. It works well when tasks are roughly uniform in effort.
Workload-based assignment. Tasks are assigned to the team member with the lowest current workload, measured by the number of open items, the total estimated effort of open items, or a weighted score that considers both. Workload-based assignment adapts to variable throughput across team members and handles uneven task complexity better than round-robin.
Queue management. When tasks cannot be immediately assigned (because all qualified team members are at capacity), they enter a queue. Queue management includes: priority ordering within the queue (SLA deadline, dollar value, client tier), visibility into queue depth and wait time for management, and automatic re-routing if a queue exceeds a defined depth or wait-time threshold.
Capacity planning. Historical data on task volumes, processing times, and SLA targets feeds capacity models that determine how many staff are needed for each role. Workflow systems capture the data needed for capacity planning: arrival rate (tasks per hour/day), service rate (average processing time per task), and queue wait time. Little's Law (queue depth = arrival rate times average time in system) provides the theoretical foundation.
Many operations tasks require one or more approvals before proceeding. Approval chains enforce segregation of duties, limit authority by seniority and dollar value, and create a documented decision trail.
Multi-level approval workflows. A simple task may require one approval (e.g., standard account maintenance reviewed by a team lead). A high-risk task may require two or three levels (e.g., a large wire transfer reviewed by an operations analyst, then a senior manager, then a compliance officer). The number of approval levels is determined by the risk profile of the task, defined in the firm's delegation of authority matrix.
Approval matrices by dollar amount and risk level. A delegation of authority matrix maps task types and dollar thresholds to required approval levels. Example structure:
| Task Type | Amount or Risk | Approval Required |
|---|---|---|
| Cash disbursement | Under $25,000 | Operations analyst |
| Cash disbursement | $25,000 - $100,000 | Operations analyst + team lead |
| Cash disbursement | Over $100,000 | Operations analyst + team lead + operations manager |
| Account transfer (full ACAT) | Any | Operations analyst + supervisory review |
| Journal entry (different registration) | Any | Operations analyst + compliance review |
| Fee waiver or adjustment | Under $500 | Team lead |
| Fee waiver or adjustment | Over $500 | Operations manager |
Four-eyes principle. A foundational control in financial services: no single individual should be able to initiate and approve a transaction. The maker-checker pattern requires one person to prepare (make) and a different person to review and approve (check). For high-value or high-risk items, a third reviewer (four-eyes plus) may be required. Workflow systems enforce the four-eyes principle by preventing the initiator from also serving as the approver for the same item.
Delegation of authority. When an approver is unavailable (out of office, on leave), the workflow must support delegation — the designated alternate inherits the approval authority for a defined period. Delegation must be: (1) explicitly configured in advance by the primary approver or a system administrator, (2) time-limited (auto-expires at the end of the delegation period), (3) logged (the audit trail records that the delegate approved on behalf of the primary), and (4) restricted (the delegate cannot further delegate).
Timeout and auto-escalation. If an approval sits unactioned beyond a defined threshold, the workflow escalates automatically. A first-level escalation sends a reminder to the assigned approver. A second-level escalation notifies the approver's manager. A third-level escalation reassigns the item to an alternate approver. Timeout thresholds are tied to the SLA for the task type — a same-day disbursement cannot wait 24 hours for approval.
Service-level agreements define the expected completion time for each task type. Escalation rules enforce SLAs by triggering progressively urgent actions as items age toward or beyond their deadlines.
SLA definition per task type. Each operational task type has a defined SLA based on regulatory requirements, client expectations, and operational capacity. Examples:
| Task Type | SLA Target | Regulatory Driver |
|---|---|---|
| ACAT transfer validation | 3 business days | FINRA Rule 11870 |
| ACAT transfer completion | 6 business days | FINRA Rule 11870 |
| Account maintenance (name change) | 2 business days | Internal service standard |
| Cash disbursement | Same day (if before cutoff) | Client expectation |
| Corporate action election submission | 1 business day before DTC deadline | DTC PTOP/ATOP rules |
| Reconciliation break resolution | 5 business days (standard), 1 business day (high value) | SEC Rule 15c3-3, fiduciary obligation |
| New account opening | 3 business days | Internal service standard |
SLAs are measured from the time the task enters the workflow (not from when it is assigned to an individual) to the time it is completed or resolved.
Aging thresholds. Work items are classified by age relative to their SLA:
Escalation tiers. Escalation follows a defined chain:
Each tier includes a defined time interval. If Tier 1 does not resolve the item within the interval, Tier 2 fires automatically.
Notification cadence. Escalation notifications follow a frequency schedule: initial alert, then periodic reminders at defined intervals (e.g., every 2 hours for same-day SLAs, every business day for multi-day SLAs). Notification fatigue is a real risk — if escalations fire too frequently or for low-priority items, recipients learn to ignore them. Calibrate notification thresholds to match the urgency and volume of each task type.
SLA breach handling. When an SLA is breached, the workflow system records the breach with: the task identifier, the SLA target, the actual completion time (or that the item remains open), the root cause (if determined), and the responsible party. Breach data feeds management reporting, trend analysis, and process improvement prioritization.
Management reporting. SLA dashboards provide real-time and historical views:
Orchestration defines how individual tasks are sequenced, parallelized, and conditioned to form a complete workflow.
Sequential processing. Tasks execute in a defined order. Each task must complete before the next begins. Example: account maintenance request received, then validated, then executed, then confirmed. Sequential processing is appropriate when each step depends on the output of the previous step.
Parallel processing. Multiple tasks execute simultaneously. Example: during account opening, KYC verification, document review, and custodian pre-validation run in parallel because they are independent. A synchronization point (join gateway) waits for all parallel tasks to complete before the workflow proceeds to the next step. Parallel processing reduces total cycle time.
Conditional branching. The workflow takes different paths based on data conditions. Example: if the account type is individual, route to the simple opening path; if the account type is trust, route to the entity review path; if the account type is estate, route to the legal documentation review path. Conditional branching is implemented with exclusive (XOR) gateways.
Sub-process invocation. A parent workflow delegates a portion of its work to a self-contained sub-process. The sub-process has its own tasks, gateways, and error handling. Example: the account opening workflow invokes a "KYC verification" sub-process that handles identity verification, screening, and risk scoring. Sub-processes promote reuse (the same KYC sub-process is invoked by account opening, account maintenance, and periodic review workflows) and maintainability (changes to KYC logic are made in one place).
Event-driven triggers. The workflow starts or advances in response to an external event rather than a timer or human action. Example: a custodian sends a settlement confirmation message, which triggers the reconciliation workflow for that transaction. A corporate action announcement from a data vendor triggers the event setup workflow. Event-driven processing requires a message bus or event broker (Kafka, RabbitMQ, or a cloud-native equivalent) to decouple the event source from the workflow engine.
Timer-based triggers. The workflow starts or advances based on a schedule or elapsed time. Example: daily reconciliation runs at 7:00 AM after custodian files arrive. An account maintenance request that has been in "pending documentation" state for 30 calendar days triggers an auto-close workflow. Timer-based triggers are essential for deadline-driven processes like corporate action elections and regulatory filings.
Human-in-the-loop gates. At defined points in an otherwise automated workflow, the process pauses and waits for a human decision. Example: an automated KYC check returns a "review required" result; the workflow assigns the review to a compliance analyst and waits for an approve/reject decision before continuing. Human gates should be the exception, not the rule — each gate adds latency and staffing requirements. Design the workflow to minimize human gates by handling the most common cases automatically and reserving human review for genuinely ambiguous items.
Selecting a workflow platform for securities operations requires evaluating both technical capabilities and financial-services-specific requirements.
Platform categories:
Evaluation criteria for financial services:
Build vs. buy. The decision depends on the firm's size, engineering capability, and workflow complexity. Firms with fewer than 50 operations staff and standard workflows typically benefit from commercial platforms. Firms with large, specialized operations teams and highly customized workflows may find that the cost of customizing a commercial platform exceeds the cost of building a purpose-fit engine.
In regulated financial services, every workflow action is a potential examination artifact. The audit trail must be complete, immutable, and retrievable.
Every action logged. The workflow system must record: who performed the action (user identity, not just role), what action was performed (state change, approval, rejection, reassignment, data modification), when the action occurred (timestamp with timezone), why the action was taken (approval reason, rejection reason, override justification), and the data state before and after the action.
Immutable records. Audit log entries must be write-once. No user — including administrators — should be able to modify or delete audit entries. This is a direct requirement of SEC Rule 17a-4, which mandates that records be preserved in a non-rewriteable, non-erasable format. Workflow systems that store audit logs in a standard relational database must implement application-level immutability controls or use append-only storage.
Books-and-records requirements for automated workflows. SEC Rule 17a-3 requires broker-dealers to create and maintain specified records, including records of all orders, transactions, and communications. When workflows automate the creation, routing, or approval of these records, the workflow itself becomes part of the books and records. The automated rules, decision logic, and configuration that govern the workflow must be documented and preserved alongside the transaction records. If a workflow rule is changed (e.g., the approval threshold for cash disbursements is raised from $25,000 to $50,000), the change must be documented with the effective date, the business justification, and the approver.
FINRA Rule 3110 (Supervision). FINRA requires member firms to establish and maintain supervisory systems, including written supervisory procedures, reasonably designed to achieve compliance with applicable securities laws and regulations. When operations workflows enforce supervisory controls (approval chains, exception reviews, compliance gates), the workflow configuration is part of the supervisory system. The workflow design must be reviewed and approved by compliance, and the firm must be able to demonstrate that the workflow enforces the supervisory procedures as written.
Examination defensibility. During a regulatory examination (SEC, FINRA, state regulators), examiners may request: a description of the workflow for a specific process, the audit trail for specific transactions or time periods, evidence that approval controls were functioning as designed, documentation of any workflow rule changes, and SLA performance data. The workflow system must support efficient retrieval of this information.
Quantitative measurement is essential to identify bottlenecks, justify investments, and demonstrate operational improvement.
Cycle time. The elapsed time from when a work item enters the workflow to when it reaches a terminal state (completed, rejected, cancelled). Cycle time includes both processing time (time actively being worked) and wait time (time in queues, awaiting approval, waiting for external input). Measuring cycle time by task type and by process step reveals where delays accumulate.
Throughput. The number of work items completed per unit time (per hour, per day, per month). Throughput per analyst measures individual productivity. Throughput per process measures operational capacity. Declining throughput with stable volume indicates a capacity or efficiency problem.
Queue depth. The number of work items waiting to be processed at any point in time. Persistently growing queue depth indicates that arrival rate exceeds processing capacity. Queue depth by task type identifies which processes are under-resourced or under-automated.
SLA compliance rate. The percentage of work items completed within their defined SLA. Calculated as: items completed within SLA divided by total items completed. SLA compliance below target triggers root cause analysis and process improvement.
Rework rate. The percentage of work items that are returned to a previous step due to errors, missing information, or rejected approvals. Rework consumes capacity without producing throughput. High rework rates indicate unclear procedures, inadequate training, or poor upstream data quality.
Automation rate. The percentage of work items that complete without any human intervention (fully automated, or STP). Automation rate is the inverse of the exception rate. Tracking automation rate over time measures the effectiveness of STP initiatives and rule-based processing enhancements.
First-contact resolution rate. The percentage of work items resolved by the first person who touches them, without reassignment or escalation. Low first-contact resolution indicates routing problems (items are reaching the wrong person) or skill gaps (the assigned person cannot resolve the item).
Scenario: A mid-size broker-dealer processes approximately 300 account transfers per month. Management has identified that high-value transfers (over $500,000) lack a consistent approval process — some receive supervisory review, others do not, depending on which analyst processes them. The compliance department has flagged this as a FINRA Rule 3110 supervisory concern. The firm needs a structured approval workflow for all account transfers, with additional controls for high-value and high-risk transfers.
Design Considerations:
Analysis:
Define the approval matrix:
| Transfer Type | Value / Risk | Approvals Required | SLA Impact |
|---|---|---|---|
| Full ACAT (standard) | Under $500K | Operations analyst (self-review) + automated supervisory log | No added delay |
| Full ACAT (high-value) | $500K - $2M | Operations analyst + team lead review | Add 4 hours max |
| Full ACAT (very high value) | Over $2M | Operations analyst + team lead + operations manager | Add 8 hours max |
| Transfer to third-party account | Any value | Operations analyst + team lead + compliance review | Add 1 business day max |
| Transfer from client age 65+ | Over $100K | Operations analyst + team lead (senior investor protection review) | Add 4 hours max |
| Non-ACAT wire transfer | Over $50K | Operations analyst + team lead + verbal callback confirmation | Add 2 hours max |
Model the workflow as a state machine with states: Received, Validated, Pending Approval (Tier 1), Pending Approval (Tier 2), Pending Approval (Tier 3), Approved, Submitted to ACATS/Custodian, In Progress, Completed, Rejected. Guard conditions on each transition enforce the approval matrix — the system evaluates transfer value, transfer type, client age, and destination account ownership to determine which approval tiers are required.
Implement timeout escalation on each approval tier. If a Tier 1 approval (team lead) is not acted upon within 2 hours, send a reminder. If not acted upon within 4 hours, escalate to the operations manager for either direct approval or reassignment. These timeouts are calibrated to keep the total approval cycle within the FINRA Rule 11870 timelines.
For the compliance review tier (transfers to third-party accounts), the compliance analyst receives a structured review package: client identity verification, relationship between the client and the third-party recipient, source of the transfer instruction (client-initiated vs. advisor-initiated), and any recent account activity that may indicate exploitation or unauthorized transactions. The compliance review SLA is 1 business day, with escalation to the Chief Compliance Officer if the deadline is approaching.
The audit trail captures every approval decision: approver identity, timestamp, decision (approve/reject/request more information), and any comments or justification. This audit trail is the firm's evidence of supervisory review for FINRA Rule 3110 examination purposes.
Scenario: An RIA with $6 billion in AUM processes approximately 800 account maintenance requests per month, including name changes, address updates, beneficiary changes, account re-registrations, and fee schedule adjustments. The firm has no formal SLA tracking — requests are managed through a shared email inbox and a spreadsheet. Advisors frequently complain that requests "disappear" or take too long. The head of operations wants to implement SLA monitoring with real-time visibility for both operations staff and advisors.
Design Considerations:
Analysis:
Step 1 — Define SLA targets per maintenance type:
| Maintenance Type | SLA Target | Rationale |
|---|---|---|
| Address change | 1 business day | Simple, no documentation required beyond client confirmation |
| Name change (marriage, divorce) | 3 business days | Requires supporting documents (marriage certificate, court order) and custodian processing |
| Beneficiary change | 2 business days | Requires signed beneficiary designation form; advisor review recommended |
| Account re-registration (individual to trust) | 5 business days | Requires trust documentation, custodian re-titling, cost basis continuity verification |
| Fee schedule adjustment | 2 business days | Requires advisor approval, billing system update, and confirmation |
| Account closure | 3 business days | Requires asset disposition (transfer or liquidation) and custodian close-out |
Step 2 — Build the workflow in Salesforce. Create a custom object (or use Salesforce Case) for maintenance requests. Each request captures: request type, requesting advisor, client account, date received, SLA deadline (auto-calculated from request type), assigned analyst, current status (Received, In Progress, Pending Documentation, Submitted to Custodian, Completed, Cancelled), and custodian.
Implement routing rules: requests are auto-assigned to the next available analyst using workload-based assignment. Complex request types (re-registrations, closures) are routed to senior analysts with the appropriate skill tag.
Step 3 — Implement SLA monitoring. Salesforce Process Builder (or Flow) evaluates each open request against its SLA deadline on a scheduled basis (every hour during business hours). The aging thresholds:
Step 4 — Advisor visibility. Build a Salesforce Experience Cloud portal (or a custom Lightning component accessible to advisors) that displays: all open requests for the advisor's clients, current status and assigned analyst, SLA deadline and color-coded aging indicator, and a comment thread for advisor-operations communication. This eliminates the need for advisors to email or call operations for status updates.
Step 5 — Management reporting. A weekly SLA dashboard displays: total requests received and completed, SLA compliance rate by maintenance type, average cycle time by maintenance type, breach count and root causes, and analyst-level throughput. The operations manager reviews the dashboard in the weekly team meeting and assigns process improvement actions for any maintenance type with SLA compliance below 90%.
Scenario: A broker-dealer processes voluntary corporate action elections for approximately 4,000 client accounts. The firm has experienced two incidents in the past year where election deadlines were missed, resulting in clients receiving the default election on tender offers instead of their instructed election. In both cases, the root cause was a combination of late client notification and insufficient escalation when elections were not returned in time. The COO has mandated a formal escalation framework for corporate action elections.
Design Considerations:
Analysis:
Define the escalation timeline working backward from the DTC deadline. Assume a typical tender offer with a DTC deadline of Day 0 (expressed as business days before the DTC deadline):
| Day (Before DTC Deadline) | Action | Owner |
|---|---|---|
| Day -10 | Event announced, validated, and set up in system. Client notification generated. | Corporate actions analyst |
| Day -9 | Notification sent to all affected clients and advisors via email and portal. | Automated |
| Day -5 | First follow-up to clients/advisors who have not responded. Yellow status assigned. | Automated notification, analyst monitors |
| Day -4 | Second follow-up with direct call to advisor for accounts above $100K in affected position. Team lead notified of non-responses. | Analyst (calls), automated (team lead alert) |
| Day -3 | Firm internal deadline. All received elections aggregated for submission. Non-respondents receive default election unless override is approved. | Corporate actions analyst + team lead review |
| Day -2.5 | Escalation to corporate actions manager for any account where the advisor disputes the default and requests a late election. Manager decides whether to attempt late submission. | Corporate actions manager |
| Day -2 | Elections submitted to custodian. | Corporate actions analyst |
| Day -1 | Custodian deadline. Confirm custodian has accepted the firm's election submission. Escalate to manager immediately if custodian rejects or flags any issues. | Corporate actions analyst + manager (if issues) |
| Day 0 | DTC deadline. Verify final settlement. Any issues escalated to senior VP. | Corporate actions manager + senior VP (if issues) |
Implement monitoring controls:
Post-event review: after each voluntary corporate action settles, the team logs the response rate, any elections that missed the internal deadline, whether late submissions were attempted and accepted, and any client impact from default elections. This data feeds a monthly review that identifies patterns (specific advisors who consistently respond late, event types that require longer lead times, clients who need proactive outreach) and drives process improvements.
Audit trail requirements: every notification, follow-up, escalation, and election submission is logged with timestamps and responsible parties. If a client later disputes that they received the default election, the firm can produce the complete communication and escalation history demonstrating that the client was notified, reminded, and escalated through the defined process. This audit trail satisfies FINRA Rule 3110 supervisory obligations and provides examination-ready documentation.