> ## 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.
# How Glimps works
> The road an invoice travels through Glimps, and the points where a person steps in.
Every invoice travels the same road. Glimps does each step by itself and only stops when it needs something a person knows.
## The road
The invoice reaches Glimps by mail, from a watched mailbox, or because someone dragged it in. See [Getting invoices in](/intake/overview).
Glimps reads the document: supplier, invoice number, dates, amounts, VAT, and every line. It also checks that the numbers add up. See [How Glimps reads an invoice](/intake/reading-invoices).
Glimps matches the sender to a relation in Exact Online. If it cannot, it asks which supplier this is, or you create the relation from the invoice itself.
Every line gets a ledger account, a VAT code, and where used a cost center. Glimps takes this from your rules, from what you booked before, and from the invoice text. See [Coding](/invoices/coding).
The math check, the duplicate check, the bank account check, and the purchase order or contract check all run here. A failed check holds the invoice and says why. See [Checks](/invoices/checks).
If your rules ask for approval, Glimps routes the invoice to the right person or group and waits. See [Approvals](/approvals/overview).
Glimps posts the invoice in your purchase journal in Exact Online and records the purchase entry. See [Sending to Exact Online](/booking/sending).
The invoice, the document, every decision, and who made it stay readable. See [Archive](/booking/archive).
## Where a person steps in
Glimps only stops for things that cannot be worked out from the document.
| It stops for | Because | What you do |
| - | - | - |
| An unknown supplier | The sender is not a relation yet | Pick the right relation, or create it |
| A line with no ledger account | Nothing in your rules or history fits | Code the line once, Glimps remembers |
| A difference with the purchase order | Price, quantity, or a line that exists on one side only | Accept, reject, or ask the buyer |
| A changed bank account | The IBAN differs from the one on file | Confirm it, or refuse it |
| A possible duplicate | The same number or the same file came in twice | Delete one, or say it is not a duplicate |
| Totals that do not add up | The lines do not sum to the total | Correct the reading, or record an override |
| An approval | Your rules ask for one | The approver approves or declines |
## Zero-touch
An invoice is zero-touch when arrival, supplier, coding, and sending all happened without a person. Approval steps do not count against it, because approval is meant to be human work.
You can see your own rate under [Insights](/insights/overview).
Most of the work of raising that rate is done once: fixed coding per supplier, a clean approval setup, and a purchase order or contract to hold invoices against. The last step is permission. A supplier only books itself once you put it on [book automatically](/booking/sending#automatic-booking); until then Glimps prepares and waits for you.
## Who does what
Glimps names the parts of itself so you know what you are talking to.
* **Glimps** is the app and the pipeline.
* **Luca** is the assistant. Luca reads your mailbox, answers questions in the chat, proposes rules, and prepares or books your invoices as far as you allow. The settings screens use this name, which is why a supplier level reads "Luca books the invoice itself". See [Luca](/ai/luca).
* **Self-driving** is the part that opens its own cases, asks the right person, and settles the outcome. See [Self-driving](/self-driving/overview).
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.