Skip to main content

Prime Contracts (Main Contracts)

Visual Mapping​

Autodesk Build and Acumatica Prime Contract Mapping

Autodesk Build and Acumatica Prime Contract Mapping

Demonstration​

Configuration​

Cost Types​

Acumatica only accepts Cost Types (Account Groups) associated with income accounts on the Revenue Budget.

When syncing Prime Contracts from Autodesk to Acumatica, you can set a default income Cost Type that Agave will use for each line item in Acumatica ("REVENUE" in the above example). Work with your Agave account rep to set this up.

Sub Job (Task) Aggregation​

Acumatica users may choose to track revenue solely at the sub job level (ignoring Cost Code detail) in Acumatica. This is set on the project record via the "Revenue Budget Level" setting:

Autodesk Build and Acumatica Prime Contract Mapping

When syncing Prime Contracts from Autodesk to Acumatica, Agave has a setting that will aggregate Prime Contract Line Items by sub job and write them to Acumatica at the Task level. This allows you to keep your Autodesk Prime Contract at the Cost Code level to match your budget SOV.

Work with your Agave rep to enable this setting. Note that it will also impact other AR workflows (Prime Contract Change Orders and AR Invoices).

Common Errors and FAQs​

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.