Which direction does data move between SYSPRO and Adyen?

The main flow is Adyen into SYSPRO. Payment authorizations, captures, refunds, and daily settlements flow from Adyen via webhook into SYSPRO AR and GL. SYSPRO is read-only on the Adyen side, so ml-connector does not write payments or disputes back to Adyen. Customer and invoice reference data in SYSPRO can be read to help match incoming Adyen events.

How does the integration match Adyen payments to SYSPRO invoices?

ml-connector stores the SYSPRO customer code and invoice number in the Adyen payment's metadata at the time of payment. When a payment event arrives from Adyen, ml-connector reads that metadata and looks up the matching SYSPRO customer and open invoice. If the amount matches the invoice balance and the date is within your tolerance window, the payment is recorded. Unmatched payments are flagged for manual review so nothing is lost.

Does Adyen's webhook require special setup?

Yes. You must register ml-connector's webhook endpoint in the Adyen Customer Area and configure your webhook secret. ml-connector verifies every incoming event with HMAC-SHA256 signature validation using that secret, so unverified requests are rejected. Adyen fires payment and settlement event types separately, and ml-connector handles both.

SYSPROAdyen

SYSPRO and Adyen integration

SYSPRO runs your manufacturing finance and order-to-cash process. Adyen processes your customer payments across channels and delivers settlement data. Connecting them means payment receipts and settlement details flow directly from Adyen into SYSPRO without re-keying. New payments are matched to open SYSPRO invoices and customer records, and settlement reports land in your general ledger on schedule. The two systems stay in sync so your accounts receivable and cash accounts reflect reality.

How SYSPRO works

Adyen exposes payments, captures, refunds, cancellations, and settlement reports through REST JSON APIs authenticated with an API Key in the X-API-Key header or Basic Auth. Adyen pushes payment and settlement events to a registered webhook endpoint via HTTP POST with HMAC-SHA256 signature verification. Event types include AUTHORISATION, CAPTURE, REFUND, CANCELLATION, and REPORT_AVAILABLE. Adyen test and live environments use separate API keys and base URLs. Adyen is a payment platform only: it has no native support for vendor records, purchase orders, GL accounts, or cost centers.

How Adyen works

SYSPRO Adaptive ERP exposes customers, invoices, general ledger accounts, and balances through e.net Business Objects (REST and SOAP with session token auth) and OData (REST read-only with HTTP Basic Auth). The e.net API layer accepts and writes XML payloads for AP and AR transactions, while OData is read-only. SYSPRO does not push outbound webhooks, so data reads are by polling with $filter on timestamp fields. Cloud SYSPRO prohibits direct database access and enforces multi-tenant isolation. Session tokens expire on logoff or timeout, so the connector must handle re-authentication on 401 responses.

What moves between them

The main flow is Adyen into SYSPRO. Payment authorizations, captures, and refunds flow from Adyen via webhook into SYSPRO customer invoices and AR subsidiary ledger. Settlement reports from Adyen are matched to SYSPRO invoice batches and posted to the general ledger on a daily or weekly schedule that you define. Refunds and chargebacks reverse the matching invoice in SYSPRO. Reference data such as customer codes and invoice numbers are stored in Adyen payment metadata so each event maps cleanly without additional lookup. SYSPRO is read-only on the Adyen side, so no payments or disputes are sent back to the payment processor.

How ml-connector handles it

ml-connector registers a webhook endpoint with Adyen for payment and settlement events. When Adyen fires an event, ml-connector verifies the HMAC-SHA256 signature using your Adyen webhook secret, then parses the payment or settlement details. For payments, it looks up the matching SYSPRO customer using the Adyen merchant reference, searches for an open invoice with amount and date logic, and records the payment in SYSPRO's AR tables via the e.net API, which requires session token auth (ml-connector logs in once and renews on 401 responses). For settlement reports, ml-connector polls the Adyen API for daily settlement data, aggregates by customer, and posts the net deposit to SYSPRO's general ledger mapped to your cash and revenue accounts. All payment and settlement records are tagged with the Adyen event ID for reconciliation traceability, and failed matches are logged for manual review so no payment is lost.

A real-world example

A mid-sized B2B distributor runs SYSPRO for order management and invoicing, and Adyen for online and ACH payment processing. Before the integration, the finance team received Adyen settlement reports via email every morning, matched them to open invoices in SYSPRO by hand using a PDF pivot table, then recorded customer payments and the daily deposit in separate AR and GL entries. Month-end reconciliation required chasing 30 days of manual matches. With SYSPRO and Adyen connected, each customer payment received by Adyen flows into SYSPRO within minutes, matched to the correct invoice and customer, and daily settlement reports post to the cash and revenue accounts automatically. The finance team now reconciles AR in hours instead of days, and month-end close starts with cash already verified.

What you can do

Receive Adyen payment and settlement events via webhook and post them into SYSPRO customer invoices and AR subsidiary ledger.
Match Adyen payments to SYSPRO open invoices by customer code, amount, and invoice reference stored in payment metadata.
Post Adyen daily settlement reports into SYSPRO's general ledger mapped to your cash and revenue accounts.
Authenticate Adyen via API Key header and SYSPRO via session token, with automatic re-authentication and HMAC signature verification.
Maintain a full audit trail using Adyen event IDs and flag unmatched payments for manual review.

Questions

Which direction does data move between SYSPRO and Adyen?: The main flow is Adyen into SYSPRO. Payment authorizations, captures, refunds, and daily settlements flow from Adyen via webhook into SYSPRO AR and GL. SYSPRO is read-only on the Adyen side, so ml-connector does not write payments or disputes back to Adyen. Customer and invoice reference data in SYSPRO can be read to help match incoming Adyen events.
How does the integration match Adyen payments to SYSPRO invoices?: ml-connector stores the SYSPRO customer code and invoice number in the Adyen payment's metadata at the time of payment. When a payment event arrives from Adyen, ml-connector reads that metadata and looks up the matching SYSPRO customer and open invoice. If the amount matches the invoice balance and the date is within your tolerance window, the payment is recorded. Unmatched payments are flagged for manual review so nothing is lost.
Does Adyen's webhook require special setup?: Yes. You must register ml-connector's webhook endpoint in the Adyen Customer Area and configure your webhook secret. ml-connector verifies every incoming event with HMAC-SHA256 signature validation using that secret, so unverified requests are rejected. Adyen fires payment and settlement event types separately, and ml-connector handles both.

Connect SYSPRO and Adyen

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started