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

# Purchase order matching

> Hold every invoice against the order it belongs to, before anything is booked.

If you order before you buy, the purchase order is the agreement. PO matching holds every invoice against it, so a price that quietly went up does not get booked because nobody looked.

PO matching is optional, and it is part of some plans as an add-on. Switch it on under **Settings > PO matching**.

## Where the orders come from

<CardGroup cols={2}>
  <Card title="Exact Online" icon="database">
    Glimps syncs the purchase orders from your Exact Online administration.
  </Card>

  <Card title="Your own API" icon="plug">
    Glimps reads purchase orders from your own system through an API connection.
  </Card>
</CardGroup>

Some connections answer one order at a time. Those cannot be synced in bulk, so Glimps reads the order per invoice instead. You can always read an order again from the invoice itself.

Glimps reads every line of an order, also on long orders. An order or order line that was deleted in Exact Online is not offered for matching.

<Note>
  If Exact Online refuses purchase orders for an administration, **Settings > PO matching** shows **Exact refuses purchase orders for this administration**. The administration has no purchase module in Exact, or the connected Exact user has no rights on purchase orders. Fix it in Exact, then choose **Try again**. Glimps also checks once a week.
</Note>

## Switching it on

<Steps>
  <Step title="Pick the source">
    Exact Online, or your own API. Exact Online needs a working connection, and an API needs its endpoints configured.
  </Step>

  <Step title="Set the tolerances">
    How much difference between invoice and order you accept. See [Matching](/purchase-orders/matching#tolerances).
  </Step>

  <Step title="Decide on receipts and partial deliveries">
    Whether automatic processing waits until the goods are received, whether an invoice may match while some order lines are still open, and whether such a partial delivery may book by itself. See [Partial deliveries and receipts](/purchase-orders/matching#partial-deliveries).
  </Step>

  <Step title="Turn it on">
    From that moment, invoices carrying a purchase order number are held against the order.
  </Step>
</Steps>

<Note>
  You can tune the rules before you switch matching on. They take effect the moment you do.
</Note>

## Suppliers that never use orders

Not every supplier fits. Under **Relations without PO matching** you exclude suppliers, and their invoices go straight to your booking rules.

## The Purchase orders page

**Purchase orders** in the sidebar shows every order available for matching, plus the history of past match decisions.

* **All POs**: what is synced, what is still open, and what is matched.
* **Match history**: which invoice matched which order, and who decided what.

The counters tell you whether the sync is healthy. If the number of orders stays at zero, the source is not delivering.


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