top of page
black-textured-background_926199-8358.avif

DISSY AWARDS ARCHIVE​​​

​

​​

April 2025 - MarketAxess Corp.

​

March 2025 - UBS.

​​

BUTTON - 0Left Arrow.jpg
BUTTON - 0DownArrow.jpg
BUTTON - 0DownArrow.jpg

APRIL 2025
And the Dissy Award Goes To... MarketAxess Corporation

DISCIPLINARY ACTION OF THE MONTH

FINRA Regulators stand idly by and horrific abuses go uninvestigated and virtually unpunished

Charles Fraud hereby recognizes MarketAxess Corporation for their "pattern and practice" of misreporting trade execution times to the Real-time Transaction Reporting System (RTRS) due to the firm's "incorrect interpretation of the time of trade" and, additionally, for similar issues due to "technological errors" that caused inaccurate and untimely transaction reporting to the Trade Reporting and Compliance Engine (TRACE).  The majority of the misreported transactions were inaccurate by only one second - which may not seem particularly severe, but there are several issues that make this "Disciplinary Action" stand out, and a deeper dive confirms that it is genuinely worthy of the DISSY award.   
 
"MarketAxess reported 57,340 [municipal securities] transactions to the RTRS with an inaccurate time of trade due to the firm’s incorrect interpretation of time of trade. For a majority of these transactions, the execution time was inaccurate by one second." MarketAxess A.W.C. FINRA NO. 2020065254901, p.3

Also, 51,252 corporate bond transactions and 2,446 U.S. Treasury transactions were reported to TRACE with inaccurate transaction times. "For about half of these transactions, the time of execution was inaccurate by one second... These inaccurate and late reports occurred due to a technological error..."  MarketAxess A.W.C., p.3

While a one second deviation may seem insignificant, that is more than enough time to exploit and conceal manipulative and abusive trading.  Generally, in electronic trading (and especially in the context of high-frequency algorithmic trading), where many strategies rely on quick responses to real‑time data, even a one‑second deviation can be exploited into an unfair advantage, including Shadow Front Running of Customer Orders and/or concealing Matched-Book or Wash Trades - more on that below.  To be fair, nothing of this sort is reported in this A.W.C., but there is nothing to suggest that any serious inquiry was made by FINRA in this regard, either.  

The deciding factor for awarding this Dissy was that, even after new measures were implemented "
to ensure that accurate execution times were reported to TRACE and RTRS", THE PROBLEMS CONTINUED, AND THERE IS NO MENTION OF THE ISSUE EVER BEING RESOLVED.  Astoundingly, the inaccurate times continued to be attributed to the firm's "incorrect interpretation of the meaning of time of trade.p.4  

From FINRA MarketAxess A.W.C. NO. 2020065254901 - page 4 (literally as a footnote):
"After January 2022 when the firm began performing automated surveillance and manual reviews of surveillance alerts, the firm continued to report certain municipal bond transactions to RTRS with inaccurate times of trade due to its incorrect interpretation of the meaning of time of trade."

But since this is now a settled matter, and so long as MarketAxess "accepts and consents to the findings without admitting or denying them" and pays the $180,000 fine, the firm may now exempt from further action regarding this matter... even for problems that continued after remedial measures were taken and which may still be unresolved because, of course, this A.W.C. contains the standard boilerplate verbiage:​ 

"FINRA will not bring any future actions against Respondent alleging violations based on the same factual findings described in this AWC." p.1​

So, perhaps MarketAxess continues to operate with an "incorrect interpretation of the meaning of time of trade" and...

NO FURTHER ACTION CAN BE TAKEN REGARDING THIS MATTER. 
Congratulations!  That is an impressive feat well-deserving of a DISSY! 

Dissy Trophy reflects state of financial world where wrongdoing rarely gets meaningfully punished

The Dissy

DISSY AWARD.webp

No other details were provided that could answer the following questions: 

What caused the firm to have an "incorrect interpretation of the time of trade"?  What does this even mean?  And why is this such a difficult matter to resolve?

What were the nature of the "technological errors" that caused the untimely reporting?  And why were only some transactions reported inaccurately?   

The A.W.C. states that half or more of the erroneous timestamps were 1s late.  So, there are many inaccurately reported transactions erroneous by something other than 1 second.  Was there more than one error?  Were there additional types of "incorrect interpretation of time of trade"?  

Did anyone investigate whether Front Running, Matched-Book or Washed Trades, or other exploitative or manipulative activities were facilitated by or otherwise coincided with these errors?  DID FINRA EVEN INQUIRE?

Lastly, a couple examples explaining how reporting transactions late by one second could be exploited for manipulative purposes:

SHADOW FRONT RUNNING
Suppose a customer order arrives at time zero seconds 0.00s.  The firm could front-run the transaction and purchase at time 0.5s.  If the execution time of the customer order is delayed by one second, reported as executed at time 1.00s, then surveillance would show the firm's own trade occurring before the customer and thus would not be flagged for front-running.  


HIDING MATCHED-BOOK OR WASHED TRADES
Suppose the firm executes both sides of a risk‑free flip (buy → sell) (or is acting in concert with another market participant).  By forward-shifting the timestamp of the final transaction by +1s (or more), this can camouflage and prevent detection of exploitative trading to manipulate asset prices.  

Silverback.webp

DISCIPLINARY ACTION OF THE MONTH

MARCH 2025

And the Dissy Award Goes To... UBS Financial Services!



Charles Fraud hereby recognizes UBS Financial Services, Inc. for submitting 17,000 Blue Sheets that misreported, or failed to report information about 4.4 million transactions due to "coding errors."  UBS was fined $1.1 million, just $.25 per misreported blue sheet.  UBS began revising the coding issues in November 2017, and by September 2018 "all of the logic impacting the transaction fields was remediated." 

No other details were provided regarding the following : 

Dissy Trophy reflects how abuses are rampant and corruption out in the open
Dissy of the Month Trophy Recognizes Fraud, abuse, ineffective disciplinary action

The Dissy

Excerpt from page 2 of FINRA AWC NO. 2019061777501 

image.png
  • What actually caused the "coding errors"? 

  • Why did it so long to notice or to fix the problems?   Also, why don't FINRA's Monthly Disciplinary Actions report how long it took for UBS to fix the "logic."

  • Were all issues remediated, or just the "logic impacting the transaction fields"? 

  • Did the issues impact only the Blue Sheet reporting data, or did it also cause problems with (or perhaps originated from) their transaction and accounting systems? 


Well, since this is now a settled matter, there will be no further inquiries by the authorities, so it's unlikely that we'll have those answers. 

Bravo! This fecklessness is well deserving of the inaugural DISSY AWARD!   
   

Electronic Blue Sheets (EBS) | FINRA.org:  

Electronic Blue Sheet (EBS) data files, which contain both trading and account holder information, provide regulatory agencies with the ability to analyze a firm’s trading activity. Firms are expected to provide complete, accurate and timely Blue Sheet data in response to regulatory requests. Incomplete, inaccurate and untimely Blue Sheet data compromises regulators’ ability to identify individuals engaging in insider trading schemes and other fraudulent activity.   

© 2035 by T.S. Hewitt. Powered and secured by Wix

bottom of page