Bring one client case
Poland · White-label partner delivery

Connect a foreign or custom ERP to KSeF 2.0.

We map the source invoice to FA(3), validate it, submit through the agreed KSeF integration path and return the KSeF reference and technical status to the partner's workflow.

First valid test invoice target: two working days after source access, representative data, KSeF test authorisation and a partner technical owner are ready.

The route

ERP → FA(3) → KSeF 2.0

KSeF provides public API documentation and integration/demo environments. Standard Polish ERP users often already have a native path. The better eurinvoice cases are foreign-group systems, custom software, unusual Business Central or NetSuite data, and partners with several implementations in a queue.

Mandate status checked 26 September 2026. The staged obligation began in February and April 2026, with the micro-business stage on 1 January 2027. The Ministry announced that penalties for KSeF errors remain deferred through the end of 2027.

What the partner owns

  • Client contract, ERP-side configuration and source-data quality
  • KSeF authorisation, token/certificate decisions and client approvals
  • Production cutover, operating users and tax-process decisions

What eurinvoice owns

  • Source-to-FA(3) mapping for the agreed invoice family
  • Schema/business validation and integration-environment submission
  • KSeF reference/status return and technical handover
Delivery sequence

Use the public test path before production.

01 · Confirm

Entity, authorisation, source system and representative invoice family.

02 · Map

Transform source fields and tax logic into FA(3).

03 · Submit

Validate and send through the selected KSeF integration path.

04 · Return

KSeF number, status or rejection detail to the source workflow.

Use us where the native Polish connector stops.

Bring a foreign ERP, custom software or partner backlog case. We will qualify it against the standard scope before work starts.

Bring one client case