KSeF 2.0 Taxpayer App: How to Use the Free Invoicing App

In the National E-invoice System, the invoice ceases to be a regular file and starts to act as an e-invoice in the system. Added to this are permissions, login, various working environments and the question of whether a free application is enough or is it better to immediately think about integrating with the software.

In this article we show what the KSeF 2.0 Taxpayer Application is for and how to use it in practice. We discuss the difference between test mode, test version, pre-production version and production environment. We also explain how the issuance and receipt of e-invoices works, what is the management of permissions, when the KSeF mobile application is useful and at what point it is worth integrating the process through the API with the accounting program and working with an accountant.

Finally, we show you a simple direction, how to organize the handling of documents so that KSeF works in the background and does not become an additional job. If you care about fewer manual steps, I also indicate where Altera.app can help with all this as a platform to support work with documents and finances.

Taxpayer application KSeF 2.0: what changes KSeF 2.0 and what it is for

The KSeF 2.0 Taxpayer Application is a free, official application for working with KSeF. It is a tool provided by the Ministry of Finance and helps to use the National E-Invoice System in the daily handling of documents. In practice, the idea is that the taxpayer can execute the issuance and receipt of invoices as an e-invoice in one place, and then manage the access and visibility of documents in the system.

Simply put, the KSeF taxpayer application allows you to:
— issuing invoices in KSeF, i.e. sending invoices to the system in the appropriate format
— receiving invoices that come through the National E-Invoice System
— work on document data, their statuses and user activity history
— basic management, including permissions management and granted permissions for people to act on your behalf

It is also worth understanding what changes KSeF 2.0 in practice. The importance of the security layer is growing, that is, who can log in to the system, what permissions they have and what identity verification looks like. In this context, an important role is played by the Certificates and Authorizations Module (MCU), in which you can generate KSeF certificates and implement the granting of permissions. It is the KSeF system that verifies certificates and permissions regardless of whether you use the Ministry of Finance application or your own software.

Free tools of the Ministry of Finance: when the start is free

If you want to get into using KSeF without investing in additional solutions, free tools are the natural choice. The Taxpayer application is free, available online and allows you to start handling invoices without having to buy an accounting program to start.

For whom it most often makes sense:
— when you are just learning the process and checking how the e-invoice is issued and sent to KSeF
— when you want to see how the system works from the user side, without rebuilding the entire document flow
— when you want a tool that is compatible with the current solutions on the part of the Ministry of Finance

It is also important that the application allows you to enter the process directly, without the integration layer and without the need to connect to other tools. This is often sufficient in simpler processes, especially when the number of documents is small and the work is more manual.

Rules for using the application: test version, demo and production environment

From the perspective of the user, it is worth distinguishing between versions of environments, because this affects whether the actions have legal effects and what data can be entered. As part of the KSeF 2.0 taxpayer application, learning and testing environments are available, i.e. test version and pre-production version (Demo). In these environments, fictitious data can be used, and the actions do not have legal consequences. The data in the test version of the taxpayer application will be periodically deleted.

The most important rules are simple:
— in the test version, the documents are for training purposes and invoices must contain fictitious data
— in the test environment you can test processes, but without affecting real settlements, for example VAT
— Demo allows you to go through processes in conditions similar to those that will ultimately work in KSeF, still without legal consequences
— in the production environment, documents are real and invoices are issued and received in a manner that does not have legal consequences

How to log in and start using

To log in to the application, you need to go through the login process and confirm your identity in a way accepted by the system. Then the key is whether you have the permissions granted. Without them, the user may see a limited range of data or not perform actions such as sending invoices or receiving invoices.

In KSeF 2.0, the topics of entitlements and certificates are particularly relevant. The KSeF 2.0 taxpayer application allows you to implement basic access management, but the authorization mechanism itself is decided by the KSeF side. Therefore, the range of available operations depends on how permission management is set up and what the granting of access looks like.

If after the first tests you see that the process becomes too manual and the documents arrive, a good direction is to integrate and integrate the work with documents into the daily circulation. Then comes the topic of the API, the accounting program and how to arrange roles with the accountant. In practice, Altera.app can help as a supporting platform for working with documents and finances, including organizing circulation, automating activities, and reducing manual activities.

Test environment, Demo and production: how the versions of the KSeF 2.0 Taxpayer Application differ

In KSeF there are different working environments, because learning the process is different, and the real issuing and receiving of invoices is different. Therefore, the test version, the pre-production version (Demo) and the production environment are not three variants of the same. These are three different modes of operation of the system, with different rules and different responsibilities.

In the test modes, it is about checking how the application of the KSeF taxpayer behaves in practice. You can practice submitting invoices, receiving invoices and handling permissions. However, there are two things to keep in mind:

— actions in the test environment have no legal effects
— data in these modes may disappear, because the data from the taxpayer's application will be periodically deleted

This is important, because in tests you do not build history permanently. You build confidence that the process is compliant and that the user in your organization knows how to use KSeF.

In test mode, there is also the principle that the documents are practice. The invoices issued must contain a fictitious context. Invoices must contain fictitious data. Thus, you do not confuse real settlements, for example VAT, with simulation.

Demo: how to check features without risk

If you want to preview what the KSeF 2.0 version of the Taxpayer app looks like without setting everything to ready, Demo is the safe path. It's a way to see what the app allows, how the login works, what the management looks like, and where you manage permissions.

In practice, Demo is useful when:
— you want to get used to the app screen and basic navigation
— check if the function is available in your context
— you learn how e-invoicing is carried out in practice in the National System.

System: what you see when you send the document

After sending the invoice to KSeF, the system shows the statuses and confirmations of the operation. It is important both in testing and in production work, as it informs whether a document has been accepted, rejected or is in the process of being processed.

In practice, the KSeF 2.0 taxpayer application allows you to:
— tracking at what stage the e-invoice is
— verifying that the permissions allow the action in question
— check whether the document actually went to the KSeF and not only was prepared locally

This is crucial, because in the National E-Invoice System it counts that the document has passed through the system.

Production environment: when it works “for real”

The production environment is used for real work. It is here that the taxpayer actually invoices, carries out the issuance of invoices, the receipt of invoices and the full handling of documents that have legal effects.

In this mode:
— you do not use fictitious data
— what you generate and send works in real settlements, including VAT
— it is important that the access is granted correctly and the granted permissions correspond to the roles of the people who will log in to the system

It is also worth remembering that the version of the KSeF 2.0 taxpayer application may vary depending on the update. This also applies to certificates. If you use certificates, what matters is that the generated KSeF certificates in the MCU are handled by the MCU, and the verification mechanism is a system component. It works whether you are working in an application or through software and integration.

Taxpayer ksef application: issuing an invoice step by step

In the ksef taxpayer application the process is quite simple. The user fills in the document data, the system checks the compatible format, and then sends invoices to KSeF. So you don't send the file by email. You send a document to the system and only there it “lives” in circulation.

In practice, you can issue an invoice manually in the panel. You can also integrate it through the api into the software or accounting program. Then the issuance and receipt of invoices is carried out without constantly switching windows and without rewriting data.

Permissions: who can issue and receive

Permissions in KSeF are not an ornament. They decide who can log in, who can generate documents, who has access to the data and who is responsible for handling the system. If the taxpayer gives access too widely, he makes a mess. If he gives too narrow, the process stops.

Most often, the roles are arranged like this:
— Exhibitor. Responsible for invoicing and sending invoices
— the receiving person. Responsible for receiving invoices and preview.
— the managing person. Responsible for management and order in access

In KSeF 2.0, the subject of authorization is even more important, because the taxpayer in terms of entitlements may differ depending on the login method and the confirmation method used.

Permission management: how to grant access

Entitlement management consists in the fact that the taxpayer determines who and on what principles is supposed to operate in the system. Assignment should correspond to real tasks, not job titles.

A good setting is one that:
Restricts access to data only to those who need it
— allows you to issue and receive invoices without asking for any action
— complies with regulations and responsibility for finances and VAT

Management: how to organize roles and contexts

Management is not just a click in the panel. It's a way of working. If several people are to work in KSeF, it is worth establishing simple rules so that the system does not turn into “who is the last best”.

The most practical layout looks like this:
— one person is responsible for the given powers and watches over changes when someone arrives or leaves
— Operators are responsible for issuing and receiving invoices as part of their roles
— the accountant has access matched to what he actually does in the process

When you get a lot of documents, the manual model in the app can eat up time. Then integration through the api and integrate KSeF with the accounting program makes sense. And if you want to embrace document flow without tension and without rewriting, Altera.app can take over some of the work around invoices and finances, and you have order instead of clicking to collapse.

KSeF mobile application: what it gives on the phone and outside the office

The KSeF mobile application allows you to have a quick view of documents when you are not at the computer. It is a solution focused on the convenience of daily use of the application, especially when issuing and receiving invoices happens in the background, and you only want to check if the e-invoice is available and if the sending of invoices went correctly.

It is worth remembering that the range of functions on your phone may change with updates. This applies to both what the application shows and how it presents permissions and management elements. In the case of KSeF 2.0, it is also important that the KSeF 2.0 mobile application is to be available for download from February 1, 2026.

Quick view of documents and statuses

Time is what counts on the phone. The application allows you to quickly check whether a new invoice has appeared in the National E-invoice System, what status it has and whether the document actually went to the KSeF.

Most often it is used like this:
— quick view of whether the document is in the system, without going into details
— check that the issuance went correctly and that the system accepted the sending of invoices
— check the basic information about the document before the topic goes further to the accounting program or to the accountant

What is more convenient to do on the computer

The phone is great for control and preview, but not always for full handling of the process. With more documents and working on a wider set of data, the browser version can be more convenient, especially when you enter into more extensive management.

Differences that usually matter:
— the mobile application is dominated by the functions of quick insight and simple actions, and less extensive management
— for more complex operations, permissions and permission management are important, and the phone may be less comfortable
— if different people have different roles, a consistent model of granted permissions and clear access becomes crucial

In addition, in KSeF 2.0 in terms of certificates, part of the activities can be more convenient on the computer. In practice, the mechanism of certificates and entitlements is a systemic element. It works regardless of whether you use the app or other software and integrations.

The most common scenarios outside the office

The application is most useful when you want to have control without going into manual mode of working on a document. It works in short time windows, for example between meetings.

The most common applications:
— you check whether the invoice is in the system and whether it is available for further service
— you verify the basic data of the document before it returns to circulation and further actions
— you confirm that the sending of invoices to KSeF was successful before the topic goes to the team or to the accounting program

If you want these activities not to require constant switching between tools, it's a good idea to have one place to work with documents and finances. In this approach, Altera.app organizes the flow of invoices and payments. It helps to collect documents in one place, set acceptance paths, comment and prepare packages of transfers to the bank. Thanks to this, KSeF and the mobile application remain a channel for exchanging documents, and not a place where everything has to be done manually.

Integration with KSeF via API: how to improve the issuance and receipt of e-invoices

When KSeF starts to be an everyday thing and not a topic “from time to time”, the application itself in the browser may turn out to be too manual mode of operation. Then it makes sense to integrate, that is, to connect the National E-Invoice System with how your finances and document flow already work. Most often, this is done through the API, so that issuing and receiving invoices can run in the background, without constantly logging in and manually rewriting data.

Integration means that the document is created in your tool and then goes to the KSeF system as an e-invoice. The same applies to reception. Incoming invoices in many cases can be downloaded automatically and forwarded to the service, instead of manually checking what is available in the dashboard every day.

Integration with the accounting program: how to reduce manual actions

If you use an accounting program or an invoicing system, the integration allows you to shift the workload from “click in KSeF” to “works in software”. In practice, the idea is to:

— invoicing was done in one place, and sending invoices to KSeF was automatic
— receiving invoices from KSeF did not require daily login to several tools
— the document data were consistent, without the risk of errors when manually rewriting the data
— work in the production environment was faster, because the system immediately shows the status of e-invoice acceptance

This approach is especially convenient when there are a lot of documents, you pay VAT and you want to have order in what was sent, received and accepted.

Division of tasks with an accountant: how to set the process and responsibilities

Integration does not replace people. She arranges roles. This makes it easier to determine who is responsible for what and how management works throughout the process. Most often it looks like this:

— the taxpayer sets permissions and rights management so that the access is tailored to the roles
— the operational person is responsible for issuing and receiving invoices and ensures the correctness of the data
— the accountant works on documents that are already in the system, instead of asking for them to be sent and completed

Well-set granted permissions make the user see exactly what he needs, and document handling does not depend on one person who has to constantly log in and click everything manually.

When integration makes sense and when the application of the Ministry of Finance is enough

The Taxpayer application is usually sufficient when documents are scarce and you want to use the KSeF occasionally. Integration makes sense when KSeF becomes a permanent part of the job and you start to feel the cost of manual handling.

The most common signals that it is worth integrating the process:
— sending invoices and receiving invoices takes real time every day
— the number of e-invoices is growing and you need consistent status management in the system
— you want the use of the application to be an addition, not the main place of work
— you care about the consistency of data and the connection of documents with finances and VAT settlements

If you want to approach this as a normal process and not a “separate world of KSeF”, you can rely on a tool that organizes the flow of documents around invoices. In such a model, Altera.app can support work with documents and finances, for example through OCR, acceptance paths, comments, archive and payment order. Thanks to this, KSeF becomes a place to exchange e-invoices, and daily service is simply more organized.

Taxpayer: order in document circulation and responsibility in the process

In practice, it is the taxpayer who is responsible for how the use of KSeF works in the organization. KSeF is a system that registers e-invoices and organizes the issuance of invoices and receipt of invoices, but it will not decide for you who has what to do and what rights to have. That is why it is essential to consciously manage access and to ensure that the entire process complies with the regulations.

The simplest way to define responsibility is as follows:
— You set the rules of service and division of roles
— the system keeps an eye on the format and records the sending of invoices
— access to data and the ability to perform operations depends on whether permissions are granted

This is also important because the National E-Invoice System includes documents that affect finances and VAT settlements. When there are a lot of documents, the KSeF taxpayer application panel itself may require manual work. Then the importance of integration grows and whether you want to integrate the process through the API with the software or the accounting program.

Who is responsible for granting access and roles in the team

The most stable model is simple. One person takes care of the management of permissions, and the other roles are assigned to specific actions in the process.

In practice, it is worth separating:
— granting authority to issue, send and receive invoices
— access to document data for those who need to verify them
— administrative powers for the person who is responsible for the management and order in the system

Thanks to this, each user operates within clearly defined limits, and the risk of errors when working on data is reduced.

How to maintain consistency in personnel changes

Team changes can break down the process faster than any update. Therefore, it must be remembered that the granted permissions are not set once and for all. When someone changes roles, leaves, or joins the team, you need to update the assignment and make sure that access is consistent with responsibility.

In KSeF 2.0, the topic of authorization may be more sensitive, because solutions in the field of certificates and permissions are part of the system mechanisms. If your organization uses certificates associated with the Certificates and Authorizations Module (MCU), the verification rules work on the KSeF side. This means that regardless of whether you log in through the application or through other software, the correct certificates and correctly granted permissions count.

How to react when access stops working

If someone can't sign in, can't see documents, or doesn't have the ability to perform an operation, most often the problem is with permissions, context, or how they log on to the system. Then it is worth checking whether:

— granted permissions include the action you need
— permissions are set in the appropriate range, including in the permission management area
— you operate in the right environment, because the test environment and the production environment are different modes of operation
— in the tests you remember the principle that invoices must contain a fictitious context, and the actions have no legal effect

If you want the app not to be a bottleneck, but to keep your document flow running smoothly, a good approach is to work in one place that organizes documents and statuses. In such a model, Altera.app can support work with documents and finances, and KSeF and the Ministry of Finance application remain an e-invoice submission layer, rather than a place to manually handle each step.

summary

The KSeF 2.0 Taxpayer App is a sensible starting point if you want to enter KSeF at no extra cost and see how the National E-Invoice System works in practice. It is crucial to distinguish between environments. We work differently in the test version and differently in the production environment, where the e-invoice produces legal effects.

It is worth remembering a few things that really make a difference:
— 🧩 Permissions decide what the user can do after logging in. Without them, issuing and receiving invoices will simply stand
— 🧪 The test environment is used to learn the process. Invoices must contain fictitious data, and data from the taxpayer's application may be periodically deleted
— 📲 The KSeF mobile app is useful for quick viewing and control, but at a larger scale, an orderly process counts anyway
— 🔌 When you get a lot of documents, integration via API and tie-in with accounting software or program reduces manual work and organizes handling

If you want KSeF to work in the background and not be a daily click, it is worth approaching the topic procedurally. Altera.app can support the organization of document flow and work around finances, so that issuing and receiving invoices is more efficient and managing permissions and documents less burdensome.

‍