July 15, 2026
Businesses do not always create their financial data directly in QuickBooks or Xero.
Invoices may be prepared in spreadsheets. Payroll information may come from a payroll provider. Historical bank transactions may be available only in statements. Accountants may receive customer, vendor, expense, bill, payment, or journal-entry data from several clients in different file formats.
Entering all of this information manually can take hours, especially when hundreds or thousands of records are involved.
SaasAnt helps businesses and accounting professionals move and manage this data more efficiently. This guide explains what SaasAnt Transactions Online does, who it is intended for, and how it fits into different accounting workflows.
SaasAnt Transactions is an accounting-data automation application that helps users import, export, edit, and delete supported transactions and lists in QuickBooks and Xero.
It is available in different versions for:
QuickBooks Online.
QuickBooks Desktop.
Xero.
The features and supported records are not identical across all three versions. A workflow available for QuickBooks Online may work differently or may not be available in QuickBooks Desktop or Xero.
This guide focuses mainly on SaasAnt Transactions Online for QuickBooks Online.
SaasAnt Transactions Online is a cloud-based application for managing QuickBooks Online and Xero data in bulk.
For QuickBooks Online users, it can help with tasks such as:
Importing transactions and lists from files.
Exporting supported QuickBooks data to Excel or CSV.
Editing existing transactions in bulk.
Deleting selected transactions.
Creating several transactions from one working screen.
Importing IIF files.
Extracting information from selected documents and statements.
Applying rules to incoming data.
Automating recurring file imports.
Managing more than one QuickBooks company under supported plans.
The product is intended for situations where entering, exporting, or correcting each record individually would require too much manual work.
Video Tutorial for what is SaasAnt Transactions Online and How to Connect SaasAnt Transactions Online with QuickBooks Online:
No. SaasAnt Transactions Online does not replace QuickBooks Online.
QuickBooks Online remains the accounting system where the company maintains its:
Chart of accounts.
Customers and vendors.
Products and services.
Sales and purchase transactions.
Bank and credit card accounts.
Taxes.
Financial reports.
SaasAnt connects to the QuickBooks company and helps the user perform supported data-management tasks.
A simple way to understand the relationship is:
QuickBooks Online stores and reports the accounting records. SaasAnt Transactions helps users move, prepare, export, correct, and manage those records in bulk.
SaasAnt Transactions Online helps when accounting information exists outside QuickBooks or when existing QuickBooks records need to be managed in bulk.
Common situations include:
A business has hundreds of invoices in Excel.
A bookkeeper receives monthly files from clients.
A payroll provider supplies journal-entry data in a spreadsheet.
Historical transactions are missing from QuickBooks.
A bank feed does not contain the full transaction history.
Existing transactions contain incorrect accounts, dates, classes, locations, or descriptions.
An accounting firm needs a repeatable process across several clients.
QuickBooks data needs to be downloaded for analysis or correction.
A recurring file needs to be imported without repeating the complete setup every time.
SaasAnt reduces the repetitive work involved in these processes. It does not decide every accounting treatment automatically.
The user remains responsible for confirming how the data should be recorded in QuickBooks.
SaasAnt Transactions Online is intended for people who regularly work with financial data in QuickBooks Online or Xero.
Its main user groups include:
User group | Common reason for using SaasAnt |
Accountants and bookkeepers | Import client files, complete catch-up work, post journals, correct transactions and manage recurring workflows |
Accounting firms | Manage several client companies, standardize imports and give team members controlled access |
Small business owners | Move invoices, expenses, payments and lists from spreadsheets into QuickBooks |
Controllers and finance teams | Process recurring entries, large transaction batches and month-end corrections |
Accounts payable teams | Import bills, expenses, vendor credits and purchase transactions |
Accounts receivable teams | Import invoices, sales receipts, customer payments and credit transactions |
Consultants and QuickBooks professionals | Set up accounting data, correct records and transfer supported data between company files |
Multi-company organizations | Manage financial data across several entities or locations |
The product is not limited to a particular industry. It is useful wherever structured accounting information needs to be moved into or out of QuickBooks efficiently.
Accountants and bookkeepers frequently receive information from clients in spreadsheets, statements, exports, PDFs, or other file formats.
SaasAnt can support several parts of the bookkeeping process.
During onboarding, an accountant may need to import:
Customers.
Vendors.
Products and services.
Chart of accounts information.
Open invoices.
Open bills.
Payments.
Historical transactions.
Journal entries.
Bank or credit card activity.
SaasAnt can help prepare and import these records in bulk.
The accountant must still decide the correct import order, confirm opening balances, review dependencies between transactions, and reconcile the completed records.
A bookkeeper may receive the same file every week or month.
Examples include:
Monthly payroll journals.
Weekly invoice files.
Expense reports.
Client-provided transaction spreadsheets.
Credit card activity.
Intercompany entries.
Branch or location files.
The bookkeeper can save the field mapping and reuse it when later files follow the same structure.
This reduces repeated setup and helps the firm follow a more consistent process.
SaasAnt can help correct supported QuickBooks data when many records contain similar problems.
For example, an accountant may need to update:
Transaction dates.
Account assignments.
Customer or vendor names.
Classes.
Locations.
Memos.
Reference numbers.
Product or service information.
Depending on the transaction type, the user may make the changes through a spreadsheet-based Modify workflow or through Live Edit inside SaasAnt.
Small businesses commonly use SaasAnt when information has already been created in another application or spreadsheet.
Examples include:
Importing invoices created outside QuickBooks.
Uploading an expense spreadsheet.
Adding customers or vendors in bulk.
Importing products and services.
Posting journal entries prepared by an accountant.
Adding older bank or credit card activity.
Correcting incorrectly entered transactions.
Downloading QuickBooks data for review.
A business owner does not need to be an accountant to upload a file. However, someone involved in the process must understand what the transactions represent and where they belong in QuickBooks.
SaasAnt can reduce data entry. It cannot replace accounting knowledge.
Internal accounting and finance teams can use SaasAnt for high-volume and repeatable processes.
Common examples include:
Monthly payroll postings.
Accrual and allocation journals.
Large invoice batches.
Vendor bill imports.
Credit card expense imports.
Class and location corrections.
Data exports for audits or internal reviews.
Bulk changes identified during month-end closing.
Files produced by billing, payroll, inventory, or operational systems.
The main value for these teams is consistency. A recurring file can be mapped, reviewed, and processed using the same workflow each period.
A standard import follows a structured process.
The user connects SaasAnt Transactions Online to the required QuickBooks Online company and authorizes the application.
The connecting user must have suitable QuickBooks permissions. The company should also control which team members can access SaasAnt and which QuickBooks companies they are allowed to manage.
To Know more read this guide: Connect SaasAnt Transactions online with QuickBooks Online
The user selects the required QuickBooks transaction or list type.
Examples include:
Invoice.
Bill.
Journal entry.
Expense.
Customer.
Vendor.
Product or service.
Receive payment.
Selecting the correct entity is important because each entity has its own fields and requirements.
The user uploads the relevant file for importing using file selection or drag and drop method. They can also schedule automatic uploads via email, FTP, Zapier, and local folder automation.
For a standard spreadsheet import, SaasAnt accepts supported file formats and allows the user to select the sheet containing the source data.
Field mapping connects each column in the source file to the matching QuickBooks field.
For example:
Source column | QuickBooks field |
Invoice Date | Transaction Date |
Invoice Number | Invoice Number |
Customer Name | Customer |
Item | Product or Service |
Quantity | Quantity |
Unit Price | Rate |
Department | Class or Location |
SaasAnt can map fields automatically when the file headings match recognizable QuickBooks fields. Users can review and adjust the mapping manually.
The mapping should be checked carefully before the data is submitted.
To Know more read this guide: How does Field mapping work in SaasAnt Transactions Online
The review stage gives the user an opportunity to inspect how SaasAnt has interpreted the file.
The user can check:
Mapped fields.
Dates.
Amounts.
Customer and vendor names.
Accounts.
Products and services.
Multi-line transaction grouping.
Classes and locations.
Required information.
Errors identified before submission.
The review process can identify structural problems. It cannot confirm that every accounting decision is correct.
SaasAnt displays the results of the job.
Users can review successful and unsuccessful records, correct errors, and verify the created transactions in QuickBooks Online.
A technically successful import should still be checked against the source file and relevant QuickBooks reports.
Current SaasAnt documentation lists the following formats for most QuickBooks Online import workflows:
XLS.
XLSX.
XLSM.
CSV.
TXT.
Google Sheets.
IIF.ย
SaasAnt also supports PDF and image files for selected document-based workflows like receipts and statements. Document support depends on the type of record being processed.
Because file support can vary by entity and workflow, users should check the relevant support article before preparing a large project.
To Know more read this guide: File Format Guidelines for SaasAnt Transactions Online
Current SaasAnt support documentation lists a wide range of QuickBooks Online transactions and lists.
The current list includes:
Invoices.
Receive payments.
Estimates.
Credit memos.
Sales receipts.
Refund receipts.
The current list includes:
Expenses.
Checks.
Bills.
Bill payments.
Purchase orders.
Vendor credits.
Credit card credits.
Pay Down Credit Card transactions.
The current list includes:
Journal entries.
Deposits.
Transfers.
Time activities.
Bank statements.
Credit card statements.
Trial balances.
General ledgers.
Budgets.
Inventory adjustments.
The current list includes:
Customers.
Vendors.
Employees.
Locations.
Products and services.
Chart of accounts.
Not every entity supports every operation. Import, export, Modify, Live Edit, Delete, and Undo availability can differ by record type.
Users should confirm the required entity and operation in the current application or its specific support article.
To Know more read this guide: Supported QuickBooks Online Transactions and Lists By SaasAnt Transactions Online
Yes. SaasAnt can process supported transactions that contain several detail lines.
A single invoice, for example, may contain several products or services. The source file can use several rows for the invoice while repeating an identifying value such as the invoice number.
SaasAnt uses the reference or transaction number to group the lines into one transaction.
The identifying values must remain consistent. If rows that belong to one transaction use different reference numbers, SaasAnt may treat them as separate transactions.
Yes. Users can import their own supported spreadsheet instead of using a SaasAnt template.
SaasAnt also provides sample templates that show the available fields and a suitable file structure.
A template is useful when creating a new workflow. A custom file may be more suitable when the data is already produced by another business system.
In either case, the user must map the source columns to the required QuickBooks fields.
Video Tutorial for How to Import Data into QuickBooks Online using SaasAnt Transactions Online:
Yes. Mappings can be saved and reused when later files follow the same structure.
For example, a monthly payroll file may always contain:
Date.
Account.
Debit.
Credit.
Memo.
Department.
After these columns have been mapped once, the mapping can be reused for later payroll files with the same structure.
The mapping should be reviewed when the source file changes. A renamed, removed, or newly added column can affect the result.
SaasAnt includes an Auto Create List Entities setting for supported imports.
When enabled, it can create missing customers, vendors, products, or services based on the source data instead of rejecting the related transaction immediately.
This setting should be used carefully.
Differences in spelling, spacing, or naming may create a new record when the user intended to use an existing one. Users should review source names and matching settings before enabling automatic creation for a large file.
Yes. SaasAnt provides customization rules that can change or control source data during supported workflows.
Documented rule actions include:
Setting a value when a field is empty.
Overriding a value.
Merging fields.
Skipping rows that meet selected conditions.
Rules can be used to:
Apply a default account.
Set a class or location.
Combine source information into a description.
Replace an inconsistent value.
Exclude records that should not be imported.
Rules should be tested with a small file before they are applied to a recurring or high-volume workflow.
Yes. SaasAnt provides two main editing methods for supported data.
Modify is a spreadsheet-based workflow.
The user:
Exports existing data.
Changes the required fields in the exported file.
Uploads the file through Modify.
Maps and reviews the fields.
Submits the updates to QuickBooks.
Modify is suitable when many records need to be changed or when the corrections need to be reviewed in a spreadsheet.
Live Edit allows users to search for supported QuickBooks data and update available fields directly in a grid inside SaasAnt.
Live Edit is suitable for quicker corrections that do not require a separate spreadsheet.
The records and fields available for editing depend on the selected entity.
Video Tutorial for How to Edit Data in QuickBooks Online using SaasAnt Transactions Online:
Yes. SaasAnt can export supported QuickBooks Online transactions and lists into Excel or CSV files.
Users can select the transaction or list type, apply available date or search filters, and download the results.
Exports can support:
Accounting reviews.
Audit preparation.
Data analysis.
Cleanup work.
Spreadsheet-based modifications.
Record retention outside the application.
Moving selected data into another supported QuickBooks company.
An export contains the selected records and available fields. It should not automatically be treated as a complete QuickBooks company backup.
Video Tutorial for How to Export Data from QuickBooks Online using SaasAnt Transactions Online:
SaasAnt can help move supported lists and transactions between QuickBooks Online companies.
A typical workflow is:
Export the required data from the source company.
Connect SaasAnt to the destination company.
Import the exported files in the required order.
Review the records in the destination company.
Compare balances and reports.
Recent SaasAnt export documentation confirms that files exported for supported entities can be used with SaasAntโs import workflow in another QuickBooks Online company.
This should be treated as a supported data-transfer workflow, not as a complete company-file migration service.
The user is responsible for determining:
Which records must be moved.
The correct import sequence.
Which settings or relationships are not included in the files.
Whether the destination company already contains overlapping data.
Whether balances and reports match after the transfer.
Yes. SaasAnt provides a Delete workflow for supported QuickBooks Online records.
Users can search for records using available criteria, review the results, and submit the deletion.
Bulk deletion should be approached carefully.
Before deleting anything, users should confirm:
The connected QuickBooks company.
The transaction type.
The selected date range.
The records returned by the search.
Whether the records are linked to other transactions.
Whether an export should be retained first.
A deletion itself may not be reversible. Users should not assume that every deleted record can be restored through SaasAnt.
Video Tutorial for How to Delete Data in QuickBooks Online using SaasAnt Transactions Online:
SaasAnt provides Undo options for supported jobs and workflows.
Users can locate a completed import job on the dashboard and use Undo to remove records created by that job. Some edit workflows also provide an Undo option.
Undo availability depends on:
The operation performed.
The transaction type.
The status of the job.
The current product workflow.
Undo should not be presented as a universal replacement for careful review or data protection.
Users should check whether Undo is available before processing a large job.
SaasAnt supports document-based workflows for selected financial documents.
Current documentation includes workflows for uploading items such as receipts and bank statements, extracting available fields or transaction lines, reviewing the extracted information, and syncing approved data to QuickBooks Online.
The review step is important because a document may contain:
Unclear text.
A missing field.
An incorrectly read number.
A vendor that does not match.
A transaction that already exists.
An account that requires user selection.
Document extraction reduces retyping. Users should still confirm the extracted data before posting it.
Yes. SaasAnt can help bring missing bank-statement transactions into QuickBooks Online for catch-up bookkeeping.
Users can upload a supported bank statement, review the extracted lines, and create the corresponding transactions in QuickBooks based on the statement data. Depending on the transaction, SaasAnt may create records such as expenses, checks, deposits, or transfers using the available description, amount, date, and mapping details.
However, these transactions do not appear in the QuickBooks Banking or Bank Transactions screen as downloaded bank-feed entries.
This means users will not receive the usual bank-feed workflow where they can review, match, add, or categorize each downloaded transaction from the Banking screen. SaasAnt creates the accounting transactions directly in QuickBooks based on the reviewed statement data.
This workflow is mainly intended for:
Catch-up bookkeeping.
Older periods that are no longer available through the bank feed.
Accounts with incomplete bank-feed history.
Bringing statement activity into QuickBooks from a file.
Reconstructing missing accounting records.
After importing the transactions, the user should still:
Check for duplicates.
Review the accounts and transaction types used.
Confirm transfers and payments.
Compare the imported totals with the statement.
Complete the bank reconciliation in QuickBooks.
SaasAnt helps create the missing transactions. It does not place them in the QuickBooks bank-feed review screen or complete the reconciliation.
Video Tutorial for ๐จ๐ฝ๐น๐ผ๐ฎ๐ฑ ๐ฃ๐๐ ๐๐ฎ๐ป๐ธ ๐ฆ๐๐ฎ๐๐ฒ๐บ๐ฒ ๐ป๐๐ ๐๐ผ ๐ค๐๐ถ๐ฐ๐ธ๐๐ผ๐ผ๐ธ๐ ๐ข๐ป๐น๐ถ๐ป๐ฒ:
Credit card statement import follows a similar process.
Users can upload a supported credit card statement, review the extracted activity, and create the corresponding transactions in QuickBooks. Based on the available statement information and user mappings, SaasAnt may create records such as credit card expenses, charges, credits, or payments.
The imported activity does not appear in the QuickBooks Banking or Bank Transactions screen as downloaded credit card-feed entries.
Users will not use the normal feed workflow to match or categorize those records after import. SaasAnt creates the transactions directly in the credit card account based on the reviewed statement data.
This workflow is useful for:
Catch-up bookkeeping.
Older credit card periods.
Missing or incomplete credit card feeds.
Importing card activity from statements.
Rebuilding historical credit card records.
After the import, users should review the created transactions, check for overlap with existing records, compare the account activity with the statement, and complete the credit card reconciliation in QuickBooks.
Quick Create, previously called Batch Transactions, allows users to create several supported QuickBooks transactions directly inside SaasAnt without first uploading a file.
It is useful when the user has data in a spreadsheet but does not want to save and upload it as a separate import file.
Users can:
Open Quick Create in SaasAnt.
Select the required QuickBooks transaction type.
Use the SaasAnt Quick Create template.
Arrange the spreadsheet data using the same columns and structure.
Copy the rows from the spreadsheet.
Paste them directly into the SaasAnt Quick Create screen.
Review the values.
Submit the transactions to QuickBooks.
Copying and pasting works best when the spreadsheet and the SaasAnt Quick Create grid follow the same template and column order.
Quick Create can be useful for:
Entering a small or medium batch of transactions.
Copying prepared data directly from Excel.
Creating transactions without uploading a separate file.
Posting adjusting or recurring entries.
Entering records that were missed from an earlier batch.
The supported transaction types, fields, and current entry limits can vary. Users should confirm the available options in the current SaasAnt interface before preparing a large batch.
Yes. SaasAnt supports recurring import workflows through sources such as:
Email.
FTP or SFTP.
Zapier.
Local folder
Google Drive files can also be routed through a Zapier workflow documented by SaasAnt.
A recurring workflow normally involves:
Selecting the file source.
Choosing the QuickBooks company and entity.
Mapping the file.
Configuring any required rules.
Testing the workflow.
Monitoring later jobs.
Automation works best when the incoming file uses a consistent format. Users should review job results because a file can be received successfully while individual transactions still return errors.
Video Tutorial for integrating Zapier with QuickBooks Online using SaasAnt Transactions Online:
Video Tutorial for Email integration with QuickBooks using SaasAnt Transactions Online:
Video Tutorial for How to Automate QuickBooks Data Entry using SaasAnt Transactions Online:
The difference is mainly the accounting platform they connect to.
SaasAnt Transactions Online | SaasAnt Transactions Desktop |
Connects to QuickBooks Online or Xero | Connects to QuickBooks Desktop |
Runs as an online application | Requires the Desktop application to be installed |
Supports cloud-based connection and automation workflows | Works with an open QuickBooks Desktop company file |
Uses the fields and operations supported by QuickBooks Online or Xero | Uses the fields and operations supported by QuickBooks Desktop |
Both versions support bulk accounting-data operations, but their supported entities, mappings, automation methods, and product interfaces can differ.
Users should always follow documentation for the correct version.
The main difference is where the data comes from.
SaasAnt Transactions is suitable when the source data is in:
Excel.
CSV.
Text files.
IIF files.
Google Sheets.
Supported PDFs or images.
Existing QuickBooks records.
Recurring files received through an automation source.
The user maps the available source data to QuickBooks or Xero fields.
PayTraQer is suitable when the source is a supported:
Payment processor.
Ecommerce platform.
PayTraQer connects to the platform and brings supported payment, sales, fee, refund, and related transaction information into QuickBooks or Xero.
A Shopify seller with a prepared spreadsheet may use SaasAnt Transactions. A Shopify seller who wants to connect the store or payment platform directly would normally consider PayTraQer.
SaasAnt publishes information about its product, network, application, and data-security controls.
Its current security page describes controls and practices related to:
Permissions and authentication.
Credential protection.
Encryption.
Network segmentation.
Firewalls.
Restricted system access.
Monitoring and audit logs.
Backups.
Vulnerability scanning.
Customer-data separation.
GDPR and SOC 2 alignment.
Businesses with formal legal, privacy, or security requirements should review the current security, privacy, and terms pages before connecting production accounting data.
SaasAnt Transactions Online uses subscription plans.
Plans vary based on factors such as:
Number of connected companies.
Number of users.
Monthly credits.
File line limits.
Automation allowances.
Included product features.
Single-company plans are intended for businesses or teams managing one company. Multi-company plans are intended for accountants, bookkeepers, and organizations managing several QuickBooks companies.
Credits measure usage inside SaasAnt Transactions Online.
Different operations can use credits differently. Current documentation separates usage for actions such as:
Import and Modify.
Export.
Delete.
Live Edit.
Reports.
Document parsing.
Bank-statement parsing.
Users can review usage in the Credit Usability Log.
Because credit rules can change, users should check the current credit guide and pricing page when estimating the plan required for a large or recurring workflow.
SaasAnt currently provides a trial for new SaasAnt Transactions Online users.
The current trial duration, included credits, and processing limits are listed on the live pricing and support pages.
A first import should use a small sample file.
A safe process is:
Connect the correct QuickBooks company.
Select one transaction type.
Use a file containing only a few records.
Map every required field.
Review the source rows.
Submit the sample.
Open the resulting transactions in QuickBooks.
Compare the records with the source file.
Review the related QuickBooks reports.
Confirm how errors or unwanted records can be corrected.
Once the sample produces the expected result, the user can process a larger batch.
SaasAnt Transactions Online is likely to be useful when:
Accounting data already exists in a file or supported document.
Many records need to be imported.
QuickBooks data needs to be exported in a structured format.
Existing transactions need the same type of correction.
A recurring file needs to be processed.
An accountant manages several client companies.
Historical transactions need to be added.
Supported data needs to be moved between QuickBooks companies.
Manual entry is taking too much time.
It may not be the right fit when:
Only a few transactions need to be entered.
The required entity or field is unsupported.
The user expects a full accounting system.
The user wants accounting decisions made without review.
The source data is incomplete or unreliable.
A direct ecommerce or payment connection would be better handled through PayTraQer.
SaasAnt Transactions Online helps businesses, accountants, and bookkeepers import, export, edit, delete, and automate supported accounting data in QuickBooks Online and Xero.
It is designed to reduce repetitive data entry while giving users control over mapping, review, correction, and verification.
The application handles the data work. The user remains responsible for the accounting decisions and the accuracy of the final books.