Sage Intacct and Procore integration

What moves between them

The main flow is from Procore into Intacct. Purchase order contracts, commitments, and requisitions from Procore projects flow into Intacct as GL transactions, allocated to the cost code and budget line item in Procore and mapped to the matching GL account and dimension in Intacct. Payment applications also sync into Intacct's payables. Vendor master records flow bidirectionally: new vendors created in Intacct sync to Procore so project commitments reference valid vendors, and vendor name or contact changes in either system propagate to the other. GL accounts and cost dimensions from Intacct are read into Procore so budget configurations reference current accounting structures. The sync runs on a daily schedule and also accepts Procore webhooks for immediate push on commitment or requisition changes.

How ml-connector handles it

ml-connector obtains a session ID from Intacct via the XML gateway using cached senderId, senderPassword, companyId, and userId, and refreshes it automatically before expiry. On the Procore side it holds OAuth2 credentials and refreshes the bearer token when a call returns 401. For every Procore commitment or requisition, it reads the associated project, cost code, and line item detail, then constructs an Intacct AP bill XML document with line items mapped to matching GL accounts and cost dimensions, and posts it through the Intacct XML gateway with a uniqueid for server-side deduplication on retry. Vendor creates and updates flow the opposite direction: ml-connector reads changes from Intacct, parses the XML response for errormessage tags, and posts vendor records to Procore with the corresponding company_id. Cost code and budget validation happens before any GL posting so a commitment references a GL account and dimension that already exist in Intacct. Procore rate limits and custom headers are handled on each request, and XML control characters that would break XML parsing are stripped before escaping. Every record carries a full audit trail of source, destination, timestamp, and result status.

A real-world example

A regional general contractor runs Procore across five active projects with a combined budget of 35 million dollars and uses Sage Intacct for project accounting and month-end close. Before the integration, the accounting department downloaded commitment and requisition reports from Procore each week, mapped costs to GL accounts by hand, and entered the summary into Intacct as manual journal entries. Month-end close required a three-day reconciliation between Procore project costs and Intacct GL accounts, and cost overruns or change orders often appeared in one system before the other, creating variance reports that required manual investigation. With Sage Intacct and Procore connected, commitments and requisitions post to the GL automatically within 24 hours, mapped to the correct cost codes and vendor accounts, and change orders flow as amendments to existing GL transactions. Month-end close now starts with the GL already reconciled to Procore project records, and the controller can spend time on variance analysis rather than re-keying.

What you can do

• •Post Procore purchase order contracts, commitments, and requisitions to Sage Intacct as GL transactions mapped to the correct cost codes and GL accounts.
• •Sync Procore payment applications into Intacct payables with line item detail and project allocation.
• •Keep vendor records in sync across both platforms so Procore commitments reference valid Intacct vendors and vendor changes propagate to Procore.
• •Synchronize GL accounts and cost dimensions from Intacct to Procore so budget configurations and cost code validation reference current accounting structures.
• •Refresh Intacct sessions before expiry and Procore OAuth2 tokens on 401 responses, with full audit trail on every posted record.

Questions

Which direction does data move between Sage Intacct and Procore?

The primary flow is Procore to Intacct. Purchase order contracts, commitments, requisitions, and payment applications flow from Procore into Intacct's GL, mapped to cost codes and GL accounts. Vendor records flow bidirectionally so new vendors in Intacct sync to Procore and vendor updates propagate both ways. GL accounts and cost dimensions flow from Intacct to Procore for reference data and cost code validation.

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

ml-connector caches the Intacct session ID obtained via the XML gateway and refreshes it automatically before the 50-minute expiry. It posts AP bills and vendor records as XML documents through the single gateway endpoint with uniqueid for server-side deduplication on retry. XML responses are parsed for errormessage tags to surface application-level errors, and XML control characters are stripped before posting to prevent parse failures.

Does ml-connector support Procore webhooks, or does it poll for changes?

ml-connector supports both. It can poll Procore on a daily schedule to pull commitment and requisition changes, and it also accepts Procore webhooks for real-time push on create, update, and delete events for Commitments, Requisitions, DirectCosts, and Vendors, so urgent changes post to the GL without waiting for the next scheduled run.