Crunchafi

Troubleshooting File Upload Errors

The article details troubleshooting steps for file upload errors related to unsupported file types, file size limits, maximum file counts, and file formatting issues for COA or Trial Balance files, advising users to ensure files have correct extensions (.csv, .xls, .xlsx), appropriate sizes (under 10MB and over 4 bytes), valid content matching their format, and to contact support if errors persist.

Troubleshooting File Upload Errors

This article provides troubleshooting help for potential error messages related to file upload or AI processing. Contact the support team for assistance if you receive an error not covered in this article.

File Size & Type

  • Unsupported file type: The COA or Trial Balance file does not have one of the following file extensions: .csv, .xls, or .xlsx. Upload a file with a supported file extension to continue.
  • File too large (max 10 MB): The COA or Trial Balance file size exceeds the limit of 10MB. Upload a file that is 10MB or smaller to continue.
  • Cannot upload N files. Maximum 60 files allowed, currently have X.: The selected Trial Balance files would exceed the 60-file maximum. Consolidate or remove one or more files to continue. Note: This only applies to Trial Balance files.
  • File is too small to be a valid document.: The COA or Trial Balance file is smaller than 4 bytes. Confirm you are uploading a valid document to continue.

File Formatting & Validation

The following error messages are triggered if the uploaded file does not match the format expected for the file extension:

  • File content does not match .xls format.: The uploaded file has the .xls extension, but the contents do not match the Excel 97-2003 data structure. This could be due to a .xlsx or .csv file being renamed or saved with the .xls extension. Try re-exporting the file from your accounting system or open the file in Excel and save it with the correct extension.
  • File content does not match .xlsx format.: The uploaded file has the .xlsx extension, but the contents do not match the ZIP/Office Open XML archive data structure. The file may be of a different type (e.g., .csv, .xls, or HTML) or was corrupted mid-export. Try re-exporting the file or open it in Excel and save it with the correct extension.
  • File content appears to be a binary document, not CSV.: The uploaded file has the .csv extension, but the contents follow the data format of a standard Excel file (.xls). The file was most likely mislabeled. Either rename it to .xls or open it in Excel and save as CSV if you prefer to upload a CSV file.

Excel Formula Evaluation Errors (.xlsx files only)

When .xlsx files are uploaded, the system checks them for a safe subset of Excel formulas. Any formula outside of this subset triggers an error message. In most cases, files exported from accounting systems have cached values and are not impacted by these validations. These errors most commonly appear with files that were manually edited in Excel before upload.

Unless otherwise noted, the error can be fixed by opening the Excel file, selecting and copying all impacted cells, pasting them as Values Only (i.e., remove formulas), saving the file, and re-uploading it.

  • This file contains N formula(s) that cannot be evaluated. For example: {sample}.: Triggered when any unsupported formula is present with no cached values.
  • Cell {ref}: VLOOKUP (lookup formula): Cell uses VLOOKUP, HLOOKUP, or XLOOKUP.
  • Cell {ref}: XLL.GL (add-in formula): Cell uses an Excel add-in function (e.g., Dynamics 365 GL functions).
  • Cell {ref}: EOMONTH (date formula): Cell uses a date function such as EOMONTH, TODAY, NOW, or EDATE.
  • Cell {ref}: IF (conditional formula): Cell uses IF, IFS, SWITCH, IFERROR, IFNA, SUMIFS, COUNTIFS, or AVERAGEIFS.
  • Cell {ref}: SUBTOTAL (subtotal formula): Cell uses SUBTOTAL.
  • Cell {ref}: circular reference detected: Cell formula depends on its own value directly or indirectly.
  • Cell {ref}: whole-column range references (e.g., A:A) in SUM are not supported - save the file with values and re-upload.: SUM formula contains a whole-column range reference. This error can also be fixed by narrowing the range to only show the actual data if the formula needs to remain.

Chart of Accounts - Structural Validation

These checks apply to COA uploads only and run after the file has been converted to CSV.

  • File is empty or could not be read.: File contains no content. Confirm the correct file was selected and try again.
  • Failed to parse file: {details}: CSV parsing threw an exception. Review the exception message for guidance.
  • File contains no data rows.: File parsed successfully but no data rows were found. Confirm the correct file was selected and try again.
  • File has only N data rows. A Chart of Accounts should have at least 5 accounts.: Fewer than 5 data rows were detected. Confirm the full file was exported from the accounting system and try again.
  • File has only N column(s). A Chart of Accounts needs at least 2 columns (account ID and name).: Fewer than 2 columns were detected. Confirm the full file was exported from the accounting system and try again.
  • Could not detect an account identifier column. Expected a column with account numbers or codes (e.g., '1000', 'A-100', '4.1.001').: No column matching account number patterns could be identified. Check the file for an account ID and try again.

Warning Messages

If you receive any of the following warning messages, you can still proceed with your upload (if applicable):

  • N of total rows (%) are empty. This may indicate a formatting issue.
  • This file may be a Trial Balance rather than a Chart of Accounts. Found columns that look like amounts {list}. If this is intentional, you can proceed.

Note: If you do not have access to a COA, review the guide on using a Trial Balance instead of a Chart of Accounts.

System-Specific Messages

When users submit files for processing, the system can trigger three types of errors:

  1. 1.AI ran into data validation issues that can be recovered by the user
  2. 2.AI ran into a backend workflow issue that is not recoverable by the user
  3. 3.The system ran into a data ingestion issue that requires the user to re-upload files

AI Data Validation Issues

If processing completes and AI detects validation issues, the user is shown expandable issue groups with details and options to download the full error report and re-upload files once fixed.

  • Balance: {Month Year} monthly totals don’t balance to zero. Check for missing or incorrect entries in your source file. Correct the trial balance for the named month and re-upload.
  • Missing Data: {Month Year} is missing from the trial balance. Add the missing month(s) and re-upload.
  • Duplicate Data: Review the downloadable error report for specifics.
  • Other categories: Review the downloadable error report for specifics.

AI Processing Issues

Receiving a Something Went Wrong error message with the details below means that the issue cannot be resolved by retrying the processing or re-uploading the file. Contact support for assistance. This may be the case, for example, if there has been no progress on processing for more than 1 hour.

We're sorry - the AI ran into a problem it couldn't recover from. Unfortunately, there is no workaround for this issue. Please contact Crunchafi Support and provide the reference number below.

Data Ingestion Issues

Receiving a Processing Failed error message indicates that the files need to be re-uploaded. Clicking the Re-upload files button redirects you to the Chart of Accounts upload step. Below are the possible error codes and their descriptions:

  • TypeConversionFailure: Unable to parse data format in uploaded file.
  • ValidationFailure: Data validation failed.
  • MissingRequiredField: Required data is missing from uploaded file.
  • MappingColumnNameNotFoundInSourceFile: A required column was not found in the uploaded file.
  • (any other code): Data processing error: {code}
  • (no error code present): Data processing encountered an error.