As published, Poland's national e-invoicing system, KSeF, became mandatory in phases in 2026: from 1 February 2026 for large taxpayers with turnover above PLN 200m, and from 1 April 2026 for other entities, with micro-entrepreneurs following from 1 January 2027. That is as published — confirm current rules with your tax or legal adviser. Kraków has a large IT and business-services sector, and firms there often run several systems side by side that all touch an invoice.
LATYNEX Digital builds the workflows that connect those systems to the invoicing route a company already uses. This page covers that work for Kraków businesses. The general service is at Workflow Automation & Systems Integration, and the market overview is at LATYNEX Digital for businesses in Kraków.
Typical industries
- IT services and software houses
- Business-process outsourcing and shared-service centres
- Financial and accounting services
- Education and research-linked companies
- Tourism and hospitality operators
- Light manufacturing and trade
Common lead-handling problems
- Invoice data re-typed between the CRM or ERP and the invoicing tool
- Rejected or failed documents that nobody is assigned to fix
- No agreed source of truth for the invoice record across systems
- Contract and time-based billing data that lives in spreadsheets
Direct answer
If a Kraków company re-types invoice data between its ERP, CRM or billing sheet and the tool it uses for KSeF, LATYNEX scopes and builds the workflow that moves that data once, from one agreed source, with validation before hand-off and a queue for documents that come back rejected. The invoicing tool or provider you already use stays responsible for the submission.
Why the global workflow page is not enough for Kraków
The global Workflow Automation & Systems Integration page does not assume any national invoicing system. Here the target is fixed: a phased Polish rollout with different start dates by company size, which means two Kraków companies can face different timing. Our first task is to establish which of your systems holds the authoritative invoice record and what your submission route expects. This page is about finance and order data flowing into KSeF from a services or BPO firm's systems, not about development infrastructure or warehousing.
What we build
The workflow sits between your business systems and your existing submission route.
- A single source-of-truth rule for the invoice record, agreed in writing
- Field mapping from ERP, CRM or billing data to what your submission route requires
- Pre-submission checks so incomplete records are stopped and explained
- A rejected-document queue with a named owner and a retry path
- A log linking each internal record to the document reference returned
What needs technical review or custom scope
Whether your ERP or invoicing tool exposes an API, a webhook or only file export decides the shape of the integration. Connections are scoped per project, through an API or webhook where the system supports it, after technical review. This is not a prebuilt connector, and older systems may need custom scope that we describe before you commit.
What we do not do
LATYNEX is not a KSeF integrator or certified provider, does not submit invoices for you, does not give tax advice and does not deliver in Polish. Do not read any date on this page as guidance for your company; confirm your own timing with your tax adviser.
How delivery actually works
LATYNEX Digital has no office in Kraków and does not claim one. We work with Kraków businesses remotely, over video calls and written updates, in English, with the same team and process as in every other market.
Questions
Do you have an office in Kraków?+
No. We work with businesses in Kraków remotely, over video calls and written updates, in English, and we do not imply a local presence.
Are you a KSeF integrator or certified provider?+
No. LATYNEX prepares and routes invoice data between your systems. Submission stays with the invoicing tool or provider you already use.
When does KSeF apply to my company?+
As published, it applies in phases during 2026 and from 1 January 2027 for micro-entrepreneurs. We do not give tax advice; confirm your own position with your tax or legal adviser.
Is the integration a ready-made connector?+
No. Each integration is scoped per project, through an API or webhook where the system supports it, after technical review.
How are you invoiced, and in what currency?+
In EUR, by Latynex Trade OÜ, a company registered in Estonia (EU). Tax treatment for a client in Poland is confirmed on the quote, and we do not give tax advice.
What happens next
- 01
We map the process and the tools
Where the work starts, what is done by hand, which systems are involved.
- 02
We pick the simplest reliable route
A platform, a workflow or a little custom code — whichever is simplest and safest for this outcome.
- 03
Scope and price in writing
One scope and one price for you to approve. Nothing starts before you agree.
- 04
We build it with failure handling
Retries, duplicate protection and a named person told when something breaks, in accounts you own.
- 05
Test, monitor, hand over
We check it against real cases, agree who watches it, and document how it works and what to do when it fails.
Who you would be working with
- Company · Who you would be working with
- LATYNEX Digital is a service line of Latynex Trade OÜ, a company registered in Estonia (EU). Contact: info@latynexdigital.com.
- How we work · Delivery
- Remote, in English, with the person who would run the project. No local office is implied in any market.
- How we work · Commercial terms
- One scope and one price, agreed in writing before work starts. Your accounts, code and domain stay yours; any access we use is granted by you and can be withdrawn.
There are no client case studies on this page, and none are implied. What LATYNEX has built and runs itself is on the portfolio, each system labelled by stage. Published prices are on the pricing page; anything not listed there is scoped and quoted after review.