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

# Sending to Exact Online

> How an invoice is booked, what has to be true first, and what the send options mean.

Booking is the last step. Glimps posts the invoice in your purchase journal and records the purchase entry it got back.

## Sending one invoice

Open the invoice and click **Send**. For an invoice with purchase orders from an external system, the button says **Book with PO**, and the menu next to it offers **Book without PO**. For an invoice with an Exact Online purchase order, the menu only offers **Book without PO** when the order cannot be matched, for example because its lines are already invoiced or the order is not found.

## What has to be true first

Glimps only books an invoice when every one of these holds:

* The invoice has a number, a type (invoice or credit note), an invoice date, a financial year and period, and a currency.
* It has payment terms or a due date. One of the two is enough. The fields only turn red when both are empty.
* A supplier is known, and it exists in Exact Online.
* Every line has a ledger account, and a VAT code where your settings require one.
* The math check passed. If it failed, correct the lines so they add up.
* No changed bank account is waiting for confirmation.
* The purchase order matched, or somebody chose to book without it.
* The contract matched, where the contract register applies.
* The invoice is not on hold.
* A purchase journal is set.

If one of them fails, the button refuses and the invoice says which one. If the purchase order is not matched, the invoice says so once and names the way out: match the order, or choose **Book without PO**.

Two things do not stop you, only automatic booking:

* **A suspected duplicate.** The invoice warns you and names the invoice it matched. If you know it is not a duplicate, you can send it. Automatic booking stays off for it.
* **An open approval.** By default Glimps books the invoice with a payment block and lifts the block after the last approval. If your company books after approval, **Send** asks the approvers and Glimps books the invoice after the last approval. See [Booking before or after approval](/approvals/book-after-approval). See [Why an invoice is not booked](/troubleshooting/invoice-not-booked).

<Note>
  These conditions are checked in Glimps at the moment of sending, not only in the screen. That is why an invoice sometimes refuses although the screen looks clean: something changed since you last loaded it. Reload the invoice and the notice appears.
</Note>

## What happens when you click Send

* **Unsaved changes are saved first.** Glimps does not ask. Clicking **Send** means: book what is on the screen.
* **One question per click.** If Glimps asked you about the purchase order, it does not also ask in the same click whether to save a booking rule for the supplier. That question comes back with a later invoice from this supplier.

## Automatic booking

An invoice that needs nothing from anybody can be booked without a click. That is what zero-touch means. Whether it happens is your decision, not Glimps's, and you make it per supplier.

Under **Settings > Booking rules > Relations** every supplier sits at one of three levels:

| Level | What Glimps does | What you do |
| - | - | - |
| Manual | Nothing | You process and book everything yourself |
| Prepare | Gets the booking ready, with the coding it recognises already filled in | You check it and you book |
| Book automatically | Books the invoice in Exact Online itself | You see it the next morning and correct what is off |

A supplier with no level of its own follows the company default at the top of the same screen. A new administration starts on **Prepare**, so nothing books itself until you say so.

Two things hold at every level. An invoice that fully matches a purchase order is booked straight away, because it was approved when the order was placed. And an invoice Glimps is unsure about comes to you first: a new supplier, an unusual amount, a changed bank account.

Automatic booking also stays off for an invoice where a person made a manual decision, such as accepting a purchase order difference. A person started it, so a person finishes it.

### Moving a supplier up

You can set a level by hand at any time. Glimps also proposes: when a supplier has run clean for a while, it asks on the dashboard whether it may book that one itself. You answer yes or no. Correct an automatically booked invoice and Glimps steps that supplier back down on its own.

### The brake

**All manual** in the header stops automatic booking for the whole administration, whatever the per-supplier levels say. Everything is still read, coded, and prepared for you. Switch back to **Per supplier** and your levels pick up where they were.

## Booking without a purchase order

An invoice that carries a purchase order number normally waits for a match. **Book without PO** overrules that for this invoice. You code the lines yourself, and the purchase order stays open in your accounting system. Glimps records who chose it.

## What comes back

Once Exact accepts the booking, the invoice carries its purchase entry: the entry number, the journal, the period, and the booked lines. You find it on the invoice and in the [archive](/booking/archive). To correct a booked invoice, see [Changing a booked invoice](/booking/change-booked-invoice).

## When sending fails

The invoice keeps the error from Exact, in Exact's own words, and stays where it is. Nothing is half booked.

Fix the cause and send again. See [Booking errors](/booking/errors).

<Warning>
  Do not book the same invoice by hand in Exact while Glimps still has it open. You end up with two entries and a reconciliation job. Settle it in one place.
</Warning>


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