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

# Booking errors

> The errors Exact Online sends back, what they mean, and how to fix them.

When Exact refuses a booking, Glimps keeps the message and leaves the invoice where it is. These are the ones you are most likely to meet.

<AccordionGroup>
  <Accordion title="Invoice journal not found" icon="book">
    No purchase journal is set for this administration, or the one that was set no longer exists in Exact.

    Set it under **Settings > Booking defaults**. If the list is empty, the Exact connection has not synced yet.
  </Accordion>

  <Accordion title="The relation does not exist" icon="building">
    The supplier is known in Glimps but not in the Exact administration you are booking to, often because the invoice was assigned to a relation from another administration.

    Pick the right relation, or create the supplier from the invoice.
  </Accordion>

  <Accordion title="The ledger account or VAT code is not valid" icon="calculator">
    The account or code was removed or blocked in Exact after Glimps synced it.

    Recode the line. Glimps syncs with Exact by itself, at least every night. If it keeps happening, check in Exact that the account or code is still active.
  </Accordion>

  <Accordion title="The period is closed" icon="calendar-x">
    Exact does not accept bookings in a closed period.

    Switch the booking period to the current period and year under **Settings > Booking defaults**, or ask your accountant to reopen the period.
  </Accordion>

  <Accordion title="The connection needs reconnecting" icon="plug">
    The token refresh failed, and Exact refuses every call.

    Reconnect under **Settings > Integrations**. Invoices keep processing while the connection is down. Only booking waits.
  </Accordion>

  <Accordion title="The invoice appears twice in Exact" icon="copy">
    Usually an invoice that was also booked by hand in Exact while Glimps had it open.

    Reverse one of the two entries in Exact. Glimps recognises a booking that was made outside it, and does not book it a second time once it knows.
  </Accordion>
</AccordionGroup>

## Before the invoice reaches Exact

Some messages come from Glimps itself. They mean the send stopped before anything was written to Exact.

<AccordionGroup>
  <Accordion title="Not sent to Exact yet" icon="circle-pause">
    An earlier send was held back: the invoice was still waiting for approval, or it had an open notice, such as a possible duplicate. Nothing is in Exact, so there is no Exact error to look for.

    Settle the notice and send the invoice again. If it waits for approval and your company [books after approval](/approvals/book-after-approval), Glimps books it after the last approval.
  </Accordion>

  <Accordion title="The supplier is not linked to a relation in Exact" icon="link">
    Glimps knows the supplier, but not which relation in Exact it is.

    Choose the supplier on the invoice and send it again.
  </Accordion>

  <Accordion title="This invoice has no booking lines yet" icon="list">
    There is nothing to send to Exact.

    Add the lines under **General Ledger Accounts**, or match the purchase order if the invoice has one. Reprocessing creates the lines too, and then books the invoice if everything checks out.
  </Accordion>
</AccordionGroup>

## After you fix it

Send the invoice again. If the invoice was changed in the meantime, reprocess it first so the booking is built from the current values.

## An invoice that is already booked

Once Exact has booked an invoice, it stays booked. A later send that fails does not mark it as failed, and it cannot be deleted from the dashboard.

To correct a booked invoice, change it from Glimps. See [Changing a booked invoice](/booking/change-booked-invoice).

## If the message is not here

The message on the invoice comes straight from Exact Online, so their documentation covers it. Ask Luca as well: it can see the invoice and the error at the same time.


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