Centas invoice import: how to automate it (2026)

Centas is one of the accounting systems used in Lithuania, and keying invoices into it by hand costs the most at month end. This article covers how to prepare purchase and sales invoices for import into Centas automatically — and why the thing that matters is not the import itself, but whether the amounts still match the paper afterwards.

Where the time goes when you key invoices into Centas

The invoice itself is rarely the hard part. You have to find or create the supplier card, key in the lines, pick a VAT code for each of them, assign the object or department, and then check whether the document total actually matches the sum of the lines. At a few hundred documents a month that is several working days, and all of them compress into the last week.

The most dangerous error is the one the import does not stop

When an import fails, it is annoying but safe — you see the error and you fix it there and then. The expensive case is the other one: the file loads with no warning at all, the document looks tidy, and the sum of the lines differs from the document total by a couple of cents. That invoice is now living in your accounts. It usually surfaces weeks later, while reconciling with the supplier or preparing i.SAF — nowhere near where the mistake was made, and not on the day it would have been easy to fix.

Discounts and awkward prices are the usual cause

Almost always the culprit is the unit price, not the total. The supplier states a discount on the line, or a price carried to three decimal places, and what reaches the accounts is a rounded price. 250 units at €0.416 is €104.00; the same 250 units at a rounded €0.42 is €105.00. On one line that is a euro. On twenty lines it is a difference big enough to stop the document reconciling — and somebody has to go and find it.

The line total stays the one printed on the invoice

So what Ezura hands to Centas is not an approximate recalculation but the same line total that is printed on the supplier's document, discount included where there is one. The lines add up to the document total, and the document total matches what the supplier is asking to be paid. That sounds obvious right up until the afternoon you spend hunting two cents.

The same principle applies earlier in the process: an invoice whose lines do not add up to its own total never reaches the export at all. Ezura stops it and names how much is missing and where, while the document is still in front of you.

VAT codes and i.SAF come from your own classifiers

Every line gets its VAT code from your classifiers, not from a list of ours. The same code can exist at different rates — which is what foreign-supplier invoices need, the ones that otherwise get corrected by hand every single time. Lines that are not a VAT object, a returnable deposit for example, are handled separately so they do not land in the registers where they do not belong.

Objects, departments and warehouses travel with the line

If you allocate costs by object, department or warehouse, that analysis should not be a separate job after the import. Values are assigned by your rules — by supplier, by product name, by the text on the invoice — and they travel with the line. You set the rules and change them yourself; you do not have to ask us.

Purchases and sales in the same flow

The export covers both purchase and sales documents, so two kinds of document do not need two different processes and two different habits. Review and approval work the same way for both, and credit notes and returns travel along with everything else.

What is worth preparing before the first export

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

• •Product and service codes as you use them in Centas
• •VAT classifiers as you use them for reporting and i.SAF
• •A list of objects, departments or warehouses — if you use them, they travel with the line
• •Agreement on who approves invoices before export

Codes and classifiers are agreed once during onboarding, and after that they change when they change in your own accounts. The first run usually takes one conversation and a few test invoices: we put a couple of real documents through, look together at how they land in Centas, and only then switch on the full flow. Nothing gets installed on your computers.

What is worth knowing in advance

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

From email to an entry in Centas

• •1. The invoice arrives by email at your Ezura address
• •2. Ezura reads it and extracts the details, the lines and the amounts
• •3. You review the prepared entry and adjust dimensions if needed
• •4. You export the approved documents and load them into Centas

Where to start

If you already use Centas, the fastest way to find out whether this fits is to run a few of your own real invoices through and look at how they come out before the import. Not demo samples — the actual invoices, with their discounts and their awkward prices, that cost you the most work at month end.