Introduction
Under the Bank of England Wholesale Cash Distribution Recognised Persons Codes of Practice (the codes of practice), recognised persons are required to submit certain information to the Bank of England (Bank). The Wholesale Cash Distribution Market Oversight (WCDMO) Data Catalogue (the data catalogue) sets out how this should be undertaken.
This data catalogue should be read in conjunction with the codes of practice and guidance, including provisions regarding the application of the codes of practice and the defined terms used therein.
Submission Requirements
Data item applicability
Subject to the codes of practice, recognised persons must submit to the Bank the data items specified in the Data Item Summary as applicable to them as operator and/or backing FI.
Where a recognised person is required to submit data items to the Bank under a code of practice, in respect of the recognised person’s capacity as both an operator and a backing FI, such recognised person may comply with the submission requirements by providing the data items in a single document. For example, with respect to the recognised person’s activities as both an operator and as a backing FI, a single business continuity plan may be submitted.
This data catalogue operates in addition to the rules of the Bank of England Note Circulation Scheme (NCS). Therefore, where a recognised person is also a member of the NCS, the person should comply with their reporting and information obligations under both the NCS rules as well as under this data catalogue unless specified otherwise where dual reporting requirements would apply.
Data item format
Recognised persons must submit each data item to the Bank in the format specified for such data item in the Data Item Summary.
2 data item formats are used for submitting information electronically, which are explained below:
- Table – Recognised person submits information in rows and columns as specified in the reporting form and data catalogue. To be submitted in XML file format (See Instructions for submitting WCDMO reporting form in XML file format for details).
- Document – Recognised person provides a report or file which meets the content requirements outlined in the codes of practice and associated guidance. Documents can be provided in one of the following supported file formats: XBRL, CSV, DOC, DOCX, PDF, PPT, PPTX, XLS, XLSX, XML, ZIP.
The data item format required for each data item is recorded in the Data Item Summary and in the grey box prior to the detailed requirements for each data Item.
Data item file naming convention
When submitting table or document-based data items to the Bank, the recognised person must adhere to the relevant file naming convention outlined in Annex 1 – Data Item File Naming Conventions.
Group reporting
Where a recognised person is in a group in relation to one or more other recognised person(s), each such recognised person may comply with certain submission requirements of the Information-gathering code of practice as if the recognised person formed, together with one or more of the other such recognised person(s), a single recognised person whose specified relevant functions were set out in each relevant wholesale cash oversight order read together as a whole. This must be done using an additional [Firm ID] specified by the Bank. Details of which data items can be submitted as a group are outlined for each data item in paragraph 17.1 of the Information-gathering code of practice and set out in the Data Item Summary.
The Bank has the power to direct a recognised person in a group to not apply group reporting provisions.
Where group reporting is not permitted for a data item, each recognised person must submit a data item using their [Firm ID] assigned by the Bank.
Reporting frequencies and reporting periods
A recognised person is required to submit a data item at the frequency (the reporting frequency) and in respect of the period (the reporting period) specified or otherwise referred to for each data item in the Data Item Summary.
Submission dates
Recognised persons must submit each data item to the Bank by the submission date.
Unless stated otherwise, the submission date is specified in the Code of Practice – Information gathering. For initial submission requirements, please see the Code of Practice – Information gathering.
If the due date for submission of a data item falls on a date which is not a business day, the information must be submitted so as to be received by the Bank no later than the first business day after such due date.
Submission methodology
Recognised persons must submit data items in accordance with the codes of practice and this data catalogue, by email to wholesalecashsupervision@bankofengland.co.uk until such time as the Bank of England Electronic Data Submission (BEEDS) is made available by the Bank for the online submission of information. The Bank will specify the date by which recognised persons must submit such data items through BEEDS. BEEDS is accessed using an online portal.
In the event BEEDS becomes unavailable, recognised persons should inform the Bank and if instructed, submit data items by email to wholesalecashsupervision@bankofengland.co.uk.
Data Item Summary
The information required to be reported by recognised persons pursuant to the codes of practice includes the following data items.
Data item name | Data item format | Applicable to operator? | Applicable to backing FI? | Option to report as group? | Reporting frequency | Reporting period |
|---|---|---|---|---|---|---|
Table | Yes | Yes | Yes | With every submission from a given recognised person | Not applicable but to be submitted with every data item submission. | |
Table | Yes | No | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering and Code of Practice – Third-party arrangements | |
Table | Yes | No | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering and Code of Practice – Third-party arrangements | |
Table | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Table | Yes | No | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering and Code of Practice – Third-party arrangements | |
Table | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Table | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering and Code of Practice – Third-party arrangements | |
Table | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Table | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Table | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | Yes | Update as required | Not specified. See Code of Practice – Information gathering | |
Document | Yes | No | No | Event based/Ad-hoc notification | Not specified. See Code of Practice – Cash centre closure and market exit | |
Table | Yes | Yes | Yes | Event based/Ad-hoc notification | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | No | Event based/Ad-hoc notification | Not specified. See Code of Practice – Cash centre closure and market exit | |
Table | Yes | Yes | Yes | Annually | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | Yes | Annually | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | Yes | Annually | Not specified. See Code of Practice – Information gathering | |
Document | Yes | Yes | Yes | Annually | Not specified. See Code of Practice – Information gathering | |
Table | Yes | Yes | Yes | Quarterly | Previous calendar quarter | |
Table | Yes | Yes | Yes | Quarterly | Previous calendar quarter | |
Table | Yes | No | Yes | Monthly | Previous calendar month | |
Table | Yes | Yes | Yes | Monthly | Previous calendar month | |
Table | Yes | No | Yes | Monthly | Previous calendar month | |
Table | Yes | Yes | Yes | Monthly | Previous calendar month |
Return Header
Data item name: Return Header
Date item format: Table
Summary: Contains metadata for the information gathering submission.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: With every submission from a given recognised person.
Reporting period: Not applicable but to be submitted with every data item submission.
Other information: At least one reporter ID must be provided.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Firm ID | Integer | Yes | Must be a valid [Firm ID] from Firm Details | Links return to a given firm. [Firm ID] must exist in the Firm Details table. |
Return Comments | String | Yes | Max 2,000 Characters | Summarise the contents of the return, including any notable changes (additions, edits or updates, deletions) since the last return. |
Submission Date | Date | Yes | YYYY-MM-DD | The date the return was submitted to the Bank. |
Data Owner Reporter ID | Integer | No | Must be a valid [Reporter ID] from Reporter Details | [Reporter ID] must exist in the Reporter Details table. [Reporter ID] must be affiliated to the stated Firm ID. [Reporter Role] associated with entered [Reporter ID] must equal ‘Owner’. The given [Reporter ID] must not be repeated in [Data Steward Reporter ID], [Data Expert Reporter ID 1], [Data Expert Reporter ID 2] or [Data Expert Reporter ID 3]. |
Data Steward Reporter ID | Integer | No | Must be a valid [Reporter ID] from Reporter Details | [Reporter ID] must exist in the Reporter Details table. [Reporter ID] must be affiliated to the stated Firm ID. [Reporter Role] associated with entered [Reporter ID] must equal ‘Steward’. The given [Reporter ID] must not be repeated in [Data Owner Reporter ID], [Data Expert Reporter ID 1], [Data Expert Reporter ID 2] or [Data Expert Reporter ID 3]. |
Data Expert Reporter ID 1 | Integer | No | Must be a valid [Reporter ID] from Reporter Details | [Reporter ID] must exist in the Reporter Details table. [Reporter ID] must be affiliated to the stated Firm ID. [Reporter Role] associated with entered [Reporter ID] must equal ‘Expert’. The given [Reporter ID] must not be repeated in [Data Owner Reporter ID], [Data Steward Reporter ID], [Data Expert Reporter ID 2] or [Data Expert Reporter ID 3]. |
Data Expert Reporter ID 2 | Integer | No | Must be a valid [Reporter ID] from Reporter Details | [Reporter ID] must exist in the Reporter Details table. [Reporter ID] must be affiliated to the stated Firm ID. [Reporter Role] associated with entered [Reporter ID] must equal ‘Expert’. The given [Reporter ID] must not be repeated in [Data Owner Reporter ID], [Data Steward Reporter ID], [Data Expert Reporter ID 1] or [Data Expert Reporter ID 3]. |
Data Expert Reporter ID 3 | Integer | No | Must be a valid [Reporter ID] from Reporter Details | [Reporter ID] must exist in the Reporter Details table. [Reporter ID] must be affiliated to the stated Firm ID. [Reporter Role] associated with entered [Reporter ID] must equal ‘Expert’. The given [Reporter ID] must not be repeated in [Data Owner Reporter ID], [Data Steward Reporter ID], [Data Expert Reporter ID 1] or [Data Expert Reporter ID 2]. |
Firm Details
Data item name: Firm Details
Data item format: Table
Summary: Information about the recognised person or group.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: None
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Firm ID | Integer | Yes | Must be unique | Unique identifier for the Firm. Bank assigned integer. |
Firm Name | String | Yes | Max 50 Characters | The full, unabbreviated version of the name of the recognised person. |
Firm Abbreviation | String | Yes | Max 10 Characters | The typical short form or acronym used for the recognised person. |
Firm Type | List | Yes | Operator; Backing FI; Both | Denotes the kind of recognised person. |
Firm Companies Registration Number (CRN) | String | Yes | Must be 8 Characters long. Alphanumeric and Capitalised. | The 8-character, alpha-numeric code that a recognised person is registered with Companies House. |
Additional Firm Companies Registration Number (CRN) | String | No, unless submitting as a group | Must be 8 Characters long. Alphanumeric and Capitalised. | The 8-character, alpha-numeric code that any additional recognised person within the group is registered with Companies House. |
Firm Legal Entity Identifier (LEI) | String | Yes | Must be 20 Characters long. Alphanumeric and Capitalised. | For a recognised person, the 20-character, alpha-numeric code based on the ISO 17442 standard developed by the International Organization for Standardization (ISO). |
Additional Firm Legal Entity Identifier (LEI) | String | No, unless submitting as a group | Must be 20 Characters long. Alphanumeric and Capitalised. | For any additional recognised person within the group, a 20-character, alpha-numeric code based on the ISO 17442 standard developed by the International Organization for Standardization (ISO). |
Reporter Details
Data item name: Reporter Details
Data item format: Table
Summary: Contact information about individuals responsible for data governance and reporting on behalf of the recognised person.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated per reporter
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: For a detailed description of the reporter roles, see 'Information Reporting Framework’ in the guidance to Code of Practice - Information gathering. Please see ‘Personal data collected for regulatory purposes’ at https://www.bankofengland.co.uk/legal/privacy for more details on how this information is handled.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this reporter record was last amended. Recognised person to update each time a record is amended. |
Reporter ID | Integer | Yes | Must be unique | Unique identifier for the reporting individual. Integer assigned by recognised person and used consistently over time. |
Full Name | String | Yes | Max 70 Characters | The legal name of the reporter excluding personal titles. |
Reporter Role | List | No | Owner; Steward; Expert | Denotes the type of reporter. For a detailed description of the reporter roles, see associated guidance. |
Job Title | String | Yes | The formal role or designation the reporter holds within the firm. | |
Department | String | Yes | Max 100 Characters | The division of the firm the reporter is assigned to. |
Work E-mail Address | String | Yes | Max 100 Characters | The reporter’s work e-mail address. |
Date Effective | Date | Yes | YYYY-MM-DD | The date from which a reporter begins to carry out a given reporter role. |
Date Superseded | Date | No | YYYY-MM-DD | The date at which a reporter ceases to carry out a given reporter role. Leave blank if reporter is in-post. |
Primary Work Phone Number | String | Depends on [Reporter Role] | Max 25 Characters | Only mandatory if [Reporter Role] = ‘Owner’ or ‘Steward’, otherwise optional. The reporter’s primary work phone number. Include international dialling code (eg +44) and internal extensions if applicable. Exclude spaces and brackets. |
Secondary Work Phone Number | String | No | Max 25 Characters | The reporter’s alternate work phone number. Include international dialling code (eg +44) and internal extensions if applicable. Exclude spaces and brackets. |
Work Address Line 1 | String | Depends on [Reporter Role] | Max 50 Characters | Only mandatory if [Reporter Role] = ‘Owner’ or ‘Steward’, otherwise optional. The building Name/Number where the reporter’s work is situated. |
Work Address Line 2 | String | No | Max 50 Characters | Street Name/Number where the reporter’s work is situated. |
Work Address Line 3 | String | No | Max 50 Characters | Locality Name where the reporter’s work is situated. |
Work Address City | String | Depends on [Reporter Role] | Max 50 Characters | Only mandatory if [Reporter Role] = ‘Owner’ or ‘Steward’, otherwise optional. City where the reporter’s work is situated. |
Work Address County | String | No | Max 50 Characters | County where the reporter’s work is situated. |
Work Address Country | List | Depends on [Reporter Role] | England; Wales; Scotland; Northern Ireland | Only mandatory if [Reporter Role] = ‘Owner’ or ‘Steward’, otherwise optional. Country where the reporter’s work is situated. |
Work Address Postcode | String | Depends on [Reporter Role] | Max 8 Characters | Only mandatory if [Reporter Role] = ‘Owner’ or ‘Steward’, otherwise optional. Postcode where the reporter’s work is situated. |
Cash Centre Details
Data item name: Cash Centre Details
Data item format: Table
Summary: Details about the premises used to facilitate the storage, processing and transportation of banknotes and coin in the UK.
Applicable to: Operator ONLY
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated per cash centre
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: Should include all cash centres that the operator has its disposal to perform operational activities.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this cash centre record was last amended. Recognised person to update each time a record is amended. |
Cash Centre ID | Integer | Yes | Must be unique | Unique identifier for the cash centre. Integer assigned by recognised person and used consistently over time. |
Cash Centre Name | String | Yes | Max 50 Characters | Comprised of [Firm Abbreviation] and [Cash Centre City] (eg BoE Debden). |
Cash Centre Address Line 1 | String | Yes | Max 50 Characters | Building Name/Number where the cash centre is situated. |
Cash Centre Address Line 2 | String | Yes | Max 50 Characters | Street Name/Number where the cash centre is situated. |
Cash Centre Address Line 3 | String | No | Max 50 Characters | Locality Name where the cash centre is situated. |
Cash Centre City | String | Yes | Max 50 Characters | City where the cash centre is situated. |
Cash Centre County | String | No | Max 50 Characters | County where the cash centre is situated. |
Cash Centre Country | List | Yes | England; Wales; Scotland; Northern Ireland | Country where the cash centre is situated. |
Cash Centre Postcode | String | Yes | Max 8 Characters | Postcode where the cash centre is situated. |
Ownership Type | List | Yes | Freehold; Leasehold; Other contract | Indicate whether the recognised person occupies the cash centre under either a Freehold, Leasehold or other contractual arrangement. |
Cash Centre Owner | String | Yes | Max 500 Characters | If [Ownership Type] = ‘Freehold’, provide the name and identifying details of the person or organisation who is the registered proprietor of the cash centre. If [Ownership Type] = ‘Leasehold’ or ‘Other contract’, provide the name and identifying details of the landlord and other relevant contracting parties. If the cash centre is occupied under a sub-lease, please provide the details of any Head Lessor. |
Cash Centre Operator | String | Yes | Provide the name of the person or organisation who operates the cash centre. | |
Lease Term | Integer | Depends on [Ownership Type] | Must be greater than or equal to 0 | Only mandatory if [Ownership Type] = ‘Leasehold’, otherwise leave blank. The duration of the leasehold agreement expressed in number of months. For example, a 3-year lease would be reported as 36. |
Security of Tenure | Boolean | Depends on [Ownership Type] | True; False | Only mandatory if [Ownership Type] = ‘Leasehold’, otherwise leave blank. Confirm whether the recognised person has the statutory right to be granted a new lease of their cash centre once the current lease expires. Indicate no if that right has been excluded by the terms of the lease. |
Break Clause in-place? | Boolean | Depends on [Ownership Type] | True; False | Only mandatory if [Ownership Type] = ‘Leasehold’, otherwise leave blank. Whether the leasehold arrangement allows either the tenant or landlord to end the tenancy agreement during the lease term. |
Break Clause | Date | Depends on [Break Clause in-place?] | YYYY-MM-DD | Only mandatory if [Break Clause in-place] = ‘True’, otherwise leave blank. From the date of commencement of the lease, from what date in the tenancy can the break clause be invoked? |
Notice Period | Integer | Depends on [Break Clause in-place?] | Must be greater than or equal to 0 | Only mandatory if [Break Clause in-place] = ‘True’, otherwise leave blank. How many calendar months’ notice does either party need to give before invoking the break clause? For example, a lease with a 1-year break-clause would be reported as 12. |
Lease Expiry Date | Date | Depends on [Ownership Type] | YYYY-MM-DD | Only mandatory if [Ownership Type] = ‘Leasehold’, otherwise leave blank. The last day of the Lease Term. |
NCS Eligibility | List | Yes | None; Conditional; Full | Is the cash centre recognised as a Note Circulation Scheme cash centre? See NCS Rulebook for eligibility definitions. |
Store BoE Banknotes? | Boolean | Yes | True; False | Does the cash centre currently store cages of banknotes issued by the Bank of England? |
Authenticate BoE Banknotes? | Boolean | Yes | True; False | Does the cash centre currently authenticate banknotes issued by the Bank of England? |
Fitness Sort BoE Banknotes? | Boolean | Yes | True; False | Does the cash centre currently undertake fitness sorting of banknotes issued by the Bank of England? |
Dispense BoE Banknotes? | Boolean | Yes | True; False | Does the cash centre currently pack and distribute banknotes issued by the Bank of England to wholesale customers? |
Processes Coin? | Boolean | Yes | True; False | Does the cash centre currently authenticate coin and out sort damaged/garbled Coin issued by The Royal Mint? |
S&NI Banknote Centre? | Boolean | Yes | True; False | At present, is the cash centre expressly intended to store, process, and dispense banknotes issued by the Scotland and Northern Ireland commercial banknote issuers? |
Foreign Currency Centre? | Boolean | Yes | True; False | At present, is the cash centre expressly intended to store, process, and dispense banknotes that are not issued by either the Bank of England, Scotland and Northern Ireland commercial banknote issuers or The Royal Mint? |
Current Cash Centre Service Offering | String | No | Max 1,000 Characters | Detail any additional functions/services currently being provided at this cash centre that are not already addressed in the Cash Centre Details table (eg Other Sterling Cash handling, High Value Document/Gold/Jewellery storage etc.). |
Cash Centre Status | List | Yes | Operational; Mothballed; Closed | Operational = Cash centre is open and carrying out at least 1 operational activity. Mothballed = Cash centre remains available for use by the recognised person but does not currently carry out any operational activities. Closed = Cash centre has been shut down permanently. |
Cash Centre Opening Date | Date | Yes | YYYY-MM-DD | The first day from which a cash centre functions as an ‘Operational’ cash centre. |
Cash Centre Mothballed Date | Date | Depends on [Cash Centre Status] | YYYY-MM-DD | Only mandatory if [Cash Centre Status] = ‘Mothballed’, otherwise leave blank. The first day from which a cash centre is Mothballed. |
Cash Centre Closing Date | Date | Depends on [Cash Centre Status] | YYYY-MM-DD | Only mandatory if [Cash Centre Status] = ‘Closed’, otherwise leave blank. The first day from which a cash centre is Closed. |
Renewable Electricity Contract? | Boolean | Yes | True; False | Does this cash centre use an electricity contract based on 100% renewable energy generation (i.e. ‘energy from renewable non-fossil sources, namely wind, solar, aerothermal, geothermal, hydrothermal and ocean energy, hydropower, biomass, landfill gas, sewage treatment plant gas and biogases’)? |
Renewable Electricity Contract Details | String | No | Max 1,000 Characters | Describe the terms of the current electricity contract. If [Renewable Electricity Contract] = ‘True’, describe how this is certified as renewable. Otherwise explain if and when a renewable electricity contract will be obtained. |
Number of vaults | Integer | Yes | Must be greater than or equal to 0 | Including vaults used as part of the NCS Bond facility, state how many secure vault spaces suitable for storing cash are installed at the cash centre. |
Number of secure vehicle loading bays | Integer | Yes | Must be greater than or equal to 0 | State how many secure vehicle loading bays are installed at the cash centre. |
Back-up Generator? | Boolean | Yes | True; False | Indicate whether the cash centre has a generator capable of supporting typical operation. |
Blackout Exemption? | Boolean | Yes | True; False | Indicate whether the cash centre has a blackout exemption or dedicated grid connection. |
Battery Backup? | Boolean | Yes | True; False | Indicate whether the cash centre has a battery backup capable of supporting typical BAU operation. |
Uninterruptable Power Supply? | Boolean | Yes | True; False | Indicate whether the cash centre has Uninterruptable Power Supplies (UPS) installed for business-critical IT equipment. |
Vault Capacity in Cages (BoE + S&NI Banknotes) | Integer | Yes | Must be greater than or equal to 0 and not exceed 20,000 cages | Assuming no other type of cash is stored, the maximum number of standard banknote cages that can be stored at a cash centre with the use of blockstacking while complying with site health & safety requirements, not taking into account insurance limits. This should include all usable, secured vault space, including Bond vaults where applicable. |
Vault Capacity in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and not exceed 20,000 cages | Assuming no other type of cash is stored, the maximum number of standard coin cages that can be stored at a cash centre with the use of blockstacking while complying with site health & safety requirements, not taking into account insurance limits. This should include all usable, secured vault space. |
Bond Capacity in Cages (BoE Banknotes) | Integer | Depends on [NCS Eligibility] | Must be greater than or equal to 0 and not exceed 20,000 cages | Only mandatory if [NCS Eligibility] = ‘Conditional’ or ‘Full’, otherwise leave blank. The maximum number of standard BoE cages that can be stored at the cash centre’s Bond Vault area with the use of blockstacking while complying with site health & safety requirements, not taking into account insurance limits. Exclude any vault space that is not part of Bond. |
Insurance Coverage Type | List | Yes | Cash Centre Specific; Estate Wide | Is the insurance coverage applicable to the individual cash centre location (Cash Centre Specific) or all the cash centres owned by the operator (Estate Wide)? |
Estate Wide Insurance Limit | Integer – GBP | Depends on [Insurance Coverage Type] | Must be greater than or equal to 0 and not exceed £100 billion. (£100,000,000,000) | Only mandatory if [Insurance Coverage Type] = ‘Estate Wide’, otherwise leave blank. Across the recognised person’s entire cash centre estate, the total value of protection available for loss/damage/destruction of BoE banknotes, Royal Mint coin and banknotes issued by the Scotland and Northern Ireland commercial issuers. To be expressed in GBP rounded down to the nearest pound sterling. |
Cash Centre Specific Insurance Limit | Integer – GBP | Depends on [Insurance Coverage Type] | Must be greater than or equal to 0 and not exceed £10 billion. (£10,000,000,000) | Only mandatory if [Insurance Coverage Type] = ‘Cash Centre Specific’, otherwise leave blank. At the given cash centre, the total value of protection available for loss/damage/destruction of BoE banknotes, Royal Mint coin and banknotes issued by the Scotland and Northern Ireland commercial issuers. To be expressed in GBP rounded down to the nearest pound sterling. |
Commentary | String | No | Max 5,000 Characters | Note any observations about the information provided in the Cash Centre Details record. |
Vault Utilisation
Data item name: Vault Utilisation
Data item format: Table
Summary: Reports use of storage capacity in cash centres.
Applicable to: Operator ONLY
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated for each day in the calendar month per cash centre
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Monthly
Reporting period: Previous calendar month
Other information: Daily reporting includes weekends and public/bank holidays.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Reporting Date | Date | Yes | YYYY-MM-DD | The calendar date the vault utilisation figures relate to. |
Cash Centre ID | Integer | Yes | Must be a valid [Cash Centre ID] from Cash Centre Details | Associates the vault utilisation figures with a given cash centre. [Cash Centre ID] must exist in the Cash Centre Details table. |
£5 Vault Utilisation in Cages (BoE Banknotes) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of £5 Bank of England banknote cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
£10 Vault Utilisation in Cages (BoE Banknotes) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of £10 Bank of England banknote cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
£20 Vault Utilisation in Cages (BoE Banknotes) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of £20 Bank of England banknote cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
£50 Vault Utilisation in Cages (BoE Banknotes) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of £50 Bank of England banknote cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
1p Vault Utilisation in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of 1p Coin cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
2p Vault Utilisation in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of 2p Coin cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
5p Vault Utilisation in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of 5p Coin cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose.. If none reported, provide a 0 value. |
10p Vault Utilisation in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of 10p Coin cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
20p Vault Utilisation in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of 20p Coin cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
50p Vault Utilisation in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of 50p Coin cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
£1 Vault Utilisation in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of £1 Coin cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
£2 Vault Utilisation in Cages (Coin) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | The number of £2 Coin cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
All Denominations Vault Utilisation in Cages (S&NI Banknotes) | Integer | Yes | Must be greater than or equal to 0 and less than or equal to 20,000 cages. | Across all denominations and S&NI note issuers, the number of S&NI banknote cages stored at a given cash centre at day end. Part cages should count as 1 cage for this purpose. If none reported, provide a 0 value. |
Total Vault Utilisation in Value (BoE Banknotes) | Integer – GBP | Yes | Must be greater than or equal to 0 and less than or equal to £10 billion (£10,000,000,000). | In GBP, the sum value of all Bank of England banknotes stored at a given cash centre at day end. If none reported, provide a 0 value. |
Total Vault Utilisation in Value (Coin) | Integer – GBP | Yes | Must be greater than or equal to 0 and less than or equal to £10 billion (£10,000,000,000). | In GBP, the sum value of all Coin stored at a given cash centre at day end. Rounded up to the nearest pound sterling. If none reported, provide a 0 value. |
Total Vault Utilisation in Value (S&NI Banknotes) | Integer – GBP | Yes | Must be greater than or equal to 0 and less than or equal to £10 billion (£10,000,000,000). | In GBP, the sum value of all S&NI banknotes stored at a given cash centre at day end. If none reported, provide a 0 value. |
Commentary | String | No | Max 5,000 Characters | Note any observations about the information provided in the Vault Utilisation record, including methodology used in calculations. |
Key Equipment Details
Data item name: Key Equipment Details
Data item format: Table
Summary: Information about principal machinery used to process banknotes and coins at cash centres owned or affiliated to the recognised person.
Applicable to: Operator ONLY
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated per equipment installation (i.e. A machine that has been installed at Cash Centre A before being relocated to Cash Centre B would have 2 records)
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: Include all medium/high speed or bulk processing equipment at cash centres reported in the Cash Centre Details table.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this key equipment record was last amended. Recognised person to update each time a record is amended. |
Equipment Item ID | Integer | Yes | Must be unique | Unique identifier for the individual equipment item. Integer assigned by recognised person and used consistently over time. |
Cash Centre ID | Integer | Yes | Must be a valid [Cash Centre ID] from Cash Centre Details | Associates the equipment item with the cash centre it is presently located in. [Cash Centre ID] must exist in the Cash Centre Details table. |
Equipment Type | List | Yes | High Speed Note Sorter; Medium Speed Note Sorter; Bulk Coin Sorter; Bulk Coin Bagger; Cash Packaging Applicator; Cash Packaging Stripper | The category applicable to the equipment item. Desktop equipment should be reported in the Desktop Equipment Details table. |
Equipment Manufacturer | String | Yes | Max 50 Characters | The name of the equipment manufacturer. For example, Cash Processing Solutions or Giesecke & Devrient. |
Equipment Model | String | Yes | Max 50 Characters | A description of the equipment model. For example, CPS 7000 or BPS M5-22. |
Equipment Installation Date | Date | Yes | YYYY-MM-DD | The date on which the equipment item was first used in BAU operations at the cash centre. |
Expected Equipment Service Life (Years) | Integer | Yes | N/A | In years, the approximate duration the machine is expected to last from the [Equipment Installation Date] until decommissioning is required. |
Equipment Status | List | Yes | Operational; Undergoing Repair; Mothballed; Relocated; Decommissioned; | Describes the equipment item’s current condition. Operational = Equipment is actively used in BAU operations. Undergoing Repair = Equipment is temporarily out of service for a significant time period for non-routine maintenance. Mothballed = Equipment is ready for use in BAU operations but is not currently in use. Relocated = Equipment has been moved to another cash centre operated by the recognised person. Decommissioned = Equipment is permanently out of service as it has reached the end of its serviceable life or is no longer used by the recognised person. |
Equipment Decommission Date | Date | No | YYYY-MM-DD | The last day of operation of the equipment item before it was decommissioned. |
Equipment Relocation Date | Date | No | YYYY-MM-DD | The last day of operation of the equipment before it was moved to another cash centre. |
Equipment Previously Relocated? | Boolean | Yes | True; False | Records whether the equipment item has been previously moved from another cash centre since the Firm became designated under a wholesale cash distribution order. |
Previous Equipment Item ID | Integer | Depends on [Equipment Previously Relocated] | Must be a valid [Equipment Item ID] from Key Equipment Details that previously has been reported. | Only mandatory if [Equipment Relocated?] = ‘True’, otherwise leave blank. Cannot be the same as [Equipment ID]. Provides a link to the previous equipment item record. |
Coin Checking and Validation Framework Approved? | Boolean | Yes | True; False | Against The Royal Mint’s Coin Checking and Validation Framework, does the [Equipment Model] achieve ‘Pass’ accreditation? See Coin Checking and Validation in the UK for a list of machines that meet the standard. |
£1 High Security Feature Capable? | Boolean | Yes | True; False | Does the [Equipment Model] check for the £1 high security feature (HSF)? |
BoE Machine Testing Framework Standard | List | Yes | None; Standard; Silver; Gold | Does the [Equipment Model] meet any of the Bank of England Machine Testing Framework (MTF) standards? See Testing automatic banknote handling machines for details on which machines meet each MTF standard. |
BoE Banknote Fitness Sorting capable? | Boolean | Yes | True; False | Does the [Equipment Model] currently sort BoE banknotes according to fitness standards prescribed by the Bank of England’s Note Circulation Scheme? |
Machine Add-ons Installed? | Boolean | Yes | True; False | Does the equipment have modifications that have been designed to affect the throughput of the machine? |
Machine Add-on Details | String | Depends on [Machine Add-ons Installed?] | Max 500 Characters | Only mandatory if [Machine Add-ons Installed?] = ‘True’, otherwise leave blank. Indicate what modifications are currently installed on the equipment. Examples of modifications include automated note loading systems and additional machine pockets/stackers. |
Theoretical Throughput (Pieces per hour) | Integer | Yes | Must be greater than 0 and less than 200,000. | Factoring in the [Equipment Model] and any machine add-ons, state the maximum number of cash items that can be processed in 1 hour, as detailed by the manufacturer’s specifications. |
Commentary | String | No | Max 5,000 Characters | Note any observations about the information provided in the Key Equipment Details record. |
Desktop Equipment Details
Data item name: Desktop Equipment Details
Data item format: Table
Summary: Information about smaller machinery used to process (reconcile, authenticate, fitness check, sort, or package) banknotes and coins at a recognised person’s cash centre.
Applicable to: Operator ONLY
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated per ‘group’ of desktop equipment of a given model in use at each cash centre.
Reporting frequency: Update as required
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: Include all desktop equipment present at cash centres reported in the Cash Centre Details table.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this desktop equipment record was last amended. Recognised person to update each time a record is amended. |
Equipment Set ID | Integer | Yes | Must be unique | Unique identifier for the equipment set. Integer assigned by recognised person and used consistently over time. |
Cash Centre ID | Integer | Yes | Must be a valid [Cash Centre ID] from Cash Centre Details | Associates the equipment set with the cash centre it is presently located in. [Cash Centre ID] must exist in the Cash Centre Details table. |
BoE Banknote Capable? | Boolean | Yes | True; False | Is the equipment capable of processing Bank of England notes? |
S&NI Banknote Capable? | Boolean | Yes | True; False | Is the equipment capable of processing banknotes issued by Scotland & Northern Ireland banknote issuers? |
Coin Capable? | Boolean | Yes | True; False | Is the equipment capable of processing coin issued by The Royal Mint? |
Equipment Manufacturer | String | Yes | Max 50 Characters | The name of the equipment manufacturer. For example, Glory. |
Equipment Model | String | Yes | Max 50 Characters | A description of the equipment model. For example, Glory Vertera 6G. |
Coin Checking and Validation Framework Approved? | Boolean | Yes | True; False | Against The Royal Mint’s Coin Checking and Validation Framework, does the [Equipment Model] achieve ‘Pass’ accreditation? See Coin Checking and Validation in the UK for a list of machines that meet the standard. |
£1 High Security Feature Capable? | Boolean | Yes | True; False | Does the [Equipment Model] check for the £1 high security feature (HSF)? |
BoE Machine Testing Framework Standard | List | Yes | None; Standard; Silver; Gold | Does the [Equipment Model] meet any of the Bank of England Machine Testing Framework (MTF) standards? See Testing automatic banknote handling machines for details on which machines meet each MTF standard. |
Equipment Quantity | Integer | Yes | Must be greater than or equal to 0 | The number of equipment items of a given manufacturer and model that are currently installed and operational at the cash centre. |
Theoretical Throughput Per Equipment Item (Pieces per hour) | Integer | Yes | Must be greater than 0 and less than 200,000 pieces per hour. | Per equipment item, factoring in the [Equipment Model] and any machine add-ons, state the maximum number of cash items that can be processed in 1 hour, as detailed by the manufacturer’s specifications. |
Commentary | String | No | Max 5,000 Characters | Note any observations about the information provided in the Desktop Equipment Details record. |
Cash Centre Throughput
Data item name: Cash Centre Throughput
Data item format: Table
Summary: Information about the cash processing taking place at each cash centre.
Applicable to: Operator ONLY
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated monthly per cash centre
Reporting frequency: Monthly
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting period: Previous calendar month
Other information: Where no BoE Banknote and/or S&NI Banknote and/or Coin handling takes place at a given cash centre, input 0 into the respective attribute.
Service Level Agreement Details
Data item name: Service Level Agreement Details
Data item format: Table
Summary: Describes the service level agreements (SLAs) put in place by the recognised person in accordance with the Code of Practice on Information gathering.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated according to the number of SLAs a recognised person has.
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: For details on the SLAs expected from recognised persons, see Annex 3 – Providing Service Level Agreement Data.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this SLA record was last amended. Recognised person to update each time a record is amended. |
SLA ID | Integer | Yes | Must be unique | Unique identifier for the Service Level Agreement (SLA). Integer assigned by recognised person and used consistently over time. |
SLA Type | List | Yes | Firm-Wide; Cash Centre Specific; Material Third-Party; Wholesale Customer | Denotes what the SLA applies to. Firm-Wide = An SLA that aggregates performance across a recognised person’s operations. Cash Centre Specific = An SLA that summarises performance at a particular cash centre operated by the recognised person. Material Third-Party = An SLA where performance is substantially driven by a material third-party arrangement. Wholesale Customer = An SLA that is linked to the recognised person’s performance of its specified relevant functions in relation to a specific wholesale customer. |
Cash Centre ID | Integer | Depends on [SLA Type] | Must be a valid [Cash Centre ID] from Cash Centre Details | Only mandatory if [SLA Type] = ‘Cash Centre-specific’, otherwise leave blank. [Cash Centre ID] must exist in the Cash Centre Details table. |
Arrangement ID | Integer | Depends on [SLA Type] | Must be a valid [Arrangement ID] from Material Third-Party Arrangements | Only mandatory if [SLA Type] = ‘Third-party’, otherwise leave blank. [Arrangement ID] must exist in the Material Third-Party Arrangements table. |
Customer ID | Integer | Depends on [SLA Type] | Must be a valid [Customer ID] from Wholesale Customer Details | Only mandatory if [SLA Type] = ‘Wholesale Customer’, otherwise leave blank. [Customer ID] must exist in the Wholesale Customer Details table. |
SLA Name | String | Yes | Max 100 Characters | The full, unabbreviated version of the SLA name. |
SLA Category | String | Yes | Max 50 Characters | Paraphrase the topic the SLA relates to (eg Cash in Transit activity, Branch Deliveries, ATM Replenishment, Cash Processing etc.) |
SLA Start Date | Date | Yes | YYYY-MM-DD | The first day the SLA was applied. |
SLA End Date | Date | No | YYYY-MM-DD | The last day the SLA was applied. Leave blank if SLA is active. |
SLA Definition | String | Yes | Max 1,000 Characters | A description of the SLA’s purpose. Include details of what deliverable, task or process the SLA applies to, as well as any deadlines, time limits, quantitative targets, or other relevant criteria. Include a description of what ‘Red’, ‘Amber’, ‘Green’ or ‘Pass’ and ‘Fail’ looks like. |
SLA Monitoring Plan | String | Yes | Max 1,000 Characters | Detail what actionable measures the recognised person has in-place for ensuring that the SLA is met, including the steps it can take to hold itself/others to account. |
SLA Unit | List | Yes | Percentage; Number | Denotes the unit of measurement the SLA is reported against. Percentage = Target is expressed as a fraction of 100 (0-100%) up to 2 decimal places. Number = Target is expressed as a quantity or amount up to 2 decimal places. For examples of how to apply the [SLA Unit], see Annex 3 – Providing Service Level Agreement Data. |
SLA Assessment Type | List | Yes | RAG; Pass/Fail | Signifies how performance for the SLA is monitored. RAG = SLA performance can be rated as either ‘Red’ (Major breach), ‘Amber’ (Minor breach) or ‘Green’ (On-track). Pass/Fail = SLA can be rated as either pass/on-track or fail/breach. For examples of how to apply the [SLA Assessment Type], see Annex 3 – Providing Service Level Agreement Data. |
SLA Rating Approach | List | Yes | High Value Favourable; Low Value Favourable | Determines whether a favourable [SLA Figure] is represented by a high value or low value. For examples of how to apply the [SLA Rating Approach], see Annex 3 – Providing Service Level Agreement Data. |
SLA Amber Lower Limit | Numeric | Yes | 2 decimal places If [SLA Unit] = ‘Percentage’, value must be greater than or equal to 0 AND less than or equal to 100. | The threshold value (including the value itself) above which the SLA’s RAG rating is classified as amber and is consequently a minor breach. If [SLA Assessment Type] = ‘RAG’, SLA can be rated as amber/minor breach, so [SLA Amber Lower Limit] must be less than [SLA Amber Upper Limit] If [SLA Assessment Type] = ‘Pass/Fail’, SLA can only be rated as red/major breach or green/on-track only, [SLA Amber Lower Limit] must equal [SLA Amber Upper Limit]. For examples of how to apply [SLA Amber Lower Limit] and [SLA Amber Upper Limit], see Annex 3 – Providing Service Level Agreement Data. |
SLA Amber Upper Limit | Numeric | Yes | 2 decimal places If [SLA Unit] = ‘Percentage’, value must be greater than or equal to 0 AND less than or equal to 100. | The threshold value (including the value itself) below which the SLA’s RAG rating is classified as amber and is consequently a minor breach. If [SLA Assessment Type] = ‘RAG’, SLA can be rated as amber/minor breach, [SLA Amber Upper Limit] must be greater than [SLA Amber Lower Limit] If [SLA Assessment Type] = ‘Pass/Fail’, SLA can only be rated as red/major breach or green/on-track only, [SLA Amber Upper Limit] must equal [SLA Amber Lower Limit]. For examples of how to apply [SLA Amber Lower Limit] and [SLA Amber Upper Limit], see Annex 3 – Providing Service Level Agreement Data. |
Service Level Agreement Performance
Data item name: Service Level Agreement Performance
Data item format: Table
Summary: Tracks whether recognised persons are meeting their stated service level agreements (SLAs).
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated monthly according to the number of SLAs a recognised person has.
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Monthly
Reporting period: Previous calendar month
Other information: For detail on the SLAs expected from recognised persons, see Annex 3 – Providing Service Level Agreement Data.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Reporting Period Start Date | Date | Yes | YYYY-MM-DD | The first day the information relates to. For monthly data, this is the first day of the month (2025-01-01). |
Reporting Period End Date | Date | Yes | YYYY-MM-DD | The last day the information relates to. For monthly data, this is the last day of the month (2025-01-31). Cannot be earlier than [Reporting Period Start Date]. |
SLA ID | Integer | Yes | Must be a valid [SLA ID] from Service Level Agreement Details | Associates the SLA performance metrics with a given SLA. [SLA ID] must exist in the Service Level Agreement Details table. |
SLA Figure | Numeric | Yes | 2 decimal places | The latest actual performance of the recognised person against the SLA for the calendar month. If SLA performance expressed as a Percentage, value must be greater than or equal to 0 AND less than or equal to 100. For example, 99.95% should be provided as 99.95 |
SLA Commentary | String | Depends on [SLA Figure] and resulting rating derived from the corresponding [SLA ID] record in Service Level Agreement Details | Max 2,000 Characters | Only mandatory if [SLA Figure] is flagged as ‘Fail’ for Pass/Fail SLAs and ‘Red’ or ‘Amber’ for RAG SLAs according to the [SLA Assessment Type], [SLA Amber Lower Limit] and [SLA Amber Upper Limit] defined in the corresponding [SLA ID] record in the Service Level Agreement Details table. [SLA Commentary] optional if [SLA Figure] is ‘Pass’ for Pass/Fail SLAs and ‘Green’ for RAG SLAs. Record any observations and occurrences as to the reasons for the stated [SLA Figure], including actions being taken to improve performance, particularly if remediation efforts are required to rectify a performance breach. |
Material Third-Party Arrangements
Data item name: Material Third-Party Arrangements
Data item format: Table
Summary: Details the recognised person’s material third-party arrangements.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated for each material third-party arrangement.
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: For detail on the types of material third-party arrangements expected to be reported by recognised persons, see guidance to Code of Practice – Third-Party Arrangements. Renewals of existing material third-party arrangements should be represented by a new record.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this material third-party arrangement record was last amended. Recognised person to update each time a record is amended. |
Arrangement ID | Integer | Yes | Must be unique | Unique identifier for the material third-party arrangement. Integer assigned by recognised person and used consistently over time. |
Arrangement Type | List | Yes | Cash Processing Equipment; Cash in Transit Activity; Cash Packaging; IT Provision; Upkeep of Security Measures; Financial Settlement; Cash Handling | The function of the material third-party arrangement. See guidance to Code of Practice – Third-Party Arrangements for details on how to categorise/classify. |
Arrangement Provider Name | String | Yes | Max 100 Characters | The full, legal name of the provider of the material third-party arrangement. |
Arrangement Status | List | Yes | Active; Lapsed | Records the current state of the material third-party arrangement. Active = Arrangement is currently in-place with the material third-party. Lapsed = Arrangement is no longer in-place with the material third-party either due to expiry or termination. |
Negotiations in-progress? | Boolean | Depends on [Arrangement Status] | True; False | Only mandatory if [Arrangement Status] = ‘Active’, otherwise leave blank. The arrangement is currently subject to discussions about renewing an arrangement between the recognised person and material third-party. |
Due to Lapse? | Boolean | Depends on [Arrangement Status] and [Negotiations in-progress?] | True; False | Only mandatory if [Arrangement Status] = ‘Active’ and [Negotiations in-progress?] = False otherwise leave blank. The arrangement is currently active but at contract end, there are no plans to renew the material third-party arrangement? |
Arrangement Start Date | Date | Yes | YYYY-MM-DD | The first day that the material third-party arrangement comes into effect. |
Arrangement Expiry Date | Date | Yes | YYYY-MM-DD | The last day that the material third-party arrangement applies to both parties. |
Arrangement Description | String | Yes | Max 5,000 Characters | Details about the material third-party arrangement. Include information on the goods/services provided, pertinent contract terms (closed or open-ended contract, notice period, clauses for contract revision or termination), and whether step-in rights or alternative third-party providers have been identified by the recognised person. |
Wholesale Customer Details
Data item name: Wholesale Customer Details
Data item format: Table
Summary: Lists wholesale customers of the operator or backing FI (as applicable).
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated for each wholesale customer of the operator or backing FI (as applicable).
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: Each operator and backing FI to provide information on all DIRECT wholesale customers they provide cash products to. For operators, this is typically their backing FIs. For backing FIs, this is typically their wholesale customers that they arrange cash provision for.
As a minimum, at least 90% of the recognised person’s total customer deposits and at least 90% of total customer dispense volumes should be disclosed as individual records that identify each wholesale customer being serviced. The remaining 10% of its total wholesale customer deposits and remaining 10% of its total wholesale customer dispense may be aggregated under ‘group’ records. Alternatively, at the recognised person’s discretion, it may choose to provide ‘individual’ records identifying every wholesale customer.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this wholesale customer record was last amended. Recognised person to update each time a record is amended. |
Customer ID | Integer | Yes | Must be unique | Unique identifier for one wholesale customer OR a ‘group’ of wholesale customers. Integer assigned by recognised person and used consistently over time. |
Individual or Group Record? | List | Yes | Individual; Group | Indicate whether the record applies to 1 or more wholesale customers of the recognised person. Individual = Record represents one wholesale customer. Group = Record represents multiple wholesale customers of a given [Sector Classification]. |
Customer Name | String | Yes | Max 100 Characters | Provide the full, unabbreviated name of the wholesale customer. |
Sector Classification | List | Yes | Own ATM; Other FI ATM; Independent ATM Deployer; Own FI; Other FI; FOREX; Retailer; Other | Identifies the type of industry the wholesale customer operates in. See Annex 4 – Classifying Wholesale Customers for details on how to categorise. |
Customer Companies Registration Number (CRN) | String | Depends on [Individual or Group Record?] and [Sector Classification] | Must be 8 Characters long. Alphanumeric and Capitalised. | Only mandatory if [Individual or Group Record?] = ‘Individual’ AND [Sector Classification] is NOT = ‘Own ATM’ or ‘Own FI’ or ‘Other’. Otherwise optional. The 8-character, alpha-numeric code that the wholesale customer is registered with Companies House. If wholesale customer does not have CRN, leave blank. |
Customer Legal Entity Identifier (LEI) | String | Depends on [Individual or Group Record?] and [Sector Classification] | Must be 20 Characters long. Alphanumeric and Capitalised. | Only mandatory if [Individual or Group Record?] = ‘Individual’ AND [Sector Classification] is NOT = ‘Own ATM’ or ‘Own FI’ or ‘Other’. Otherwise optional. A 20-character, alpha-numeric code based on the ISO 17442 standard developed by the International Organization for Standardization (ISO). If wholesale customer does not have LEI, leave blank. |
Customer Requires BoE Banknotes? | Boolean | Depends on [Individual or Group Record?] | True; False | Only mandatory if [Individual or Group Record?] = ‘Individual’, otherwise optional. Indicate whether the wholesale customer requires Bank of England Banknotes from the recognised person. |
Customer Requires Coin? | Boolean | Depends on [Individual or Group Record?] | True; False | Only mandatory if [Individual or Group Record?] = ‘Individual’, otherwise optional. Indicate whether the wholesale customer requires Coin issued by The Royal Mint from the recognised person. |
Customer Requires S&NI Banknotes? | Boolean | Depends on [Individual or Group Record?] | True; False | Only mandatory if [Individual or Group Record?] = ‘Individual’, otherwise optional. Indicate whether the wholesale customer requires commercially issued Scotland & Northern Ireland Banknotes from the recognised person. |
Customer Description | String | Yes | Max 2,000 Characters | Describe the nature of the wholesale customer’s activities. |
Standard or Bespoke Pricing? | List | Depends on [Individual or Group Record?] | Standard; Bespoke | Only mandatory if [Individual or Group Record?] = ‘Individual’, otherwise optional. Indicate what type of wholesale cash charges apply to the wholesale customer. Standard = wholesale customer incurs typical charges as publicly advertised by the recognised person. Bespoke = wholesale customer incurs charges that are specific to its relationship with the recognised person. |
Customer Arrangement Setup | List | Depends on [Individual or Group Record?] | Rolling; Fixed | Only mandatory if [Individual or Group Record?] = ‘Individual’, otherwise leave blank. Rolling = a contract that continues indefinitely until either party decides to terminate it. Fixed = a contract with a particular start and end date. |
Customer Contract Start Date | Date | Depends on [Contract Setup] | YYYY-MM-DD | Only mandatory if [Customer Contract Setup] = ‘Fixed’, otherwise leave blank. State the first day of the wholesale customer contract term. |
Customer Contract End Date | Date | Depends on [Contract Setup] | YYYY-MM-DD | Only mandatory if [Customer Contract Setup] = ‘Fixed’, otherwise leave blank. State the last day of the wholesale customer contract term. |
Customer Status | List | Depends on [Individual or Group Record?] | Active; Lapsed | Only mandatory if [Individual or Group Record?] = ‘Individual’, otherwise leave blank. Indicate the current position of the wholesale customer contract. Active = wholesale customer contract is live, with wholesale cash services being provided. Lapsed = wholesale customer contract business has concluded, with wholesale cash services no longer being provided. |
Negotiations in-progress? | Boolean | Depends on [Individual or Group Record?] and [Customer Status] | True; False | Only mandatory if [Individual or Group Record?] = ‘Individual’ and [Customer Status] = ‘Active’, otherwise leave blank. Discussions are in-progress with the wholesale customer to renew their contract? |
Due to Lapse? | Boolean | Depends on [Individual or Group Record?] and [Customer Status] and [Negotiations in-progress?] | True; False | Only mandatory if [Individual or Group Record?] = ‘Individual,’ [Customer Status] = ‘Active’, and [Negotiations in-progress?] = ‘False,’ otherwise leave blank. The wholesale customer contract is due to end with all parties aware that there are no plans to renew? |
Commentary | String | No | Max 5,000 Characters | Note any observations about the information provided in the Wholesale Customer Details record. |
Wholesale Customer Flows
Data item name: Wholesale Customer Flows
Data item format: Table
Summary: Logs volumes information by denomination about a recognised person’s wholesale customers.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated monthly for each wholesale customer at a recognised person.
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Monthly
Reporting period: Previous calendar month
Other information: See Wholesale Customer Details for more information. Volumes by denomination and cash issuer is mandatory for customer dispense and optional for customer deposits. Wholesale Customer Flows information does not need to be provided for wholesale customers whose contractual relationship with the recognised person has ended.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Reporting Period Start Date | Date | Yes | YYYY-MM-DD | The first day the information relates to. For monthly data, this is the first day of the month (2025-01-01). |
Reporting Period End Date | Date | Yes | YYYY-MM-DD | The last day the information relates to. For monthly data, this is the last day of the month (2025-01-31). Cannot be earlier than [Reporting Period Start Date]. |
Customer ID | Integer | Yes | Must be a valid [Customer ID] from Wholesale Customer Details | Associates the wholesale customer flow information with a given wholesale customer. [Customer ID] must exist in the Wholesale Customer Details table. |
Customer Dispense Volume – ALL GBP CASH | Integer | Yes | Must be greater than or equal to 0 | Across all UK cash issuers/types, the number of GBP (From all UK cash issuers) banknotes or coin dispensed to a wholesale customer by the recognised person during a given calendar month. |
Customer Dispense Value – ALL GBP CASH | Integer – GBP | Yes | Must be greater than or equal to 0 | In GBP, across all UK cash issuers/types, the value of cash dispensed to a wholesale customer by the recognised person during a given calendar month. Rounded down to the nearest pound sterling. |
Customer Deposit Volume – ALL GBP CASH | Integer | Yes | Must be greater than or equal to 0 | Across all UK cash issuers/types, the number of cash deposits from the wholesale customer processed by the recognised person during a given calendar month. |
Customer Deposit Value – ALL GBP CASH | Integer – GBP | Yes | Must be greater than or equal to 0 | In GBP, across all UK cash issuers/types, the value of GBP deposits from the wholesale customer processed by the recognised person during a given calendar month. Rounded down to the nearest pound sterling. |
£5 Customer Dispense Volume – BoE Banknotes | Integer | Yes | Must be greater than or equal to 0 | The number of £5 Bank of England banknotes dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£5 Customer Deposit Volume – BoE Banknotes | Integer | No | Must be greater than or equal to 0 | The number of £5 Bank of England banknote deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£10 Customer Dispense Volume – BoE Banknotes | Integer | Yes | Must be greater than or equal to 0 | The number of £10 Bank of England banknotes dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£10 Customer Deposit Volume – BoE Banknotes | Integer | No | Must be greater than or equal to 0 | The number of £10 Bank of England banknote deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£20 Customer Dispense Volume – BoE Banknotes | Integer | Yes | Must be greater than or equal to 0 | The number of £20 Bank of England banknotes dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£20 Customer Deposit Volume – BoE Banknotes | Integer | No | Must be greater than or equal to 0 | The number of £20 Bank of England banknote deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£50 Customer Dispense Volume – BoE Banknotes | Integer | Yes | Must be greater than or equal to 0 | The number of £50 Bank of England banknotes dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£50 Customer Deposit Volume – BoE Banknotes | Integer | No | Must be greater than or equal to 0 | The number of £50 Bank of England banknote deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
1p Customer Dispense Volume – Coin | Integer | Yes | Must be greater than or equal to 0 | The number of 1p Royal Mint coin dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
1p Customer Deposit Volume – Coin | Integer | No | Must be greater than or equal to 0 | The number of 1p Royal Mint coin deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
2p Customer Dispense Volume – Coin | Integer | Yes | Must be greater than or equal to 0 | The number of 2p Royal Mint coin dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
2p Customer Deposit Volume – Coin | Integer | No | Must be greater than or equal to 0 | The number of 2p Royal Mint coin deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
5p Customer Dispense Volume – Coin | Integer | Yes | Must be greater than or equal to 0 | The number of 5p Royal Mint coin dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
5p Customer Deposit Volume – Coin | Integer | No | Must be greater than or equal to 0 | The number of 5p Royal Mint coin deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
10p Customer Dispense Volume – Coin | Integer | Yes | Must be greater than or equal to 0 | The number of 10p Royal Mint coin dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
10p Customer Deposit Volume – Coin | Integer | No | Must be greater than or equal to 0 | The number of 10p Royal Mint coin deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
20p Customer Dispense Volume – Coin | Integer | Yes | Must be greater than or equal to 0 | The number of 20p Royal Mint coin dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
20p Customer Deposit Volume – Coin | Integer | No | Must be greater than or equal to 0 | The number of 20p Royal Mint coin deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
50p Customer Dispense Volume – Coin | Integer | Yes | Must be greater than or equal to 0 | The number of 50p Royal Mint coin dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
50p Customer Deposit Volume – Coin | Integer | No | Must be greater than or equal to 0 | The number of 50p Royal Mint coin deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£1 Customer Dispense Volume – Coin | Integer | Yes | Must be greater than or equal to 0 | The number of £1 Royal Mint coin dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£1 Customer Deposit Volume – Coin | Integer | No | Must be greater than or equal to 0 | The number of £1 Royal Mint coin deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£2 Customer Dispense Volume – Coin | Integer | Yes | Must be greater than or equal to 0 | The number of £2 Royal Mint coin dispensed to the wholesale customer by the recognised person during a given calendar month. If none reported, provide a 0 value. |
£2 Customer Deposit Volume – Coin | Integer | No | Must be greater than or equal to 0 | The number of £2 Royal Mint coin deposits from the wholesale customer processed by the recognised person during a given calendar month. If none reported, provide a 0 value. |
Commentary | String | No | Max 5,000 Characters | Note any observations about the information provided in the Wholesale Customer Flows record, including methodology used in calculations. |
Firm Financials
Data item name: Firm Financials
Data item format: Table
Summary: Financial reporting on the total cost and revenue associated with the recognised person’s delivery of operational activities.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Quarterly
Reporting period: Previous calendar quarter
Other information: Recognised person should provide unaudited figures at the earliest opportunity and resubmit figures if required where auditing is undertaken. If feasible to do so, recognised person should provide Firm Financials on a calendar year basis.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Reporting Period Start Date | Date | Yes | YYYY-MM-DD | The first day the information relates to. For quarterly data, this is the first day of the quarter (2025-01-01). |
Reporting Period End Date | Date | Yes | YYYY-MM-DD | The last day the information relates to. For quarterly data, this is the last day of the month (2025-03-31). Cannot be earlier than [Reporting Period Start Date]. |
Financial Year Start Date | Date | Yes | YYYY-MM-DD | Provide the date from which the recognised person’s financial year begins. Cannot be later than [Financial Year End Date]. |
Financial Year End Date | Date | Yes | YYYY-MM-DD | Provide the date on which the recognised person’s financial year finishes. Cannot be earlier than [Financial Year Start Date]. |
Reporting Last Updated | Date | Yes | YYYY-MM-DD | Indicate when the forecast and actuals were last updated. |
End-Year Figures? | Boolean | Yes | True; False | Indicate whether this reporting return represents the final figures for the financial year? |
Actuals Audited? | List | Yes | No; Yes - Internal only; Yes - External only; Yes - Internal AND External | Indicate whether the actuals in the financial reporting have been audited. If so, denote who has completed the audit. |
Forecast Total Revenue (ALL GBP CASH) | Integer – GBP | Yes | Must be greater than or equal to 0 | Including all financial proceeds attributable to the operational activities pertaining to any GBP banknotes or coin, state the projected total income for the entire current calendar year. Rounded down to the nearest pound sterling. |
Actual Total Revenue (ALL GBP CASH) | Integer – GBP | Yes | Must be greater than or equal to 0 | Including all financial proceeds attributable to the operational activities pertaining to any GBP banknotes or coin, state the realised total income for the entire current calendar year to date. Rounded down to the nearest pound sterling. |
Total Revenue (ALL GBP CASH) Description | String | Yes | Max 5,000 Characters | Summarise what is included and excluded from the financial proceeds arising from operational activities pertaining to GBP banknotes or coin. |
Forecast Total Revenue (BoE Banknotes) | Integer – GBP | No | Must be greater than or equal to 0 | Including all financial proceeds attributable to the operational activities pertaining to BoE banknotes, state the projected total income for the entire current calendar year. Rounded down to the nearest pound sterling. |
Actual Total Revenue (BoE Banknotes) | Integer – GBP | No | Must be greater than or equal to 0 | Including all financial proceeds attributable to the operational activities pertaining to BoE banknotes, state the realised total income for the entire current calendar year to date. Rounded down to the nearest pound sterling. |
Total Revenue (BoE Banknotes) Description | String | No | Max 5,000 Characters | Summarise what is included and excluded from the financial proceeds arising from operational activities pertaining to BoE banknotes. |
Forecast Total Revenue (Coin) | Integer – GBP | No | Must be greater than or equal to 0 | Including all financial proceeds attributable to the operational activities pertaining to coin, state the projected total income for the entire current calendar year. Rounded down to the nearest pound sterling. |
Actual Total Revenue (Coin) | Integer – GBP | No | Must be greater than or equal to 0 | Including all financial proceeds attributable to the operational activities pertaining to coin, state the realised total income for the entire current calendar year to date. Rounded down to the nearest pound sterling. |
Total Revenue (Coin) Description | String | No | Max 5,000 Characters | Summarise what is included and excluded from the financial proceeds arising from operational activities pertaining to Coin. |
Forecast Total Operating Costs (ALL GBP CASH) | Integer – GBP | Yes | Must be greater than or equal to 0 | Including all fixed and variable costs attributable to the operational activities pertaining to any GBP banknotes or coin, state the projected total expenditure for the entire current calendar year. Rounded up to the nearest pound sterling. |
Actual Total Operating Costs (ALL GBP CASH) | Integer – GBP | Yes | Must be greater than or equal to 0 | Including all fixed and variable costs attributable to the operational activities pertaining to any GBP banknotes or coin, state the realised total expenditure for the entire current calendar year to date. Rounded up to the nearest pound sterling. |
Total Operating Cost (ALL GBP CASH) Description | String | Yes | Max 5,000 Characters | Summarise what is included and excluded from the operating costs for any GBP banknotes or coin, listing all fixed and variable costs. |
Actual Fixed Costs as Percentage of Total Operating Costs (ALL GBP CASH) | Numeric – Percentage | Yes | 2 decimal places Must be greater than or equal to 0 AND less than or equal to 100. | As a proportion of the total operating cost of providing any GBP banknotes or coin, outline the fixed costs incurred. Examples of fixed costs include Building, equipment, and systems upkeep. Value must be greater than or equal to 0 AND less than or equal to 100. For example, 99.95% should be provided as 99.95 |
Actual Variable Costs as a Percentage of Total Operating Costs (ALL GBP CASH) | Numeric – Percentage | Yes | 2 decimal places Must be greater than or equal to 0 AND less than or equal to 100. | As a proportion of the total operating cost of providing any GBP banknotes or coin, outline the variable costs incurred. Examples of variable costs include labour costs. Value must be greater than or equal to 0 AND less than or equal to 100. For example, 99.95% should be provided as 99.95 |
Forecast Total Operating Costs (BoE Banknotes) | Integer – GBP | No | Must be greater than or equal to 0 | Including all fixed and variable costs attributable to the operational activities pertaining to BoE banknotes, state the projected total expenditure for the entire current calendar year. Rounded up to the nearest pound sterling. |
Actual Total Operating Costs (BoE Banknotes) | Integer – GBP | No | Must be greater than or equal to 0 | Including all fixed and variable costs attributable to the operational activities pertaining to BoE banknotes, state the realised total expenditure for the entire current calendar year to date. Rounded up to the nearest pound sterling. |
Total Operating Cost (BoE Banknotes) Description | String | No | Max 5,000 Characters | Summarise what is included and excluded from the operating costs for BoE Banknotes, listing all fixed and variable costs. |
Actual Fixed Costs as Percentage of Total Operating Costs (BoE Banknotes) | Numeric – Percentage | No | 2 decimal places Must be greater than or equal to 0 AND less than or equal to 100. | As a proportion of the total operating cost of providing BoE banknotes, outline the fixed costs incurred. Examples of fixed costs include Building, equipment, and systems upkeep. Value must be greater than or equal to 0 AND less than or equal to 100. For example, 99.95% should be provided as 99.95 |
Actual Variable Costs as a Percentage of Total Operating Costs (BoE Banknotes) | Numeric – Percentage | No | 2 decimal places Must be greater than or equal to 0 AND less than or equal to 100. | As a proportion of the total operating cost of providing BoE banknotes, outline the variable costs incurred. Examples of variable costs include labour costs. Value must be greater than or equal to 0 AND less than or equal to 100. For example, 99.95% should be provided as 99.95 |
Forecast Total Operating Costs (Coin) | Integer – GBP | No | Must be greater than or equal to 0 | Including all fixed and variable costs attributable to the operational activities pertaining to Coin, state the projected total expenditure for the entire current calendar year. Rounded up to the nearest pound sterling. |
Actual Total Operating Costs (Coin) | Integer – GBP | No | Must be greater than or equal to 0 | Including all fixed and variable costs attributable to the operational activities pertaining to Coin, state the realised total expenditure for the entire current calendar year to date. Rounded up to the nearest pound sterling. |
Total Operating Cost (Coin) Description | String | No | Max 5,000 Characters | Summarise what is included and excluded from the operating cost for Coin, listing all fixed and variable costs. |
Actual Fixed Costs as Percentage of Total Operating Costs (Coin) | Numeric – Percentage | No | 2 decimal places Must be greater than or equal to 0 AND less than or equal to 100. | As a proportion of the total operating cost of providing Coin, outline the fixed costs incurred. Examples of fixed costs include Building, equipment, and systems upkeep. Value must be greater than or equal to 0 AND less than or equal to 100. For example, 99.95% should be provided as 99.95 |
Actual Variable Costs as a Percentage of Total Operating Costs (Coin) | Numeric – Percentage | No | 2 decimal places Must be greater than or equal to 0 AND less than or equal to 100. | As a proportion of the total operating cost of providing Coin, outline the variable costs incurred. Examples of variable costs include labour costs. Value must be greater than or equal to 0 AND less than or equal to 100. For example, 99.95% should be provided as 99.95 |
Actual Cash in Transit Cost (ALL GBP CASH) | Integer – GBP | Yes | Must be greater than or equal to 0 | State the realised total expenditure on any GBP banknote and coin Cash in Transit activity for the entire current calendar year to date. Rounded up to the nearest pound sterling. |
Cash in Transit Cost (ALL GBP CASH) Description | String | No | Max 5,000 Characters | Summarise how total CIT costs for banknotes and coin are calculated and apportioned. |
Actual Cash in Transit Cost (BoE Banknotes) | Integer – GBP | No | Must be greater than or equal to 0 | State the realised total expenditure on BoE banknote Cash in Transit activity for the entire current calendar year to date. Rounded up to the nearest pound sterling. |
Cash in Transit Cost (BoE Banknotes) Description | String | No | Max 5,000 Characters | Summarise how CIT costs for BoE banknotes are calculated and apportioned. |
Actual Cash in Transit Cost (Coin) | Integer – GBP | No | Must be greater than or equal to 0 | State the realised total expenditure on Coin Cash in Transit activity for the entire current calendar year to date. Rounded up to the nearest pound sterling. |
Cash in Transit Cost (Coin) Description | String | No | Max 5,000 Characters | Summarise how CIT costs for coin are calculated and apportioned. |
Commentary | String | No | Max 5,000 Characters | Note any observations about the information provided in any Firm Financials field. |
Sustainability Target Details
Data item name: Sustainability Target Details
Data item format: Table
Summary: Lists any targets or objectives adopted by the recognised person for improving the sustainability and environmental impact of their specified relevant functions.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated for each target implemented by the recognised person.
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering.
Other information: For detail on the types of sustainability targets expected to be reported by recognised persons, see Annex 5 – Setting Sustainability Targets.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this sustainability target record was last amended. Recognised person to update each time a record is amended. |
Target ID | Integer | Yes | Must be unique | Unique identifier for the Sustainability Target. Integer assigned by recognised person and used consistently over time. |
Target Name | String | Yes | Max 200 Characters | The full, unabbreviated version of the target name. |
Target Description | String | Yes | Max 5,000 Characters | Description of target or objective. This should include a description of the purpose of the target or objective, and details of what specified wholesale cash distribution activity the target or objective applies to. Include a description of what markers will determine the target or objective being met such as, for example, a list of certain actions having been completed by a certain date, or empirical evidence of the target or objective having been met. |
Target Category | List | Yes | Cash in Transit Activity; Building Efficiency; Energy Management; Water Management; Waste Management; Cash Packaging; Greenhouse Gas Emissions; Nature-based Initiatives; Other | Identifies the sustainability field the target pertains to. See Annex 5 – Setting Sustainability Targets for more details. |
Target Start Date | Date | Yes | YYYY-MM-DD | The date on which the target or objective was set. |
Target Due Date | Date | No | YYYY-MM-DD | The date by which the target is expected to be met. Cannot be earlier than [Target Start Date]. |
Target Achieved Date | Date | Depends on [Target Status] | YYYY-MM-DD | Only mandatory if [Target Status] = ‘Achieved’, otherwise leave blank. The date when the target was met. Cannot be earlier than [Target Start Date]. |
Target Status | List | Yes | Achieved; On-track; Delayed; Cannot Achieve | Signifies the state of progress towards meeting the target. Achieved = Target has been met. On-track = Progress towards meeting target deadline is as expected. Delayed = Initial target due date is likely to be missed but there remains a realistic prospect of the target being met at a future date. Cannot Achieve = Target is no longer feasible with no realistic prospect of being met at a future date. |
Target Reporting Format | List | Yes | Percentage; Number | State how progress against the target will be reported. Percentage = Target is expressed as a fraction of 100 (0-100%). Number = Target is expressed as a quantity or amount. |
Cash Centre ID | Integer | No | Must be a valid [Cash Centre ID] from Cash Centre Details | Optional for sustainability targets applicable to a cash centre. Must be a valid [Cash Centre ID] and must exist in the Cash Centre Details table. |
Arrangement ID | Integer | No | Must be a valid [Arrangement ID] from Material Third Party Arrangements | Optional for sustainability targets applicable to a material third-party arrangement. Must be a valid [Arrangement ID] and must exist in the Material Third-Party Arrangements table. |
Customer ID | Integer | No | Must be a valid [Customer ID] from Wholesale Customer Details | Optional for sustainability targets applicable to a wholesale customer. Must be a valid [Customer ID] and must exist in the Wholesale Customer Details table. |
Sustainability Target Performance
Data item name: Sustainability Target Performance
Data item format: Table
Summary: Logs progress towards targets adopted by the recognised person for improving the sustainability and reducing the environmental impact of their specified relevant functions.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: Unbounded – Attributes repeated for each target in-place at the recognised person.
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Quarterly
Reporting period: Previous calendar quarter
Other information: None
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Reporting Period Start Date | Date | Yes | YYYY-MM-DD | The first day the information relates to. For quarterly data, this is the first day of the quarter (2025-01-01). |
Reporting Period End Date | Date | Yes | YYYY-MM-DD | The last day the information relates to. For quarterly data, this is the last day of the quarter (2025-03-31). Cannot be earlier than [Reporting Period Start Date]. |
Target ID | Integer | Yes | Must be a valid [Target ID] from Sustainability Target Details | Associates the sustainability performance reporting with a given sustainability target. Must be a valid [Target ID] and exist in the Sustainability Target Details table. |
Target Performance in Reporting Period | Numeric | Yes | 2 decimal places | Provide actual performance data for the entirety of the reporting period. For example, 1.35 for a number metric or 99.95 for a percentage metric. |
RAG Rating | List | Yes | Red; Amber; Green | Report progress towards achieving the target. Progress can be rated as either ‘Red’ (Target likely to be delayed or missed), ‘Amber’ (Facing challenges, target at risk) or ‘Green’ (On-track to being achieved). Ensure the corresponding [Target Status] in the Sustainability Target Details table aligns with the [RAG Rating] indicated here. If [RAG Rating] = ‘Green’, [Target Status] should be ‘Achieved’ or ‘On-track’. If [RAG Rating] = ‘Amber’, [Target Status] should be ‘On-track’ or ‘Delayed’. If [RAG Rating] = ‘Red’, [Target Status] should be ‘Delayed’ or ‘Cannot Achieve’. |
Target Commentary | String | Yes | Max 5,000 Characters | Summarise progress to date and next steps for the next quarterly reporting period to achieve target. |
Event Notification
Data item name: Event Notification
Data item format: Table
Summary: Pursuant to the Code of Practice – Information gathering, logs events that the recognised person is required to inform the Bank of.
Applicable to: Operator AND Backing FI
Min occurrence: 0
Max occurrence: Unbounded – Attributes repeated per event notification.
Option to report as group: Yes
Reporting frequency: Event based/Ad-hoc notification.
Reporting period: Not specified. See Code of Practice – Information gathering
Other information: For detail on the types of event notifications expected to be reported by recognised persons, see Code of Practice – Information gathering.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Last Updated Date | Date | Yes | YYYY-MM-DD | The date this event notification record was last amended. Recognised person to update each time a record is amended. |
Event ID | Integer | Yes | Must be unique | Unique identifier for the Event. Integer assigned by recognised person and used consistently over time. |
Event Opened Date | Date | Yes | YYYY-MM-DD | The date the event was first identified by the recognised person. |
Event Closed Date | Date | No | YYYY-MM-DD | The date the event was resolved to the recognised person’s satisfaction. |
Event Name | String | Yes | Max 100 Characters | Summarise the nature of the event. |
Event Details | String | Yes | Max 5,000 Characters | Provide a description of the event. |
Event Attachment References | String | Yes | Max 2,000 Characters | Specify any supplementary documents or files that accompany this event notification. Indicate if no attachments provided. |
Reporter ID | Integer | No | Must be a valid [Reporter ID] from Reporter Details | Complete only if event is related to a recognised person’s reporter, otherwise leave blank. [Reporter ID] must exist in the Reporter Details table. |
Cash Centre ID | Integer | No | Must be a valid [Cash Centre ID] from Cash Centre Details | Complete only if event is related to a recognised person’s cash centre, otherwise leave blank. [Cash Centre ID] must exist in the Cash Centre Details table. |
Equipment Item ID | Integer | No | Must be a valid [Equipment Item ID] from Key Equipment Details | Complete only if event is related to a recognised person’s key equipment, otherwise leave blank. [Equipment Item ID] must exist in the Key Equipment Details table. |
Equipment Set ID | Integer | No | Must be a valid [Equipment Set ID] from Desktop Equipment Details | Complete only if event is related to a recognised person’s desktop equipment, otherwise leave blank. [Equipment Set ID] must exist in the Desktop Equipment Details table. |
SLA ID | Integer | No | Must be a valid [SLA ID] from Service Level Agreement Details | Complete only if event is related to a recognised person’s service level agreement, otherwise leave blank. [SLA ID] must exist in the Service Level Agreement Details table. |
Arrangement ID | Integer | No | Must be a valid [Arrangement ID] from Material Third-Party Arrangements | Complete only if event is related to a recognised person’s material third-party arrangement, otherwise leave blank. [Arrangement ID] must exist in the Material Third-Party Arrangements table. |
Customer ID | Integer | No | Must be a valid [Customer ID] from Wholesale Customer Details | Complete only if event is related to a recognised person’s wholesale customer, otherwise leave blank. [Customer ID] must exist in the Wholesale Customer Details table. |
Target ID | Integer | No | Must be a valid [Target ID] from Sustainability Target Details | Complete only if event is related to a recognised person’s sustainability target, otherwise leave blank. [Target ID] must exist in the Sustainability Target Details table. |
Attestation
Data item name: Attestation
Data item format: Table
Summary: In accordance with the Code of Practice – Information gathering, a declaration by the recognised person that the information it has provided to the Bank is complete, accurate and up to date.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Annually
Reporting period: Not specified. See Code of Practice – Information gathering
Other information: To be completed once the recognised person reviews (and if required updates) all relevant data items. If the recognised person is not required to submit a given data item, complete the relevant attribute as 'True' in the Attestation.
Attribute | Data type | Mandatory? | Attribute restrictions | Data definition and validations (where applicable) |
|---|---|---|---|---|
Attestation Date | Date | Yes | YYYY-MM-DD | The date on which the attestation is made. |
Firm Details Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Firm Details table and that the information provided is complete, accurate and up to date. |
Reporter Details Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Reporter Details table and that the information provided is complete, accurate and up to date. |
Cash Centre Details Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Cash Centre Details table and that the information provided is complete, accurate and up to date. |
Vault Utilisation Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Vault Utilisation table and that the information provided is complete, accurate and up to date. |
Key Equipment Details Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Key Equipment Details table and that the information provided is complete, accurate and up to date. |
Desktop Equipment Details Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Desktop Equipment Details table and that the information provided is complete, accurate and up to date. |
Cash Centre Throughput Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Cash Centre Throughput table and that the information provided is complete, accurate and up to date. |
Service Level Agreement Details Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Service Level Agreement Details table and that the information provided is complete, accurate and up to date. |
Service Level Agreement Performance Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Service Level Agreement Performance table and that the information provided is complete, accurate and up to date. |
Material Third-Party Arrangements Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Material Third-Party Arrangements table and that the information provided is complete, accurate and up to date. |
Wholesale Customer Details Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Wholesale Customer Details table and that the information provided is complete, accurate and up to date. |
Wholesale Customer Flows Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Wholesale Customer Flows table and that the information provided is complete, accurate and up to date. |
Firm Financials Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Firm Financials table and that the information provided is complete, accurate and up to date. |
Sustainability Target Details Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Sustainability Target Details table and that the information provided is complete, accurate and up to date. |
Sustainability Target Performance Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Sustainability Target Performance table and that the information provided is complete, accurate and up to date. |
Event Notification Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Event Notification table and that the information provided is complete, accurate and up to date. |
Business Continuity Plan Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Business Continuity Plan document and that the information provided is complete, accurate and up to date. |
Business Plan Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Business Plan document and that the information provided is complete, accurate and up to date. |
Cash Centre Closure Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has provided the Bank with all notifications and documentation relating to Cash Centre Closures, and the information provided is complete, accurate and up to date. |
Market Exit Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has provided the Bank with all notifications and documentation relating to a Market Exit notice, and the information provided is complete, accurate and up to date. |
Self-Assessment Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Self-Assessment document and that the information provided is complete, accurate and up to date. |
Wholesale Customer Pricing Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Wholesale Customer Pricing document and that the information provided is complete, accurate and up to date. |
Materiality Assessment | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Materiality Assessment document(s) and that the information provided is complete, accurate and up to date. |
Due Diligence Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Due Diligence document(s) and that the information provided is complete, accurate and up to date. |
Risk Assessment Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Risk Assessment document(s) and that the information provided is complete, accurate and up to date. |
Contract Reviewed? | Boolean | Yes | True; False | Confirm that the recognised person has reviewed the Contract document(s) and that the information provided is complete, accurate and up to date. |
Business Continuity Plan
Data item name: Business Continuity Plan
Data item format: Document
Summary: Identifies threats or risks to a recognised person’s performance of its specified relevant functions in relation to its specified activities, and details how such threats and risks may be mitigated.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Annually. Bank to be notified of material changes within one calendar month of making any such change.
Reporting period: Not specified. See Code of Practice – Information gathering.
Other details: None
No standardised reporting template required.
Please see the Code of Practice on Information gathering, and associated guidance.
Business Plan
Data item name: Business Plan
Data item format: Document
Summary: Details how the recognised person will perform their specified relevant functions in relation to their specified activities over the next two years.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Annually. Bank to be notified of material changes within one calendar month of making any such change.
Reporting period: Not specified. See Code of Practice – Information gathering.
Other details: None
No standardised reporting template required.
Please see the Code of Practice on Information gathering, and associated guidance.
Cash Centre Closure
Data item name: Cash Centre Closure
Data item format: Document
Summary: Details how the operator plans to close a cash centre whilst minimising adverse effects on its own wholesale cash activities and the wider UK wholesale cash market.
Applicable to: Operator ONLY
Min occurrence: 1
Max occurrence: 1
Option to report as group: No
Reporting frequency: Event based/Ad-hoc notification. See Code of Practice – Cash centre closure and market exit for minimum required notice period ahead of any actual cash centre closure.
Reporting period: Not specified. See Code of Practice – Cash centre closure and market exit
Other details: None
No standardised reporting template required.
Please see the Code of Practice on Cash centre closure and market exit and associated guidance.
Market Exit
Data item name: Market Exit
Data item format: Document
Summary: Details how the recognised person intends to leave the wholesale cash market in an orderly manner.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: No
Reporting frequency: Event based/Ad-hoc notification. See Code of Practice – Cash centre closure and market exit for minimum required notice period ahead of any actual market exit.
Reporting period: Not specified. See Code of Practice – Cash centre closure and market exit
Other details: None
No standardised reporting template required.
Please see the Code of Practice on Cash centre closure and market exit and associated guidance.
Self-Assessment
Data item name: Self-Assessment
Data item format: Document
Summary: Details how the recognised person has regard to the principles of the Wholesale Cash Market Oversight regime.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Annually. Bank to be notified of material changes within one calendar month of making any such change with new self-assessment.
Reporting period: Not specified. See Code of Practice – Information gathering
Other details: None
No standardised reporting template required.
Please see the Code of Practice on Information gathering and associated guidance.
Wholesale Customer Pricing
Data item name: Wholesale Customer Pricing
Data item format: Document
Summary: Details the standard tariffs payable by recognised person’s wholesale customers for each specified wholesale cash distribution activity.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering
Other details: None
No standardised reporting template required.
Please see the Code of Practice on Information gathering and instructions below.
The Bank considers that the above involves the creation of a standard pricing tariffs document, which details the typical charges levied on wholesale customers for the performance of the recognised person’s specified relevant functions.
The standard pricing tariffs document must:
- detail the wholesale customer fees and charges payable for providing products related to each specified relevant function;
- include any thresholds or specific eligibility requirements that may apply to each wholesale cash product or customer type;
- if multiple charges are charged to a wholesale customer for a given product or service by a recognised person and a third-party provider (such as for example, a cash-in-transit or outsourced operator) please indicate; and
- provide an overview of how product prices and changes are calculated, the frequency and date on which they are typically applied, as well as the notice period given to wholesale customers of product price changes.
Materiality Assessment
Data item name: Materiality Assessment
Data item format: Document
Summary: Details the recognised person’s materiality assessment of a third-party arrangement.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering and Code of Practice – Third-party arrangements.
Other details: Recognised persons must provide a copy of their materiality assessment in respect of a material CIT provider in accordance with this data catalogue, the Code of Practice – Information gathering and the Code of Practice – Third-party arrangements. In addition, recognised persons must provide a copy of their materiality assessment in respect of any third-party provider under a third-party arrangement (including any cash-in-transit provider and regardless of whether such third-party provider is deemed to be a material third-party arrangement or not) where requested in a written notice by the Bank, before the end of such reasonable period as is specified by the Bank in such notice.
No standardised reporting template required.
Please see the Code of Practice on Third-party arrangements and associated guidance.
Due Diligence
Data item name: Due Diligence
Data item format: Document
Summary: Details the recognised person’s due diligence of a third-party provider in respect of a material third-party arrangement.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering and Code of Practice – Third-party arrangements.
Other details: Recognised persons must provide a copy of their due diligence in respect of a material CIT provider in accordance with this data catalogue, the Code of Practice – Information gathering and the Code of Practice – Third-party arrangements. In addition, recognised persons must provide a copy of their due diligence in respect of any other third-party provider under a material third-party arrangement where requested in a written notice by the Bank, before the end of such reasonable period as is specified by the Bank in such notice.
No standardised reporting template required.
Please see the Code of Practice on Third-party arrangements and associated guidance.
Risk Assessment
Data item name: Risk Assessment
Data item format: Document
Summary: Details the recognised person’s risk assessment of a third-party provider in respect of a material third-party arrangement.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering and Code of Practice – Third-party arrangements.
Other details: Recognised persons must provide a copy of their risk assessment in respect of a material CIT provider in accordance with this data catalogue, the Code of Practice – Information gathering and the Code of Practice – Third-party arrangements. In addition, recognised persons must provide a copy of their risk assessment in respect of any other third-party provider under a material third-party arrangement where requested in a written notice by the Bank, before the end of such reasonable period as is specified by the Bank in such notice.
No standardised reporting template required.
Please see the Code of Practice on Third-party arrangements and associated guidance.
Contract
Data item name: Contract
Data item format: Document
Summary: Details the recognised person’s contract with a third-party provider in respect of a material third-party arrangement.
Applicable to: Operator AND Backing FI
Min occurrence: 1
Max occurrence: 1
Option to report as group: Yes, unless otherwise directed by the Bank.
Reporting frequency: Update as required
Reporting period: Not specified. See Code of Practice – Information gathering and Code of Practice – Third-party arrangements.
Other details: Recognised persons must provide a copy of their contract in respect of each material CIT provider in accordance with this data catalogue, the Code of Practice – Information gathering and the Code of Practice – Third-party arrangements. In addition, recognised persons must provide a contract (or where no written contract is in place with the third-party provider, a written description) in respect of any other third-party provider under a material third-party arrangement where requested in a written notice by the Bank, before the end of such reasonable period as is specified by the Bank in such notice.
No standardised reporting template required.
Please see the Code of Practice on Third-party arrangements and associated guidance.
Annexes
To ensure robust and consistent data handling by the recognised person and the Bank, data items submitted to the Bank are required to adhere to a file naming convention.
Table-based data items are submitted together using the reporting form. When submitted to the Bank, the reporting form file name must use the following file naming convention.
File Naming Convention: T_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Version Number]
Example: T_BOE_1_20241231_1
Document-based data items are submitted individually to the Bank in a supported file format. When submitted to the Bank, the document-based data item file name must use the corresponding file naming convention.
Business Continuity Plan
File Naming Convention: D_BCP_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Reporting Period Start Date]_[Reporting Period End Date]_[Version Number]
Example: D_BCP_BOE_1_20250114_20240101_20241231_1
Business Plan
File Naming Convention: D_BP_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Reporting Period Start Date]_[Reporting Period End Date]_[Version Number]
Example: D_BP_BOE_1_20250114_20240101_20241231_1
Cash Centre Closure
File Naming Convention: D_CCC_[Cash Centre Name]_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Version Number]
Example: D_CCC_Leeds_BOE_1_20250131_1
Market Exit
File Naming Convention: D_ME_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Version Number]
Example: D_ME _BOE_1_20251231_1
Self Assessment
File Naming Convention: D_SA_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Reporting Period Start Date]_[Reporting Period End Date]_[Version Number]
Example: D_SA_BOE_1_20250114_20240101_20241231_1
Wholesale Customer Pricing
File Naming Convention: D_WCP_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Reporting Period Start Date]_[Reporting Period End Date]_[Version Number]
Example: D_WCP_BOE_1_20250114_20240101_20241231_1
Materiality Assessment
File Naming Convention: D_MA_[Name of Third-Party]_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Version Number]
Example: D_MA_Microsoft_BOE_1_20250114_1
Due Diligence
File Naming Convention: D_DD_[Name of Third-Party]_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Version Number]
Example: D_DD_Microsoft_BOE_1_20250114_1
Risk Assessment
File Naming Convention: D_RA_[Name of Third-Party]_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Version Number]
Example: D_RA_Microsoft_BOE_1_20250114_1
Contract
File Naming Convention: D_C_[Name of Third-Party]_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Version Number]
Example: D_C_Microsoft_BOE_1_20250114_1
All other documents
File Naming Convention: D_Misc_[Informative name of document without spaces]_[Firm Abbreviation]_[Firm ID]_[Submission Date]_[Version Number]
Example: D_Misc_EventReport_BOE_1_20250114_1
Notes:
[Version Number] should begin at 1 for the initial version and increment by 1 each time amendments are required.
[Submission Date], [Reporting Period Start Date] and [Reporting Period End Date] should use the YYYYMMDD format.
Unique identifiers (IDs) are a distinguishing signature for individual records for a given data item. When recognised persons are required to create and assign their own unique identifiers (IDs) to records, they should conform to the following criteria.
- Be an integer (whole number).
- Begin from 1 and ascend in sequential order for each record in each data item.
- Used consistently over time (e.g. The ID of a particular cash centre does not change between data submissions).
An example of a valid ID is 1. An example of a valid set of 5 unique IDs is 1; 2; 3; 4; 5.
Unique identifiers (IDs) assigned by the recognised person in this data catalogue are: [Reporter ID], [Cash Centre ID], [Equipment Item ID], [Equipment Set ID], [SLA ID], [Arrangement ID], [Customer ID], [Target ID].
- Where possible, SLAs should be separated for Coin and Banknotes.
- For continuity, SLAs reported in voluntary commitments should continue to be provided.
- If SLAs are shared with senior management/internal governance boards, it is advisable that the recognised person provide these same SLAs to the Bank.
An SLA should consist of the following elements:
- State the objectives to be achieved, including service deliverables.
- Establish clearly defined performance standards.
- Provide an ongoing reporting mechanism for measuring expected performance standards.
- Detail a remediation process to identify and address issues when performance standards are not achieved.
- Be subject to regular review by the recognised person.
Using SLA Limits
Red Amber Green (RAG) Example 1: Machine Uptime
[SLA Figure] of 94.99% and below
‘Red’ (Major Breach)
[SLA Figure] between 95.00% and 97.50%
‘Amber’ (Minor breach)
[SLA Figure] of 97.51% and above
‘Green’ (On-track)
Footnotes
- [SLA Unit] = Percentage, [SLA Assessment Type] = RAG; [SLA Rating Approach] = High Value Favourable;
- [SLA Amber Lower Limit] = 95.00% and [SLA Amber Upper Limit] = 97.50%
RAG Example 2: Invoicing errors per 1,000 pieces
[SLA Figure] of 2.99 or below
‘Green’ (On-track)
[SLA Figure] between 3.00 and 5.00
‘Amber’ (Minor breach)
[SLA Figure] of 5.01 and above
‘Red’ (Major Breach)
Footnotes
- [SLA Unit] = Number, [SLA Assessment Type] = RAG; [SLA Rating Approach] = Low Value Favourable;
- [SLA Amber Lower Limit] = 3.00 and [SLA Amber Upper Limit] = 5.00
Pass/Fail Example 1: Machine Uptime
[SLA Figure] of 94.99% and below
‘Fail’ (Breach)
[SLA Figure] of 95.00% and above
‘Pass’ (On-track)
Footnotes
- [SLA Unit] = Percentage, [SLA Assessment Type] = RAG; [SLA Rating Approach] = High Value Favourable;
- [SLA Amber Lower Limit] = 95.00% and [SLA Amber Upper Limit] = 95.00%
Pass/Fail Example 2: Invoicing errors per 1,000 pieces
[SLA Figure] of 2.99 or below
‘Pass’ (On-track)
[SLA Figure] of 3.00 and above
‘Fail’ (Breach)
Footnotes
- [SLA Unit] = Number, [SLA Assessment Type] = Pass/Fail; [SLA Rating Approach] = Low Value Favourable;
- [SLA Amber Lower Limit] = 3.00 and [SLA Amber Upper Limit] = 3.00
Firms should provide at least 1 SLA for each of the following categories.
- Cash in Transit activity– Collection and deliveries to/from branches/customers being on-time.
- ATM replenishment (if applicable) – Success/fulfilment within a certain time limit; ATM availability/downtime.
- Cash processing – Processing of branch/customer deposits within a certain time.
- Wholesale Customer satisfaction – Complaints/queries (Number, type, time to respond/address, number upheld).
- Invoicing – Accuracy; reconciliation errors.
FI and ATM activities are to be reported separately wherever possible. If separate reporting is not able to be provided, include details of which records/figures are aggregated (including which sectors are being aggregated) in the corresponding [Customer Description] attribute.
Sector
Description
Own ATM
Any ATM or Cash Deposit Machine (CDM) business derived from the relevant reporting operator or backing FI.
Other FI ATM
Any ATM or Cash Deposit Machine (CDM) business derived from a financial institution that is NOT the relevant reporting operator or backing FI.
Independent ATM Deployer
Any ATM or Cash Deposit Machines (CDM) business NOT derived from any financial institution, the relevant reporting operator or backing FI.
Own FI
Non-ATM related FI activity derived from the relevant reporting backing FI. Examples include the backing FI’s (or its respective group) own branch counters and deposit facilities.
Other FI
Non-ATM related FI activity that is NOT derived from the relevant reporting backing FI. Examples include branch networks of Banks and Building Societies that are NOT controlled by the backing FI (or its respective group).
FOREX
Any cash business used for the purpose of foreign currency exchange.
Retailers
Any corporate businesses handling cash.
Other
Miscellaneous undertakings (Local Authority, Schools, Third Sector etc.) AND activities NOT otherwise classifiable under the categories listed. Use the [Customer Description] attribute in the Wholesale Customer Details table to elaborate.
Sustainability of the wholesale cash distribution market refers to the ability of the infrastructure to continue to support access to cash for wholesale and retail customers throughout the UK. Many of the data items required from recognised persons support the Bank's assessment of the overall sustainability of the market, including identifying risks. This section is intended to capture any other indicators/measures of sustainability not captured elsewhere.
Recognised persons are encouraged to provide at least 1 target for each of the categories outlined. If the recognised person is a signatory to the Cash Industry Environmental Charter and/or the industry commitments published in the December 2021 public update, the firm should provide progress against these targets.
Sustainability target category
Examples of target
Cash in Transit Activity
- Vehicle fuel efficiency
- Vehicle emissions
- Vehicle routing/telemetry
- Fuel use
- Electrification
Building Efficiency
- Insulation
- Lighting
- Equipment
- Heating/cooling
- Ventilation
Energy Management
- Gas usage
- Electricity usage
- Auxiliary/back-up power storage or generation
Water Management
- Water usage
- Chemical use
Waste Management
- Waste reduction
- Recycling
- Segregating waste streams
- Reduce landfill waste stream
Cash Packaging
- Packaging reduction
- Single use plastic
- Recyclable packaging
- Reusable packaging
- Biodegradable packaging
Greenhouse Gas Emissions
- Greenhouse Gas reduction target. Should be specific to the Wholesale Cash part of the recognised person’s business and include Scope 1, 2 and 3 emissions.
- Carbon intensity per £m handled.
- Carbon offsets
Nature-based Initiatives
- Biodiversity
- Rewilding
Other
- S&NI note initiatives
- Any other sustainability target that does not fall under one of the listed categories.
Acronyms & Glossary
Further details on terminology can be found in the codes of practice, its annexes, and guidance.
Terminology | Meaning |
|---|---|
Arrangement | See Code of Practice – Definitions. |
Associate | See Code of Practice – Definitions. |
ATM | Automated Teller Machine. Equipment providing cash withdrawal services. Also known as a cash machine or cash point. See also CDM. |
Attribute | A field of data to be reported. All attributes are assigned a Data Type, whether it is Mandatory or not and any other Attribute Restrictions or Data Validations that apply. Also known as Data Attribute, Data Element or Data Field. See also Data Item, Data Type, Mandatory, Attribute Restriction, and Data Validation. |
Attribute Restrictions | Requirements to assist a Recognised Person in supplying accurate and high-quality information to the Bank of England. See also Data Validation. |
Backing FI | Backing Financial Institution. See Code of Practice – Definitions. Also known as FI Guarantor or Settlement Agent. |
Bank | See Code of Practice – Definitions. See also BoE. |
Banknote | See Code of Practice – Definitions. See also Note. |
BAU | Business as Usual. In the context of Wholesale Cash, refers to typical or standard operating conditions and circumstances. |
BEEDS | Bank of England Electronic Data Submission. An online application that manages formal regulatory data submissions between recognised persons and the Bank of England. Accessed via an online portal, recognised persons can complete and submit all data submissions, as well as view and update information held about them by the Bank of England. See BEEDS | Bank of England. |
Blockstacking | The practice of stacking cash cages on top of one another to increase storage capacity of a given physical footprint. |
BoE | Bank of England. When used in the context of Notes, refers to banknotes issued by the Bank of England. |
Bond | Notes physically held in an NCS member’s vault but owned by the Bank of England in order to provide off-balance-sheet treatment of their value for the member. |
Boolean | A Data Type where input is restricted to True or False. |
Bulk Coin Sorter | A machine that processes Coin by separating out different denominations of coin and/or performs coin validation/authentication. |
Bulk Coin Bagger | A machine that bags up loose/shot Coin for customer use. |
Business Continuity Plan | See Code of Practice – Definitions, Code of Practice – Information gathering, and associated guidance. |
Business Day | See Code of Practice – Definitions. |
Business Plan | See Code of Practice – Definitions, Code of Practice – Information gathering, and associated guidance. |
Cage | A storage container for wholesale quantities of Banknotes or Coin. Cage dimensions are largely standardised for Banknotes and Coin. |
Calendar Month | A reporting period that begins on the first day of the month and ends on the last day of the same month. |
Calendar Quarter | A reporting period that ends on either: 31 March, 30 June, 30 September and 31 December. A reporting period of three months within the same year that starts on 1 January and ends on 31 March, or starts on 1 April and ends on 30 June, or starts on 1 July and ends on 30 September, or starts on 1 October and ends on 31 December. |
Calendar Year | The reporting period that begins on 1 January of a given year and ends on 31 December of the same year. |
Cash Centre | See Code of Practice – Definitions. |
Cash Centre Closure | See Code of Practice – Definitions, Code of Practice – Cash centre closure and market exit, and associated guidance. |
Cash Packaging Applicator | Equipment that can apply protective packaging and/or banding to Notes or Coin (excludes coin bagging – see Bulk Coin Bagger). |
Cash Packaging Remover | Equipment that can remove protective packaging and/or banding from Notes or Coin. |
Cash Processing | Any combination of counting, reconciliation, authentication, fitness checking, categorisation, sorting, or packaging of Notes or Coin. Typically carried out using Equipment but can involve manual human-based activities. Also known as Cash Sorting and Processing. |
Cash Services User | See Code of Practice – Definitions. |
CDM | Cash Deposit Machine. Equipment providing cash deposit services. See also ATM. |
Code of Practice | See Code of Practice – Definitions. |
Coin | Coins made by The Royal Mint on behalf HM Treasury, within the meaning of section 11 of the Coinage Act 1971. |
CIT | Cash in Transit. Also known as Cash in Transit Activity. See Code of Practice – Definitions and guidance. |
Cash-in-Transit Activity | See Code of Practice – Definitions. |
Cash-in-Transit Arrangement | See Code of Practice – Definitions. |
Cash-in-Transit Provider | See Code of Practice – Definitions. |
Cash Services User | See Code of Practice – Definitions. |
Data Catalogue | This document. See Code of Practice – Definitions. Also known as Wholesale Cash Distribution Market Oversight (WCDMO) Data Catalogue. |
Data Item | One or more related Data Attributes. See also Attribute and Data Item Format. |
Data Item Format | Denotes how a Data Item is presented. The WCDMO Data Catalogue utilises 2 different formats for submitting information electronically: Table and Document. See also Table and Document. |
Data Type | The format in which an attribute is expressed. See also Boolean; Date; Integer; List; Numeric; String. |
Data Validation | Data quality processes to ensure that data is clean and inputted correctly. See also Attribute Restrictions. |
Date | A Data Type where input is restricted to calendar day, month and year. All dates are expressed in YYYY-MM-DD format. For example, 2023-12-31 |
Date of Specification | See Code of Practice – Definitions. |
Deposit | Notes or Coin exiting public circulation to be paid into a Recognised Person. See also Total Cash In. |
Desktop Sorter | A small, desk-based, low-capacity machine capable of Note processing to Bank of England standards. The typical theoretical throughput of desktop sorter equipment is around 10+ notes per second. |
Director | See Code of Practice – Definitions. |
Dispense | Notes or Coin entering public circulation from a Recognised Person. See also Total Cash Out. |
Document | A Data Item Format where a Recognised Person provides a report or file which meets the content requirements outlined in the Codes of Practice and associated guidance. Documents can be provided in one of the following supported file formats: XBRL, CSV, DOC, DOCX, PDF, PPT, PPTX, XLS, XLSX, XML, ZIP. See also Data Item Format and Table. |
Employee | See Code of Practice – Definitions. |
Equipment | When used in the context of Wholesale Cash, automated machines that undertake Cash Processing. Also known as machinery. |
Event Notification | See Code of Practice – Definitions and Code of Practice – Information gathering. |
Exit | See Code of Practice – Definitions, Code of Practice – Cash centre closure and market exit, and associated guidance. Also known as Market Exit. |
Fit Notes | Bank of England Notes that are of sufficient quality to re-enter public circulation, as defined by the Bank of England’s Fitness Sorting standards. |
Fitness Sorting | The process of identifying and separating damaged Notes and Coin from Notes and Coin that is of sufficient quality to re-enter circulation. Also known as fitness checking, quality sorting or quality checking. |
Garbled Coin | Coin that is too damaged to re-enter public circulation. Also known as Damaged Coin. |
GBP | British pound sterling. The official currency of the United Kingdom and, for the sake of reporting here, includes coin, and banknotes issued by authorised banks in Scotland and Northern Ireland and by or on behalf of Crown dependencies of the United Kingdom. This definition reflects the practical considerations of recognised persons separating out different issuers in their reporting. |
Governing Body | See Code of Practice – Definitions. |
Group | See Code of Practice – Definitions. |
Guidance | A non-exhaustive document which details the steps that a recognised person may take in order to comply with the Codes of Practice. |
HSF | High Security Feature. A machine-readable, covert security feature built into the £1 Coin introduced in 2017 to protect against counterfeiting. |
HSNS | High Speed Note Sorter. A large, high-capacity machine capable of Note processing to Bank of England standards. The typical theoretical throughput of HSNS equipment is around 40+ notes per second. |
Integer | A Data Type where input is restricted to whole numbers. For example, 100. |
Issue | See Code of Practice – Definitions. |
List | A Data Type where input is restricted to a finite and pre-defined number of possible values. For example, Option A; Option B; Option C. |
Mandatory | Denotes whether an Attribute must be completed in order for a data submission to be accepted. |
Material CIT provider | A Third-Party Provider under a Material Third-Party Arrangement that is a Cash-in-Transit Arrangement. |
Material Third-Party Arrangement | See Code of Practice – Definitions, Code of Practice – Third-party arrangements, and associated guidance. |
Materiality Assessment | See Code of Practice – Third-party arrangements, and associated guidance. |
Max Occurrence | The maximum number of times each Data Item needs to be completed per submission. |
Min Occurrence | The minimum number of times each Data Item needs to be completed per submission. |
MSNS | Medium Speed Note Sorter. A mid-capacity machine capable of Note processing to Bank of England standards. The typical theoretical throughput of MSNS equipment is around 15+ notes per second. |
MTF | Machine Testing Framework. The framework implemented by the Bank of England to verify that machines in use only give value for genuine Bank of England Notes. |
NCS | Note Circulation Scheme. See Code of Practice – Definitions. |
NCS Member | A participant in the Note Circulation Scheme. As of October 2024, the 4 NCS members are: G4S Cash Centres (UK) Limited, Post Office Ltd, National Westminster Bank plc and Vaultex UK Limited. See also Operator. |
Notes | Banknotes issued either by the Bank of England or Scotland & Northern Ireland commercial banknote issuers. Also known as Banknotes. Includes banknotes regardless of their classification, categorisation, or eligibility under the NCS. |
Numeric | A Data Type where input is restricted to numbers that contain decimal points or for fractions. The number of decimal points and rounding behaviour is stated for all attributes where this data type applies. Also referred to as Float or Real. An example is 0.75. |
Operator | See Code of Practice – Definitions. |
Operational Activity | See Code of Practice – Definitions. |
Person | See Code of Practice – Definitions. |
Principles | See Code of Practice – Definitions. |
Recognised Person | See Code of Practice – Definitions. |
Record | A collection of Attributes pertaining to (but not limited to) the Recognised Person, its personnel, customers, contracts, property, performance or operations. Typically represented as a row of information within the Reporting Form. |
Reporting Form | The template used to collate information on table-based Data Items for submission to the Bank of England. To be completed in accordance with the requirements detailed in the WCDMO Data Catalogue, Codes of Practice and associated guidance. Also known as Reporting Template. |
Reporting Frequency | The regularity with which a firm is expected to submit a given Data Item. See also Reporting Period. |
Reporting Period | The duration over which a firm is expected to provide information on a given Data Item. See also Calendar Month, Calendar Quarter, Calendar Year, and Reporting Frequency. |
S&NI | Scotland and Northern Ireland. When used in the context of Notes, refers to banknotes issued by the commercial issuers in Scotland and Northern Ireland as permitted by Part 6 of the Banking Act 2009. |
Self-Assessment | See Code of Practice – Definitions. |
SLA | Service Level Agreement. Means the steps taken by a Recognised Person in accordance with paragraph 6 of the Code of Practice – Information gathering. See also Annex 3 – Providing Service Level Agreement Data. |
Specified Activity | See Code of Practice – Definitions. |
Specified Relevant Function | See Code of Practice – Definitions. |
String | A Data Type that unless specified otherwise, permits any combination of characters that appear on a keyboard, such as letters, numbers and symbols. |
Sustainability Target | See Code of Practice – Information gathering, associated guidance and Annex 5 - Setting Sustainability Targets. |
Table | A Data Item Format where a Recognised Person submits information in rows and columns as specified in the Reporting Form and WCDMO Data Catalogue. |
Total Cash In | Notes or Coin entering a cash centre. See also Deposit. |
Total Cash Out | Notes or Coin leaving a cash centre. See also Dispense. |
Third-Party Arrangement | See Code of Practice – Definitions. See also Material Third-Party Arrangement and Third-Party Provider. |
Third-Party Provider | See Code of Practice – Definitions, Code of Practice – Third-party arrangements, and associated guidance. See also Material Third-Party Arrangement and Third-Party Arrangement. |
Undertaking | See Code of Practice – Definitions. |
Unfit Notes | Bank of England Notes that are of insufficient quality to re-enter public circulation, as defined by the Bank of England’s Fitness Sorting standards. |
Unique ID | Unique Identifier. An Integer which represents a single entity within a collection of entities reported by a Recognised Person. Entities with Unique IDs include Returns, Firms, Reporters, Cash Centres, Equipment, Service Level Agreements, Wholesale Customers, Material Third-Party Arrangements, Sustainability Targets and Event Notifications. See also Annex 2 – Recognised Person Assigned Identifiers. |
Vault | One or more areas within a Cash Centre that are specifically designated as an area to store Notes and Coin under secure conditions. Also known as Vault Facility and Strong Room. |
WCDMO Data Catalogue | Wholesale Cash Distribution Market Oversight Data Catalogue. This document. See Code of Practice – Definitions. Also known as Data Catalogue. |
Wholesale Collection or Delivery of Cash Service | See Code of Practice – Definitions. |
Wholesale Customer | See Code of Practice – Definitions, and Annex 4 – Classifying Wholesale Customers. |
XML | eXtensible Markup Language. A software- and hardware-independent tool for storing and transporting data. In the WCDMO Data Catalogue, XML is the required file format for submitting Table-based data items. See also XSD. |
XSD | XML Schema Definition. Defines the building blocks of a valid XML file. For Wholesale Cash Distribution Market Oversight, a single XSD file exists. The XSD is included within the Reporting Form and provided as a separate standalone file to enable Recognised Persons to create a custom reporting arrangement whilst complying with the Data Catalogue requirements. Also known as an XML Schema. See also XML. |
WCDMO Data Catalogue Ends