What is KSeF: deadlines, obligations and how to integrate it

A business, technology, legal and accounting guide.

Introduction

If you run a company in Poland, use invoicing software, manage customers in a CRM, work with an ERP or simply want to automate your back-office processes, you need to understand KSeF (Krajowy System e-Faktur – National e-Invoicing System).

KSeF is Poland's national e-invoicing platform, operated by the Ministry of Finance (Ministerstwo Finansów).

It allows businesses to issue, receive, look up and store structured e-invoices through central government infrastructure.

But KSeF is far more than a new way of producing invoices. It changes how companies manage information, automate processes, share documents with their accountants and keep control of their operations.

Integrating your existing systems with KSeF can turn a tax obligation into an opportunity to modernise how your company is run.

This guide looks at KSeF from three angles:

1. As a business owner or senior manager: what integrating your systems means, how it would work and what you stand to gain.
2. As a CTO or head of technology: what the project requires, how complex it is, what the risks are and how to assess its feasibility.
3. As a legal or finance lead: how it can make compliance easier, strengthen controls, reduce administrative work and improve traceability.

1. First things first: what is KSeF and why does it matter?

Imagine your company uses a program to generate invoices.

Today, your process probably looks something like this:

1. You record a sale in your system.
2. You generate an invoice.
3. You convert it to PDF.
4. You email it to your customer.
5. Your accountant books the transaction.
6. You keep the documents for future reference or tax audits.

With KSeF, structured e-invoicing adds one essential step: the invoice must pass through the government platform whenever the transaction falls within the mandate.

The system checks that the document matches the required electronic structure and, once it accepts it, assigns an official identifier known as the numer KSeF (KSeF number).

This number identifies the invoice within the system.

One point is worth stressing: KSeF does not replace your ERP, CRM, sales system or accounting software. Nor does it decide whether your taxes have been calculated correctly.

Its role is to handle the official exchange and storage of structured invoices.

1.1. Is KSeF already mandatory?

Yes. KSeF 2.0 is live, and the mandate was phased in during 2026.

If you exceed the monthly threshold for that relief during 2026, you must start using KSeF from the invoice that takes you over the limit.

The obligation to receive invoices through KSeF started on 1 February 2026, subject to the statutory exceptions, even for companies that still had a transitional period for issuing them.

Bear in mind, too, that the mandate can apply to VAT-exempt businesses, because it does not depend solely on being an active VAT payer.

1.2. Must every transaction go through KSeF?

No.

There are exclusions and special treatments. For example:

• Invoices to private consumers (B2C) are not subject to mandatory issuance in KSeF, although they may be issued there voluntarily.
• Certain transactions and special schemes are excluded.
• Specific rules apply to foreign businesses without a seat or a relevant fixed establishment in Poland.
• Invoices from foreign suppliers are not uploaded to KSeF simply because a Polish company receives them.
• Pro forma invoices and certain internal documents or accounting notes are not submitted as structured invoices.

On the other hand, a company established in Poland may be required to issue an invoice to a foreign customer through KSeF.

In other words, selling services to businesses in Germany, Mexico or the United States does not automatically take you outside the KSeF mandate.

Your customer's nationality, the place of supply, the existence of a fixed establishment and the applicable VAT treatment all need to be assessed properly.

A. The business perspective: integrating your systems with KSeF

2. What does integrating your current system with KSeF mean?

It means enabling the software you already use to communicate electronically with the government platform, so that you do not have to handle every invoicing step by hand.

Suppose, for example, that your company uses a CRM to manage customers and contracts.

When you sell a service, the CRM already knows:

• Who your customer is.
• Which service they bought.
• How much they need to pay.
• Which currency the transaction is in.
• When it should be invoiced.
• Which commercial terms were agreed.

Instead of opening another application, re-entering the data and submitting the invoice to KSeF manually, an integration can do it from within your normal workflow.

2.1. A practical example

Imagine you sell an IT service for EUR 1,000 to another company established in Poland.

Without integration:

You record the service in your CRM, open a KSeF-compatible invoicing program, re-enter the customer's details, issue the invoice and check that it has been accepted.

Then you go back to the CRM to record the official identifier and mark the document as issued.

With integration:

1. You record the sale in your CRM.
2. Your system pulls the data it needs.
3. The integration builds the invoice in the required official format.
4. The document is submitted electronically to KSeF.
5. The integration checks whether the platform has accepted or rejected it.
6. Where applicable, the KSeF number and the official confirmation are retrieved.
7. The CRM updates the invoice status.
8. Your finance team can access the information without keying it in again.

All of this can happen without leaving your usual system, although rejected submissions, exceptions and certain checks will still need human attention.

The key advantage is that you do not have to adapt your whole company to a new invoicing tool; you adapt your tools to KSeF.

3. Which systems can be integrated?

Virtually any business system that can extract, process and transmit the required information can be integrated with KSeF, either directly or through a middleware component.

Not every project is equally difficult.

Connecting a CRM that already holds complete tax data is a very different job from integrating a legacy application that only produces PDFs.

In the second case, you will probably need to change part of how it works so that it can produce the structured data KSeF requires.

4. What functionality can you get?

A good integration should not be limited to a "send invoice" button.

It can include a range of features, depending on what your business needs.

4.1. Issuing invoices

Your system generates invoices from business transactions and submits them to KSeF where required.

This can cover standard invoices, advance invoices, final invoices and corrective invoices.

4.2. Automatic receipt

The integration regularly checks for invoices that suppliers have issued to your company.

That way, you can bring all incoming invoices together on a single platform.

KSeF does not push individual notifications to your ERP when an invoice appears; your integration has to query the system and pick up new documents.

4.3. Status tracking

You can see whether an invoice:

• Is being prepared.
• Is awaiting submission.
• Has been sent.
• Is still being processed.
• Has been accepted.
• Has been rejected.
• Needs review or correction.

The exact statuses depend on the software, but it is important to distinguish between having sent an invoice and KSeF having accepted it.

4.4. Retrieving documents and confirmations

The system can store the structured file, its KSeF number and the official confirmation of receipt (UPO, Urzędowe Poświadczenie Odbioru – Official Confirmation of Receipt).

This makes later look-ups easier and simplifies reconciliation between your commercial records and your tax documentation.

4.5. Recurring invoicing

If you bill monthly services, maintenance contracts, licences or subscriptions, you can automate much of the process.

For example, at each billing cycle your system can generate the required documents, submit them and flag any problems.

4.6. Integration with your finance team

Issued and received invoices can be made available to your accountant through the appropriate permissions or by syncing with the accounting software.

This cuts down on emailing documents back and forth.

4.7. Alerts and controls

You can set up internal alerts for situations such as:

• Rejected invoices.
• Documents awaiting regularisation.
• Communication failures.
• Credentials about to expire.
• Discrepancies between orders and invoices.
• Invoices received from unknown suppliers.

These features are built by your system or your integration provider; not all of them come out of the box with KSeF.

5. What does your company gain?

Less administrative work

You avoid entering the same data into several applications and cut down on repetitive tasks.

Fewer operational errors

Data can be submitted straight from your source records, reducing transcription mistakes.

This does not mean KSeF will catch every tax or commercial error. Data must be validated before it is submitted.

Faster document retrieval

Instead of hunting for invoices across emails, folders and files, you can consult centralised records and link them to your business transactions.

Better financial control

You can link invoices to customers, contracts, orders, due dates and payments.

Bank reconciliation and credit control are not automatic tax functions of KSeF, but they can be built into an integrated solution.

Scalability

A company issuing 20 invoices a month can manage manually without much difficulty.

A company processing thousands of invoices needs automation so that it can grow without a proportional increase in administrative work.

Greater business continuity

A well-designed integration can include processing queues, controlled retries, error logs and procedures for working through KSeF outages.

This helps ensure that a temporary communication problem does not necessarily bring all your business processes to a halt.

6. Do you have to buy a private integration?

No.

The Ministry of Finance provides free tools, including the KSeF taxpayer web application, its mobile app and services linked to e-mikrofirma.

You can use them to carry out various operations directly.

A private integration makes sense when you want KSeF to become part of your own processes.

So the business decision is not simply whether to comply, but how:

Comply by doing the work manually, or comply by automating the operations that matter to your business.

If you issue few invoices, a free tool may be enough.

If you manage many customers, bill on a recurring basis or rely on several systems, integration can deliver significant operational benefits.

B. The CTO perspective: assessing project feasibility

7. How complex is it to integrate a system with KSeF?

From a technology standpoint, KSeF is a platform that exposes an official API.

An API, or Application Programming Interface, is a mechanism that lets two computer systems exchange information according to predefined rules.

Put simply, it acts as a controlled gateway between your software and KSeF.

Your application prepares and sends specific requests, and KSeF returns the corresponding responses.

Integration is technically feasible because the Ministry of Finance provides documentation, test environments, OpenAPI specifications and development libraries.

However, the hardest part is usually not establishing the connection, but making sure your company's processes and data meet the tax and operational requirements.

8. What does an integration need technically?

8.1. System access and authorisations

KSeF needs to know who is performing each operation and on behalf of which taxpayer.

Your integration must use approved authentication mechanisms.

These include KSeF certificates and the tokens permitted under the applicable rules.

There are also electronic identification methods used to log in, manage permissions and request certificates.

Once authentication via the API is complete, the software can obtain temporary access credentials to carry out the permitted operations.

This means deciding who may issue invoices, who may view them and who may manage authorisations.

It is not advisable to grant full administrative access to an application that only needs to issue invoices.

Certificates and tokens

KSeF provides for two specific types of certificate:

• Type 1: authenticates the holder to the system.
• Type 2: identifies the issuer in certain offline invoicing procedures.

Certificates are valid for a maximum of two years.

As for tokens, the original plan was to allow their use until the end of 2026. However, the Ministry of Finance later announced in its official documentation (the Podręcznik KSeF 2.0 manual and the official KSeF certificates page) its decision to keep them indefinitely, together with a planned amendment to the implementing regulations.

Your technical design should therefore take this change into account and confirm how it is finally implemented in law.

Certificates and tokens are not functionally identical. In particular, authentication certificates identify their holder, while authorisations are managed through the KSeF permissions model.

8.2. Invoice format: FA(3)

KSeF does not use a conventional PDF as the primary document.

Invoice data is represented in XML, using an official schema called FA(3).

XML is a format that structures data so that other computer systems can interpret it.

For example, an invoice contains information such as:

• The issuer's tax identification.
• The buyer's identification.
• The internal invoice number.
• The issue date.
• A description of the goods or services.
• Quantities and prices.
• Net amounts.
• Taxes and tax treatments.
• Currency.
• Total amount.
• Permitted supplementary information.

The integration must transform ERP or CRM data into the official FA(3) schema.

This process is known as data mapping.

Why does it matter?

Because your system probably stores information differently from the way KSeF requires it.

For example, your application may have a field called total, whereas the official schema requires certain information to be split across specific elements.

In addition, some transactions require data you may never have stored before.

That is why reviewing your data model before development starts is essential.

FA(3) also covers corrective invoices, advance invoices, final invoices and certain additional data structures.

8.3. Validation

Before submitting an invoice, your system should check that:

• All mandatory data is present.
• The amounts are consistent.
• The transaction uses the correct tax treatment.
• The currency and values are expressed correctly.
• The XML complies with the FA(3) schema.
• No attempt is being made to reissue a document that is already registered.
• Valid permissions are in place for the operation.

It is particularly important to distinguish between two types of validation.

Technical validation: determines whether a document complies with the structural rules and can be processed.

Tax and commercial validation: determines whether the amounts, recipients, VAT rates and other data are correct for the actual transaction.

KSeF may accept a technically valid document that contains tax or commercial errors.

For example, an incorrect NIP (Numer Identyfikacji Podatkowej – Polish tax identification number) or a wrong total will not necessarily cause the XML to be rejected.

8.4. Submission, tracking and confirmations

The KSeF 2.0 API allows invoices to be submitted in interactive sessions and batch sessions.

Interactive sessions suit individual operations; batch sessions are useful when large volumes need to be processed.

Submission involves encryption and asynchronous processing.

Asynchronous means the system may accept a request first and process its outcome later.

So it is not enough to check that the server responded to a request.

The integration needs to check the document's final status, retrieve its KSeF number and obtain the corresponding UPO.

8.5. Receipt and synchronisation

The integration can also query received documents.

The Ministry provides mechanisms for searching, downloading and incrementally importing invoices.

Incremental download lets you retrieve new documents without needlessly re-fetching the entire history.

This is important for accounting systems, ERPs, administrative platforms and solutions serving multiple companies.

8.6. Security

The documents handled by the integration contain commercial and financial information and, in some cases, personal data.

For that reason, the project should cover:

• Encryption of communications and of any data that needs protecting.
• Protection of private keys, certificates and tokens.
• User management and least-privilege permissions.
• Logging of administrative actions.
• Monitoring for anomalous access.
• Rotation and revocation of credentials.
• Backups of locally held data.
• Oversight of technology providers with access to the data.
• Incident response procedures.

Credentials should never be stored directly in source code or exposed in error logs.

9. What would the integration architecture look like?

A common architecture uses an intermediate layer, known as middleware or a connector.

Its purpose is to avoid building all the KSeF communication logic directly into the business system.

The flow runs through four layers, from top to bottom:

Communication needs to be two-way if you want to both issue and receive invoices.

One advantage of this architecture is that you can keep your current system and change only the connector when certain aspects of the API or the exchange rules change.

It does not remove the need to adapt your ERP when the tax data it has to supply changes.

10. What happens if KSeF goes down?

This is one of the most important questions for any CTO.

No company should depend on an external service being available at all times.

KSeF provides for several special modes, including:

As a general rule, invoices issued in offline24 mode must be submitted by the next business day at the latest.

When KSeF unavailability has been announced, the standard deadline for regularisation is the business day after it ends.

In declared failure mode, the general deadline is seven business days from the end of the failure.

Total failure scenarios are governed by different rules.

You should not treat these modes as interchangeable options: their requirements, dates and document delivery rules differ.

A professional integration should account for these contingencies from the initial design, not after the first outage.

Among other things, you will need to hold pending documents, track deadlines and prevent duplicate submissions.

11. A particularly important technical issue: duplicate invoices

Suppose your application submits an invoice and loses its connection before receiving the final response.

What do you do?

If you simply resend it without checking what happened, you may trigger errors or a duplicate submission attempt.

The architecture must maintain a verifiable link between:

• Your internal invoice identifier.
• The request or session reference.
• The processing status.
• The KSeF number, once assigned.
• The retrieved confirmations.

This lets you resume processes without wrongly assuming that every failed request must be repeated.

You also need to distinguish between a rejected invoice and an accepted one that needs correcting.

Once accepted, an invoice cannot be edited or deleted from the system like an ordinary file.

As a rule, errors are corrected by issuing a corrective invoice (faktura korygująca).

12. What are the technology options?

As CTO, you can weigh up three main approaches.

The best option depends on your current system, transaction volume, budget and security requirements.

It does not always make sense to build from scratch an integration your ERP vendor already provides properly.

On the other hand, if you run your own platform with hundreds of customers, a reusable architecture can become a strategic investment.

13. How long might the project take?

There is no one-size-fits-all timeline.

As a rough planning guide only, not a committed timeline:

These estimates assume access, documentation, cooperation from the finance team and testing capacity are in place.

A CTO should plan for the following phases:

1. Assessment: review the current system and processes.
2. Functional and tax analysis: determine which transactions need to be handled.
3. Design: define the architecture, security, data and responsibilities.
4. Development or configuration: build the chosen integration.
5. Testing: validate standard and exceptional scenarios.
6. Go-live: deploy with monitoring and contingency measures.
7. Maintenance: handle incidents and regulatory and technical updates.

13.1. Available environments

The Ministry of Finance provides three main environments:

• TEST: integration testing with fictitious data (for example, random NIP numbers), never with real company data.
• DEMO: a pre-production environment configured like production, for final validation of the integration, without tax effect.
• PRODUCTION: the official environment, where accepted invoices have legal effect.

You should never use production to test with dummy invoices.

13.2. What drives the cost?

The cost depends mainly on:

• The quality of your existing data.
• The number of systems to connect.
• Document volume.
• Whether you need issuance, receipt or both.
• The range of tax scenarios.
• Continuity and security requirements.
• The number of companies sharing the integration.
• The support and maintenance required.

The Ministry does not require you to buy a private solution in order to use KSeF.

The costs of an integration project come mainly from development, commercial licences where applicable, infrastructure, operations and maintenance.

14. How do you know the integration is working properly?

It is not enough to check that a test invoice reached KSeF.

A project should also test:

• Standard invoices.
• Corrective invoices.
• Invoices in foreign currencies.
• Sales to foreign customers.
• Advance and final invoices.
• Rejected documents.
• Duplicates and interruptions.
• Revocation of permissions.
• Certificate expiry.
• Downloading received invoices.
• High-volume processing.
• Special offline modes, where they are in scope.
• Updating internal status after receiving KSeF responses.

It is also wise to set objective acceptance criteria.

For example, every submitted invoice should be traceable to its internal document, final status, KSeF number and official confirmation where applicable.

C. The legal and accounting perspective: compliance, control and efficiency

15. Why does KSeF matter to the legal team?

From a legal standpoint, KSeF changes fundamental aspects of document management and tax evidence.

You can no longer think of an invoice as a file you can replace, delete or redo.

A structured invoice accepted in KSeF is part of a formal procedure laid down in Polish law.

That has consequences for corporate controls.

15.1. Invoice traceability

KSeF assigns an official identifier to accepted invoices.

This helps link documents to business transactions and makes them easier to find.

However, the KSeF number does not in itself prove that goods were delivered, that a service was provided or that the invoice is correct for tax purposes.

An invoice can be properly registered and still document a transaction that never took place, or contain errors.

Technical traceability must therefore be backed by legal and commercial controls.

15.2. Greater clarity on issuance and receipt

Dates take on particular importance.

In online mode, the legal date of issue is determined by the KSeF submission rules.

When the statutory offline modes are used, special rules apply that take into account the date shown on the invoice.

Likewise, the date of receipt through KSeF is tied, subject to the relevant exceptions, to the assignment of the KSeF number.

This can affect the analysis of contractual obligations, deadlines and accounting processes.

It is therefore worth reviewing any contracts in which legal consequences depend on receipt of an invoice.

15.3. Access control and responsibilities

The integration lets you define who may act on the company's behalf.

For example:

• Sales staff can prepare invoices.
• The finance manager can approve them before submission.
• The authorised system can send them to KSeF.
• The accountant can view the documents they need.
• Administrators can manage authorisations within their remit.

Proper segregation of duties reduces the risk of errors, misuse and unauthorised operations.

This segregation can be achieved by combining KSeF permissions with internal controls in your business software.

15.4. Document corrections

As a general rule, invoices accepted by KSeF cannot be modified or deleted.

If an invoice contains an error, you must use the statutory correction procedure.

This keeps a documentary link between the original record and any subsequent changes.

It also means organisations need upfront validation controls, because correcting a document after acceptance can take more work than preventing the error in the first place.

15.5. Data protection and confidentiality

The integration may involve access to data about customers, representatives, suppliers and business transactions.

When you use an external technology provider, you should review:

• What information it can access.
• For what purposes it processes it.
• Where it is stored.
• Who can access it.
• Which subcontractors are involved.
• How it is protected.
• What happens when the contract ends.

The General Data Protection Regulation (GDPR, known in Poland as RODO) may apply where personal data is processed.

Depending on the service model, a data processing agreement under Article 28 GDPR may be required.

If access or processing takes place from countries outside the European Economic Area, the rules on international transfers must also be assessed.

There is no general requirement for every technology component a company uses to be physically hosted in Poland simply because it connects to KSeF.

What matters is that the architecture complies with the applicable law, security requirements and contractual obligations.

16. What does the legal team gain?

A properly implemented integration can help to:

Strengthen evidence management. By linking each invoice to its identifier, confirmations, transactions and authorisations.

Reduce documentary risk. Through validation, approval procedures and controls over corrections.

Make audits easier. By retrieving information and evidence without relying solely on scattered files.

Formalise responsibilities. Through internal policies on issuance, receipt, review and incident handling.

Improve relationships with technology providers. When contracts clearly define security, confidentiality and continuity obligations.

However, KSeF does not replace contract review, does not automatically determine whether a business transaction is valid and does not, on its own, guarantee GDPR compliance.

17. What changes for accountants?

Some of the most significant operational benefits are likely to be felt in the finance department.

Traditionally, many processes require companies to send PDF or paper invoices to their accountant at regular intervals.

The accountant receives the documents, keys in the data, checks the amounts, requests corrections and prepares the tax records.

With KSeF, part of that work can change.

17.1. Direct access to documents

A company can grant its accounting firm the permissions needed to view or issue invoices within the system.

This means you no longer have to rely solely on someone remembering to send every document.

You can also integrate the documents directly with your accounting software.

Structured receipt makes automated reading easier and reduces manual data entry.

17.2. Less data entry

A structured invoice contains fields that can be read by software.

This allows information to be imported, such as:

• Issuer and recipient.
• Number and date.
• Line items.
• Amounts.
• Currency.
• Taxes.
• Transaction-related information.

Instead of transcribing that information, the accountant can spend more time reviewing its consistency, classification and tax treatment.

17.3. More efficient reconciliation

By integrating KSeF with an ERP or financial system, you can link:

• Orders.
• Invoices.
• Goods received notes.
• Contracts.
• Payments.
• Bank transactions.

KSeF does not perform all of this reconciliation automatically.

But it does provide structured data that can be used to build it.

17.4. Better preparation of returns and records

In Poland, accounting and tax obligations may include VAT records and returns such as JPK_V7 (Jednolity Plik Kontrolny – Standard Audit File for Tax) where applicable.

Since February 2026, the new JPK_V7M(3) and JPK_V7K(3) structures include KSeF numbers and other markers that apply depending on the document type.

An integration can pass this information to the accounting software and reduce data entry errors.

This does not mean KSeF files all your tax returns automatically.

The obligation to keep accurate records, calculate taxes and file the relevant returns remains.

17.5. Document storage

Structured invoices are stored in KSeF for ten years from the end of the year in which they were issued.

So invoices issued in 2026 are covered by that official storage period until the end of 2036.

This reduces the need to keep your own copies solely to meet certain invoice retention obligations.

However, other obligations may require you to keep supporting documentation or retain invoices for longer, for example where a tax limitation period extends beyond the period covered by KSeF.

A company may also choose to keep internal copies for operational and continuity reasons.

17.6. VAT refunds

The introduction of mandatory KSeF came with a reduction in the standard VAT refund period from 60 to 40 days, subject to the applicable statutory conditions.

This can help business cash flow.

However, you should not assume that buying a private integration guarantees a refund within 40 days, or that every claim automatically qualifies for that treatment.

The actual timeframe depends on the rules governing the refund.

18. Which tasks will remain the accountant's responsibility?

Automation does not replace professional judgement.

You will still need your accountant for matters such as:

• Determining the correct VAT treatment.
• Classifying income and expenses.
• Reviewing deductions.
• Handling intra-Community transactions.
• Reviewing imports and exports.
• Determining reverse charge treatment.
• Applying currency conversion rules.
• Analysing special transactions.
• Preparing tax returns.
• Reviewing adjustments and corrections.
• Assessing supporting documentation.

A platform can check that a field has been filled in, but not necessarily that the chosen tax treatment is legally correct.

Automation should reduce mechanical work and free your accountant to focus on higher-value professional tasks.

19. What about international invoicing and currencies?

This is particularly important if your company works with customers in several countries.

KSeF supports invoices denominated in foreign currencies.

For example, you can issue documents in EUR or USD where the transaction and tax rules allow it.

The FA(3) format includes currency information and certain fields for conversions.

Where Polish VAT is charged on an invoice in a foreign currency, specific obligations may apply to show the tax amount in PLN and use the exchange rate required by law.

You also need to distinguish between three concepts:

Invoicing currency: the currency in which you express the value of the transaction.

Payment currency: the currency in which you actually receive the funds.

Accounting currency: the currency used for your accounting and tax obligations.

They do not necessarily have to be the same.

Example

Suppose your Polish company invoices a Mexican customer EUR 2,000 for services.

The transaction might require you to:

1. Determine whether it falls under the KSeF mandate.
2. Assess its VAT treatment under the applicable rules.
3. Prepare the invoice in EUR.
4. Submit it to KSeF if required.
5. Retrieve its KSeF number.
6. Deliver the invoice to the foreign customer through an agreed channel, for example a PDF visualisation with the required QR code.
7. Book the transaction and properly account for any exchange differences that arise.

Do not assume that the invoice amount necessarily equals the net amount that reaches your bank after fees or conversions.

Nor should you confuse the obligation to use KSeF with the obligation to charge Polish VAT.

The two are legally related, but distinct.

D. Compliance and business risk

20. What happens if your company fails to comply with KSeF?

During 2026, transitional rules prevent KSeF-specific financial penalties from being applied to breaches committed in that period.

However, this does not remove general tax obligations.

From 1 January 2027, the rules provide for specific administrative penalties. In September 2026 the Ministry of Finance announced plans to defer them until the end of 2027 (not yet law).

The statutory caps include:

• Up to 100% of the VAT shown on the invoice.
• Up to 18.7% of the invoice total where no tax is shown.

How they apply depends on the type of breach and the relevant legal circumstances.

This does not mean every irregularity automatically attracts the maximum penalty.

The situations to guard against include issuing outside KSeF when you are required to use it, missing certain submission deadlines and using procedures that do not apply.

That is why the integration project must include both technical validation and tax review procedures.

21. What about bank payments?

From 1 January 2027, certain transfers between active VAT payers will have to identify the invoice by its KSeF number or a collective identifier, under the conditions laid down by law.

This also applies to certain payments made under the split payment mechanism (Mechanizm Podzielonej Płatności, MPP).

It does not mean that every bank transfer, international payment or advance payment without an invoice must carry a KSeF number.

The scope depends on the type of transaction and the parties involved.

From a technical standpoint, your ERP should store KSeF numbers correctly so they can be used, where required, in treasury and reconciliation processes.

22. What risks should a company consider before integrating?

E. How do you decide whether an integration is worth the investment?

23. Assessing the return

Before commissioning a project, work out how much time and how many resources your invoicing process currently consumes.

For example, imagine your company processes 400 invoices a month and the associated manual tasks take three minutes per invoice on average.

That adds up to 20 hours a month.

If an integration saved half that time, you would recover ten hours a month.

This calculation is purely illustrative.

To assess the return on investment properly, you should consider:

• Administrative time saved.
• Errors avoided.
• The cost of corrections.
• Current software costs.
• Implementation costs.
• Maintenance.
• The benefits of integrating several processes.
• Expected growth in volume.

An integration can be justified by administrative savings, but also by continuity, control and reduced operational risk.

The investment is especially attractive when the same connector can serve several applications or companies.

24. What should a professional integration proposal include?

A serious proposal should clearly explain:

Initial assessment. Which systems will be connected and what information is available.

Functional scope. Which operations will be automated: issuance, receipt, corrections, confirmations, notifications and any other contracted functions.

Technical design. How communication will work, where the integration will run and how credentials will be protected.

Responsibilities. Who supplies tax data, who validates the business rules and who manages authorisations.

Test plan. How the integration will be verified in the official environments.

Go-live. The procedure for switching the service on without unnecessary disruption to operations.

Support and maintenance. How incidents and regulatory or technical changes will be handled.

Deliverables. Which documentation, access, manuals and evidence the client will receive.

Acceptance criteria. The specific results that must be achieved for the implementation to be considered complete.

A proposal that simply says "we'll connect your software to KSeF" is not enough to assess the scope and responsibilities properly.

25. What should you ask before signing up?

Before choosing an integrator, make sure you have answers to these questions:

1. Does the solution use the official KSeF 2.0 API?
2. Is it compatible with FA(3)?
3. Can it both issue and receive invoices, or only issue them?
4. How are rejected invoices handled?
5. Can it retrieve the KSeF number and UPOs?
6. What happens if the government service is temporarily unavailable?
7. How are certificates, tokens and data protected?
8. Who is responsible for keeping the integration up to date?
9. Does it handle invoices in other currencies and foreign customers?
10. What controls are in place against duplicates?
11. How are operations and incidents logged?
12. What happens if you decide to switch provider?
13. Has the integration been tested with cases similar to yours?
14. What is explicitly excluded from the service?

These questions help you tell the difference between basic connectivity work and an enterprise integration solution built for continuous operation.

F. Use cases

26. Examples of businesses that can benefit from KSeF

Professional services firm

A consultancy that manages contracts in a CRM can generate invoices directly from the services delivered, submit them to KSeF and sync them with its accounting.

Hosting and IT services provider

A company that bills monthly for web hosting, licences or maintenance can use its subscription records to automate invoiceable documents.

The system can link contracts, billing periods, renewals, invoices and payments.

E-commerce

An online shop can link certain orders to its invoicing system and submit the documents that must be issued in KSeF.

Business sales need to be distinguished from consumer sales, as they are not necessarily treated the same way.

Logistics company

An organisation handling large numbers of orders and deliveries can link its invoices to operational data to reduce errors and make reconciliation easier.

Accounting firm

A firm serving several companies can manage the access each client authorises and integrate received documents into its accounting processes.

This can reduce manual file exchange.

SaaS developer

A platform providing administrative services to multiple companies can offer a KSeF integration module as part of its feature set.

In this case, it is especially important to design proper separation of each company's data, credentials, permissions and tax context.

27. Official resources to get started

The Ministry of Finance publishes documentation for businesses, integrators and developers.

Legal and business information

• Official KSeF portal
• Scope of the mandate and exclusions
• FA(3) invoice structure
• KSeF certificates
• Official questions and answers
• Official materials and manuals
• Act of 5 August 2025 amending the VAT Act for mandatory KSeF (Dz.U. 2025 item 1203)
• New JPK_V7M(3) and JPK_V7K(3) structures, applicable from 1 February 2026

Technical documentation

• Official portal for integrators
• KSeF 2.0 API documentation
• Test API
• Demo API
• Official technical repository on GitHub
• API changelog
• Offline modes and submission deadlines

The official repository includes examples, documentation on authentication, invoice operations and session management, and reference libraries for .NET and Java.

The changes published in September 2026 show why connectors need to be kept up to date, even now that KSeF is live.

Conclusion: integrating KSeF is about much more than automating invoices

The rollout of KSeF in Poland is a major shift in how companies manage tax and documentation.

For business owners, integration means continuing to use familiar tools while automating processes, cutting repetitive work and gaining tighter control over invoicing.

For CTOs, it is a feasible project built on officially documented technology, but one that demands close attention to architecture, security, data validation, status management and operational continuity.

For legal teams, it offers opportunities to strengthen traceability, accountability, document controls and compliance procedures.

For accountants, it reduces manual data entry, improves access to structured information and frees up time for analysing and reviewing transactions.

That said, the value of an integration depends on sound design and on the involvement of the people responsible for technology, administration and tax.

KSeF is mandatory for many business transactions in Poland; integrating your systems with it properly is a decision about efficiency, continuity and modernisation.

The best integration is not necessarily the most complex one. It is the one that meets the applicable requirements, keeps your data secure and makes your day-to-day operations simpler, more controlled and more reliable.

Scope note: this guide describes the general framework in force and the technology currently available. Specific tax treatments, exceptions and contractual obligations must be checked against each company's circumstances and the applicable rules. The recommendations on architecture, phases and timelines are implementation guidance, not universal legal requirements.