> ## 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.

# When an invoice does not match

> What each purchase order stop means, and the four ways out.

A held invoice is not a bug. Glimps stops automatic booking for something that does not add up, and the invoice tells you what it found. A person can always finish it.

## What the stops mean

| Stop | What Glimps found |
| - | - |
| The unit price | The price per unit differs from the order |
| The quantity | More or fewer units than ordered |
| A line on one side only | A line on the invoice is not on the order, or the other way around |
| Which lines belong together | The pairing between invoice lines and order lines is not certain |
| The link to the purchase order | The order number on the invoice does not lead to a usable order |
| Purchase order not found | No order with the number on the invoice was found |
| Purchase order without open lines | The order is found, but its lines are already invoiced, or nothing is received yet |
| Outside tolerance | The difference is bigger than you allow |
| Not received yet | The goods are not recorded as received, and your setting requires that |

## Two kinds of stop

Every purchase order stop shows as **Automatic booking blocked**. What you can do depends on the kind of stop.

<CardGroup cols={2}>
  <Card title="A difference with the order" icon="scale">
    The price, the quantity or the total differs from the order. You can still send the invoice yourself. Glimps asks you to confirm with **Send anyway**, and records that you approved the difference.
  </Card>

  <Card title="An order that cannot be matched" icon="unlink">
    The order is not found, it has no open lines left, or the goods are not received. The warning offers **Book without PO**. This also works on Exact Online.
  </Card>
</CardGroup>

When you send an invoice whose order is not matched yet, Glimps tells you once: match the order, or choose **Book without PO**.

## The four ways out

<Steps>
  <Step title="Fix the reading">
    Check the invoice against the document. A misread quantity or price is the most common cause, and it is a two second fix.
  </Step>

  <Step title="Ask the person who knows">
    Use **Ask** under the three dots at the top of the invoice. The buyer knows whether the price went up, and the warehouse knows whether it arrived. The question carries the invoice with it, so they can answer in one go. See [Questions](/invoices/questions).
  </Step>

  <Step title="Accept the difference">
    If the difference is real and acceptable, confirm the match, or send the invoice and choose **Send anyway**. Glimps records who accepted it and what the difference was. An accepted difference is a decision with a name on it.
  </Step>

  <Step title="Book without the purchase order">
    Sometimes the order does not exist, its lines are already invoiced, or it belongs to a different process. Use **Book without PO**, then **Continue without PO**. You code the invoice lines yourself with a GL account and VAT code. There is no tolerance check, and the purchase order stays open in your accounting system. The choice is recorded. Changed your mind? Use **Book with PO after all**.
  </Step>
</Steps>

<Note>
  On Exact Online, **Book without PO** is offered when the order cannot be matched. A price or quantity difference is not a reason to drop the order: accept the difference instead. With your own API, **Book without PO** is always available.
</Note>

<Note>
  A manual decision lets you book this invoice. It does not turn automatic booking back on for it. That is on purpose: a person decided this one, so a person finishes it.
</Note>

## The order changed after the invoice arrived

Purchase orders move. Use **Read these POs again** on the invoice to pull the current version from the source.

If the new amounts are newer than the last check, Glimps says so and asks you to process the invoice again, so the decision is taken on the numbers you are looking at.

## The number format

If your purchase order numbers follow a house format, record it under **Settings > General**. Glimps then recognises a number in the document text, even when the supplier prints it in an odd place.

## Nothing matches at all

If no invoice ever matches, the problem is usually the source rather than the invoices:

* The sync brings in zero orders. Check the connection under **Settings > Integrations**.
* Exact Online needs reconnecting. The invoice list says so at the top.
* Exact Online refuses purchase orders for this administration. **Settings > PO matching** says so, with **Try again**. See [Purchase order matching](/purchase-orders/overview).
* The supplier is excluded from matching.
* The orders live in another administration.


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