Oracle NetSuite and JAGGAER integration

What moves between them

The primary flow is from Oracle NetSuite into JAGGAER. Purchase orders, vendor master records, and invoice headers move on a schedule you define, typically daily or weekly. GL account mappings ensure that when JAGGAER processes an invoice, it posts to the correct NetSuite GL account and cost center. Vendor changes in NetSuite flow to JAGGAER so the supplier master stays in sync across both systems.

How ml-connector handles it

ml-connector stores OAuth 2.0 credentials encrypted for both Oracle NetSuite and JAGGAER, refreshing the NetSuite token every 55 minutes (before the 60-minute expiry). It polls NetSuite via SuiteQL or REST records endpoints for purchase orders, vendor bills, and vendor master on a schedule you set, then maps GL accounts and cost centers from NetSuite's classification structure into JAGGAER's GL dimensions. It then POSTs those records to JAGGAER's J1P API. NetSuite webhook Event Subscriptions can optionally push records instead of polling. If a record arrives in JAGGAER with an unmapped GL account, ml-connector queues a retry with backoff until the account exists in JAGGAER or the mapping is provided. Every record carries a full audit trail and can be replayed if a downstream call fails. ml-connector handles rate-limit backoff and token refresh on both sides transparently.

A real-world example

A mid-market manufacturing business runs Oracle NetSuite for global finance and procurement planning, and uses JAGGAER for tactical purchasing execution and vendor invoice management across three regional plants. Before the integration, the procurement team exported purchase orders from NetSuite weekly and manually entered them into JAGGAER through the supplier portal, and accounts payable received vendor invoices in JAGGAER that did not cross-reference NetSuite POs. Invoices landed on default GL accounts rather than the cost centers budgeted in NetSuite, forcing the finance team to reverse and remap entries at month-end. With NetSuite and JAGGAER connected, each PO flows from NetSuite to JAGGAER automatically and incoming invoices match directly to the NetSuite PO with GL accounts pre-populated. The finance team no longer re-enters data and month-end reconciliation is automated.

What you can do

• •Sync purchase orders from Oracle NetSuite into JAGGAER's procurement system on a schedule you define, push or pull.
• •Move vendor master records and GL accounts from NetSuite to JAGGAER so your supplier and cost center data stays aligned.
• •Map Oracle NetSuite GL accounts and classifications to JAGGAER GL accounts so invoices post to the correct cost center.
• •Authenticate both Oracle NetSuite (OAuth 2.0 and TBA) and JAGGAER (OAuth 2.0), with transparent token refresh and rate-limit backoff.
• •Deliver a full audit trail on every record synced, with the ability to replay failed records when a downstream system recovers.

Questions

Which direction does data move between Oracle NetSuite and JAGGAER?

The primary direction is NetSuite into JAGGAER. Purchase orders, vendor records, GL accounts, and cost classifications flow from NetSuite to JAGGAER so your procurement execution layer stays in sync with your source of truth. JAGGAER invoices can reference NetSuite POs, but invoice data itself does not flow back into NetSuite (that is a separate cycle).

Does ml-connector use NetSuite Event Subscriptions or SuiteQL polling?

ml-connector can use either. NetSuite Event Subscriptions push changes via webhooks when purchase orders, vendors, or GL accounts are created or modified, which is lower-latency. Alternatively, ml-connector polls via SuiteQL on a schedule you define, which gives you explicit control over sync frequency and is useful for bulk historical syncs. You can also use both together.

What happens if a JAGGAER GL account does not match a NetSuite GL account?

ml-connector stores the mapping between NetSuite GL accounts (identified by their NetSuite ID or custom field) and JAGGAER GL accounts in its local mapping table. If an invoice arrives referencing a NetSuite GL account that has no JAGGAER counterpart, ml-connector queues the record for retry with exponential backoff until the mapping is added or the account is created in JAGGAER. The full audit trail shows which records are pending and why.