{"id":27358,"date":"2026-05-04T15:31:09","date_gmt":"2026-05-04T15:31:09","guid":{"rendered":"https:\/\/synder.com\/help\/?p=27358"},"modified":"2026-05-04T16:23:39","modified_gmt":"2026-05-04T16:23:39","slug":"detailed-guide-to-the-most-common-business-importer-errors","status":"publish","type":"post","link":"https:\/\/synder.com\/help\/detailed-guide-to-the-most-common-business-importer-errors\/","title":{"rendered":"Most Common Business Importer Errors"},"content":{"rendered":"\n
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.<\/p>\n\n\n\n
The goal is to help identify the root cause quickly, understand why it happens, and know how to fix it before re-importing.<\/p>\n\n\n\n
Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error messages:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error messages:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error messages:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error message:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error messages:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error messages:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Do not use custom values like Yes, No, or Billed.<\/p>\n\n\n\n Typical error messages:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error message:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error message:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error messages:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error message:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error message:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error messages:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong> Typical error message:<\/strong><\/p>\n\n\n\n Problem:<\/strong> Solution:<\/strong> Right way:<\/strong>
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Update all date values in the import file to the required format: MM\/dd\/yyyy.<\/p>\n\n\n\n
<\/strong> Use dates like 01\/15\/2026 and make sure the entire date column uses the same format consistently.<\/p>\n\n\n\n\n
2. Invalid currency code<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Replace the incorrect value with a supported currency code such as USD, EUR, CAD, or GBP.<\/p>\n\n\n\n
<\/strong> Keep the Currency column standardized and use only valid ISO currency codes before importing.<\/p>\n\n\n\n\n
3. Account not found in your books<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Create the missing account in your Books before importing again, or enable Account Auto-creation.<\/p>\n\n\n\n
<\/strong> Make sure every account name in the file exactly matches an existing account in your accounting platform.<\/p>\n\n\n\n\n
4. Bank account not found<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Create the missing bank account in your Books before re-importing.<\/p>\n\n\n\n
<\/strong> Verify the bank account setup before importing any check transactions. Example: Southside-bank Of America.<\/p>\n\n\n\n\n
5. Product or service not found<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Review every transaction line and make sure the Product\/Service column is filled in with valid.<\/p>\n\n\n\n\n
6. Customer not found or missing<\/strong><\/h2>\n\n\n\n
<\/strong> Your books requires a customer, but the customer does not exist in the company file or the customer field is blank.<\/p>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Confirm customer mapping whenever the transaction is customer-facing or billable.<\/p>\n\n\n\n\n
7. Invalid billable status<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Replace the invalid value with a supported one.<\/p>\n\n\n\n
<\/strong> Use the exact version required by your import setup, such as:<\/p>\n\n\n\n\n
\n
8. Missing customer for billable expenses<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Provide a valid customer name for every billable line and make sure that customer already exists in Books.<\/p>\n\n\n\n
<\/strong> Always validate the Billable status field together with the Customer field. Example customer: ABC Marketing.<\/p>\n\n\n\n\n
9. Incorrect amount calculation<\/strong><\/h2>\n\n\n\n
<\/strong> The numeric values in the file do not reconcile the way your accounting platform expects. For Bills, the line amount must match Quantity \u00d7 Rate.<\/p>\n\n\n\n
<\/strong> Make sure the import file uses the correct formula: Quantity \u00d7 Rate = Amount.<\/p>\n\n\n\n
<\/strong> If Quantity is 2 and Rate is 4, the Amount must be 8. Use spreadsheet formulas instead of typing totals manually whenever possible.<\/p>\n\n\n\n\n
10. Incorrect transaction reference in Bill Payments<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Verify that:<\/p>\n\n\n\n\n
<\/strong> Always confirm that the bill has already been imported or already exists before importing the related payment. Correct examples: Bill Number: 243, TxnID: 234.<\/p>\n\n\n\n\n
11. Incorrect total amount when paying multiple bills<\/strong><\/h2>\n\n\n\n
<\/strong> One payment is applied to several bills, but the total payment amount in the file does not equal the sum of the selected bills.<\/p>\n\n\n\n
<\/strong> Add together the full value of all bills included in that payment and make sure the payment amount matches the total.<\/p>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n\n
12. Incorrect total amount when applying credits or journal entries<\/strong><\/h2>\n\n\n\n
<\/strong> The payment amount does not correctly account for vendor credits or journal entries, causing the totals to be inconsistent.<\/p>\n\n\n\n
<\/strong> Calculate the payment total using:
Bill amount \u2013 Journal Entry or Vendor Credit<\/p>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n\n
13. Incorrect or missing tax code<\/strong><\/h2>\n\n\n\n
<\/strong> The tax code in the file does not exist in Books, is spelled differently from the configured tax code, or is missing completely.<\/p>\n\n\n\n
<\/strong> Use the exact existing tax code name from your Books, or create\/import the tax code before importing the transactions that depend on it.<\/p>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n\n
14. Tax rate or tax amount mismatch<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Make sure the tax amount logically matches the tax rate.<\/p>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n\n
15. Duplicate document number<\/strong><\/h2>\n\n\n\n
<\/strong> 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.<\/p>\n\n\n\n
<\/strong> Use a unique number in the import file, or enable auto-increment numbering in importer settings if that option is available.<\/p>\n\n\n\n