Troubleshooting Common Import Errors

When importing data into AccuArk, the validation step (Step 3 of the import wizard) checks every row before any data is written to the database. Rows that fail validation are flagged with an Error status and a description of the problem. This article covers the most common import errors and provides step-by-step solutions for each one.

1. “Category ‘X’ Not Found” / “Vendor ‘X’ Not Found” / “Customer ‘X’ Not Found”

What it means: The value in your CSV file does not match any existing record in AccuArk. The import wizard tried to look up the name you provided, but no matching category, vendor, or customer was found.

How to fix it:

• Check spelling and spacing — The lookup is case-insensitive, but the name must otherwise match exactly. Look for extra spaces, missing hyphens, or abbreviations that differ from the record in AccuArk.
• Verify the record exists — Open the relevant area of AccuArk (for example, Inventory > Categories for category lookups) and confirm that the record is present.
• Import dependencies first — AccuArk validates lookup references against existing data. If you are importing inventory items that reference categories, the categories must already exist. Follow this recommended import order:
  1. Categories
  2. Vendors
  3. Customers
  4. Inventory Items
  5. Employees
  6. Financial data (Chart of Accounts, Opening Balances, Bills, Invoices)

Importing in this order ensures that each data type can find the records it depends on.

2. “Amount Must Be Greater Than Zero”

What it means: A required numeric field contains a value that is zero, negative, or not a valid number.

How to fix it:

• Check for empty cells — If a numeric field is left blank in your CSV, AccuArk may interpret it as zero. Make sure every required numeric column has a value.
• Remove currency symbols and commas — Values like $29.99 or 1,250.00 can cause parsing failures. Use plain numbers without formatting: 29.99 or 1250.00.
• Look for non-numeric text — Values like “N/A”, “TBD”, or “--” in a numeric column will fail validation. Replace them with a valid number or leave the cell empty if the field is optional.
• Check for negative values — Certain fields (such as selling price or quantity) must be positive. If your CSV contains negative numbers, correct them before re-importing.

3. “Required Field Missing”

What it means: A field that is marked as required has no value for that row, or the required column was not mapped during Step 2 of the import wizard.

How to fix it:

• Check your column mapping — Return to Step 2 and verify that every required field (marked with an asterisk *) is mapped to a column in your CSV file. If a required field shows (Not Mapped), click the dropdown and select the correct column.
• Verify the CSV has data — Open your CSV file in a spreadsheet application and check that the required columns contain values for every row. Look for rows where cells are blank or contain only whitespace.
• Check for hidden characters — Sometimes a cell may appear empty in your spreadsheet but actually contains invisible characters (such as non-breaking spaces). Try deleting the cell contents and retyping the value.

4. “Account Type ‘X’ Not Found”

What it means: When importing a Chart of Accounts, the account type column contains a value that does not match any of the defined account types in AccuArk.

How to fix it:

• Use the exact type names — AccuArk recognizes the following account types: Asset, Liability, Equity, Revenue, and Expense. Your CSV must use one of these exact names.
• Check for variations — Common mistakes include using “Income” instead of Revenue, “Expenses” (plural) instead of Expense, or “Net Worth” instead of Equity. Correct these in your CSV before re-importing.
• Remove extra text — Do not include subcategory qualifiers such as “Current Asset” or “Long-term Liability.” Use only the base type name.

5. “Debits Do Not Equal Credits”

What it means: When importing Opening Balances, the total of all debit amounts must equal the total of all credit amounts. If they do not balance, the import cannot proceed.

How to fix it:

• Review your debit and credit columns — Open your CSV in a spreadsheet and add a sum formula for the debit column and the credit column. The two totals must match exactly.
• Check for missing rows — A common cause of imbalance is a missing balancing entry. For example, if you have asset and liability balances but forgot the equity or retained earnings entry, the totals will not match.
• Check for rounding differences — If your amounts have more than two decimal places, rounding can cause small differences. Round all amounts to two decimal places before importing.
• Verify the correct columns are mapped — Make sure you have not accidentally mapped the debit column to the credit field, or vice versa.

6. “Duplicate Serial Number”

What it means: When importing Serial Numbers, a serial number in your CSV file already exists in the AccuArk database, or the same serial number appears more than once within your file.

How to fix it:

• Check for duplicates within your file — Use your spreadsheet's duplicate detection feature (in Excel: Home > Conditional Formatting > Highlight Cells Rules > Duplicate Values) to find and remove duplicates within your CSV.
• Check if it was already imported — Open Inventory > Serial Tracking in AccuArk and search for the serial number. If it already exists, remove it from your CSV file to avoid the conflict.
• Correct typos — If two serial numbers look similar but should be different, verify that each one is typed correctly.

7. File Read Errors

What it means: AccuArk could not read your file. You may see messages such as “Error loading file,” “File could not be opened,” or “Invalid file format.”

How to fix it:

• Make sure the file is saved as CSV — AccuArk only accepts CSV files. If your file has an .xlsx, .xls, or .ods extension, open it in your spreadsheet application and re-save it as CSV (Comma delimited) (*.csv).
• Close the file in other programs — If the file is currently open in Excel, Google Sheets, or another application, close it before starting the import. Some programs lock the file while it is open.
• Check for file corruption — If the file was transferred via email or downloaded from the internet, it may have been corrupted during transfer. Try re-saving the file from your original spreadsheet.
• Verify the file is not empty — Open the CSV in a text editor (such as Notepad) to confirm it contains data. The first row should contain column headers, and subsequent rows should contain your data.

General Tips for Resolving Import Errors

• Always review Step 3 carefully — The validation preview shows you exactly which rows will succeed, which will be updated, and which have errors. Take the time to scroll through the list before clicking Import.
• Use the Export Error Report — After an import completes, the summary screen provides an Export Error Report button if any rows failed. This report contains only the failed rows along with the specific error message for each one. Use it as your guide for corrections.
• Fix and re-import — Correct the errors in your CSV file, save it, and start a new import. For data types that support upsert (such as Inventory Items, Customers, and Vendors), rows that were already imported successfully will be matched and updated rather than duplicated.
• Import in small batches first — If you are unsure about your data quality, try importing just the first 10 to 20 rows as a test. Once those validate cleanly, import the full file.