National Fraud Initiative: public-sector data specifications

Please note that data should:

• be extracted according to the the National Fraud Initiative (NFI) timetables
• only be submitted through the the secure secure NFI web web application
• be password-protectedpassword protected once extracted from the relevant systems
• unless otherwise stated, do not include minors’minor’s data.

Before submitting data, you must read the guidance provided on uploadinghow to upload data and the pre-upload checks you should carry out to ensure you are providing the best possible data.

The upload process automatically maps the fields in the file you are uploading by field name recognition. However, if there is no header row containing field names within the extracted data, the person uploading data will be required to manually map each field to the appropriate field on the data file upload screen. Therefore, it’s advisable to include field names in the header row within the data extract, if possible.

To find out who should supply data, refer to the data requirements guide.

Data specifications detailing the exact data we process for National Fraud Initiative pilots can be found at National Fraud Initiative: Pilot Data SpecificationRead more about uploading data to the NFI.

Changes for the 2024 to 2025 exercise

The NFI reviews data specifications before each exercise. Although changes have been kept to a minimum, some are necessary to improve the matching process and the quality of matches.

Changes for the 2024 to 2025 exercise

PDF, 41.5 KB, 1 page

Trade creditors’creditors data specifications

Trade creditors’creditors standing data should:

• be a snapshot of trade creditors current at the date of extraction
• exclude dormant or suspended creditors
• cover the period given in the data specification

Trade creditors standing data: data specification 2024 to 2025

PDF, 60 KB, 3 pages

Trade creditors payment history data: data specification 2024 to 2025

PDF, 59.7 KB, 2 pages

Personal budgets and social care payments data specification

Data should:

• relate to personal budget payments paid as direct payments (for the mandatory exercise) or social care payments (if matching this data voluntarily) to those applicants over 18 years of age only
• include only current recipients
• have one single record for each recipient

Personal budgets data specification 2024 to 2025

PDF, 52.1 KB, 2 pages

Pensions data specification

Data should be uploaded in 3 separate files:

• current pensioners (those currently receiving a pension)
• pensioners currently receiving a pension gratuity (if applicable)
• deferred pensioners not currently in payment (optional)

Please note any pensions currently in payment should be included in the ‘current pensioners’ file.

Pensions: data specification 2024 to 2025

PDF, 63.1 KB, 5 pages

Payroll data specification

Payroll data should be provided followingin accordance with this data specification.

Payroll: data specification 2024 to 2025

PDF, 66.1 KB, 3 pages

Licences data specification

This specification includes licences for taxi drivers.

Taxi driver licences: data specification 2024 to 2025

PDF, 54.5 KB, 2 pages

Housing data specifications

Housing waiting list

The following housing waiting list data is required.

Housing waiting list: data specification 2024 to 2025

PDF, 47.9 KB, 1 page

Housing tenants

The housing data that should be uploaded includes:

• current named tenants, including those where a right to buy purchase is in progress
• former tenants who completed a right-to-buyright to buy application during the period stated in the data specification

Housing tenants: data specification 2024 to 2025

PDF, 67.1 KB, 3 pages

Electoral Register data specification

Electoral Register data should be submitted annuallyannually. forView the NFIcouncil mandatorytax single-personsingle person discount (SPD)timetable. fraudPlease matching.note Referthat you are required to password protect each dataset once extracted from the councilrelevant taxsystems.

To singlefind personout discountwho timetableshould supply data, refer to the data requirements. guide.

The data should:data:

• should be the ‘full version’ of the Electoral Register (not the commercially available ‘edited version’)
• should relate to the appropriate registration exercise
• should include the Unique Property Reference Number (UPRN) field in your submission if it is fully or partiallypart populated
• should be extracted and submitted after the Register is formally published

The upload process involves automatic mapping of fields to the specification by field name recognition. However, if there are no field names within the extracted data, it will require the person uploading to manually map each field to the appropriate field within the specification on the data file upload system. Therefore, it’s better to include field names within the data extract if possible.

Electoral Registration: data specification 2024 to 2025

PDF, 51.8 KB, 2 pages

Council Tax data specification

Council Tax (CT) data should be submitted annuallyannually. forThis themeans NFIthat mandatorywhen single-personyou discounthave (SPDsubmitted CT) fraudand matching.Electoral OnceRegister both(ER) CTdatasets andfor ERsingle dataperson arediscount uploaded,(SPD) fraud matching, the NFI can generaterelease your SPD matches (unless you encounter data issues that we need to resolve). You will not need to wait for all councils to submit their data.

View the NFI council tax single person discount timetable. Please note that you are required to password-protect each dataset once extracted from the relevant systems.

To find out who should supply council tax data, view the data requirements.

The

Extracting data

Whilst should:the process is up to individual bodies, we encourage the principle of sharing extraction routines to make the process more efficient and economical. For example, we are aware that standard extract routines are being offered by all the major Council Tax (CT) system suppliers. If you would like more information about this, contact your system supplier.

• include

  Data afields

  The dateupload process involves automatic mapping of birthfields to the specification using field name recognition. However, if there are no field names within the extracted data, it iswill capturedrequire the person uploading to manually map each field to the appropriate field within the specification on yourthe system,data butfile weupload acceptsystem. thatTherefore, thisit iswould notbe routinelypreferable stored. 

• to include surnamefield andnames forenamewithin fieldsthe evendata file if theypossible.

  If the surname and forename fields are not fully populated, or are unpopulated, these fields will still need to be provided as they musthave to be mapped for the upload to be accepted. If your CT systemsystems where this is the case will normally also includesinclude an aggregated field that holds all name details,details. Where this datahappens, the aggregated field should also be provided so it can be mapped to the ‘Full name’ field.

field within the specification.

A date of birth field is included, but it is accepted that this is not routinely stored as it is not mandatory for charging of CT. However, if it is captured, even as an optional field, it should be included in the extraction.

The data should:

• include the Unique Property Reference Number (UPRN) field in your submission if it is populated or partiallypart populated
• only be current/live accounts
• relate to all CT accounts, whether or not there is a discount or exemption (i.e.,(i.e. it should cover every domestic property where CT applies)
Council Tax: Data Specification 2025 to 2026

PDF, 238 KB, 5 pages

Transport passes and permits data specification

The Blue Badge Digital Service (BBDS) will upload data on behalf of the local authorities that have opted for this service. Please check whether you have opted in with your Blue Badge teams. If you do not use the BBDS service,service then you will need to extract and upload the data locally.

Please upload data in 3 separate files:

• current holders of a resident’s parking permit
• current holders of a blue badge (including local schemes)
• current holders of a concessionary travel pass (e.g.,(eg a Freedom pass)
Transport passes and permits: data specification 2024 to 2025

PDF, 61.8 KB, 4 pages

Private supported care home residents’residents data specification

All data should relate to current care home residents,residents at the date of extract,extract who are receiving allall, or partpart, of their funding from the Local Authority.

Private supported care home residents: data specification 2024 to 2025

PDF, 91.3 KB, 2 pages

Council Tax Reduction Scheme data specification

Data should be provided in accordance with the Council Tax Reduction scheme data specification.

Council Tax Reduction Scheme: data specification 2024 to 2025

PDF, 52.5 KB, 2 pages

Company check data specification

This data specification is specifically intended for use of the Bank Account Verification and Active Company Check product.

Company check data specification
PDF, 69.6 KB, 2 pages
This file may not be suitable for users of assistive technology.
Request an accessible format.
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email accessible.formats@cabinetoffice.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.