Skip to main content

Common Errors and FAQs

General FAQs​

What requirements must be met before connecting Agave Sync to Sage Intacct?​

  1. You need to purchase the Sage Intacct Construction Accounting module.
  2. You need to enable the Web Services Subscription (see Authentication).

Connecting at the Top Level vs. Child-Entity Level​

Are there any particular considerations or best practices we should be aware of when integrating at the top level versus the entity level with Intacct?

Each Agave sync configuration links one Autodesk Hub with one Sage Intacct Entity.

Both integration approaches -- at the top level or at an individual child level -- are viable. We would generally recommend integrating at the top level for the following reasons:

  1. Most core objects (e.g., Vendors, Customers) can be set up at the top level and shared with child entities as needed.
  2. Inter-company transactions are only possible at the top level.
  3. Less overhead work: permissions, modules, and settings can be configured once at the top level.
  4. If additional entities are added over time (e.g., through acquisitions), they become a deliberate opt-in, rather than being automatically included.

Are there any known issues or limitations that could affect the integration's performance or functionality at either level?

Typically, no major issues arise at either level. Some important things to consider include:

  1. A top-level entity may contain significantly more data, potentially leading to a higher request volume to Intacct and the need for more filtering, which could slow down requests.
  2. While filters can be applied at the top level to achieve similar results, managing syncs at the child level provides more control.
  3. Each new sync configuration (e.g., integrating another entity with Autodesk) would incur additional costs from Agave.

What are costs from Sage Intacct for using Agave Sync?​

You will need to must purchase a separate "Web Services" license, which costs $2,500/yr for 100k total requests per month.

For more details on enabling the Web Services license, see link.

How are UoM, conversion type, etc. populated on entries for a change order synced as a purchasing transaction?​

Agave will populate the unit of measure from the original line item that has been changed, and will default the conversion type from the unit of measure of that line item (e.g. a lump sum line item will have conversion type price)

Why are the price and quantity values on entries from a change order zero on the original purchasing transaction?​

When change orders are synced from Agave to Sage Intacct, they’re added as new line items with original price and quantity set to $0.

The actual impact of the change is shown in the revised price and revised quantity fields on that line item.