This guide sets out the dataset specifications for the NFI 2016/17 national exercise and NFI council tax single person discount 2016/17 exercise.
Please note that data:
- should be extracted according to the National Fraud Initiative timetables
- should only be submitted through the secure NFI web application
Read more about uploading data to the NFI.
Changes for the 2016/17 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.
PDF, 104KB, 1 page
Payroll data specification
Payroll data should be provided in accordance with this data specification.
PDF, 169KB, 3 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.
PDF, 141KB, 3 pages
Trade creditors data specifications
Trade 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
PDF, 124KB, 2 pages
PDF, 128KB, 2 pages
Housing data specifications
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 buy application during the period stated in the data specification
PDF, 141KB, 3 pages
Housing waiting list
The following housing waiting list is required.
PDF, 196KB, 1 page
Insurance claimants data specifications
Claims data should only relate to personal injury claims (i.e. trips and slips).
You should only provide claim details for the period stated in the data specification. The NFI will approach providers of insurance services to supply insurance data in bulk on behalf of local authorities.
PDF, 129KB, 2 pages
Private supported care home patients data specifications
All data should relate to current care home residents at the date of extract.
PDF, 120KB, 2 pages
Transport passes and permits data specifications
Please note, NFI are liaising with the Blue Badge Improvement Service (BBIS) in order to secure a bulk upload of blue badge data on behalf of all local authorities. We will confirm whether BBIS will upload the data or whether local authorities will be required to do so.
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 (eg a Freedom pass)
PDF, 138KB, 3 pages
Licences data specifications
This specification includes licences for market traders, taxi drivers and personal licences for the supply of alcohol. Please upload data in 3 separate files: • current holders of a market trader or similar licence • current holders of a taxi driver licence (private hire and Hackney carriages) • current holders of a ‘personal alcohol licence’ (PAL) where the licence holder is also a ‘Designated Premises Supervisor’ (DPS).
PDF, 136KB, 3 pages
Personal budgets data specifications
- relate to Personal Budget payments paid as direct payments to those applicants over 18 years of age only
- include only current recipients
- have one single record for each recipient
PDF, 282KB, 2 pages
Council Tax Reduction scheme data specification
Data should be provided in accordance with the Council Tax Reduction scheme data specification.
PDF, 67.4KB, 2 pages
Council Tax data specifications
The NFI now requires Council Tax (CT) data to be submitted annually. This means that when you have submitted CT and Electoral Register (ER) datasets for single person discount (SPD) fraud matching, the NFI can release your matches (unless you encounter data issues that we need to resolve). You will not need to wait for all councils to submit their data.
To find out who should supply council tax data, view the data requirements.
Whilst 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.
The upload process involves automatic mapping of fields to the specification using 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 would be preferable to include field names within the data file if possible.
If the surname and forename fields are not fully populated, or are unpopulated, these fields will still need to be provided as they have to be mapped for the upload to be accepted. CT systems where this is the case will normally also include an aggregated field that holds all name details. Where this happens, the aggregated field should also be provided so it can be mapped to the ‘Full name’ 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 part populated
- only be current/live accounts
- relate to all CT accounts, whether or not there is a discount or exemption (i.e. it should cover every domestic property where CT applies)
PDF, 230KB, 4 pages
Electoral Register data specifications
The NFI now requires Electoral Register data to be submitted annually. View the NFI council tax single person discount 2017/18 timetable. Please note that you are required to password protect each dataset once extracted from the relevant systems.
To find out who should supply data, refer to the data requirements guide.
- 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 part 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.
PDF, 122KB, 1 page
Published: 20 March 2015
Updated: 16 June 2016
- Updated data specification sets for 2016/17.
- Updated for 2016/2017 NFI exercise
- Council tax and electoral register data specifications updated.
- Updated references to council tax timetable and the single person discount
- Updated council tax and electoral register data specifications.
- First published.
From: Cabinet Office
Part of: National Fraud Initiative
Related guides: National Fraud Initiative: public sector data requirements