Identify the item that requires approval through the workflow process.

In Oracle Payables, the Invoice Approval Workflow automates the routing of invoices to designated approvers based on predefined business rules. Standard invoices that are not matched to a purchase order typically require approval through this workflow to ensure proper financial authorization and coding before payment processing. Oracle's architecture explicitly excludes certain pre-authorized or legacy transactions from triggering this workflow to prevent redundant approvals. Because options B, C, and D represent these exact system-defined exclusions, unmatched standard invoices (Option A) remain the primary items that require routing through the Invoice Approval Workflow.

B. Oracle documentation explicitly states that legacy invoices existing in the system before the Invoice Approval Workflow feature was enabled are not routed for approval.
C. Expense reports imported via the Payables Expense Report Import Program are excluded because they are already approved within Oracle Internet Expenses prior to import.
D. Recurring invoices generated from a template bypass the workflow process if the "Approval Workflow Required" option was intentionally left disabled on that specific template.

1. Oracle Corporation. (2010). Oracle Payables User's Guide, Release 12.1 (Part No. E13624-05). Chapter 2: Invoices, Section: "Invoice Approval Workflow Overview". This section explicitly lists the transaction types that the workflow program does not route, matching options B, C, and D.

2. Oracle Corporation. (2009). Oracle Payables Implementation Guide, Release 12.1 (Part No. E12796-02). Chapter 3: Invoice Setup, Section: "Setting Up Invoice Approval Workflow". Details the configuration and default behavior for unmatched invoice routing.