Axya integrates with IFS Cloud using IFS's native REST APIs and IFS Connect event management for bidirectional PO synchronization. The integration uses a lightweight on-premise middleware for reliable data exchange.
| Aspect |
Details |
| Type |
Partner-Delivered Integration |
| Architecture |
On-premise middleware with IFS Connect events |
| Deployment |
Windows service on customer VM |
| Sync Frequency |
Configurable polling interval |
| Direction |
Bidirectional |
- Purchase Orders — Headers and line items
- PO Documents — PDF generated via IFS Reports
- Revisions — Updated POs detected via custom status field
- Reception Data — Receipt status for delivery tracking
- Supplier Acknowledgments — PO confirmation status
- Delivery Date Confirmations — Promise dates written back
- Price and Quantity Adjustments — Negotiated changes
- Buyer creates a PO in IFS Cloud and sets the custom status field to trigger sync
- IFS Connect event subscriptions detect the status change
- The middleware retrieves PO data and generates the PDF via IFS Reports
- Data is sent to Axya through a reliable message queue
- Supplier interacts via Axya's portal
- Supplier responses are polled from Axya and applied to IFS
- Receipts are tracked and POs auto-archive when fully received
- IFS Connect Integration — Uses IFS's native event management for efficient change detection
- Native REST APIs — No custom web services needed; leverages IFS's standard API layer
- PDF via IFS Reports — Documents generated using IFS's built-in reporting engine
- Delivery Progress Visibility — Receipt tracking synced for supplier and buyer visibility
- Price and Quantity Negotiation — Full support for supplier-proposed changes
| Resource |
Minimum |
Recommended |
| OS |
Windows Server |
Windows Server |
| RAM |
8 GB |
16 GB |
| Disk |
40 GB |
80 GB |
| CPU |
2 vCPU |
4 vCPU |
- OAuth 2.0 credentials (Client ID, Client Secret)
- Service account with Purchase Order access, custom field permissions, and report execution permissions
- IFS Connect configuration (event subscriptions and outbound connections)
- VPN access to IFS Cloud environment
- Windows VM provisioned per requirements above
- OAuth 2.0 authentication with dedicated service account
- Middleware communicates outbound only over HTTPS
- IFS Connect event subscriptions scoped to PO changes only
- All communication encrypted in transit
For setup assistance, contact your Axya account representative.