Reporting at market entry — the sequencing that works
Reporting is almost always scheduled after launch, and in at least two markets in this cluster that is already non-compliant on day one. Some obligations are preconditions to operating at all. Some enrolments carry deadlines that run from the commencement of activity rather than from a filing date. And the item with the longest lead time — channel access — is the one item whose duration you do not control. Sequencing, not effort, is what makes a market entry go cleanly.
1. What belongs before launch
| Item | Why it is a precondition |
|---|---|
| Connections that gate the product | In the Netherlands, connection to the reference portal is required before Dutch IBANs are issued — it gates the product, not the report |
| Enrolments with their own deadlines | Italy requires portal registration within 30 days of commencing activity; Germany’s AML registration duty binds whether or not any report is ever filed |
| Detection calibration | Where the host standard differs — the Dutch “unusual” threshold — retro-fitting means re-reviewing the whole period since launch |
| Customer-attribute capture | Residence, tax identifiers and connected-person roles must be captured at onboarding; collecting them later is a remediation programme |
2. The six-step plan
- 1. Inventory the obligations against four attachment rules — the authorised entity, residence of the reporting agent, where the activity is carried on, and the customer’s residence. The fourth is the one that catches firms with no establishment.
- 2. Start every enrolment immediately. It is the only task whose duration is set by someone else, and it gates testing as well as filing.
- 3. Fix the onboarding data model so the attributes the returns need are captured from the first customer.
- 4. Build the mapping against the specification applicable to the first reference date, not the current one if they differ.
- 5. Rehearse — a parallel run on a period you understand, and a test submission as early as the channel allows.
- 6. Assign owners by trigger type — calendar, threshold, lifecycle, suspicion, maintained state — because each needs a different control.
3. The three traps
Assuming the licence defines the perimeter. It does not. Obligations attaching to residence catch unlicensed group entities; obligations attaching to the customer catch firms with no establishment. Both are invisible from the authorisation file.
Assuming enrolment is one event. In Spain it is granted per reporting process, so a firm with six returns can face six enrolments — each with its own paperwork, and several with their own test environments.
Assuming language is a formality. In Germany, Italy and France, filings, specifications and supervisory correspondence proceed in the local language. That is a resourcing dependency with a lead time, and it bites hardest exactly when a specification changes mid-year.
4. A worked entry
Facts: an EMI plans to enter a new market in six months, with reporting scheduled to begin after launch.
What the analysis produces: a re-sequenced plan. Enrolment starts in month one, in parallel with licensing, because it is the binding constraint. The onboarding data model changes in month two, before any customer exists. Detection calibration is set to the host standard before the first transaction. The mapping and parallel run occupy months four and five. Launch happens with the reporting capability already tested rather than with a first submission still to attempt.
What that costs: almost nothing extra — the same work, done in a different order. The cost of the original sequence is a first filing attempted under deadline pressure, on a channel nobody has used, with data the onboarding process never captured.
5. After launch
One control matters more than the rest once you are live: an annual re-test of the perimeter. The obligations themselves are stable. What changes is whether you are inside them — and a new product, a new customer segment or organic growth into a neighbouring market can move a firm into a return with no regulatory event marking the change.
Reviewing the perimeter column of the obligations register is a short exercise with a high hit rate. Reviewing the whole register is a long exercise that usually confirms what you already knew.
FAQ
What must be done before launch?
Connections that gate the product, enrolments carrying their own deadlines, detection calibrated to the host standard, and the onboarding attributes the returns will need.
What has the longest lead time?
Channel enrolment. It is the only item whose duration the firm does not control, and it gates rehearsal as well as filing.
What is the cheapest high-value change?
Adding the required customer attributes — residence, tax identifiers, connected-person roles — to onboarding before the first customer. Afterwards it becomes a remediation programme.
Related: Reporting channels compared · Testing a new return · Home or host reporting
