A direct payment or quick expense can be rejected during its after-the-fact review even though the money already left the account. Nothing reverses on its own when that happens. This article explains...
Last updated
A direct payment or quick expense can be rejected during its after-the-fact review even though the money already left the account. Nothing reverses on its own when that happens. This article explains what you will see and what you can do about it.
On the expense list, the row keeps its Paid status and gains a second, warning-coloured tag underneath it, so it is easy to spot without opening anything.
Inside the expense, you will see a flag stating that the review was rejected, and naming the person who rejected it.
By email, whoever recorded the expense (and only that person) gets an email explaining that the review was rejected and that the payment is still standing.
Nobody else is notified. The reviewer's decision does not get broadcast to the whole approval chain, and it does not go to anyone but the person who recorded the expense.
A rejected review means a reviewer disagreed with the expense after it was already paid. Automatically undoing the payment would hide that disagreement and quietly move the money a second time, which is worse than leaving a visible flag. Instead, URBI leaves the payment exactly as it is and puts the decision in front of the person who recorded it.
Once you see the rejected flag, you have a real choice, not a forced action:
You will find these actions on the expense itself, from its own action menu.
None of this applies to a vendor bill. A vendor bill is never paid before it is approved, so a rejection there simply stops it before any money moves. There is nothing to refund, void, or resubmit, because nothing was ever paid.