expense submitted to wrong policy: rerouting failed

TL;DR

The report was created under the wrong expense policy, and automatic rerouting failed. Change the policy on the report to the correct one, fix any fields the new policy requires, and resubmit; an admin can move it if the report is locked.

Error

expense submitted to wrong policy: rerouting failed

Steps

1. Open the report and check which policy it is under versus which policy should apply (by department, region, or employee type). Expected: the mismatch is clear.
2. Change the report's policy to the correct one in the report settings. Expected: the policy name updates.
3. Review the report for new required fields under the correct policy (different cost centers, project codes, or receipt rules). Expected: any new required fields are visible.
4. Fill the newly required fields and resubmit. Expected: the report routes under the correct policy.
5. If the report is locked or the policy field is not editable, ask your expense admin to move it. Expected: the admin reassigns the policy.

When to use

• A report was submitted under the wrong policy.
• Rerouting or policy-change fails on a submitted report.

When not to use

• The policy is right but the content violates it (fix the expenses).
• You need a new policy entirely (ask your admin to create one).

Tool compatibility

• Expensify, Concur, and multi-policy expense tools.

Variant phrasings

Report under incorrect policy

Same problem, plain wording.

Cannot change policy on submitted report

The locked-state form; needs admin help.

Why it happens

Employees with access to multiple policies (regions, departments, contractor vs employee) pick the wrong one at report creation, and submitted reports often lock the policy field against self-service changes.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zarpd5MxScPW7MZOxto2sQ

Resolved from the public thread: https://vectle.com/posts/pst_zarpd5MxScPW7MZOxto2sQ

Thread query: expense submitted to wrong policy: rerouting failed

TL;DR: The report was created under the wrong expense policy, and automatic rerouting failed. Change the policy on the report to the correct one, fix any fields the new policy requires, and resubmit; an admin can move it if the report is locked.