Information about how to upload data to the National Fraud Initiative (NFI) and how to format the data correctly to avoid issues.
View taking part in National Fraud Initiative for information about bodies’ obligations under the data protection legislation.
How to upload data
To upload the data, log in to the secure NFI web application and select the Data File Upload option from the homepage. The secure application features 256 bit Secure Sockets Layer encryption and enables data files to be password protected. This is the only acceptable way to supply data. If any other method of submission is used, the NFI will inform the organisation’s senior responsible officer for the NFI (director of finance or equivalent) that data has been put at unnecessary risk.
If you require any further guidance on extracting, downloading or submitting data contact the NFI Data Centre (Synectics Solutions Ltd) via email (email@example.com) or call 0845 345 8019.
The following checks will minimise the risk of the data having to be re-submitted. This can cause a delay of more than a week and results in unnecessary increases in download costs for bodies taking part. The NFI key contact should ensure that:
- the nominated user extracts and submits the data by the required deadlines
- the data is readable and complete: some data fields may not be available from a single system but contained in a second or third system – if so these should be brought across to complete the data submission
- the record layout is consistent with the data specification (see public and private sector specifications)
- a ‘look up’ table is provided that describes the codes used in fields, whether system or manually generated (eg type of creditor)
- copies of any intermediate files are retained so that the data may be re-supplied if it proves unreadable
- data is only submitted using the Data File Upload (DFU) tool within the NFI secure web application
Formatting your data
Data should be formatted as ASCII, ie text. You can use fixed length or character delimited records (eg CSV files), where each field is separated by a specific character. If you’re supplying a delimited file, the delimiter should not be in the data unless fields are encapsulated with text qualifiers (usually quotation marks). Likewise the text qualifier should not be in the data. A good choice for a delimiter, instead of the conventional comma, is a pipe (also known as a vertical bar) or a tilde.
There are a number of risks associated with exporting data into Excel from the host system. Although NFI accepts Excel files, we recommend that you carry out basic pre-submission data quality checks to make sure that the following formatting issues don’t affect the quality of the data.
Common issues using Excel include:
- numeric strings of 16 digits or more are treated as numbers by default, and only the first 15 significant figures are stored
- leading zeros are removed from numeric strings (eg when typing “01062007” into a cell): this is a very common problem which can affect dates, invoice numbers, bank details etc
- Excel automatically transforms some numbers into dates: this causes problems with bank sort codes using hyphens (eg “21-11-97”) and house numbers if they are supplied in a different column to the street name (eg “05-07”)
- most versions of Excel have a maximum number of rows it can store in a spreadsheet: if the number of rows is exceeded, the data will be cut off when the file is saved, resulting in a loss of records
|Excel version||Maximum number of rows|
|Excel 7.0 or earlier||16,384|
|Excel 97 (version 8.0)||65,536|
|Excel 2000 (version 9.0)||65,536|
|Excel 2002 (version 10)||65,536|
|Excel 2003 (version 11)||65,536|
|Excel 2007 (version 12)||1,048,576|
|Excel 2010 (version 14)||1,048,576|
|Excel 2013 (version 14)||1,048,576|
|Excel 2016 (version 14)||1,048,576|
Checking your data is readable
For Excel submissions, you can check this by opening the data file. Close the file without saving it, as Excel may truncate the data if it exceeds the maximum number of rows for that version of the software. For text file submissions, you can check the data by opening the file in a text editor (eg Notepad), but again, close the file without saving.
For date fields, NFI prefers “ddmmyyyy” but “ddmmyy” is also acceptable). If a date separator is used, it should be either a forward slash ( / ) or a hyphen ( - ). Other date formats are also acceptable: dd-mmm-yyyy (01-JAN-2012); dd month yyyy (01 January 2012); dd/mm/yyyyhh:mm:ss (01/01/2012 10:14:36); etc.
Monetary amounts must be in the same format throughout the field. Formats must not be mixed. Amounts can be supplied with or without a £ sign. Preferably the amount should be in pounds and pence (for example £123.45), but we can accept amounts that are all in pence if this is the way you hold your data (it is advised to add this as a note to the processor when uploading the data).
If monetary values cannot be supplied, leave the field blank. Do not insert a zero.
If a field type is alpha numeric (neither a date nor a number), this is referred to as a ‘character’ field for the purposes of this exercise. Fields such as “VAT registration number” and “suppliers invoice number” (which can often contain a combination of letters and numbers) are character fields.
Blank fields should be space filled for fixed-length records. For CSV records, the blank field must still be represented by a delimiter.
Data should be password protected at the earliest opportunity after extraction. Standard encryption or compression software usually produces a file with a .zip, .7z or .rar extension.
Here is a list of acceptable extensions for the file types of data extracted from the host system:
However, this list is not exhaustive so if your file data has an extension that is not on the above list, please consult our helpdesk at firstname.lastname@example.org.