March 2, 2026
Files do not always arrive in the exact structure used in QuickBooks Desktop.
Your spreadsheet may already contain invoice numbers you need to preserve. Customer names may be slightly different from the names in QuickBooks. A file may contain new products that have not yet been created in QuickBooks. You may also need to check for transactions that were imported previously before running the file again.
SaasAnt Transactions Desktop provides Import Settings to control how these situations are handled during a QuickBooks Desktop import.
Instead of changing every Excel or CSV file manually, you can configure how SaasAnt handles transaction numbers, dates, matching records, customers, vendors, items, accounts, multiline transactions, custom fields, and other import requirements.
This guide explains each setting and, more importantly, when it can be useful in a real QuickBooks Desktop workflow.
SaasAnt Transactions (Desktop) provides limitless customizations to meet the unique requirements of every accountant. Following configurations are available in SaasAnt Transactions (Desktop).
You can open Import Settings in either of these ways:

Edit → Import Settings
or
Click Import Settings from the import screen.
If you are already preparing an import, using the Import Settings button from the import workflow is usually the quickest option.
Before changing a setting, check what your source file contains and how you want that data to appear in QuickBooks Desktop.
Learn how to import transactions into QuickBooks Desktop using SaasAnt Transactions Desktop
Video Tutorial for How to Import Bulk Data into QuickBooks Desktop using SaasAnt Transactions Desktop:

Turn this setting on when the transaction numbers in your source file should also become the transaction numbers in QuickBooks Desktop.
This can apply to reference numbers such as:
Invoice Number
Check Number
Sales Receipt Number
Payment Number
Bill Number
Suppose your billing system exports invoices numbered:
INV-10051
INV-10052
INV-10053
If those numbers are already being used to identify the invoices outside QuickBooks, you may want the same reference numbers in QuickBooks Desktop.
Turn Assign Transaction Reference From File on so SaasAnt uses the numbers supplied in your import file.
If you want QuickBooks to handle the transaction numbering instead, turn this setting off.
Choose the date format used in your Excel or CSV file.
This helps SaasAnt interpret the dates correctly before sending the transactions to QuickBooks Desktop.
For example, your file may contain dates formatted as:
DD/MM/YYYY
or another supported date structure.
Instead of manually changing every date in the spreadsheet, select the format that matches your source file.
This is particularly useful when files come from another system, another country, or another department where the date structure differs from the format normally used in QuickBooks.
Always check the dates in the Review and Import screen before sending the transactions to QuickBooks.
Repeated imports can be a problem when a file contains records that have already been added to QuickBooks.
SaasAnt lets you decide how an imported transaction should be matched with an existing QuickBooks transaction.
You can match transactions using:
Use the transaction reference number, such as an Invoice Number, Bill Number, or Payment Number, to look for an existing QuickBooks transaction.
You can also match using the QuickBooks Internal ID.
The QuickBooks Internal ID is generated by QuickBooks and can be obtained by exporting the transactions using SaasAnt Transactions Desktop.
Suppose you imported invoices earlier in the week and later received a revised spreadsheet containing some of the same invoice numbers.
Before processing the new file, you can configure SaasAnt to find existing transactions using their reference numbers.
You can then decide how the matched transactions should be handled.
After choosing how SaasAnt should find an existing transaction, select what should happen when a match is found.
There are four available actions.
Choose this when you intentionally want SaasAnt to create another transaction even when the same reference number already exists.
Use this option carefully because it can result in transactions sharing the same reference number.
Use this when you do not want a matched transaction processed again.
The matched record is reported on the results screen so you can review it.
Practical use case
You receive the same weekly file again but are unsure whether some invoices were already imported.
Match using the invoice reference number and use Ignore & Show Warning so existing matching transactions can be identified instead of intentionally creating another copy.
Use this when you want the matched QuickBooks transaction to be replaced with the transaction information from the import.
Important: The complete transaction details are rewritten when this option is used.
Review the source file carefully before using Replace Existing Transaction.
Practical use case
A transaction was previously imported with incorrect information and your corrected source file contains the complete replacement transaction.
You can identify the existing record using its reference number or QuickBooks Internal ID and use the Replace option.
Use this option when the imported data should add a new line item to the existing matched transaction.
Practical use case
An invoice already exists in QuickBooks, but additional line-item data needs to be added to that same transaction.
Use the appropriate matching method and choose Append Existing Transaction.
SaasAnt can also identify matching QuickBooks list records such as:
Customers
Employees
Vendors
Items
You can choose:
The matching list record is reported on screen instead of being replaced.
The existing list information is replaced with the information supplied in the import.
Because the existing list details can be overwritten, check the source data carefully before using this option.
Turn on Pre-Import Validation when you want SaasAnt to validate the complete file before the actual import begins.
The validation can identify common issues such as missing customers or items.
The import begins only when validation for the complete file is successful.
Consider a file containing several hundred invoices.
Without complete-file validation, you may not want to discover halfway through the workflow that required customers or items are missing.
Pre-Import Validation allows you to check the file first and correct the issues before starting the full import.
Files from inventory, ecommerce, billing, or other business systems may contain items that are not yet available in the QuickBooks Item List.
The Product/Service settings control how those items are found or created.

Enable this option when SaasAnt should create an item if the item name supplied in the file cannot be found in QuickBooks.
Suppose you are importing invoices from another system and the file contains several new service or product names.
Instead of stopping to create each missing item separately in QuickBooks before continuing, you can configure SaasAnt to create the missing items during the import.
If you enable this option, review the related default item settings carefully.
You can choose how items from your file are matched to existing QuickBooks items.
Available options include:
Matches the exact item name. The search is not case-sensitive.
Matches the item name while ignoring spacing differences.
Matches the item using a QuickBooks custom field instead of the item name.
Matches the item using an uploaded lookup file.
Your source file contains:
Installation Service
but spacing in the source data is inconsistent.
Using Full Name - Ignore Spaces can help when the difference is caused by spaces rather than the actual item identity.
Your other business system identifies products using an internal product code stored in a QuickBooks custom field.
Instead of relying only on product names, you can use the associated custom-field value to locate the QuickBooks item.
Use this option when item matching should use an associated QuickBooks custom field.
The required custom field must already exist in QuickBooks.
If Create Product/Service Automatically is enabled, you can configure the values used for newly created items.
Select the type of item SaasAnt should create:
Non Inventory
Inventory
Service
Choose the type that correctly represents the items being imported.
Select the income account that should be assigned to the newly created item.
You can provide an expense account for the created item when required.
When creating an Inventory item, specify the Cost of Goods Sold account.
When creating an Inventory item, specify the asset account.
When creating an Inventory item, you can provide the initial quantity.
You can provide the tax code that should be used for automatically created items.
Because these settings affect how new items are created in QuickBooks, confirm the appropriate item type and accounts before running the import.
If Price Level rules are already configured for customers in QuickBooks Desktop, enable this setting when you want those rules to be used when calculating item pricing.
This setting is useful when customers already have QuickBooks price-level rules and the imported transaction should follow those configured prices.
Your source file may contain separate columns for:
Shipping
Discount
Handling
Instead of manually adding those amounts after the transactions are imported, use the Shipping/Discount settings.


Enable Show Shipping/Discount Settings.
Provide the item names used for:
Shipping Charges
Discount
Handling Charges
On the mapping screen, map your source columns to:
Shipping Amount
Discount
Handling Charge
Practical use case
An order export contains:
Invoice | Product | Amount | Shipping | Discount |
|---|---|---|---|---|
INV-501 | Product A | 200 | 15 | 10 |
You can map the transaction values and the separate shipping and discount columns rather than manually adding those values to the invoice after import.

One of the most common problems when moving data between systems is that the name in the source file does not exactly match the name stored in QuickBooks.
SaasAnt provides several ways to locate the correct QuickBooks record.
Enable this option when a customer specified in the import file should be created if that customer cannot be found in QuickBooks.
Use this only when creating a new customer from the import is the intended result.
If a customer may already exist under a different name, first review the customer matching options below.
Customers can be matched using:
Full Name
Full Name - Ignore Spaces
Company Name
First Name
Account Number
Resale Number
Custom Field
Lookup
Example: Source-system IDs are included in customer names
Suppose an older system exports a customer as:
CUST-1845 - Green Valley Services
while the QuickBooks customer is simply:
Green Valley Services
Matching only on Full Name may not suit this file structure.
If your QuickBooks data contains another reliable identifier such as Company Name, Account Number, or a Custom Field, select that matching method instead.
This is especially useful when data comes from systems that use different naming conventions.
Use this option when the value supplied in the file should be matched with a customer custom field stored in QuickBooks Desktop.
Enable this option when a vendor from the import file should be created if that vendor cannot be found in QuickBooks.
Vendor matching options include:
Full Name
Full Name - Ignore Spaces
Company Name
First Name
Account Number
Vendor Tax ID
Custom Field
Lookup
Choose the field that most reliably identifies the vendor in both your file and QuickBooks.
Use this when the vendor should be located using a value stored in a QuickBooks vendor custom field.
Enable this option when an employee from the import file should be created if the employee does not already exist in QuickBooks.
Employee matching options include:
Full Name
Full Name - Ignore Spaces
First Name
Account Number
Custom Field
Lookup
Use this when employee matching should be based on an associated QuickBooks custom field.

Enable this setting when an account named in the import file should be created if the account cannot be found in QuickBooks.
Because the Chart of Accounts affects your accounting records, review account names and the intended accounting structure before automatically creating new accounts.
Use this setting when a class referenced in your source file does not already exist and should be created as part of the import workflow.
Review your existing Class List first so that naming differences do not unintentionally create additional classes.

For some transaction types, the source file can contain a name that does not yet exist in QuickBooks.
SaasAnt allows you to specify which type of name entity should be created when one cannot be found.
Select the type of entity SaasAnt should create when a name used in an imported Journal Entry cannot be found in QuickBooks.
Select the entity type to create when a name used in an imported Deposit cannot be found.
Select the entity type to create when a name used in imported Time Tracking data cannot be found.
Use these settings only when automatically creating the missing name is the intended result.

When this setting is enabled, SaasAnt creates the corresponding:
Receive Payment for an imported Invoice
Bill Payment for an imported Bill
Use this setting only when the imported Invoice or Bill should also have the corresponding payment transaction created.
If the invoice or bill is still unpaid, leave this setting disabled.
Normally, reference numbers can be used to group rows that belong to the same multiline transaction.
Turn Process Each File Line Separately on when each row should instead be treated as its own transaction.
Your spreadsheet contains:
Invoice Number | Item | Amount |
INV-700 | Service A | 100 |
INV-700 | Service B | 150 |
INV-700 | Service C | 75 |
These rows can represent line items belonging to the same invoice because they share the same reference number.
If you enable Process Each File Line Separately, the grouping by reference number is ignored and each row is processed separately.
Choose the setting based on how the rows in your file are intended to become QuickBooks transactions.
Enable this setting when negative numbers in a vendor-transaction file should be converted to positive values during processing.
Review the source file and the intended QuickBooks transaction before enabling this option.
QuickBooks Desktop allows custom fields to be created for information that is specific to your business.
When Display Custom Fields in Mapping Screen is enabled, custom fields configured in QuickBooks are shown on the SaasAnt mapping screen.
You can then map the appropriate source-file column to the QuickBooks custom field.
A company may store an external customer ID, project code, internal product code, or another business-specific value in a QuickBooks custom field.
If that value also exists in your source file, enabling this option lets the field appear during mapping rather than limiting the import to standard fields.
Not every spreadsheet stores invoice items on separate rows.
Some files are structured like this:
Invoice | Item 1 | Amount 1 | Item 2 | Amount 2 |
INV-801 | Consulting | 200 | Setup | 100 |
Enable this option when your line items are stored across multiple columns rather than multiple spreadsheet rows.
SaasAnt allows up to 20 line items to be mapped using this column-based structure.
This can save you from restructuring a source file into multiple rows before importing it.
Enable this option when the import requires supported credit-card-related fields such as:
Card Number
Expiry Date
The relevant fields then become available during mapping.
Only map fields that are required for the transaction and that you are authorized to handle.
You do not need to enable every setting.
Before running an import, ask these questions:
Should QuickBooks use the numbers from my file?
Review Assign Transaction Reference From File.
Does my file use a specific date format?
Set Date Format in File.
Could some transactions already exist?
Configure Find Matching Transactions and the action for matched records.
Could customers, vendors, employees, items, accounts, or classes be missing?
Decide whether they should be matched differently, created automatically, or corrected in the source data.
Does my file contain multiple lines for the same transaction?
Check whether rows should be grouped or processed separately.
Does my file contain custom fields, shipping, discounts, or handling charges?
Enable the appropriate mapping options.
Do I want the entire file checked before anything is imported?
Enable Pre-Import Validation.
Then continue to the Review and Import screen, verify the records, and click Send to QuickBooks only after the file looks correct.
Open Edit → Import Settings from the top menu, or click Import Settings from the import screen.
Yes. Enable Assign Transaction Reference From File to use supported transaction reference numbers from the source file.
Yes. Transactions can be matched using the Reference Number or QuickBooks Internal ID.
You can then choose what SaasAnt should do when a match is found.
You can choose:
Create New Transaction
Ignore & Show Warning
Replace Existing Transaction
Append Existing Transaction
Remember that Replace Existing Transaction rewrites the complete matched transaction.
Yes. Enable Pre-Import Validation. SaasAnt validates the complete file and starts the import only after the full file passes validation.
Yes. Separate settings are available for automatically creating missing customers and vendors.
Before enabling them, check whether the name may already exist in QuickBooks under a different format and review the available matching options.
Yes. Customer matching options include Full Name, Full Name with spaces ignored, Company Name, First Name, Account Number, Resale Number, Custom Field, and Lookup.
You can enable Display Custom Fields in Mapping Screen to display custom fields already configured in QuickBooks during field mapping.
Yes. SaasAnt supports multiline transaction structures. You can control whether rows sharing a reference number are grouped or each row is processed separately.
For files where line items are stored in separate columns, Enable Column Based Multi Line Transaction Mapping supports mapping up to 20 line items.
Yes. Enable Show Shipping/Discount Settings, select the appropriate QuickBooks items, and map the corresponding columns from your source file.
Yes. Use Date Format in File and select the format that matches your Excel or CSV file.