Operating contexts

The same statute reads differently in a payments file and in a warehouse office.

Sectors are not marketing labels. They change onboarding data, supervision intensity, and what “good evidence” looks like. This page states who the practice is built for and who it is not.

Dossier 04
Sectors

Financial and value-moving businesses

Payment facilitators, forex and investment intermediaries, and teams exploring crypto-asset or e-money pathways. Typical work: AML programme, licensing condition map, bank questionnaire support. Start with AML / CFT.

Trade, logistics and import-export offices

Companies that look ordinary until a counterparty asks for beneficial-ownership, sanctions screening and data-processing terms. Typical work: screening logic, contract annexes, a defensible KYC file for key buyers.

Professional and client-file businesses

Consultancies, agencies and firms that store identity and financial data of clients. Typical work: processing records, access-request path, processor overlay. See data protection.

Licensed and permit-heavy operators

Activities that cannot be “tried and regularised later”. Typical work: condition tracker, change control, application hygiene. See licensing.

Who this practice will decline

Requests to backdate controls, conceal facts from a supervisor, or present consulting output as an official certificate. Anonymous “guarantee of approval” work. Mandates that require a courtroom advocate or a statutory auditor. If the matter is a legal dispute, you need counsel; this desk can still map the operational file that counsel will use.

If you are unsure which sector box you sit in, write the activity in plain language on the briefing form. The first reply is a fit check, not a sales script.