---
title: Intégration d'Epicor Kinetic avec Axya pour le module PO
description: This article explains how the Axya Purchase Order (PO) module integrates with Epicor Kinetic to manage PO transmission, supplier confirmations, revisions, date changes, and receipts. It details the full feedback loop between Epicor, Axya, and suppliers, ensuring accurate data synchronization, revision control, and supplier performance tracking.
---

[Passer au contenu](https://www.outsourcing.axya.co/knowledge/intégration-depicor-kinetic-avec-axya-pour-le-module-po#main-content)

Français

Afficher le sous-menu pour les traductions

[![Logo Axya for light background](https://www.outsourcing.axya.co/hubfs/Logo%20Axya%20for%20light%20background.svg)](https://axya.co)

- axya.co

Ouvrir la navigation principale

Fermer la navigation principale

- axya.co
- Français
  
  Afficher le sous-menu pour les traductions
- [Contact](mailto:customerservice@axya.co)

[Contact](mailto:customerservice@axya.co)

 Comment pouvons-nous vous aider ?

- Il n'y a aucune suggestion car le champ de recherche est vide.

1. [Base de connaissance / Knowledge Base](https://www.outsourcing.axya.co/knowledge?hsLang=fr)
2. [Intégration](https://www.outsourcing.axya.co/knowledge/int%C3%A9gration?hsLang=fr)

# Intégration d'Epicor Kinetic avec Axya pour le module PO

## This article explains how the Axya Purchase Order (PO) module integrates with Epicor Kinetic to manage PO transmission, supplier confirmations, revisions, date changes, and receipts. It details the full feedback loop between Epicor, Axya, and suppliers, ensuring accurate data synchronization, revision control, and supplier performance tracking.

<iframe src="https://www.loom.com/embed/c73365b856e8404c9afc05917817660a" frameborder="0" webkitallowfullscreen="" mozallowfullscreen="" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe>

 

---

### 1. Sending a Purchase Order from Epicor to Axya

#### Key Steps

1. Open a **Purchase Order** in Epicor Kinetic.
2. Review:
   
     - **PO number**
     - **Supplier**
     - **Buyer (PO owner)**
3. Set the **Axya Status** to **Send to Axya**.
4. Save and approve the PO.

![generated-image-at-00:00:31](https://loom.com/i/1a7acf784f954935be92b4c405bb1128?workflows_screenshot=true)

#### Result

- The PO is synchronized to Axya based on the configured sync frequency (**every 1 to 5 minutes depending on your IT configuration**).
- The PO is automatically sent to the supplier via Axya's email delivery system and tracked onwards within Axya interface for buyers.
- Ownership in Axya is assigned to the same buyer as in Epicor.
- Supplier mapping is done using the **vendor code**.

---

### 2. Purchase Order Structure in Axya

#### Line and Release Management

- Axya reflects:
  
    - **Lines**
    - **Releases per line**
- Each release includes metadata such as:
  
    - Quantity
    - Unit price
    - Due date
    - Promise date

This structure allows granular tracking of supplier commitments at the **release level**.

![](https://www.outsourcing.axya.co/hs-fs/hubfs/0-png.png?width=670&height=197&name=0-png.png)

---

### 3. Supplier Confirmation Workflow

![generated-image-at-00:05:11](https://loom.com/i/60ca76f085204fc3aa40d467aa116eaf?workflows_screenshot=true)

#### Initial Confirmation

- Once the supplier confirms the PO in Axya:
  
    - Axya sends the confirmation back to Epicor at the next sync.
    - The PO status updates to **PO Confirmed** in Epicor.
    - Confirmation dates are populated at the **release level**.

#### Date Handling Logic (Configurable)

- **Due Date**:  
  Can represent the *initial confirmed date* (frozen).
- **Promise Date**:  
  Can represent the *latest approved supplier commitment* (continuously updated).

> This logic is fully configurable per client and can be reversed depending on planning and KPI needs.
> 
> ![](https://www.outsourcing.axya.co/hs-fs/hubfs/image-png-Feb-05-2026-07-41-56-8664-PM.png?width=670&height=296&name=image-png-Feb-05-2026-07-41-56-8664-PM.png)

---

### 4. Revisions Triggered by Quantity or Price Changes

#### Buyer-Initiated Changes

- Changes to **quantity** or **price** in Axya:
  
    - Trigger a **PO revision**
    - Automatically:
      
          - Increment the revision number on Axya (e.g., REV01, REV02)
          - Reprint the PO PDF from Epicor
          - Resend the updated PO to the supplier
- The PO status in Epicor reverts to **Successfully Sent** until reconfirmed by vendor.
  
  ![](https://www.outsourcing.axya.co/hs-fs/hubfs/image-png-Feb-05-2026-07-43-38-6028-PM.png?width=670&height=290&name=image-png-Feb-05-2026-07-43-38-6028-PM.png)

#### Supplier-Proposed Changes

- If a supplier proposes quantity or price changes:
  
    - Buyer approval is required before:
      
          - Updating Epicor
          - Triggering a revision
          - Sending a new PDF to the supplier

#### PDF Version History

- Axya maintains a **full history of PO PDFs**, including:
  
    - Original version
    - All revised versions
- Each revision is timestamped for auditability.

---

### 5. Date Changes Without Revisions

- **Date-only changes** (approved by the buyer):
  
    - Update Epicor
    - **Do not trigger a new revision**
    - **Do not require supplier reconfirmation**
- Dates are managed at the **release level**.

![](https://www.outsourcing.axya.co/hs-fs/hubfs/image-png-Feb-05-2026-07-44-23-8424-PM.png?width=670&height=248&name=image-png-Feb-05-2026-07-44-23-8424-PM.png)

---

### 6. Initiating Revisions from Epicor

#### Axya Revision from ERP

Buyers can:

- Add or remove lines
- Change quantities
- Change unit prices

By setting the Axya status to **Send Revision** and approving:

- Axya detects the changes at the next sync
- A new revision is generated

A new PDF is sent to the supplier for reconfirmation

![](https://www.outsourcing.axya.co/hs-fs/hubfs/image-png-Feb-05-2026-07-44-58-7477-PM.png?width=670&height=316&name=image-png-Feb-05-2026-07-44-58-7477-PM.png)

![](https://www.outsourcing.axya.co/hs-fs/hubfs/image-png-Feb-05-2026-07-45-35-7052-PM.png?width=670&height=288&name=image-png-Feb-05-2026-07-45-35-7052-PM.png)

---

### 7. Draft Purchase Orders

#### Send as Draft

- Similar to **Send to Axya**, but:
  
    - The PO is created as a **draft** in Axya
    - No email is sent to the supplier initially
- Use case:
  
    - Add **technical documents or attachments within Axya's environment before sending to the vendor as a single email event.**

Once ready, the PO can be sent to the supplier directly from Axya.

---

### 8. Receipt Synchronization and Archiving

#### Goods Receipt

- Receipts are performed **in Epicor as usual**
- Axya automatically captures:
  
    - Quantity received
    - Receipt date
    - Line and release status

![](https://www.outsourcing.axya.co/hs-fs/hubfs/image-png-Feb-05-2026-07-46-31-2004-PM.png?width=1906&height=800&name=image-png-Feb-05-2026-07-46-31-2004-PM.png)

#### Impact

- Enables **on-time delivery KPIs**
- Supports supplier performance analytics
- Prevents follow-ups on fully received lines

#### Archiving

- When all lines and releases are fully received:
  
    - The PO is moved from **Ongoing** to **Archive** in Axya

---

### **Procedure for Cancelling an Order in Axya**

#### **1. Cancelling an Order No Longer Required**

If you need to cancel an order because it is no longer needed:

1. Log in to the Axya platform.
2. Go to the **Orders** tab.
3. Search for the order using the search bar.
4. Once on the order page, click the three dots in the top right corner.
5. Select **Cancel Order**.
6. You may then delete this order in Epicor.
   
   ![](https://www.outsourcing.axya.co/hs-fs/hubfs/undefined-Dec-05-2025-11-31-01-3208-AM.png?width=670&height=544&name=undefined-Dec-05-2025-11-31-01-3208-AM.png)

---

#### **2. Cancelling an Order Sent to the Wrong Supplier**

If you accidentally sent the order to the wrong supplier:

1. Cancel the order by following the previous steps.
2. Email **customerservice@axya.co** to request deletion of the transaction in Axya.

Once the transaction is deleted, you can:

- Modify the PO in Epicor
- Resend it through Axya to the correct supplier

⚠️ **Important:**  
If the transaction is not deleted in Axya, you will not be able to resend the order to the correct supplier, as it still exists in the database. Step 2 is therefore essential.

---

#### **Need Help?**

If you have any questions or issues, contact our team at:  
📧 **customerservice@axya.co**

- [Général](https://www.outsourcing.axya.co/knowledge/g%C3%A9n%C3%A9ral?hsLang=fr)
- [Utilisateurs acheteurs](https://www.outsourcing.axya.co/knowledge/utilisateurs-acheteurs?hsLang=fr#main-content)

    - [Général](https://www.outsourcing.axya.co/knowledge/utilisateurs-acheteurs?hsLang=fr#g%C3%A9n%C3%A9ral)
    - [Module RFQ](https://www.outsourcing.axya.co/knowledge/utilisateurs-acheteurs?hsLang=fr#module-rfq)
    - [Module PO](https://www.outsourcing.axya.co/knowledge/utilisateurs-acheteurs?hsLang=fr#module-po)
- [Utilisateurs fournisseurs](https://www.outsourcing.axya.co/knowledge/utilisateurs-fournisseurs?hsLang=fr#main-content)

    - [Général](https://www.outsourcing.axya.co/knowledge/utilisateurs-fournisseurs?hsLang=fr#g%C3%A9n%C3%A9ral)
    - [Module RFQ](https://www.outsourcing.axya.co/knowledge/utilisateurs-fournisseurs?hsLang=fr#module-rfq)
    - [Module PO](https://www.outsourcing.axya.co/knowledge/utilisateurs-fournisseurs?hsLang=fr#module-po)
- [Intégration](https://www.outsourcing.axya.co/knowledge/int%C3%A9gration?hsLang=fr)

- axya.co

[![Logo Axya for light background-1](https://www.outsourcing.axya.co/hubfs/Logo%20Axya%20for%20light%20background-1.svg "Logo Axya for light background-1")](http://www.axya.co)

customerservice@axya.co

Copyright © 2025, Axya