# What is FitekAI?

FitekAI is an artificial intelligence tool built into Fitek that automatically fills in accounting data on Your purchase invoices and expense reports. Instead of manually assigning cost centres, dimensions, and product codes on every invoice, FitekAI does it for You, based on how You've handled similar invoices before.

### **Why it's useful**

If You process invoices regularly, You know how repetitive the accounting part can be, same suppliers, same cost centres, same dimensions, month after month. FitekAI takes that routine work off Your plate.

Based on real usage, customers typically see:

* Invoice processing speed increase of 80–95%
* 23–31 minutes saved per invoice compared to manual processing
* Most cost centres and dimensions filled in without human intervention

The time adds up quickly, especially if You're handling hundreds or thousands of invoices per month.

### **How it works**

FitekAI learns from Your company's own data, Your historical invoices, the cost centres and dimensions You've used, and how You've posted different types of costs. Each company gets its own AI model, because no two companies post their invoices the same way.

The learning process starts with an initial training period of about 24 hours after activation. After that, the model keeps improving continuously. Every new invoice, every manual correction, every export with finalised postings, it all feeds back into the model. Over time, the suggestions get more accurate and You'll find Yourself making fewer corrections.

FitekAI doesn't rely on fixed rules. It finds patterns. So if You always post telecom invoices to the same cost centre, it picks that up. If Your posting logic changes, it adapts.

### **What FitekAI proposes**

When an invoice is imported into Fitek with FitekAI enabled, it's processed automatically before it appears in Your dashboard. This typically takes 1–2 minutes. Once ready, the invoice shows up with transaction rows already filled in.

FitekAI suggests **dimensions and cost centres** based on invoice content and Your historical patterns. It only proposes active dimensions, anything with an expired end date is automatically excluded.

If Your company has the **product items module** enabled, FitekAI also proposes **product codes** for transaction rows. If product codes are already filled by automation, FitekAI won't overwrite them.

For **expense reports** submitted through the mobile app, FitekAI works the same way, it analyses the receipt data and suggests the relevant dimensions based on similar past expenses.

{% hint style="warning" %}

* It doesn't execute autotransactions: those follow their own rules and triggers
* It doesn't process duplicate invoices: if an invoice is flagged as a duplicate, FitekAI skips it
  {% endhint %}

### **How FitekAI works alongside autotransactions**

FitekAI and autotransactions are designed to complement each other. After FitekAI fills in its proposals, autotransactions are applied on top. If Your autotransaction rules recreate transaction rows, they fully overwrite what FitekAI proposed. If they don't recreate rows, they only overwrite the specific fields covered by the rule and FitekAI's suggestions stay in place for everything else.

This gives You control over which cases are fully handled by rules and which ones benefit from AI filling in the gaps.

**Every change is logged.** When FitekAI fills in data, it's marked with the source tag "AI" in the transaction row history. So You can always see what was done by AI, what came from system automation, and what was changed by a user.

###


---

# 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/fitekai/what-is-fitekai.md?ask=<question>
```

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.