Exporting the Comarch Optima ledger for import

Flowtly Editorial Team7 minUpdated

Project costs your accountant books in Comarch ERP Optima can reach your project budgets in Flowtly without anyone typing them in again. The accountant exports the ledger entries from Optima to an Excel workbook. Flowtly support then imports the workbook into your organisation, and each project cost entry becomes a cost on its project, in the month the accountant booked it to.

This page is for the accountant who prepares the file. It covers the Optima steps, what the workbook must contain, and what happens to it in Flowtly.

Before you start

  • Project costs come from the project accounts. Only entries booked to an account named 601-PROJEKT_<code>, such as 601-PROJEKT_ALPHA, are imported, as costs of the project that code stands for. Entries on any other account stay out of Flowtly.
  • Each code needs a project. Agree with Flowtly support which Flowtly project each code stands for. Entries whose code is matched to no project are reported back with their total and are not imported.

Exporting the ledger from Optima

  1. In Comarch ERP Optima, open Księgowość → Dzienniki.
  2. Set the date range to start on the first day of the first month Flowtly should cover, for example 1.01.2026, and to end today.
  3. Select all journals, so that no journal's entries are left out.
  4. Add the columns Numer dokumentu and Numer KSeF to the list.
  5. Export the list to Excel.
  6. Check that the entries are on a sheet named Zapisy, and keep that name.
  7. Save the workbook and send it to Flowtly support.

What the workbook must contain

Flowtly reads only the sheet named Zapisy; a workbook without one is refused. The first row of the sheet holds the column headers, and each row below it is one ledger entry. These columns must be present, under these headers:

Column What it is used for
Nr dziennika Identifies the entry, together with the columns marked below
Nr dziennika cząstkowego Identifies the entry
Data księgowania The cost's booking date. Its year also identifies the entry, because journal numbers start again each year
Konto The account. Only 601-PROJEKT_<code> accounts are imported. Also identifies the entry
Kwota Wn The debit amount. Also identifies the entry
Kwota Ma The credit amount. Also identifies the entry
Opis The cost's name in Flowtly. Also identifies the entry
Kategoria The category, kept with the cost
Okres The month the cost counts in on the budget
Numer dokumentu The invoice number the cost comes from
Numer KSeF The invoice's KSeF number

Headers are matched without regard to capital letters. When a header appears twice, as Kategoria can, the first of the two columns is read. Other columns, such as Id. księgowy or Konto przeciw., can stay in the sheet: they are not read.

Okres

Okres is a Polish month name and a year, such as luty 2026, or a date, which counts as its month. A project cost entry whose Okres is neither is reported back.

Numer dokumentu and Numer KSeF

These two columns are needed for each cost to show which invoice it comes from: the budget lists the invoice number and the KSeF number with the cost. Entries from older months may have nothing in these columns. Keep both columns in the sheet anyway. An entry with them empty is still imported, without an invoice number or a KSeF number.

Amounts and formulas

  • An entry counts at debit minus credit, Kwota Wn minus Kwota Ma, in PLN, as booked. An entry on the credit side, such as a correction, therefore lowers the project's cost. The same amount is used as net and as gross, so a net budget and a gross budget show the same figure.
  • A formula is read as the result Excel saved with it. A formula saved without a result, or with an error result such as #N/A, stops the import. Correct it in Excel, save the workbook and send it again.
  • An amount typed as text that could be read two ways, such as 1.000, is reported back for its row.

When something in the file is reported back

Nothing from the file is imported while any of its entries is reported back for a reason that belongs to that entry: a project cost entry whose Okres is not a month, an amount that can be read two ways, or two project cost entries that agree in every column that identifies an entry. Correct those rows in Optima or in the workbook and send the file again.

An entry that would change a frozen budget month also stops the import: one that is new to Flowtly and falls in a frozen month, or one whose month or project changes into or out of a frozen month. A frozen month is never edited. Such a cost is first settled as a correction in an open month, and the file is imported after that.

Sending a later export

The same date range can be exported again, for example each month from the same start date. Flowtly recognises an entry it has already imported by the year of its booking date, its journal numbers, its account, its amounts and its description, so an entry sent twice is never added twice:

  • An entry already imported is updated when its Okres, booking date, category, Numer dokumentu or Numer KSeF changed. A corrected Okres moves the cost to its new month. An entry with nothing changed is left as it is.
  • An entry changed in one of the identifying columns reads as a new entry. Changing its description, account or amounts in Optima after it was imported adds it again, and the earlier one stays in Flowtly. Tell Flowtly support when entries already sent were changed this way.
  • An entry missing from a later file is not removed from Flowtly.

Where the imported costs appear

  • In the incoming invoices list, each imported entry is a cost with a "Ledger import" badge. It has no file and no party, so there is nothing to preview or download for it. See Transaction Attachments.
  • On the budget of its project, in the month of its Okres. A month's drill-down lists it as a cost document, with its invoice number and KSeF number when the file carried them.

These costs come from the books, so the accountancy exports to Optima leave them out: they are never sent back into the books they came from.

Example use cases

  • First import: The accountant exports every journal from the first day of the year, with Numer dokumentu and Numer KSeF, and the project costs booked so far appear on the project budgets, month by month.
  • Monthly refresh: Each month the accountant exports the same range again. New entries are added, a corrected Okres moves its cost, and nothing is counted twice.
  • Tracing a cost to its invoice: A project manager opens a budget month's drill-down and reads the invoice number and KSeF number of each cost booked by the accountant.
  • A late cost: An entry for a month already sent to the accountant is settled as a correction in an open month, so the frozen month's project split stays as it was sent.

Related terms