Expense Receipts Approval Map - Supervisor Rule?

Hi, can you share a screen capture of both tab of the approuval map for the step and the rule: Conditions and Rule Actions? For the Step, you can specify to always execute it.

I am actually trying to add additional conditions besides limiting on “X” projects, but it is going through for all projects, not just “X” anyway.  The rule used to be “Supervisor Approval” but I changed it to Manager, but you can see that on the Expense, it is going to “Supervisor Approval” which isn’t even in the approval map anymore.

Thank you!

I tested the approval of expense receipts on my side and it is working as expected.

1- Is it possible that the approval map defined at the Time and Expenses Preferences is not the same as the one that we see here?

2- If the one defined at the Time and Preferences screen refers to this one, would it be possible to get as many screen captures as possible of the Conditions and the Rule Action for the rule and of the step?

Thank you,

Here is the one defined on the Time & Preferences screen:

There are a number of steps that follow the “Supervisor Approval” but they all work.  

Does your approval have a “Supervisor Approval” step?  Is it called that on your approval map?

Thanks

​@maggiel ,
Note: suggestion generate from AI

1. Editing the map doesn't retroactively change receipts that are already in "Pending Approval."
When a receipt is submitted, Acumatica evaluates the map at that moment and writes the resulting approval step(s) into the receipt's Approval Details. If you rename or deactivate a step after a receipt has already gone into Pending Approval, that receipt keeps the step assignment it was given at submission time — it won't pick up your edits. That's almost certainly why you're still seeing "Supervisor Approval" on a receipt even though you renamed/removed that step. To test your changes, you need a new receipt (or take an existing one On Hold and re-Submit it, which re-evaluates the map from scratch).

2. Renaming a step doesn't change who it routes to.
The step's Description (what you edited to "mgr Approval"/"Manager") is just a label. The actual approver is set on the Rule Actions tab of that step. So even a correctly-renamed step will still send to whoever is configured there (e.g., "Employee's Supervisor" via the Reports-To hierarchy on the Employee screen) unless you also change the Rule Actions.

3. Check for a second, condition-less rule catching everything.
Your tree shows three branches — Capital, manager, Non-Project — each with its own step (COO Approval, mgr Approval, Bus Admin). If a receipt can match more than one branch, or if any step has no conditions (or a condition row that's blank/inactive) sitting alongside your "Project/Contract Equals X" row, that step will fire for every document regardless of project. Worth checking:

• Is there more than one condition row under this step, and is the Bracket column combining them the way you expect (AND vs. OR)?
• Is there a step elsewhere in the map with zero conditions acting as a catch-all default?
• Is the row's Active checkbox (the one in the grid, not just the step-level Active checkbox) actually checked the way you think?

4. Double-check EP101000 is pointing at this exact map.
Worth confirming the Expense Receipt Approval Map field really says "Expense Receipts" and not a similarly-named map — easy to mix up if there's more than one.

If you want, tell me what's on the Rule Actions tab for the old "Supervisor Approval" step (or post it) and I can help pin down exactly why it's still firing.