CSV Validator

File Structure and Required Columns

This CSV validator checks the file against your selected delimiter and column rules. Choose the source encoding before reading the results. UTF-8 suits many exports. Windows-1252 and UTF-16LE handle files saved in those encodings.

Column-count errors mean a record has more or fewer fields than the first record. Quoting errors mean a field’s quotes cannot be read consistently. Required-value errors identify a selected column whose value is missing or contains only spaces.

If the first record contains headers, empty or repeated headings are reported separately. Enter any documented required headings, one per line, to detect a missing column. Select the columns that require a value. With no headers, the check names columns by their position.

Review Each Error

Each finding shows the source line, column and original value. A quoted field can span several physical lines, so its record number can differ from its source line. Use the source line to locate it.

The check preserves spaces and non-ASCII text. A quoted comma stays inside its field, and two quotes inside a quoted field become one quote in its value. These rules follow RFC 4180’s CSV format. The tool also accepts LF or CR record endings.

Export a Deliberate Correction

Edit the source copy to repair a value or quoting error. Select the export delimiter and encoding, then choose Check and compare export. Changing a source setting reads the original file again and clears edits.

The comparison shows the source and export record counts, column counts and each changed cell. Added and removed values are labelled separately. All findings and changes remain available through their page controls.

The export quotes every field and uses CRLF record endings. UTF-8 and UTF-16LE exports preserve Unicode text. Delimiter or encoding conversion alone leaves the decoded cell values unchanged. Confirm the comparison before downloading.

Correct blocking errors before exporting. Duplicate combinations remain warnings for you to assess. CSV preserves formula-looking text, so spreadsheet software can interpret it when opened. Review unfamiliar formulas before opening the export in a spreadsheet.

Your file is read locally and never uploaded, logged or saved in browser storage. Clear file, navigation or a restored page clears the working copy. A downloaded file remains wherever you save it.

Duplicates and Import Schemas

Select one or more columns that identify a record, such as an invoice number and entity code. The check flags repeated combinations with matching text. Blank combinations are left to the required-value checks.

The optional Xero bank field pre-check asks you to map a date column and one signed amount column. It checks real calendar dates in your selected format and decimal amounts. Xero’s bank CSV instructions explain the Date and Amount fields and the import mapping.

A pass covers only those local field rules. The destination’s mapping, account settings and other import checks still apply. This tool does not lodge a TPAR or confirm an official lodgment. For another import, select required columns from its documented requirements before checking the file.

Start From a Blank CSV Template

Enter the destination’s exact column headings, then select the required fields for your blank CSV template. The bank field pre-check includes Date and Amount automatically. Choose the export delimiter and encoding used for corrected files, then download the header-only template.

The template contains no data records. Add your own reviewed records, then choose the completed file in the validator. Set its source delimiter and encoding to match the template. Select the required-value columns and map the date and amount columns when using the bank field pre-check.

A blank template cannot pass the completed-file check. Validate your filled file and review its findings before importing it. A local pass does not confirm that the destination will accept the import.