The inFakt Alternative Question: Where Biurko.io Actually Fits
inFakt is a mature Polish accounting ecosystem with a free KSeF plan. If you run a single Polish entity and need bookkeeping in the same system, inFakt is hard to beat, and we will say so plainly. Biurko.io solves a different problem: many companies in one panel, certificate-based KSeF authentication instead of tokens, readable KSeF error messages, and a Ukrainian-language interface. Here is how to tell which one you need.

Since 1 April 2026, e-invoicing through KSeF (Poland's National e-Invoicing System) has been mandatory for essentially all VAT taxpayers except the smallest. The largest taxpayers (VAT sales above PLN 200 million in 2024) joined on 1 February 2026, and the smallest follow from 1 January 2027. Until 31 December 2026, taxpayers whose monthly gross value of B2B invoices covered by the KSeF obligation does not exceed PLN 10,000 may still issue invoices outside KSeF. Under the current act, penalties under Article 106ni of the VAT Act apply from 1 January 2027. On 16 September 2026 the Ministry of Finance announced it will move them to 1 January 2028; that is a bill not yet passed, and it moves only the penalties, not the obligation to use KSeF. The legal basis is Dz.U. 2025 poz. 1203, and the Ministry of Finance maintains the official rollout schedule at ksef.podatki.gov.pl.
The practical consequence: a lot of companies picked the first tool that promised KSeF compliance. Now comes the harder question of whether that tool matches how they actually work.
I am the founder of Biurko.io, so treat the following with appropriate suspicion. That is why I start with where inFakt is simply the better choice.
Where inFakt wins outright
It is an accounting platform, not just invoicing. inFakt lets you stay on self-invoicing, move to self-service bookkeeping, or hand your filings to a dedicated accountant without changing systems. Biurko does not do that: there is no KPiR and no annual PIT return, and it does not replace an accountant, although it calculates ZUS (social security) contributions for sole proprietors on the lump-sum tax and builds JPK tax files. It is above all a tool for invoices, KSeF and VAT registers.
The price for a single entity. Per the inFakt price list (July 2026), the inFakt KSeF plan costs 0 PLN with unlimited KSeF sending, and inFakt Faktury costs 4.99 PLN net per month on an annual plan. Biurko's free tier (FREE) has no limit on invoices or KSeF sending either, and its paid plans start at 29 PLN net per month (SOLO), adding JPK files, the lump-sum tax and AI access, among other things. For one sole proprietorship (JDG) issuing a dozen invoices a month that needs nothing but invoicing, the cost is the same: 0 PLN.
It is more mature. OCR on purchase invoices, mobile apps, bank integrations, phone support, years in market. Biurko is younger and I am not going to pretend otherwise: it does read purchase invoices from a PDF or a scan with AI, but it has no native apps (there is a PWA with push notifications) and no bank integrations.
If you need bookkeeping in one system or product maturity, stay with inFakt.
Where the "app plus accountant" model runs out
The friction starts when your work does not fit the shape of "one company, one owner, one accountant."
Real situations from user conversations:
You run an accounting firm (biuro rachunkowe) serving 40 clients. Each one means a separate account, separate login, separate KSeF integration.
Your group has a Polish subsidiary, a holding entity, and a dormant company. Three accounts, three subscriptions, three dashboards.
A client asks why an invoice did not go through, and your screen shows a raw KSeF error code with no context.
Your finance team in Poland works in Ukrainian, and the entire interface is in Polish.
None of these is a flaw in inFakt. They are simply a different job, and inFakt was not designed for that job.
What Biurko does differently
Many companies, one panel
Biurko was built from day one around one user holding many companies. You switch between entities without logging out, and roles are set per company: the bookkeeper sees documents only, the owner sees everything, a junior can draft invoices but not submit them.
TEAM at PLN 99 net per month gives five users and lets you run up to five companies, each company having its own plan. SCALE at PLN 199 net removes both limits. There is no separate workspace for accounting firms: the accountant joins a client's company as a free guest (one seat in every company, on every plan, including the free one) and switches between companies in one click.
Certificates, not tokens
Biurko connects to KSeF with Profil Zaufany (the default) or a KSeF certificate, either your own or one ordered through Biurko from the Ministry of Finance; we do not support tokens. That was a deliberate architectural decision.
A KSeF token behaves like a password: whoever holds it can act on your behalf. A certificate is bound to a private key and a signature, and its expiry is visible in advance (Biurko shows a warning on screen 30 days out and sends notifications 7, 3 and 1 day before and on the day of expiry).
Under the current rules KSeF tokens expire on 31 December 2026. At consultations on 9 June 2026 the Ministry of Finance proposed keeping them, but no regulation has been adopted yet, so moving to a KSeF certificate is the safer choice. Current announcements are at ksef.podatki.gov.pl.
KSeF errors in plain language
KSeF rejects an invoice and returns a code. Say 21115. In the raw API that means an invalid certificate, and nothing more. You cannot tell whether the problem is yours or the gateway's.
Biurko translates codes into sentences a human can act on: the buyer's NIP (Polish tax ID) failed validation, check for a PL prefix; or the session expired before submission and the invoice is queued for retry. This sounds trivial until you are the one answering a client at 5 p.m. on a Friday.
Offline24, emergency mode, and UPO
When KSeF is unavailable, you can issue an invoice offline and submit it later. You can choose offline24 at any time, with submission by the next business day; for a declared unavailability, submission is due on the next business day after it ends; in emergency mode, within 7 business days of the end of the outage in the Ministry's announcement; in a total failure there is nothing to submit afterwards. Biurko prints the KOD I QR code on the PDF (the KOD II code only if the company holds a KSeF certificate of the Offline type, which Biurko can order), resubmits invoices automatically every 5 minutes, and once the deadline passes sets the status "Needs review" and sends a notification. It also retrieves the UPO (the official confirmation receipt) and verifies the Ministry of Finance signature automatically.
A Ukrainian interface
The full panel runs in Ukrainian, not "translated menus, Polish everywhere else." That matters for roughly 60,000 Ukrainian-owned businesses operating in Poland and for the accounting firms serving them. I do not know another Polish KSeF system that offers it.
Pricing side by side
| inFakt | Biurko.io | |
|---|---|---|
| Free plan | inFakt KSeF, 0 PLN, unlimited sending | FREE, 0 PLN, unlimited invoices and KSeF sending |
| Cheapest paid | inFakt Faktury, 4.99 PLN net/month | SOLO, 29 PLN net/month |
| Multiple companies | separate accounts | TEAM: up to 5 companies, 99 PLN net (each company with its own plan); SCALE: unlimited, 199 PLN net |
| Bookkeeping | yes, up to a dedicated accountant | no |
| Ukrainian UI | no | yes |
| KSeF auth | Profil Zaufany, certificate, token | Profil Zaufany, KSeF certificate (your own or ordered through Biurko); no tokens |
Net prices. The inFakt price list is as of July 2026, the Biurko price list as of 8 October 2026. Price lists change. Verify with both vendors before deciding.
Three scenarios
One Polish entity, a handful of invoices, lowest cost wins. Both tools have a 0 PLN plan with unlimited KSeF sending, so pick the one that fits the rest of your work better.
One entity, but you also want an accountant inside the same system. Choose inFakt. Biurko does not offer that.
An accounting firm, a group of entities, or a Ukrainian-speaking team. Choose Biurko. This is where the multi-company panel, per-company roles, certificate auth and readable errors stop being nice-to-haves.
Checklist before you switch
Count the entities you actually handle. One versus more than one changes the entire decision.
Check how your current tool authenticates to KSeF: token or certificate.
Confirm it supports offline24 and emergency mode, not just online submission.
Confirm it retrieves and verifies the UPO, rather than merely displaying it.
Map who on your team needs access and to what. More than one person means you need roles.
Export your contractor and invoice data before migrating. Always.
Send one test invoice through a test or demo environment before sending the first real one. In Biurko, practise on the demo (demo.biurko.io, 7-day access), because an account on app.biurko.io sends invoices to production KSeF.
Bottom line
inFakt and Biurko are not competing for the same customer, even though both list KSeF on the box. inFakt is an accounting ecosystem for a single business. Biurko is a KSeF tool for someone handling several businesses who needs control over authentication, deadlines and error handling.
If that second description is you, create a free account at biurko.io and connect your first company. The FREE plan needs no card. To practise without legal effect, use the Biurko demo (demo.biurko.io, 7-day access, the KSeF demo environment). An account on app.biurko.io sends invoices to production KSeF, so every invoice you send there is real.
FAQ
Is Biurko.io cheaper than inFakt? Not in the basic case: for a single sole proprietorship both have a 0 PLN plan with unlimited KSeF sending (inFakt KSeF and Biurko FREE), and inFakt also has a paid tier at 4.99 PLN net. Biurko's paid plans are 29 PLN (SOLO), 59 PLN (PRO), 99 PLN (TEAM) and 199 PLN (SCALE) net per month, and you choose the plan for each company separately.
Does Biurko handle bookkeeping? Not full bookkeeping: there is no KPiR and no annual PIT return. Biurko issues invoices, submits them to KSeF, imports incoming purchase invoices, manages UPO receipts, keeps VAT registers and builds JPK files (download from the SOLO plan, submission to the Ministry from PRO). The rest of the filings stay with your accountant or accounting firm.
Can I migrate my data from inFakt to Biurko? There is no import from inFakt or from CSV or XML files. You can pull your invoice history from KSeF (manual import or on a schedule, off by default), continue your numbering by setting a starting number, and add contractors by hand or look them up by NIP in the GUS registry.
What is the difference between certificate and token authentication in KSeF? A token works like a password: anyone holding it can act as you. A certificate relies on a private key and signature, carries an expiry date and is harder to leak unnoticed. Under the current rules KSeF tokens expire on 31 December 2026 (the Ministry of Finance proposed keeping them, but no regulation has been adopted yet); for the current status, check ksef.podatki.gov.pl.
When do penalties for missing KSeF invoices start? Under the current act, penalties under Article 106ni of the VAT Act apply from 1 January 2027. On 16 September 2026 the Ministry of Finance announced it will move them to 1 January 2028; that is a bill not yet passed, and it moves only the penalties, not the obligation to use KSeF, which already began on 1 February and 1 April 2026, depending on company size (the smallest follow from 1 January 2027).
Tags
Previous article
Can't Log In to KSeF with Profil Zaufany? 7 Reasons and Fixes
Next article
KSeF Login in 2026: Trusted Profile, Signature or Certificate