Blog— Anton Ignashev

What enova365 costs in 2026: the price list, read to the end, and the three costs it leaves out

What enova365 costs in 2026: the price list, read to the end, and the three costs it leaves out

The Price List Is Public. That's the Easy Part.

enova365 publishes its prices, which is more than most Polish ERP vendors do. On the 2026 list for companies, Handel costs 70 zł a month per seat in the Silver version and 120 zł in Gold. Księga Handlowa is 203 zł, WebApi 131 zł per installation. That answers the question people type into Google, and it's the cheapest line of the real bill.

I work on the other side of these installations: connecting enova365 to B2B portals, bank statements, KSeF and, more recently, AI agents for accounting offices. When a client asks me what enova365 "costs", the licence is rarely what surprises them a year later. Three other numbers do, and none of them is on the vendor's site. So: the list first, with two worked examples. Then the three costs it leaves out.

Every figure below comes from the vendor's own price lists on enova.pl: net, described as suggested, valid from 2 January 2026. Partners can and do quote differently, so treat these as the starting point of a negotiation, not as the invoice.

What the List Says

The model is simple once you see it. You pay per seat (stanowisko) per month for each core module, in one of three versions: Silver (srebrna), Gold (złota) or Platinum (platynowa). Or you buy the licence outright instead.

Monthly subscription, company price list, per seat:

Module Silver Gold
Handel (sales, purchasing, warehouse) 70 zł 120 zł
Księga Handlowa (full accounting) — 203 zł
Kadry i Płace (HR and payroll) 120 zł 265 zł
CRM 35 zł 72 zł

Then come the lines priced per installation, not per seat:

  • WebApi: 131 zł a month. This is the module every external integration goes through, and it's not in the base package.
  • Integrator: 361 zł a month.
  • Add-on modules: most between 50 and 180 zł a month. The footnote that matters: they require the Gold version of the base module they extend.
  • Business Intelligence: tiered by seat count, from 205 zł (up to 5 seats) to 1 511 zł (over 40).
  • SaaS hosting: 50 to 65 zł per user a month, with a minimum user count.

Accounting offices get their own list, also per seat and not per client company: Księga Handlowa 244 zł, Księga Podatkowa 50 zł, Kadry i Płace 145 to 318 zł depending on version, WebApi the same 131 zł.

If you'd rather buy, the Platinum purchase list puts Handel at 5 950 zł, Księga Handlowa at 7 930 zł, Kadry i Płace at 8 690 zł and CRM at 4 140 zł net in the standard variant, and 7 120 / 9 500 / 10 450 / 4 970 zł in the multi-company variant. The list itself says these cover the licence, not implementation.

Two Worked Examples

A wholesaler with six people in sales, two in accounting, CRM for the two sales leads and an integration with a B2B portal. Subscription, Gold:

  • Handel: 6 × 120 = 720 zł
  • Księga Handlowa: 2 × 203 = 406 zł
  • CRM: 2 × 72 = 144 zł
  • WebApi: 131 zł

That's 1 401 zł net a month, about 16 800 zł a year. The integration line, WebApi, is under a tenth of it.

An accounting office with eight accountants and three people on payroll, Gold, with WebApi for KSeF downloads and bank statements:

  • Księga Handlowa: 8 × 244 = 1 952 zł
  • Kadry i Płace: 3 × 318 = 954 zł
  • WebApi: 131 zł

That's 3 037 zł net a month, about 36 400 zł a year. If the office serves 120 clients, the licence works out at roughly 25 zł per client per month.

The second example hides the most useful sentence in the whole price list: for an office, the cost is per seat, not per client. Client number 121 adds nothing to the licence bill. The only way the cost per client goes down is if the same eight people handle more clients. That's a capacity question, not a pricing one, and I'll come back to it.

Cost One: The Version You Pick Today Limits What You Can Add Later

Silver is cheaper. On Handel it's 50 zł a seat less, which for six seats is 3 600 zł a year. It looks like an easy saving.

The catch is the footnote. Add-on modules need the Gold version of the module they extend. So the version isn't really a price decision. It decides which extensions you can buy next year without first upgrading every seat. You can see this one coming: a company buys Silver, runs it for a year, then needs something that turns out to be an add-on, and the "small" add-on arrives with an upgrade of the whole base module attached.

Before you choose a version, list the add-ons you might plausibly want in the next two years and ask the partner, in writing, which version each one needs. That takes ten minutes. It's cheaper than finding out later.

Cost Two: The Warranty Extension After Year One

A purchased licence comes with 12 months of updates and warranty, as partners describe it. After that you can buy an extension to keep getting updates. The price of that extension isn't on any public list I could find.

That matters more than it sounds, for two reasons.

First, it decides the subscription-versus-purchase comparison. Without it, "buy once and own it" looks cheap over five years. With it, the gap may shrink or flip. You can't do the arithmetic without that number, so get it from the partner before you compare.

Second, in Poland updates aren't optional. Since February KSeF has been mandatory, and JPK schemas, payroll rules and e-declarations change every year. An enova365 that stopped updating in 2025 isn't a cheaper enova365. It's a system that can't file correctly. So the warranty extension isn't an extra. It's part of the running cost, whether you call it that or not.

Cost Three: The Integration Is a Project, Not a Module

WebApi at 131 zł a month is the cheapest line in either example above. The work it makes possible isn't.

Connecting enova365 to a B2B portal, a shop, a bank, KSeF or an AI agent means building something on top of WebApi: authentication, mapping, error handling, a way to know when it stopped working. I've written about the mechanics in the WebAPI developer guide, and about a typical portal integration in enova365 + B2B portal. The build for one flow is usually days, not months. The calendar time is set by something else: how long it takes to get working read-only credentials to production. I called that the access lag in the post on implementation timelines.

Two details from real installations that change the budget:

  • Does the integration user take a seat? In every installation I've worked with, a WebAPI session behaved like a login and needed its own headroom. Licence terms vary by agreement and version, so check yours. But if it does, the integration costs a seat as well as WebApi. I cover the service-account side in the post on agent permissions in enova365.
  • Custom fields. Every installation has them, and an integration that reads them is fragile in a specific way: someone can change them without telling anyone. Scope them before you price the work. See enova365 custom fields.

Five Questions for the Partner Before You Sign

  1. Which version does each add-on we might need require? In writing, for the next two years, not just today.
  2. How are seats counted, and does an integration or WebAPI user take one?
  3. Is WebApi included in the offer, and as a subscription or a perpetual licence? If the offer doesn't mention it, it isn't included.
  4. What does the warranty extension cost after month 12, and how is it calculated? This is the number that decides subscription versus purchase.
  5. What exactly is in the implementation, in hours, and who maintains the configuration and custom fields afterwards?

A partner who answers all five clearly in one email is a good sign. If the answer is "we'll work it out during implementation", the price you're comparing isn't the price you'll pay.

Back to the Office Example

For an accounting office the most important line on the price list isn't on the list at all. Licences are paid per seat, so the cost per client only falls when each person serves more clients. That doesn't come from a cheaper version. It comes from taking repetitive work off the seats you already pay for: KSeF downloads, bank-statement matching, checking registers before JPK. That's what I build. I wrote about the economics, including the volume below which it doesn't pay, in what an AI agent for accounting costs.

Running enova365 and want the full cost before you sign or renew? Write to me. I'll go through the offer with you, including the three lines that aren't on the list.

Let’s talk about your project

Free 30-minute consultation. We’ll figure out if and how I can help.

Book a Free 30-Minute Call

Select a date

November 2026
Mon
Tue
Wed
Thu
Fri
Sat
Sun
← Back to Blog

Related Posts

What Symfonia costs in 2026: the price list for Finanse i Księgowość, the cloud, eBiuro and accounting-office bundles
Blog

What Symfonia costs in 2026: the price list for Finanse i Księgowość, the cloud, eBiuro and accounting-office bundles

Symfonia Finanse i Księgowość costs 1 620 to 3 550 zł net a year in 2026 and is sold only as a subscription. The cloud ERP is 490 zł per user per month, eBiuro for accounting offices starts at 409 zł a year, and the office bundles cost 1 890, 3 696 or 11 694 zł. The full list from symfonia.pl, KSeF Plus limits from 2027 and a three-year comparison.

Read more→
PIT-11, PIT-4R, PIT-8AR and IFT-1R for 2026: the 1 February and 1 March 2027 deadlines and the three totals that must agree
Blog

PIT-11, PIT-4R, PIT-8AR and IFT-1R for 2026: the 1 February and 1 March 2027 deadlines and the three totals that must agree

The payer's annual returns for 2026 go to the tax office by Monday 1 February 2027, because 31 January is a Sunday. PIT-11 to employees and IFT-1R follow by 1 March. Before anything goes out, three totals have to agree: PIT-11s against PIT-4R, PIT-4R against the bank statement, and flat-rate tax against PIT-8AR. Correct a PIT-11 after mid-February and it lands on an employee whose Twój e-PIT is already prefilled.

Read more→
KSeF API 2.0 error codes: 440, 450, 21405 and the rest — what they mean and how to fix them in enova365, Optima and Subiekt
Blog

KSeF API 2.0 error codes: 440, 450, 21405 and the rest — what they mean and how to fix them in enova365, Optima and Subiekt

KSeF reports errors on three levels: an HTTP exception with a 21xxx code, a session status and an invoice status. The same number means different things on each, so 440 is a duplicate invoice in one place and a cancelled session in another. The code table from the Ministry's own spec, the fix for each, and the one error you must never fix by renumbering the invoice.

Read more→