Autodesk Fusion Operations allows you to integrate with Quickbooks online. This integration is a connection between the two applications that work together to share data among them. In this article, you can see which data flows and triggers are available from Fusion Operations to QBO.
Supported Actions
Below are presented the possible options to configure from Fusion Operations to QBO.
From Fusion Operations | Action | To QBO |
Receiving | create | Bill |
Shipping | create | Invoice |
Inventory | update | Inventory |
Purchase Order | create | Purchase Order |
Purchase Order | create | Bill |
Sales Order | create | Sales Receipt |
Sales Order | create | Invoice |
Sales Order | create | Estimate |
Integration settings
All entities above can be transferred manually, by selecting the button "Manually" on the integrations page, or automatically, by selecting the button "Automatically" (except for the inventory update). To reach this page press here.
The system provides additional configuration options in the Edit button under the Advanced fields, which are described below.
Start Entity: Sales Order
When transferring a sales order from Fusion Operations to QBO three entities can be created on QBO end: Estimate, Invoice, and Sales Receipt. All of them share the configurations below:
Quickbooks document Number: Definition of how the document number will be generated in QBO.
Sequential Number Generated By Quickbooks: The document number will be generated considering the last "NO" in QBO. The code in Fusion Operations will be disregarded.
Order Code: The Fusion Operations sales order code will be the document number of the end entity in QBO.
If left empty: it will have the following behaviors considering the end entity:
Estimate and Sales Receipt: It will use the Sales order code.
Invoice: It will use the "Sequentially generated index".
Prefix: The value identified in this field will be added (as a prefix) to the number of the generated document.
Auto Increment: When activated, an incremental suffix index will be added to the document number of the end entity in QBO.
Customer Match By: The customer field of Fusion Operations (identified below) will be used to match or create a customer in QBO, populating the field "NAME".
Billing Address Name: If this option is selected, the Fusion Operations billing address name, will populate the name of the new customer created in QBO.
Name: If this option is selected, Fusion Operations customer name, will populate QBO name of the new customer created.
Code: If this option is selected, Fusion Operations customer name, will populate QBO code of the new customer created.
Create Missing Customer: If the customer does not exist in QBO, a new one will be created considering the option selected in "Customer Match By".
Quickbooks Service Item Name: This configuration will only affect shipping products with no product associated (e.g. Discounts). The name of the line item will match the selected option.
Fixed Value: If selected, a new line with the value identified will be created.
Shipping/Receiving product observations: If selected, a new line with the value identified in the product's sales order description will be added.
If left empty: same as option above.
Save Fusion Operations Entity Code to Quickbooks Custom Fields: The value on the field "Name of the Custom field" will be populated with the code of the entity that's being transferred. Note that the "Name of the Custom field" needs to match the custom field on QBO end.
Save Fusion Operations Custom Fields to QB Custom Fields: It is used to transfer data from Custom Fields in Fusion Operations to corresponding Custom Fields in QBO. After selecting this option, you should identify the custom field name in QBO (QuickBook Custom Field 1) and its corresponding one in Fusion Operations (Fusion Operations Custom Field 1). Note that the field names are case-sensitive.
Use Taxes: Used to populate the taxes field when transferring an order from Fusion Operations into QBO. It can also be inherited from the marketplace where the order was placed.
For the invoice entity, two additional configurations are available:
Allow Online Bank Transfer Payment: Specifies if the invoice can be paid with online bank transfers and corresponds to the "Free bank transfer" online payment check box on the QBO end.
Allow Credit Card Payment: Specifies if online credit card payments are allowed for the invoice and correspond to the "Cards" online payment check box on the QBO end.
Start Entity: Purchase Order
When transferring a Purchase order from Fusion Operations to QBO two entities can be created in QBO end: Bill and Purchase Order. Note that not all options mentioned below are available when creating a Bill.
Quickbooks Document Number: Definition of how the document number will be generated in QBO. By default, if left empty, it will use the purchase order code.
Sequential Number Generated By Quickbooks: The document number ("NO") will be generated considering the last "NO" in QBO. The code in Fusion Operations will be disregarded.
Order Code: The Fusion Operations purchase order code will be the document number ("NO") of the end entity.
PreFix: The value identified in this field will be added (as a prefix) to the number of the generated document.
Auto Increment: When activated, an incremental suffix index will be added to the document number of the end entity in QBO.
Quickbooks Item Line Description: Used to define the field in Fusion Operations that is going to populate the item line "Description" field in the QBO end entity.
Product Name: If selected, the Fusion Operations product name will populate the item line "description" field in QBO end.
Product Observations: If selected, fusion operations observations will populate the item line "description" field in QBO end.
Empty: If left empty, the receiving product observation will populate the item line "description" field in QBO end.
Supplier Match by: Identifies the Fusion Operations supplier field that will have to match supplier "Name" in QBO.
Code or Empty: If selected, the supplier code in Fusion Operations must match the supplier name in QBO.
Name: If selected, the supplier name in Fusion Operations must match the supplier name in QBO.
Save Fusion Operations Entity Code to Quickbooks Custom Field: Fusion Operations Purchase order code will be stored in the identified QBO Custom Field.
Use Taxes: Used to populate the taxes field when transferring an order from Fusion Operations into QBO. It can also be inherited from the marketplace where the order was placed.
Start Entity: Receiving
When doing a receiving in fusion operations a Bill can be created in QBO. The available configurations are described below:
Quickbooks Document Number: Definition of how the document number will be generated in QBO. By default, if left empty, it will use the purchase order code.
Sequential Number Generated By Quickbooks: The document number ("NO") will be generated considering the last "NO" in QB. The code in fusion operations will be disregarded.
Order Code: The fusion operations purchase order code will be the document number of the end entity.
Supplier Match by: Identifies the fusion operations supplier field that will have to match supplier "Name" in QBO.
Name: If selected, the supplier name in fusion operations must match the supplier name QBO.
Code or Empty: If selected, the supplier code in fusion operations must match the supplier name in QBO.
Use Taxes: Used to populate the taxes field when transferring an order from Fusion Operations into QBO. It can also be inherited from the marketplace where the order was placed.
Start Entity: Inventory
Allows the update of inventory in QBO, by selecting the button "Send All Inventory to QuickBooks" in the inventory menu.
The available configurations are described below:
Only Sync the inventory for products marked with the Quickbooks tag: If selected, it will only be possible to update inventory on items that have this specific tag activated. Please contact support if you do not know how to check this.
Custom field to match Quickbooks item: When trying to match the Fusion Operations product with the Quickbooks item it will first check if the product (in Fusion Operations) has a custom field populated with the identified value and try to match it with the product name in QBO. If the custom field is not filled, the Fusion Operations code will be used instead.
Start Entity: Shipping
When shipping in fusion operations an Invoice can be created in QBO. The available configurations are described below:
Quickbooks Document Number: Definition of how the document number will be generated in QBO.
Sequential Number Generated By Quickbooks: The document number will be generated considering the last "NO" in QBO. The code in Fusion Operations will be disregarded.
Order Code/Empty: The Fusion Operations sales order code will be the document number of the end entity in QBO.
Prefix: The value identified in this field will be added (as a prefix) to the number of the generated document.
Auto Increment: When activated, an incremental suffix index will be added to the document number of the end entity in QBO.
Quickbooks item Line Description: Used to define the field in Fusion Operations that is going to populate the item line "Description" field in the QBO end entity.
Product Name: If selected, Fusion Operations product name will populate the item line "description" field in QBO end.
Product Observations: If selected, Fusion Operations observations will populate the item line "description" field in QBO end.
Empty: If selected, Fusion Operations product code will populate the item line "description" field in QBO end.
Save Fusion Operations Entity code to quickbooks custom field: Fusion Operations entity code will be stored in the identified QBO Custom Field.
Save Fusion Operations custom fields to QB custom Fields: It is used to transfer data from Custom Fields in Fusion Operations to corresponding Custom Fields in QBO. You should identify the custom field name in QBO (QuickBook Custom Field 1) and its corresponding one in Fusion Operations (Fusion Operations Custom Field 1). Note that the field names are case-sensitive, and you can save up to 3 custom fields.
Allow Online Bank Transfer Payment: Specifies if this invoice can be paid with online bank transfers and corresponds to the "Free bank transfer" online payment check box on the QBO end.
Allow Credit Card Payment: Specifies if online credit card payments are allowed for this invoice and correspond to the "Cards" online payment check box on the QBO end.
Use Taxes: Used to populate the taxes field when transferring an order from Fusion Operations into QBO. It can also be inherited from the marketplace where the order was placed.
FAQ:
1. Why is my QBO end entity not respecting the incremental counting of the last document number?
The setting below needs to be activated in QBO:
