<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}</style><p id="isPasted"><strong>In this guide we will cover:</strong></p><p><strong>- What is the Sage Intacct Integration?</strong></p><p id="isPasted"><strong>- Connecting to Sage</strong></p><p><strong>- Tax Rates</strong></p><p><strong>- Accounts</strong></p><p><strong>- Importing Customers</strong></p><p><strong>- Importing Products</strong></p><p><strong>- Supplier Import</strong></p><p><strong>- Currency </strong></p><p><strong>- Syncing Invoices, Credit Notes, Bills, Purchase Orders, and Sales Orders</strong></p><p><strong>- Syncing Projects</strong></p><p><strong>- Syncing with Sage Intacct </strong></p><p><strong>- Integrating when using Multi-Entity Distributed (MED) or Multi-Entity Shared (MES) mode on Intacct</strong></p><p><br></p><p><br></p><p><strong><span style="font-size: 14pt;">What is the Sage Intacct Integration?</span></strong></p><p>The Sage Intacct integration allows you to sync invoices, purchase orders, credit notes and bills from Halo to Sage Intacct, allowing you to leverage both platforms in your billing procedures for effective automation. As part of the integration customer, product, supplier and tax rates data can be imported into Halo from Sage. When updates are made to certain entities in Halo, these updates will be pushed over to Sage almost instantly. The integration also supports Multi-Entity Distributed (MED) or Multi-Entity Shared (MES) mode on Intacct as well as multi-currency setups. In this guide we will cover how to connect to and set up the integration as well as what to expect when syncing each type of entity. </p><p><br></p><p><strong><span style="font-size: 14pt;">Connecting to Sage</span></strong></p><p id="isPasted">You will first need to enable the integration module, head to Configuration > Integrations and enable the Sage Intacct integration using the '+' icon. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImVhMWM1YmRiLWI3MDMtNDM1NC1hYzlmLWU4ZjVmN2M0Mjc5YyJ9.ygaSfYwK7kahcua8pBgOFxm-ZMv0LEvDf_nWS5MhYhU" class="fr-fic fr-fil fr-dib" width="168" style="width: 170px; height: 158.75px;" height="159"></p><p><strong><span style="font-size: 10pt;">Fig 1. Enable integration module</span></strong></p><p><br></p><p>Once enabled click into the module to begin configuration. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjU4NTNiOWYyLTVjZmItNGQ4ZS04NmQ0LWJlODkxZjc2M2EzZCJ9.ZsJujIWV7B0FCtM98UPTnT1KCvEt-FEr0ofkwDbHtwY" class="fr-fic fr-fil fr-dib" width="939" style="width: 941px; height: 673.765px;" height="674"></p><p><strong><span style="font-size: 10pt;">Fig 2. Sage Intacct connection details.</span></strong></p><p><br></p><p>When connecting you can either use your own sender credentials or our Halo credentials. In order to use your own sender credentials you will need a developer licence from Sage. If you would like to use the Halo sender credentials simply enable 'Use Halo's Sender Credentials'. </p><p><br></p><p style="margin-left: 20px;"><strong>Using Halo Sender credentials </strong></p><p style="margin-left: 20px;">When Halo credentials are enabled you will need to have the integration activated by our support team before you can connect. You can reach our support team at <a data-fr-linked="true" href="mailto:support@halopsa.com" data-pasted="true">support@halopsa.com</a>/<a data-fr-linked="true" href="mailto:support@halopsa.com" data-pasted="true">support@haloitsm.com</a>/<a data-fr-linked="true" href="mailto:support@halopsa.com" data-pasted="true">support@halocrm.io</a> once enabled you can continue setup. </p><p style="margin-left: 20px;"> </p><p style="margin-left: 20px;">When connecting using Halo's sender credentials you will need to create a web services authorization in Sage Intacct and enter Halo's sender ID (HaloMPP) and give the connection a name. To create a web services authorisation in Sage head to Company > Configuration > Company > Security > Web Services Authorizations > Add > Use 'HaloMPP' as the Sender ID.</p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;">Adding a web services authorization allows you to use the regular username and password to authenticate the Intacct integration and test the credentials.</p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;"><strong><span style="font-size: 12pt;">Using Own Credentials</span></strong></p><p style="margin-left: 20px;"><strong>Sender ID</strong> - Here enter your developer licence ID, Sage will provide this to you upon obtaining a developer licence. </p><p id="isPasted" style="margin-left: 20px;"><strong>Sender password - </strong>Here enter the password for your Sage developer account Sage will provide this to you upon obtaining a developer licence. </p><p><br></p><p><strong>Company ID</strong>: The ID of your company in Intacct i.e. CompanyName, if connecting a Sandbox environment it will be followed by -Sandbox i.e. CompanyName-Sandbox</p><p><br></p><p><strong>Username and Password</strong>: The regular user accounts that are used to log into Intacct.</p><p><br></p><p>Once you have entered your credentials you can check connection using the 'Test Credentials' button. </p><p><strong><br></strong></p><p><strong>Use AP Invoices instead of Purchasing Transactions</strong> - When enabled the AP Invoices endpoint will be used to post updates to rather than the Purchasing Transactions endpoint. The AP Invoices endpoint is used to when you would just like to post invoice updates to Sage, the update will be posted directly to your accounts payable ledger. Whereas the purchasing transactions endpoint allows you to match invoices to the associated PO in Sage. </p><p><br></p><p><strong>Use AR Invoices instead of Order Entry Transactions</strong> - When enabled the AR Invoices endpoint will be used to post updates to rather than the Order Entry Transactions endpoint. The AR Invoices endpoint is used to when you would just like to post invoice updates to Sage, the update will be posted directly to your accounts payable ledger. Whereas the purchasing transactions endpoint allows you to match invoices to the associated PO in Sage. </p><p><br></p><p><strong><span style="font-size: 14pt;">Tax Rates</span></strong></p><p>Tax rates configuration takes place under the 'Tax Rates' tab.</p><p><br></p><p><span style="font-size: 11pt;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ4NDRkMTM2LTNkNzQtNGQ5Mi1hYjg1LTI1ODcyNjg0YTE4MyJ9.mwHE8E0SfDQKxeXzIvDtmkHb94LLteM1WZGBQnMoyZs" class="fr-fic fr-fil fr-dib" width="1030" style="width: 1032px; height: 347.253px;" height="347"></span></p><p><span style="font-size: 10pt;"><strong>Fig 3. Tax rates setup page</strong></span></p><p><br></p><p>Each Halo tax rate will need to be mapped to a Sage Intacct tax rate. This will determine what tax rate is applied to the line when it is synced over to Sage.</p><p><br></p><p>To map tax rates open up a tax rate in Halo (select 'Edit Tax Rates' > select a rate) then choose which Sage Intacct rate to map to using the 'Sage Intacct Tax Rate' field. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY0ZWEwNGZkLTg5M2ItNDkwZC1iOTljLTBkYWI0YTc1ODQ3NSJ9.qNriTrKhIe55uxof7_TFzKbwvjCXnqg-lrT7vE-J90E" class="fr-fic fr-fil fr-dib" width="691" style="width: 693px; height: 519.186px;" height="519"></p><p><strong><span style="font-size: 10pt;">Fig 4. Map Halo tax rate to Sage tax rate</span></strong></p><p><br></p><p><strong><em>Note: We specify exact tax rate values for syncing so these will take precedence over these set tax rates.</em></strong></p><p><br></p><p><strong>Use the SIG Tax module</strong> - When this is enabled Tax will be calculated by Halo, using the Halo tax rate against the line item. This value will then be synced over to Sage. </p><p><br></p><p><strong>Create a Tax Line rather than in-line Tax values for Taxes marked at Tax level (Invoice-Only) </strong>- When enabled, tax that needs to be added to line items can be added as a new line on the invoice in Sage rather than in-line with the item. This will need to be enabled per tax rate, any items using the tax rates this is enabled for will have tax appear as an additional line, otherwise it will be in line. This only applies to invoices and no other entities. </p><ul><li>When enabled you will need to select an 'Item for new Tax Lines', this will be the item representing the tax line. We recommend creating an item for this with a name/description including 'tax' so it is clear the line is for tax and not an additional item.</li></ul><p><span style="color: rgb(0, 0, 0);"><strong>Default Tax Solution</strong> - This field is used if you are using an external or integrated tax solution to calculate tax. Here you can select the solution you would like to use, when a solution is selected invoices that are synced to Sage will have their tax calculated using this method rather than using the native Sage solution or Halo tax solution.</span><span style="color: rgb(226, 80, 65);"> </span></p><p><br></p><p><strong><span style="font-size: 14pt;">Accounts</span></strong></p><p>Accounts codes from Sage Intacct can be imported into Halo under the 'Accounts' tab, however, these are not required to be imported. </p><p><br></p><p>When using the Sage Intacct integration the account code (GL account) for a line item will be calculated when the invoice/purchase order is synced over to Sage. Sage Intacct determines the accounts code of a line item based on various criteria such as the GL item group, item category etc. (depending on your Sage Intacct configuration). Therefore, you do not need to assign an income/expense account to the item/item group in Halo for the line to sync successfully. When the Sage Intacct integration is enabled you will no longer see the fields 'income account' and 'expense account' against the item or item group as these do not need to be set. </p><p><br></p><p>Importing accounts codes is legacy functionality, therefore you can still import Sage Intacct accounts codes into you Halo for reference purposes. </p><p><br></p><p><strong><span style="font-size: 14pt;">Importing Customers</span></strong></p><p>Customers can be imported from Sage into Halo under the 'Customers' tab. When importing clients Sage clients will attempt to match to an existing Halo customer based on name, if the names are an exact match data from the Sage customer will update the associated Halo customer record. If no name match can be made a new customer will be created in Halo. </p><p><br></p><p>Following a customer import, customers in Halo that have been created from/matched to a Sage customer will have their Sage Intacct accounts ID assigned to them. Customer accounts ID can be used to match the Halo and Sage customer for future imports/syncs, allowing you to change the customer name if needed. </p><p><br></p><p><strong><em>Note: When syncing back from Halo to Sage, the delivery address will not sync back due to limitations in the Sage Intacct SDK provided.</em></strong></p><p><br></p><p>If you have top level functionality enabled, you will also be able to select which Top Level customers created from a Sage import are created under using the 'Top Level for Customers' field. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ4YjJmMTczLWNmOGItNDY5OC1iNmQ3LWQwNTkwMzI0YjU5NCJ9.iE1ko3CPRxKP73WOiSMo7ownKbuEOpOs0ZywwzEs0S4" class="fr-fic fr-fil fr-dib" width="1323" style="width: 1325px; height: 395.037px;" height="395"></p><p><strong><span style="font-size: 10pt;">Fig 5. Top Level for Customers created from Sage</span></strong></p><p><br></p><p><strong>Default Entity to Save to -</strong> Here, set the default Sage Entity you would like new customers to be saved to. This can be overridden per customer (under the "Billing" tab within the customer). </p><p><br></p><p>When syncing clients to Sage we sync the following properties: accounts id, active, taxable, accounts first name, accounts last name, accounts email address, customer name, address, Tax code and default currency. </p><p><br></p><p><strong><span style="font-size: 14pt;">Importing Products</span></strong></p><p>Products/items can be imported from Sage into Halo, under the 'Products' tab. Any items import from Sage will have their Sage Intacct ID stored against them in Halo. This ID can be used to match the Halo item to the Sage item for future syncs. </p><p><br></p><p>Before importing products you will need to import Item GL Groups from Sage Intacct, these will be created as item groups in Halo. This will determine which Halo item group items are created under when importing from Sage. </p><p><br></p><p>You will also need to complete the fields on the product import page prior to import. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM5MDllYTM1LTkwNTUtNDZiNC04MWIzLTRmYTNmY2ViYWFhMCJ9.jAYMhw9ViZvtyDSZy7erS8OYeCnykqeGWN6GhcKsnAg" class="fr-fic fr-fil fr-dib" width="1408" style="width: 1410px; height: 517.236px;" height="517"></p><p><strong><span style="font-size: 10pt;">Fig 6. Product Import setup page</span></strong></p><p><br></p><p data-pasted="true"><strong>Default Entity to Save to -</strong> Here, set the default Sage Entity you would like new products created in Halo to be saved to in Sage. This can be overridden per product (under the "Billing" tab within the product). Only applicable when using Multi-Entity Distributed (MED) or Multi-Entity Shared (MES) mode on Intacct.</p><p><br></p><p><strong>Intacct Item type when manually creating an item</strong> - Here choose the Intacct item type that an item will be created as in Sage when a product has been manually created in Halo and this product is synced to Sage. This can be overridden against the Halo product group the product in Halo itself. This will only be applicable if you have enabled product sync (under the 'Syncing with Sage Intacct' tab).</p><p><br></p><p><strong>Intacct Item type when Items are created by other integrations</strong> - Here choose the Intacct item type that an item will be created as in Sage when a product has been created in Halo by another integration, and this product is synced to Sage. This can be overridden against the Halo product group the product in Halo itself. This will only be applicable if you have enabled product sync (under the 'Syncing with Sage Intacct' tab). </p><p><br></p><p><strong>Default Product Group</strong> - Here choose a default Halo product group, this is the group that items will be created under in Halo if the Sage item does not belong to a GL group, or the GL group has not been matched to a Halo item group. </p><p><br></p><p>To import GL item groups and items use the respective buttons on the configuration page in Halo. </p><p><br></p><p>When importing items, Sage items will attempt to match to a Halo item based on the item name and Sage Intacct ID. Sage Intacct ID will always be matched first, if no match can be found name will be used to match. If there is a Halo item with the exact same name as the Sage Intacct item these items will match upon import and the Halo item will have the associated Sage Intacct ID assigned. </p><p><br></p><p><strong><em>Note: Name matching will only be used when importing items. When syncing items from Halo to Sage the item must have a Sage Intacct ID in order to sync successfully. </em></strong></p><p><br></p><p>Imported items will have the Sage Intacct item type and Product Line details imported too. These will be fields against the item so any manually created products in Halo can have these fields set too. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImE1OGFjNjc1LTY4ZjEtNDNlYy04YzZmLTcwYmUyMDM5YWE5ZSJ9.aTzkrMalX53P4s2IWkJYIE82I6243A6EABKR81EwsEw" class="fr-fic fr-fil fr-dib" width="626" style="width: 628px; height: 473.457px;" height="473"></p><p><strong><span style="font-size: 10pt;">Fig 7. Sage Intacct item type and product line fields</span></strong></p><p><br></p><p><span style="font-size: 11pt;">The Sage Intacct item type and product line can be set against product groups in Halo, allowing these values to be defaulted at group level. This means any products created in Halo will automatically have their item type and product line set in line with the item group they belong to. These will be the item type and product line used for the item that is created in Sage Intacct, unless this is overridden on the item level. <br></span></p><p><br></p><p>Once you have imported your items and item GL groups check the Halo item groups that have been created are associated to the correct item GL group. Do this under products > view products by group > right click on a group > Billing tab > see 'Intacct Item GL Group'. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjFmN2NkZTNmLTdiNDItNGE0NS04MTEwLWRlMTZhYWEwODU5OSJ9.M_ufcuU3cQqQWwS4Cb87WaviOgjcjStJSHNlinNa_1g" class="fr-fic fr-fil fr-dib" width="771" style="width: 773px; height: 554.182px;" height="554"></p><p><strong><span style="font-size: 10pt;">Fig 8. Intacct Item GL Group associated to Halo item group</span></strong></p><p><br></p><p><strong><em>Note: This field will be automatically populated upon import. If manually creating a new product group in Halo you will need to populate this field manually. </em></strong></p><p><br></p><p>When items are added to invoices/purchase orders the GL accounts used in Sage will be influenced by the Intacct Item GL group associated to the Halo product group the product is in, in line with Sage Intacct functionality. </p><p><br></p><p><span style="font-size: 14pt;"><strong>Supplier Import</strong></span></p><p>Suppliers can be imported from Sage into Halo under the 'Suppliers' tab. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImIzMGU5MjVkLWFmMjYtNDUxZC05MDk2LTAxZDdkNzAwYjM1NCJ9.sEr19zSk2qAOzp_BmdepfGi_CzTRKTRgkqklINqS0_A" class="fr-fic fr-fil fr-dib" width="1401" height="365"></p><p><strong><span style="font-size: 10pt;">Fig 9. Supplier import</span></strong></p><p><br></p><p data-pasted="true"><strong>Default Entity to Save to -</strong> Here, set the default Sage Entity you would like new suppliers created in Halo to be saved to. This can be overridden per supplier (under the "Settings" tab within the supplier). Only applicable when using Multi-Entity Distributed (MED) or Multi-Entity Shared (MES) mode on Intacct.</p><p><br></p><p>When importing suppliers they will be matched based on name and Sage Intacct Vendor ID. If no supplier can be matched a new supplier will be created in Halo. Suppliers created in Halo by Sage will have a Sage Intacct Vendor ID stored against them. </p><p><br></p><p><strong><span style="font-size: 14pt;">Currency </span></strong></p><p>The use of multiple currencies can be enabled from the 'Currency' tab using the setting 'Use multiple currencies'. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijk0YmY2YjgyLTRkNzAtNDg2NC1hYzc3LWJhMjI3OWM5YzhiNSJ9.LTOwnAtREoIAfdwf8boub36wTyHFPx4aqizqvkT1BMY" class="fr-fic fr-fil fr-dib" width="981" style="width: 983px; height: 365.973px;" height="366"></p><p><strong><span style="font-size: 10pt;">Fig 10. Currency configuration</span></strong></p><p><br></p><p>This should be enabled when you are using multi-currency in Halo. Enabling this will result in Halo's currency conversion being used over Sage's. This means when a Halo invoice is synced to Sage, the currency ISO codes Halo uses will be synced to Sage. Halo's currency conversion will remain and no be overwritten. </p><p><br></p><p>Even if you are not using multi-currency we recommend enabling this setting as this can help prevent schema errors. </p><p><br></p><p><strong><span style="font-size: 14pt;">Syncing Invoices, Credit Notes, Bills, Purchase Orders, and Sales Orders</span></strong></p><p>Invoices, credit notes, purchase orders, and sales orders can be synced to Sage from Halo, this is a one way sync only. </p><p><br></p><p>To configure how data is synced head to the respective configuration tab. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY2ZTJmY2JjLTdlYTktNDIwOS04MTA3LTk1YzVkMTEyZDAzNSJ9.XAu8R_cew0UGx-nLzOuVhPdF7TUuVLtTTUqencpyiX0" class="fr-fic fr-fil fr-dib" width="1313" style="width: 1315px; height: 551.531px;" height="552"></p><p><strong><span style="font-size: 10pt;">Fig 11. Invoices configuration </span></strong></p><p><br></p><p data-pasted="true"><strong>Default Entity to Save to -</strong> Here, set the default Sage Entity you would like new invoices/credit notes, bills and purchase orders to be saved to. This can be overridden per Halo entity. Only applicable when using Multi-Entity Distributed (MED) or Multi-Entity Shared (MES) mode on Intacct.</p><p><br></p><p><strong>Transaction Definition for Invoices/Credit Notes/Bills/Purchase orders</strong> - Here you can choose what transaction definition is used when syncing invoices to Sage. That is, when an invoice in Halo is synced to Sage, what transaction definition will it be created under. </p><p><br></p><p><strong>Use Intacct Simple Tax </strong>- This setting is available under the Invoices tab only. Enable this if you are using Simple Tax in Sage Intacct, otherwise invoices will not sync over. When using Simple Tax tax, tax will be added onto existing Invoice lines when synced across. If you would like tax to be added as a separate line, 'Create a Tax Line rather than in-line Tax values for Taxes marked at Tax level(Invoice-Only)' will need to be enabled, then each tax rate ( in Halo) will need to be set to be added as a separate line. </p><p><br></p><p>Mappings can also be configured for invoices, this will determine which Sage fields data from the Halo invoice is imported to. Mappings can also be configured at the line level to control which Sage fields data from the Halo invoice is imported to. Any fields that are not mapped will not be synced. </p><p><br></p><p>Sage fields can be mapped to certain Halo Custom Fields of the same type. The Custom field must be the same type as the mapping. For example, Invoice Custom Fields can be mapped under the Invoice tab, in the "Field Mappings" section. Similarly, Invoice Line Custom Fields can be mapped in the Invoice tab, however these must be under the "Line Field Mappings" section shown at the bottom of <strong>Fig 11</strong>. "RevRecEndDate", "RevRecStartDate", and "RevRecTemplate" can be added as Line mappings for Invoices and Sales Orders, allowing you to sync your Revenue Recognition Schedule. You will also be able to map Sage fields against a template.</p><p><br></p><p><em><strong>Note: Field mappings are optional and should only be used to override the standard mappings</strong></em></p><p><br></p><p>If you're using multi-location configuration in Sage and you have enforced location at line item level, each line will require a Sage Intacct location ID in order to sync successfully. This is set against the line itself in Halo. The Sage Intacct location ID is found against the location in the drop down in Sage.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQwZWM5YTRlLWFhZDgtNGUwMC05NGJmLWM4ZTUwZDc3MjRhOCJ9.9VH4O4GF7IKZpof2rDFScBgrvOUzHXU-gB9YpW_jTFU" class="fr-fic fr-fil fr-dib" width="909" style="width: 911px; height: 592.463px;" height="592"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 12. Invoice line level Sage fields</span></strong></p><p><br></p><p>You can also set the Sage department and warehouse at the line level. These fields are not mandatory for sync but are useful if you are tracking departments/warehouse. </p><p><br></p><p><strong><em>Note: Due date and currency is mandatory in Sage Intacct to post invoices.</em></strong></p><p><br></p><p>When using multi-currency the currency ISO code the invoice uses will be synced to Sage Intacct. </p><p><br></p><p><br></p><p data-pasted="true"><span style="font-size: 14pt;"><strong>Syncing Projects</strong></span></p><p>To sync Projects to Sage Intacct you will need to enable "Sync to Intacct" on the Defaults tab of your Projects and Project Tasks Ticket Types. Now within the Sage Intacct integration module head to the Projects tab. Here set the "Default Entity to save to". This will be the default Sage Entity you would like new Projects to be saved to. Next you can create Project and Task field mapping by adding to the respective tables.</p><p><br></p><p>You will be able to map against templates, and you will be able to map the observed percent complete on Projects and Tasks </p><p> </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjExOWY5ZjY5LTI2MjctNDVlNC1iZmRkLTZhZWZmNWU0Nzg5ZiJ9.OEWXfOwx6t1qzELbkIMXeAOmRqSq2QbWq3Eqbdnxuvo" class="fr-fic fr-fil fr-dib" width="1113" style="width: 1115px; height: 393.622px;" height="394"></p><p data-pasted="true"><span style="font-size: 10pt;"><strong>Fig 13. Projects Sage fields</strong></span></p><p><br></p><p><br></p><p><strong><span style="font-size: 14pt;">Syncing with Sage Intacct </span></strong></p><p>Changes to certain entities in Halo can be synced to Sage Intacct, configuration for this takes place under the 'Syncing with Sage Intacct' tab.</p><p><br></p><p>When the following entities are created or updated in Halo, they will be created/updated in Sage:</p><ul><li>Invoices</li><li>Bills</li><li>Credit Notes</li><li>Products</li><li>Purchase Order </li><li>Sales Orders</li><li>Projects</li></ul><p id="isPasted">When the following entities are created in Halo, they will be created/updated in Sage:</p><ul><li>Customers</li><li style="box-sizing: inherit;" id="isPasted">Suppliers</li></ul><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjhlMmNjMjQ3LTQ5NmYtNDFiZS1iM2ZkLTJiZjMwYjg1YTA4ZCJ9.0qGvfODANHZhJS6Qyi-kO-i64kbuPnYMiIc0rn7hiek" class="fr-fic fr-fil fr-dib" width="1217" style="width: 1219px; height: 592.182px;" height="592"></p><p><strong><span style="font-size: 10pt;">Fig 14. Syncing with Sage Intacct configuration</span></strong></p><p><br></p><p>The 'Entities to Sync' field is used to determine which entities are synced to Sage, but other configuration needs to be set before completing this field. </p><p><strong><br></strong></p><p><strong>Default Entity to save to</strong> - Here choose the default Sage entity changes are synced to. This is only applicable if you have multiple Sage entities (tenants). This provides a global default but defaults can be set per Halo entity.</p><p><br></p><p><strong>Default Intacct Department</strong> - Here choose the default department line items (invoices, credit notes, purchase orders etc.) will be associated with in Sage when synced to Sage. This provides a global default but department can also be set per line. </p><p><br></p><p><strong>Default Warehouse</strong> - Here choose the default warehouse line items (invoices, credit notes, purchase orders etc.) will be associated with in Sage when synced to Sage. This provides a global default but warehouse can also be set per line. </p><p><br></p><p><strong>Warehouse -</strong> Entity mappings will also need to be configured if your Sage has multiple entities. The mappings will determine which entity each warehouse comes under, which is required when syncing the warehouse information for line items. </p><p><br></p><p><strong>Default Item Group GL Group</strong> - Here, choose a default Item Group GL Group, this will be the GL group items are created under when new items are created in Sage by Halo. If a new item is created in Halo (and item sync enabled) the item will be created under this GL group unless the Halo item is under a Halo product group already associated with a different GL group. </p><p><br></p><p><strong>Entities to Sync</strong> - Here, choose which entities to sync to Sage. When any of the entities set here are created and/or updated in Halo the changes will be pushed to Sage. </p><p><br></p><p><strong>Entities to Sync Halo Id to</strong> - When the entities chosen here are synced to Sage the Halo ID of the entity will be pushed to Sage as part of the sync. Useful if you would like a record of the Halo ID against the entity in Sage. </p><p><br></p><p><strong>Show a message for each successful sync to Sage Intacct </strong>- When checked, a pop-up message will appear each time a sync to Sage is attempted, notifying you if the sync was successful or not. </p><p><br></p><p><strong><span style="font-size: 14pt;">Integrating when using Multi-Entity Distributed (MED) or Multi-Entity Shared (MES) mode on Intacct</span></strong></p><p>When Multi-Entity Distributed (MED) or Multi-Entity Shared (MES) mode is in use in your Sage Intacct you will have to complete some additional configuration in your Halo to determine which Sage Entity (tenant) to send updates to. </p><p><br></p><p>Set which is the default Entity to send updates to under configuration > integrations > Sage Intacct > Syncing with Sage Intacct > 'Default Entity to save to'. This will act as a global default. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImJlYjdhMjZhLWMyYWQtNGFlYy1hMjliLWQzMGVkNzJhYWMyMyJ9.XfskZpn1q4icN5IGT4uw9iRd8j4pUXv6uUmd-UMEIdM" class="fr-fic fr-fil fr-dib" width="906" style="width: 908px; height: 242.072px;" height="242"></p><p><strong><span style="font-size: 10pt;">Fig 15. Default Entity to save to/push changes to</span></strong></p><p><br></p><p>The Entity can then also be specified per customer and per vendor. </p><p><br></p><p>For customers head to Customers > select a customer > Billing tab > 'Sage Intacct Entity'.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjUwZDFjODkzLWFiNTItNDMwNi04M2FjLWEyMDI4YTYxZmYwNSJ9.5dmlE2OS2uvQoKryM9FfedS6p5hGmAPJ7Ne0Ro4KrJI" class="fr-fic fr-fil fr-dib" width="561" height="392"></p><p><strong><span style="font-size: 10pt;">Fig 16. Set Sage Intacct Entity for Customer</span></strong></p><p><br></p><p>Once set, any invoices, POs, bills, credit notes for this customer will sync to this Sage Intacct Entity. </p><p><br></p><p>You can also set a separate Entity for this customers invoices to sync to in the 'Default Entity to save Invoices to' field. </p><p><br></p><p>For suppliers/vendors head to Suppliers > select a supplier > Settings tab > see 'Sage Intacct Entity'. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImI4NDFmMTBlLTA3MTgtNDExNi05NTc5LTBjNTM0NjY2ZWM3MSJ9.S6TVep7rARk67MyrVl-73llpkoH6oP38TSU1rZgPjo4" class="fr-fic fr-fil fr-dib" width="744" style="width: 746px; height: 309.932px;" height="310"></p><p><strong><span style="font-size: 10pt;">Fig 17. Set Sage Intacct Entity for Supplier</span></strong></p><p><br></p><p>The Sage Entity to sync to can also be defaulted for products, invoices, bills and purchase orders created in Halo.</p><p><br></p><p>Each default can be set under the associated tab in the setup page in Halo for the integration. For example, to set the default entity invoices are saved to head to the 'Invoices' tab within the integration setup in Halo. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImI1YzU1NzFlLTMxMDUtNGEzNi1hOGMwLWQ3NjM2MjlhNjRmMSJ9.MaemyWhKHO3HgpDNjQl3XHLSY4hITi7HVybfRc8qCCU" class="fr-fic fr-fil fr-dib" width="1325" style="width: 1327px; height: 350.511px;" height="351"></p><p><strong><span style="font-size: 10pt;">Fig 18. Default Entity to save to (in Sage)</span></strong></p><p><br></p><p data-pasted="true"><strong>Default Entity to Save to </strong>- Here, set the default Sage Entity you would like new invoices/credit notes, bills and purchase orders to be saved to. This default can also be overridden per Halo entity.</p><ul><li>For invoices, the entity to save to can also be set when creating the invoices from the Ready for Invoicing screen and against the invoice itself. This can also be defaulted per customer. </li><li>For credit notes, the entity to save to also be set against the credit note. </li><li>For bills, the entity to save to also be set against the bill. </li><li>For purchase orders, the entity to save to can also be set against the purchase order.</li></ul><p><br></p>
