Stp Automation

This walks you through building straight-through processing for securities operations, from measuring your current STP rate to designing exception-based workflows that replace review-all processes. It covers the architectural layers you need (data standardization, validation rules, integration patterns), helps you choose between RPA and API-based automation for legacy systems, and explains how to set up exception queues with auto-resolution. The benchmark numbers are useful: equity trade processing hits 90-98% STP at mature firms while complex account opening might only reach 20-40%. Best when you're trying to eliminate manual touchpoints in trade processing, settlement, reconciliation, or account opening and need to think through controls and audit trails for automated environments.

skills.sh installs: 686
GitHub stars: 224
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add joellewis/finance_skills --skill stp-automation --agent claude-code

Installs into .claude/skills of the current project.

Files

STP & Automation

Core Concepts

1. STP Fundamentals

Straight-through processing is the end-to-end automated completion of a business process without manual intervention: a transaction enters the system at one end and exits as a completed, booked, and confirmed event at the other with no human touching it along the way. True STP means zero manual intervention for the happy path; a process with a human review or approval at a midpoint is partially automated, not STP.

STP rate calculation. The fundamental metric is:

STP Rate = Automated Completions / Total Volume * 100

An "automated completion" is a transaction or workflow instance that passed through every step without manual intervention. If a trade requires a human to confirm a counterparty identifier before it can settle, that trade is not STP even though every other step was automated. The denominator is total volume, including both automated and exception items.

SKILL.md on GitHub