Integrations

• Accounts payable. Share approved order revisions, applied amendments and posted receipts for invoice matching. Return each mismatch to the responsible Buyer with its source identifier. Invoice approval and payment stay in accounts payable; an order closes only when the agreed fulfillment and matching conditions are satisfied.
• Budgeting. Share current commitment by department, category and account. Reconcile approved increases, reductions, cancellations and receipt progress against the same cutoff. Preserve the last accepted revision and expose failed updates.

• Warehouse system. Send eligible order lines to the receiving system selected for each location. Map its inspection and receipt results back to the corresponding order line and revision. A supplier’s shipment notice is expected inbound work, not proof that goods were received.
• Inventory. Agree which system posts the inventory movement. Use one posting owner for a receipt so a warehouse update and a Procurement message cannot increase stock twice. Separate accepted quantities, rejected quantities, returns and corrections.

• Supplier portal. Configure access to a supplier’s own invitations, responses, orders, acknowledgments and permitted performance information. Validate tenant and supplier boundaries before enabling external access. Uploaded qualification evidence waits for internal review.
• EDI. Scope purchase orders and acknowledgments with participating suppliers, including the applicable 850/855 versions and mappings. Keep the order revision and partner message identifier so duplicate or out-of-order acknowledgments cannot accept the wrong version.
• Punchout catalogs. Assess cXML or OCI support for each catalog supplier. Validate returned carts against approved suppliers, item mappings, prices and category rules before creating a request. A returned cart does not grant purchasing authority.

• Department systems. Accept requests from service management, facilities or other approved sources with a resolvable Requester, department, cost center and category. Incomplete requests wait for correction before entering approval.
• Directory. Map people, organizational units and budget owners from the maintained identity source. Disable departed users and resolve pending assignments before relying on the next synchronization.

• Vendor management layer. Exchange supplier identity, reviewed qualification evidence and performance with the responsible vendor-management process. Risk signals require the designated person’s status decision; a connector cannot silently reactivate a blocked supplier.

Retain source identifiers, document revisions, delivery status and actionable errors. Test replay, interruption and recovery before launch. Retry the same event without duplicating orders, receipts or commitments, and reconcile what the receiving system actually accepted. Historical imports use their own reviewed baseline and do not emit normal receipt or approval messages. Keep credentials in managed connections and restrict each identity to the actions it needs.