SYSPROSYSPRO, extended without touching the core.
We build integrations, screens and AI agents on SYSPRO through its business objects, the route SYSPRO itself calls always forward compatible, so your next upgrade doesn't break them. And we support the layer SYSPRO's own support contract leaves out: customizations, scripts, integrations and EDI maps.
Business objects and e.net, scoped operator accounts, no direct database writes.
A formal SYSPRO notice of 15 July 2026 ends the upfront and annual licence-fee models in favour of named-user subscriptions. Check which date applies to you.
Count your named users and integration accounts before you sign.
Integrations and agents that log in as operators need licensing too.
From SYSPRO's formal notice on its licensing change. Ask your SYSPRO channel partner for the terms that apply to your contract.
SYSPRO's own guidance: business objects are always forward compatible; direct SQL is not advised because it ties you to one release.
| Approach | Use it for | Upgrade safety |
|---|---|---|
| e.net business objects | Orders, invoices, stock and postings from portals, stores and AI agents. The only supported way to write | High |
| OData Data Connector | Read-only access for reports, Power BI and AI lookups (from SYSPRO 8 2021 R2) | Medium |
| Document Flow Manager | EDI and bulk file imports, posted through business objects | High |
| Rules Engine | Alerts, approvals and workflow after a posting | High |
| Avanti screens and Power Tailoring | Custom screens and logic built with SYSPRO's own tools | Medium to high |
| Direct SQL | Nothing new. Replace it during your next upgrade | Low |
From SYSPRO's best-practice guide for connecting to SYSPRO and SYSPRO help, October 2026.
SYSPRO launched Torque on 2 September 2026. It works the same way we build agents: through business objects, inside the permissions of a SYSPRO operator, with approvals before anything posts.
Usage-based subscription plans.
Reaches on-premises SYSPRO without opening inbound ports.
The same supported route our integrations use.
Earlier releases connect API-first.
From SYSPRO's Torque launch release and SYSPRO help. Where Torque doesn't cover a job, such as cash application, a custom agent uses the same business objects.
SYSPRO's support agreement is clear: it covers releases under mainstream maintenance and excludes the custom layer. That's where most problems live.
| Area | SYSPRO support | QServices |
|---|---|---|
| The SYSPRO product | Yes, for releases under mainstream maintenance | We escalate to SYSPRO and run the workaround |
| Customizations and scripting | Excluded | Supported, and rebuilt the upgrade-safe way |
| Integrations and EDI maps | Excluded | Monitored, with the Document Flow Manager failed folder watched |
| Third-party products | Excluded | Supported where we built or connected them |
| Database fixes | Excluded | Traced and fixed through business objects |
| Release planning | Your responsibility | We keep you on a release under mainstream maintenance |
From SYSPRO's cloud ERP software support services agreement. SYSPRO's targets: level 1 same business day, level 2 next day, level 3 two days.
Flexible Metal runs on SYSPRO. We built barcode receiving, batch tracking and multi-warehouse stock on top of it through SYSPRO's own business objects, and left the core exactly as it was. We still support it today.
Fixed price per phase. Every extension is documented and covered by our support.
Every customization, script, integration and EDI map listed, with its upgrade risk.
Your team picks what to rebuild, retire or leave, and the licence count for integrations.
Direct SQL and old scripts moved to business objects and SYSPRO's own tools.
Cash application and other finance agents through the same business objects. See AI agent development.
Customizations, integrations and EDI under one SLA, with a regression pack for each upgrade.
Yes. SYSPRO's own Torque agents, launched in September 2026, work through business objects with approval steps before posting. Custom agents use the same route for jobs Torque doesn't cover, such as cash application, within a SYSPRO operator's permissions.
Write through e.net business objects, read through the OData connector, build screens with Avanti and Power Tailoring, and use the Rules Engine for workflow. Avoid direct SQL, which SYSPRO says ties a solution to one release.
SYSPRO's own agreement covers the product on releases under mainstream maintenance and excludes customizations, scripting, integrations, third-party products and database fixes. A good partner contract names each of those, monitors integrations and EDI, and plans releases so you stay supported.
It depends on direct SQL integrations, scripts and reports that need rebuilding, and the infrastructure: SYSPRO 2026 R1 needs Windows Server 2022, SQL Server 2019 and Windows 11 clients, plus a new licence if you're on 2024 or earlier. We price each phase after the assessment.
Document Flow Manager picks up files from folders, maps them with XSLT and posts them through business objects. Each trading partner needs its own map, and the failed folder needs watching.
Ask whether they write through business objects or SQL, how they document and support customizations SYSPRO excludes, what they test before each upgrade, and what they've built on SYSPRO that's still running.
Find out what to fix first on SYSPRO, with the hours and dollars attached.
Facts on this page checked on 22 October 2026.
Founder and CEO
Chief Sales Officer
Join our live webinar on Sept 24 and see five
ways to automate meetings, approvals, and
document search with tools already in your
tenant.
