Help Documents
Chevron arrow pointing to the right.
Uploading a claims file

What this article covers: How to upload a claims file to ClaimScore for bulk fraud analysis β€” preparing your file, adjusting import settings, matching columns, and moving the file through pre-processing, review, and analysis. Use this method when you have a batch of existing or already-submitted claims to analyze. To submit claims in real time, see Connecting via API (Real-time) instead.


What is a Claims File?

A claims file is a CSV containing one row per claim. Uploading a file is the batch method of getting claims into ClaimScore: you bring in a set of existing claims together in a single file.

A claims file can represent:

  • Claims submitted through a paper form that have been digitized
  • Claims collected through another system and exported for review
  • Any batch of already-submitted claims you want ClaimScore to analyze

ClaimScore checks the file, classifies each claim as New, Duplicate, Existing, or Insufficient, and then runs fraud analysis on the eligible claims.

πŸ’‘ Tip: Upload and API submission aren't mutually exclusive. Many cases run real-time API submission for their live claims flow and use file upload to bring in paper or legacy claims from other systems.

How to Get There

There are two ways to start an upload:

  • Click the β€˜+’ button in the top-right corner of the screen and select Upload Claims File.
  • Or go to the Claim Files page and click the Upload Claims File button in the top right.

The Upload Process

Step 1 β€” Prepare Your File

Click Download template file to get a CSV containing all the required and recommended columns ClaimScore expects for a proper analysis. Matching your file to the template now means far less manual work at the column-matching step.

Once your file is ready, either drag and drop it into the upload zone or click Browse to select it from your folders. Only CSV files are accepted.

Import settings

‍In the top-right corner of this screen, click Import Settings to adjust how ClaimScore reads your CSV:

  • Delimiter character β€” The character separating values in each row. Select from the list, or choose Other to type in any character.
  • Escape character β€” The character used to escape special characters in your data. Select from the list, or choose Other to type in any character.
  • File contains column headers β€” Toggle this on if your file's first row is column names rather than claim data.

Adjust these as needed, then click Continue to move to column matching.

πŸ’‘ Tip: If your file opens correctly in a spreadsheet program with clean, separate columns, the default delimiter and escape settings will usually work. Only change them if you know your file uses non-standard formatting.

Step 2 β€” Column Matching

On the Column Matching screen, you tell ClaimScore which column in your file corresponds to each field it expects.

Field groups‍

At the top, three progress indicators show the fields grouped by importance:

Group Count Description
Required 2 Admin ID and Access Type. Both must be matched β€” you cannot proceed without them.
Recommended 12 Not mandatory, but they broaden the evidence available for analysis.
Optional 10 Additional fields that add further corroborating signal when available.

Click any of these indicators to open a drawer showing exactly which fields in that group are already matched and which still need matching.

πŸ’‘ Note: Matching more fields does not make fraud analysis more accurate β€” accuracy comes from ClaimScore's methodology, not from field count. What additional fields do is increase coverage and evidentiary breadth, giving the analysis more corroborating signals to work with. Matching the required and recommended fields is strongly encouraged for this reason.

Chip filters

‍Below the indicators, use the chip filters to toggle your view between All, Matched, Unmatched, and Errors. The Errors filter is the fastest way to find what's blocking you from proceeding.

Matching a column

‍For each of your columns, use the field dropdown to select which ClaimScore field it maps to. Beneath each column you'll see a preview of up to five sample rows drawn from the file, so you can confirm the match looks right. If your file contains column headers, those appear above the sample rows.

Error states to watch for:
  • Formatting error β€” The data in that column doesn't match the expected format (e.g., ZIP Code with non-numeric characters, or a date in the wrong format). You'll see this flagged in red on the affected column.
  • Missing data β€” A required field has a column matched but the data is largely empty.
  • Unmatched required column β€” A field ClaimScore requires has not been matched to any column in your file.

When there are errors, the Pre-Process File button at the bottom remains disabled. You cannot proceed until all errors are resolved.

When all required columns are matched and error-free, click Pre-Process File to continue.

πŸ’‘ Tip: At minimum, match both Required fields and as many Recommended fields as your file contains before pre-processing. You can skip Optional fields, but each one you add strengthens the evidentiary picture for that batch.

Step 3 β€” Pre-Processing

After you click Pre-Process File, ClaimScore analyzes the file's contents in the background to profile what's inside it. This can take several minutes depending on file size. You don't need to stay on this screen β€” you can keep using the app, and the file's status will update when it's done.

Step 4 β€” Review the Results Summary

When pre-processing finishes, the file's status changes to Ready for Review. Go to the Claim Files page and open your file to see the results summary, which reports the total claims in the file along with a count and percentage for each type:

Claim Type Definitions
New Claims not previously seen in the system. These are the primary candidates for fraud analysis.
Duplicate Claims that appear more than once, either within this file or against a claim already in our system.
Existing Claims already present in the system from a previous upload.
Insufficient Claims that don't carry enough data for ClaimScore to produce a score, and so cannot be processed.

From here you have two options:

  • Archive β€” Choose this if the file isn't what you expected (for example, far fewer valid claims than anticipated, or a high rate of duplicate or insufficient claims).
  • Analyze Claims β€” Send the new claims forward for fraud analysis. This changes the file's status to Pending Analysis.
πŸ’‘ Tip: Review the distribution before analyzing. An unusually high duplicate or insufficient rate often points to a problem in the source file β€” worth investigating before you commit the batch to analysis.

Step 5 β€” Analysis and completion

While the file is in Pending Analysis, fraud analysis runs in the background and may take some time. When it finishes, you'll receive an email notification and the status will change to Completed. Your results are then available in the dashboard.

Understanding File Statuses

As your file moves through the process, its status in the Claim Files table will change:

Status What it means
Pre-Processing ClaimScore is parsing and validating the file contents
Ready for Review Pre-processing is complete. Review the results summary and decide whether to proceed
Pending Analysis You've clicked Analyze Claims. Fraud analysis is running
Completed Fraud analysis is done. Results are available in the dashboard
Archived File is no longer active. This is permanent and cannot be undone.
πŸ’‘ Note: Archiving a file can't be undone from within the app. If you archived a file by mistake, contact us at contact@covalynt.com and we can recover it for you.

What Happens Next

Once analysis is complete, the file status changes to Completed. Head to the dashboard to review your claim results. See: 6. ClaimScore Dashboard Quickstart

‍