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

# Why an invoice is not booked

> Work down this list and you will find the reason in under a minute.

An invoice that will not book always has a reason, and the invoice carries it. Open the invoice and read the notices at the top first. If you would rather work down a list, here it is in the order these things actually happen.

<Steps>
  <Step title="Is it on hold?">
    A hold parks the invoice and keeps automatic processing off it. Release it, and it continues. See [Notes and holds](/invoices/notes-and-holds).
  </Step>

  <Step title="Is the supplier known?">
    An unresolved supplier stops everything after it. Pick the relation, or create the supplier from the invoice. The message **The supplier is not linked to a relation in Exact** means the same: choose the supplier and send again.
  </Step>

  <Step title="Do the totals add up?">
    A failed math check holds the invoice. Correct the lines so they add up to the total. See [Checks](/invoices/checks#math).
  </Step>

  <Step title="Is a duplicate suspicion open?">
    Then Glimps will not book it automatically. Compare it with the invoice it points at. Delete one, or send it yourself if it is not a duplicate.
  </Step>

  <Step title="Is a bank account waiting for confirmation?">
    Call the supplier on a number you already had, then confirm or refuse the account.
  </Step>

  <Step title="Does every line have a ledger account?">
    And a VAT code, if your settings require one. An empty field blocks the booking on purpose.

    An invoice with no booking lines at all has nothing to send. Add the lines under **General Ledger Accounts**, or match the purchase order if it has one.
  </Step>

  <Step title="Did the purchase order match?">
    Fix the reading, ask the buyer, accept the difference, or book without the purchase order. See [When an invoice does not match](/purchase-orders/blockers).
  </Step>

  <Step title="Does the contract match?">
    A tariff outside the agreed deviation, or a second invoice for the same period, holds the invoice. See [Contracts](/contracts/overview).
  </Step>

  <Step title="Does it wait for an approval?">
    If the card says **Waiting for approval, not booked yet**, your company books after approval. Glimps books it by itself after the last approval. **Authorizations > Active** names the step and the person it waits on. **Declined, not booked** means an approver said no; see [Declined invoices](/approvals/rejections).
  </Step>

  <Step title="Is a purchase journal set?">
    Under **Settings > Booking defaults**. Without one, nothing can be booked in this administration.
  </Step>

  <Step title="Is Exact Online connected?">
    The invoice list shows a banner when the connection needs reconnecting.
  </Step>

  <Step title="Does it say Not sent to Exact yet?">
    Then an earlier send was held back before anything reached Exact, because the invoice still waited for approval or had an open notice. Nothing is in Exact. Settle the notice and send again.
  </Step>

  <Step title="Did Exact refuse it?">
    Then the invoice carries Exact's own message. See [Booking errors](/booking/errors).
  </Step>
</Steps>

<Note>
  If the archive says **Booked**, the invoice is in Exact. To correct it, see [Changing a booked invoice](/booking/change-booked-invoice).
</Note>

## Still stuck

Ask Luca. It can see the invoice, the checks, and the error at the same time, and it answers "why has this invoice not been booked" better than any list can.

If Luca cannot explain it either, use the bug report button in the sidebar and include the invoice number.


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