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

# Coding

> How a line gets its ledger account and VAT code, and how to make that automatic.

Coding is the work that repeats. Glimps does it by pulling on four things, in this order.

<Steps>
  <Step title="Your rules per supplier">
    A booking rule fixes the ledger account and the VAT code for a supplier, or for a supplier and a description together. This wins over everything else, because you said so on purpose.
  </Step>

  <Step title="What you booked before">
    Glimps compares the line against what your team coded for similar lines from this supplier in the past.
  </Step>

  <Step title="The text on the invoice">
    Glimps reads the line and matches it against your ledger account descriptions.
  </Step>

  <Step title="Nothing certain enough">
    The line stays empty and the invoice asks you. An empty field beats a confident wrong answer, because a wrong ledger account is expensive to find later.
  </Step>
</Steps>

## Why a line got its account

Next to a ledger account or VAT code that Glimps filled in, an info icon shows **Why this value was selected**. Click it to see where the value came from and why. A few of the sources you can see:

| Source | What it means |
| - | - |
| Supplier default | It is set as the default for this supplier in your booking rules |
| Supplier history | Your earlier bookings for this supplier point here. The popover says how: this is the account the supplier is most consistently booked on, earlier lines with the same wording are on it, or new items from this supplier always go there |
| Another administration | The bookings of this administration do not settle it, and another administration in your organization books this supplier on this account |
| From the invoice | The document itself says which one |
| AI suggestion | Glimps chose it from the available options |
| Changed manually | A person set it |

Another administration only counts when your organization shares learning between administrations. See [Learning](/insights/firm-portal#learning) on the organization overview.

## Booking rules

Find them under **Settings > Booking rules**. Two parts work together.

### Relations

A relation is a supplier. Per relation you set the default ledger account and VAT code, and how far Glimps may go on its own: manual, prepare, or book automatically. See [Automatic booking](/booking/sending#automatic-booking) for what each level means.

### Descriptions

A description is your own label for a ledger account or a VAT code, in your words rather than the accountant's. A good description tells Glimps what belongs on the account and, just as useful, what does not.

The form can walk you through it with five questions:

1. What costs does this account cover?
2. Which invoice lines are the usual examples?
3. What must never land here, even from the same supplier?
4. Which words on an invoice point at this account?
5. How does this account differ from the neighbouring ones?

<Tip>
  Exclusions do the heavy lifting. "Not software subscriptions, not shipping" prevents more mistakes than another list of examples.
</Tip>

## Description templates

Your booking lines can carry your own text instead of the supplier's. Set that up under **Settings > Booking rules > Standard descriptions**.

Two ways to build one:

* **Fixed pattern**: build the text from variables such as month, year, quarter, invoice day, invoice date, supplier name, invoice number, purchase order number, or cost center. **Invoice date (dd-mm-yyyy)** and **Invoice day** take the date printed on the invoice.
* **Instruction**: describe the format in your own words, including the exceptions. Glimps writes the description per invoice, or per line.

For a line template, **Position** decides where your text goes: **Before item**, **After item**, or **Replace item**. Replace item drops the supplier's line text, so every booking line reads the way you want, for example supplier, account and date.

An instruction can be learned from your own booked invoices, and tested against the last ten before you switch it on. The test shows your text next to the text Glimps would write.

<Note>
  Pick the suppliers a template applies to. A template with no supplier applies to everything, which costs an extra reading step on every invoice.
</Note>

## Cost centers

If your administration uses cost centers, switch them on under **Settings > Booking defaults**. Glimps then fills the cost center when the document or your instruction says which one it is, and leaves it empty when it is not sure. It never guesses one from history.

The cost center travels to Exact Online with the booking.

## Rule proposals

Glimps notices when you correct the same thing over and over. It then proposes a fixed rule, with the evidence next to it. Accept it with **Zo doen**, or turn it down with **Liever niet**.

Find proposals under **Settings > Bedrijfsgeheugen**, and in the recommendations on [Insights](/insights/overview).

## Aggregation

Some suppliers send fifty lines where your books want three. Under **Settings > Booking defaults** you set a threshold: above that many lines, Glimps combines them into fewer booking lines. You can also force it per supplier.

Glimps only combines lines that share the same ledger account, VAT code, cost center, project, and accrual period. The lines Glimps read off the document stay as they were, so you can always see where a booking line came from.


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