At a glance

1. A Swiss SRO application is a supervisory admission file, not a short registration form. The applicant must show what it does, who owns and controls it, who runs the AML framework and how the business will comply after admission.

2. FINMA recognises and supervises self-regulatory organisations. The SRO supervises its affiliated financial intermediaries and advisers for compliance with the Swiss Anti-Money Laundering Act. SRO membership is not a FINMA banking, securities or prudential licence. [1]

3. The exact checklist depends on the selected SRO and the applicant's activity. Current official forms from PolyReg, ARIF and VQF nevertheless reveal a common core: corporate evidence, ownership and group structure, personal files for responsible people, a precise business description, AML governance, training, audit arrangements and signed declarations. [2, 3, 4]

4. A polished policy manual cannot rescue an unclear operating model. The SRO needs to understand the clients, countries, products, transaction flows, control over assets, outsourced functions and systems that will exist when the business launches.

5. The quickest application is usually the one that is complete before submission. Missing criminal-record extracts, unsigned forms, stale register documents, unexplained shareholders, generic transaction diagrams and unappointed AML or audit functions create avoidable follow-up rounds.

6. The practical objective is an application data room that tells one consistent story across the commercial register, website, contracts, business plan, AML risk assessment, procedures and banking file.

Founders often search for a “Swiss SRO licence checklist” expecting a fixed list of documents. No universal pack exists. Each FINMA-recognised SRO applies its own statutes, regulations, admission forms, fees and supervisory model. The right approach is to build a common regulatory file first, then adapt it to the selected SRO's current forms.

This guide turns the official requirements into a pre-filing work plan for payment, foreign-exchange, fiduciary, crypto and other para-banking businesses. It focuses on the evidence that should exist before an application is signed.

1. Confirm that SRO affiliation is the correct route

Professional financial intermediaries under Article 2 paragraph 3 AMLA, and covered advisers under the relevant adviser provisions, must affiliate with a FINMA-recognised SRO where they are not supervised through another applicable regime. The SRO specifies the detailed AML duties in regulations approved by FINMA and monitors implementation through reporting, reviews and periodic audits. [1]

That does not mean every Swiss fintech belongs in the SRO route. The service map must first rule out a separate authorisation. Deposit-taking, securities services, portfolio management, payment models using a settlement account, custody structures and token activities can raise questions under legislation beyond AMLA.

If the business model is uncertain, resolve the uncertainty before the operating company signs client contracts or begins professional financial-intermediary activity. VQF's published guidance recommends a detailed description of activities for an applicability enquiry and notes that a legal assessment or FINMA non-action request may be appropriate in individual cases. [2]

2. Select the SRO before finalising the application pack

FINMA maintains the current list of recognised SROs. Recognition confirms the organisation's supervisory status; it does not make every SRO commercially identical. Admission process, language, sector experience, digital submission, auditor model, training, fee structure and appetite for the applicant's activity can differ. [1]

Run the selection exercise before tailoring the policies. The application should use the selected SRO's vocabulary, forms and control expectations. Filing the same generic pack with several organisations can create inconsistent answers and duplicate cost.

For a detailed route comparison, see Which Swiss SRO Should You Join?. The choice should follow the operating model. It should not be made only on the lowest published admission fee.

3. Build the corporate and ownership file

The corporate folder proves the applicant's legal existence and identifies the people and entities behind it. PolyReg's application materials request company details, legal form, Swiss and foreign places of business, certified statutes, a business plan and a current commercial-register extract where applicable. ARIF requests the application form, register evidence and disclosure of legal or business links that exert a dominant influence or create a group. [3, 4]

Prepare the ownership chart from the applicant upwards to the ultimate natural persons. Show direct and indirect percentages, voting rights, special control rights, nominee or fiduciary relationships and connected companies. The chart should agree with shareholder registers, incorporation documents and beneficial-owner declarations.

Corporate changes made during review should be controlled. A last-minute new shareholder, director, office or business line can invalidate signed declarations and force the reviewer to reassess the file.

4. Prepare personal files for directors, owners and AML roles

SROs assess the people who own, direct and operate the applicant. The exact population and thresholds differ by form. PolyReg's published materials request identity, CV, relevant qualifications, criminal-record evidence and personal statements for specified responsible persons. ARIF's checklist extends personal-file requirements to management and people involved in AMLA-relevant business, including the AML officer, subject to its directive. [3, 4]

Create one indexed folder per person. Use the spelling and nationality shown in the passport throughout the application. Explain gaps, overlapping roles, other mandates and past regulatory, criminal, insolvency or disciplinary matters openly. A declaration that conflicts with public records is more damaging than a properly explained historical issue.

5. Describe the business model at transaction level

“Crypto services”, “payments” or “financial consulting” is not an adequate business description. The SRO needs enough detail to classify the activity and understand the AML exposure. PolyReg's current form asks for a precise activity description and identifies categories such as currency exchange, payment transaction services, money transfer, lending, fiduciary activity and transport or safekeeping of assets. [3]

Prepare a separate flow for every product. Each flow should show the customer, contracting entity, bank, payment provider, exchange, custodian, wallet, liquidity provider and settlement leg. Mark who can initiate, approve, redirect, freeze or reverse a transfer. State whether the applicant ever receives fiat or crypto into an account, wallet or address it controls.

For each service, answer these questions:

• Who is the customer and which entity signs the contract?
• Which countries are targeted, accepted or prohibited?
• What asset or value moves, from whom, to whom and through which accounts or wallets?
• Does the applicant have legal or technical power of disposal?
• Which third parties perform onboarding, screening, custody, exchange, banking or settlement?
• How does the company earn revenue and when is the fee deducted?
• What volumes, transaction sizes, customer numbers and corridors are expected in year one?
• Which unusual scenarios can occur, and who stops or escalates them?

6. Appoint the AML function before filing

The application should identify who owns AML compliance inside the company. VQF's published FAQ states that an affiliated company appoints an AML officer who implements the AMLA framework, monitors internal directives and acts as a contact with the SRO and MROS. It also describes specialist-knowledge and training expectations and notes higher requirements for virtual-asset service providers. [2]

The selected SRO's rules determine whether a deputy is required, which functions may be outsourced and what independence or location expectations apply. Do not copy a role chart from another SRO. Confirm the current rule and document any outsourcing agreement, access rights, reporting line and escalation authority.

The AML responsibility matrix should cover:

• client acceptance and risk approval;
• identification and beneficial-owner verification;
• PEP, sanctions and adverse-information screening;
• enhanced due diligence and source-of-funds or source-of-wealth review;
• transaction-monitoring alerts and case closure;
• suspicion escalation and MROS reporting;
• record retention and file quality;
• staff training and testing;
• regulatory reporting and change notifications; and
• audit preparation and remediation.

Names alone are insufficient. The role holder should have time, access to data, authority to stop onboarding or transactions, and a route to the board.

7. Draft an AML framework that matches the product

FINMA explains that AMLA duties include identifying contracting parties and beneficial owners, clarifying unusual or higher-risk relationships and transactions, maintaining records and reporting relevant suspicions. SRO regulations translate those duties into controls for their members. [1, 5]

The procedures submitted with the application should therefore be usable from the first client. Replace generic statements with thresholds, decision owners, data sources, forms and evidence. If the policy says “high-risk customers require enhanced checks”, define how risk becomes high and what enhanced work is performed.

For a crypto model, add wallet ownership and control, blockchain analytics, hosted and unhosted wallet treatment, transaction traceability, asset-risk rules, Travel Rule operations where applicable, and the response to sanctions exposure. The written controls should match the technical product that will launch.

8. Set the audit and training model

SRO affiliation creates continuing supervision. FINMA notes that SRO rules provide for monitoring through periodic internal or external checks and allow sanctions for breaches. VQF publicly describes risk-based audit cycles and mandatory training as ongoing membership obligations. The exact cycle and auditor arrangement remain SRO-specific. [1, 2]

ARIF's published checklist requests acceptance of the audit mandate by an approved AML auditor. PolyReg's materials describe the information required where the applicant proposes its own approved auditor. These examples show why the audit route must be settled during the application rather than after admission. [3, 4]

Before filing, confirm:

1. which audit firm or audit pool will cover the member;
2. whether a signed auditor acceptance is required;
3. the expected audit scope, cycle and fee basis;
4. which staff need basic and continuing AML training;
5. whether external courses require SRO recognition; and
6. how findings, remediation and board reporting will be tracked.

9. Assemble the application data room

A numbered data room reduces inconsistent submissions and makes follow-up questions easier to answer. Keep a clean submission version and a working version with comments. Record the date, signer, language, certification and expiry of every document.

Apply one naming convention, for example folder-document-entity-date-version. A document register should identify any item that expires during review. Criminal-record extracts and commercial-register evidence often need special attention because current official checklists impose age or original-document requirements. [3, 4]

10. Run a pre-submission challenge

The final review should be performed by someone who did not draft the file. Their task is to find contradictions and missing operating detail.

11. What usually delays an SRO application?

Delays often start before the reviewer opens the policy manual. The recurring causes are an incomplete form, unpaid admission fee, missing original or current personal documents, an ownership structure that cannot be reconstructed, and an activity description that changes across the business plan, website and contracts.

Operational gaps create a second category of delay:

• the AML officer lacks relevant knowledge, time or authority;
• the product permits flows that the risk assessment does not cover;
• outsourcing contracts do not give the applicant access or oversight;
• country and customer restrictions are asserted but not implemented;
• the monitoring process is postponed until after admission;
• audit and training arrangements remain undecided; or
• the SRO route is being used to describe an activity that may need another licence.

ARIF states that its normal decision timing begins once the file is complete and the first membership fee is paid; a more detailed review can lead to an interview. VQF states that review begins after the applicable processing fee and complete required documents are received. These examples support a simple planning rule: measure the timeline from completeness, not from the day the project starts. [2, 4]

12. A practical filing sequence

Swiss SRO application checklist

1. Confirm that the activity falls within AMLA and that SRO affiliation is the correct route.
2. Select a FINMA-recognised SRO that accepts the actual business model.
3. Download the SRO's current forms, regulations, guidance and fee rules.
4. Prepare current corporate, register, ownership and group evidence.
5. Create complete personal files for all people captured by the selected application.
6. Document every service, customer type, country, provider and transaction flow.
7. Appoint the AML officer and any deputy or authorised access person required by the SRO.
8. Approve the enterprise risk assessment and product-specific AML procedures.
9. Contract screening, monitoring, custody, banking and outsourced compliance providers.
10. Agree the audit model and obtain an auditor acceptance where required.
11. Complete required training and retain certificates or confirmed bookings.
12. Run sample onboarding, enhanced review, monitoring and escalation cases.
13. Check dates, signatures, certifications, translations, originals and fee receipts.
14. Submit one controlled version and maintain a question-and-response log.
15. Do not change the operating model during review without assessing and disclosing the impact.

Frequently asked questions

Is Swiss SRO membership a financial licence?

SRO membership is an AML supervisory affiliation. The member is supervised by the SRO for compliance with AMLA; FINMA recognises and supervises the SRO. Membership does not itself authorise banking, securities, deposit-taking or another prudentially regulated activity. [1]

Which documents are required for a Swiss SRO application?

The exact list depends on the selected SRO and applicant. The common core includes application forms, corporate and register evidence, ownership and group information, personal files for responsible people, a detailed business description, AML organisation and procedures, audit arrangements, training evidence, declarations and fee payment. Use only the selected SRO's current checklist.

Do I need an AML officer before applying?

The application should identify the person responsible for AML implementation and communication with the SRO. Role, deputy coverage, training, access and authority depend on the SRO and business model. VQF's current guidance expressly requires an AML officer for affiliated companies. [2]

Can the AML officer be outsourced?

Some arrangements can involve external specialists, but the SRO's rules and the operating model determine what can be delegated. The company remains responsible for adequate organisation, access, oversight and implementation. Confirm the proposed arrangement with the selected SRO before filing.

How long does SRO admission take?

There is no universal timeframe. Completeness, business complexity, ownership, responsible persons, interview or committee schedules and follow-up questions all matter. ARIF currently states that a complete, paid file is normally decided in less than 30 days, while more detailed review may require an interview. This should not be treated as a market-wide promise. [4]

Does a crypto company need more than SRO membership?

Possibly. Exchange, transfer and certain custody models may fit an AMLA/SRO route, while deposits, securities, payment accounts, collective investment or other services can trigger separate Swiss regulation. The decision depends on the contractual and technical flow.

Should banking be arranged before or after the application?

Regulatory and banking work should be coordinated. The bank will often ask for the same ownership, product, flow and AML evidence. Waiting until admission to test banking feasibility can reveal that the approved model cannot operate through the available account or settlement structure.

Related DM Strategy guides

• Swiss SRO License Requirements in 2026, covering directors, AML responsibility, substance and capital questions.
• Swiss SRO Membership Cost and Process, covering admission, annual, audit and training costs.
• Which Swiss SRO Should You Join?, comparing selection factors before filing.
• Swiss Crypto Licence Routes, comparing SRO membership, the FinTech route and banking authorisation.
• Swiss SRO Membership for Advisers, explaining the October 2026 AMLA reform and transitional application rules.
• Swiss SRO Membership, outlining DM Strategy's structuring and application support.

Key primary sources

Disclaimer

This article is for information only and is not legal, tax or regulatory advice. SRO forms, fees, document requirements and supervisory practice can change. The correct route depends on the applicant's services, control of assets, customers, countries, structure, people and other Swiss regulatory requirements.

DM Strategy helps founders classify the Swiss model, select an SRO, organise the application data room, prepare the operating evidence and coordinate licensing with banking. If you are preparing a Swiss payment, crypto, fiduciary or adviser business, book an introductory call with DM Strategy before filing a generic application that does not match the product.