Agnum invoice import: how to automate it (2026)

Agnum is one of the accounting systems used in Lithuania, and typing invoices into it by hand hurts most at month end. This article covers how to prepare purchase and sales invoices for import into Agnum automatically: what the system does for you, what is worth preparing in advance, and where the process usually gets stuck.

Where the time goes when you key invoices into Agnum

The invoice itself is rarely the hard part — everything around it is. You have to find the supplier, key in the lines and the amounts, pick a product code from your nomenclature for every line and the right VAT code, and assign the object or department while somebody still remembers what the invoice was for. At a few hundred documents a month that turns into days, and all of those days compress into the last week.

Imports break on codes, not on amounts

If you have ever loaded a prepared file into an accounting system, you know the pattern: the totals are right and the import still will not start, because one line points at a product code that is not in the nomenclature, or at a supplier whose card nobody has created yet. The worst part is not the fix itself — it is that the fix happens somewhere other than where the mistake was made, and often not on the same day.

Your client and product lists come from your own Agnum

So Ezura does not offer codes of its own. Your client and product lists are taken from Agnum itself and refreshed afterwards, which means lines are coded with exactly what you already see in your accounts. When a product or a client stops being used in Agnum, it stops being offered in Ezura too — the list does not quietly go stale.

The practical difference is simple: nobody retypes a nomenclature into a second system, and the typing mistakes that only surface during an import never get created in the first place.

A new supplier does not stop the import

The second common obstacle is a document from a supplier you are dealing with for the first time, or a product that is not in the nomenclature yet. What Ezura prepares carries not only the documents themselves but the supplier and product details those documents need. So a first-time supplier does not mean a separate trip into Agnum to create a card just to get the import moving.

What Ezura prepares for you

• •Reads every line, total and VAT rate — purchases and sales alike
• •Assigns product codes from your own nomenclature
• •Assigns a VAT code to each line based on your classifiers
• •Assigns dimensions — object, department, warehouse — using your rules
• •Checks the supplier's registry details, so the record is not built on an old address or VAT number

What is left for the accountant is review and approval. When something is missing, or the system is not confident, it says so separately instead of quietly filling the gap with a guess — that is the difference between real automation and "we will check all of it again afterwards".

Objects and departments travel with the document

If you split costs by object, department or warehouse, that analysis should not be a separate job after the import. You decide which of your dimensions corresponds to which piece of Agnum analytics, and Ezura fills the values using rules — by supplier, by product name, or by text on the invoice. You set and change those rules yourself; you do not have to ask us.

What is worth preparing before the first export

Getting started does not mean rebuilding Agnum — we adapt to what is already there. Before the first export it helps to have:

• •A working Agnum system with the nomenclature and client list you use day to day
• •VAT classifiers exactly as you use them for reporting
• •Your list of objects, departments or warehouses — if you use them, they travel with the document
• •An agreement on who approves invoices before export

In practice the first run takes one conversation and a handful of test invoices: we push a couple of real documents through, look together at how they land in Agnum, and only then switch on the full flow. Nothing gets installed on your computers.

One thing to know up front

With Agnum, invoices reach the accounts by import: Ezura prepares a file and you load it yourself. The last step stays in your hands, and so does the decision about when the records appear in the accounts. Some systems accept data directly, without a file — the Agnum route is an import, and that is worth knowing when you plan a month-end close.

From email to a record in Agnum

• •1. The invoice arrives by email at your Ezura address
• •2. Ezura reads it and extracts the details, lines and totals
• •3. You review the prepared record and adjust dimensions if needed
• •4. You export the approved purchases and sales and load them into Agnum

Where to start

If you already run Agnum, the quickest way to tell whether this fits is to put a few of your real invoices through it and look at how they come out before the import. Not demo samples — the same documents that cause you the most work at month end.