SYSPRO and Airbase integration

What moves between them

The main flow runs from SYSPRO into Airbase. ml-connector polls SYSPRO's supplier table on a schedule (recommended 15-minute interval) and creates or updates vendor records in Airbase. Purchase order headers and details flow from SYSPRO into Airbase as purchase requests, mapped to the matching vendors. Invoices and GL postings are read from SYSPRO and can be synchronized into Airbase for matching and payment workflows. Reference data such as GL accounts flows in both directions so purchase orders land on valid accounts in Airbase.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the SYSPRO side, it obtains a session token by calling the Logon endpoint with supplied operator credentials, then uses that token for all subsequent REST calls to the e.net Business Objects API, refreshing when the session expires. For read-only operations it can use the OData API with HTTP Basic Auth instead. On the Airbase side, it stores the bearer token encrypted and presents it in the Authorization header on every request. ml-connector polls SYSPRO's OData tables with $filter conditions on timestamp fields to fetch only new or changed records since the last run. Vendors are mapped by a unique key (supplier code) so updates are idempotent. Purchase order lines are enriched with vendor and GL account mappings before posting to Airbase. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized manufacturing company uses SYSPRO for production, procurement, and GL management, and Airbase for spend control and accounts payable approval workflows. Before the integration, the procurement team exported purchase orders from SYSPRO and manually entered them into Airbase, and new suppliers had to be created in both systems by hand. With SYSPRO and Airbase connected, purchase orders flow automatically into Airbase for approval, suppliers sync across both systems, and invoice matching is immediate because GL accounts and vendor codes align. The procurement team spends less time on data entry and more time on approval and vendor management.

What you can do

• •Sync SYSPRO suppliers to Airbase vendors automatically, with updates for address and status changes.
• •Push SYSPRO purchase orders into Airbase as purchase requests, mapped to the correct vendors and GL accounts.
• •Map SYSPRO invoice data to Airbase for GL posting and three-way matching with orders and receipts.
• •Authenticate SYSPRO with session tokens from e.net Business Objects or HTTP Basic Auth from OData, and Airbase with bearer token credentials.
• •Poll SYSPRO on a schedule tied to your procurement cycle, with retries and a full audit trail on every record.

Questions

Which direction does data move between SYSPRO and Airbase?

The main flow is SYSPRO into Airbase. Vendors, purchase orders, and invoices move from SYSPRO into Airbase, while GL accounts and subsidiary mappings are validated in both directions. SYSPRO's OData API is read-only, so data flows one way from source records into Airbase for approval and payment processing.

Does ml-connector support SYSPRO's different authentication methods?

Yes. ml-connector can use SYSPRO's REST API with session tokens (obtained by calling Logon with operator credentials), or the OData API with HTTP Basic Auth (operator code and OData password). It handles token refresh automatically when the session expires.

How does the integration handle SYSPRO's lack of webhooks?

ml-connector polls SYSPRO's OData tables on a schedule, using $filter conditions on timestamp fields like InvoiceDate and PostDate to fetch only new or changed records. A recommended interval is 15 minutes for procurement and financial data, which can be adjusted to match your business cycle.