KSeF and invoicing
KSeF for small businesses in Poland: an integration and continuity checklist
KSeF changes more than the way an invoice is issued. It changes when the buyer receives it, how approvals work, who needs access, and what the team does when a document is rejected or the service is temporarily unavailable.
Being ready for KSeF means the company can receive, approve, account for, and issue an invoice when an exception occurs. Access to the government app or a KSeF button in accounting software is not enough.
Quotable definition
KSeF readiness is a company’s ability to receive, issue, approve, and account for structured invoices while controlling permissions, errors, offline modes, and continuity.
What applies to small businesses in 2026
Since 1 February 2026, domestic buyers with a Polish tax identification number receive invoices through KSeF. Most other businesses became required to issue structured invoices on 1 April 2026. The smallest taxpayers, whose monthly invoiced sales do not exceed PLN 10,000 gross, have an issue-side deferral until 1 January 2027.
The dates matter, but an owner should begin with the document flow. Who retrieves purchase invoices, how do they reach accounting, who approves a cost, and who responds when validation fails? Without clear answers, KSeF can become another inbox that nobody consistently owns.
Start with responsibility and permissions
Access to invoices and the ability to issue them should reflect actual roles. The owner, accountant, administrator, and external accounting firm do not need identical rights. The company should also decide who grants and revokes access after an employee or supplier changes.
Use the least access required. An integration should not depend on an employee’s personal account or credentials nobody knows how to replace. It needs a technical owner and a short recovery instruction.
- a list of people and entities using KSeF
- rights to issue, receive, and manage permissions
- integration authentication and certificate renewal dates
- an offboarding process for employees and accounting providers
The integration should cover the whole flow
A useful integration retrieves invoices and official acknowledgements, detects duplicates, assigns a status, and sends the data into the right workflow. A purchase invoice may need a project code and manager approval, while a sales invoice may require a customer-data check before submission.
Not every small company needs a custom API integration. If the accounting product handles KSeF reliably, use it and connect only the missing stages: approvals, cost descriptions, alerts, or an exception report. Custom code makes sense when the standard module does not match the company’s process or several systems must be coordinated.
Exceptions worth testing
The largest risk sits at the edge of the happy path. Run an end-to-end test with corrections, rejected documents, offline issuance, and an invoice for a new customer.
Every failure needs a visible status, owner, and next action. An integration that retries forever can hide the problem. Set retry limits, keep an event log, and alert a human.
- missing access or an expired certificate
- a document rejected because of invalid data
- temporary KSeF or accounting-system downtime
- a correction, duplicate, or document outside the standard flow
Acceptance checklist
Before calling the implementation complete, the company should know where to see every invoice, its KSeF number, status, and error history. The team should know how to operate during an outage and reconcile discrepancies with accounting.
A useful test is one trial day without the implementer. If an employee can process a normal document, find an exception, and follow the recovery guide, the system is closer to production than to a demo.
- tested invoice issue and receipt
- documented roles, permissions, and responsibilities
- alerts and a queue for documents requiring action
- offline procedure, data backup, and team instructions
- integration monitoring and a named incident owner
FAQ
Frequently asked questions
Must a small business receive invoices through KSeF?
As a rule, domestic buyers with a Polish tax identification number have received invoices in KSeF since 1 February 2026, even if the smallest taxpayers still have an issue-side deferral.
Is KSeF support in accounting software enough?
It may cover communication with KSeF, but the company still needs rules for access, approvals, cost coding, exceptions, and outage handling.
When is a custom KSeF integration useful?
When the standard module does not match the real workflow, several systems must be coordinated, or the company needs custom validation, alerts, and exception reporting.
Next step
Want to find the first workflow worth automating?
Bring one manual workflow or IT bottleneck. In 20 minutes, we will identify 3-5 improvements, estimate time saved, and tell you whether the right answer is automation, integration, an internal tool, or ordinary IT work.
Book a free workflow audit