Start with the decision, not the hierarchy.

Effective AP approval design separates two questions: why does an invoice require approval, and who is accountable for it? Conditions define the control. Data sets manage changing ownership.

Data sets turn many rules into one maintainable policy.

A data set is a reusable mapping table. For example, one high-value-invoice rule can route to a different finance approval group depending on the invoice distribution cost center.

Four practical routing patterns.

01 — Finance approval by cost center

For invoices at or above a financial threshold, use a data set to select the correct approval group by business unit and cost center—rather than creating one rule for every department.

02 — Non-PO invoice ownership

Route non-PO invoices to the requester’s manager. If requester details are missing, reject the invoice or send it to an AP exception queue before the workflow begins.

03 — Project and asset controls

Project-coded invoices can route to the project manager, while higher-value asset invoices can require both cost-center owner and asset-accounting approval.

04 — Source-based approval paths

Low-risk recurring invoices from controlled sources can follow a streamlined path. Manually entered, high-value non-PO invoices should receive additional scrutiny.

Hidden capabilities worth using.

Invoice approval rules can use more than header data. Oracle Fusion exposes fields from invoice lines, distributions, requesters, suppliers, purchase orders, projects, holds, assets, and descriptive flexfields. Workflow notifications can also be tailored to show decision-ready details such as supplier, amount, due date, match status, cost center, project, and the invoice image.

A short go-live test pack.

Test low-value PO-matched invoices, high-value invoices for each major cost center, non-PO invoices with and without a requester, project-coded and asset-related invoices, multiple distributions, inactive approvers, and rejection or resubmission paths.