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 QBO to Fusion Operations.
Supported Actions
Below are presented the possible tested options to configure from QBO to Fusion Operations.
From QBO | Action | To Fusion Operations |
Invoice | create | Sales Order |
Invoice | create | Ship |
Invoice | create | Job/Production Order |
Purchase Order | create | Purchase Order |
Estimate | create | Sales Order |
Bill | create | Purchase Order |
Integration settings
All entities are automatically transferred from QBO to Fusion Operations and it is not possible to transfer them manually. The system provides additional configuration options on this page, which are described below.
Start Entity: Bill
When transferring a Bill from QBO a purchase order can be created in Fusion Operations. The available configurations are described below:
Quickbooks Item Line Description: Used to identify and create the product information in Fusion Operations end entity.
Product Name: If selected, the name of the product that will be created/identified in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Empty: If selected, the code of the product that will be created in Fusion Operations will have the value of the QBO's item "Description" field.
Ignore Category Names on products import: If selected, categories that may be configured at the QBO's item level will be ignored. Example: The QBO item with the full name "Category:subCategory:itemName" will match a product with the code "itemName". If the product doesn't exist, it will create it.
Use Taxes: Used to populate the taxes field when transferring an order from QBO to Fusion Operations. It can also be inherited from the marketplace where the order was placed. All values configured in QBO will be available for selection in the order's drop-down menu. However, the default value will be the one from the marketplace where the order was imported from.
Start Entity: Invoice
When transferring an invoice from QBO to Fusion Operations three entities can be created on Fusion Operations end: Sales Order, Production Order, and shipping inventory movement. The available configurations are described below:
End Entity: Sales Order
Quickbooks Item Line Description: Used to identify and create the product information in Fusion Operations end entity.
Product Name: If selected, the name of the product that will be created in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Empty: If selected, the code of the product that will be created in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Ignore Category Names on products import: If selected, categories that may be configured at the QBO's item level will be ignored. Example: The QBO item with the full name "Category:subCategory:itemName" will match a product with the code "itemName". If the product doesn't exist, it will create it.
Product Code placeholder: If the product doesn't exist in Fusion Operations the product code identified as the placeholder will be used instead. Note that the product must already exist in Fusion Operations.
Use Taxes: Used to populate the taxes field when transferring an order from QBO into Fusion Operations. It can also be inherited from the marketplace where the order was placed. All values configured in QBO will be available for selection on the order's drop-down menu. However, the default value will be the one from the marketplace where the order was imported from.
End Entity: Production Order
Use Taxes: Used to populate the taxes field when transferring an order from QBO into Fusion Operations. It can also be inherited from the marketplace where the order was placed. All values configured in QBO will be available for selection in the order's drop-down menu. However, the default value will be the one from the marketplace where the order was imported.
End Entity: Shipping Movement
Quickbooks Item Line Description: Used to identify and create the product information in Fusion Operations end entity.
Product Name: If selected, the name of the product that will be created in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Empty: If selected, the code of the product that will be created in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Auto Archive Sales Order: This configuration only takes effect if the mapping with the start entity "Estimate" and end entity "Sales Order" is active. Once Fusion Operations receives a new invoice for a previously imported Estimate, Fusion Operations will archive the Sales Orders corresponding to the Estimate (if it is fully fulfilled).
Use Taxes: Used to populate the taxes field when transferring an order from QBO into Fusion Operations. It can also be inherited from the marketplace where the order was placed. All values configured in QBO will be available for selection in the order's drop-down menu. However, the default value will be the one from the marketplace where the order was imported.
Start Entity: Purchase Order
When transferring a purchase order from QBO it is only possible to create a purchase order in Fusion Operations. The available configurations are described below:
Quickbooks Item Line Description: Used to identify and create the product information in Fusion Operations end entity.
Product Name: If selected, the name of the product that will be created in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Empty: If selected, the code of the product that will be created in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Ignore Category Names on products import: If selected, categories that may be configured at the QBO's item level will be ignored. Example: The QBO item with the full name "Category:subCategory:itemName" will match a product with the code "itemName". If the product doesn't exist, it will create it.
Product Code placeholder: If the product doesn't exist in Fusion Operations the product code identified as the placeholder will be used instead. Note that the product must already exist in Fusion Operations.
Use Taxes: Used to populate the taxes field when transferring an order from QBO into Fusion Operations. It can also be inherited from the marketplace where the order was placed. All values configured in QBO will be available for selection in the order's drop-down menu. However, the default value will be the one from the marketplace where the order was imported.
Start Entity: Estimate
When transferring an estimate from QBO it is possible to create a sales order in Fusion Operations. The available configurations are described below:
Quickbooks Item Line Description: Used to identify and create the product information in Fusion Operations end entity.
Product Name: If selected, the name of the product that will be created in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Empty: If selected, the code of the product that will be created in Fusion Operations end entity will have the value of the QBO's item "Description" field.
Ignore Category Names on products import: If selected, categories that may be configured at the QBO's item level will be ignored. Example: The QBO item with the full name "Category:subCategory:itemName" will match a product with the code "itemName". If the product doesn't exist, it will create it.
Product Code placeholder: If the product doesn't exist in Fusion Operations the product code identified as the placeholder will be used instead. Note that the product must already exist in Fusion Operations.
Use taxes: Used to populate the taxes field when transferring an order from QBO into Fusion Operations. It can also be inherited from the marketplace where the order was placed. All values configured in QBO will be available for selection in the order's drop-down menu. However, the default value will be the one from the marketplace where the order was imported.
If after reading this article you still have some doubts, feel free to reach out to us through our Live-chat feature, or directly to your CSM.