AnaCredit Reporting in Germany: Bundesbank Credit Data and Deadlines

Subject to applicable reporting relief, AnaCredit covers qualifying instruments where a debtor’s aggregate commitment in relation to an observed agent reaches at least EUR 25,000 at a reporting reference date within the relevant reference period. Commitment includes outstanding nominal and off-balance-sheet amounts. From that threshold the loan is reported to the Deutsche Bundesbank on a named-borrower, named-loan basis, in XML, month after month, under Regulation (EU) 2016/867 of the European Central Bank (ECB/2016/13). The German implementation timetable provided for collection of counterparty reference data from January 2018 and selected credit attributes from March 2018, with the harmonised ECB data collection starting in September 2018, and the return sits next to a much older national one built for far larger exposures.

The Bundesbank runs the collection as its Kreditdatenstatistik. It is a statistical return, not a supervisory capital calculation, yet it feeds directly into how the ECB and national supervisors read credit risk across the euro area. Get the counterparty master data wrong, miss the sixth business day, or blur the line with the EUR 1 million Millionenkredit return under section 14 of the German Banking Act, and it is the reporting officer who fields the validation feedback.

Three areas call for particular attention: the debtor-level threshold, the split between monthly and quarterly data, and the boundary between AnaCredit and the national large-loan regime. Understanding how each one works is what keeps a reporting calendar clean.

Related reading: COREP Reporting Explained

Key dates and thresholds for AnaCredit in Germany

The calendar is fixed. The figures below are the ones a reporting team pins to the wall rather than recalculating each period.

• Reporting threshold: a debtor’s aggregate commitment in relation to an observed agent of at least EUR 25,000 at a reporting reference date within the reference period (Article 5).
• Monthly reference date: the last calendar day of each month.
• Monthly remittance, German-resident observed units: close of business on the sixth business day, extended to the ninth or twelfth business day only where the Bundesbank has granted a longer deadline.
• Monthly remittance, foreign-resident observed units: close of business on the fifteenth business day.
• Quarterly accounting data: due by 12 May for the first quarter, 11 August for the second, 11 November for the third, and 11 February of the following year for the fourth. Where a quarterly deadline falls on a statutory holiday, Saturday or Sunday, it moves to close of business on the following business day; consult the Bundesbank’s published AnaCredit deadline calendar for precise dates in any given year.
• Separate national return: the section 14 KWG Millionenkredit, threshold EUR 1,000,000, quarter-end reference dates, amount data due by the fifteenth business day of January, April, July and October.

The legal basis: ECB Regulation 2016/867 and the Bundesbank’s statistical order

AnaCredit rests on Regulation (EU) 2016/867 of the European Central Bank of 18 May 2016 on the collection of granular credit and credit risk data (ECB/2016/13). Article 3 defines the reporting population. The templates are set out in Annex I; attribute definitions appear in Annex IV. The procedures for collecting the data across the Eurosystem are set out in ECB Guideline ECB/2017/38.

The Regulation deliberately stops short of the operational detail. Article 13 specifies the reference dates and the arrangements for NCBs to transmit data to the ECB; Article 14 constrains the national arrangements. Within that framework, the deadlines and the file format for German reporters are specified in the Bundesbank’s own instruments: the statistical order for a credit data statistic (the statistische Anordnung einer Kreditdatenstatistik) and the accompanying rulebook, the Richtlinien zur Kreditdatenstatistik, published in the Bundesbank’s Statistical Special Publication 1 under the heading for reporting provisions and validation rules.

This division matters when a question comes up. If it concerns which instruments cross the threshold or which attributes exist, the answer is in the Regulation and the ECB Reporting Manual (which is explanatory and has no binding legal status; German filing obligations must also be read with the Bundesbank’s statistical order and applicable national reporting provisions). For any question about when a file is due, what the schema is called, or how the Bundesbank sends feedback, the starting point is the German rulebook rather than the Regulation.

AnaCredit is a statistical obligation owed to the ECB and the Bundesbank in their statistics role. It is distinct from the supervisory returns built on the Capital Requirements Regulation, even though it draws on the same loan book. The reporting agent definition, the reference to legal entities in Article 1(5), and the individual-basis requirement in Article 6 all belong to this statistical framework rather than to prudential own-funds reporting.

Who must report AnaCredit credit data in Germany

The German return is owed by credit institutions resident in Germany and by German-resident branches of credit institutions that are resident abroad. Those two populations transmit to the Deutsche Bundesbank. The reporting population in Article 3 of the Regulation is credit institutions, and the first phase of AnaCredit covers credit that credit institutions grant to legal entities.

Two categories change the filing answer more than any other. A reporting agent that is a legal entity reports in respect of all its observed agents, meaning the domestic part of the institution together with its foreign branches, subject to the coordination in Article 6(3) that operates as a mechanism to avoid the same data being collected twice when the legal entity and its branch both sit in reporting Member States. A reporting agent that is itself a foreign branch reports only its own activity as creditor or servicer. Where an institution has foreign branches located in the same country, German instructions aggregate them for filing purposes, meaning a physical branch office is not necessarily a separate observed-unit filing perimeter. Getting the observed-agent perimeter right is what determines how many separate credit-data files an institution has to build.

AnaCredit covers credit institutions only, and the current phase’s scope does not extend to every kind of financial firm. Other deposit-takers that are not credit institutions, asset-management vehicles and other financial corporations that grant credit sit outside the current population and could be brought in only in a later phase, adopted at least two years before it applies. An investment firm without a banking licence is not an AnaCredit reporting agent today. Natural persons are also outside the first phase as debtors, so no personal data of individual borrowers is collected. The exclusion covers instruments whose obligors consist solely of natural persons; where a legal entity co-obligor is involved, the instrument can remain reportable and the relationship is indicated while the personal records of the natural-person debtor are excluded.

Proportionality is handled through derogations rather than a blanket small-bank exemption. Under Article 16(1) a national central bank may grant derogations to small reporting agents, provided the combined contribution of all derogated agents to the total outstanding loans of resident reporting agents does not exceed 2 percent. Article 16(3) separately permits derogations where a national central bank can obtain the required data from other sources. Article 7 and Annex II also allow for reduced reporting requirements in specified cases, and the German rulebook provides additional forms of reduced reporting for particular situations. Article 16(1) and Article 16(3) provide for discretionary NCB derogations. Article 7 and Annex II separately specify reduced reporting requirements in defined circumstances: information marked X is not required, while entries marked N depend on NCB arrangements. German reporters must apply the Bundesbank’s statistical order and applicable schemata rather than assume that every reduction requires an individual grant.

What the AnaCredit report contains: counterparty master data, instrument data and accounting data

AnaCredit collects information at the level of the individual borrower and the individual loan. The credit concept covers book claims and bills of exchange, described together as credit data. Marketable securities are excluded: a marketable bond on the balance sheet is captured through securities investment statistics, not through AnaCredit. German instructions include non-marketable debt securities and Schuldscheindarlehen within the category of other loans.

The German submission is built in two streams. The first is counterparty reference data, the master data on each contract partner, delivered through the RIAD-BBk application. The second is the credit data, which the Regulation already splits across templates in Annex I, essentially by reporting frequency. The Bundesbank mirrors that split with three credit-data schemata: monthly instrument data and related monthly credit data (the T1M schema, which also carries financial data, counterparty-instrument data and joint-liability data), further monthly credit data covering counterparty risk and default data, protection received, instrument-protection received and protection-provider relationships (T2M), and accounting data on a quarterly basis (the T2Q schema). The quarterly accounting-data template is the one that carries impairment, write-offs, performing status and accounting classification.

Rather than list every attribute, it helps to hold the four families in mind: counterparty reference data such as identifier, legal form, institutional sector, enterprise size and economic activity; instrument data such as type, inception and settlement dates, interest-rate type and amortisation type; financial data such as outstanding nominal amount, arrears, default status and the numeric interest rate; and accounting data such as accumulated impairment, accumulated write-offs and accounting classification. The last family is the quarterly one.

The threshold is defined at debtor level. The EUR 25,000 figure in Article 5 is measured as the sum of the debtor’s commitment across all instruments held against the observed agent, so three loans of EUR 10,000 to the same borrower put that borrower in scope even though no single loan reaches the figure. The test is applied at any reference date within the reference period, which Article 4 defines as running from the last reference date of the previous quarter to the current reference date.

One master-data habit is worth watching. Counterparty reference data is reported only where it has changed against the previous month. If nothing changed for a reporting agent in a given period, the Bundesbank still expects an empty report, a Leermeldung, rather than silence.

Reference dates, frequency and remittance deadlines

The reference date for monthly data is the last calendar day of the month. The reference dates for the quarterly accounting data are the four quarter-ends: 31 March, 30 June, 30 September and 31 December.

Remittance runs on business days for the monthly stream and on fixed calendar dates for the quarterly one. Monthly instrument data, further monthly credit data and counterparty master data for German-resident observed units are due by close of business on the sixth business day after the reference date. That can be extended to the ninth business day where the Bundesbank has granted the longer deadline under point 5 of its statistical order. A further extension to the twelfth business day, introduced by the supplement to point 5 effective 1 January 2024, applies only to reporters that exceeded one million eligible instruments and that have applied for and been granted this extension. Data relating to foreign-resident observed units are due by the fifteenth business day.

The quarterly accounting data have their own fixed dates: the quarter now closing is due in the second month after it, on 12 May for the first quarter, 11 August for the second, 11 November for the third, and 11 February of the following year for the fourth. Where a quarterly deadline falls on a statutory holiday, Saturday or Sunday, it moves to close of business on the following business day; the Bundesbank publishes a deadline calendar that accounts for regional as well as national holidays. Writing the schedule this way, rather than around whichever quarter happens to be open, is how a reporting team keeps it current without editing it every three months.

The extended monthly deadlines carry two points that can be misread. The ninth and twelfth business days apply only where the Bundesbank has specifically granted them. An institution without that grant remains on the sixth business day. The fifteenth business day is the standard deadline for the specific case of foreign-resident observed units.

Submission channel and format: XML files over NExt

Reports are XML files built to the RIAD-BBk and AnaCredit-BBk schemata, which follow the SDMX 2.1 standard, and they are delivered through the Bundesbank’s NExt application. Counterparty master data goes through the RIAD-BBk application; credit data goes through the AnaCredit-BBk application. The two routes are not interchangeable, and the technical specification specifies distinct acceptance conditions for each.

The file structure is granular. A credit-data submission may carry data for only one schema, one observed unit and one reporting period at a time, so an institution with several observed units builds several files. Each file is a single XML compressed into its own zip archive, one XML per zip. Where the uncompressed file would exceed 100 megabytes it has to be split across valid XML files, and the file-name length limit was raised to 100 characters in version 2.8 of the technical specification. A reporting agent can appoint a service provider to submit, and that provider may file for several reporting agents.

Two header fields decide whether a technically valid file is processed. The Test flag must be set to false for the production environment; an omitted Test value defaults to false, and a wrong value causes the message to be rejected. The Prepared timestamp is used to ensure messages are processed in the correct order. For counterparty master-data messages, the comparison key is the same reporting agent and reporting period; for credit-data messages, it is the same reporting schema, observed unit and reporting period. The system rejects a message whose Prepared time predates the last processed message within that key, which is how a re-sent older file can be turned away even when its contents are correct.

Check both the reporting-period applicability and the submission-date transition rules when preparing a file. Under Bundesbank Circular 50/2025, NExt is mandatory for AnaCredit and RIAD submissions received from 1 February 2026 regardless of the reporting reference date, so historical corrections submitted on or after that date must also comply with the revised filename and header conventions in the applicable version of the technical specification; non-compliant files are rejected. The German rulebook also distinguishes how credit-data records are handled under different monthly reporting approaches, and not every unchanged static record necessarily requires retransmission each period; consult the applicable rulebook version for the institution’s submission approach.

Validation rules and the errors that get AnaCredit files rejected

The Bundesbank publishes the checks in two handbooks, one for the AnaCredit validation rules (Handbuch zu den AnaCredit-Validierungsregeln) and one for the data quality indicators (Handbuch zu den AnaCredit-Datenqualitätsindikatoren), both alongside the German rulebook. After a submission the Bundesbank sends structured feedback: a validation-result response on each file, a reminder message where an expected report has not arrived, and data quality indicator feedback. For credit-data submissions, the validation-result feedback operates at both file level and reporting-reference-date level. Where a plausibility check flags a value as an anomaly, the reporter investigates the flagged value; where the value is incorrect it is corrected and resubmitted, and where the unusual value is correct the reporter confirms it through a dedicated confirmation schema rather than resubmitting the whole file.

Referential-integrity validation ensures that counterparties referenced in credit-data files have a corresponding entry in the RIAD-BBk master data; where a master-data submission has been rejected, follow-on referential-integrity findings can appear in the credit-data feedback because the required master records are absent. This category is distinct from technical file-level rejection, from the completeness reminders the Bundesbank sends when an expected report has not arrived, and from the plausibility findings described above. Other file-level issues include the wrong schema version for the period, a file over the size limit that was never split, and the ordering rejection from the Prepared timestamp, which surfaces as a refusal that looks like a data problem but is really a sequencing one.

This validation cycle is specific to AnaCredit and should not be confused with the periodic validation-rule updates that the EBA issues for the supervisory reporting framework, which our EBA quarterly validation-rules update covers separately. Institutions that allocate responsibility for both AnaCredit and supervisory reporting to one team benefit from the same discipline on referential integrity that underpins BCBS 239 risk data aggregation, but the rule sets and their release cadences are independent.

Caveats and interactions: the EUR 1 million Millionenkredit overlap

The most consequential interaction is the one closest to home. Germany runs a separate national large-loan return, the Millionenkredit under section 14 of the Banking Act, and the two are legally and operationally distinct returns, built for different purposes and differing on almost every operational axis.

The Millionenkredit threshold is EUR 1,000,000 of credit to a borrower or to a borrower unit, against EUR 25,000 for AnaCredit. Its legal basis is the Banking Act and the large-exposure and million-loan ordinance, the GroMiKV, rather than the ECB Regulation. Its frequency is quarterly. Its reference dates are the last calendar day of March, June, September and December, and the borrower-unit volume is assessed over the three calendar months preceding each reference date. The Millionenkredit involves two distinct reporting streams. The amount-data stream is submitted electronically through the Bundesbank ExtraNet or its capture platform, on the BA family of forms, due by the fifteenth business day of January, April, July and October. There is also a separate master-data notification obligation under GroMiKV section 16 for specified initial-reporting and master-data-change events; those notifications are submitted on paper, principally on forms EA, GbR and MKNE, due by the fifteenth calendar day of January, April, July and October. The large-exposure master data under Article 394 of the Capital Requirements Regulation share the same technical implementing rules. An institution can therefore owe monthly AnaCredit and quarterly Millionenkredit on the same borrower, on different thresholds, channels and calendars.

Proportionality inside AnaCredit involves several routes. The Article 16(1) derogation is capped and discretionary. The reduced-frequency option that once let small agents report credit data quarterly instead of monthly under Article 16(2) applied only to reference dates before 1 January 2021. It has lapsed, and a small institution today cannot elect quarterly-only AnaCredit credit data on that basis; the monthly obligation stands unless a derogation is granted. Article 16(3) still permits derogations where a national central bank can obtain the required data from other sources, and Article 7 together with Annex II allows reduced reporting requirements in further specified cases.

AnaCredit also sits close to the supervisory returns without merging into them. The accounting data it collects overlaps conceptually with the financial reporting framework, covered in our FINREP guide, and its exposure view relates to the large-exposure templates in our COREP guide. The definitions are not identical across these frameworks, and reconciling them is a task in its own right rather than a mapping that falls out automatically.

Recent and upcoming changes to German AnaCredit reporting

The framework has been stable in its core since the harmonised ECB data collection start in September 2018, but several dated changes matter for how a team plans. The German implementation timetable provided for collection of counterparty reference data from January 2018 and selected credit attributes from March 2018. The transitional reduced-frequency window under Article 16(2) closed for reference dates before 1 January 2021, so the quarterly-only credit-data route is now historical. On the German side, the supplement to point 5 of the statistical order effective 1 January 2024 added the twelfth business day as a further extended monthly deadline for qualifying reporters on top of the earlier ninth-business-day extension.

The Bundesbank technical specification, validation handbook and Handbuch zu den AnaCredit-Plausibilisierungsprüfungen are versioned and refreshed on a regular cycle. The applicable versions are: technical specification 2.8 (applicable from 1 February 2026), Handbuch zu den AnaCredit-Validierungsregeln version 22 (applicable from 1 August 2026) and Handbuch zu den AnaCredit-Plausibilisierungsprüfungen version 1.4 (applicable from 1 February 2026). The published forthcoming versions are: technical specification 2.9 (applicable from 1 February 2027), Handbuch zu den AnaCredit-Validierungsregeln version 23 (applicable from 1 February 2027) and Handbuch zu den AnaCredit-Plausibilisierungsprüfungen version 2 (applicable from 1 November 2026). A reporting team’s practical task at each transition is to verify the schema, code-list and handbook version the Bundesbank expects for the relevant reporting period before the file is built. The applicable submission and correction rules determine whether use of an earlier version produces a rejection; reporting teams should confirm applicability dates from the Bundesbank AnaCredit pages before transitioning production systems to a forthcoming version.

Looking further out, on 8 June 2026 the ECB announced conditional planning milestones for its integrated reporting framework (IReF) (ECB press release, 8 June 2026): a public consultation on the draft IReF Regulation in the second half of 2027, a one-year pilot starting in Q2 2030, and first official reporting in Q2 2031 followed by one year of parallel reporting. The ECB expressly makes this timetable conditional on adoption of the IReF Regulation and the consultation outcome, and has stated that the plan explaining changes to national collection frameworks is still being prepared. These are planning milestones, not enacted German filing requirements; the position to work to remains the current Regulation and the Bundesbank rulebook. The next thing to watch is the applicable schema, code-list and handbook version for the coming reporting period, published on the Bundesbank AnaCredit pages.

Frequently Asked Questions

If a borrower’s commitment drops below EUR 25,000 after being reported, does reporting stop immediately?

Under the German rulebook, continuation depends on when the drop occurs within the reference period. An instrument that was in scope earlier in the period can remain reportable for that period even after the balance falls below the threshold, and the German rulebook also provides for quarter-end continuation. Instruments fully repaid according to contract are expressly excepted. The exact treatment is governed by the German rulebook, which should be consulted directly rather than relying solely on the ECB Reporting Manual, as the two documents address certain aspects of the post-threshold-drop position differently.

Can a service provider submit AnaCredit files on our behalf?

Yes. A reporting agent can appoint a service provider, and that provider may submit for several reporting agents. The file granularity does not change: each credit-data file still covers one schema, one observed unit and one reporting period, so the provider builds the same set of files the institution would.

Our institution is a German branch of a euro-area bank. How do we avoid double reporting?

Article 6(2) makes a foreign branch report its own activity as creditor or servicer, and Article 6(3) provides for coordination between the national central banks where both the legal entity and its branch are resident in reporting Member States, as a mechanism to avoid the same data being collected twice. The article permits coordinated NCB decisions to omit specified template data; it is not an automatic guarantee of single collection. The practical perimeter, and any coordination or derogation between the home and host central banks, is confirmed with the Bundesbank rather than assumed.

Does the EUR 25,000 threshold apply to each loan or to the borrower?

To the borrower, in relation to an observed agent. Article 5(2) sums the debtor’s aggregate commitment across all instruments held against the observed agent, so several sub-threshold loans to one borrower can together cross EUR 25,000 and bring all of them into scope.

We had no counterparty master-data changes this month. Do we still file?

Yes. Counterparty reference data is reported only where it has changed against the previous month, but a period with no change requires an empty report rather than no submission. Silence is treated as a missing report and triggers a reminder message.

Is AnaCredit the same as the Millionenkredit return, given both go to the Bundesbank?

Both go to the Bundesbank but are legally and operationally distinct returns. AnaCredit is the ECB statistical return at EUR 25,000, monthly and quarterly, filed in XML over NExt; the Millionenkredit is the national large-loan return at EUR 1,000,000, quarterly, covering an amount-data stream filed electronically on the BA forms through ExtraNet and a separate master-data notification stream filed on paper. They differ in legal basis, threshold, frequency and channel, and an institution can owe both on the same borrower.

Can a small bank choose to report AnaCredit quarterly to save effort?

Not by election. The quarterly-instead-of-monthly option under Article 16(2) applied only to reference dates before 1 January 2021 and has lapsed. Further relief may be available under Article 16(1), where the Bundesbank may grant a derogation capped at a 2 percent combined contribution to total outstanding loans, or under Article 16(3), where the Bundesbank can obtain the required data from other sources. Article 7 and Annex II separately specify reduced reporting requirements in defined circumstances: information marked X is not required, while entries marked N depend on NCB arrangements. German reporters must apply the Bundesbank’s statistical order and applicable schemata rather than assume that every reduction requires an individual grant.

Related Articles

• COREP Reporting Explained: the supervisory own-funds and large-exposure framework whose exposure view sits close to AnaCredit.
• FINREP Reporting Explained: the accounting-based supervisory financial reporting return that overlaps with AnaCredit’s quarterly accounting data.
• FI Bank Barometer H2 2025: EU Credit Risk Reporting: how lending trends feed into credit-risk reporting across the EU.
• EBA Validation Rules Quarterly Update Q3 2026: the separate validation-rule cycle for the EBA supervisory reporting framework.
• BCBS 239 Risk Data Aggregation and Risk Reporting: the data-aggregation discipline that underpins granular returns like AnaCredit.

Key Takeaways

• AnaCredit in Germany is owed by resident credit institutions and German-resident branches of foreign credit institutions, filing loan-level data to the Bundesbank under Regulation (EU) 2016/867.
• The EUR 25,000 threshold is a per-debtor commitment test, summed across all of that debtor’s instruments in relation to an observed agent, not a per-loan figure.
• Monthly instrument and credit data for German-resident observed units are due by the sixth business day, or the ninth or twelfth only where the Bundesbank has granted the extension; foreign-resident observed units are due by the fifteenth.
• Quarterly accounting data are due on fixed dates: 12 May, 11 August, 11 November and 11 February of the following year; where a date falls on a holiday or weekend it moves to the next business day.
• Files are XML built to the RIAD-BBk and AnaCredit-BBk schemata and delivered over NExt; a wrong Test flag or an out-of-order Prepared timestamp causes rejection, with master-data messages compared on the reporting-agent/period pair and credit-data messages on the schema/observed-unit/period triplet.
• A missing counterparty master-data change still requires an empty report, and a counterparty referenced in credit data must exist in the RIAD-BBk master data.
• The section 14 KWG Millionenkredit is a separate national return at EUR 1,000,000 covering two streams: an electronic amount-data stream on BA forms via ExtraNet and a paper master-data notification stream; filing AnaCredit does not discharge it.
• The quarterly-only frequency relief under Article 16(2) ended for reference dates before 1 January 2021; further relief is available under the discretionary Article 16(1) derogation (capped at 2 percent), under Article 16(3) where the Bundesbank can source the data elsewhere, and under Article 7 and Annex II in specified circumstances.

Sources and References

• Regulation (EU) 2016/867 of the European Central Bank of 18 May 2016 on the collection of granular credit and credit risk data (ECB/2016/13): EUR-Lex, CELEX 32016R0867
• European Central Bank, AnaCredit overview and ECB Guideline ECB/2017/38 on the procedures for the collection of AnaCredit data: ecb.europa.eu AnaCredit
• ECB Reporting Manual, Part I, General Methodology (May 2019): ecb.europa.eu (PDF)
• ECB press release, 8 June 2026, on the main milestones for the roll-out of the Integrated Reporting Framework (IReF): ecb.europa.eu
• Deutsche Bundesbank, Kreditdatenstatistik (AnaCredit) service page with reporting population, deadlines, formats and applicable handbook versions: bundesbank.de
• Deutsche Bundesbank, AnaCredit technical specification for master and credit-data reporting, version 2.8 (applicable from 1 February 2026): bundesbank.de (PDF)
• Deutsche Bundesbank, AnaCredit technical specification version 2.9 (applicable from 1 February 2027): bundesbank.de (PDF)
• Deutsche Bundesbank, Handbuch zu den AnaCredit-Validierungsregeln, version 22 (applicable from 1 August 2026): bundesbank.de (PDF)
• Section 14 of the German Banking Act (Kreditwesengesetz), Millionenkredite: gesetze-im-internet.de
• Large-Exposures and Million-Loan Ordinance (GroMiKV), including the amount-data and master-data reporting rules for Millionenkredite: gesetze-im-internet.de
• Deutsche Bundesbank, Millionenkreditmeldewesen (section 14 KWG) service page: bundesbank.de
• Deutsche Bundesbank, implementing rules for the submission of large-loan and million-loan reports (DFBS), version 2.3: bundesbank.de (PDF)
• Deutsche Bundesbank, Rundschreiben 50/2025 (24 September 2025) on the mandatory transition to NExt for AnaCredit and RIAD submissions from 1 February 2026: bundesbank.de (PDF)
• Deutsche Bundesbank, Handbuch zu den AnaCredit-Plausibilisierungsprüfungen, version 1.4 (applicable from 1 February 2026): bundesbank.de (PDF)
• Deutsche Bundesbank, Handbuch zu den AnaCredit-Datenqualitätsindikatoren: bundesbank.de (AnaCredit hub)

Filing AnaCredit and the Millionenkredit without crossing the wires

A practical control risk on these returns is the slow drift between two neighbouring regimes: the EUR 25,000 monthly AnaCredit to the ECB through the Bundesbank, and the EUR 1,000,000 quarterly Millionenkredit under national law. Keep them on separate calendars, separate channels and separate thresholds, and the remaining discipline is schema and version management: before the next reference period closes, confirm the applicable schema, code-list and handbook versions the Bundesbank expects for that period, because that check is what stands between a built file and a rejection.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.