KSeF: What to Do When the Mobile App Is Not Working

If the KSeF mobile app is not working, do not start by deleting data or reinstalling it. First identify whether the problem is the phone, app version, National Login Node authentication, company permissions or KSeF availability.

The KSeF 2.0 mobile app works in the production environment. This means an invoice submitted from the app enters the real legal and accounting workflow.

If the invoice is urgent, prepare a fallback: a web app, accounting system, API integration or KSeFGPT. The objective is not to fix the phone at all costs, but to issue valid FA(3) XML, submit it to KSeF and receive the KSeF number and UPO.

The common mistake is to call every issue "KSeF is not working". A crashing app, failed biometrics, an outdated version, a Profil Zaufany outage, missing NIP permissions and official KSeF unavailability are different situations.

The Ministry of Finance describes the KSeF 2.0 mobile app as a free tool for entrepreneurs, available in Google Play and the App Store. It supports invoices, buyers, bank accounts, business-card data, invoices and corrections. The official page also states that the app is available only in production.

Separate the problem into four layers:

1. Phone: operating system, network, memory, biometrics and the browser used during authentication.

2. App: version, forced update, terms acceptance, local data and drafts.

3. Identity and permissions: National Login Node, Profil Zaufany, mObywatel, mojeID, e-ID and actual company permissions.

4. KSeF: service status, maintenance, unavailability, failure or request limits.

Once the layers are separated, diagnosis becomes much safer.

The table below summarizes the most important decisions: when to fix the app and when to switch to another submission channel.

Start with reversible actions. Do not delete the app, clear data or reset configuration until you know whether you have a draft copy, cloud synchronization or another way to access the invoice.

Follow this order:

1. Internet: switch between Wi-Fi and mobile data.

2. Update: check whether the store requires a new app version.

3. Restart: close the app, restart the phone and try again.

4. PIN instead of biometrics: use the app PIN if fingerprint or Face ID fails.

5. National Login Node: check the login method outside the app.

6. KSeF status: check MF announcements or the KSeF status page on KSeFGPT before treating the problem as local.

If basic diagnostics do not require deleting data, the next step is the app version.

The official changelog says the KSeF 2.0 mobile app was adapted to KSeF 2.0 and the FA(3) structure. As checked on 31 May 2026, MF lists version 2.2.2, focused on stability improvements. The App Store requires iOS 15.0 or later, so an older phone can be an operational blocker.

Some issues can come from the update process itself. Depending on configuration, an update may be forced, re-authentication may be required and updated terms may need to be accepted.

Before reporting an error, note the app version, phone system, time and screen of the error, whether re-authentication was required and whether new terms were accepted.

The KSeF mobile app is not just an invoice note-taking tool. Access requires identity confirmation through the National Login Node, for example mObywatel, mojeID, e-ID or Profil Zaufany. The app then checks permissions for the company context.

If you see no company profile or cannot act for a NIP, the login may be correct while the permission scope is wrong.

Check identity, company context and permission scope. A user may be authenticated but still unable to submit invoices for a company.

A mobile app problem is not always a KSeF problem. MF may publish separate technical notices about app maintenance or Profil Zaufany unavailability. The user may feel that KSeF is down while only one layer blocks the process.

Test whether the same issue appears on another device, in a web app, in accounting software or through an integration. If only one phone fails, diagnose the phone or app. If many tools cannot authenticate through the same identity method, check the identity provider. If independent tools cannot send invoices, check official announcements and the KSeF status page on KSeFGPT.

For urgent submission, check MF announcements, login availability, another tool such as ERP, API or KSeFGPT, and the current document status before recreating the invoice.

If the invoice is urgent, the question is not how to repair the app, but how to safely get the document into KSeF. The mobile app is one tool, not the only way to work with a structured invoice.

Your options are to finish later in the app, use another official channel, use accounting software or an API integration, or switch to KSeFGPT for FA(3) XML validation, submission history and UPO handling.

KSeFGPT works in the browser, supports invoice preparation, imports, data checks, KSeF submission and status tracking. Its interface is fully rendered for mobile devices as well, so it can also be used on a phone or tablet through the browser. It does not repair the MF mobile app, but it can provide an operational fallback.

A typical small-business scenario: the owner starts an invoice on a phone, the app stops responding after an update and the customer is waiting. Instead of deleting the app and risking the draft, recreate the data in a web process, check status and download UPO in KSeF after acceptance.

Offline and failure modes are not a remedy for every phone problem. If only your mobile app fails while KSeF and other channels work, it is usually not an official system failure.

Official modes matter when the problem affects legal work with KSeF, not only the comfort of one app. MF describes offline24, KSeF unavailability, KSeF failure and total failure. Each has different consequences and deadlines. See How long to submit an invoice to KSeF?.

As a rule: phone failure means use another device or tool, mobile app failure means use web, ERP, API or KSeFGPT, identity failure means try another login method, and official KSeF unavailability means follow the MF announcement.

The Ministry of Finance lists `info.ksef@mf.gov.pl` for KSeF mobile app support. A useful report helps distinguish app, login, permission and service-status issues.

Provide the app version and phone system, date and time, screen where the error appeared, login method, whether the issue appears in another channel and a screenshot with sensitive data hidden.

The mobile app is convenient, but it should not be the only access point if the company issues invoices regularly. A phone can discharge, be lost, lose biometric access or get stuck on an update.

The minimum operating setup is a second access channel, clean permissions, a submission register, update control and an urgent fallback procedure.

KSeFGPT helps by moving the process from one phone to the browser and keeping invoices, imports, validation and statuses in one place. It is still mobile-friendly: the KSeFGPT web app is fully rendered for mobile devices and can serve as a backup path on a smartphone. See also common KSeF implementation challenges.

The biggest risk during mobile app trouble is not the technical error itself, but acting without checking the document status. A user who does not see confirmation on the phone may recreate the invoice elsewhere, only to discover that the original submission was accepted or is still processing.

Separate the tool from the proof. The tool may be the mobile app, web, ERP or KSeFGPT. The proof of acceptance is the KSeF number and UPO.

For occasional invoicing the mobile app may be enough. For accounting offices, teams or higher correction volume, the safer process is one that does not depend on one phone and one login method.

To prepare a reliable KSeF fallback process, start with these four articles:

How long to submit an invoice to KSeF? - deadlines for online, offline24, unavailability and failure modes.

UPO in KSeF - what the official receipt confirms and why clicking submit is not enough.

Common KSeF implementation challenges - organizational and technical risks to solve before the mandatory process.

KSeFGPT - import, export, AI and analytics for invoices - how an alternative browser-based KSeF invoice process works.