AP Payments
Agave Sync allows you to sync Sage Intacct AP Payments to Autodesk Build Payments.
Each Autodesk Build Payment must apply to exactly one AP Invoice. If your Sage Intacct AP Payments commonly cover several Bills at once, see What happens if one payment covers multiple invoices? below.
Visual Mapping
Common Errors and FAQs
Are there any prerequisites to syncing AP Payments?
Yes. A payment attaches to an existing Cost Payment Application in Autodesk Build, so the following must be synced beforehand:
- Vendors
- Projects (Jobs)
- Subcontracts or Purchase Orders
- AP Invoices (Cost Payment Applications)
How does Agave determine which AP Invoice a payment belongs to?
Sage Intacct creates two records when you enter a purchasing transaction:
- The invoice itself, in the Purchasing module.
- A matching Bill, in the Accounts Payable module.
Payments can only be applied to AP records, so a payment always attaches to the Bill rather than to the purchasing invoice. Neither record carries the commitment or project directly.
Agave therefore traces the chain backwards: from the Payment to the Bill it was applied to, and from the Bill to the purchasing invoice it originated from. That purchasing invoice is matched to the Autodesk Build Cost Payment Application it was synced from, and the payment is written against it.
Why does my AP Payment show "Missing Dependency"?
This is expected and does not prevent the payment from syncing.
Because the payment attaches to the Bill rather than to the purchasing invoice (see above), Agave looks for the Bill when resolving the payment's dependencies. Bills are not synced in their own right, so the dependency appears unmet and the record is flagged.
The payment can still be synced normally.
Which Sage Intacct payments can sync?
Only payments applied to an AP Bill.
A payment line in Sage Intacct can be applied to several different things — a Bill, a credit memo, a debit memo, an AP advance, or a negative bill. Only a Bill leads back to a purchasing invoice, which is what Autodesk Build needs, so payments applied to the other types will not sync.
What happens if one payment covers multiple invoices?
Error message: AP Payment line items must only reference exactly 1 AP Invoice to sync to Autodesk Build. Enable sage-intacct.ap-payment.split-by-invoice in account settings
A single Sage Intacct payment can cover Bills belonging to different projects and different commitments. Because Agave has to resolve one project and one Cost Payment Application for the Autodesk Build Payment (see above), a payment spanning several Bills is ambiguous and cannot be synced as-is.
Agave can split these automatically: when enabled, a Sage Intacct payment applied to three Bills is brought across as three separate Autodesk Build Payments, one per invoice, each carrying its own amount and landing on its own project and Cost Payment Application. Reach out to your Agave Account Manager to turn this on.
A Bill paid across several of its own entries produces one payment detail row per entry in Sage Intacct. That is still a payment against a single invoice and syncs normally — only the number of distinct invoices referenced matters.
What is the mapping between Sage Intacct and Autodesk Build Payment Types?
Autodesk Build supports three payment types for synced payments, so Sage Intacct's payment methods are grouped as follows:
| Sage Intacct Payment Method | Autodesk Build Payment Type |
|---|---|
| Cash | Check |
| Printed Check | Check |
| Check Delivery | Check |
| WF Check | Check |
| Credit Card | Credit Card |
| Amex Charge Card | Credit Card |
| ACH | Electronic |
| EFT | Electronic |
| Amex ACH | Electronic |
| WF Domestic ACH | Electronic |
| WF USD Wire | Electronic |
If the Sage Intacct payment uses any other payment method, the sync will fail with Sage Intacct payment method 'X' is not supported when syncing to Autodesk Build. Reach out to your Agave Account Manager if you need an additional payment method supported.
Does Agave update the AP Invoice status to be "Paid"?
Yes, but only when both of the following are true:
- The total of all payments applied to the Cost Payment Application equals its net amount, and
- The Cost Payment Application is currently in an Approved status.
Partial payments leave the status unchanged, and the paid amount still appears in the Paid Amount column.