Skip to content
django-nms
en

E-invoicing: KSeF (Poland)

Mandatory e-invoicing. Thousands of invoices. One button.

KSeF is Poland's national e-invoicing system, mandatory for businesses from 2026. django-nms issues invoices in the FA(3) schema and sends them in batches straight from the current-month invoice list. No external tool, no manual XML export. Other national platforms on request.

Book a demo with the KSeF sandbox Compliance reports
  • XAdES certificate or token authentication, separate per selling entity
  • Batch sessions of 100 invoices, statuses polled automatically
  • Offline mode when the platform is down: invoice with a type II QR code
FA(3)
current structured invoice schema
100
invoices per batch session
2 modes
of authentication: certificate or token
0
manual XML exports

From invoice to official number without leaving the panel

The system builds the full FA(3) context: seller and buyer with tax ID validation, EU VAT, VAT exemption legal basis, lines, VAT summary, payment method, settlement data and the date of the last payment from the ledger. For corrections: corrected rows against the original invoice.

After sending it stores the KSeF number, document hash and timestamp. The invoice is locked against editing and deletion. The number appears on the PDF as a verification QR code and in the tax reports.

  • Single (online) or batch sending, grouped per selling entity
  • Invoices for consumers without a tax ID (B2C) skipped automatically
  • Per-invoice errors visible in the sending statistics

A platform outage does not stop your invoicing

When KSeF returns a server error, django-nms switches to offline mode. The invoice gets a type II QR code signed with the offline certificate (RSA-PSS or ECDSA) and the XML waits for resending. The customer receives the invoice on time, you stay compliant.

  • Type II offline certificate stored per selling entity, passwords encrypted
  • Test and production environments switched by configuration
  • Official acknowledgement (UPO) download: on the roadmap

E-invoicing the ISP way

What separates telecom billing from invoicing in an office.

  • Scale

    Hundreds or thousands of invoices on the first of the month. Sending in the background job queue, without blocking the panel.

  • Multiple sellers

    Every company or brand has its own credentials and prefix. One run handles all of them.

  • Immutability

    Once an official number is assigned, invoice fields and lines are locked. Changes only through a correction.

  • Corrections

    A corrective invoice references the original e-invoice number and follows the same sending path.

  • Tax reports

    E-invoice number and marker in the JPK tax files.

  • Planned

    Acknowledgements and purchase invoices

    UPO download and inbound invoice retrieval. On the roadmap.

E-invoicing questions

Do you send invoices for private individuals?

Invoices for buyers without a tax ID are skipped in the KSeF run, as the regulation requires. They still receive the PDF by e-mail.

What about the official acknowledgement (UPO)?

The system stores the KSeF number and document hash. UPO download and archiving are on the roadmap for the coming quarters.

Can I test against the KSeF sandbox?

Yes, the TEST environment is the default in development configuration. On the demo we show a full sandbox run.

Check e-invoicing on a test invoice

We will connect the KSeF sandbox and send an invoice with your seller data.

Book a demo See pricing