Axya supports electronic data interchange with your trading partners using the cXML (commerce eXtensible Markup Language) standard. Automate the exchange of purchase orders, order confirmations, shipping notices, and invoices between your procurement system and your suppliers — without manual data entry.
cXML is an industry-standard XML format used in procurement and supply chain management. It enables platforms like SAP Ariba, Coupa, and other procurement systems to communicate directly with supplier systems.
Axya acts as a cXML-capable endpoint — it can both send and receive cXML documents, allowing seamless integration with any trading partner that supports the standard.
Sending POs to Suppliers (Outbound):
When a purchase order is created or revised in Axya, it can be automatically sent to the supplier's cXML endpoint:
Receiving POs from Buyers (Inbound):
Axya can receive purchase orders from external procurement systems:
Direction: Inbound (Supplier to Axya)
When a supplier responds to a purchase order, Axya processes the confirmation intelligently:
Nothing is auto-applied. Proposed changes always require buyer approval before taking effect.
The buyer receives an email notification when a supplier proposes changes.
Direction: Inbound (Supplier to Axya)
When a supplier ships goods, they send an Advance Ship Notice (ASN) via cXML:
Direction: Inbound (Supplier to Axya)
Suppliers can submit invoices electronically:
| Document | Inbound | Outbound |
|---|---|---|
| Purchase Orders | Receive and auto-create POs | Send POs and revisions to suppliers |
| Order Confirmations | Receive, auto-acknowledge, or create revision proposals | — |
| Shipping Notices | Receive and update line-item shipment data | — |
| Invoices | Receive and link to POs | — |
Each supplier (or buyer-supplier pair) that exchanges cXML documents with Axya is set up as a Trading Partner. Configuration includes:
| Setting | Description |
|---|---|
| Name | A friendly name for the partner (e.g., "Motion Industries") |
| cXML Identity | The partner's cXML identity (organization ID or DUNS number) |
| cXML Domain | The cXML domain identifier used for routing documents |
| Endpoint URL | Where Axya sends outbound documents |
| Buyer Company | Which buyer this configuration applies to (optional — can apply to all buyers) |
| Supplier Company | The supplier company linked to this partner |
| Attachment Support | Whether the partner can receive file attachments (e.g., PDFs) in cXML |
You can configure multiple trading partners for the same supplier if different buyers require different settings.
| Measure | Details |
|---|---|
| Authentication | Each trading partner uses an encrypted shared secret. Inbound cXML is verified against the stored secret before processing. |
| Encrypted storage | Shared secrets are encrypted at rest — never stored in plain text. |
| Partner validation | Inbound documents must include valid credentials matching an active trading partner. Unknown or inactive partners are rejected. |
| Transport security | All cXML communication uses HTTPS (TLS 1.2+). |
Every cXML document exchanged through Axya is fully logged:
When things go wrong:
To set up EDI / cXML integration with your trading partners:
For setup assistance, contact customerservice@axya.co or reach out to your Axya account representative.