Skip to main content

Purchase Orders

Agave Sync allows you to sync Sage Intacct Purchase Orders (i.e. a type of Purchasing Transactions) to or from Autodesk Build Cost Contracts.

note

If you sync Purchase Orders from Autodesk Build to Sage Intacct, Agave Sync will export Purchase Orders to Sage Intacct in an Pending status. Purchase Orders will appear in Sage Intacct's Purchasing Transactions module. You can then apply AP Invoices against them.

Visual Mapping​

Autodesk Build and Sage Intacct Visual Mapping

Autodesk Build and Sage Intacct Visual Mapping

Autodesk Build and Sage Intacct Visual Mapping

Video Tutorial​

Common Errors and FAQs​

Matching Sage Intacct Purchasing Transaction Types to Autodesk Build Contract Types​

To ensure a seamless sync, you will want to make sure your Purchasing Transaction Types match your Autodesk Build Cost Contract Types:

Autodesk Build and Sage Intacct Visual Mapping

Setting a Purchase Order Line Item in Sage Intacct​

If you choose to export Purchase Orders from Autodesk Build to Sage Intacct, keep in mind that Autodesk Build does not assign an Item ID, which is required for Purchasing Transactions in Sage Intacct. To address this, your Agave Account Manager can enable a setting that will automatically apply an Item ID to each Purchase Order Line Item during the sync.

Error: Document Number is missing​

This error occurs when your Sage Intacct configuration requires a document number for purchase orders. Please reach out to your Agave implementation team so that they can enable a setting in your configuration to fix this.

Does Agave Support Syncing Sub-items from Autodesk Build?​

Yes, Agave supports syncing one level of sub-items from Autodesk Build for the following record types:

  • Subcontracts
  • Purchase Orders
  • Change Orders
  • AP Invoices
  • Prime Contracts
  • Prime Contract Change Orders
  • AR Invoices

To enable syncing for sub-items, ask your Agave Account Manager to enable it for you.

How It Works

Autodesk Build records have a hierarchical structure with:

  • Root items — parent line items
  • Sub-items — child line items
  • Sub-sub items — which are explicitly filtered out (only one level of nesting is supported)

Agave Sync will include root items and their direct sub-items when syncing. Any items nested deeper than one-level are excluded.