On April 28, 2026, Poland's Ministry of Finance confirmed that a new functionality had been made available in the KSeF 2.0 taxpayer application: taxpayers can now report invoices they suspect are linked to fraud or abuse directly from within the application itself. The ministry notes that the feature was made available on April 24 and that the old standalone KSeF reporting form should no longer be used for these cases.
24 Apr 2026
Functionality made available
In-app
Reporting now happens inside KSeF 2.0
24/7
KAS hotline support remains available
What Changed
The ministry has moved suspected scam-invoice reporting into the core KSeF experience. The reporting path is operationally simple: log in to the KSeF 2.0 taxpayer app, open the invoice list, select the invoice, enter the details view, use the abuse-report option, provide the reason and justification, confirm the declaration, and submit.
This is not just a user-interface change. It embeds fraud escalation into the same environment where invoice review already happens. That reduces friction, shortens internal response time, and creates a cleaner audit trail around suspicious documents.
Why It Matters
KSeF is maturing operationally
Poland is showing that mandatory e-invoicing platforms need more than schema validation. They also need controls for suspicious activity, operational review, and trusted escalation paths.
Fraud review becomes process-native
Instead of forcing users into a separate form or side process, the ministry has placed reporting where invoice handling already happens. That design choice matters for adoption and response speed.
Internal governance has to catch up
Finance teams now need a clear decision tree: who reviews suspicious invoices, what evidence gets captured, what gets reported externally, and how the ERP records the incident.
Controls become part of compliance readiness
As KSeF becomes mandatory at scale, authorities will expect businesses to manage exceptions in a structured way, not only process happy-path invoices correctly.
Workflow Impact
For AP, tax, and ERP teams, the practical implication is that suspicious invoices can no longer sit in an informal grey zone. Teams need a documented path for triage, escalation, and evidence capture. That may include status fields in the ERP, role-based approval steps, links to KSeF invoice IDs, and handoffs between finance and compliance.
Recommended internal rule
Treat suspected scam invoices as a dedicated workflow state, not as a generic exception. That helps separate fraud-risk handling from ordinary validation errors and supports cleaner reporting to the tax authority.
What To Do Next
Update your KSeF operating procedures to reflect the in-app abuse-report flow.
Define who in finance or tax is authorised to submit a report externally.
Capture KSeF identifiers and evidence in your ERP or case-management workflow.
Train AP teams to distinguish suspicious invoices from ordinary XML or data-quality issues.
Review whether your integration layer should flag suspicious patterns before users even enter the KSeF portal.
Final takeaway
Poland's latest KSeF 2.0 update is a reminder that compliance platforms do not stand still after launch. The next phase of readiness is not only about generating valid invoices. It is about handling risk, exceptions, and trust inside the same digital process.
Contact us