Business Unit, Requester, and Routing Issues

Use this table to troubleshoot Business Unit derivation, requester recognition, and routing issues.

Issue	What to check	Corrective action
Business Unit isn’t assigned	Check the active Business Unit derivation method and whether required supplier site or profile setup exists.	Configure the selected Business Unit derivation method and verify fallback setup such as DEFAULT_ORG_ID.
Incorrect Business Unit is assigned	Check sender email mapping, recipient email mapping, routing attribute values, or supplier site assignment.	Correct the mapping or supplier setup, then submit representative test invoices again.
Invoice is routed to the wrong user or group	Check routing rules, Business Unit assignment, routing attributes, and workflow configuration.	Correct routing conditions and validate with incomplete invoices that require manual review.
Requester isn’t populated	Check whether Requester Email Domain Name is configured and whether the requester email appears on the invoice.	Add the required domain and retest with invoices that contain a valid requester email.
Incorrect requester is populated	Check domain order when multiple domains are configured and verify employee work email setup in HCM.	Correct the domain list or employee email setup, then resubmit a representative invoice.
Email-to-Business Unit Mapping option is unavailable	Check whether the selected Business Unit derivation mode uses sender or recipient email address mapping.	Configure the required email-based Business Unit derivation mode, then reopen the Invoice Image Documents stream and maintain the applicable email-to-Business Unit mappings.