Skip to main content

Prime Contract Change Orders (Owner Change Orders)

Agave Sync allows you to export Autodesk Build Owner Change Orders to Sage Intacct Change Requests and Job Contract Change Orders.

When syncing an Autodesk Build Owner Change Order, Agave will create the following in Sage Intacct:

  1. A new Job Contract Line Item for the Owner Change Order,
  2. A Change Request with multiple Line Items for each Owner Change Order Line Item to update the Job Estimate, and
  3. A Job Change Order to update the newly created Job Contract Line Item.

Visual Mapping​

Job Contract Change Order​

Autodesk Build and Sage Intacct Visual Mapping

Autodesk Build and Sage Intacct Visual Mapping

Job Contract Change Request​

Autodesk Build and Sage Intacct Visual Mapping

Autodesk Build and Sage Intacct Visual Mapping

Autodesk Build and Sage Intacct Visual Mapping

Job Contract Line Item​

Autodesk Build and Sage Intacct Visual Mapping

Autodesk Build and Sage Intacct Visual Mapping

Video Tutorial​

FAQs​

Creating Job Contract Line Items​

As part of syncing Owner Change Orders from Autodesk Build to Sage Intacct, Agave will create a new Job Contract Line Item for each Owner Change Order Line Item.

To create a Job Contract Line Item, the following defaults are required. You can work with your Agave Account Manager to automatically apply these for you:

  1. A default Ledger Account
  2. A default Item

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.

Differentiating Revenue and Cost Amounts When Syncing Owner Change Orders from Autodesk​

When syncing Owner Change Orders from Autodesk to your ERP, you may want to separate cost and revenue amounts so that profit (i.e. revenue − cost) can be calculated correctly.

By default, a Change Order line item may generate both cost and revenue in the ERP. Agave Sync provides two ways to mark certain line items as revenue-only, meaning they generate revenue but no cost.

Available Approaches​

1. Revenue-only Cost Code​

A specific Cost Code can be configured as revenue-only.

  • Line items using this Cost Code will:
    • Generate revenue
    • Not generate cost
  • Configuration is enabled by your Agave Account Manager

Best used when:

  • Markups, fees, or similar items are tracked using dedicated Cost Codes
  • You want the rule to apply regardless of Cost Type
2. Revenue-only Cost Type​

A specific Cost Type can be configured as revenue-only.

  • Line items using this Cost Type will:
    • Generate revenue
    • Not generate cost
  • Configuration is enabled by your Agave Account Manager

Best used when:

  • Markups or fees are categorized by Cost Type (e.g., Markup, Fee)
  • You want consistent behavior across multiple Cost Codes

Important Notes​

  • These settings must be enabled by your Agave Account Manager
  • Once configured, the rules are applied automatically during syncs