Most Common Business Importer Errors

This guide summarizes the most frequent problems users face when importing data into your accounting platforms through Business Importer. These errors appear across different entities such as Invoices, Bills, Bill Payments, Checks, Estimates, Tax Codes, and some account or access scenarios.

The goal is to help identify the root cause quickly, understand why it happens, and know how to fix it before re-importing.

1. Incorrect date format

Problem:
 The accounting platform expects dates in a specific format. If the import file uses a different style, the value cannot be read correctly. For example, 01-14-2015 may be used instead of 01/14/2015.

Solution:
 Update all date values in the import file to the required format: MM/dd/yyyy.

Right way:
 Use dates like 01/15/2026 and make sure the entire date column uses the same format consistently.

Typical error messages:

  • WARNING Error parsing date 01-15-2026. Expected format currently MM/dd/yyyy.
  • WARNING Error parsing date 01-15-2026: Expected format currently MM/dd/yyyy.

2. Invalid currency code

Problem:
 The currency field contains a value that is not a valid ISO 4217 currency code supported by the accounting platform. For example, US is not valid, while USD is valid.

Solution:
 Replace the incorrect value with a supported currency code such as USD, EUR, CAD, or GBP.

Right way:
 Keep the Currency column standardized and use only valid ISO currency codes before importing.

Typical error messages:

  • ERROR Bill BILL-020: Invalid or Unsupported currency type supplied. Supplied value: US.
  • ERROR Bill Payment 20: Invalid or Unsupported currency type supplied. Supplied value: US.
  • ERROR Purchase PUR-002: Invalid or Unsupported currency type supplied. Supplied value: US.

3. Account not found in your books

Problem:
 The application tries to match an account from the file to the Chart of Accounts in books, but that account does not exist. This can affect expense accounts, AR-related accounts, or other mapped accounts used in the transaction.

Solution:
 Create the missing account in  your Books before importing again, or enable Account Auto-creation.

Right way:
 Make sure every account name in the file exactly matches an existing account in your accounting platform.

Typical error messages:

  • Account with Name = “name” is not found in your QuickBooks Online account.
  • Account with Name = “Meals and Entertainment” is not found in your QuickBooks Online account.
  • Required parameter Line.AccountBasedExpenseLineDetail.AccountRef: is missing in the request.

4. Bank account not found

Problem:
 This is a specific account-mapping issue, especially common when importing Checks. A Check must be linked to a valid bank account in books. If the bank account named in the file does not exist, the transaction cannot be imported.

Solution:
 Create the missing bank account in your Books before re-importing.

Right way:
 Verify the bank account setup before importing any check transactions. Example: Southside-bank Of America.

Typical error message:

  • ERROR Purchase CHK-001: CP: Account with Name = “BI Bank” is not found in your QuickBooks Online account.

5. Product or service not found

Problem:
 A transaction line refers to a product or service that does not exist in books, or the product/service field is left blank. Every line must include a valid product or service. If item-based lines are being imported, the item must already exist in the Products and Services list.

Solution:
 Create the missing product or service in your Books, enable automatic product creation if available, or fill in the missing field in the import file.

Right way:
 Review every transaction line and make sure the Product/Service column is filled in with valid.

Typical error messages:

  • Product(Service) with Name = “Design” is not found in your QuickBooks Online account.
  • Required parameter Line.SalesItemLineDetail is missing in the request.

6. Customer not found or missing

Problem:
 Your books requires a customer, but the customer does not exist in the company file or the customer field is blank.

Solution:
 Create the customer in books before importing, or enable customer auto-creation. If the transaction is billable, provide a valid customer name on each applicable line.

Right way:
 Confirm customer mapping whenever the transaction is customer-facing or billable.

Typical error messages:

  • Customer with DisplayName = “Cool Cars” is not found in your QuickBooks Online account.
  • Business Validation Error: You must select a customer.
  • Business Validation Error: You must select a customer for each split line that is billable.

7. Invalid billable status

Problem:
 The Billable status field contains a value that Books does not recognize. The field must use one of the exact supported values expected by the importer and Books mapping.

Solution:
 Replace the invalid value with a supported one.

Right way:
 Use the exact version required by your import setup, such as:

  • Billable
  • Not Billable or NotBillable
  • Has Been Billed or HasBeenBilled

Do not use custom values like Yes, No, or Billed.

Typical error messages:

  • ERROR Bill BILL-001: Property Name: Cannot construct instance of BillableSt specified is unsupported or invalid.
  • ERROR Purchase PUR-026: Property Name: Cannot construct instance of BillableSt specified is unsupported or invalid.

8. Missing customer for billable expenses

Problem:
 When a line is marked as billable, Books require a customer to be assigned to that line. If the customer is missing, the importer cannot create the transaction correctly.

Solution:
 Provide a valid customer name for every billable line and make sure that customer already exists in Books.

Right way:
 Always validate the Billable status field together with the Customer field. Example customer: ABC Marketing.

Typical error message:

  • Business Validation Error: You must select a customer for each split line that is billable.

9. Incorrect amount calculation

Problem:
 The numeric values in the file do not reconcile the way your accounting platform expects. For Bills, the line amount must match Quantity × Rate.

Solution:
 Make sure the import file uses the correct formula: Quantity × Rate = Amount.

Right way:
 If Quantity is 2 and Rate is 4, the Amount must be 8. Use spreadsheet formulas instead of typing totals manually whenever possible.

Typical error message:

  • Amount is not equal to UnitPrice × Qty.

10. Incorrect transaction reference in Bill Payments

Problem:
 The payment refers to a bill number or transaction ID that your Books cannot find, or the bill exists but does not match the specified vendor.

Solution:
 Verify that:

  • the referenced bill already exists in your Books,
  • the document number is correct,
  • the transaction ID is valid,
  • the transaction belongs to the correct vendor.

Right way:
 Always confirm that the bill has already been imported or already exists before importing the related payment. Correct examples: Bill Number: 243, TxnID: 234.

Typical error messages:

  • ERROR BillPayment: Bill with DocNumber = “2” is not found in your QuickBooks Online account.
  • ERROR BillPayment: TxnID Cannot Be Linked.

11. Incorrect total amount when paying multiple bills

Problem:
 One payment is applied to several bills, but the total payment amount in the file does not equal the sum of the selected bills.

Solution:
 Add together the full value of all bills included in that payment and make sure the payment amount matches the total.

Right way:
 If one bill is 155.00 and another is 55.00, the total payment amount must be 210.00. Reconcile the payment total against the bill list before importing.

Typical error message:

  • Business Validation Error: The Amount Paid (plus credits) can’t be less than the selected charges.

12. Incorrect total amount when applying credits or journal entries

Problem:
 The payment amount does not correctly account for vendor credits or journal entries, causing the totals to be inconsistent.

Solution:
 Calculate the payment total using:
Bill amount – Journal Entry or Vendor Credit

Right way:
 If the bill is 155.00 and the vendor credit is 55.00, the total payment amount should be 100.00. Check whether credits are being applied before finalizing the payment amount.

Typical error message:

  • Business Validation Error: The Amount Paid (plus credits) can’t be less than the selected charges.

13. Incorrect or missing tax code

Problem:
 The tax code in the file does not exist in Books, is spelled differently from the configured tax code, or is missing completely.

Solution:
 Use the exact existing tax code name from your Books, or create/import the tax code before importing the transactions that depend on it.

Right way:
 Use exact configured values such as TAX and NON for US companies, or 20% / another configured tax code for non-US companies. Do not assume values like FALSE or tax will work unless they exactly match your Books.

Typical error messages:

  • TaxCode with Name = “tax” is not found in your QuickBooks Online account.
  • TaxCode with Name = “FALSE” is not found in your QuickBooks Online account.
  • Business Validation Error: Make sure all your transactions have a VAT rate before you save.

14. Tax rate or tax amount mismatch

Problem:
 The tax rate, tax code, and tax amount do not agree with each other. For example, a tax rate of 0.00 is used together with a non-zero tax amount.

Solution:
 Make sure the tax amount logically matches the tax rate.

Right way:
 If the tax rate is 0.00, the tax amount must also be 0. If the tax amount is non-zero, use the correct non-zero tax rate. Example: Tax Rate: 20% VAT with the tax amount calculated accordingly.

Typical error message:

  • Business Validation Error: We’re sorry, QuickBooks encountered an error while calculating tax. Try reselecting the tax rate or reentering the product/service item and saving the form again.

15. Duplicate document number

Problem:
 The document number, reference number, or check number in the import file has already been used in your Books, and duplicate numbering is not allowed.

Solution:
 Use a unique number in the import file, or enable auto-increment numbering in importer settings if that option is available.

Right way:
 Use unique values such as Check Number: PUR-021 or Reference Number: 122. Be especially careful when re-importing corrected transactions, because it is easy to reuse numbers that were already imported successfully.

Typical error messages:

  • ERROR Purchase PUR-003: Duplicate Document Number Error. You must specify a different number. This number has already been used.
  • Duplicate Document Number Error: You must specify a different number. This number has already been used.

Reach out to Synder Team via online support chat or email with any questions you have – we are always happy to help you!

Author

Leave a Reply

Your email address will not be published. Required fields are marked *