01 · FLAGSHIP

Polish Compliance Tooling

KSeF, JPK, GDPR, e-Doręczenia — native integration with Polish regulatory infrastructure.

Real client problem this solves

A mid-sized Polish manufacturer faces the April 2026 KSeF deadline. Their existing ERP was custom-built 8 years ago by a long-departed contractor. Comarch quoted 280k PLN for full migration to their system. SAP proposed 600k for a greenfield implementation. The internal IT team estimated 9 months and 2 senior developers to integrate KSeF themselves.

The real problem: compliance is binary. On April 1st you either submit invoices to KSeF or you cannot legally invoice. Migration risk: months of testing plus uncertainty plus dual-running cost. Internal-build risk: timeline slip, KSeF spec changes, missing the deadline.

Our approach: a KSeF integration layer that talks directly to the Ministry of Finance API and to the existing ERP through a small adapter. 6-week pilot. The existing ERP stays. Compliance achieved without migration. Audit trail intact. Future ERP migration optional.

Why Polish compliance is hard

The KSeF API has more than 200 schema validation rules. Reject reasons return as Polish-only error codes. UPO confirmation timing varies between minutes and hours. Retry logic must handle network failures without ever submitting an invoice twice. Most ERP connectors handle the happy path and break at quarter-end.

Beyond the protocol: real businesses also need JPK_V7M generation, GDPR data subject request flows, e-Doręczenia integration, multi-currency invoicing and an audit trail a compliance officer can actually use. None of that comes in a single box.

From April 2026 every Polish VAT taxpayer must use KSeF. There is no opt-out, no grace period for late connectors. We treat compliance as a system, not a checkbox.

What we deliver

KSeF outbound

FA(3) XML build, schema pre-validation, signed submission, retry queue with deduplication.

KSeF inbound

Periodic fetch of received invoices, normalization, persistence, downstream hooks.

JPK_V7M

Monthly generation from your invoice ledger, reconciliation against KSeF UPO, ready-to-submit XML.

GDPR data flows

Data subject request handling, export, redaction, retention policies. RODO-aligned audit trail.

e-Doręczenia

ePUAP-style mailbox integration once obligation lands. Outbound and inbound.

Multi-currency

PLN, EUR, USD invoices with NBP rate snapshotting, conversion at issue date, accounting export.

Tech we use

Backend

Python 3.11+ · FastAPI · SQLAlchemy

KSeF integration

Ministry of Finance API direct · No intermediaries

Document layer

FA(3) XML · lxml validation · canonicalization

Signing

Qualified certificates · Token authentication · KSeF session lifecycle

Typical engagement

Week 1

Discovery

Audit your current invoicing flow, ERP connectors, certificate setup.

Weeks 2–6

Pilot build

KSeF outbound + inbound on real data. UAT in DEMO env, then production cutover.

Week 7

Production deploy

Live deployment, monitoring, runbook handover, training session.

Why not just use Comarch or SAP?

Comarch and SAP make sense when you are already running their stack or when you genuinely need a full ERP. They bring deep modules — accounting, HR, supply chain — that we do not pretend to offer. If your roadmap is 'replace everything with one vendor', their pricing is not unreasonable.

Where they hurt is the in-between case: you need KSeF in 6 weeks, your ERP works, and you do not want a 12-month migration. Their model assumes you migrate. Ours assumes you don't. We integrate; they replace.

Pick them when migration is on your roadmap anyway. Pick us when KSeF is the immediate problem and your ERP is fine.