Building the CRS return — from onboarding to file
A CRS return is produced in January and determined at onboarding, twelve months earlier. Almost everything that makes the file correct — tax residence, self-certification, the account classification — is captured when the customer joins. Firms that treat it as a year-end reporting exercise spend January chasing information they could have collected in seconds at account opening, from customers who are far less inclined to provide it after the fact.
1. Are you in scope at all?
The threshold question for a payments business is whether it is a reporting financial institution, and for e-money firms the answer changed. Under the amended framework, an entity holding e-money for customers falls within the depository-institution definition subject to a defined test, with a carve-out for certain pass-through arrangements.
2. The work is at onboarding
Three things must be captured when the account is opened, and none of them can be reliably reconstructed later:
- Self-certification of tax residence, obtained from the account holder — and for entity accounts, of the entity’s classification and, where relevant, its controlling persons.
- Indicia — the address, telephone, standing instructions and similar data that suggest a residence, against which the self-certification is tested for reasonableness.
- Tax identification numbers for each reportable jurisdiction, in the correct format.
The reasonableness test is the part most often skipped. A self-certification that conflicts with the indicia the firm already holds is not a completed step; it is an inconsistency requiring resolution, and accepting it unresolved is the defect that surfaces years later as an incorrect residence on a filed return.
3. Building the population
The annual population is the set of reportable accounts — accounts held by persons resident in a reportable jurisdiction, or by entities with controlling persons so resident. Constructing it has three steps and one recurring failure:
| Step | Output | Failure |
|---|---|---|
| Classify each account | In scope or out | Product types never classified because they launched after the framework was built |
| Determine residence | Reportable jurisdictions per holder | Self-certification missing, or contradicted by indicia and never resolved |
| Look through entities | Controlling persons where required | Entity classification treated as a formality at onboarding |
The first row is the one to design against. A product launched mid-year with no CRS classification does not announce itself at reporting time — it simply does not appear, and the return is short with nothing to indicate it.
4. The annual cycle
The mechanics are the ordinary reporting shape, with one distinctive feature: the reference period is the calendar year and the file is built after it closes, so the extract is a full-year population with year-end balances rather than a point-in-time snapshot.
Sequenced sensibly, the year looks like this: run the completeness checks on self-certification and tax identification coverage during the year, not in January; freeze and pin the population after year end; build and validate; file through the national channel; and archive the file, the extract and the acknowledgement keyed to the reporting year.
Running the coverage checks quarterly is the single highest-value change available. Missing data found in October can still be collected from an engaged customer; the same gap found in January is a chase against a deadline.
5. A worked case
Facts: a firm discovers in January that a material share of its customer base has no self-certification on file, because the onboarding flow made it optional for a product launched mid-year.
What the options are: none of them good. Filing without the data misstates the return. Chasing customers in January produces a low response rate. Deriving residence from indicia alone is not the same thing as a self-certification and does not discharge the requirement.
What the practitioner does: for the current year, documents the gap, its size and the remediation plan — because a disclosed limitation is a controlled outcome and an undisclosed one is a finding. For the future, makes self-certification a blocking field in onboarding for every product, and adds a quarterly coverage report that reconciles the account population against the certification population. The gap is then a number someone watches rather than a discovery.
FAQ
When is the real work done?
At onboarding. Self-certification, indicia and tax identification numbers determine the return, and none of them is reliably collectable a year later.
What if self-certification conflicts with what we hold?
That is an inconsistency to resolve, not a completed step. Accepting it unresolved produces an incorrect residence on the return.
What is the most common cause of a short return?
A product launched without a CRS classification. It never appears in the population, and nothing in the output indicates the omission.
Related: CRS for EMIs · DAC7 platform reporting · CARF and DAC8
