# Accounting
The Accounting page under Settings is where You define Your company's cost objectives - the accounting dimensions that appear on transaction rows when invoices are processed. Things like general ledger accounts, VAT codes, cost centres, projects, departments, and any other custom dimensions Your company uses for cost allocation.
If You've ever wondered why certain fields show up on transaction rows and others don't, or why some are mandatory and some optional, this is where it's all configured.
Only users with the Administrator or Accountant role can access this page.
### **What You see on the Accounting page**
The page shows a table listing all Your cost objectives. Each one has:
* **Cost objective:** the name (for example "Account", "VAT code", "Cost centre", "Project")
* **Code:** a short code used in exports and throughout the interface
* **Optionality:** whether this dimension is mandatory, optional, or hidden
* **Visibility:** where it's visible (purchase invoices, purchase orders, or both)
**Export -** You can download the data shown on this page to Excel using the Export button at the top.
The total number of cost objectives is shown in the page title, for example "Accounting (11)" means You have 11 dimensions configured.
You can search the list by name or code, and sort by any column. Your sorting preference is saved, so next time You open the page it looks the same way You left it.
### **Account and VAT code are always first**
Two cost objectives have a fixed position: Account is always first and VAT code is always second. These can't be reordered because they're fundamental to every transaction row. All other cost objectives - cost centres, projects, departments, whatever Your company uses - can be reordered by drag-and-drop or by changing the order number.
### **Mandatory, optional, or hidden**
For each cost objective, You decide how it behaves:
**Mandatory** means users must select a value for this dimension on every transaction row before the invoice can be confirmed or exported. Use this for dimensions that are critical to Your accounting - like the general ledger account or department.
**Hidden** means the dimension doesn't show up in the interface for users. It can still exist in the background for specific integrations or scenarios, but it won't clutter the screen.
### **Different settings for purchase invoices and purchase orders**
You can configure each cost objective independently for purchase invoices and purchase orders. A dimension that's mandatory on invoices can be optional on POs, or the other way around.
{% hint style="info" %}
This is practical because the level of detail You need is often different at the ordering stage compared to when the invoice actually arrives. For example, You might want a budget code mandatory on purchase orders but hidden on invoices, or a project code required on invoices but optional when someone creates a PO.
{% endhint %}
### **How this connects to daily work**
Everything You define here directly affects what users see on transaction rows. The dimensions, their order, which ones are required - it all comes from this register. This applies to manual posting by users, autotransaction rules, FitekAI proposals, and Excel imports to transaction rows.
If You combine these settings with "**Verify transaction rows on the final confirmation**" under Company settings, You create a strict setup where invoices can't leave Fitek until all mandatory dimensions are properly filled. That's useful when Fitek is Your main pre-accounting tool and You want clean, complete data going to Your ERP.
### **Adding and importing cost objectives**
You can add new cost objectives one by one using the "**+ New Cost Objective**" button, which opens a sidebar where You fill in the name, code, and settings.
### **Managing dimension values**
When You click on a cost objective in the list, You open the values that belong to it. For example, clicking on "Account" shows all Your general ledger accounts. Clicking on "Cost centre" shows all Your cost centres.
Each value has:
* **Code:** the account or dimension code (for example 5501, 6340)
* **Description:** what the code stands for (for example "Other costs", "Transport")
* **Start date and end date:** if a value is only valid for a certain period. When the end date has passed, the value is no longer available for selection on new transaction rows. This also means FitekAI won't propose expired values.
* **Mandatory cost objectives:** some values can have other dimensions linked as mandatory. For example, if account 5504 shows "2 items", it means two other dimensions must be filled whenever that account is used.
* **In use:** whether the value is currently active
You can add new values with the "**+ Add dimension**" button, import them in bulk via CSV, or export the existing list. The delete button removes individual values- but be careful with values that are already in use on posted invoices.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://fitek-learning.fitek.com/fitek-learning-space/copy-of-english/getting-started/settings/accounting.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.