BCL S 1.12 Report: Euro Banknotes Moved Through an Intermediary

BCL S 1.12 reporting is the monthly return in which Luxembourg banks count the euro banknotes they withdraw from, or remit to, the Eurosystem through an intermediary. The Banque centrale du Luxembourg (BCL) created it with Regulation 2018/No 25 of 23 July 2018, published in Memorial A No 604 that day, and the first file, covering December 2018, was due on 15 January 2019. The filing population is every resident credit institution plus the financial services of the Entreprise des Postes et Telecommunications, which the BCL’s regulatory reporting page refers to as the financial services of POST Luxembourg.

The report itself is small. One intermediary generates at most 14 lines, seven denominations in each direction, and every figure is a count of notes. The work sits in the perimeter. Notes a bank draws at the BCL on its own account, with no intermediary, stay out. The same notes routed through another euro-area bank go in, and so does a withdrawal made directly at another Eurosystem central bank, which the instructions treat as the intermediary for reporting purposes.

Related reading: BCL S 0.1 Report: Daily Deposit Reporting for Luxembourg Banks

The dates that frame S 1.12:

• 23 July 2018: Regulation 2018/No 25 published in Memorial A No 604 and in force the same day (Article 7).
• December 2018: first reference period; the BCL’s S 1.12 page states that Layout 0 is mandatory from this period.
• 15 January 2019: first transmission due (Article 7).
• Every month since: the file is due within 10 working days after month-end, on the date fixed in the BCL’s annual calendar (Article 4 and section 1.2 of the instructions).

Legal basis of BCL S 1.12: Regulation 2018/No 25 and its three annexes

The binding text is Regulation of the Banque centrale du Luxembourg 2018/No 25 of 23 July 2018, filed under the domain “Statistics”. Its official French title refers to the “prelevement” and “versement” of euro banknotes, withdrawal and remittance, by credit institutions and the financial services of the Entreprise des Postes et Telecommunications. The English version on the BCL site renders this as “collection and remittance” and carries the BCL’s standard notice that the French text prevails in case of discrepancy. The two report line codes, PR and VE, match those French terms.

The preamble lists the powers relied on: Articles 127(2) and 128(1) of the Treaty on the Functioning of the European Union, Article 5.1 of the Statute of the ESCB and of the ECB, Guideline ECB/2008/8 on data collection regarding the euro and the operation of the Currency Information System (as amended), Decision ECB/2010/29 on the issue of euro banknotes (as amended), Article 108bis of the Luxembourg Constitution, and Articles 2(1), 32 and 34(1) of the law of 23 December 1998 on the monetary status and the BCL. Article 32(1) of that law empowers the BCL to collect statistical information directly from economic agents, and Article 34(1) lets it adopt regulations published in the official journal. The recitals give a single purpose: monitoring the withdrawal and remittance of euro banknotes.

The obligation on banks is national. Guideline ECB/2008/8, as amended, sets duties for the Eurosystem central banks: it governs how they report euro banknote data to the ECB through the Currency Information System. What reaches a Luxembourg bank is the BCL regulation, which runs to eight articles.

Article 1 defines the declarant, the intermediary, the credit institution and the postal financial services. Article 2 puts an information duty on intermediaries that withdraw or remit notes on behalf of a credit institution or the postal financial services. Article 3(1) sets the declarants’ monthly statistical obligations in four points, 1.1 to 1.4, and Article 4 the 10-working-day deadline, the annual calendar and electronic transmission. Articles 5 to 8 cover use of data, sanctions, entry into force and publication.

Article 8(3) names three annexes, “regularly updated” on the BCL website: Annex 1, the S 1.12-L instructions; Annex 2, the S 1.12-L report; and Annex 3, the manual of electronic transmission for banks’ statistical reports. Those three documents carry the operational detail, so a change to S 1.12 can arrive as an annex update on the BCL site without a new regulation in the Memorial.

Article 2 is the provision most easily misread. Its addressees are the intermediaries, which must inform the BCL when they move notes on behalf of a credit institution or the postal financial services. The declarant’s own reporting obligation sits in Article 3, and the S 1.12-L file implements Article 3.

Who must report S 1.12: resident banks and POST, with no size threshold

Article 1(2) defines the declarant as “all resident credit institutions” together with the financial services of the Entreprise des Postes et Telecommunications. Article 1(4) defines a credit institution as a legal person whose business is to receive deposits or other repayable funds from the public and grant credit for its own account, plus any other person qualified as a credit institution in Chapter 1 of Part I of the law of 5 April 1993 on the financial sector. Neither the regulation nor the instructions set a size threshold, an activity trigger or an exemption.

The instructions differ by language on one word. The English section 1.1 says “all resident credit institutions regardless of their legal status”. The French section 1.1, which prevails, describes the population as the “luxembourgeois” credit institutions, again regardless of legal status. The regulation itself uses the residence wording in both languages.

My reading is that the regulation’s residence test governs, which places Luxembourg branches of banks incorporated elsewhere in the population. The BCL’s general document on definitions and concepts for credit institutions fits that reading on the format side: it says branches of foreign-law credit institutions established in Luxembourg provide statistical reports in a single L version. A branch in doubt about its status can settle the point with the BCL in writing.

The L version is the only version. The manual of electronic transmission and the 2026 calendar list S 1.12-L Layout 0 and no S 1.12-N. Under the same definitions document, the L version covers the Luxembourg head office and the N version adds foreign branches. My reading is that banknote movements booked by a Luxembourg bank’s foreign branches fall outside the file, since there is no N version to carry them. The instructions do not address foreign branches directly.

The intermediary is defined in Article 1(3) as a credit institution in the euro area or a national central bank of the Eurosystem. That definition decides most scope questions. A Luxembourg bank can be both a declarant, for notes it moves through someone else, and an intermediary, for notes it moves on another bank’s behalf, and the second role triggers Article 2. A non-euro-area bank falls outside the definition. Another euro-area central bank qualifies, which is why a direct withdrawal there is reported.

Being in scope and having something to report are different questions. A resident bank whose cash moves only through its own dealings at the BCL counter belongs to the population and still has no line to fill, because own-account movements at the BCL without an intermediary are excluded.

What the report contains: up to 14 lines per intermediary, counted in notes

Section 2 of the instructions asks for three types of information:

• the identity of each intermediary through which the declarant withdraws or remits euro notes, given as the RIAD (Register of Institutions and Affiliates Data) code that the ECB publishes on its website;
• the number of euro notes withdrawn from the BCL or another Eurosystem central bank through an intermediary;
• the number of euro notes remitted to the BCL or another Eurosystem central bank through an intermediary.

Two boundary rules follow. A direct withdrawal or remittance at another Eurosystem central bank is reported, with that central bank treated as the intermediary and identified by its RIAD code. This mirrors points 1.3 and 1.4 of Article 3(1), which ask for the name of any Eurosystem central bank other than the BCL used directly and the number of notes moved there. Notes withdrawn from or remitted to the BCL on the bank’s own account, without an intermediary, “must not be reported”. Section 3 adds a single breakdown: by banknote denomination.

The Excel report (Annex 2, cover version “2018.06”) has a cover sheet and one data sheet, “Banknotes”, with the columns Line, Items, Banknote and Number of banknotes. The rows are:

“Code RIAD” is a placeholder: each intermediary gets its own set of lines keyed on its RIAD code. Every figure is a number of notes, in pieces. The documents give no euro value, no sign convention and no netting rule, and the line structure keeps withdrawals and remittances on separate lines, so there is no place for a net figure.

In the XML file, each line becomes a reportedLine element whose identifier combines four fields, followed by the amount:

The EUR 500 lines are still in the layout. The ECB announced on 4 May 2016 that issuance of the EUR 500 note would stop around the end of 2018, and that the note remains legal tender and can be exchanged at Eurosystem central banks for an unlimited period. Remittances of EUR 500 notes through an intermediary therefore remain possible, and when they happen they belong on the VE-500 line.

S 1.12 measures movements, line by line per intermediary. The euro value of cash a bank holds is a stock, reported elsewhere: the BCL’s definitions document lists item 1-001000 Cash among the statistical balance sheet assets. The S 1.12 instructions do not link the two reports, and nothing in them asks for a reconciliation.

S 1.12 deadlines: ten working days after month-end, on the BCL calendar

The reference period is the calendar month, entered in the XML header as endMonthDate. Article 4(1) of the regulation and section 1.2 of the instructions set the deadline at 10 working days after the end of the period, and Article 4(2) requires the BCL to publish each year a calendar with the precise dates. The 2026 edition, dated December 2025, carries a footnote that matters for anyone counting days: the deadlines “are based on the working days defined by the ECB for the transmission of statistics by the national central banks”. The date in the calendar is the deadline. A count of Luxembourg business days is a cross-check at best.

In that calendar, S 1.12-L carries the same remittance dates as S 1.1, S 1.4, S 1.8 and S 1.9 for every 2026 reference month. S 1.5 runs on later dates. For the 2026 reference months, the BCL calendar sets these remittance dates for S 1.12-L Layout 0:

The calendar edition names the exact day for each reference month, and that date is the deadline. When a new calendar year starts, the dates move to the next edition, so the table above is a reference for 2026 periods only.

The BCL calendar is a separate document from the CSSF’s prudential timetable, which our CSSF reporting calendar for Q3 2026 covers. S 1.12 dates come from the BCL edition.

A second clock can start after submission. The BCL’s April 2025 document on feedbacks says the BCL will specify a deadline within any feedback it sends, because the urgency of a correction or confirmation varies.

Submission: the S0112-L XML file, its name and the Sofie or e-file route

S 1.12 is filed as XML against the BCL’s own schema package, version 1.0 (the archive folder is named S0112-L_L0_Schema_XML_v1_0_r139). The BCL publishes XML schemas for S 1.12 and no XBRL taxonomy. The package holds three schemas: S112-L.xsd as the main schema, structures.xsd and datatypes.xsd. It also contains HTML documentation and one sample file.

The namespace is http://www.bcl.lu/2018/S1.12-L. The root element S112-L carries two required attributes, version (fixed at 1.0) and creationDateTime. It then holds a header with six elements: endMonthDate, closingDate, reporterID, declarantID, reportingCurrency and layout. After the header comes a content block with the banknote lines.

The file name follows the BCL’s manual of electronic transmission (February 2021), which lists the S 1.12-L Layout 0 pattern as S0112-L_L0_yyyymm_Rrrrrrrrrr_Dddddddddd_yyyymmdd_nnn. The parts read as follows:

• yyyymm is the reference month.
• R stands for the reporter’s type letter (B for a CSSF bank number, P for a CSSF professional-of-the-financial-sector number) and is followed by the nine-digit identifier; the reporter is the entity that submits the file.
• D stands for the declarant’s type letter, which the manual fixes as B for banks, and is followed by the nine-digit identifier; the declarant is the bank whose data the file contains.
• yyyymmdd is the file creation date and nnn a sequence number.

Identification numbers are allocated by the CSSF and left-padded with zeros, so bank 999 becomes 000000999. The sample file in the BCL package is named S0112-L_L0_201801_B000000999_B000000999_20180620_001.xml.

The reporter and the declarant can differ. Section 4 of the manual gives two identifier types: type 23 for an identification number allocated by the CSSF to banks, shown as B in the file name, and type 32 for one allocated to professionals of the financial sector, shown as P. On the manual’s definitions, a bank that outsources its submissions to a support PFS would show the PFS as reporter, with type 32 in the header and P in the file name, and itself as declarant with type 23 and B. The manual adds that “banks must use the letter B” for the declarant.

The sequence number has its own rules: files created on the same day for the same report are numbered from 001, a new sequence starts each day, and 000 is never used. The documents say nothing more on resubmission. They do not state whether a later file replaces an earlier one for the same month or how a correction is flagged. A second file on the same day takes 002, and anything beyond that is a question for the BCL.

Two channels are accepted. The manual names Sofie (SIX Payment Services (Europe) S.A., CETREL Securities) and e-file (Bourse de Luxembourg, Fundsquare), and says the BCL will consider any other secure channel that both sides accept. Since the BCL’s circular letter ST.24-0013 of 15 January 2024, addressed to all reporters except financial companies, statistical reports are no longer accepted by e-mail. The Excel report is the layout reference for Annex 2. The filing itself is the XML file.

Validation: what the S 1.12 schema checks and what it leaves to the BCL

The BCL’s S 1.12 page offers three documents: the instructions, the report and the XML schemas. It lists no compendium of verification rules. That gap stands out because the BCL’s general definitions document for credit institutions says reports must follow the norm in the manual of electronic transmission and the “Compendium of verification rules” established for each statistical report. For S 1.12, the only checks the BCL’s reporting page publishes are the ones built into the schema; whether the BCL applies further business checks is not documented there.

Those checks are strict on structure. A file fails XML validation in these cases:

• A denomination outside 500, 200, 100, 50, 20, 10 and 5.
• A reportingCurrency that is not three uppercase letters, or an institution type that is not two digits.
• A version attribute other than 1.0.
• A missing header element; all six are mandatory.
• Two reportedLine entries with the same combination of riadCode, transactionType, denominationType and amountType, which the schema’s uniqueness rule blocks.

The uniqueness rule shapes how the file is built. Several withdrawals from the same intermediary in the same denomination during the month have to be summed into one line before the XML is generated.

The schema is loose on content. transactionType accepts any two uppercase characters, although only PR and VE appear in the template. amountType accepts any four, and the only value in the BCL documents is VOLU in the sample file. reportedAmount allows five decimal places, although a count of notes is a whole number.

The schema does not check that a RIAD code exists. The manual says plainly that the schema “contains format constraints for the data, but it does not necessarily specify the validity of a code that respects the format”. A file can therefore pass validation with a PR line under the wrong RIAD code, or a decimal count, and still be wrong.

After submission, the BCL’s April 2025 document says reporters of its statistical reports, S0112 included, can receive up to three types of feedback, which it describes as being set up “in the near future”:

• FL-OK or FL-NOK: whether the file was processed or contains technical errors.
• DQ-FDB: data points where the BCL needs a correction or a confirmation.
• ADHC-FDB: ad hoc requests outside the normal production cycle.

Feedback files are named FDBBUSI_[date of feedback]_[name of entry file]_[feedback type]_[BCL exchange ID]. Under BCL Circular 2021/243, delivery is moving in stages from e-mail to the Sofie and e-file channels, with an e-mail notice per report type before the first feedback arrives through the channel. The BCL describes the model as the one already used for AnaCredit; our piece on AnaCredit v1.0.15 and the BCL’s schema update covers the BCL’s AnaCredit technical and business feedback and the feedback schema. The BCL has published no list of common S 1.12 rejection causes, and the failures listed above come from the schema itself.

Caveats: cross-references, the French text, nil months and the ECB sanctions regime

Three cross-references in the regulation do not line up with its structure, and they appear identically in the French text published in the Memorial. Article 4(1) sets the 10-working-day deadline for “the information required in Article 2 paragraphs 1 to 2”, yet Article 2 is the intermediaries’ information duty and has no numbered paragraphs, while the declarants’ monthly content sits in Article 3. Article 7 sets the first transmission for “the information defined in Article 2 paragraph 1”. Article 4(3) points to “the electronic transmission methods described in Annex 2”, while Article 8(3) lists the transmission manual as Annex 3 and the report as Annex 2.

My reading is that the deadline provisions refer to the Article 3 content and the transmission provision to Annex 3. The instructions confirm the 10-working-day rule for S 1.12-L, and the manual sets out the transmission methods, so the practical effect is clear even where the cross-references are not.

The French and English instructions also differ on the population, as covered above: “luxembourgeois” in French, “resident” in English. Both texts of the regulation say resident.

Three header fields are thinly documented. closingDate has no definition beyond “closing date”, and the BCL sample file sets it equal to endMonthDate. reportingCurrency is mandatory although the figures are note counts, and the sample file uses EUR. The BCL’s general definitions document (section 2.3) says statistical reports are established in the accounting currency of the credit institution, and it does not say how that rule applies to a return that counts euro notes, so a bank should confirm the correct header value with the BCL in writing. layout is an integer, and the published layout is Layout 0.

Months without an indirect movement are another open point. The regulation says declarants transmit “monthly”, and the schema makes the banknotes block optional, so a file with a header and an empty content block is valid XML. Neither the regulation nor the instructions say whether the BCL expects such a file for a month with nothing to report. Ask the BCL before assuming either way.

The sanctions position needs care. Article 6 of the regulation allows the BCL, without prejudice to other sanctions, to make any infringement public and to inform the financial sector’s supervisory authorities. Separately, circular letter ST.24-0013 applies Regulation (EU) 2022/1917 (ECB/2022/31) on infringement procedures, under which the ECB may impose sanctions, from 30 April 2024 to the collections listed in its Annex I. That annex lists ECB regulations only, and BCL Regulation 2018/No 25 is not among them. The April 2025 feedback document, which names S0112, nevertheless states that compliance with feedback deadlines falls within the ECB non-compliance framework of Regulation (EU) 2022/1917 and ST.24-0013.

The two BCL documents do not line up for S 1.12. Article 1 of Regulation (EU) 2022/1917 frames the regime around statistical reporting requirements laid down by ECB regulations and decisions, and BCL Regulation 2018/No 25 is a national act outside that wording. My reading is that, on that text, the regime’s stated basis does not extend to an S 1.12 breach, while the April 2025 feedback document nonetheless ties S0112 feedback deadlines to the framework. The documents reviewed do not reconcile the two positions.

The regulation and instructions provide no proportionality regime, waiver or national discretion. On record keeping, the BCL’s general definitions document requires reporting agents to keep monthly and quarterly statistical reports and related documents for 24 months. The S 1.12 instructions do not cross-refer to that document, so the 24-month rule applies here as the BCL’s general standard for credit institutions’ statistical reports, with no S 1.12-specific restatement.

Changes to S 1.12: one layout since 2018, new channels and a wider euro area

S 1.12 has kept a single layout since it started. The instructions are dated June 2018, the report template carries version 2018.06, the schema package is version 1.0, and the BCL’s index of reporting instructions shows the S 1.12 page as last updated on 25 July 2018. Changes since then have come from documents that apply across the BCL’s statistical reports:

• February 2021: the manual of electronic transmission, which lists the S0112-L_L0 file-name pattern.
• 15 January 2024: circular letter ST.24-0013 ends e-mail transmission of statistical reports and applies Regulation (EU) 2022/1917 from 30 April 2024 to the collections in its Annex I.
• April 2025: the feedbacks document moves FL, DQ and ADHC feedback for S0112 and the other bank statistical reports onto Sofie and e-file in stages.

The euro area grew on 1 January 2026. The BCL’s circular letter ST.25-0366 of 31 July 2025 records the EU Council’s approval on 8 July 2025 of Bulgaria joining from that date. It covers S 1.1, S 1.4, S 1.5 and S 1.8, finds no impact on S 2.5, deals with the reserve base, and does not mention S 1.12. Read against Article 1(3) of the regulation, my reading is that Bulgaria’s central bank and Bulgarian credit institutions fall within the intermediary definition from 1 January 2026. A direct withdrawal at Bulgaria’s central bank would be reported under its RIAD code like any other Eurosystem central bank.

None of the BCL documents reviewed for this guide announces a new S 1.12 layout or schema version. The recurring update is the annual calendar. The S 1.12 documents predate the Eurosystem’s digital euro work and say nothing about it. Our note on the ECB digital euro pilot and the BCL’s participation covers that separate track.

Frequently Asked Questions

Does a cash-in-transit company that collects notes for us count as an intermediary?

Article 1(3) limits intermediaries to euro-area credit institutions and Eurosystem central banks, so a cash-in-transit company falls outside the definition. My reading is that a carrier moving notes against the bank’s own BCL account leaves the movement in the excluded own-account category, and that where the carrier acts for another bank holding the central bank relationship, that bank is the intermediary. Where the contract structure is unclear, confirm the treatment with the BCL.

We act as intermediary for another Luxembourg bank. Do those notes go into our own S 1.12-L?

The instructions ask each declarant for the notes it withdraws or remits through an intermediary, so my reading is that notes you move on a client bank’s behalf belong in that bank’s file under your RIAD code. Your own duty for those movements sits in Article 2, which requires intermediaries to inform the BCL. The regulation does not specify the form or timing of that Article 2 information, so agree it with the BCL.

What if the bank between us and the central bank sits outside the euro area?

The definition of intermediary does not cover it, and the report counts notes moved with the BCL or another Eurosystem central bank. The instructions do not address a chain in which a non-euro-area institution stands between the declarant and a Eurosystem central bank. Raise it with the BCL before choosing a RIAD code or leaving the movement out.

Do coins or non-euro banknotes belong in S 1.12?

No. The report, its instructions and its schema cover banknotes denominated in euro only. The schema’s denomination list stops at the seven euro note values, so there is no line for coins or for notes in other currencies.

Can the BCL share our S 1.12 data or a breach with the CSSF?

Article 5 limits use of the data to the BCL’s tasks, and Article 6 allows the BCL to inform the supervisory authorities of the financial sector about an infringement. Article 33(2) of the BCL’s organic law, an exception to the BCL’s professional secrecy, separately permits information exchanges with the CSSF to the extent needed for the BCL’s missions.

How do we correct an S 1.12-L file the BCL has already processed?

The S 1.12 documents give no correction procedure. A DQ-FDB feedback will state its own deadline for a correction or confirmation. The BCL’s general minimum standards add that revisions outside regular revisions must come with explanatory notes. For an unprompted correction, contact the BCL first, then send the new file under the naming rules.

Related Articles

• BCL S 0.1 Report: Daily Deposit Reporting for Luxembourg Banks: the BCL’s twice-monthly deposit report, with its legal basis, template, checks and submission workflow.
• AnaCredit v1.0.15: BCL Swaps the NUTS 3 Code List for January 2027: the BCL’s AnaCredit schema update and the file changes banks need to avoid rejection.
• CSSF Reporting Calendar Q3 2026: Deadlines and Submissions for Luxembourg Firms: the CSSF’s prudential deadlines for Luxembourg banks and fund managers in the third quarter.
• ECB Digital Euro Pilot: BCL and Two Luxembourg PSPs Join: the scope and timeline of the pilot the BCL joined, and what it does and does not require.

Key Takeaways

• Map every cash route to one of three outcomes before month-end: own-account at the BCL (excluded), through a euro-area bank (reported under that bank’s RIAD code), or direct at another Eurosystem central bank (reported under that central bank’s RIAD code).
• Sum all movements per intermediary, direction and denomination into one line; duplicate keys fail the schema.
• Take the deadline from the BCL’s annual calendar, which counts ECB working days. For 2026 periods it matches S 1.1.
• Name files S0112-L_L0_yyyymm_R…_D…_yyyymmdd_nnn, starting the daily sequence at 001, and send them through Sofie or e-file.
• Check RIAD codes and whole-number counts yourself, because the schema validates neither.
• Get the BCL’s written position on nil months and closingDate, which the documents leave open, and on how the accounting-currency rule applies to the reportingCurrency header.
• Treat Article 6 of Regulation 2018/No 25 as the stated sanction, and note that the BCL’s own documents disagree on whether the ECB infringement regime covers S 1.12.

Sources and References

• Regulation of the Banque centrale du Luxembourg 2018/No 25 of 23 July 2018 (English version, French prevails): BCL Regulation 2018/No 25 (PDF)
• Reglement de la BCL 2018/No 25 du 23 juillet 2018, Journal officiel du Grand-Duche de Luxembourg, Memorial A No 604 (French, prevailing text): Memorial A No 604 text (PDF)
• BCL, S 1.12 reporting page (instructions, report, XML schemas): S 1.12 Indirect withdrawal and remittance of banknotes denominated in EUR through an intermediary
• BCL, Report S 1.12-L instructions, June 2018 (English): S0112-L_L0 instructions (PDF)
• BCL, Rapport S 1.12-L instructions, juin 2018 (French, prevailing text): S0112-L_L0 instructions FR (PDF)
• BCL, Report S 1.12-L template, version 2018.06: S0112-L_L0 report (XLS)
• BCL, S 1.12-L XML schemas, version 1.0: S0112-L_L0 XML schemas (ZIP)
• BCL, Manual of electronic transmission for statistical reports of credit institutions, February 2021: Electronic transmission manual (PDF)
• BCL, Feedbacks for the statistical reports, April 2025: Feedbacks document (PDF)
• BCL, Definitions and concepts for the statistical reporting of credit institutions, July 2024: Definitions and concepts (PDF)
• BCL, Calendar of remittance dates for the statistical reporting of credit institutions in 2026: 2026 reporting dates (PDF)
• BCL circular letter ST.24-0013 of 15 January 2024, Monitoring compliance with statistical reporting: ST.24-0013 (PDF)
• BCL circular letter ST.25-0366 of 31 July 2025, Adoption of the euro by Bulgaria: ST.25-0366 (PDF)
• Loi du 23 decembre 1998 relative au statut monetaire et a la Banque centrale du Luxembourg, consolidated version of 30 July 2021: BCL organic law (PDF)
• Guideline of the ECB of 11 September 2008 on data collection regarding the euro and the operation of the Currency Information System 2 (ECB/2008/8): EUR-Lex
• Decision of the ECB of 13 December 2010 on the issue of euro banknotes (recast) (ECB/2010/29): EUR-Lex
• Regulation (EU) 2022/1917 of the ECB of 29 September 2022 on infringement procedures in cases of non-compliance with statistical reporting requirements (ECB/2022/31): EUR-Lex
• ECB press release, 4 May 2016, ECB ends production and issuance of EUR 500 banknote: ECB

Preparing the next S 1.12-L file

Before the next calendar date, pull every banknote movement of the month from the cash ledger, tag each with the intermediary’s RIAD code or the Eurosystem central bank used directly, and drop the own-account BCL movements. Sum by PR or VE and by denomination, build the S0112-L_L0 file against S112-L.xsd, and send it through Sofie or e-file by the date in the BCL’s current calendar. The open questions on nil months and header fields go to the BCL in writing before the file is due.

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.