External-sector reporting compared across the EU
External-sector reporting is the obligation most groups discover through a letter, because it attaches to residents rather than to licences. Every euro-area member state collects data on cross-border transactions and cross-border positions to build its balance of payments. The obligation reaches ordinary companies with no financial licence at all — which is why, in a fintech group, the entity that gets missed is almost never the licensed one.
1. Flows and stocks: the universal split
Every one of these regimes separates two questions, and a firm can be inside one and outside the other:
| Question | Spain | Germany |
|---|---|---|
| Flows — what crossed the border? | Reported within the ETE transactions limb; for registered PSPs, through the DTE | Z4 and the related payment reports |
| Stocks — what do we hold and owe? | The ETE assets-and-liabilities limb | Z5, Z5a, Z5b |
| Threshold logic | Bands: monthly at EUR 300m, quarterly at EUR 100m, annual below, request-only under EUR 1m | A flat exemption for payments up to EUR 12,500 |
2. Why the ledger, not the payments system
The strongest common thread across these regimes is that the payments system is the wrong source, for two independent reasons.
First, stocks are not payments. An intragroup loan balance, a receivable or an equity holding is a position, and it appears only on the balance sheet. Spain’s band test can put an entity into monthly reporting on the balance limb alone, even with negligible transaction volume.
Second, some flows are not payments either. The German definition expressly includes set-offs and compensations alongside transfers, direct debits, cheques, bills of exchange and cash. A netted intercompany settlement moves value across a border without producing a payment instruction, and a process built from payment messages cannot see it.
3. Residence is the field that decides everything
What makes an item external is the residence of the counterparty — not the currency, not where the bank account is held, and not the invoice address. This is the single most common data gap in the whole family, because general ledgers routinely carry counterparty name and account without carrying residence as a maintained field.
It cannot be inferred reliably from an IBAN prefix: an account at an institution in one country tells you nothing dependable about where its holder is resident. Where the information exists at all in a fintech group, it usually exists in the customer due-diligence record and has simply never reached the ledger — which makes the fix a data-plumbing exercise rather than a collection exercise.
4. The perimeter trap, and the carve-out
Two scoping features recur and pull in opposite directions.
The trap is that the obligation follows residence, so every resident entity in a group has its own answer — including holding companies, service companies and property-owning subsidiaries with no financial activity and no reporting team. Those are the entities nobody assigns an owner to.
The carve-out is that a licensed payment firm may be excluded from the general survey precisely because it reports through a dedicated channel. Spain’s Circular 4/2012 applies to residents other than payment service providers registered in the Banco de España’s official registers — so the licensed entity is out and the group’s non-PSP Spanish entities are squarely in. A group that concluded “we are a PSP, so this does not apply to us” has answered the question for one entity and left the rest unanswered.
5. Building it once
Facts: a group has licensed entities in Spain and Germany, plus a Spanish holding company and a German service company, and settles part of its intragroup position by netting.
What the analysis produces: four separate scoping answers, not two. The licensed entities are assessed against the dedicated PSP channel in Spain and the AWV in Germany. The two unlicensed entities are assessed against the general regimes — and the Spanish holding company is inside the survey precisely because it is not a registered PSP.
What the practitioner does: builds one extract per resident entity from the general ledger, carrying counterparty residence, instrument type and both flow and position data; then renders it per market. Because the frequency bands are set by the prior year in Spain, the coming year’s obligation is knowable each January — which makes this a planning exercise rather than a surprise, provided somebody runs the test.
FAQ
Does external-sector reporting apply to unlicensed entities?
Yes. It attaches to residents, so holding companies, service companies and similar entities can be in scope with no licence and no supervisor.
Why can’t we build it from the payments system?
Because stocks are positions rather than payments, and because some in-scope flows — set-offs and compensations in the German definition — never produce a payment instruction.
What is the key missing field?
Counterparty residence. It decides what is external, it cannot be inferred from an IBAN prefix, and most ledgers do not maintain it.
Related: The Spanish ETE · German AWV reporting · The Spanish DTE
