This guide is designed to help you evaluate whether integrating your accounting package with Commusoft is the right decision for your business. By carefully following the flowchart and instructions, you will gain a clear understanding of the requirements, steps involved, and manual effort necessary for a successful integration.

This preparation ensures that you:

Have a full understanding of your data.
Are confident in the process and the next steps.
Can make informed decisions tailored to your business needs.

We strongly recommend completing this guide before beginning the integration process to avoid potential errors or disruptions.

Understanding your setup

Follow the steps below in sequence to assess your readiness for accounting integration:

Step 1. Do you have any Customers/Suppliers in your Commusoft account?

👍 If Yes: Go to Step 2.
👎 If No: Skip to Step 3.

Step 2. Do those same Customers/Suppliers already exist in your accounting package?

👍 If Yes: Read Linking Customers/Suppliers, then go to step 3.
👎 If No: Skip to Step 3.

Step 3. Do you have Customers/Suppliers that you want to import from the Accounting Package in to Commusoft?

👍If Yes: Read Field mapping

👎 If No: Go to step 4

Step 4. After answering the previous questions do you wish to proceed with integrating your accounting package with Commusoft?

👍 If Yes: Read Set-up your Accounting Package

👎 If No: No further action is required for the integration at this time.

Account Specific

Xero

Importing contacts from Xero

How are customer types are determined when importing from Xero?

When customers are imported from Xero into Commusoft, they are assigned a designation (a customer, a private company, etc.) depending on how their information is stored within Xero itself.
When a customer is stored with the 'Contact name' section filled in as well as both their first and last names, they will be imported to Commusoft as a private customer. Without this information, however, they will be imported as a company instead.
The following tables should help clarify things. They show the list of the fields listed in Commusoft and the corresponding ones in Xero:

For a New Private Customer:

Name	If the 'Contact Name' is populated but the Primary person is not then it creates in Commusoft as a Private customer.
Surname
Landline	Phone
Email	Email
Address line 1	Postal Address - Address
Address line 2	N/A
Address line 3	N/A
Town	Postal Address - City/Town
County	Postal Address - Country
Postcode	Postal Address - Postal/Zip Code
Email	Email
Title	N/A
Contact first name	N/A
Contact surname	Contact Name
Mobile	Mobile

For a New Company:

Company	If Contact Name and Primary Person both are populated then it creates in Commusoft as Company. The contact name will be the Company name.
Address line 1	Postal Address - Address
Address line 2	N/A
Address line 3	N/A
Town	Postal Address - City/Town
Country	Postal Address - Country
Postcode	Postal Address - Postal/Zip Code
Landline	Phone
Email	Email
County	N/A
Contact first name	Primary Person FN
Contact surname	Primary Person LN
Mobile	Mobile
Landline	Phone

For Suppliers:

Supplier Name	Contact Name
Address line 1	Postal Address - Address
Address line 2	N/A
Address line 3	N/A
Town	City/Town
County	State/Region
Postcode	Post/Zip Code
Landline	Phone
Email	Email

Xero linking categories

See this article: Business units

Quickbooks Desktop Enterprise v24

Supported version

QuickBooks Enterprise v22 and v24.

US and Canada only

Tax descriptions

See this article: Tax descriptions

Importing contacts from Quickbooks desktop

Title field check: If the title field is blank in QuickBooks, Commusoft will assign the first available title from your system settings. (Default: '-')
Customer name limit: Due to QuickBooks limitations, customer names are restricted to 18 characters.

Quickbooks Online

How are customer types are determined when importing from Quickbooks?

When customers are imported from QBO into Commusoft, they are assigned a designation (a customer, a private company, etc.) depending on how their information is stored within QBO itself.
When a customer is stored with the 'Contact name' section filled in as well as both their first and last names, they will be imported to Commusoft as a private customer. Without this information, however, they will be imported as a company instead.
The following tables should help clarify things. They show the list of the fields listed in Commusoft and the corresponding ones in QBO:

Sage 50 Accounts

Supported version

Sage 50 Accounts version 27 to 32

Commusoft interface version v1.106

Sage SDO

Sage Data Object (SDO) – Why It’s Needed and What It Does

The Sage Data Object (SDO) is a crucial component for integrating with Sage accounting software. It acts as a bridge, enabling third-party applications—like Commusoft—to interact with Sage data securely and efficiently.

Why is the SDO important?

The SDO allows our system to:

Read and write data to Sage (such as invoices, payments, and customer records)
Ensure seamless syncing between Sage and Commusoft
Provide real-time updates where applicable, improving accuracy and efficiency

Version Compatibility

The SDO version must match the version of your Sage client. If Sage is installed separately (i.e., the client only), you'll need to install the corresponding SDO version manually.

However, if you’ve used Sage’s all-in-one installer—which includes both the Sage client and the SDO—you typically don’t need to install the SDO separately.

Installation and Support

To confirm what version you have or to get help with installation, please contact Sage support directly. They can provide guidance based on your specific setup and licensing.

Preparing for Accounting Integration