DNB statistical reporting — BSI, MIR and AnaCredit
De Nederlandsche Bank does not collect statistics for its own sake — it acts as a Eurosystem national central bank, feeding the ECB’s harmonised monetary-and-financial statistics that underpin euro-area monetary policy. The headline returns are BSI (Balance Sheet Items) and MIR (monetary financial institutions’ interest-rate statistics), sitting alongside AnaCredit for institutions in scope. This piece walks through what each return captures, the legal basis and who actually files, the reporting population and its derogations, where the mapping work concentrates, and — with worked examples — how BSI reconciles with FINREP and AnaCredit in practice.
1. What DNB statistical reporting is
DNB is the National Central Bank (NCB) in the Eurosystem statistics framework. Monetary financial institutions (MFIs) resident in the Netherlands report their balance-sheet positions and interest rates to DNB, which validates the data and transmits aggregates to the European Central Bank. The data feeds the ECB’s monetary aggregates, the analysis of credit and deposit conditions, and — through the interest-rate statistics — the monetary-policy transmission analysis. This is statistical reporting, legally and operationally separate from prudential supervision: the same underlying ledger feeds it, but the framework, taxonomy and deadlines differ from the supervisory returns.
2. Legal basis
The framework is set in ECB regulations, applied nationally by DNB:
- Regulation (EU) 2021/379 (ECB/2021/2) — the recast ECB regulation on the balance sheet items of credit institutions and of the MFI sector (it replaced the earlier Regulation (EU) 1071/2013). This is the current BSI legal basis.
- Regulation (EU) 1072/2013 (ECB/2013/34) — the ECB regulation on MFI interest-rate statistics (MIR), as amended.
- Regulation (EU) 2016/867 (ECB/2016/13) — AnaCredit, for institutions holding in-scope credit.
- Guideline (EU) 2021/830 (ECB/2021/11) and successors — the ECB guideline on BSI and interest-rate statistics that DNB implements.
- DNB reporting policy notices and the Dutch statistical-collection powers that give the returns domestic legal force.
3. The reporting population — and the “tail” derogation
The reference reporting population is the MFI sector: credit institutions, money market funds and other resident financial institutions that take deposits and/or issue close substitutes and grant credit. EMIs are treated as part of the MFI sector for statistical purposes; payment institutions come in where DNB designates them based on their balance-sheet profile. Crucially, the BSI regulation lets NCBs grant derogations to small institutions — the “cutting-off-the-tail” mechanism — so the smallest MFIs report a reduced set or at lower frequency, provided the tail still accounts for a capped share of the national balance-sheet total. The practical consequence: your exact obligation is not “the full BSI” by default — it is what DNB assigns you in the reporting population, and that can be a reduced return.
4. Who files which returns
| Firm type | BSI | MIR | AnaCredit |
|---|---|---|---|
| Credit institution | Full | Full | Full where in scope |
| EMI | Full or reduced (per derogation) | Where interest-bearing business exists | Where holding credit |
| Payment institution | Where designated by DNB | Where relevant | Where holding credit |
| Money market fund | Full (separate MMF taxonomy) | — | — |
| Other MFI-sector entities | As designated by DNB | Where applicable | — |
5. Balance Sheet Items (BSI) — what is captured
BSI captures the month-end balance-sheet positions of the MFI, broken down along the ECB’s harmonised dimensions:
- Assets — loans, holdings of securities, equity, remaining assets, with counterparty sector and country breakdowns.
- Liabilities — deposits (by type: overnight, with agreed maturity, redeemable at notice, repos), money market fund shares/units, debt securities issued, capital and reserves.
- Counterparty sector — every counterparty carries an ESA 2010 sector code (for example S.11 non-financial corporations, S.121 the central bank, S.122 deposit-taking corporations, S.14 households).
- Maturity — original-maturity bands for the relevant instruments.
- Currency — euro versus non-euro splits.
- Adjustment data — reclassifications and revaluations, so the ECB can derive transactions (flows) from the change in stocks; a fall in a loan stock caused by a write-off or an FX move must not be read as a repayment.
6. MIR — interest-rate statistics
MIR captures the interest rates MFIs apply to euro-denominated deposits from and loans to households and non-financial corporations resident in the euro area — split between new business (rates on business agreed in the reference month) and outstanding amounts (the rate on the stock), by instrument category and maturity/notice band, with the associated business volumes. For a Dutch PSP that neither lends nor pays interest on customer balances, the relevance is limited; for one that pays interest on wallet-like accounts or extends credit, the MIR obligation bites on that subset of business, and the rate definitions (annualised agreed rate) must be applied consistently with the ECB manual.
7. Cadence, channel and revisions
- BSI: monthly, reference date end of month, submitted on the DNB reporting calendar (typically within roughly a fortnight of month-end).
- MIR: monthly, reference date end of month, on a comparable timeline.
- AnaCredit: monthly (and quarterly attributes) — see our AnaCredit piece.
- Channel: via DNB Digitaal Loket Rapportages (DLR) in XBRL, against the DNB-published taxonomy aligned to the ECB framework.
- Revisions: DNB accepts and expects corrections; a wrong figure discovered later is restated in the next cycle rather than left standing.
8. How it plays out — three worked examples
Scenario A — an EMI misclassifies a corporate counterparty.
- Facts: A Dutch EMI books safeguarded client float and codes a large corporate client as a household (S.14) in its customer master.
- Rule: BSI requires the ESA 2010 sector code on every counterparty; the household-versus-non-financial-corporation split feeds the ECB deposit aggregates.
- Action: Fix the sector code at source in the customer master, not in a spreadsheet on the way out, and restate the affected months.
- Outcome: The deposit breakdown reconciles; the same corrected master also serves AnaCredit and any FINREP counterparty analysis, so the fix pays off across returns.
Scenario B — a loan write-off read as a repayment.
- Facts: A loan stock drops by EUR 2m month-on-month, but EUR 1.5m of that is a write-off, not customer repayment.
- Rule: BSI adjustment data separates reclassifications and revaluations from genuine transactions so the ECB derives true flows.
- Action: Report the EUR 1.5m as a revaluation/write-off adjustment rather than letting the raw stock change imply a EUR 2m repayment flow.
- Outcome: The derived lending-flow statistic is correct; skipping the adjustment would have overstated repayments in the euro-area credit data.
Scenario C — a growing PI crosses into designation.
- Facts: A payment institution that never filed BSI grows its balance sheet and starts holding credit balances that look MFI-like.
- Rule: DNB designates PIs into the reporting population based on their profile, and the tail derogation is size-dependent.
- Action: Engage DNB proactively, confirm the assigned return and any derogation, and stand up the counterparty-sector and maturity mapping before the first live filing.
- Outcome: The firm files a correct first return instead of discovering the obligation after a missed deadline.
9. Where the mapping work concentrates
- Counterparty sectoring — every counterparty needs an ESA 2010 sector code; integrating this into the customer master is the long pole and the most common source of error.
- Maturity bands — internal systems often track maturity differently from the ECB-required original-maturity bands.
- Currency split — euro versus non-euro must be clean at instrument level.
- Flows versus stocks — the reclassification/revaluation adjustments are where firms most often get the derived transactions wrong.
- Inter-MFI reconciliation — claims and liabilities against other MFIs must square across reporters; DNB cross-checks across the sector and queries persistent mismatches.
10. Data quality and its supervisory shadow
DNB’s data-quality bar is high and it produces feedback per reporting agent. Persistent statistical-quality problems do not stay in the statistics department — they feed the supervisor’s picture of a firm’s data governance and can shape inspection planning. In practice, building a documented reconciliation between BSI, FINREP and the audited financial statements is not optional: it is the control that lets you answer a DNB query quickly and demonstrates that the numbers are governed rather than assembled by hand each month.
11. FAQ
Which regulation is the current BSI legal basis?
Regulation (EU) 2021/379 (ECB/2021/2), the recast balance-sheet-items regulation, which replaced Regulation (EU) 1071/2013. MIR remains Regulation (EU) 1072/2013 (ECB/2013/34), and AnaCredit is Regulation (EU) 2016/867.
Are EMIs and PIs really in BSI?
EMIs are part of the MFI sector for ECB statistical purposes and file BSI — full or reduced depending on the derogation DNB applies. PIs file where DNB designates them based on their balance-sheet profile. Confirm your assigned return with DNB rather than assuming.
What is the “cutting-off-the-tail” derogation?
The BSI regulation lets national central banks grant the smallest MFIs a reduced or less-frequent reporting obligation, provided the exempt “tail” stays within a capped share of the national balance-sheet total. It is why two similar-sized firms can face different BSI obligations.
How does BSI differ from FINREP?
FINREP is EBA-coordinated supervisory financial reporting; BSI is ECB-coordinated statistical reporting. They draw on the same ledger but feed different frameworks with different taxonomies and definitions. Both can apply to an in-scope Dutch PSP, which is exactly why reconciliation between them matters.
Why does BSI ask for reclassification and revaluation data?
So the ECB can derive true transactions (flows) from the change in stocks. A stock fall caused by a write-off, a reclassification or an exchange-rate move is not a repayment; the adjustment data strips those out so the monetary statistics reflect real economic flows.
Is this mandatory for AISPs?
Account information service providers do not hold client funds and typically fall outside the MFI sector for statistical purposes. Confirm your status with DNB at registration.
12. What to do, today
- Get your reporting-population assignment and any derogation from DNB in writing — build to the return you were actually given.
- Pull the current DNB XBRL taxonomy and pin the version against the reporting calendar.
- Put ESA 2010 counterparty-sector coding into the customer master at source so BSI, AnaCredit and FINREP all draw on one clean field.
- Map internal maturity to the ECB original-maturity bands, and get the reclassification/revaluation adjustment logic right so flows are derived correctly.
- Reconcile BSI against FINREP and the audited financials every cycle, and run dry submissions before the first live filing.
Related: DNB DLR channel · AnaCredit for payment firms · FINREP for non-bank PSPs · DAC8 XML reporting — the data build · CSSF legal reporting — the Z and W tables


