{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":49673,"path":"source-to-pay-operations/accounts-payable-operations/email-parser-agent-for-apo.md","title":"Email parser agent for APO","bundle":null,"doc_type":null,"release":"australia","body":"\n# Email parser agent for APO\n\nThe Email parser AI agent processes incoming emails from suppliers and invoice owners. This agent identifies and classifies actionable requests, and routes them to the appropriate workflows to create invoice cases.\n\nThe agent intelligently distinguishes between request types such as invoice inquiries, payment inquiries, payment acceleration requests, and payment term updates. This verifies that each query is categorized correctly and routed to the appropriate business process.\n\n## Key benefits\n\n-   Reduced manual triage: Automated classification eliminates the need for manual email review and routing.\n-   Faster query resolution: Structured data extraction enables quicker case creation and response.\n-   Consistent categorization: All queries are classified using the same criteria, ensuring uniform handling across your organization.\n-   Improved supplier experience: Suppliers receive faster acknowledgment and status updates on their requests.\n\n## How it works\n\nAs a prerequisite, you must set:\n\n-   Inbound email action- Trigger Intent to Action to true\n-   Email properties-Inbound email configuration to true\n\nWhen a supplier or invoice owner sends an email, the agent receives and processes the message. The agent identifies the sender's email address and validates that the sender is a registered, active supplier contact. It then analyzes the email content to determine whether it contains one or more of the following Accounts Payable Operations request types: invoice inquiry, payment inquiry.\n\nIf the email matches one of the recognized request types, the agent extracts the relevant details and maps the request type to the appropriate case category and subcategory. The agent then initiates a case creation workflow. Informational emails that don't contain actionable requests aren't processed.\n\n## Case creation behavior\n\nThe email parser agent follows these case creation rules:\n\n-   For emails with one or more recognized request types, a case is created with the appropriate category and subcategory.\n-   For emails with no recognized request types \\(non-actionable or informational emails\\), no case is created. The email is archived.\n\n"}}