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

# Working on one invoice

> The invoice viewer: the document, the fields, the lines, and the actions.

Click an invoice and you get the document on one side and what Glimps read on the other. Everything you need to decide is on this screen.

## Notices at the top

Glimps puts what it wants you to know above the invoice, in plain words. A duplicate suspicion, a changed bank account, a purchase order difference, a failed math check, a contract that does not match, a hold, or an open question.

A notice that is settled disappears. A notice that blocks the booking says so.

## The fields

Supplier, invoice number, invoice date, due date, amounts, VAT, payment details, and purchase order numbers. Click a field to correct it, then save.

If Glimps found no invoice number, the **Invoice Number** field is empty. Fill it in before you send.

You can type a date instead of picking it in the calendar:

* Type `2506` or `25-06-2026`. **Tab** or **Enter** confirms and moves on to the next field.
* A half date completes to this year: `25-06` becomes 25-06 of this year.
* Text that is not a date goes back to the stored date. **Escape** undoes your typing.
* The calendar icon still opens the calendar.

Correcting a field is not just a fix for today. Glimps uses your corrections to read the next invoice from this supplier better.

## The lines

The booking lines sit under the document, in the **General Ledger Accounts** section. Every line carries a description, ledger account, VAT code, amount, and VAT amount, and where used a cost center, a project, and accrual dates.

You can edit a line, add one, or delete one. The line total and the invoice total are held against each other while you work, so you see straight away when they no longer agree.

### Sums in amount cells

An amount or VAT cell works like a desk calculator. Type a sum and Glimps works it out:

| You type | Result |
| - | - |
| `120+35` | 155,00 |
| `3x12,50` | 37,50 |
| `(100-20)/2` | 40,00 |
| `100+21%` | 121,00 |
| `242-10%` | 217,80 |

While you type, the answer shows at the right end of the cell. **Enter** works the sum out and keeps you in the cell. **Escape** drops your typing. A sum that is not complete keeps the old amount.

### Dates on a line

The line date and the accrual start and end dates complete a half date: `25-06` or `2506` becomes 25-06 of this year, and `25-06-26` becomes 25-06-2026. When you change part of a date, the rest stays as it was.

See [Coding](/invoices/coding) for how the ledger account and VAT code are chosen, and how to make that automatic.

## The actions

| Action | What it does |
| - | - |
| Save | Stores your changes without sending anything |
| Send | Saves your changes and books the invoice in Exact Online |
| Book with PO | Books it against the matched purchase order |
| Book without PO | Books it although the invoice carries a purchase order number |
| Reprocess | Reads and codes the invoice again from scratch |
| Ask | Sends a question to a colleague, attached to this invoice |
| On hold | Parks the invoice, and keeps automatic processing off it |
| Delete | Removes the invoice from Glimps |
| Next invoice | Opens the next one in your list |

<Note>
  If **Send** is disabled, something is blocking it. The invoice says what. See [Why an invoice is not booked](/troubleshooting/invoice-not-booked).
</Note>

## The audit trail

Once an invoice is booked, open it in the [archive](/booking/archive) to see every step: what Glimps did, what you did, what an approver decided, and when. A decision taken on someone's behalf is recorded with both names.

This is also where an override lands, with the reason you typed.

## Questions and notes

A question goes to a colleague and expects an answer. A note is for anyone who opens the invoice later. Both stay attached to the invoice. See [Questions](/invoices/questions) and [Notes and holds](/invoices/notes-and-holds).


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