Pre-Trade Position Limit Controls — Case Analysis

// The Audit Lens — Three Assertions Applied to the PLM System

Completeness. Accuracy. Timeliness.

Three audit assertions — completeness, accuracy, timeliness — applied directly to the PLM. Each failed.

Completeness

All positions that count toward the CFTC Part 150 aggregate limit are included in the PLM calculation — futures, options delta-equivalent, and OTC swap positions across all accounts under common control.

Gap found: OTC swap positions excluded from the delta-equivalent aggregate. The PLM system captured exchange-listed positions only. OTC positions in the same underlying were not fed to the system. The aggregate the PLM checked against was structurally incomplete.

Accuracy

The delta-equivalent conversion method applied to options positions correctly translates each option contract into its futures-equivalent exposure, using a documented and independently validated calculation.

Gap found: Delta-equivalent calculation method not independently documented or validated. The conversion applied by the PLM system could not be traced to an approved methodology. No evidence of periodic validation against an external calculation or benchmark.

Timeliness

The position data used in the pre-trade check reflects the current position at the moment the order is submitted — not a position as of an earlier snapshot that may not capture recent executions.

Gap found: Position feed runs on a batch update cycle. Intraday executions are not reflected in the PLM aggregate until the next batch refresh. An order submitted between batch cycles is checked against a stale position — the actual exposure at execution is not what the system tested.

// Audit Scope — CFTC 17 CFR Part 150

Five PLM Control Objectives

The engagement tested five control objectives drawn directly from CFTC 17 CFR Part 150 requirements. Each maps to one or more gaps identified in fieldwork.

1 · Regulatory ComplianceConduct business activities in accordance with CFTC position limit monitoring requirements.

2 · Day-to-Day SupervisionProvide adequate supervision for daily position limit monitoring operations.

3 · Application OperationsAdequately operate and manage the firm's position limit monitoring applications.

4 · Application Development & MaintenanceDevelop, test, and maintain PLM applications — including keeping code logic current with regulatory revisions.

5 · Data Completeness, Accuracy & TimelinessCapture complete and accurate positions, exposures, and reference data — including third-party delta settlement prices — on a timely basis in the PLM application.

// Four-Stage Failure Chain

How the Gaps Compound in Practice

Stage 1

Limit loaded without independent verification

Gap: No change management over configuration

CFTC Part 150 speculative limits manually loaded into PLM. No formal change request. No reconciliation to the published limit schedule. Limit in system may differ from current regulatory requirement.

Stage 2

OTC positions not in the aggregate

Gap: Completeness failure — OTC excluded

PLM checks exchange-listed position only. OTC swaps in the same underlying contribute to the CFTC Part 150 aggregate but are not fed to the pre-trade system. The aggregate the system tests is not the aggregate the regulation requires.

Stage 3

Batch feed — stale position at point of check

Gap: Timeliness failure — not real-time

Between batch cycles, executions are not reflected in the PLM. An order submitted in the gap period is checked against the prior batch position. Intraday limit breach possible without detection until next refresh.

Stage 4

Breach alert with no documented response

Gap: Alert escalation — no evidence

When the PLM generates a threshold alert, no documented acknowledgment procedure exists. Alert routed to a shared inbox. No response SLA defined. No sign-off evidence. The control fired — what happened next cannot be evidenced.

// Control Gap Identification — CFTC Part 150 · CME Group · ITGC · SOX 404

Four Gaps. What Was Required. What Was Found.

Control ID	Control Required	What Was Found	Risk Consequence	Sev	Framework
PL-01 Limit configuration, code logic & regulatory change management	PLM code logic and limit configuration kept current with CFTC 17 CFR Part 150. When the regulator revises position limit requirements, the PLM application is updated, tested, and validated before the next trading day. Changes subject to formal ITGC change management with reconciliation to the revised regulatory standard.	CFTC revised 17 CFR Part 150. PLM code logic not updated to reflect the change — operating against a superseded standard. No process existed to track regulatory revisions and trigger a code review cycle.	Position limit monitoring conducted against a superseded regulatory standard. Control appears operative — but is not compliant with current CFTC Part 150 requirements.	HIGH	ITGC CM-1 CFTC Part 150 CME Rule 559 SOX 404 ITGC
PL-02 Completeness — OTC position inclusion	Delta-equivalent aggregate includes all positions counting toward the CFTC Part 150 limit — exchange-listed futures, options on futures (delta-equivalent), and economically equivalent OTC swaps. OTC position data fed to the PLM on the same cycle as exchange-listed positions.	PLM receives exchange-listed position feed only. OTC swap positions in the same underlying are not fed to the PLM and are not included in the delta-equivalent aggregate. The aggregate the pre-trade check tests is structurally incomplete — OTC exposure invisible to the system.	Firm can build an OTC position that, when combined with the exchange-listed position, exceeds the CFTC Part 150 limit while the pre-trade system shows the position as within limit. Regulatory violation undetected at the point of order entry.	HIGH	CFTC Part 150.2 CFTC §4a(a)(1) ITGC AC-6 SOX 404 ITAC
PL-02b Accuracy — third-party delta price validation	Delta settlement prices received from third-party vendor feeds are independently validated before use in the delta-equivalent calculation. Any vendor-provided price used to determine the equivalent futures position is verified against an internal benchmark before the PLM applies it.	A third-party system vendor provided an incorrect Brent options delta settlement price. This price was used directly in the delta-equivalent calculation — applied to determine the equivalent futures position for CFTC Part 150 purposes — without independent validation. No control existed to detect vendor feed errors before they entered the PLM.	Incorrect delta settlement price produces an inaccurate equivalent futures position. The PLM aggregate reflects the vendor error. Firm may be above or below the CFTC Part 150 limit without accurate detection — depending on the direction of the pricing error.	HIGH	CFTC Part 150.2 CFTC §4a(a)(1) ITGC AC-6 SOX 404 ITAC
PL-03 Timeliness — real-time position feed	Position data used in the pre-trade check reflects executions up to the point of order submission. Intraday executions are reflected in the aggregate without a material delay at the moment the pre-trade check fires.	Position feed to PLM updates on a batch cycle. Intraday executions not reflected between updates. Pre-trade check fires against the prior batch position — not the current exposure.	Intraday position build-up can breach the limit between batch cycles without detection. The pre-trade control operates but does not see what it is supposed to prevent at the moment it needs to act.	HIGH	CFTC Part 150 ITGC MO-3 CME Rule 560 SOX 404 ITAC
PL-04 Threshold alert escalation — documented response	When the PLM generates a threshold alert, a documented escalation procedure governs the response — defined ownership, response SLA, acknowledgment record, disposition code, and independent sign-off. Evidence retained for each alert.	Threshold alerts route to a shared risk inbox. No documented acknowledgment procedure. No defined response SLA. No sign-off evidence. Alert history exists in the system — evidence of what was done with each alert does not.	Pre-trade control generates the alert but the response cannot be evidenced. Under SOX 404 or regulatory examination, an alert without a documented response is equivalent to no alert. The control is not operating effectively as designed.	MEDIUM	ITGC MO-3 SOX 404 ITAC COSO Monitoring OCC Exam Guidance

// Key Takeaways

What Pre-Trade Position Limit Audits Consistently Find

The aggregate the system checks is rarely the aggregate the regulation requires.

CFTC Part 150 limits apply across exchange-listed futures, delta-equivalent options, and OTC swaps. Most pre-trade systems check the exchange-listed position only. The OTC position requires a separate feed and a separate aggregation step — and in most trading platform audits, at least one of those elements is absent or incomplete.

An alert without a documented response is not an operating control under SOX 404.

The pre-trade system generating the alert is the detective control. The escalation procedure and the documented response are the corrective control. Under SOX 404 operating effectiveness testing, both halves are required. A threshold alert that routes to a shared inbox with no acknowledgment procedure and no sign-off cannot be evidenced as a functioning control.

Pre-Trade Controls in Your Trading Environment

Whether assessing a proprietary PLM system, a third-party pre-trade risk platform, or building the audit programme for a new trading desk — the completeness, accuracy, and timeliness assertions are the right starting point. Start with a conversation about the specific control environment.

Discuss This Analysis

Composite Case Study — Disclaimer
This analysis is prepared by IT Audit Consulting (itauditconsulting.com) for independent educational and professional commentary purposes. It is a composite case study based on recurring control gap patterns identified in technology audits of pre-trade risk systems at regulated financial institutions. No specific firm, institution, trader, desk, or system is identified, referenced, or implied. This analysis does not constitute legal, financial, regulatory, or professional advice and does not create any professional-client relationship. Past institutional affiliations (Goldman Sachs, Tradeweb, and others) are referenced for biographical context only and do not imply endorsement. Readers should conduct their own independent due diligence and consult qualified legal, financial, and regulatory advisors before acting on any information herein.