KSeF integration in Poland. Check your CRM and invoices

The invoice was sent, but was it accepted? Check your KSeF integration, software module and test cases before rollout.

In this article
  1. Who the requirement covers
  2. Six things to check in your software
  3. Tokens and certificates have different roles
  4. An existing module or a custom connection
  5. Test before rollout
  6. Questions before connecting systems

In short

A KSeF integration should show whether an invoice was accepted and support the rest of its workflow. A PDF or send button cannot confirm this. Check issuing, receiving, permissions and error handling. Review the legal scope and transition periods with your accountant.

Your program shows an invoice as sent. Do you also have its KSeF number and acceptance confirmation?

Start there when speaking to the software vendor. The integration should distinguish pending, accepted and rejected documents. The person handling sales needs to know what requires action.

Who the requirement covers

This article concerns Poland’s KSeF system. The Ministry of Finance explains its scope and exclusions.

Issuing became mandatory on 1 February 2026 for taxpayers whose 2024 sales exceeded PLN 200 million including VAT. Other taxpayers within scope followed on 1 April 2026, subject to transitional arrangements.

The monthly PLN 10,000 gross allowance runs until the end of 2026. The Ministry explains which invoices count toward it. It is not simply the company’s entire turnover. This particular allowance ends on 1 January 2027.

Other exclusions still matter. Issuing consumer invoices through KSeF remains voluntary. A foreign entity’s status and fixed establishment can also affect the requirement.

Review receiving and issuing separately. A small business’s temporary issuing allowance does not automatically defer receiving invoices.

Six things to check in your software

AreaWhat to ask the vendor
Format and sendingDoes it support FA(3) and the correct KSeF 2.0 API?
Processing resultWhere are each invoice’s status, KSeF number and UPO receipt?
ReceivingHow do purchase invoices reach accounting without missing documents?
PermissionsWho can issue, read and revoke a person’s access?
ErrorsWho sees a rejection, and what happens after a connection failure?
UnavailabilityHow does it distinguish special modes and track the applicable deadlines?

The API documentation separates session status from individual invoice results. Finishing an upload is not enough to mark every document as accepted.

Agree on retries after an uncertain result. The software should check the document’s state before creating another invoice without review.

Tokens and certificates have different roles

The current Ministry certificate page announces indefinite token availability and a planned amendment to the regulation. Older material gave an end date in 2026. Check the rules in force and available methods before rollout.

An authentication certificate differs from a type 2 certificate for special modes. List the required permissions, expiry dates and people responsible. Do not send private keys or tokens to a contractor in an ordinary message.

An existing module or a custom connection

First check the module in your current software. Compare its scope with your document workflow. A sending feature may leave out receiving, corrections or transfer to accounting.

Consider a custom connection when invoices originate in your CRM or store. Define the issuing trigger, data source, error responsibility and expected confirmation before development. This helps scope a CRM integration.

Test before rollout

The Ministry describes separate integration, Demo and production environments. Prepare fictional invoices in the appropriate test environment. Documents issued in production have legal effects.

Ask to see six cases. Successful acceptance, invalid document rejection, missing permission, connection failure, retry and receipt of a purchase invoice. Record the result and person responsible for each. This is an acceptance checklist, not a completed customer test.

A web application brief helps define the scope. Also limit document data using the principles described in our client data guide.

Questions before connecting systems

Does emailing a PDF replace KSeF?

For an invoice within scope, a PDF alone does not confirm issuing through KSeF. Check the required mode and processing result.

Will tokens definitely stop working at the end of 2026?

The Ministry announced their continuation and a planned regulatory change. Do not base rollout solely on an older instruction with that deadline.

Can a small business skip receiving invoices?

Receiving has separate rules. An allowance for issuing outside KSeF does not settle the receiving requirement.

Does postponing penalties defer the issuing requirement?

These are separate issues. The Sejm passed the bill on 6 November 2026. Check penalty dates with accounting against the rules in force and their effective dates.

What should we prepare for an integration discussion?

Your software’s name, invoice workflow and missing features. Start with a description without real invoices, passwords or keys.

Describe where you currently copy invoice data manually in the form below. We can help define the connection’s scope.

What would you like to change in your business?

Leave your number. We will talk about your process and see whether we can help. The first call is free.

When is the best time to call?
Controller: Oleksandr Bondarenko (BondSoft)Privacy PolicyTerms of Service
Legal details

The data controller is Oleksandr Bondarenko, trading as Oleksandr Bondarenko Software Solutions (BondSoft), ul. Jana Heweliusza 11, 80-890 Gdańsk, Poland, NIP 5833576264, e-mail: office@bondsoft.pl.

We process your data solely to contact you about your enquiry and to present an offer — on the basis of your consent (Art. 6(1)(a) GDPR and Art. 398 of the Polish Electronic Communications Law) and our legitimate interest in handling the enquiry (Art. 6(1)(f) GDPR).

Providing the data is voluntary but necessary for us to reply. You may withdraw your consent at any time by writing to office@bondsoft.pl — this does not affect the lawfulness of processing before the withdrawal.

You have the right to access your data, rectify it, erase it, restrict its processing, transfer it, and lodge a complaint with the President of the Polish Personal Data Protection Office.

Full information: Privacy Policy.

Send us an email

The service this text is about

CRM systems

A system for your industry instead of spreadsheets and an inbox, with permissions and change history.