Symfonia — One Company, Three Sets of Books

Symfonia runs the books of a large part of Polish business, and it has earned that position. Keeping pace with Polish tax and labour law across three decades — the VAT overhauls, JPK, the Nowy Ład payroll rewrites and now KSeF — is a substantial ongoing commitment, and one that has survived several changes of ownership without a break in service. The books Symfonia keeps are disciplined, and that discipline is what makes them good material to build on.

At a glance

What Symfonia is

Symfonia is a family of Windows applications that run the financial and operational books of a Polish company. It is not one program with modules switched on and off; it is a set of products, sold separately, that share a company list and exchange documents with each other. That is a design decision, and for most of the market it is the right one — a business buys the accounting product because it must keep books, adds the trade product when stock and invoicing outgrow a spreadsheet, and adds payroll when the headcount justifies it.

The finance product, Symfonia Finanse i Księgowość, holds the chart of accounts (plan kont), the journals, the VAT registers, settlements with counterparties and the statutory reports. Symfonia Handel holds the commercial side — items, warehouses, stock movements, orders, sales and purchase documents, price lists. Symfonia Kadry i Płace holds employees, contracts, working time, absence and the payroll run, with its own obligations to ZUS and the tax office. Around those sit fixed assets, production planning, shop-floor reporting panels, a POS product, mobile sales and warehouse apps, and an e-commerce connector.

The localisation is the product’s real achievement, and it is harder than it looks from outside. Polish accounting and payroll law changes constantly, and Symfonia has tracked it: JPK files generated from inside the application, the JPK_V7 record with its current KSeF attributes, the Krajowy System e-Faktur handled through a dedicated product and API as the obligation phased in through 2026, and a payroll engine rebuilt more than once as contribution and relief rules moved underneath it. Doing that continuously, for three decades, while the company changed hands twice, is a commitment that does not show up in a feature comparison and matters more than most things that do.

For a Polish company that needs to be correct with the tax office, wants stock and payroll kept properly, and does not want to pay for an international platform it will not use, Symfonia is a well-judged answer. A great many businesses should stay on it for a long time.

The Symfonia product family

Most buyers choose products one at a time, on need and price. It is worth understanding what else that choice determines, because the product boundary is also a data boundary.

The move from the classic line to Symfonia ERP is worth knowing about. On the ERP line the data sits in Microsoft SQL Server, which makes reporting work simpler and faster, and entirely invisible to the people using the system. For a company where reporting has started to matter, it usually pays for itself quickly.

Who Symfonia fits

Micro companies and sole traders. Simplified bookkeeping, invoicing, a VAT return, a handful of employees. Symfonia Start or eBiuro is the correct tool and there is nothing here that needs improving.

Established Polish SMEs. Twenty to three hundred people, one legal entity, full double-entry books, stock, payroll. This is the core of the market and Symfonia serves it well. What these companies usually want next is not a different system — it is a management view of data Symfonia is already holding correctly.

Accounting and tax practices. A practice may hold a large number of client companies in one installation, and Symfonia’s multi-company licensing is built for exactly that. Practices are among the most loyal parts of the user base, and increasingly they are the ones asking whether they can offer clients reporting on top of books they already keep well.

Manufacturers and construction businesses. The production and construction editions add routings, production orders, shop-floor confirmation panels and project cost control on top of the same finance and trade products. These are the Symfonia clients with the richest operational data and the strongest appetite for profitability analysis below the top line.

Groups that grew sideways. A Polish operating company on Symfonia, a second company acquired with a different system already installed, a foreign subsidiary on something local to its own jurisdiction. Every individual choice was sound. What nobody owns is the view across them, and this is the context in which Symfonia most often reaches us.

What Symfonia holds — and why it is good material

Before the reporting question, it is worth being clear about the asset.

Symfonia data is disciplined. Statutory obligation enforces a rigour that voluntary data entry never does: the VAT record has to reconcile, JPK_V7 has to tie back to documents with the right KSeF attributes, the payroll run has to agree with ZUS, the books have to balance. A Symfonia company database kept properly by a competent accountant is complete to document-line level, internally consistent, and stable across years. That is a better starting point than a great deal of what we connect.

It is also richer than most users exploit. Symfonia ERP carries analytical dimensions (wymiary analityczne) alongside the chart of accounts, including a dedicated cost centre structure (miejsce powstawania kosztów, universally shortened to MPK) and dictionary-backed dimensions (słowniki) that can be attached to postings, counterparties, accounts and documents. The vendor’s own guidance is to widen the management picture through dimensions rather than by extending the chart of accounts — which is the correct instinct, and the same one behind our own chart of accounts architecture work. Dimensions defined in the finance product are shared across the Symfonia ERP estate and feed the Business Intelligence module.

Where those dimensions have been used consistently, they carry most of what is needed for real profitability analysis. Where they have been used partially — which is more common, because nothing forces them the way the tax office forces the VAT record — they are still a foundation worth building on. The data quality of what feeds a reporting layer sets that layer’s ceiling, and Symfonia sets a high one.

What sits outside Symfonia’s scope

Symfonia is scoped to one company at a time, and to one domain per product. Both boundaries are design decisions rather than omissions, drawn deliberately for the market the products serve.

Three things sit outside them.

The view across the products. Finance, trade and payroll each do their job, and they exchange documents with each other properly. What none of them holds is the combined picture — revenue by channel from Handel, its cost of delivery from Finanse i Księgowość, and the labour that produced it from Kadry i Płace, on one line, with one definition of margin. The gross margin a trading report shows and the margin the accounts show are usually both right and rarely the same number, because they are answering different questions from different products.

The view across companies and across systems. One database per company means a group of four companies is four Symfonia databases, with no shared chart of accounts, no intercompany elimination and no currency translation . Symfonia ERP Business Intelligence will aggregate across companies in the group, which is more than many systems in its class offer and genuinely useful — but aggregation is not statutory consolidation , and it stops at the edge of the Symfonia estate. This is worth saying plainly: no ERP does this. Not Symfonia, not Business Central, not SAP. Cross-system truth is a layer above every transaction system, which is the point we make at more length here .

The management view. The statutory chart of accounts is built to satisfy the tax office, and it does that job well. It is not built to answer which customers make money after the cost of serving them or what did that contract cost against what we priced. Symfonia’s own reporting answers the questions it was scoped to answer — statutory outputs, the OLAP analyses and budget tracking in Business Intelligence, sales analysis in Analityk Sprzedaży. None is a semantic data model that a dashboard or an AI assistant can query across a group and several systems.

None of this is a reason to change system. It is a reason to add a layer.

How we elevate it

Getting the data out is the routine part. On Symfonia ERP our default is a direct read-only SQL connection to the company databases, read incrementally, with nothing written back and no measurable effect on the people using the system. Where a direct connection is not available, Symfonia ERP WebAPI gives a documented REST interface with session-token authentication; the cloud applications have their own documented APIs; and on the classic Pervasive line we read a controlled copy on a schedule rather than the live data set. Read-only throughout.

What happens next is the Symfonia-specific work.

One record across finance, trade and payroll

The product split is Symfonia’s defining structural fact, and it is the first thing we resolve. We take the ledger from Finanse i Księgowość, the document and stock detail from Handel, the payroll result from Kadry i Płace and, where they are in use, the production orders — and we join them into one model on a common set of keys: company, period, counterparty, item, cost centre, project. The ledger stays the control total. The subsidiary detail explains it. That single step turns three correct sets of books into one answer about the business, and it is why a Symfonia client can suddenly see labour cost sitting inside a product margin instead of arriving as a monthly lump.

The analytical dimensions and MPK, put to work

Wymiary analityczne, MPK and the słowniki behind them are where profitability lives, and they reward attention. We audit how consistently they have been applied across history — which accounts carry an MPK and which do not, where a dictionary has drifted, which periods were tagged well and which were not. We then map the statutory chart to a second, management structure built to answer management questions, so that revenue is grouped by what you actually sell and cost by what you actually control, with the cost centre hierarchy behind it agreed rather than inherited. Rules for filling the dimensions going forward are encoded as validation, so the discipline holds after we leave. Where a client has used MPK well, this step is quick and the payoff is immediate.

One view across every company and every system

Each Symfonia company database becomes one entity in a common model, sitting alongside another Polish system in a sister company, an international ERP in a foreign subsidiary, an e-commerce platform, a separate payroll product or a spreadsheet — all producing the same standardised output. Group reporting in any currency, intercompany elimination handled properly, and drill-down from a consolidated total back to the Symfonia document that produced it. This is routine rather than aspirational: we work with 70+ companies across 11 countries, on 12+ different ERP and accounting systems. See Group Reporting & Consolidation .

On the governed layer, the rest is the platform doing its standing job: daily reconciliation against the ledger so the close confirms rather than rebuilds, a semantic model that Power BI and AI can both query reliably , and your business context accumulating so answers get sharper the longer it runs.

What becomes answerable

The clearest way to describe the difference is to list what a Symfonia client can ask afterwards.

• Which customers are actually profitable, after delivery, service and the labour that went into them — not just margin on the invoice?
• What did that contract cost against what we priced, while it is still running?
• What is group EBITDA in one currency, when three companies sit on three separate Symfonia databases and a fourth is on something else entirely?
• Which product lines earned their shelf space this year, at the cost the ledger actually recorded?
• Why did overhead move this month, ranked by the cost lines that moved most against budget ?
• How much cash is tied up in stock that has not moved in six months, and what does that do to cash flow next quarter?
• Where does the reported number differ from the booked number, and why?

Every one of these is answered from data Symfonia is already holding. The information was there. What was missing was the structure to ask.

What it takes, and what does not change

Connection in days. First reports in the first week. For a single-entity Symfonia ERP client, the connection is a read-only login and the first governed reports follow inside a week. A full build — management chart of accounts, dimension repair, consolidation across several entities, the reporting suite — runs in phases over the following months. The distinction matters, and we would rather be precise about it than promise a finished model in a fortnight.

What we need from you: an NDA, read-only credentials, and a conversation about what the numbers should mean.

What does not change: Symfonia stays your system of record. Your accountant keeps working the way they work. No migration, no data cleanse project, no retraining, nothing written back.

Read-only access throughout. Your data stays in an EU-hosted Azure environment, aligned with ISO 27001 and GDPR, governed by you.

In practice

No published Onetribe case study names Symfonia, and we would rather say so than dress up an anonymous story. What we can point at is the pattern, which does not depend on which system sits under each company.

TEPEDE — one group view across six different ERPs A CEE large-format printing group: 8 entities, 6 countries, 6 different ERP and accounting systems. Symfonia is not among them, and that is rather the point — each entity had chosen sensibly for its own jurisdiction, and none of those choices had to be revisited. Chart of accounts mapping, currency normalisation, intercompany elimination and daily automated extraction produced a single group P&L, balance sheet and cash flow. A Polish company on Symfonia joins a structure like that the way any other entity does.

JING Tea — reporting across an operational stack The relevant part for a Symfonia reader is the multi-product shape: finance in one system, trade and stock in another, and a governed layer above both holding the definitions. That is structurally the same problem as joining Finanse i Księgowość, Handel and Kadry i Płace into one record.

When Symfonia is eventually replaced

Some Symfonia clients change system at some point, usually because they have outgrown the scope rather than because anything went wrong — typically to Business Central, to an international platform brought in by a new owner, or to a larger Polish system.

Because the governed layer sits above the ERP, only the connection changes. The data model, the reports, the dashboards and the consolidation logic stay as they are. Clients who built the layer first find the migration measurably easier, because they can prove the new system’s numbers against the old system’s numbers from day one — and they keep their reporting history through the change rather than starting again.

This is not a theoretical claim. When JING Tea replaced its operational stack, the reporting layer carried through the change unaltered — the systems underneath moved, the numbers and the reports did not.

Symfonia in the regional context

Symfonia is one of several capable systems serving the Polish market and its neighbours. Each gets its own article in the series .

From a data-layer perspective the choice matters less than it appears. Each of these becomes an entity in the same governed model, which means the system decision can be made on operational fit rather than on reporting fear. The full matrix — including the whole Polish stack — is on the series hub .

Frequently asked questions

Do we need to replace Symfonia to get proper management reporting? No, and we would usually advise against it. Keep Symfonia for what it does well — statutory correctness, VAT, JPK and KSeF, payroll compliance, clean transaction capture — and build the reporting layer above it. Replacing a working ERP to solve a reporting problem is an expensive way to solve the wrong problem, which is the argument we set out in Do You Need a New ERP .

Is Onetribe a replacement for Symfonia? No. Symfonia remains your system of record and your team keeps using it exactly as they do now. We read from it, never write to it. If you change ERP later, the reporting layer stays.

Is Symfonia an ERP or accounting software? Both are defensible, and which one applies depends on what you have bought. The classic line is accounting and trade software for a small company. Symfonia ERP, with finance, trade, payroll, fixed assets, production and document flow on one company database, is ERP scope by any reasonable definition — it simply reaches that scope by combining products rather than by shipping one.

What database does Symfonia use? It depends on the line. Symfonia ERP runs on Microsoft SQL Server — versions 2017, 2019 and 2022 are supported, in Express, Standard or Enterprise edition, with server collation Polish_CI_AS and mixed-mode authentication. Each company is a separate database. The classic desktop line ships with a Pervasive PSQL v12 file engine instead, which is a sound choice for the single-company installations it serves and simply means the data is read differently.

Can Symfonia connect to Power BI? Yes. On Symfonia ERP the practical route is a read-only extract into a governed model, with BI reporting on the model rather than on Symfonia directly. Pointing Power BI straight at the tables works once and gets harder to maintain from there — the tables are transactional by design, they differ between products, and the definitions need to live somewhere durable. Reading this way does not slow Symfonia down: we read incrementally on a read-only login, outside working hours where a client prefers it, and on the classic line only ever from a controlled copy.

Can Symfonia consolidate several companies? Not in the sense a group finance function means. Symfonia ERP holds one company per database, and Business Intelligence will aggregate figures across selected or all companies in the group, which covers useful ground. What sits outside that is statutory consolidation proper — intercompany elimination, currency translation, a single group chart of accounts — and anything involving a company that is not on Symfonia. That is a layer above the ERP, and the most common reason multi-company Symfonia users come to us.

Does Symfonia have an API? Yes, several. Symfonia ERP WebAPI is a REST interface exchanging JSON over HTTP or HTTPS with session-token authentication, exposing counterparties, items, stock levels, orders and sales documents from Handel and Finanse i Księgowość. The cloud applications have their own: OpenAPI 3 for eDokumenty, GraphQL for KSeF, key-based access for eBiuro. All are transactional interfaces rather than bulk analytical ones, which is the reason direct SQL remains our default on the ERP line.

Is Symfonia ERP Business Intelligence enough? For a single company, or a group entirely on Symfonia, with finance users comfortable in Excel, it does real work and is worth using — over fifty predefined analyses, budget tracking by project and cost centre, and output an external tool can read. Where it runs out is at the edge of the Symfonia estate: cross-system reconciliation , one set of definitions owned under proper data governance , and a model an AI assistant can query reliably. If Symfonia is your only system and one company is your whole business, start there. On AI: Symfonia applies AI inside the products — document capture and OCR-led automation — and is visibly building AI competence, but publishes no conversational assistant and no MCP endpoint today. The WebAPI is transactional, so an AI connection built on it inherits documents, not definitions; the governed layer is where an assistant’s answers become defensible — why AI fails on raw ERP data .

Official Symfonia resources

• Symfonia — product site
• Symfonia ERP
• Symfonia Finanse i Księgowość
• Symfonia Handel — trade and warehouse
• Symfonia — payroll and HR products
• Symfonia ERP Business Intelligence
• Symfonia ERP WebAPI
• Product documentation — pomoc.symfonia.pl
• Symfonia ERP system requirements, including SQL Server sizing
• Symfonia KSeF API — GraphQL documentation
• Symfonia eDokumenty API — OpenAPI 3 documentation
• KSeF — Ministry of Finance

Onetribe is not a Symfonia sp. z o.o. partner or reseller. We build the governed data layer above your ERP, whichever ERP that is.

Next steps

• Every source system we connect — the series hub, with the full matrix
• How we consolidate any combination of ERPs — group reporting
• Why your ERP doesn’t govern your data — the cross-system layer, in detail
• Discuss your Symfonia estate — free assessment