Point Nine: managed regulatory reporting for brokers and institutions

Point Nine is a specialist managed trade and transaction reporting provider. The operating business, Point Nine Data Trust Limited in Cyprus, serves banks, brokers, investment managers, funds and corporate counterparties. Its role is to turn trading records into regulatory submissions and to help operate the reporting process after submission. It is separate from both the Point Nine venture-capital firm and MUFG’s acquired middle- and back-office business.[1]

The service combines proprietary technology with reporting operations. It receives source records, adds required reference data, applies validation, prepares submissions and processes repository or reporting-mechanism feedback. For a brokerage, this puts execution data, lifecycle events and regulatory reporting in one operational chain; the reporting service itself does not supply trading liquidity or execute the customer’s orders.[3]

Point Nine accepts structured trading data rather than requiring the broker to re-key every regulatory field. Its stated input formats include CSV, XML and FpML, alongside APIs. The practical integration therefore depends on the broker’s available trade, counterparty and lifecycle records, with Point Nine applying the reporting transformation and enrichment.[3]

MiFIR instrument eligibility is an ongoing data task. Point Nine says it takes daily FIRDS delta files and weekly full files from ESMA and the FCA, re-evaluates reportability and alerts clients when an instrument changes status. The portal also permits inclusion or exclusion decisions. This is useful when an instrument’s reporting status changes after a broker first adds it to the trading catalogue; it does not make an incorrect instrument classification harmless.[10]

Point Nine uses a sales-led commercial process. The inspected service presentation offers a demonstration and discussion, but no public per-trade tariff, monthly minimum or standard implementation charge. A broker’s actual price and contracted regime coverage therefore come from its proposal and service agreement. The presentation’s infrastructure and availability claims should be read with the contracted service levels, rather than treated as a price-backed universal guarantee.[4]

The public Terms of Service page is a website-use document. It is not a substitute for the managed-service agreement on termination, liability, reporting responsibilities, service credits or the treatment of historical data. Those commercial terms are not disclosed in that page, so this profile does not invent a standard minimum term or cancellation period.[18]

The published onboarding approach starts with the client’s actual trading flow: how orders pass through the chain, who makes investment and execution decisions, and how the relevant fields are populated. Point Nine describes validation at import, after enrichment and before ARM submission. This matters for brokers because a technically valid file can still describe the wrong transaction chain or decision-maker.[11]

These controls support two distinct questions: whether the submission was accepted and whether it accurately reflects the transaction. An operations team can use the exception view for unresolved items while retaining the historical view for investigation. The reported refresh window also means that a recently corrected item may remain visible until the dashboard catches up.[12]

Point Nine’s service is supported by a managed reporting team and account contacts. Portal access changes are handled through that team or the account manager. The July 2026 release distinguishes Standard users from View-Only users more strictly than the label alone suggests: viewing a report does not carry permission to download it.[13]

The August 2026 table-view release allows each user to choose visible columns and their order for EMIR, MiFIR and SFTR tables. Saved layouts survive logout; an indicator shows when the layout differs from the default, which can be restored. These are personal presentation preferences, separate from the account permissions that determine whether the user may change or export data.[14]

Delegated reporting does not make the technology provider the regulator or repository. The FCA’s UK EMIR guidance permits reporting through a third party but requires submission to a registered or recognised trade repository. It also assigns legal responsibility to particular counterparties or managers in specified circumstances. A Point Nine engagement must therefore fit the client’s applicable reporting responsibility; the act of outsourcing alone does not settle who is legally liable.[23]

Instrument scope is equally important for FX firms. FCA Market Watch 74 expressly states that spot FX is not a MiFID financial instrument and identifies incorrect inclusion of spot-FX instruments in FIRDS as a source of erroneous transaction reporting. A broker should not treat every product carrying an FX label as identical for reporting purposes. Point Nine’s eligibility controls address the operational classification problem; they do not replace the underlying scope rules.[24]

Point Nine’s history traces its technology work to 2002 and its EMIR reporting platform to 2015. Its current About page describes the 2019 separation of the reporting business from the former Point Nine operation acquired by MUFG. This history concerns the evolution of the business; it should not be used to imply that today’s Cyprus entity has existed under the same legal identity throughout that period.[2]

Operator

Point Nine Data Trust Limited

Service scope

Managed trade and transaction reporting, enrichment, validation, submission and reconciliation.

Customer types

Brokers; Banks; Asset managers; Funds; Corporate counterparties

Delivery

Managed service; SaaS; API

Pricing publication

Quote only

Headquarters

Nicosia, Cyprus

Integrations

SFTP; Amazon S3; Database interfaces; FIS Trade and Transaction Reporting Manager

Implementation

Source-data mapping and staged validation, with portal and automated ingestion routes.

Support

Managed reporting operations, account contacts and request-based portal permissions.

Permissions and regulatory scope

Reporting technology and managed operations; repository and ARM roles remain distinct, and client reporting responsibility follows the applicable regime.

Provider metadata checked 20 Oct 2026Source 1Source 3Source 4Source 7Source 8Source 11Source 13Source 23Source 20

Bulk export is available from Jobs for input and output CSV/XML files, with date, integration, file-type, filename and workflow filters. The published limit is 100 workflows per export. Users can combine outbound CSV output and select historical records, and are notified when the download is ready. Scheduled reports can deliver input/output files and trade-repository end-of-day data to SFTP.[15]

The generated export files remain available for seven days in the portal or SFTP location before automatic expiry. That is a retrieval window for exported files, not a statement that the underlying reporting history is deleted after seven days. It makes an independent archive useful for a broker that needs to retain a particular reconciliation or migration extract beyond the download window.[15]

Point Nine also publishes reference tools for LEIs, instrument classification and reporting identifiers, including CFI, UPI and UTI utilities. These can help operations staff investigate identifiers and formatting before a record reaches the managed reporting flow. A format or check-digit validation is not proof that an identifier was correctly issued, and a browser utility is not itself a regulatory submission or legal determination of a reporting obligation.[19]