Singapore MAS AE/RMO market operator application pack

Route focus

A market-operator application should prove whether the platform operates an organised market, whether AE or RMO is the right route, how participants access the market, how orders or interests are matched or routed, how market conduct and technology risks are controlled, and whether CMS dealing, custody, clearing, or product financing analysis is also needed.

Who this helps

• - Singapore trading venues, private market platforms, securities marketplaces, exchange-like fintechs, and tokenised securities platforms
• - Brokerage, fund distribution, or private placement platforms checking whether software has become an organised market
• - Existing CMS applicants adding matching, order book, RFQ, auction, bulletin-board, or venue-like features
• - Compliance, technology, operations, market surveillance, and risk teams preparing MAS source-led route evidence

Licence scope

• - Confirm whether the platform operates an organised market and whether the route is approved exchange, recognised market operator, CMS dealing, corporate finance, fund marketing, custody, product financing, clearing house, or software-only support.
• - Map users, products, order or interest submission, matching, routing, pricing, access rules, discretion, settlement, custody, clearing, market data, fees, outages, and participant communications.
• - Separate AE/RMO analysis from ACH/RCH clearing facility analysis, CMS dealing in capital markets products, custodial services, product financing, and financial advisory services.
• - Identify whether critical systems, APIs, cyber controls, surveillance, market-abuse controls, outsourcing, cloud vendors, incident reporting, and business continuity are ready enough for MAS review.

Pre-draft questions

• - Does the platform bring together buying and selling interest, set access rules, match orders, route orders, operate auctions/RFQs, or otherwise function like an organised market?
• - Which products trade or are displayed: securities, CIS units, OTC derivatives, exchange-traded derivatives, leveraged FX, private securities, tokenised securities, or non-capital-markets products?
• - Who owns market rules, participant admission, surveillance, fair access, trade controls, conflicts, technology resilience, incident reporting, clearing, custody, settlement, and complaints?
• - Does the platform itself deal, arrange, hold assets, finance positions, clear trades, advise participants, or only provide venue infrastructure?
• - Do platform diagrams, product specs, participant agreements, rulebooks, risk controls, website wording, MAS FID/register expectations, and official-source assumptions tell the same route story?

Evidence pack

People and governance

• - Market-operator readiness depends on rule-making, surveillance, technology, and conduct ownership, not only licensing labels.
• - Senior management should be able to explain when the platform is an organised market, when it is a broker/dealer or arranger, and when it is merely software.
• - If clearing, custody, product financing, or dealing is outsourced or handled by a participant, document who controls those steps and what happens when they fail.
• - Technology owners should be part of the application evidence when matching, access, APIs, market data, or outage management are core to the platform.

Forms and submission

• - Use MAS/GoBusiness AE/RMO licence information as the route anchor for organised-market analysis and MAS/GoBusiness ACH/RCH where clearing facility features are present.
• - Use MAS/GoBusiness CMS and MAS Form 1 if the same business also conducts dealing, custody, product financing, corporate finance, or fund management activity.
• - Prepare platform diagrams, rulebooks, participant agreements, technology-risk evidence, surveillance controls, outsourcing files, financial resources, and governance evidence before seeking adviser review.
• - After approval, verify licence type/status, market operator status, CMS activity overlap, and key personnel through MAS FID.

Timeline risks

• - The main delay is often route ambiguity: a product is described as software but the facts show organised-market, dealing, custody, clearing, or financing functions.
• - Weak market surveillance, participant access, rulebook, outage, cyber, vendor, or incident evidence can make the application look premature.
• - Clearing/custody/settlement details can force ACH/RCH, CMS custody, product financing, or dealing analysis into the route map.
• - Cross-border participants, retail access, private securities, tokenised securities, and automated matching need careful pre-submission source alignment.

Questions to ask advisers

• - Is the product an organised market, a broker/dealer platform, a private placement tool, a fund distribution portal, a custodian, a clearing facility, or software support?
• - Does the platform set rules, admit participants, match or route trading interest, produce prices, or control settlement?
• - Which route covers custody, clearing, dealing, product financing, advice, financial promotions, and market conduct?
• - What evidence proves technology resilience, market surveillance, fair access, financial crime controls, and participant complaint handling?

Common mistakes

• - Calling a matching or RFQ platform software without analysing organised-market triggers.
• - Adding settlement, custody, or financing features without updating the route map.
• - Treating market surveillance, fair access, outages, incident notification, and vendor controls as post-launch tasks.
• - Assuming a CMS dealing licence automatically solves AE/RMO or ACH/RCH questions.

Disclaimer

Information on LicenseCompare is for general educational purposes only and does not constitute legal, regulatory, financial, tax, investment, or professional advice. Licensing requirements depend on facts and change over time. Always consult official regulator materials and qualified professional advisers.