AP Invoices (Purchasing Transactions)
Agave Sync allows you to export Autodesk Build Cost Payment Applications to Sage Intacct Purchasing Transactions.
Agave Sync exports AP Invoices to Sage Intacct in a Pending status. AP Invoices will appear in Sage Intacct's Accounts Payable module. You can then apply AP Payments against them.
Visual Mapping
Video Tutorial
FAQs and Common Errors
Setting the Sage Intacct Purchasing Transaction Type
When configuring your AP Invoice sync to Sage Intacct, your Agave Account Manager will ask you to specify a default Purchasing Transaction Type for both Subcontract and Purchase Order AP Invoices.
You can find a list of valid Order Entry Types in Sage Intacct by navigating to Order Entry-->All-->Transactions:
How does Agave Sync determine a Sage Intacct Line Item's (Entry's) Item ID?
When syncing to Sage Intacct, Agave Sync uses the Item ID linked to the corresponding Subcontract or Purchase Order Line Item. Since Autodesk does not assign Item IDs, Agave defaults to the Item ID from the Subcontract or Purchase Order Line Item during the sync.
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.
Configuration in Sage Intacct
Transaction Definition for PO Invoices and/or Subcontract Invoices
Configure a Transaction Definition in Sage Intacct for PO Invoices and/or Subcontract Invoices. The integration supports either a single shared invoice type for both POs and Subcontracts, or separate invoice types for each.
Template names are flexible; the required settings are:
- Workflow category:
Invoice - Workflow → Transaction conversion: configure the invoice to be created from the PO and/or Subcontract transaction
- Partial conversion handling: set to
Leave transaction open
Optionally, configure a default AP term as a fallback for cases when terms aren't specified on the vendor record.
