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

# Matching an invoice

> How Glimps decides that an invoice and an order belong together, and the tolerances you set.

Glimps takes the purchase order numbers off the invoice, fetches those orders, and compares them. The comparison happens on the numbers, not on a hunch.

## What Glimps compares

1. **Which lines belong together.** Descriptions rarely match word for word, so Glimps also uses the article numbers, including the supplier's own article number. The arithmetic decides whether the pairing holds.
2. **Quantity and unit price** per pair.
3. **The totals**, excluding VAT.
4. **Lines that exist on one side only.**

The invoice shows the result line by line, with the invoice on one side and the order on the other.

A price difference stays on the lines where it occurs. Glimps does not put the whole difference on one order line.

<h2 id="tolerances">
  Tolerances
</h2>

You set two limits: an amount in euros, and a percentage. Then you say how they work together.

| Logic | Meaning |
| - | - |
| Either condition | The difference is accepted if it is within the amount **or** within the percentage |
| Both conditions | The difference is accepted only if it is within the amount **and** within the percentage |

Glimps shows a worked example under the setting, so you can see the range a thousand euro order would accept.

A difference inside the tolerance matches quietly. A difference outside it holds the invoice and names the reason.

Glimps measures the difference only against the order lines that the invoice covers, not against the whole order. When an invoice covers part of an order, the message names both amounts: the order lines on this invoice, and the order total. The rest of the order is still open.

<h2 id="partial-deliveries">
  Partial deliveries and receipts
</h2>

* **Allow partial match**: an invoice may match while some order lines are not delivered or invoiced yet.
* **Book partial deliveries automatically**: shown when partial match is on, and off by default. When an invoice covers part of an order and every line matches the order, Glimps books it by itself. The rest of the order stays open for the next invoice.
* **Only match after receipt**: invoices are only processed automatically once Exact shows the goods as received. You can always process them yourself. This is the strict, three way version.

## Matching by hand

Open the invoice and choose **Match POs** in the purchase order section. After a match the button reads **Update Matching**, and after a failed match **Review PO match**. In the modal you can:

* Add a purchase order number the reading missed.
* Search for an order with **Search a PO...**, by order number, supplier or article. When an article finds the order, the result says which one, for example **Article: ...**.
* Compare lines side by side.
* Search the lines by description, article, amount or line number. Every word you type must match. Press `/` to jump to the search box.
* Switch on **Only differences** to see only the lines that differ.
* Read an order again from the source, in case it changed since the invoice arrived.

The search only changes what you see. The totals and the match always use every line.

On Exact Online, the invoice shows the **Exact PO Matching** panel in place of the coding table. One search box there covers the invoice lines and the PO lines together.

If the totals sit outside the tolerance, you can still confirm. Glimps records who accepted the difference.

<Warning>
  An order that belongs to another supplier cannot be selected, and an order that is already matched to another invoice says so. Both of those are usually a typo in the number.
</Warning>

## Costs that were never ordered

Transport, shipping, and handling are on the invoice but not on the order. That is not a mismatch, it is how suppliers invoice.

Under **Settings > PO matching > Cost rules** you say what to do with them. When a keyword appears in a line description, Glimps books that amount to a chosen Exact item, with an optional VAT code and cost center of its own. Rules run in priority order, lowest number first.

Typical keywords: transportkosten, shipping, freight, orderkosten.

## Credit notes on Exact Online

On Exact Online, a credit note does not go through PO matching. Glimps keeps the order number as a reference on the booking, so you can still find the order it belongs to.

## After a match

A matched invoice carries the order numbers and the matched amount. It then continues along the normal road: approval if your rules ask for one, then booking. See [Sending to Exact Online](/booking/sending).

Each booked line takes its article from the order line. Before sending, Glimps checks that every article on the order is set up as a purchase item in Exact. If one is not, Glimps names that article, so you can fix it in Exact first.

If Exact refuses the booking, the invoice does not stay marked as matched. Fix the cause, then match and send again.


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