Sage Intacct and AvidXchange integration

What moves between them

Vendor master records and GL accounts flow from Sage Intacct to AvidXchange on a schedule you define, typically aligned with your month-end GL close and accounts payable cycle. As invoices are processed and approved in AvidXchange, payment batches are created and payment execution status is pulled back into Intacct's APPAYMENT table to close payment records and settle GL accounts. The flow is primarily one-way on master data (Intacct to AvidXchange) and status-driven on payments (AvidXchange back to Intacct).

How ml-connector handles it

ml-connector manages Sage Intacct's XML gateway and 50-minute session lifecycle by caching the sessionid and refreshing it on timeout before the next call fails. It translates Sage Intacct's VENDOR, GLACCOUNT, and APBILL records into AvidXchange's REST JSON schema, mapping Intacct GL dimensions to AvidXchange accounting dimensions so payment allocations land on valid accounts. Because neither system offers webhooks, ml-connector polls on a schedule and batches records to reduce API calls. Retried operations rely on Intacct's uniqueid flag in control blocks for server-side deduplication. Payment status and completed payment records are pulled from AvidXchange, translated back to Intacct's APPAYMENT structure, and posted through the XML gateway. The integration tracks session expiry and payment batch completion and logs every record change for audit and replay.

A real-world example

A mid-sized professional services firm runs Sage Intacct for general ledger, accounts payable, and project accounting across three business units. They use AvidXchange to digitize invoice receipt, route invoices through approval workflows by cost center, and execute payments. Before the integration, the accounting department exported vendor master records and GL codes from Intacct and manually uploaded them to AvidXchange each quarter, and after payment batches were approved and paid in AvidXchange, a second team re-entered payment completion data into Intacct to close out the payment journal entries. With Sage Intacct and AvidXchange connected, vendor and GL changes sync automatically, invoices route to the correct cost centers on receipt, and payment completion flows back to Intacct without re-entry. Month-end close and vendor reconciliation now start with both systems in agreement.

What you can do

• •Synchronize vendor master records and GL accounts from Sage Intacct to AvidXchange on a schedule tied to your accounting cycle.
• •Map Intacct GL dimensions to AvidXchange accounting dimensions so invoice coding and payment allocation land on valid accounts.
• •Pull payment completion status and executed payment records from AvidXchange back into Intacct to close payment batches and settle GL entries.
• •Manage Sage Intacct's XML gateway session lifecycle, refreshing the 50-minute session and handling timeout retries transparently.
• •Detect and replay failed records with a full audit trail for every vendor, invoice, and payment record that moves between systems.

Questions

Which direction does data move between Sage Intacct and AvidXchange?

Master data flows primarily from Sage Intacct to AvidXchange: vendors, GL accounts, and invoice data move into AvidXchange for coding and approval. Payment completion status flows back from AvidXchange into Intacct so payment records close and GL accounts are reconciled. GL dimension mapping ensures invoice coding and payments land on valid accounts in both directions.

How does ml-connector handle Sage Intacct's XML gateway and session timeout?

ml-connector caches the Intacct sessionid after the initial login call and refreshes it automatically when the 50-minute window expires, before the next call can fail. This keeps the integration running on schedule without manual session management. The API returns HTTP 200 for all responses, so ml-connector parses XML response bodies for errormessage tags to detect application-level failures and retries with exponential backoff.

Does AvidXchange offer webhooks for real-time payment completion notifications?

No. AvidXchange does not publish webhook or push-notification capability in public documentation. ml-connector polls AvidXchange on a regular schedule to retrieve payment completion status and pulls those records back into Sage Intacct, batching calls to stay within rate limits and reducing the frequency of API calls.