> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useglimps.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Declined invoices

> What happens when an approver says no, and how you settle it.

A decline is information, not a dead end. The approver saw something you did not.

## Where declined invoices go

Open **Authorizations > Rejected**. Every declined invoice is here with its comment, who declined it, and how long ago. Each one has **Ask a question**, if you want to check something with a colleague first.

The cards at the top show how many there are, what they are worth together, and the average age. A stack of month old rejections is money nobody decided about.

## Settling one

<Steps>
  <Step title="Read the comment">
    The approver said why. Usually it is the amount, the coding, or something that was never delivered.
  </Step>

  <Step title="Fix what is wrong">
    Correct the coding, put the invoice on hold while you wait for a credit note, or ask the supplier for a corrected invoice. See [Notes and holds](/invoices/notes-and-holds).
  </Step>

  <Step title="Route it again">
    Click **Correct rejection** (in the table: **Correct**). Choose **Ask \[name] again** when the decline was a mistake, or pick another person, group, or flow. Earlier approvals stand when you pick a person or a group; a flow starts again at step 1. The old decision stays in the audit trail. Nothing is erased.
  </Step>

  <Step title="Or mark it as handled">
    If the outcome is that this invoice does not get paid, mark it as handled so it leaves the list. You can always show handled ones again with the filter.
  </Step>
</Steps>

## When your company books after approval

A declined invoice was never booked, so there is nothing to reverse in Exact. It goes back to the processing list as **Declined, not booked**, with **Ask again or correct** on its card. Fix it and click **Send**, and Glimps asks the approvers again because the invoice changed. See [Booking before or after approval](/approvals/book-after-approval#declined-invoices).

## Reassigning

You can also move an open approval to somebody else. Click **Reassign** on the invoice, or on its approval timeline, and add a reason if you like. Use this when the assigned approver is away and there is no delegate, or when the invoice clearly belongs to another department.

Both names and the reason are recorded.

### Moving to another flow

Sometimes the route itself is wrong, not the person. In the same **Reassign** list, pick a flow under **Move to another flow**.

* The approval starts again at step 1 of the new flow.
* Approvals already given are retired with the old route. They stay visible on the timeline.
* Only users and admins can choose another flow. An approver can hand off their own step, but cannot change the route.
* A declined invoice does not use this. Use **Correct rejection** to send it to another flow.

<Note>
  Reassigning is not the same as delegation. Delegation is set by the approver for a period. Reassigning is a one time move by a processor or an administrator. See [Delegation](/authorizers/delegation).
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.