Oracle Invoice Payables Workflow – Part 1

 Oracle Fusion Expenses: Common Expense Report Errors and How to Fix Them

If you’ve worked with Oracle Fusion Expenses, you already know one simple truth: creating an expense report should be easy… but sometimes the system has other plans. Users run into errors that seem random, confusing, or just plain annoying — and most of the time, they come straight to support asking, “Why is this happening?”

The reality is, these issues are usually common, predictable, and fixable. Once you understand what’s driving them, you can resolve the error in minutes instead of going down a rabbit hole of troubleshooting.

In this blog, I’ll walk through the most typical errors that show up during expense report creation, what actually causes them behind the scenes, and the simple, practical fixes that will save you (and your users) time and frustration. No jargon, no over‑complication — just clear explanations and straightforward solutions.

Let’s get into it.

Error 1:  Employee Related Setup

Error:

-  The person type can't be derived because an HCM assignment doesn't exist for the person, or isn't active as of the expenditure item date. (PJC-2220072)

-  Ensure that the person or assignment is active as of the expenditure item date and has a valid user person type that's mapped to the internal person type of Employee or Contingent Worker

- A job isn't defined for the person assignment in the human resources application. (PJC-2220499)

-You must provide an expenditure organization for this transaction. (PJC-2220145)

Solution:

This error is usually due to incorrect Employee setup in Oracle HCM- assign employees appropriate assignment, department and a Manager (if approval rules are set as Supervisory)- this should solve the issue immediately. Additionally ensure- the employee Assignment Date is less than Expense Report Date.

Error 2: Missing Expense Account on Employee

Solution: To resolve this issue ensure the employee Expense Account is entered- also ensure you submit the update record in HCM

Error 3: This error is typically seen if you have enable Project Based expense reports

The expenditure type isn't valid for the project unit of the project. (PJC-2220046)
Cause The expenditure type isn't assigned to the reference data set for the project unit.
Action Assign the expenditure type to the reference data set for the project unit and then reprocess.

Solution:  Assign the default expenditure type to the expense type if you need want POET to be captured- additionally if there are SLA derivation rules set in AP to derive any segment value based out of Expenditure type ensure those setups are also done correctly.

If you know of any other common errors while entering expense reports let me know- and we can work together to expand this list.