What API2Cart Is Evaluating for Infor SunSystems Integration
Candidate data flow
Commerce transactions prepared for controlled ledger and customer workflows. The final entity and method list will be based on verified vendor API capabilities rather than assumptions.
Operational outcome
The intended workflow is to retain business-unit, currency, analysis-code, and period details. Record ownership and idempotency would be defined before write operations are enabled.
Accounting safeguards
The connector would need to manage validation and rejection before financial records are accepted. Orders, invoices, payments, refunds, settlements, and journal entries would not be treated as interchangeable records.
Develop Integrations Faster and Save Up to 9x on Costs
Trusted by
What We Know About Infor SunSystems So Far
Based on Infor SunSystems’s own documentation and API2Cart’s discovery process — not a promise of a release date.
API & Integration. Infor SunSystems' core integration mechanism, SunSystems Connect (SSC), is a Java-based module that exchanges data as XML messages consumed via a SOAP API, with large journal payloads dropped as XML files for SSC to pick up rather than sent through a lightweight synchronous REST call — an architecture oriented toward legacy enterprise messaging rather than modern REST/JSON. More recent integration is possible through the Infor OS platform (API Gateway, ION, Business Object Documents), which layers newer connectivity on top of, but does not replace, the underlying SOAP/XML integration model.
Is this integration live yet? No. Infor SunSystems integration is not live yet. Authentication, entities, fields, write operations, webhooks, limits, regional availability, and release timing remain subject to technical discovery and customer demand.
What’s the integration challenge? Engineering discovery must verify deployment architecture, ION services, available APIs, and import constraints. Unsupported objects or operations would remain outside the published scope.
How is a release decided? Roadmap evaluation includes API maturity, sandbox access, accounting correctness, customer demand, maintenance cost, data residency, rate limits, and overlap with existing connectors. The page records an integration candidate; it does not promise a release date.
Technical validation. Engineering discovery must verify deployment architecture, ION services, available APIs, and import constraints. Unsupported objects or operations would remain outside the published scope.
Primary sources: Infor SunSystems official website · Official developer or product documentation
Related planned integrations: Xledger integration · BILL integration · BlackLine integration · Deskera Books integration
Interested in Infor SunSystems Integration?
Let us know you’re interested, and we’ll notify you as soon as Infor SunSystems support becomes available.
