Automated purchase order exception creation from emails

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Automated purchase order exception creation from emails

    This feature enables automatic creation of purchase order exceptions or universal requests from emails sent by registered supplier contacts. It uses the Email Intent to Action Agentic workflow, which analyzes incoming supplier emails to identify their intent and then executes appropriate actions. This automation streamlines handling of supplier communications related to purchase orders, improving efficiency for operational buyers.

    Show full answer Show less

    Key features

    • The Email Intent to Action Agentic workflow processes supplier emails in English, French, Canadian French, German, Japanese, and Dutch.
    • It requires suppliers to include specific identifiers in their emails to link the message to the relevant purchase order line:
      • ERP purchase order (PO) and purchase order line (POL) IDs
      • ServiceNow PO number or ERP PO number if the purchase order contains only one line
    • When multiple purchase order lines are referenced in one email, separate purchase order exceptions are created for each line.
    • If the email content is unclear, unrelated to purchase orders, or references unknown purchase orders, a universal request is created instead.
    • Suppliers receive email notifications when purchase order exceptions or universal requests are created.
    • A banner marks purchase order exceptions created by the agentic workflow, and the original email is logged in the Activity stream for buyer review.

    Prerequisites and configuration

    • Configure the [snsupplier.slmemail] system property with the supplier email address.
    • Use the same inbox for purchase order exceptions and supplier case creation (if applicable).
    • Deactivate the "Create Supplier case for email" inbound action to prevent conflicts.
    • Activate the "Trigger Intent to Action" inbound action to enable the workflow invocation.
    • Set the snunireq.universalrequestportal property to "Supplier" to ensure universal requests correctly link suppliers to the Supplier Collaboration Portal.

    Key outcomes

    • Automated and accurate creation of purchase order exceptions from supplier emails reduces manual processing.
    • Operational buyers gain visibility into exceptions created by the workflow and can track source emails for validation.
    • Suppliers receive timely notifications and can interact with universal requests via the Supplier Collaboration Portal if needed.
    • Support for multiple languages enhances supplier communication globally.

    Emails sent by a registered supplier contact are automatically converted to purchase order exceptions or universal requests by using the Email Intent to Action Agentic workflow.

    The Email Intent to Action Agentic workflow analyzes incoming supplier emails, identifies the email intent, and executes associated actions using the Intent Identification and Intent Executor agents. For more information on the Email Intent to Action Agentic workflow, see Email Intent to Action Agentic Workflow.

    The workflow can process supplier emails in any of these languages: English, French, Canadian French, German, Japanese, or Dutch.

    Suppliers must provide one of the following IDs in their email to identify the relevant purchase order line:
    • ERP purchase order (PO) and purchase order line (POL) IDs
    • ServiceNow® PO number or ERP PO number when the purchase order contains only one line

    Prerequisites for automated creation of purchase order exceptions

    To use this functionality, verify that the following steps are completed:
    • Configure the [sn_supplier.slm_email] system property. Edit the Value field to contain supplier email address. For more information, see Configure properties for Supplier Case Management.
      Note:
      If you plan to use or are using the SLO Supplier inbox for scenarios such as supplier case creation, you must use the same inbox for creating purchase order exceptions.
    • Deactivate the Create Supplier case for email inbound action. For more information, see Deactivate Create supplier case from email inbound action.
    • Activate the Trigger Intent to Action inbound action. To learn how to enable and configure intent to action workflow to invoke the agentic workflow from inbound actions, see Enable intent to action workflow from inbound actions.
    • Set the sn_uni_req.universal_request_portal property value to Supplier. This step supports supplier user experience cases where a supplier email can't be automatically converted to a purchase order exception. Instead, a universal request is created in the Supplier Collaboration Portal and the supplier receives an email with a link to the universal request created. For the link to correctly direct the supplier to the Supplier Collaboration Portal, the sn_uni_req.universal_request_portal property value must be set to Supplier.
    When a supplier sends an email to the configured email address, the Intent Executor Agent then implements the associated action based on the following conditions:
    • If the email contains a purchase order line related information, a purchase order exception is created.
    • If an email includes details for multiple purchase order lines, separate purchase order exceptions are generated for each line.
    • If the email contains unclear information or questions not related to purchase order exceptions, a universal request is created.
    • If the purchase orders and purchase order lines mentioned by the supplier can't be found in the system, a universal request is created.
    The supplier receives an email notification when a purchase order exception or a universal request is created. A banner appears on purchase order exceptions created by the agentic workflow, indicating that an agent created them. The originating email content is added as an entry in the Activity stream, allowing operational buyers to review agent actions and flag any discrepancies.
    Note:
    • The supplier email must contain one of the following identifiers for the purchase order line:
      • ERP purchase order (PO) and ERP purchase order line (POL) IDs
      • ServiceNow® purchase order line number
      • ServiceNow® purchase order number when it contains only one line
    • The workflow processes emails in any of these languages: English, French, Canadian French, German, Japanese, or Dutch.