Connect KSeF to the systems you already work with.No manual work.
We're preparing a pilot of KSeF 2.0 integrations with the systems you already use: invoicing, an online shop, an ERP or your own app. Have an idea for improving your process but not sure where to start? You're in the right place. We're looking for companies to join the pilot.
We'll write to you to see whether we can help each other.
Invoices have to go to KSeF. Your system doesn't send them there.
Since 2026, B2B invoices in Poland have to be issued in the National e-Invoicing System (KSeF). The obligation is being phased in. Ready-made KSeF integrations exist mostly in invoicing and accounting software, but invoices are often created somewhere else: in an online shop, a subscription system, an ERP or your own admin panel. Each of those has to be connected to KSeF separately, through a manual export, an extra app, or code someone then has to maintain.
What we test in the pilot
- How do you send an invoice to KSeF straight from your system?
- A sale in an online shop, subscriptions in a payment system, a document in an ERP or in an app built in-house. We want to go from that data to an invoice accepted by KSeF and back, without a manual XML export.
- Where do you need KSeF data?
- Cost invoices in an ERP, a document in an approval workflow, a report for your team, an assistant that answers questions about invoices. KSeF already has this data, and we move it to where it's useful.
- Can your idea be built?
- You know what should exist: a tool for an accounting office, a client portal, a process automation. If it can be built on KSeF 2.0, we build the first working version.
Taking part in the pilot is free. If you decide to go ahead with an implementation, we'll price it based on the size of the project.
After the invoice
Sending your first invoice to KSeF is one thing. The trouble starts later: with a refund, a correction, a discount, a foreign currency, a duplicate payment notification or a KSeF outage. We think that's where the real problems are, and the pilot will let us check.
This hypothesis is our starting point. We'll find out where it leads together with you.
How the pilot works
First, you describe in a short form what you want to connect to KSeF. Then we talk about your systems or your idea and check whether it fits the pilot. If it does, we agree on the scope and build the integration, showing you progress along the way. We run the finished version on the KSeF test environment and go through your cases together. We only talk about production once everything works.
Apply for the pilot.
A few questions so we know what you work with before we get in touch. We only require an email and your consent.
Frequently asked questions.
- Does it work yet?
- No. It's a pilot in preparation: we're collecting applications and checking, on real systems, where a KSeF integration pays off most.
- I have an idea, but I'm not sure I want to build it.
- Write anyway. A few sentences are enough. We'll check whether it can rest on KSeF 2.0 and what the first stage would look like.
- I don't write code. Can I still apply?
- Yes. The pilot is for the people who know their billing process. The code is on our side; access to your system and to KSeF we settle separately on the call.
- What about B2C?
- The pilot is about B2B invoices. If you also sell to consumers, tell us in the form. We want to know what your sales mix looks like.
- Who is behind this?
- Me, Artur. Software developer / founder of Stacking. =]