Washington CCRS CSV help

CCRS NumberRecords mismatch: check the CSV record count

A record-count mismatch means the number declared in NumberRecords differs from the data records in the file. The submission header and column names are not data records.

What to look for

In Preflight, the finding looks like NumberRecords says 3, but 2 records were found. That is Preflight's wording, not a quoted CCRS response.

  1. Open a copy of the CSV and locate its NumberRecords header.
  2. Compare the declared count with the intended data records after the column-header row.
  3. Check whether an export or edit omitted a record. Restore missing data if necessary; update the count only when the records are complete.
  4. Save a CSV copy and check that file again.

A small example

This made-up file declares three records but contains two Area records:

SubmittedBy,Alex Example
SubmittedDate,09/04/2026
NumberRecords,3
LicenseNumber,Area,IsQuarantine,ExternalIdentifier,CreatedBy,CreatedDate,UpdatedBy,UpdatedDate,Operation
123456,Flower Room,FALSE,area-01,Alex Example,09/01/2026,,,Insert
123456,Drying Room,FALSE,area-02,Alex Example,09/01/2026,,,Insert

If these are the two intended records, the count is NumberRecords,2. This example is for learning, not submission.

How Preflight counts

The checker parses CSV records rather than counting newline characters. Quoted fields can contain line breaks; Preflight ignores completely blank records. It checks the count for supported Area, Strain, and Inventory files.

Check your CSV privately

Free to use. Area, Strain, and Inventory files stay in your browser. No account or file upload. A passing result covers only implemented checks and does not guarantee CCRS acceptance.

Rule reference: LCB CCRS Upload User Guide, February 2026, pages 7. Checked September 4, 2026. Examples and descriptions of Preflight behavior are our own. This is an independent tool, not an LCB service. Official templates and resources.